Search Issue Tracker
Fixed
Fixed in 2022.3.66f1, 6000.0.55f1, 6000.1.14f1, 6000.2.0b12, 6000.3.0a3
Votes
0
Found in
2022.3.64f1
6000.0.52f1
6000.1.9f1
6000.2.0b8
6000.3.0a1
Issue ID
UUM-110840
Regression
Yes
[Mac] MainWindow doesn't appear on monitor where last closed during Launch
How to reproduce:
1. Create and Open a new project in Unity Hub
2. Drag the opened project to a different monitor than Unity Hub
3. Close the project
4. Reopen the project from Unity Hub (Keep your mouse cursor on the same screen)
5. Observe the monitors and where the Editor opens
Expected result: The Editor opens on the monitor where it was closed
Actual result: The Editor opens on the screen on which the mouse cursor is located
Reproducible with: 2022.3.62f1, 2022.3.64f1, 6000.0.49f1, 6000.0.52f1, 6000.1.9f1, 6000.2.0b8, 6000.3.0a1
Not Reproducible With: 2021.3.53f1, 2022.3.61f1 (6c53ebaf375d), 6000.0.48f1
Reproducible on: MacOS 15.5 (Silicon)
Not Reproducible On: Windows 11
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 6000.3.0a3):
Verified the fix has landed to 6000.3.0a3 using macOS 15.5 M4
Resolution Note (fix version 6000.2.0b12):
Verified the fix has landed to 6000.2.0b13 using macos 15.5 M4
Resolution Note (fix version 6000.1.14f1):
Verified the fix has landed to 6000.1.15f1 using macOS 15.5 M4
Resolution Note (fix version 6000.0.55f1):
Verified the fix has landed to 6000.0.55f1 using macOS 15.5 M4