Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2019.3.0f6
2020.1
Issue ID
1216508
Regression
No
Default Is Native Resolution is ignored when Fullscreen Mode has been changed
Reproduction steps:
1. Open attached project "1216508_resolution"
2. Go to Edit > Project Settings > Player > Resolution and Presentation
3. Set Fullscreen Mode to Windowed, Default Screen Width and Height to 640X480
4. Got to File > Build And Run
5. In the Player settings, change Fullscreen Mode to Fullscreen Window (Default Is Native Resolution becomes checked automatically)
6. Got to File > Build And Run
Expected result: Build is run in default native resolution
Actual result: Build is run in previously chosen resolution (640X480)
Reproducible with: 2017.4.36f1, 2018.4.17f1, 2019.2.21f1, 2019.3.1f1, 2020.1.0a22
Workarounds:
Building in Fullscreen Window Mode with Default Is Native Resolution unchecked and then building again with it checked
Setting Default Screen Width and Height to the wanted resolution
Note:
Following these steps in 2017.4 build is not in Windowed Mode when Default Is Full Screen option is disabled but the issue still persists
Comments (1)
-
vsertich
Mar 18, 2020 16:52
This is happening to me in Unity 2018.2.4f1.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a24
Resolution Note (fix version 2019.3):
Fixed in 2019.3.8f1