Search Issue Tracker
Won't Fix
Votes
0
Found in
Issue ID
1073162
Regression
No
[OSX Editor] During Playmode, the cursor does not unlock for several windows called out through shortcut.
If the project has cursor lock during play, the user cannot regain control after calling out a window during Playmode.
This happens to windows that are external to Unity. For example, if user call out Build Setting window, which is a native Unity Editor window, the cursor unlocks and everything works well. If user chooses CMD + B (Build...), and a Mac system window shows up, asking for save location and file name, the cursor remains locked.
List of the same situations during Playmode:
- Build (CMD + B)
- Open (CMD + O)
- Calls out Mission Control (Three finger swipe up. See attached image for reference)
Repro:
1. Launch Unity and open the attached project
2. Open "Main" scene
3. Enter Playmode (make sure the cursor is locked in the game view)
4. Press CMD + B or any action from the list above
5. Try to use mouse and move the cursor.
Expected: Cursor is free to move when a window pops out in Playmode
Actual: Cursor does not unlock when a window shows up in Playmode
Similar bug: https://fogbugz.unity3d.com/f/cases/1006813/
And it is fixed in PR: https://ono.unity3d.com/unity/unity/pull-request/72586/_/platform/osx/fix-cursor-locked-on-exit
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note (2019.2.X):
This seems to be fairly uncommon scenario, does not meet the priority bar at the moment