Search Issue Tracker
By Design
Votes
0
Found in
2018.2.21f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1134393
Regression
No
Resolution does not change to custom one if you disable "Display Resolution Dialog" after selecting resolution in it
Steps to reproduce:
1. Open a new project
2. Build setting -> Player settings
3. Change Fullscreen Mode to "Windowed", set a custom resolution and disable "Display Resolution Dialog"
4. Build and Run, observe that game launched in a custom resolution
5. Go back to Player settings and enable "Display Resolution Dialog", Build and Run again.
6. Launch a game in some resolution (doesn't really matter)
7. Go back to Player settings and disable "Display Resolution Dialog", Build and Run again.
Expected result: Game launches in the custom resolution again.
Actual result: Game launches in the resolution that was previously set in "Display Resolution Dialog".
Reproduced in: 2017.4.24f1, 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note (2019.3.X):
This happens because game saves resolution state in player preferences and uses that on second launch.