Search Issue Tracker
Duplicate
Votes
2
Found in
5.6.0f3
Issue ID
903834
Regression
No
Running editor in batchmode with -logFile parameter and no address does not output any log to console
Steps to reproduce:
1. Download and extract the project attached
2. Open Command Prompt
3. Run Unity.exe with these command line arguments: -batchmode -projectPath "<path to project>" -buildWindows64Player "Test.exe" - logFile -quit
Expected result: Since there's no path specified for a log file, the log should be printed out in the console.
Actual result: log isn't printed anywhere
Reproduced on: 5.5.2p4, 5.6.0f3, 2017.1.0b1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
This is a duplicate of issue #900754