Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.4.4
1.5.0
Issue ID
ISXB-435
Regression
No
mouseDelta returns a large value when Cursor.lockState = CursorLockMode.Locked is activated
Reproduction steps:
1. Open the attached “Cursor Lock Delta Bug Repro.zip“ project
2. Open “SampleScene” scene
3. Enter Play mode and click anywhere in Game window
4. Move mouse cursor around and press “space bar” key to pause Camera movement
5. Move mouse cursor to another location of Game window
6. Press “space bar” key to unpause and move mouse cursor to another location of Game window
7. Press “space bar” key again, exit Play mode, and observe the mouse delta value in the Console
Expected result: mouseDelta returns a low value (i.e. (0.25, 0.25, 0.00))
Actual result: mouseDelta returns a large value (i.e. (-58.00, -8.25, 0.00))
Reproducible with: 1.4.4 (2020.3.46f1), 1.5.0 (2020.3.46f1, 2021.3.21f1, 2022.2.12f1, 2023.1.0b9, 2023.2.0a7)
Reproduced on: macOS Monterey 12.6 (Intel)
-
saskenergy
Jul 12, 2023 03:09
I actually reported this issue back in March and it seems like this is still not fixed.
This issue is still present on version 1.6.1 of the Input System. Currently on 2022.3.4f1 LTS for Linux (Ubuntu 22.04).
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.