Search Issue Tracker
Fixed
Fixed in 2021.3.26f1, 2022.2.18f1, 2023.1.0b1
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.1.14f1
2022.2.0b6
2023.1.0a6
Issue ID
UUM-14913
Regression
No
1px mismatch between reported Screen size and actual back buffer size when changing Display Scale
How to reproduce:
1. Open the attached user project
2. Open Scene “SampleScene“ & enter play in editor
3. In OS display settings set scale to 125%
4. Disable "Low Resolution Aspect Ratios" in the Game View
5. Change the Aspect ratios around, sometimes it may also require to you to change the screen lay-out by simply resizing the gameview window.
Expected result: No errors appear in the Console
Actual result: “game view dimensions don’t match Screen dimensions“ errors appear in the Console
> Note for this bug these errors continuously appear every frame vs only occasionally when resizing (which is caused by bad timing of the user code)
Reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0b6, 2023.1.0a6
Reproduced on: Windows 11 (21H2)
Note: Scene View needs to be on the same Display as where the settings were changed
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
- A vertical graphical artifact appears on Android Player when clearing Z & Stencil Buffer and running with OpenGLES3 Graphics API
- Player crashes when built with IL2CPP Scripting backend
- TextMeshPro package throws multiple Shader errors when importing TMP Essential Resources
- Package Manager search text field has no validation and leads to Editor freezes
- PlayerLoop.SetPlayerLoop() function is ignored when playing game in Player
Resolution Note:
This is a duplicate issues. It is currently being fixed. Progress can be tracked using https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-14913
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-14913