You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A wireless Xbox 360 controller configured in the Gamepad module sometimes fails to reconnect on Windows 11. It doesn't always happen and seems to depend on how long the controller was disconnected for. Also the controller will be missing from the dropdown in the Gamepad module until Chataigne is restarted.
The bug is not reproducible in Linux (Debian Trixie/Sid), the same controller always successfully reconnects. I only tested with reasonable amounts of time and most of it accidentally but at least half an hour.
To Reproduce
Steps to reproduce the behavior:
Add the Gamepad module
Select the wireless Xbox 360 controller
Confirm the connection by looking at the live values
Take out the batteries or move far away for longer than a few seconds (maybe a minute?)
Put the batteries back in and power on the controller or move back within range again
Chataigne will now have a chance of being unable to detect the controller at all
Expected behavior
I would expect the controller to reconnect. For short interruptions (like quickly swapping batteries) it usually does reconnect.
Additional context
It seems to me like the handle for the particular controller gets invalidated by Windows 11 and it's necessary to reproble the XInput API for new controllers. I'm not familiar with the API itself and especially not in Windows 11, but that's the impression I'm getting.
I have not tested if the bug occurs with wired controllers as well but I can test that next time I have access to the Windows 11 machine.
The text was updated successfully, but these errors were encountered:
Environment
Describe the bug
A wireless Xbox 360 controller configured in the Gamepad module sometimes fails to reconnect on Windows 11. It doesn't always happen and seems to depend on how long the controller was disconnected for. Also the controller will be missing from the dropdown in the Gamepad module until Chataigne is restarted.
The bug is not reproducible in Linux (Debian Trixie/Sid), the same controller always successfully reconnects. I only tested with reasonable amounts of time and most of it accidentally but at least half an hour.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect the controller to reconnect. For short interruptions (like quickly swapping batteries) it usually does reconnect.
Additional context
It seems to me like the handle for the particular controller gets invalidated by Windows 11 and it's necessary to reproble the XInput API for new controllers. I'm not familiar with the API itself and especially not in Windows 11, but that's the impression I'm getting.
I have not tested if the bug occurs with wired controllers as well but I can test that next time I have access to the Windows 11 machine.
The text was updated successfully, but these errors were encountered: