Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0a13
2019.3.2f1
2020.1
2020.2
Issue ID
1223624
Regression
Yes
Running Unity with terminal and using -logFile does not provide stdout log
Reproduction steps:
1. Open terminal
2. Run Unity from the terminal (example path/to/Unity -quit -batchmode -logFile)
Expected result: Terminal logs out Unity actions
Actual result: Terminal does not log out anything
Reproduces on: 2019.1.0a13, 2019.3.3f1, 2020.1.0b1, 2020.2.0a2
Regression introduced: 2019.1.0a13
Does not reproduce: 2017.4.37f1, 2018.4.18f1, 2019.1.0a12
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note:
This change was made intentionally to align with other platforms. You now must specify "-logFile -" to get output to direct to stdout. See the documentation for more info: https://docs.unity3d.com/Manual/CommandLineArguments.html