Skip to content
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

add more flydigi compatibility #51

Open
wants to merge 2 commits into
base: stable
Choose a base branch
from

Conversation

zeddidragon
Copy link
Contributor

This is more hacks for my dumb controller. There's two extra remapping TOMLs for the same controller, but while the first one was for the wired mode, these two are for the controller connected via the wireless dongle and via bluetooth. The assigned buttons as well as which buttons are available changes a lot in these modes, much to my chagrin.

In wireless mode, you lose access to ActionL and ActionR. The various extra buttons also ended up with different assignment which I've remapped to same as before.

In bluetooth mode, button assignment is seemingly random. I ended up assigning to some previous unused flight stick buttons as well as assigning some completely new ones when appropriate. The Z button (ActionD) showed up as 0x01C and, when pressed, would emit an Enter event on my computer. This prompted me to check https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/keyCode for inspirations to other keycodes of low values and I added KEY_SLEEP and KEY_ENTER when appropriate. The buttons werre just going to be remapped anyway, but they needed an intermediary to work.

In the existing scheme, the Exit and MenuL button assumed there wouldn't exist a separate back button. In bluetooh mode, Flydigi gives access to its three meta buttons, labeled ))), ⌂, and ↰ , exist along a pair of Select and Start buttons. I dubbed the ))) button Pair, as it's used for pairing and switching modes, and added Home for the ⌂, leaving ↰ as Exit. I probably won't use this configuration much myself, but some owners may not care for the gyro capabilities of the controller which this mode lacks and would thus prefer having access to all buttons instead.

In the original remapping, I assigned Pov to just Up/Down/Left/Right as those seemed the appropriate buttons for controller dpads.

@AldaronLau
Copy link
Member

@zeddidragon Thank you for the PR! Quick glance, but this mostly looks good. I think I would rename Pair to Mode because if you're using it you're probably already paired, so that meaning doesn't make as much sense. Pretty weird about the bluetooth mappings.

@zeddidragon
Copy link
Contributor Author

I would rename Pair to Mode

Sure, no problem. Appended this change to the pull request.

Pretty weird about the bluetooth mappings.

Flydigi Apex 2: Can't live with it, can't live without it. If I could find another controller that had all of these buttons + gyro aim I would've switched already. Even when switching to the modes that lack features, it still has more features than most controllers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants