Search Issue Tracker
Fixed in 2018.3.X
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
- Deselected Game View is rendered incorrectly when resizing Game View window in two Game View window setup
- [macOS] Color picker preview shows colorful pixels when cursor is dragged on the sides of the screen
- Intensity parameter ignores Culling Mask causing incorrect lightning when additional lights are disabled
- Input.GetKeyUp is true only for the first released mouse button when releasing mouse buttons outside the Game view
- Physics objects trip and/or jump when colliding with other colliders
Add comment