Packaged Build Shows No Cooking Warnings Despite LogFileVerbosity=Error

Question

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?

Tasadduq Burney · Answer

Answer
The LogFileVerbosity=Error setting only controls what is written to the log file (Saved/Logs). It does not filter messages sent to the console, debugger, or platform‑specific logs (e.g., Android logcat, iOS console). Cooking warnings are emitted through the LogCook category and, unless that category’s verbosity is also set to Error, they will still appear in those output streams even though the file contains only errors.
Likely explanation
In a packaged build the engine often redirects its logging to the platform’s output system. Because LogFileVerbosity does not affect that path, warnings can be visible there while the log file shows none. Additionally, a custom Build.cs or Target.cs that sets bSuppressCookingWarnings = true will hide cooking warnings regardless of ini settings.
Confirmed facts (based on engine behavior)

LogFileVerbosity applies only to file logging.
  Cooking messages use the LogCook logger; their visibility is governed by the verbosity of that category (or the root logger) and by command‑line overrides such as -logcook=Warning.
  From UE 4.22 onward the logging subsystem separates file and console verbosity, making the observed split expected.
  Platform‑specific log filters (e.g., Android logcat tag limits) can further hide warnings even if the engine emits them.

Steps to verify and resolve for this case

Check Engine.ini (or DefaultEngine.ini) for a [LogCook] section. Ensure it is either absent (defaults to Warning) or explicitly set to LogCook=Warning.
  Launch the packaged executable with a verbose flag, e.g., MyGame.exe -verbose or MyGame.exe -logcook=Warning, and capture the console or platform log.
  Inspect the Saved/Logs file; with LogFileVerbosity=Error it should contain only error lines, confirming the setting’s scope.
  If you see warnings in the console/platform log but not in the file, the behavior is as expected. To also suppress them from the console, add LogCook=Error to the ini or pass -logcook=Error on the command line.
  Search your project’s Build.cs and Target.cs for bSuppressCookingWarnings. If present and set to true, change it to false (or remove it) and re‑package.
  If after the above steps warnings still do not appear, note the target platform (Windows, Android, iOS, etc.) and check that platform’s log filter settings are not discarding the LogCook tag.

Missing diagnostic detail
If you are testing on a mobile or console platform, please specify which one; the answer may need to include platform‑specific log‑capture commands (e.g., adb logcat -s LogCook for Android).

Packaged Build Shows No Cooking Warnings Despite LogFileVerbosity=Error

Goal

Constraints and uncertainty

1 answer

0 question comments

Answer

Likely explanation

Confirmed facts (based on engine behavior)

Steps to verify and resolve for this case

Missing diagnostic detail

Your perspective belongs here.