Warthog programming (TARGET) - Problem with long / short press
-
You should not program TMS in Target. Use the controller page in Falcon instead. Just select the TMS (left, right, fwd, aft) in the button assignment list and give the input. It will be a DX assignment from then. This will work flawless. You should do that for all basic HOTAS switches. In fact, best to use it for all buttons recognized without Target. The other buttons you can use Target for.
Send from my Xperia X using Tapatalk
-
I’ll try! Thank you!
-
My general rule of thumb…everything on the stick and throttle is DX and everything on the throttle base is keyboard emulation. Otherwise you can get VERY weird behavior when pressing multiple things at once (i.e holding uncage and pickling for a slammer shot). I also highly recommend learning how to write the code yourself in the form of a script. Everything about TARGET and BMS keybinds/keyfiles will make a lot more sense afterwards and, quite frankly, it’s actually easier than dealing with the TARGET GUI.
-
I used to use Foxy for the Cougar and TARGET for the WartHog, but now days I just use BMS’ KEYMAPPING file with customized additions for my other controllers. Unless you’re trying to do something fancy (custom axes curves and complex shifted and unshifted key binds with or without custom delays and hold programming), using the controllers as DX devices and mapping with the sim key binding GUI, (for BMS, DCS, il2) is sufficient for 95% of the time.
-
I am still modifying my set-up for the Warthog. I am using the GUI as I have not got into the script (yet). However there are a couple of strange behaviours:
1. CURSOR Enable just “pings” and does not switch the mode as in the MFD. I have it set-up as pulse
2. The speed breaks I have set up with DX and use the short-cut keys. What happens were is that the breaks are either fully open or fully closed, and I cannot set them where I want (even though it works fine when using the open/close keyboard strikes on the keyboard
3. I want the FOV switch as a dual function. Hold to act as shift and short press to act as FOV on FCRAny help/pointers appreciated.
-
The speed breaks I have set up with DX and use the short-cut keys. What happens were is that the breaks are either fully open or fully closed, and I cannot set them where I want (even though it works fine when using the open/close keyboard strikes on the keyboard
Programming DX bindings directly in the BMS controller GUI should work for the speedbrake. I have the Warthog also and it works perfectly at my end. Didn’t you accidentally program the “toggle speedbrake” binding?
Send from my Xperia X using Tapatalk
-
Programming DX bindings directly in the BMS controller GUI should work for the speedbrake. I have the Warthog also and it works perfectly at my end. Didn’t you accidentally program the “toggle speedbrake” binding?
Send from my Xperia X using Tapatalk
It also works for #1 and #3 on his list. IOW, it seems for those three things listed, all he needs is BMS DX callbacks.
-
All sounds great…but…without using Target you can not use the coolie switch.
No one, yet, has found a solution for it. -
All sounds great…but…without using Target you can not use the coolie switch.
No one, yet, has found a solution for it.Good point of course, although I read some people on this forum telling they can use all switches on the Warthog throttle without Target. I never understood how that’s supposed to work. I use DX if possible and Target for the switches left over. Never had problems at my end. Still need to expand the DX bindings though, I’m not using any DX binding with release modifier yet. But like I said, everything works fine, so I am not in a big hurry to change it [emoji2].
Send from my Xperia X using Tapatalk
-
Good point of course, although I read some people on this forum telling they can use all switches on the Warthog throttle without Target. I never understood how that’s supposed to work. I use DX if possible and Target for the switches left over. Never had problems at my end. Still need to expand the DX bindings though, I’m not using any DX binding with release modifier yet. But like I said, everything works fine, so I am not in a big hurry to change it
.
There are threads here on this topic…
It’s tied to the facts that the WartHog has two POV hats (one on the stick and another on the throttle) and that in BMS only the “primary” controller we choose can which have the X-Y axes can also have the POV. While this is fine for the Cougar stick and throttle setup as DX devices, it does create problems for the WartHog controller setup. Hence why the workarounds are to use TARGET and its one virtual controller capability, or to use the WartHog’s POV as DX 4-way switch functions and not as a second X-Y POV hat.
1. CURSOR Enable just “pings” and does not switch the mode as in the MFD. I have it set-up as pulse
2. The speed breaks I have set up with DX and use the short-cut keys. What happens were is that the breaks are either fully open or fully closed, and I cannot set them where I want (even though it works fine when using the open/close keyboard strikes on the keyboard
3. I want the FOV switch as a dual function. Hold to act as shift and short press to act as FOV on FCR
Send from my Xperia X using TapatalkBMS code has programming for some of its controller functions that already have dual use and press/hold timing built in, like the TWS/RCS modes on the FSS TMS hat. So pre-programmed functions like these are not good choices to also assign user defined hold and/or delay parameters to within TARGET. Rather those that are regular toggles, switches and axes that are not already pre-programmed, are fine to add hold/delay parameters to.