Hardware & Technical Thrustmaster TARGET software: advice needed!

[Roberto]

So I've had a crack at creating some custom bindings for m' Warthog HOTAS in the TARGET GUI, and I've not done too badly for someone who's not that technically minded. However, I could still use some help on a few things from any TARGET users out there:

1. I previously had FA On/Off bound to the "lever button" (on the back of the Warthog stick) within ED's control settings, and it worked perfectly. It doesn't seem to work with TARGET: it flips off and then on again instantly. If I change the behaviour from "Pulse" to "Hold" then it works, but I don't want to have to keep holding the lever! Is there any solution? Should I resign myself to using another switch/button? Or just not have a binding for FA in my TARGET file, and set it up "manually" in ED?

2. It's not something I consciously thought about before, but previously (with the controls just set up in ED), when navigating around the panels, a single nudge would move you up/down/left/right once, and holding the toggle for longer would move you up/down/whatever multiple times. Currently I've just got "single nudge" navigation working, and it's a bit laborious scrolling up and down one item at a time. Would additional "Hold" chains (with multiple events) for each control do the trick? Or, again, will I have to just strip it out of the TARGET file and set it up in ED again?

3. This one's not important, but I'd still like to know how to do it, if poss! I've created a basic sequence for the landing gear, whereby each time I press the button, in addition to the gear going up or down, an LED turns on or off. Is there a way to get all five LEDs (behind the throttle) to turn on and off together? (Since there aren't separate gear up/down controls, I figure there's no way to get it so the lights come/are on when the gear's down, as opposed to them coming on the first time you press the button during a playing sesh, and every other time thereafter. Oh well.)

 

[Roberto]

Bumping in the hope some bindings wizard will see this...

 

[Roberto]

Well, I'll just talk to myself then. Discovered I needed to switch FA Off to "toggle" in ED as well, so that was an easy fix. And I wound up stripping all the UI/panel-switching controls out of my TARGET configuration and setting them up in ED again - it's a bit messy (originally I envisaged the configuration file "taking over" everything), but now that's sorted too. Which just leaves the lights, which is just a cosmetic thing.

Went through a lot of unnecessary faff, but it's worth it to finally have the throttle setup I wanted. Now to commence intensive FA-Off training!

 

[Codger]

Good luck

 

[Roberto]

Good luck

I'm going to need it!

 

[Archvillain]

3. This one's not important, but I'd still like to know how to do it, if poss! I've created a basic sequence for the landing gear, whereby each time I press the button, in addition to the gear going up or down, an LED turns on or off. Is there a way to get all five LEDs (behind the throttle) to turn on and off together? (Since there aren't separate gear up/down controls, I figure there's no way to get it so the lights come/are on when the gear's down, as opposed to them coming on the first time you press the button during a playing sesh, and every other time thereafter. Oh well.)

You don't need to make a sequence, you can just assign more parameters to the (keypress) event. Or at least IIRC. I think I stopped bothering with sequences and got the lights working without them. The Target GUI has changed since I set it up though. (Bear in mind that the configuration file that Target generates is a text file of human-readable settings. It might be easier to copy-paste-edit complex events in the file if the GUI is not helpful)

Also, don't feel you have to use all the lights for landing gear, there are heaps of other things you can use an indicator lamp for.

Eg I have lights indicating landing gear, silent running, headlights, cargo scoop, and engine reverse.

 

[Hossi]

1. I previously had FA On/Off bound to the "lever button" (on the back of the Warthog stick) within ED's control settings, and it worked perfectly. It doesn't seem to work with TARGET: it flips off and then on again instantly. If I change the behaviour from "Pulse" to "Hold" then it works, but I don't want to have to keep holding the lever! Is there any solution? Should I resign myself to using another switch/button? Or just not have a binding for FA in my TARGET file, and set it up "manually" in ED?

Just use a 'Down+'.../'Up+...' command. I have one button to go fa-off while holding the button, and then I have a 'shift' key to hold it until I press it again.
MapKeyIO(&TWCSThrottle, TBTN3, SEQ(DOWN+DX20,UP+DX20),DX20);

2. It's not something I consciously thought about before, but previously (with the controls just set up in ED), when navigating around the panels, a single nudge would move you up/down/left/right once, and holding the toggle for longer would move you up/down/whatever multiple times. Currently I've just got "single nudge" navigation working, and it's a bit laborious scrolling up and down one item at a time. Would additional "Hold" chains (with multiple events) for each control do the trick? Or, again, will I have to just strip it out of the TARGET file and set it up in ED again?

I uses a 'REXEC' to keep pushing a button as long as I hold it down for exactly this purpose.

This one keeps pushing the button every 50 ms if I hold it longer then 400ms to start with
MapKeyIO(&Joystick, H3U,
DX10,
TEMPO(
DXHATUP,
REXEC(1,50,"ActKey(KEYON+PULSE+DXHATUP);"),
400));


No idea on the LEDs. I use a warthog together with a twcs-throttle. No LEDs for me.

 

[Roberto]

You don't need to make a sequence, you can just assign more parameters to the (keypress) event. Or at least IIRC. I think I stopped bothering with sequences and got the lights working without them. The Target GUI has changed since I set it up though. (Bear in mind that the configuration file that Target generates is a text file of human-readable settings. It might be easier to copy-paste-edit complex events in the file if the GUI is not helpful)

Yeah, I can't see a way of doing it in the GUI. This looks to be the relevant line in the script:

MapKey(&Throttle, LDGH, CHAIN( PULSE+USB[15], D(), SEQ( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED1), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1))));

I haven't gone into the scripting at all - it's really not my forte - but I can guess the sort of thing that might be required:

MapKey(&Throttle, LDGH, CHAIN( PULSE+USB[15], D(), SEQ( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED1, LED_CURRENT+LED2, LED_CURRENT+LED3, LED_CURRENT+LED4, LED_CURRENT+LED5), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1, LED_CURRENT-LED2, LED_CURRENT-LED3, LED_CURRENT-LED4, LED_CURRENT-LED5))));

Could be wrong, though, and I don't even know if you can edit the script directly from within the GUI.

​

Eg I have lights indicating landing gear, silent running, headlights, cargo scoop, and engine reverse.

That is a damned impressive setup!

Just use a 'Down+'.../'Up+...' command. I have one button to go fa-off while holding the button, and then I have a 'shift' key to hold it until I press it again.

MapKeyIO(&TWCSThrottle, TBTN3, SEQ(DOWN+DX20,UP+DX20),DX20);


I uses a 'REXEC' to keep pushing a button as long as I hold it down for exactly this purpose.

This one keeps pushing the button every 50 ms if I hold it longer then 400ms to start with
MapKeyIO(&Joystick, H3U,
DX10,
TEMPO(
DXHATUP,
REXEC(1,50,"ActKey(KEYON+PULSE+DXHATUP);"),
400));

I think I'd have to read the manual for the Script Editor to get a handle on this! Which I'll do if my current config stops working for whatever reason. But as it stands, I've now got the functionality I wanted.
​