Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2022.3.7f1, 2023.1.7f1, 2023.2.0b3, 2023.3.0a1, 2024.1.0a1
Votes
0
Found in
2021.3.27f1
2022.3.4f1
2023.1.2f1
2023.2.0a21
2023.3.0a1
Issue ID
UUM-41799
Regression
No
Player Window resolution is slightly skewed when using multiple displays and one of them has a different scaling value
How to reproduce:
1. Make sure that 2 monitors are used
2. Make sure that display 2 has a scaling of more than 100%
3. Open the “OpenCloseApplicationTest“ project
4. Open the “SampleScene“
5. Build And Run project in display 1
6. Move the Player window from display 1 to display 2, then close the Player
7. Run the Player again and observe the resolution text
8. Move the Player window slightly to any direction but not outside of display 2
9. Observe the resolution text
Expected result: the resolution text is the same as in step 7
Actual result: the resolution text is not the same as in step 7
Reproduced with: 2021.3.27f1, 2022.3.4f1, 2023.1.2f1, 2023.2.0a21
Reproduced on: Windows 11
Could not test on: macOS Monterey 12.2 (Player is always built to the same display the Editor is located in)
Notes:
1. Not reproducible when scaling of both monitors are set to 100%
2. To change the scaling of display 2 on Windows 11 open Settings > System > Display, select the display, locate the “Scale & layout” section, and change the “Scale” value
3. This issue was also tested on macOS - the reproduction steps are different since Build And Run opens the Player on the screen where the Editor is. Moving the Player window from a scaled display to an unscaled display just changes the resolution of the Player which is expected from the operating system side
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.3.0a1):
Editor: Fix edge case with the Windows Player where an incorrect resolution is used and reported by Screen.width and Screen.height. This occurred when the player was started on a monitor with different DPI settings compared to the main windows monitor.
Resolution Note (fix version 2023.2.0b3):
Editor: Fix edge case with the Windows Player where an incorrect resolution is used and reported by Screen.width and Screen.height. This occurred when the player was started on a monitor with different DPI settings compared to the main windows monitor.
Resolution Note (fix version 2023.1.7f1):
Editor: Fix edge case with the Windows Player where an incorrect resolution is used and reported by Screen.width and Screen.height. This occurred when the player was started on a monitor with different DPI settings compared to the main windows monitor.
Resolution Note (fix version 2022.3.7f1):
Editor: Fix edge case with the Windows Player where an incorrect resolution is used and reported by Screen.width and Screen.height. This occurred when the player was started on a monitor with different DPI settings compared to the main windows monitor.
Resolution Note (fix version 2021.3.30f1):
Editor: Fix edge case with the Windows Player where an incorrect resolution is used and reported by Screen.width and Screen.height. This occurred when the player was started on a monitor with different DPI settings compared to the main windows monitor.