Search Issue Tracker
Fixed
Fixed in 1.5.1
Votes
3
Found in [Package]
1.5.1
Issue ID
ISXB-986
Regression
No
Cursor is frozen in the Game view when the "Input System Package (New)" input handling is used and "UnityEngine.CursorMode" is set to "ForceSoftware"
Reproduction steps:
1. Open the attached “repro_IN-41170.zip“ project
2. Check that in the “Project Settings” -> “Player” -> “Other Settings” -> “Configuration” -> “Active Input Handling”, the dropdown selection is set to “Input System Package (New)”
3. Enter the Play Mode
4. Attempt to move the cursor
Expected result: The cursor moves freely
Actual result: The cursor is frozen and doesn't correspond
Reproducible with: 1.0.1 (2020.3.48f1), 1.5.1 (2020.3.48f1, 2021.3.26f1, 2022.2.21f1, 2023.1.0b18, 2023.2.0a16)
Couldn't test with: 0.1.2-preview - 1.0.0 (2020.3.48f1) - Errors due to downgrading
Note: Reproducible in builds
Comments (1)
-
pszNicx
Jun 21, 2023 13:04
Confirming this issue is present in 2022.3.2f1.
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 1.5.1):
The issue is now fixed for the Input System package in 6000.1.0a3 and onwards.