Search Issue Tracker
Fixed in 2019.1.X
Votes
29
Found in
5.6.0f3
Issue ID
900754
Regression
No
Command line -logFile with no parameters outputs to screen on OS X but not on Windows
Steps to reproduce:
1. Find attached project in command line Windows
2. Launch Unity with parameters -batchmode -quit -logFile
3. Notice that in -logFile we didn't input any path for the log file to be saved
4. Observe nothing being output
5. Repeat process in terminal on Mac OS
6. Observe logFile being output to terminal
Expected behaviour: The command should function the same on both Mac OS and Windows
Actual behaviour: No output in Windows, while Mac OS outputs the logFile to the terminal
Reproduces on 2017.1.0b1, 5.6.0f3, 5.6.0f2, 5.5.3p1
Notes: This behaviour is likely due to no handlers existing for -logFile command with no parameters.
Notes: The output is written in Windows, but it defaults to a location that the user probably doesn't expect: %LOCALAPPDATA%\Unity\Editor.
-
Resolution Note (fix version 2019.1):
Logging now defaults to stdout on all platforms when running in batchmode. Note that on Windows, this still means output won't go to console by default as Windows applications don't have stdout handle by default. Output will, however, go to stdout if you launch Unity with a valid stdout handle. I.e. launching as a child process of a build system with redirected handles
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
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
- Editor crashes after entering long Asset name and pressing "Force Quit" in "Moving file failed" pop-up
- Long strings are not truncated in the Assistant search results list
Juixa
Sep 28, 2018
Hey, here is a response from dev team:
"It has been on our radar for quite some time. Unfortunately the current situation with priorities is such that we might not have the bandwidth to address this issue until at least 19.1+."