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

1.30 - TQS RDR Keybinds not working #8

Closed
rurounijones opened this issue May 2, 2019 · 3 comments
Closed

1.30 - TQS RDR Keybinds not working #8

rurounijones opened this issue May 2, 2019 · 3 comments

Comments

@rurounijones
Copy link

rurounijones commented May 2, 2019

Thank you for releasing 1.30. I would not be playing BMS if not for this tool existing!

I am Attempting to bind the keybinds for TQS RDR CURSOR U/D/L/R is failng for me on the Thrustmaster Warthog throttle.

I am binding these controls to the hat next to the much maligned warthog throttle's "Nipple" (To which I have bound the associated Cursor X/Y axis, the idea being that I can use the hat for fine tuning).

The inputs are registering in The Alternate Launcher in that after setting them they will go to that entry if I activate the button. However in the Alternate launcher there is no associated numeric DX entry in the input column after they are bound (Attached GIF showing this) and the keybinds are not working inside Falcon BMS itself.

falconBMSAltLauncherTQSRDR

@chihirobelmo
Copy link
Owner

This is because of BMS only allows POV switches of a device which there X/Y axis are bound to Roll/Pitch. Currently, alt launcher is hiding those POV switches assignment which will not work in BMS. I think I can add such a description to a later version when you assigned POV switch at KeyMapping page. Anyway, until BMS supports multiple devices POV switches, alt launcher cannot solve this.

@rurounijones
Copy link
Author

rurounijones commented May 2, 2019

What a wierd BMS limitation. So just to confirm, I cannot use this HAT for anything in BMS? Thank you very much for the information and the launcher.

I am not sure if you want this ticket closed now or leave it open until you add a description / message.

@chihirobelmo
Copy link
Owner

As a workaround, you can use TARGET to assign DX or keyboard emulation for throttle POV.
Thank you and I will close this issue.

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

No branches or pull requests

2 participants