Search Issue Tracker
By Design
Votes
0
Found in
2022.3.4f1
Issue ID
UUM-42430
Regression
Yes
Game view scale is set to 1.3x by default when monitor display resolution is higher than 1920x1200
How to reproduce:
1. Open any Unity project
2. Open Game view
Expected result: Game view scale set to 1x and can be lowered
Actual result: Game view scale set to 1.3x and can’t be lowered
Reproducible with: 2022.3.0f1, 2022.3.4f1
Not reproducible with: 2021.3.27f1, 2022.2.21f1, 2023.1.2f1, 2023.2.0a21
Reproduced on: Windows 10, macOS 13.2.1 (intel)
Note: macOS is set to 2x by default
Workaround: Toggling off Low Resolution Aspect Ratios will allow to go below the default minimum
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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Resolution Note:
Hi, the Game view scale being set to 1.3x is not a result of your monitor display resolution but rather your system display scale being 125% (you can find this on Windows from Settings -> Display -> Scale). It has always been the behaviour of the Game view scale that it would clamp its lower bound to the system display scale when Low Resolution Aspect Ratios is toggled on (in the resolution dropdown of the Game view). Previously, there was a bug where this clamping would only happen for integer values. This isn't an issue on MacOS systems where display scales are always fixed to 1 or 2, but Windows can have non-integer values for display scales (e.g. 1.25 for 125%, 1.5 for 150%). These non-integer display scales caused the Game view to have big borders around the game. By clamping the lower bound of the Game view scale to match the display scale, we are ensuring that the Game view does not have borders causing the game to render in a small region than desired. This should not cause any visual distortions - the game is simply being rendered at a lower resolution then being scaled to fit in a bigger window. This has been existing behaviour for all integer display scales (e.g. 2x or 200%).