Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
947500
Regression
No
Launching a build through command line with specific height and width results in incorrect res while Unity Splash Screen is on
Launching a build through the command line with specific height and width results in incorrect resolution while Unity Splash Screen is on
Reproduction steps:
1. Open "Half-LifeSharp.zip" project
2. Build For Windows Standalone
3. Launch through command line with: -w 800 -h 600
4. See the Resolution of the application
5. Exit and Re-Launch with: -w 1920 -h 1080
Expected Result: Both times the Splash Screen should be the specified Resolution
Actual Result: the Splash Screens resolution is the last used one, not the specified one on launch
Reproduced with: 2017.2.0f1, 2017.1.1p3, 5.5.4p5
Did not reproduce on: 2017.3.0b1 (Doesn't seem to pass the Splash Screen), 5.6.3p4 (Crashes)
Note:
Launch through command line: *.exe Directory* -w xxxx -h yyyy
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
- Timeline section stops rendering after restoring Profiler Window modules
- Cursor image does not update when Cursor.SetCursor is called again with CursorMode.Auto
- Crash on do_runtime_invoke when reopening a specific project after failing to build it
- Animations change speed when rigidbody is added
- Low FPS persists when re-entering Play mode after an extended session in a specific project
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.