And here I was, looking for a simple button or slider in the GUI..

Thanks, I'll have a look at it. Somehow I miss good ole Foxy!

There are simple buttons and sliders in the GUI editor, but if you want to change light intensity or make the lights behave in a specific manner according to button-pushing ingame you have to script them.

Well,

This is a simple solution to put in a script file:


The APU switch now turns the internal power on in FC2 and at the same time the backlight of the throttle.
And when the switch is turned off, the backlight is turned off. Now I can keep the throttle plugged in without lights burning all day.

Instead of:



you can also write:

Thanks for the heads up!

Got it, now trying to find some manual to learn its programming!

All this stuff can be Controlled from the graphical interface, everything is in the manual. Most of the job is done from the virtual Keyboard/mouse/joystick window. You can access it from the event specs window.

O.O Wonderful!

Thanks a loT!

Dimebug, leaving aside the differences in file format between the GUI and the Script Editor and their apparent incompatibility one with the other, where in the manual(s) are any references to the scripting that controls the LEDs? I've read both several times and searched in vain for an LED section in either the TARGET_User_Manual_v1.5_ENG.pd or the TARGET_Script_Editor_Basics_v1.4_ENG.pdf which, unless I'm missing something really big (which is possible, of course) are the latest manual versions.

My experience with the two engines (GUI and scripting) leads me to use the Scripting Editor solely, which has no visual clues to programming syntax and nothing that I've found dealing with LEDs. Obviously programming them can be done, but the manuals are not clear on the subject, at least not to me. Perhaps there is an update I've missed or one on its way (I hope so). Or maybe, like so many things, it is there right in front of my nose and I'm not recognizing it.

GUI led management is page 24 to 27 of the gui manual (you can read it from the "how do i ?" list of the Target main page.

For the script, looks like the manual available on the TM website is the older one, not the latest. I'm gonna ask for this to be changed.

this should help you :


LED and backlight Control
The script language offer the possibility to control LED state and Backlight intensity of several controllers like the HOTAS Warthog Throttle and the MFD pack.
T.A.R.G.E.T support some device that where developed a long time before the software was created. The MFDs lightning support in the T.A.R.G.E.T software is a bonus. If you are experiencing issue like MFDs not responding, stop the script execution, simply unplug and re-plug the MFDs and launch the script. This can happen If the USB port was gone in "sleep" mode while MFDs where not used.


Turn "ON" a LED
Syntax:

LED(&input device, LED_ONOFF,LED_CURRENT operator LEDnumber);

The operator is used to control the status:

- will turn "OFF"

+ will turn "ON"

^ will revert the LED status


Example using a MapKey function (here, we turn" ON" LED 1 of the Warthog Throttle when joystick Hat 2 Up position is pressed):
MapKey(&Joystick, H2U, LED(&Throttle, LED_ONOFF, LED_CURRENT+LED1));

Turn "OFF" a LED

LED(&input device, LED_ONOFF,LED_CURRENT-LEDnumber);

Notice that we've just change the + for a - to turn off the LED. Now let's turn "OFF" our Throttle LED1 each time Hat 2 down is pressed.

MapKey(&Joystick, H2D, LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1));


Change the status of a LED
Sometimes, you may want to change the status of a LED whatever his current state (to make it blink for example).

LED(&LMFD, LED_ONOFF, LED_CURRENT^LED2)

MapKey(&Joystick, H4P, LED(&RMFD, LED_ONOFF, LED_CURRENT^LED2));

Each time we press the hat 4 push button, the LED 2 of the right MFD will change of state.

The backlight intensity is almost controlled the same way. The difference is that we have different backlight steps.
You can control the Backlighting intensity from null to full. Warthog throttle offers 6 levels of intensity, MFDs have 256 different levels of intensity, from 0 to 255.

The throttle and the MFDs share the same command, but as the throttle doesn't offer the same number of levels of lighting, you have to divide the full range of value.

0 to 42 is OFF
43 to 85 is level 1
86 to 128 is level 2
129 to 171 is level 3
172 to 214 is level 4
215 to 255 is level 5

Syntax:

LED(&Input Device, LED_INTENSITY, value of the intensity)

Let's imagine that we want to control the left MFD backlight power with the Warthog throttle EAC switch.

MapKey(&Throttle, EACON, LED(&LMFD, LED_INTENSITY, 255));
MapKey(&Throttle, EACOFF, LED(&LMFD, LED_INTENSITY, 0));


Start a configuration with all lights in the right status.
It's possible to initialize the LED status when launching the script. For this we use the advanced programming code (see later). The commands must be placed in the same part of the script than your MapKey functions.

//initialize backlight power
ActKey(PULSE+KEYON+LED(&Throttle, LED_INTENSITY, 129)); //set Throttle backlight power to middle
ActKey(PULSE+KEYON+LED(&LMFD, LED_INTENSITY, 129)); //set left MFD backlight power to middle
ActKey(PULSE+KEYON+LED(&RMFD, LED_INTENSITY, 129)); //set right MFD backlight power to middle

//initialize LED status all "OFF"
ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1)); //set LED 1 OFF
ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2)); //set LED 2 OFF
ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3)); //set LED 3 OFF
ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4)); //set LED 4 OFF
ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)); //set LED 5 OFF
ActKey(PULSE+KEYON+LED(&LMFD, LED_ONOFF, LED_CURRENT-LED1)); //set left MFD LED 1 OFF
ActKey(PULSE+KEYON+LED(&LMFD, LED_ONOFF, LED_CURRENT-LED2)); //set left MFD LED 2 OFF
ActKey(PULSE+KEYON+LED(&RMFD, LED_ONOFF, LED_CURRENT-LED1)); //set right MFD LED 1 OFF
ActKey(PULSE+KEYON+LED(&RMFD, LED_ONOFF, LED_CURRENT-LED2)); //set right MFD LED 2 OFF

Dimebug,

Very helpful. Thank you for taking the time to explain all that -- lots of typing and greatly appreciated.

Actually, both the GUI and script editor manuals on the Thrustmaster website were one version old but they've been updated (on March 15) and now contain the information you described.