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
- GUISkin background is displayed in lighter colors in the Game view than in the Preview or Icon
- Selection of multi-select ListView is changed when interacting with child element in an EditorWindow
- [Android] The '-' symbol is not allowed to be entered when entering a negative number in an InputField when the Content Type is set to Integer Number
- [Android] Crash due to null pointer dereference when UnityPlayer.UnitySendMessage() is called in onCreate
- DepthNormalPrepass or DrawDepthNormalPrepass is rendered when using the Decal renderer feature with “Technique: Screen Space” and “Use Rendering Layers”
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