Search Issue Tracker
In Progress
In Progress in 6000.0.X, 6000.1.X
Fixed in 6000.2.0a10
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
- Image is distorted when VisualElement is scaled and Scale Mode set to scale-and-crop
- Euler angles return different values during Animation Event when using Playables API and the time is 0
- Editor is frozen on "Reloading Domain" when entering Play Mode for the second time using Socket.Poll(-1, ...)
- Empty GameObjects are created without Skinned Mesh Renderers when using AnimatorUtility.DeoptimizeHierarchy() on FBX files with same-named GameObjects
- Snapshots don't work for exposed parameters after using SetFloat
Resolution Note (fix version 6000.2.0a10):
Verified the fix has landed to 6000.2.0a10 in macOS Sequoia 15.3