Search Issue Tracker
By Design
Votes
0
Found in
2021.3.35f1
2022.3.19f1
2023.2.9f1
2023.3.0b6
Issue ID
UUM-62711
Regression
No
Screen.SetResolution does not retain its value when the resolution is changed through Windows settings
How to reproduce:
1. Open the “resolution-change” project
2. Open the “SampleScene”
3. Build And Run
4. In the Player select “Full” and observe the text displayed in the first row
5. Change the system’s resolution
6. Observe the Player
Expected result: The Player’s resolution does not change
Actual result: The Player’s resolution changes
Reproduced with: 2021.3.35f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0b6
Reproduced on: Windows 11
Not reproduced on: macOS 13.5.2 (M1), Ubuntu 20.04
Note: Not reproducible in the Editor
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.