@Terminator:
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 Tapatalk
BMS 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.