Search Issue Tracker
Fixed
Fixed in 6000.0.51f1, 6000.1.7f1, 6000.2.0a10, 7000.0.0a28
Votes
0
Found in
6000.0.46f1
6000.1.0b14
6000.2.0a8
7000.0.0a1
Issue ID
UUM-102920
Regression
Yes
Progress bar defaults to main monitor when Editor is on secondary monitor
How to reproduce:
1. Open the Editor on the secondary monitor
2. Right-click in the Project window and select Reimport
3. Observe the progress bar location
Expected result: Progress bar appears on the same monitor as the Editor
Actual result: Progress bar appears on the main monitor
Reproducible with: 6000.0.13f1, 6000.0.46f1, 6000.1.0b14, 6000.2.0a8
Not reproducible with: 2021.3.50f1, 2022.3.61f1, 6000.0.12f1
Reproducible on: macOS 15.3.2 (M1 Max)
Not reproducible on: Windows 11
Workaround: If you drag the progress bar to the secondary monitor, triggering it again will make it appear on the secondary monitor. This behaviour is reset if you close and reopen the Editor.
Note: Issue is also reproducible by modifying a Script causing a domain reload
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
- [Quality Hackweek] Activated Terrain Inspector is active only until the terrain GameObject is deselected when two or more Inspectors are open
- Physics Used Memory keeps growing when GameObject colliders are enabled and disabled
- Errors are thrown and Inspector's UI element is not drawing when a GameObject with script component using a List<T> attached is selected
- ConfigurableJoint's parameters are not saved in the Prefab after Runtime Prefab baking
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
Resolution Note (fix version 7000.0.0a28):
Verified the fix has landed to 7000.0.a28 with macOS Sequoia 15.5
Resolution Note (fix version 6000.2.0a10):
Verified the fix has landed to 6000.2.0a10 in macOS Sequoia 15.3