Coolie switch
-
Yeah but it you’d have to pitch and bank with it. POV on the primary controller only. Primary controller is the pitch and bank one. Them’s the rules.
-
sorry but I don’t really understand.
I’m using BMS Key File Editor for my warthog, is there a way with this file ?
Thanks !
-
Of course it can be used, if it is an axis it can be addressed for something useful, if it’s considered a 4/8 way HAT, you can use DX assignments. Just experiment, find it’s button number with the DX keyfile instructions and give it the key for something like lights in it’s various directions. FTR, the [BMS Alternative Launcher](https://www.benchmarksims.org/forum/showthread.php?31774-Falcon-BMS-Alternative-Launcher-(Easy-Setup-Keep-Joystick-Assignments) has an included Key Mapping GUI that makes manual DX keyfile building into an “option” instead of “the only way”. May be easier for fast testing of such things…
-
No. I give you a hint.
| Device | Button | BMS Input |
| Device 1 | POV Up | POV Up |
| Device 1 | POV Right | POV Right |
| Device 1 | POV Down | POV Down |
| Device 1 | POV Left | POV Left |
| Device 1 | Button 1 | Button 0 |
| Device 1 | Button 2 | Button 1 |
| Device 1 | Button 3 | Button 2 |
| Device 1 | Button 4 | Button 3 |
| Device 1 | Button 5 | Button 4 |
| Device 1 | Button 6 | Button 5 |
| Device 1 | Button 7 | Button 6 |
| Device 1 | Button 9 | Button 8 |
| Device 1 | Button 10 | Button 9 |
| Device 1 | Button 11 | Button 10 |
| Device 1 | Button 12 | Button 11 |
| Device 1 | Button 13 | Button 12 |
| Device 1 | Button 14 | Button 13 |
| Device 1 | Button 15 | Button 14 |
| … | … | … |
| Device 1 | Button 30 | Button 29 |
| Device 1 | Button 31 | Button 30 |
| Device 1 | Button 32 | Button 31 |
| Device 2 | POV Up | –- |
| Device 2 | POV Right | –- |
| Device 2 | POV Down | –- |
| Device 2 | POV Left | –- |
| Device 2 | Button 1 | Button 32 |
| Device 2 | Button 2 | Button 33 |
| Device 2 | Button 3 | Button 34 |
| Device 2 | Button 4 | Button 35 |
| Device 2 | Button 5 | Button 36 |
| Device 2 | Button 6 | Button 37 |
| Device 2 | Button 7 | Button 38 |
| Device 2 | Button 9 | Button 39 |
| Device 2 | Button 10 | Button 40 |
| Device 2 | Button 11 | Button 41 |
| Device 2 | Button 12 | Button 42 |
| Device 2 | Button 13 | Button 43 |
| Device 2 | Button 14 | Button 44 |
| Device 2 | Button 15 | Button 45 |
| … | … | … |
| Device 2 | Button 30 | Button 61 |
| Device 2 | Button 31 | Button 62 |
| Device 2 | Button 32 | Button 63 |
| Device 3 | POV Up | –- |
| Device 3 | POV Right | –- |
| Device 3 | POV Down | –- |
| Device 3 | POV Left | –- |
| Device 3 | Button 1 | Button 64 |
| Device 3 | Button 2 | Button 65 |
| Device 3 | Button 3 | Button 66 |
| … | … | … |Device 2 POV, Device 3 POV, Device 4 POV, doesn’t map to anything for BMS input. Warthog throttle coolie switch is POV and it cannot practically be Device 1. The conclusion is that as it is the coolie hat cannot be used in BMS. If you want to use coolie hat as input you either must set it as primary controller or use some programming script so output from pressing this switch is not POV.
-
Hi
is there a way yo use coolie switch with DX method ?
Thanks
What are you hoping to control with the coolie switch?
-
…If you want to use coolie hat as input you either must set it as primary controller or use some programming script so output from pressing this switch is not POV.
So, vJoy and UJR turns that “No” into a “Yes” with a “but” requiring a little technical work? I mean no offense and I totally respect your experience, bro - I’ve been wrong before and it won’t be the last time - I just see possibilities that eliminate a flat “no” as the answer to this being a possibility.
-
Absolutely. If you can make that switch produce any DirectInput signal other than the POV type you can use it. This just requires some kind of programming effort since raw support as a traditional joystick device makes that switch produce POV output.
For example my TMWH Throttle with TARGET script applied makes that switch produce buttons 11-14 so BMS can use it.
MapKey(&Throttle, CSU, DX11); //COMM-IFF UHF SimTransmitCom1
MapKey(&Throttle, CSR, DX12); //COMM-IFF IN SimCommsSwitchRight
MapKey(&Throttle, CSD, DX13); //COMM-IFF VHF SimTransmitCom2
MapKey(&Throttle, CSL, DX14); //COMM-IFF OUT SimCommsSwitchLeft -
Sorry but I don’t have the skill to understand, is there a simple way to use this switch with the key file editor ? do I have to change the output manually after ?
and another question : can I just assign in key file editor the “F12” key to a button ?
THanks for your help
-
Key file alone cannot utilize this switch without modifying its behavior. It doesn’t matter what editor is used to write the key file.
I don’t know the key file editor but there should be no reason why F12 can’t be used for a command. The key file itself can accept this input so any problem would be a limitation of the editor.
-
Key file alone cannot utilize this switch without modifying its behavior. It doesn’t matter what editor is used to write the key file.
I don’t know the key file editor but there should be no reason why F12 can’t be used for a command. The key file itself can accept this input so any problem would be a limitation of the editor.
do you know how to input F12 to a sitck button ?
thanks
-
Just do what Frederf did - use Target software and scripts to accomplish what you want with the Coolie
Absolutely. If you can make that switch produce any DirectInput signal other than the POV type you can use it. This just requires some kind of programming effort since raw support as a traditional joystick device makes that switch produce POV output.
For example my TMWH Throttle with TARGET script applied makes that switch produce buttons 11-14 so BMS can use it.
MapKey(&Throttle, CSU, DX11); //COMM-IFF UHF SimTransmitCom1
MapKey(&Throttle, CSR, DX12); //COMM-IFF IN SimCommsSwitchRight
MapKey(&Throttle, CSD, DX13); //COMM-IFF VHF SimTransmitCom2
MapKey(&Throttle, CSL, DX14); //COMM-IFF OUT SimCommsSwitchLeft -
MapKey(&Throttle, CSU, DX11); //Button 11
MapKey(&Throttle, CSU, F12); //F12 key -
MapKey(&Throttle, CSU, DX11); //Button 11
MapKey(&Throttle, CSU, F12); //F12 keyThis if for .key file or target ?
THanks a lot
-
TARGET, use only one line at a time of course.
-
TARGET, use only one line at a time of course.
Thanks but my post was to do it without target
-
Then you can’t. Without TARGET then coolie switch is POV and POV will only be recognized from #1 device in BMS.
-
ok thanks