Search Issue Tracker
Fixed in 1.0.0
Votes
1
Found in [Package]
1.0.0
Issue ID
1265737
Regression
No
Cursors is still visible when entering the Play Mode using Cursor.lockState = CursorLockMode.Locked with Input System Package
How to reproduce:
1. Open user's attached "CursorCaptureTest3" project
2. Open the "SampleScene" Scene
3. Enter the Play Mode while the cursor is not in the Game view
Expected results: The cursor becomes invisible
Actual results: The cursor does not become invisible
Reproducible with: 2018.4.26f1, 2019.4.6f1, 2020.1.0f1, 2020.2.0a11 (0.1.2-preview, 1.0.0)
Not reproducible with: 2020.2.0a12, 2020.2.0a20 (0.1.2-preview, 1.0.0)
Notes:
- If the cursor is above the Game view when entering the Play Mode, the cursor will become invisible
- Happens only with the Input System package
- Only happens when the Active Input Handler setting is set to "Input System Package", setting it to "Both" fixes the issue
- The cursor also does not become invisible in the Build
- The "Cursor.visible = false" function also does not make the mouse invisible if entering the Play Mode while the mouse is not in the Game view
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 1.0.0):
Fixed in 2020.2.0a12