Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.48f1
2021.3.25f1
2022.2.19f1
2023.1.0b16
2023.2.0a14
Issue ID
UUM-37086
Regression
No
With specific Windows 10 settings, the player window resolution does not match the values passed into Screen.SetResolution()
Reproduction steps:
1. Open the attached project “ResolutionMismatch”
2. Open Scene “Assets/Scenes/DemoScene.unity”
3. Open Display settings by right-clicking on the desktop and selecting “Display Settings”
4 Configure settings so that one screen has 100% scale and the other one has 150%
5. Build and run the project by selecting File > Build And Run
6. Move the Player window to the screen that is not the primary one.
7. To set the resolution of the window, click on the “1920x1080” button
8. Observe the “Expected Resolution” window in the bottom right corner of the Player
Expected result: “Unity Reported Resolution” and “Windows Reported Resolution” are both set to 1920x1080 resolution
Actual result: “Windows Reported Resolution” is set to 1914x1063
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.19f1, 2023.1.0b16, 2023.2.0a14
Reproducible on: Windows 10
Note: “Windows Reported Resolution” not being the desired resolution, indicates that the window itself is not the correct size
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 your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.