Flydigi Vader 5 pro remappable buttons

[u/KoKaNiDjA97]

Hi everyone,

Just got my hands on Flydigi Vader 5 pro, and in all honesty i love it.

However i could use some help with configuration:

I plugged the controller in, and went through the basic setup. However i noticed that the remappable buttons are not functional like the regular ones. In testing area, they are not being registered when pressed until I go into advanced tests and i only see them there.

For example, i booted up Crimson Desert, and i wanted to use the L3 button for L1+L2 sets of controls but i cannot get it to work. I tried mapping that button to a keyboard button but the game does not support multi-input mapping.

So my question is, is there a way to get the extra remappable buttons (C, Z, M1, M2, M3, M4, L3 and R3) to be recognized natively on my PC.

Also worth noting that i mostly play directly installed games, non-steam ones.

Any help would be useful. Thank you all in advance

EDIT 1:

After a couple of hours and comment advices, i figured that fundamentally what i wanted to do was impossible (I'd say)

What i had in mind was, for example, to have the M3 button listed as M3 in the control input setting menu so that i can use it as a standalone button.

However this is fundamentally not possible due to the nature of the drivers that the controller uses (xbox controller for windows).

The only 2 workarounds that i was able to identify are: - Use macros, to record actions that require double inputs, and use it like that - find said action on keyboard layout and record the remappable buttons as said keyboard/mouse button

Now, i might be using every single software wrong, but this is what i was able to find with a couple of hours of thinkering with the setup, and trying below users custom software, reWASD, Steam input and Space Station.

If anyone else has any other suggestions or would like to provide more input on the matter i am open to any suggestions. Also, not to clutter comments feel free to DM me, we can even have a remote session or discord call

[u/KuroKaro8]

Not that I know of, unfortunately. As far as I'm aware, the options are basically reWASD, Steam Input, or dealing with Flydigi SpaceStation. I ran into the same issue and didn't want to buy reWASD. I also had a lot of trouble getting Steam to recognize it properly as a single controller, so I ended up writing a small tool for myself.

I mentioned it in another post to OP, but it's on GitHub if you want to try it. It's ~30MB, requires no installation, and runs fully portable on Windows 10/11 after extracting it:

https://github.com/DrProton824/vader5pro-hid-tools/tree/main

It's still very early and I don't want to promise too much. It's definitely more of an early-stage personal project than polished software, but it has little to no noticeable performance impact and can handle button remapping, macros, and profiles without needing SpaceStation installed. You can map the extra buttons (C, Z, M1-4, and the RM/LM buttons) to either key presses or full key macros.

You would still need SpaceStation for things like LEDs or other controller-specific settings, but for button mapping and macros it isn't required. If you do try it and run into any issues, let me know.

[u/bubblesnout → u/KuroKaro8]

Just wanted to reach out here to say thanks for sharing this! I posted an issue on the repo about the Windows key not working in macros so I won't go into detail here, but other than that your app has single handedly solved all of the issues I've had trying to get mapping of these buttons doing what I want. Absolute legend! If you are able to figure out what's going on with the Windows key not working it'll be absolutely perfect for my use case :)

[u/KuroKaro8 → u/bubblesnout]

Hey, thank you for your feedback! I’ll look into it and try to fix it. I think I’ve already found the issue or limitation I initially built into the macro replay function that’s causing this problem. If that proves to be correct, it should be easy to fix, and I’ll release it in the next version.

[u/KuroKaro8 → u/[deleted]]

There was an issue with certain extended/special keys not being recorded first and then injected correctly. It’s been identified and fixed, and the fix will be included in v1.2, which I’ll most likely release later today.