Search Issue Tracker
Fixed in 2021.1.X
Votes
2
Found in
2020.2.0b2
2020.2.1f1
2021.1
Issue ID
1302708
Regression
Yes
The cursor doesn't lock or become invisible with CursorLockMode.Locked method when entering the Play Mode after the first time
How to reproduce:
1. Open the user's attached "Test4" project
2. Open the Scene "SampleScene"
3. Enter the Play Mode
4. Exit the Play Mode
5. Enter the Play Mode
Expected results: The cursor becomes invisible and is locked
Actual results: The cursor stays visible and doesn't lock
Reproducible with: 2020.2.0b2, 2020.2.1f1, 2021.1.0b1
Not reproducible with: 2018.4.30f1, 2019.4.17f1, 2020.1.17f1, 2020.2.0b1
Notes:
- Pressing on the Game view will make the cursor invisible and lock it
- The issue is also reproducible with the "Cursor.visible = false" method, the cursor will not become invisible
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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Resolution Note (fix version 2021.1):
Fixes cursor lock and hide when entering playmode. Currently the cursor locks/hides on entering playmode the first time; every other time it hides but does NOT lock until you unhide (e.g. press escape) and then click in the gameview.
Fixed in 2021.2.0a11
This does not affect the build player.
Resolution Note (fix version 2021.1):
Fixed in 2021,1,17f1
After regression fix, you need to click on game view to make it invisible instead of hovering on game view.