Arch Linux

kelvie

Member

Registered: 2022-05-08

Posts: 11

Bluetooth gamepad mapping changed recently

Something changed this month and now when I play Diablo 4 (via lutris/proton/GE), my bluetooth gamepad mapping is all wrong.

Using evtest, the "select" and "start" buttons now report BTN_TL and BTL_TR, whereas if I hard-wire it, it returns BTN_SELECT and BTN_START.

This is an 8bitdo controller in xbox mode, and I have two of them that do this, only while hardwired.

Strangely, in firefox and steam, they both work, but evdev reports it wrong, and so does Diablo 4 in Proton.

This used to work. I've tried downgrading bluez to 5.66 and the kernel to 6.3.8, but neither fixed the issue. What else can I check?

kelvie

Member

Registered: 2022-05-08

Posts: 11

Re: Bluetooth gamepad mapping changed recently

https://github.com/atar-axis/xpadneo/issues/291

Interesting, it looks like this old issue is what I'm seeing exactly.

kelvie

Member

Registered: 2022-05-08

Posts: 11

Re: Bluetooth gamepad mapping changed recently

OK, looks like it was a recent SDL upgrade that broke this.

I downgraded SDL and others (I think lutris uses the lib32 one) to

sudo downgrade sdl2 lib32-sdl2 lib32-sdl12-compat sdl12-compat

[2023-07-03T23:54:03-0700] [ALPM] downgraded sdl2 (2.28.1-1 -> 2.26.5-2)
[2023-07-03T23:54:03-0700] [ALPM] downgraded lib32-sdl2 (2.28.1-1 -> 2.26.5-1)
[2023-07-03T23:54:03-0700] [ALPM] downgraded sdl12-compat (1.2.64-1 -> 1.2.60-1)
[2023-07-03T23:54:03-0700] [ALPM] downgraded lib32-sdl12-compat (1.2.64-1 -> 1.2.60-1)

And I can play D4 again with the correct binds over bluetooth.