Packaged Build Shows No Cooking Warnings Despite LogFileVerbosity=Error
22.5K reputation · 04 Oct 2020, 11:55 UTC
Goal
Determine why a packaged Unreal Engine build that fails to launch does not display expected cooking‑related warnings in the platform log when LogFileVerbosity=Error is set in Engine.ini.
Constraints and uncertainty
Although the LogFileVerbosity setting suppresses informational and warning messages, certain internal subsystems continue to emit diagnostics at the Display level, obscuring the root cause. It is unclear which ini sections govern this Display‑level output and whether a global override exists that respects the Error level without silencing critical error reports.
Which ini sections control Display‑level logging for core subsystems? How can Display‑level verbosity be globally suppressed while preserving essential error messages? Is there a documented method to force all logging to honor LogFileVerbosity=Error?