Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
1.0.0
Issue ID
1257662
Regression
No
InputSystem.onDeviceChange triggers multiple calls with different InputDeviceChange values when connecting a specific gamepad
How to reproduce:
1. Open the attached project (case-1257662.zip)
2. Enter Play Mode
3. Make sure to disable the 'Collapse' option in the Console window
4. Plug in a gamepad to your computer
Expected result: Console window logs that the gamepad was 'Added'
Actual result: the gamepad was 'Added', 'Removed' and 'Added' again (or 'Reconnected')
Reproducible with: 1.0.0 (2019.3.15f1)
Could not test with: 2018.4.29f1, 2019.4.14f1, 2020.1.11f1, 2020.2.0b10 (don't have the necessary gamepads to test)
Notes:
Reproducible with gamepads: Netway NW1045, KROM NXKROMKEY
Not reproducible with gamepads: Sony CUH-ZCT2E DualShock4, GAME GP300, DragonRise generic USB joystick, Xbox One Controller 4N6-00002, Xbox One Controller WL3-00043
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note:
Postponing until further notice due to higher priority needs. We hope to revisit this at a later time.