[Bug] [Regression] SDL3 Motion doesn't work on linux

[PiplupHelper]

Prerequisites

• I am confident that my issue has not been reported already in open OR closed issues.
• I am able to reliably reproduce the issue on the latest stable or canary version.
• I am not using an unofficial build (Flatpak, Emudeck, etc.).
• I am a silly goose and didn't read these boxes.
• I am a silly goose and DID read these boxes.

Description of the issue

SDL motion doesn't work on linux, after version 1.3.272

Reproduction steps

1. open a game like super mario odyssey
2. try a motion action

Log file

Ryujinx_Canary_1.3.271_2026-04-30_05-10-35.log
Ryujinx_Canary_1.3.272_2026-04-30_05-12-08.log

OS

CachyOS

Ryujinx version

1.3.272+

Game version

1.0.0

CPU

AMD Ryzen 9 7900X3D

GPU

AMD Radeon RX 6600 XT / NVIDIA GeForce RTX 3060

RAM

64GB

List of applied mods

Piplup Dyssey [R]
Piplup Darker Gloves [R]
Piplup Globe' [R]
Piplup Builder Outfit [R]
Piplup Checkpoint [R]

Additional context?

steam was open but steam input is disabled

[sh0inx]

can confirm the same here, ill raise it with @schuay

Game: Super Mario Odyssey
Version: 1.0.0
OS: Arch Linux 7.0.2-arch1-1
CPU : AMD Ryzen 7 6800HS
GPU: NVIDIA RTX 3050TI
RAM: 32GB
List of applied mods: SMOO
Additional Context: https://git.ryujinx.app/projects/Ryubing/pulls/19

[schuay]

• Which controller?
• Have you tried running standalone (no steam open), does it work then?
• All looking good in controller settings, nothing to reconfigure?
• Finally, try setting export SDL_JOYSTICK_HIDAPI_SWITCH=1; ryujinx.

I suspect it's SDL_JOYSTICK_HIDAPI_SWITCH; switching that off fixed my motion issues. But I run standalone, and likely have a different controller than you.

Please also add the output of ls /dev/input/by-id/; lsmod | grep hid_nintendo

[schuay]

@sh0inx I suspect whichever value of SDL_JOYSTICK_HIDAPI_SWITCH we pick will break some controllers. Looks like dolphin-emu solves this by having both an evdev and SDL input backends (along with many others). Perhaps the most pragmatic option would be to revert b7f42de5a6 and instead expose SDL_HINT_JOYSTICK_HIDAPI_SWITCH as a UI option so users can fix their controller without having to discover and set the correct env var.

[sh0inx]

• Which controller?

  • Have you tried running standalone (no steam open), does it work then?

  • All looking good in controller settings, nothing to reconfigure?

  • Finally, try setting export SDL_JOYSTICK_HIDAPI_SWITCH=1; ryujinx.

I suspect it's SDL_JOYSTICK_HIDAPI_SWITCH; switching that off fixed my motion issues. But I run standalone, and likely have a different controller than you.

Please also add the output of ls /dev/input/by-id/; lsmod | grep hid_nintendo

• Nintendo Switch Pro Controller
• Yep, I flat-out turned Steam off and reconnected my controller to ensure there was no interference even. Steam being open completely refused to connect the controller, but having it off did not fix the motion issue.
• SDL_JOYSTICK_HIDAPI_SWITCH=1 ./Space/Programs/Emulators/Ryujinx/canary/Ryujinx.sh --core-dumps was what I ended up using, and this did enable motion per my testing.

Output of ls /dev/input/by-id/; lsmod | grep hid_nintendo:

[11:50 PM] sh0inx@briana $ ~ > ls /dev/input/by-id/; lsmod | grep hid_nintendo
usb-ASUSTek_Computer_Inc._N-KEY_Device-event-mouse
usb-ASUSTek_Computer_Inc._N-KEY_Device-hidraw
usb-ASUSTek_Computer_Inc._N-KEY_Device-mouse
hid_nintendo           53248  0
ff_memless             24576  1 hid_nintendo

---

@sh0inx I suspect whichever value of SDL_JOYSTICK_HIDAPI_SWITCH we pick will break some controllers. Looks like dolphin-emu solves this by having both an evdev and SDL input backends (along with many others). Perhaps the most pragmatic option would be to revert b7f42de5a6 and instead expose SDL_HINT_JOYSTICK_HIDAPI_SWITCH as a UI option so users can fix their controller without having to discover and set the correct env var.

Since we can detect whether its an official Nintendo controller anyway, it might be better to swap flags on or off automatically, or this can be something that gets added as an advanced input option. Since @babib3l3l is working on input stuff, I'd like to hear from them on what the right play here would be.

[schuay]

Edit: removed a suggestion wrt hid_nintendo/refcnt that turned out to be wrong.

I'll defer to someone who actually knows more about input handling though. My vote is for autodetection + exposed SDL_HINT_JOYSTICK_HIDAPI_SWITCH option.

[babib3l3l]

I do agree with what sh0inx said, given we don’t really have an "advanced input settings" menu or something alike, I think it would be best to have it swap flags automatically.

[schuay]

After another look:

• SDL3 fixed the underlying issue upstream at Switch Pro controllers via hid_nintendo and gyroscope (IMU) data libsdl-org/SDL#6478 (libsdl-org/SDL@6432f45)
• What actually fixed motion in ryujinx (according to a bisect today) was a8ace3d23 "chore: SDL3 (ryubing/ryujinx!207)".

.. at least that's what I can conclude from my investigation today. I can't reconstruct how I ended up at the SDL_JOYSTICK_HIDAPI_SWITCH theory. Maybe something else changed on my system in the meantime, impossible to know.

@sh0inx sorry for the churn, please revert b7f42de5a. (Note the companion commit b7f42de5a6 is still valid though.)

[sh0inx]

god fucking damn it i just came over here to tell you i did it and i think i grabbed the wrong commit

[sh0inx]

wait maybe not
https://git.ryujinx.app/projects/Ryubing/pulls/46