protonscr

No rumble and settings not saved on Flydigi Vader 5 Pro

steamopen Steam clientDistro Family: FedoraGeneral controller / Steam Input
ValveSoftware/steam-for-linux#13234 · opened 2026-05-20 by LeoSebal · updated 2026-07-02 · 4 comments · github
LLeoSebal 2026-05-20 github

Your system information

  • Steam client version (build number or date): Steam Beta Update 1779155395
  • Distribution (e.g. Ubuntu): Nobara 43
  • Opted into Steam client beta?: [Yes/No] Yes
  • Have you checked for system updates?: [Yes/No] Yes
  • Steam Logs: steam-logs.tar.gz
  • GPU: Nvidia RTX 4070

Description:

  • While only the Flydigi Vader 5 Pro is (physically) connected, the Vader appears in the list of controllers in Steam, but a Generic X-Box pad is also there
  • Pinging the Vader doesn't do anything. Pinging the Generic X-Box pad makes the controller rumble.
  • In the Calibration & Advanced Settings window, controls work on the Vader; they do not on the Generic X-Box pad (this is expected, just some more complementary info about the bug)
  • When trying to set up a game controller layout for the Vader, many of the settings will not stick: impossible to assign another controller key to the back paddles, to set up a modifier key for the gyro, to remove M4 as A and M3 as X assignment...

Steps for reproducing this issue:

  1. Uninstall all other drivers (flydigi-vader5-linux, padctl or vader5-pro-linux-fix). Reload daemons if necessary.
  2. Install beta v1779155395
  3. Going into Steam settings / Controllers, you will see 2 controllers: Flydigi Vader 5 Pro and Generic X-Box pad. One will have working inputs (for the most part), but no working rumble; the other one, the opposite.
  4. Go in Games > Settings > Controller layout, and try to modify the profile.
Kkisak-valve maintainer 2026-05-20 github

Possible duplicate of #12680.

Xxl666 2026-05-22 github

Same exact issue here in Bazzite and SteamOS

Xxsxavier 2026-06-30 github

Possible duplicate of [#12680](https://github.com/ValveSoftware/steam-for-linux/issues/12680).

Partly, it's two separate (or related) issues. The steam input settings part, seems to be 'mostly' fixed. The issue not described in #12680 is the 2 controller part and rumble not functioning. Vader 5 pro is still being recognized as 2 controllers. Where one is showing up as usb.

Image
Aaerialhedgehog 2026-07-02 github

I recently updated on stable and started noticing this issue as well.
Steam OS: v3.8.13, build 20260701.1
Steam Client: Stable 1782861641
Hardware: Legion Go S

I'm currently blocking the Generic X-box Pad with this udev rule:

# Block binding Flydigi Vader 5 Generic Xbox
ACTION=="bind", SUBSYSTEM=="usb", DRIVER=="xpad", ATTRS{idVendor}=="37d7", ATTRS{idProduct}=="2401", RUN+="/bin/sh -c 'echo %k > /sys/bus/usb/drivers/xpad/unbind'"

I'm also noticing that on my SteamOS, that the steam-input-rules (/usr/lib/udev/rules.d/60-steam-input.rules) are not up to date with the rules here: https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules , which include some uaccess permissions for FlyDigi devices. I've copied these along side the above rule.

# Flydigi 2.4 GHz / Wired
KERNEL=="hidraw*", ATTRS{idVendor}=="04b4", MODE="0660", TAG+="uaccess"

# Flydigi HIDAPI Enhanced Mode
KERNEL=="hidraw*", ATTRS{idVendor}=="37d7", MODE="0660", TAG+="uaccess"

Here's what is and is not working for me:

  • Yes Working: All buttons
  • Yes Working: Gyro, including auto gyro calibration
  • Not Working: Rumble to the Vader 5 device (was working to the Generic Xbox Device)
  • Yes Working: Steam input configuration

I noticed this issue while opening the steam big picture menu while in game, it appeared there was a joystick input being registered on the steam menu for about a second. Some combination of the above udev rules stopped that for me.

I consider the udev rules a hack and hope that a future update removes the need for them!

Upstream links