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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
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