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
Hello, I'm not sure where to report issues for xpad, so I'm trying my luck here.
I have a controller from PDP, that identifies itself as a "PDP Controller for Xbox One".
However, the description I see in most places on my machine instead identifies it as an "PDP Xbox One Arcade Stick".
That is fine, except for the fact that this applies a MAP_TRIGGERS_TO_BUTTONS quirk which turns the triggers into a binary on/off switch, and messes up the bindings with anything that expects a standard xbox layout (e.g steam, anything SDL2, etc.).
The controller identifies itself with vendor 036f and device 015c.
I've included a patch to adjust the lookup table, which I've used for some time in custom kernel builds. pdp-controller.patch.txt
The text was updated successfully, but these errors were encountered:
Hello, I'm not sure where to report issues for xpad, so I'm trying my luck here.
I have a controller from PDP, that identifies itself as a "PDP Controller for Xbox One".
However, the description I see in most places on my machine instead identifies it as an "PDP Xbox One Arcade Stick".
That is fine, except for the fact that this applies a
MAP_TRIGGERS_TO_BUTTONS
quirk which turns the triggers into a binary on/off switch, and messes up the bindings with anything that expects a standard xbox layout (e.g steam, anything SDL2, etc.).The controller identifies itself with vendor
036f
and device015c
.I've included a patch to adjust the lookup table, which I've used for some time in custom kernel builds.
pdp-controller.patch.txt
The text was updated successfully, but these errors were encountered: