Search Issue Tracker
Fixed
Fixed in 6000.4.0a5, 6000.5.0a1
Votes
5
Found in
6000.4.0a3
6000.5.0a1
Issue ID
UUM-122498
Regression
Yes
[WinEditor] UI Scaling is incorrect when a custom scale is set in "Use custom scaling value"
Reproduction steps:
1. Make sure the monitor has a Scale higher than 100%
2. Create and open any project
3. Go to Edit > Preferences > UI Scaling
4. Uncheck “Use default desktop setting” property
5. Change the “Use custom scaling value” dropdown to any other value
6. Restart the Editor
7. Repeat 3rd step and observe the “Current scaling” value
Expected result: The previously set scaling value matches the “Current scaling” value
Actual result: The “Current scaling” value is higher than previously selected value (result varies depending on the monitor Scale value)
Reproducible with: 6000.4.0a2, 6000.4.0a3
Not reproducible with: 6000.0.60f1, 6000.2.8f1, 6000.3.0b7, 6000.4.0a1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note:
- Does not reproduce if the monitor Scale is set to 100%, but reproduces with all higher percentages. For example, if the monitor Scale is set to 200% the scaling in the Editor will be 2 times bigger, if 300% - 3 times bigger and etc.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 6000.4.0a5):
Verified the fix has landed to 6000.4.0a5 using Windows 11