Warthog Toggle Switches 2018+

[LeCuvier]

I am curious to know more about the TrackIR and TARGET issues you experienced.

I had made a significant time investment in learning TARGET and I had established and documented profiles for the aircraft I owned then. Most of the time it worked. But sometimes TARGET seemed to be in conflict with TrackIR and I could not run both concurrent with DCS World. So I had to exit from all and start again. Without SSD at that time, that was a slow and frustrating process.

Note that there is an area where only .lua editing can solve your problem. This happens mostly -but not exclusively - with new or early access modules. Sometimes the developers have not made all cockpit commands available to the default.lua files. You have then no way to map them, even in TARGET. I have often been able to use info from the clickabledata.lua (which defines clickable cockpit commands) to add the missing commands to the default.lua so they can be bound to controls.

[hansangb]

LeCuvier, thanks. Yes, if moving outside of the Thrustmaster realm, I completely understand and agree. I would like to transition to something like AutoHotKeys or Joystick Gremlin to solve that issue, or I might just create my own program to allow programming all game controllers, not just TM.

 

Thanks for clarifying about LUA scripts. I've seen a lot of posts from people having nothing but frustration with game controller LUA scripts changing on them so I may have gotten the wrong impression. People have difficulty with TARGET too, but that is usually a matter of not taking the time to learn it - which I also don't blame people for that. It can be complicated.

 

I am curious to know more about the TrackIR and TARGET issues you experienced.

 

 

Not so much changing, although there was a change from 1.5 to 2x, but the default.lua can be overwritten during an update. A simple merge takes care of it, but it's something you have to be cognizant of. No real right or wrong way. It comes down to personal preference. Clearly, if you have bodnar/dsd's/GPWiz boards, Target isn't for you.

[LeCuvier]

Not so much changing, although there was a change from 1.5 to 2x, but the default.lua can be overwritten during an update.

With OvGME that's no issue at all.

[RogueSqdn]

One option that won't give you trouble when DCS updates is to make a copy of default.lua, named it "Throttle - HOTAS Warthog.lua," and add your modified commands to that.

 

If the module you're using already contains a file for the Warthog throttle, this idea wouldn't work (The file would get overwritten during DCS updates).

 

I use OvGME, and from tiem to time vary between using solely lua edits and using TARGET. I haven't settled on one method or the other. TARGET programming doesn't bother me at all, as I've been doing it since the early 90s with bother Thrustmaster and CH programming.

[hansangb]

Yup, I use JSGME as well. Haven't bothered with OVGME as I don't really have a need for it. It's just another thing you have to remember to do. Again, for me, it's six of one half dozen or the other as far as using LUA or Target.