Warthog programming approach for DCS

[BitMaster]

Hey fellow TM-Warthog Hotas owners :)

 

I just got my Warthog combo and its been 15 years since my last TM gear broke apart, F22 Stick and F16-TQS, the one before the Cougar...

 

Well, things have changed a lot since then and programming the sticks is totally different then before as Direct-X has successfully taken over the game scene (wider scope) and buttons are usually programmed inside the game settings and not outside the game in a Stick-Software that then loads the file into your firmware, as I did with the F22 for TAW and Falcon4.

 

The stick is successfully connected, along with the rudders, all software installed (Target and Script Editor for TM, drivers for rudders). They all are present in DCS so far.

 

 

Simple things are no big deal but as I expected, you just cannot program complex things inside DCS, 3-way switches are a nightmare to make use of,

and and/or, delay, hold and release etc. is just not possible.

 

So, I didnt buy the TM to settle with this ! I need some starting aid to find the right direction on how things are best done with the Hotas and DCS.

 

Are you using Target to program complex setups ?

If yes, can that coexist with DCS settings ? What needs to be known to use Target and DCS if possible at all ?

 

 

If Target is not the way, is LUA the way to go ??

I have absolutely NO clue about LUA yet, but if need to be I am going to learn it.

 

 

I am thankful for every hint that saves me hours over hours finding the right way to approach this problem.

 

 

Some examples files would be cool too, so I can see how a working file looks like and play with it.

 

Trial and error is the best way to get to know something, it just takes way longer cause you not only learn what works, you also learn many many ways of errata and stop signs but those spent hours on the wrong path will pay back if you need to troubleshoot things because you most likely have been there before.

Only knowing how it works is half the deal, the othe rhalf is knowing most of the dead end roads.

 

*installed TS3 and thinking about using Chat as a tool for comms to solve this. Anyway, time to use TS3 as a part of the Hotas now that I am in my own room again and actually can make use of it without talking to the whole family samwe time and making a laugh of me

 

 

Bit

Edited February 21, 2015 by BitMaster

[Iku_CC]

TARGET script is way to go if you want to use Warthog as complex as it can be.

 

This GregP thread http://forums.eagle.ru/showthread.php?t=81222%c3%a4 is good place to start if you want to learn TARGET script + using DirectX buttons (and why use DirectX buttons).

 

And if you want to go "To Infinity and Beyond" look ivanwfr thread http://forums.eagle.ru/showthread.php?t=73271 for very very complex programming ( I can't understand this).

[cichlidfan]

TARGET script is way to go if you want to use Warthog as complex as it can be.

 

Agreed. The two linked threads are probably the most comprehensive resources here. I don't do anything complex but I do like Target. My stick mount is rotated a bit CCW and Target allows me to compensate for that as well.

[BitMaster]

OK, I see :)

 

Seems like I have another new hobby now, called Target !

 

 

Thank you guys, appreciated

 

Bit

[Puma]

if Helios will ever be part of your future, start now. You can use any hid as an input and drag/drop dcs actions into it. Plus all the other stuff Helios can do like gauges. I used target ONLY to setup a key combo for teamspeam PTT. Everything else is Helios or dcs internal config.

[BitMaster]

Please enlighten me what Helios is actually for.

 

I do NOT want to ever use more than 1 monitor !

If, then I get a OccRift in the future but no multi monitor setup afaict now.

 

If Helios is good for anything else I am all ears.

 

Bit

*fighting a cold and cough cough cough :(

Currently grounded by Flight Doc and Kitchen Command*

[Puma]

you can use Helios as a mapper of inputs to outputs. So for example add your joystick as an input interface. Add dcs as an output interface. Then just drag and drop rules like "when switch 27 goes on, set eac to on and batt per off". Very flexible. You can do three way switches easily. That will be all you'll use unless you get more monitors or an led board.

 

Just to be clear, I hope you are wanting to program non-native stuff into your warthog? Otherwise it should work out of the box where every control performs its real-life function without any programming.

[Shaman]

Have you ever looked at AutoHotkey?

 

I have not been using TARGET for years, I dislike limits of this software and the idea of running and switching "a profile".

I do everything in-DCS mapped to dxinput controlls and if I need to emulate a key or macro with any dxinput action, I complete it with Autohotkey scripts (emulate F14 keyboard key when pressing throttle's 4-way mic switch IN (5th action) for Voice Activated Commands' PTT button).

 

1) Warthog Stick + Throttle

2) Saitek Rudder Pedals

3) 4ea x Cougar MFD keypads

4) 2ea x USB Touchscreens with HELIOS running (touch enabled avionics panels)

5) Nostromo Keypad

 

http://www.autohotkey.com/

[BitMaster]

I see, I always thought Helios is only for monitor arrangement, not actually a device mapper that includes input and complex logical switching.

 

 

Yes, I am all for the "deeper" programming once I know the Module pretty good. You have to master the module first to know what you want and need.

 

 

Currently fighting a bad cold and can't do much but reading and getting into position :)

 

Bit