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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
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