Closed ecchilds closed 2 years ago
This might have been resolved in c31fffdfc521682e0a31f68cdc28bed929a030e4, not sure though.
Specifically, the issue might be caused because Input.gamepads().get()
was being called instead of Input.gamepads().getByID()
https://github.com/gurkenlabs/litiengine/blob/402bafac346b595c159b6eaf1b4b88fd811219f0/src/de/gurkenlabs/litiengine/input/GamepadEntityController.java#L76-L77
Ah, yeah, that does look like it would fix it. I guess I should update. Thanks for the help!
I don't believe a version that has that commit and is buildable is available yet.
Welp, I ended up fixing it by implementing a near carbon copy of GamepadEntityController with the changes from that commit.
We're planning to release v0.5.2 next week, thanks for standing by and merry Christmas!
Fixed in c31fffdfc521682e0a31f68cdc28bed929a030e4
Describe the bug Index of a newly added gamepad was out of bounds. Was likely due to a failure to add other gamepads, which did not exist, but which were still picked up by the app. Specifically, a Huion Pentablet driver seemed to ping the gamepad manager, likely incrementing the default gamepad index without actually adding to the manager's gamepad array.
Notably, this does not crash the game, but it does make gamepads unusable.
Stack Trace
Probably related error message:
To Reproduce (Probable) steps to reproduce the behavior:
Expected behavior Index of new Gamepad should be within bounds.
Your System:
Additional context Notably, this still occurs even when the pentablet drivers are not running. It is possible the pentablet drivers are not a part of this issue, I am still not sure. I will update this thread if I get further information.