Search Issue Tracker
Fixed in 2018.2.X
Won't Fix in 2018.1.X
Votes
9
Found in
5.2.0f3
Issue ID
730221
Regression
No
Standalone remembers last resolution setting without user action; bad interaction with Default Native Resolution
Steps to reproduce:
1. Open the attached project
2. Check the 'Player Settings', make sure these are set on 'Resolution and Presentation' tab:
'Default Is Fullscreen' - enabled
'Default Is Native Resolution' - enabled
'Display Resolution Dialog' - 'Hidden by default' or 'Disabled'
3. Build and run the application
4. Notice everything is as expected
5. Change your screen resolution to smaller (e.g. 800x600)
6. Run the built application again, notice it sets the resolution to 800x600 as well
7. Now switch back your screen resolution to native resolution
8. Run the built application again, notcie it still sets the resolution of the player to 800x600 even though the resolution has changed back to native
Note: After the bug occurs, even if you rebuild the application, it still shows at the changed resolution (in this case 800x600).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mouse looping to the other side of the screen when dragging tabs after clicking on the Scene view window
- Editor Window contents are not visible when opening it up
- Gamma bleeding and banding when low light baked in VR scene
- A WebGL build with complex shaders has a performance drop when tapping the screen
- No MipMaps are created when using "UnityWebRequestTexture.GetTexture"
Add comment