https://bugs.winehq.org/show_bug.cgi?id=53028
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com
--- Comment #3 from Rémi Bernon rbernon@codeweavers.com --- Having 10 buttons and 5 axes is expected for any gamepad, as we now expose them as XInput-compatible devices.
XInput-compatible devices are now exposed exactly as they do on Windows, to the DInput API through this compatibility, and limited, interface. Through this interface for instance, trigger axes are combined together, and some games expect this to be the case (Jade Empire for instance).
These devices are also now correctly exposed to the XInput API too, and should be more fully featured in that case when it is used by any game.
It is possible to revert that behavior and override the device so that it is exposed fully, but only, through the DInput API. To do that, open the joystick control panel (which can also be used to validate how both APIs are seeing the devices), with `wine control joy.cpl`, then use the "Override" button to override the device for DInput API only.
The "Reset" button can be used to revert that change. Note that it might then be necessary to restart the application for the changes to fully take effect.
If this isn't solving your problem, it would be nice if you could attach a log file when starting some Wine application, with the WINEDEBUG=+hid,+dinput,+xinput,+input,+rawinput environment variable set.