Search Issue Tracker
Fixed
Fixed in 6000.0.51f1, 6000.1.5f1, 6000.2.0b4, 6000.3.0a1, 7000.0.0a35
Votes
0
Found in
6000.0.46f1
6000.1.0b14
6000.2.0a8
6000.3.0a1
7000.0.0a27
Issue ID
UUM-102670
Regression
No
Startup Logs are missing in player logs when "Capture Startup logs" is enabled
Reproduction steps:
1. Open the attached project "LogProblemProj"
2. Enable “Capture Startup Logs“ (Edit > Project Settings > Player)
3. Build and Run
4. Observe the “Player.log“
Expected result: Player logs contain the usual startup logging information
Actual result: Player logs are empty
Reproducible with: 6000.0.46f1, 6000.1.0b14, 6000.2.0a8
Couldn’t test with: 2022.3.61f1 (no “Capture Startup Logs“ setting)
Reproducible on: Windows 11, macOS
Not reproducible on: No other environment tested
Notes:
After closing the player, shutdown operation logs are appended.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
Resolution Note (fix version 7000.0.0a35):
Modified the behavior to still log startup logs to their usual output (either the log file or the standard output) when the "Capture Startup Logs" option is enabled.
Resolution Note (fix version 6000.3.0a1):
Modified the behavior to still log startup logs to their usual output (either the log file or the standard output) when the "Capture Startup Logs" option is enabled.