Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2020.1.0a23
2020.3
2021.1
2021.2
2021.2.0b3
2022.1
Issue ID
1349737
Regression
Yes
Package import window's loading bar doesn't fit when Editor's and Package Manager's windows are on different scale monitors
How to reproduce:
1. In dual monitor setup set one monitor's scale to 125% (Right-click on desktop->Display Settings), and the other monitor's scale to 100%
2. Create a new Unity project
3. Move the Editor to the 125% scale monitor
4. Open the Package Manager (Window->Package Manager)
5. Move the Package Manager to the 100% scale monitor
6. Download ProBuilder package in Package Manager
7. Observe the import loading window on the Editor's monitor
Expected results: The loading bar fits correctly in the import window
Actual results: The loading bar is too long/short for the import window
Reproducible with: 2020.1.0a23, 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a5
Not reproducible with: 2019.4.29f1, 2020.1.0a22
Notes:
- Depending on different scale differences some different results occur:
The loading bar is too short
The loading bar is too long (doesn't fit into the window)
The text is cut off and moved slightly on the loading bar
- I was not able to reproduce the issue with any other loading/import window
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 2022.1):
Fixed in Unity 2022.1.0a14