Search Issue Tracker
Won't Fix
Won't Fix in 1.8.X
Votes
0
Found in [Package]
1.8.2
Issue ID
ISXB-903
Regression
No
InputSystem.onEvent is called when changing Cursor.lockState to "CursorLockMode.Locked"
How to reproduce:
1. Open the attached “IN-77283” project
2. Connect a gamepad
3. Open the “SampleScene” and enter Play mode
4. Click anywhere in the Game window
5. Press any button on the gamepad
6. Observe the result in the Console window
Expected result: The last registered event is triggered by the gamepad
Actual result: The last registered event is triggered by the mouse
Reproducible in: 1.7.0 (2021.3.39f1, 2022.3.32f1), 1.8.2 (2021.3.39f1, 2022.3.32f1, 6000.0.5f1)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Also 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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this specific bug. Due to other similar issues existing in our backlog, it's very likely that future plans may solve the problem in a different way.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.8.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this specific bug. Due to other similar issues existing in our backlog, it's very likely that future plans may solve the problem in a different way.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.