Mapping of X and Y buttons is mirrored

[NoXPhasma]

The X and Y buttons are mirrored, X is recognized as Y and vis versa. I guess there is something mixed up in the code :)

[medusalix]

Buttons are mapped according to the Linux docs. So the DPAD is mapped using BTN_NORTH, BTN_EAST, BTN_SOUTH and BTN_WEST. Unfortunately, it looks like BNT_NORTH is equivalent to BTN_X on Linux. I'm not sure which button scheme works best for actual games.

[NoXPhasma]

The X and Y buttons definitely doesn't follow what the XBOX One S controller is mapped with xpad (wired), hid_microsoft (bluetooth) or xpadneo (bluetooth). No matter what game/tool I use, it's wrong in all of them.

[medusalix]

Should we just ignore the docs and map the buttons using BTN_A, BTN_B, BTN_X and BTN_Y?

[NoXPhasma]

I think we should go the same route as xpadneo and xpad go. As this would make sure it's recognized the same way and we don't run into any issues.

I've also just found out that the DPAD won't be recognized in games as well. You've mapped it as buttons 11-14, but apparently with xpad it's mapped as axes 6 and 7.

[NoXPhasma]

Your commit (502abcf) fixed the wrong Y and X mapping. Now only the DPAD is left and the controller works as intended :)

[medusalix]

The latest commit should've now fixed the DPAD.

[NoXPhasma]

It does, the mapping is now as expected.