Search Issue Tracker
Duplicate
Duplicate in 5.6.X
Votes
0
Found in
5.6.2p4
Issue ID
935251
Regression
Yes
"Default Is Native Resolution" player setting in FullScreen on Windows Standalone Platform is not working
How to reproduce:
1. Open the"Resolution" project
2. Open the "MainScene" scene
3. Build the project with preset resolution, "Default Is Full Screen" checked and "Display Resolution Dialog" disabled
4. Open the built project
5. Press "Clear PlayerPrefs", now the data stored in registries (Including information about resolution) is deleted
6. Press escape to exit
7. Build the project again, now with "Default is Native Resolution" checked
8. Open the built project, the resolution is the same as before
Expected result: The game resolution sets to the monitor's resolution.
Actual result: The game resolution sets to the previous resolution it used.
Reproducible with: 5.6.3f1, 5.6.1p1, 5.6.0p1.
Regression introduced in: 5.6.0p1.
Not Reproducible with: 2017.3.0a2, 2017.2.0b5, 2017.1.0p1, 5.6.0f3, 5.5.4p2.
Note: In the gif, it is shown that registry data is deleted and the built project is set with native resolution.
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
This is a duplicate of issue #908932