Search Issue Tracker
Fixed in 2018.3
Votes
0
Found in
2018.2.0a2
Issue ID
1006813
Regression
No
[OSX] Cursor does not break Cursor.lockState and become visible on CMD+Q command
Steps to reproduce:
1. Open attached “FPSController.zip” Unity project
2. Open “Main” scene
3. Change object order in Hierarchy to dirty the scene
4. Enter Play mode
5. Press CMD+Q
Expected results:
Cursor becomes visible and you are able to navigate in the save dialog using the cursor
Actual results:
Cursor remains locked and invisible and you are not able to navigate in the save dialog using the cursor
Reproduced in: 2018.2.0a2, 2018.1.0b9, 2017.3.1p2, 2017.2.2f1, 2017.2.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- AssetDatabase is overwriting GUIDs
- Packages cannot be added from a registry that returns invalid publish dates [Windows-only]
- [PLM] OpenRL 501 error is thrown/editor crashes when baking 4K lightmaps with 16 lightmap AA samples
- Physics.SyncColliderTransforms syncs every collider when the local position hasn't changed
- [GPU PLM] Part of baked shadows are broken when hitting a backface
Add comment