24-10-2026, 09:44 PM
SuperTuxKart relies on SDL2 for gamepad support, which usually makes it compatible with a lot of devices.
We are not aware of specific issues with Windows 11 compared to older Windows versions, but these things are not always predictable...
The fact that the same gamepad worked fine with Windows 10 hints at a change in how the system handles the gamepad rather than the game having a problem with that specific make.
What you could try:
- Test some other games. If different games suffer from issues too, it may be something that's not specific to SuperTuxKart
- Tell us the gamepad model so we could check for potential known issues with SDL2 games.
- Start SuperTuxKart with the command line parameter "--gamepad-debug". Look up with a search how to start a Windows program with command line parameters, it's a bit more complicated than on Linux but still manageable. Then, test your different inputs. In gamepad debug mode, the game will output data in the log each time any gamepad input is activated. Comparing what shows up in the log with your inputs could potentially help find the source of the problem.
We can't guarantee a fix though.
We are not aware of specific issues with Windows 11 compared to older Windows versions, but these things are not always predictable...
The fact that the same gamepad worked fine with Windows 10 hints at a change in how the system handles the gamepad rather than the game having a problem with that specific make.
What you could try:
- Test some other games. If different games suffer from issues too, it may be something that's not specific to SuperTuxKart
- Tell us the gamepad model so we could check for potential known issues with SDL2 games.
- Start SuperTuxKart with the command line parameter "--gamepad-debug". Look up with a search how to start a Windows program with command line parameters, it's a bit more complicated than on Linux but still manageable. Then, test your different inputs. In gamepad debug mode, the game will output data in the log each time any gamepad input is activated. Comparing what shows up in the log with your inputs could potentially help find the source of the problem.
We can't guarantee a fix though.