Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
Issue ID
834325
Regression
No
Improve error handling for command line activation
Repro:
1. Attempt to activate Unity editor from command line (refer to https://docs.unity3d.com/Manual/CommandLineArguments.html)
2. During activation miss one of the arguments - e.g. -password, enter incorrect password
3. Observe that editor is not activated, it times out and there is no error message shown in the terminal window
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment