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
With SDL_HINT_GAMECONTROLLER_USE_BUTTON_LABELS turned off (set to "0") I expect the button positions to be the same on all devices, based on Xbox controller button naming (eg SDL_GameControllerGetButton(g, SDL_CONTROLLER_BUTTON_Y) gives me whether the North face button is pressed).
However, the Switch Pro Controller layout is wrong (matching labels rather than positions, so X and Y are swapped and A and B are swapped). And with the PowerA controller the East and West buttons are correct, but the North and South buttons are swapped instead.
On 2021-01-04 21:40:07 +0000, Sam Lantinga wrote:
Does it work correctly with the built-in SDL mappings, if you don't use gamecontrollerdb.txt? That mapping file doesn't support the hint.
On 2021-01-05 01:12:47 +0000, wrote:
(In reply to Sam Lantinga from comment # 1)
Does it work correctly with the built-in SDL mappings, if you don't use
gamecontrollerdb.txt? That mapping file doesn't support the hint.
I've just tested it out without loading gamecontrollerdb.txt, and it still behaves incorrectly as described.
On 2021-01-12 17:31:19 +0000, Mathias Kaerlev wrote:
Also seeing this on 2.0.14. This is most likely a regression, since we weren't seeing this on an earlier SDL version.
It seems like both the HIDAPI driver and SDL_gamecontroller.c will try to swap the buttons if the hint is set to 0, causing the button remap to cancel out.
This bug report was migrated from our old Bugzilla tracker.
Reported in version: 2.0.14
Reported for operating system, platform: Windows 10, x86_64
Comments on the original bug report:
On 2021-01-04 13:37:55 +0000, wrote:
On 2021-01-04 21:40:07 +0000, Sam Lantinga wrote:
On 2021-01-05 01:12:47 +0000, wrote:
On 2021-01-12 17:31:19 +0000, Mathias Kaerlev wrote:
On 2021-01-14 23:16:45 +0000, Sam Lantinga wrote:
The text was updated successfully, but these errors were encountered: