Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.6.3
Issue ID
ISXB-617
Regression
No
New Input System does not always detect when the controller is disconnected
Reproduction steps:
1. Open the attached “ControllerBug.zip“ project
2. Connect and disconnect the Xbox controller 3-4 times
3. Observe the Logged events in the Console
Expected result: The amount of “XInputControllerWindows:/XInputControllerWindows Added” and “XInputControllerWindows:/XInputControllerWindows Removed” events is the same
Actual result: The amount of “XInputControllerWindows:/XInputControllerWindows Added” and “XInputControllerWindows:/XInputControllerWindows Removed” events is not the same
Reproducible with: 1.6.3 (2022.3.6f1)
Reproduced on: Windows 10 (by the reporter)
Notes:
- Not reproduced by CQA
- If the issue is not reproducible, repeat the 2nd step in Play mode
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
- "Initialization Mode" and "Update Mode" drop-downs are not localized in the Custom Render Texture asset
- Switching Graphics Default or DevLook Profile to “NightSkyRenderingSettings Profile” throws “KeyNotFoundException” error in the Console window
- Section separator renders in the wrong place in Search Journaling and Archetypes windows
- [D3D12][UWP] Additional persistent shadows are drawn in UWP builds when using D3D12
- Search Journaling window link to Journal Manager documentation isn’t working
Resolution Note:
Unfortunately, we weren't able to reproduce the bug with multiple, different controllers on Input System 1.7.0. As this is an unreproducible and niche issue we will have to close the ticket. Please reopen the ticket if this still reproduces for you on Input System 1.7.0 with a standard controller and you have new information that could help us reproduce it locally