ValveSoftware
FlyDigi Vader 4 Pro SteamInput driver not loading on Linux
The Flydigi Vader 4 Pro isn't being detected in DInput mode on the latest beta when connected over dongle or bluetooth, and doesn't have C/Z mapping on either XInput or DInput modes, nor does it have gyro on the DInput mode. This is consistent with the behavior before the beta.
It seems as though whatever driver was written isn't picking up the device. I wrote the current DInput driver that InputPlumber uses for this controller - working for both dongle and wired. In order to pick up the controller and not the many "fake" devices it creates, I have to specifically pick up: idVendor=04b4, idProduct=2414, bInterfaceNumber=02, subsystem=hidraw
and then specifically block everything else from that vendor and product ID under the input subsystem. I can help if anything else is needed here.
Your system information
- Steam client version (build number or date): 1749507822
- Distribution (e.g. Ubuntu): Arch
- Opted into Steam client beta?: Yes
- Have you checked for system updates?: Yes
- Steam Logs: steam-logs.tar.gz
- GPU: AMD (6750 XT)
Finding the same with a Flydigi Vader 2 Pro - same Steam client and distro. Happy to help with any tests ☺️
On my end, Vader 4 Pro, also on an arch-like distro EndeavourOS, the controller does appear to be detected to an extent. Generally it'll show only the back buttons only in Dinput mode, and in Xinput mode it shows an "extended buttons" toggle that doesn't do anything or even persist after the settings window has been closed.
But with a previous beta, June 16th I believe, it used to be possible to get steam to eventually catch on to the C/Z buttons by switching the controller mode from Dinput -> Xinput -> back to Dinput. As of the June 17th or 18th beta, this is no longer the case, and it only ever sees the back buttons in Dinput again.
Behavior appears to be the same whether it's connected directly with a wire or using the dongle.
Replying to https://github.com/ValveSoftware/steam-for-linux/issues/12103#issuecomment-2988279342
for now you can use InputPlumber (https://github.com/ShadowBlip/InputPlumber) to get full controller functionality in DInput on steam with SteamInput support. it is set up so c and z are mapped to left and right touchpad touch.
For me, on CachyOS (also arch based distro), on Steam Client Version 1750571182, Flydigi Vader 4 Pro, on DInput mode, enabling "Enable Extended Buttons" on the Steam Input settings makes the extra buttons show as configurable, but saving the changes disables the "Enable Extended Buttons" option, and doesn´t save what I binded to the buttons if enable it again.
Vader 4 Pro On Steam Deck in SteamOS beta release:
The Steam doesn't detect additional features when connected in dinput mode via bluetooth, and doesn't have Guide (Home) button assigned.
When connected in dinput mode via USB dongle, it does have additional features, but whenever I open gyro settings for game, the Steam UI crashes.
xinput and switch modes don't expose additional buttons.
Vader 4 Pro On Steam Deck in SteamOS beta release:
The Steam doesn't detect additional features when connected in dinput mode via bluetooth, and doesn't have Guide (Home) button assigned.
When connected in dinput mode via USB dongle, it does have additional features, but whenever I open gyro settings for game, the Steam UI crashes.
xinput and switch modes don't expose additional buttons.
Having the same issue here. Latest Steam Beta
i've experienced a few times with inputplumber running that the steam driver for the flydigi works with all the features, and after it gets picked up and inputplumber stopped, the driver stays loaded and it continues working.
this only happens rarely, and nothing i've tried in any inputplumber config reproduces it. i've also tried this with the driver works and can be loaded, i think it just needs to be mapped to the proper device.
i've tried disabling auto manage, mapping it differently, having it pick up with no device emulated. i've tried various udev rules, including using the format found here: https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules
this is resolved with a udev rule. bluetooth doesn't work, but dongle and wired does.
# Flydigi 2.4 GHz / Wired
KERNEL=="hidraw*", ATTRS{idVendor}=="04b4", MODE="0660", TAG+="uaccess"
i put in a pull request for this and the 8bitdo controllers here: https://github.com/ValveSoftware/steam-devices/pull/66
feel free to close this issue out when udev rules are added.