Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.4.0p1
Issue ID
823993
Regression
Yes
Launching Unity from command prompt ignores command line arguments when Unity.exe is excluded from the path quotes
Reproduction steps:
1. Open the Command prompt
2. Call "C:\Program Files\Unity 5.4.1p1\Editor\"Unity.exe -batchmode
Note: Calling "C:\Program Files\Unity 5.4.1p1\Editor\Unity.exe" -batchmode works just fine.
Actual result: Unity opens with project selection UI
Expected result: Unity opens without a project selection UI
Reproducible on: 5.5.0b3, 5.4.1p1
Not reproducible on: 5.3.6p4, 5.3.5p4, 5.2.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- WaitForEndOfFrame does not work when the Game view is not visible
- Unity Events added to a ScriptableObject are not invoked if they are added in Edit mode and their Call State is set to "Runtime Only"
- The Visual Effect GPU Event is forced into sleep until another Event is sent when the visual effect consists of two particle systems that communicate with Trigger Event set to On Die
- Nativeplugin Vulkan image gets deleted while in use and AccessTexture returns an invalid texture causing a crash or corruption when QualitySettings.anisotropicFiltering is called
- Error "DllNotFoundException: __Internal assembly:<unknown assembly> type:<unknown type> member:(null)" when attaching a managed debugger for the build of a specific project with Mono Scripting Backend
Add comment