-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flydigi Apex 4 support #208
Comments
@zany130 I don't know if this helps you but I've managed to make the back buttons of the flydigi work with a set of patches:
|
Oh, interesting! I'll try this out! So, basically, this is patching xpad to support the back buttons of the Apex 4 when in x-input mode and then using input plumber to emulate an elite controller so it shows in Steam? The only thing missing with this would be gyro and the extra "circle button" (button next to home) D-input is still probably the better mode to use on Linux. Everything except rumble is already exposed. So I guess the only thing that needs to be done is get input plumber to map everything to a dual sense edge or something Though rumble would not work |
What does the home button map to? |
No the circle button doesn't send anything in x-input mode The home button maps to the xbox guide button on x-input mode. on d-input I think it's The rest is all d-input mode In d-input the circle button sends the right trigger so it might not be possible to map it separately from the the right trigger thinking back on it The only mode the circle button is sent as its own button is in dual sense mode (windows software only) and switch mode in bothe cases it's mapped to the share/capture button Gyro is sent in two hidraws. The flydigi fly mouse (gyro mouse actived by the circle button (in d-input it sends both the right trigger to the OS and internally it also activates the fly mouse) it sent in a separate hidraw from everything else . There are also mouse buttons on this hidraw mapped to two of the back buttons (I think it was the inner two) There is also what seems to be raw gyro data on the main hidraw were all the other buttons and sticks are , but a gyro mapping (button combo to enable gyro aim in the windows software) has to be set in the software for it to show up. What buttons are mapped do not matter all that matters is that some type of mapping is set. This should all be documented in handheld dameon doc fork I mentioned in the op |
If it helps, this is how the Apex 4 is mapped in d-input (note that it identifies as a Vader 3, probably because they use the same firmware or something.)
|
Hi @Fabianoshz. I'm new to using InputPlumber, so I need some help. Where I need place config and how apply it? Sorry for the stupid question. Also about apply patches for xpad. That PR is updated many times. Latest commit is 6b93b7e6b4473aadab0de870bdec91e8ee74de81 Your patch is actual? |
About inputplumber things have changed since I've added my comment, you no longer need to add any patches to inputplumber, but your capability map should look like this:
Which I believe you should add to: Nothing should change for the
Which I believe you should add to: I'm using an old version of xpad, but I would expect the latest patch should work just fine, which distro are you using? Instructions might differ based on what system you're using. |
@Fabianoshz thanks. I managed to introduce myself to the Xbox Elite controller on Steam. However, Steam hasn't yet been able to fix the paddle buttons, and the remapping might not have been finished somewhere. But that's a different problem (will check xpad). The most important thing is that I was able to introduce myself as a new controller. That was cool. |
These are great. Please PR to add them, then we can close this issue and this controller will work OOTB. We will want to make this one a 59- config, and include the device name in the config, so that generic xbox controllers aren't captured. |
As previously discussed on discord, this is to track adding support to the Flydigi Apex 4 controller
Relevant discussions and dumps can be found here:
hhd-dev/hhd#73
libsdl-org/SDL#10161
https://github.com/zany130/hwinfo/tree/master/devices/Apex4
The text was updated successfully, but these errors were encountered: