Help with Warthog script programming

[Svend_Dellepude]

You can use whatever DX button where ever you want on in TARGET, but you need to reassign them again in DCS. Thats why i'm suggesting you to go with the default WH setup (i.e.. no target), You will have all buttons assigned and just add the paddle switch as a modifier in DCS and you will instantly have two joystick layers ingame.

Unless you want to do program exec or rexec or other functions, TARGET is just dead weight and a lot of hazzle in this case.

[Yurgon]

I'm just trying to add some additional functionality - but looks like I have to redefine every button.

 

Yup, that's why I gave up on TARGET early on.

 

I used to program the F-16 FLCS and Cougar with the TM Software (Foxy for the Cougar, don't remember what the predecessor for the FLCS was called), but IMO TARGET has some fundamental flaws - one of them being that (as far as I can tell) in a TARGET profile, every single button needs to be mapped by hand.

 

Without TARGET, throttle and stick of the Warthog are simply DirectX devices with DirectX buttons mapped to every physical button, and since DCS correctly maps most of them by default, I think it's much easier to just configure this to my needs within DCS.

 

For example, trying to define china-hat forward.

 

Doc tells me what the action should be under different SOI scenarios - so what do I define.

 

For example when HUD is SOI, the short is Set Mav as SOI and long is Slave all to spi.

 

Now I can't find the definitions for these.

 

Since there are different SOI contexts - i would imagine DCS just needs to know the button was pressed (long/short) as opposed to the exact action (that would depend on the context). Right?

 

Sounds right.

 

The action triggered by, say, China Hat Forward Short, depends on the Sensor Of Interest (SOI). That means that there's no key command for "Set Mav as SOI". That's just what happens when you press the China Hat forward for a short moment while the HUD is SOI.

 

I think you should just put TARGET aside for a moment, go in-game, and go through the A-10C Training Mission "A-10C Familiarization" -> "HOTAS Fundamentals". That should clear this up easily.

 

One of the great benefits of a combined device (throttle+joystick) is you can define commands w/o the requirement to touch the keyboard.

 

Like Svend_Dellepude said, you can already do that from within DCS. Also, the modifier doesn't need to be on the same device that the key is to be bound to. I.e., you could define the Boat Switch as modifier and then have the Hat on the stick perform different actions depending on the Boat Switch (although I would advise against it because the Boat Switch is integrated into the HOTAS concept and you'll loose its functionality when using it as a modifier).

[cichlidfan]

... I.e., you could define the Boat Switch as modifier and then have the Hat on the stick perform different actions depending on the Boat Switch (although I would advise against it because the Boat Switch is integrated into the HOTAS concept and you'll loose its functionality when using it as a modifier).

 

Oddly enough, you can actually do that (have the boat switch remain functional and use it as a modifier). However, I never could think of a situation where being able to do that with any switch would be useful.

[Yurgon]

Oddly enough, you can actually do that (have the boat switch remain functional and use it as a modifier). However, I never could think of a situation where being able to do that with any switch would be useful.

 

Huh, good to know!

 

But yeah, I agree, I don't think that would work too well.

[erjdriver]

You can use whatever DX button where ever you want on in TARGET, but you need to reassign them again in DCS. Thats why i'm suggesting you to go with the default WH setup (i.e.. no target), You will have all buttons assigned and just add the paddle switch as a modifier in DCS and you will instantly have two joystick layers ingame.

Unless you want to do program exec or rexec or other functions, TARGET is just dead weight and a lot of hazzle in this case.

 

Ok I gave up on TARGET - the amount of work necessary is ridiculous and also lack of documentation.

 

I used the in-DCS modifier and it's not too bad.

 

One of the features I liked in TARGET was able to assign an action to a button press and another on release.

 

For example I would like to assign RIGHT-VIEW (w/ S4 mod) TO map-view and on release back to cockpit view.