Mapping the Warthog flaps switch to MASTER ARM?
-
I’m trying to map several of the Warthog switches/toggles, using the example of the Flaps switch on the left of the throttle.
Here, the forward position labeled UP triggers a button press (DX22, I think), and the aft position labeled DN triggers a button press (DX23). The middle position labeled MvR apparently isn’t triggering any button. The result is that, thus far, I haven’t been able to map the MASTER ARM on/off/sim switch in BMS to the Flap switch, because the middle position isn’t triggering anything.
My question: How can I map the MASTER ARM on/off/sim switch in BMS to the Flaps switch on the Warthog? Do I have to use 3rd party tools like JoystickGremlin/VJoy?
(It works in DCS, because DCS has toggle mappings available for you to use in this situation.)
-
@Elegantly It can be done by manually editing the keyfile you are using, below is an example using the AP switch.
So switch up triggers SimLeftAPUp
When it’s returned to center it triggers the SimLeftAPMid action, the key to that line is the 0x42 that tells BMS to take action when 53 is released.
Same thing applies for 54 on and off, hence the need for 4 lines.SimLeftAPUp 53 -2 -2 0 0x0 115
SimLeftAPMid 53 -2 -2 0x42 0x0 115
SimLeftAPDown 54 -2 -2 0 0x0 115
SimLeftAPMid 54 -2 -2 0x42 0x0 115 -
@TxMtb Thanks, I’ll give this a try!
Quick follow-up question: How do I know which button/switch/toggle on the Warthog maps to the key codes you mentioned, like
0x42
as well as53
/54
? Is there a utility that I can run that translates throttle actions to key codes? And/or is there a section in the manual that documents what you mentioned so I can RFTM? -
@Elegantly Check out this guide on Keyfile editing - describes these numbers, etc.
https://www.blu3wolf.com/falconbms/Kolbe/Falcon BMS Keyfile Manual.pdfFrom the Setup > Controllers screen, if you push any button, you’ll see it appear in green below the callbacks/bindings list on the right. This value will by off by 1 (zero based vs. one based) - again, see the guide link.
-
@Elegantly Specifically, 10.7.1 on the Technical Manual to find which button is which for BMS and 10.8.2 on the Technical Manual for the functions @TxMtb was demonstrating.
Any more issues, by all means ask!
-
Thanks everyone, that’s exactly the pointers that helped me!
-
Hi Elegantly
You should really do you self a big favor and use the alternative launcher for BMS.
This makes it really easy to assign you controls, and it makes it easy to do actions on button release.
-
@Thbrix said in Mapping the Warthog flaps switch to MASTER ARM?:
Hi Elegantly
You should really do you self a big favor and use the alternative launcher for BMS.
This makes it really easy to assign you controls, and it makes it easy to do actions on button release.
Elegantly, I would second THbrix in this. With AL that release function is a very easy solution to setting up a 3 way switch. For example, if you want to match the in’pit switch, map Sim to DN,Armed to Up, and set Safe as a release for both. That way it works in either direction
-
@Thbrix and @drtbkj : Thanks, I have been using Alternative Launcher already for all other keybind settings. But I wasn’t aware initially that I could use it for this scenario of “do XYZ on button release”.
While I was researching on how to prevent AL to overwrite any custom key file changes of mine (as per the other comments above) when it generates its “BMS AUTO” keyfile, I realized that there actually is an easy way to configure my keybinds directly with AL. I simply never spotted it even though it was staring me right in the face.
Here’s the relevant setting in a screenshot in case other users are looking for the same solution. You need to click on the highlighted button to change it from its default “PRESS” option to the “RELEASE” option.
The only remaining caveat is to get the desired key registered when this window is open. What worked (almost) consistently for me was to set a switch to its OFF position (e.g., the EAC ARM/OFF switch on the Warthog), then open this window to assign the binding, change it to “RELEASE”, and then move the switch from OFF to ARM. The opposite, more intuitive approach to move the switch ARM to OFF would not register the keybind in AL, even when toggling several times between ARM and OFF. In other words, the switch must be OFF before opening the window, and then moved to its non-OFF position. I hope this summary makes sense.
Lastly, I made sure to always set “on release” binds for all possible switch positions. For example, in the screenshot above you can see my binds for the MASTER ARM switch, which is the physical FLAPS 3-way switch on my Warthog. I configured AL to:
- Set MASTER ARM to ON when the FLAPS switch is moved to UP.
- Set MASTER ARM to SIM when the FLAPS switch is moved to DN.
- Now the important bit: Set MASTER ARM to OFF when either UP or DN are released for the FLAPS SWITCH, thus moving it from either UP or DN to the center MVR position. That’s why there are two keybinds for “on release”.
-
@Elegantly Exactly right. Another cool function is that it makes the "Dx Shift much more useable, IMHO. For example, you could do the flaps “under” your Master Arm.
An interesting thing about setting up a HOTAS is that there are so many ways to do it -
Hi everybody!!
Since I started Falcon BMS I always used the Morphine Profile but it seems that nobody will continue to improve and support it.
The other day I run Alternative Laucher for the first time to change scenario and 80% of the key mapping I have with morphine disappeared and there has been no way to restore it
That added to what I mentioned before, nobody supports Morphine, I think I’m going to try to do the Key mapping with the Alternative Launcher trying to replicate what I had with Morphine
Does anyone know if there is a manual or video where it is explained how it is done?