Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.1.0p2
Issue ID
955811
Regression
Yes
Launching Unity from Command prompt without batchmode results debug output to console in Windowed mode
How to reproduce:
1. Open Command Prompt
2. Launch Unity editor from a Command prompt(e.g "pathToUnity\Unity.exe" -projectPath "pathToAnyProject")
-- Unity editor should start and console doesn't wait as expected
3. Close Unity Editor
--Random output is written
Expected result: The Editor should either run a Windowed application (so no stdout output), or a Console application (with possible stdout output).
Actual result: The result is a mixture of Windowed application which still runs when Editor is launched but after closing Editor output is written.
Regression first introduced in: 5.5.1p2
Reproducible with: 5.5.1p2, 5.5.3p2, 5.5.4p2, 5.6.1f1, 5.6.3p4, 2017.1.0p2, 2017.1.1p3, 2017.2.0b11, 2017.3.0b2
Not reproducible with: 5.5.0a6, 5.5.1f1, 5.5.1p1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment