Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2019.4
2020.2.1f1
2020.3
2021.1
2021.2
Issue ID
1309804
Regression
No
Unity Player doesn't scale to match Screen Resolution correctly when moving between Screens
Reproduction steps:
1. Open user attached Project
2. Build the Game
3. Open the Player in Windowed mode
4. Move the Window to a different screen
Expected result: Everything is scaled to be the same size relative to screen size
Actual result: Some of the elements change scale, like the Window Title Bar and the build version info at bottom right corner
Reproducible with: 2019.4.24f1, 2020.3.5f1, 2021.1.3f1, 2021.2.0a12
Notes: Best observed with different resolution and display scaling on the screens
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a19
The fix for the scaling issue is to update the DPI Awareness of the WindowsPlayer which informs Windows to perform the proper DPI scaling.
This setting can be applied manually (don't have to wait for fix to be released) by editing the "WindowsPlayer.manifest" located in:
<UnityInstal>\Data\PlaybackEngines\windowsstandalonesupport\Source\WindowsPlayer\WindowsPlayer\WindowsPlayer.manifest
Change the <WindowsSettings> content block to this:
<windowsSettings>
<dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">True/PM</dpiAware>
<dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2</dpiAwareness>
</windowsSettings>
NOTE: The PerMonitorV2 setting is only supported on Windows 10 builds 1703 and later (ignored on earlier builds of Windows 10). For more info on Windows High DPI support see: https://docs.microsoft.com/en-us/windows/win32/hidpi/high-dpi-desktop-application-development-on-windows?redirectedfrom=MSDN
The other issue, app Window is 1/4 original size when relaunching on 4K display, is being fixed as part of other quality improvement work and isn't part of this fix. That is, setting the DPIAwarness won't address this specific problem.