Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.8.2
1.9.0
1.10.0
Issue ID
ISXB-995
Regression
No
Cursor does not move when using CursorMode.ForceSoftware in New Input System
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Move the cursor
Expected result: The cursor is moving
Actual result: The cursor is frozen and does not move
Reproducible with: 1.8.2 (2021.3.40f1, 2022.3.40f1, 6000.0.13f1), 1.9.0 (2021.3.40f1, 2022.3.40f1, 6000.0.13f1), 1.10.0 (2021.3.40f1, 2022.3.40f1, 6000.0.13f1)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: Reproducible in Player
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
CursorMode.ForceSoftware is Input Manager API and requires the backend to be set to Both or Input Manager in order to use it. You can change the backend in the Project Settings -> Player -> Active Input Handling field