Hi,

Since yesterday I have been working on a file for the Su-25 using the Target Script Editor.
In there I have defined trim settings to Hat1. This is the code:
MapKeyIO(&Joystick, H1D,0,
REXEC(0, 100, "TrimDXAxis(DX_Y_AXIS, 5);")); //Trim Up

All works fine, execpt the lights in the cockpit. They don't react to this, they stay on as if nothing happened.
When I use the keyboard RCtrl+, the lights do go out.
It is the same for the X & Rudder axis.
Any ideas?

Thanks.

it's logical, the game cannot know that you are using the hardware trim feature of T.A.R.G.E.T. The only way to get the light working in the cockpit is to use the Keystrokes of Flaming Cliffs to control the Simulator trim function. You only have to programm the keystroke to each position of the Hat 1.

Exactly. hsth, hardware trim via scripting is interpreted no differently by Lock On / Flaming Cliffs than an actual displacement of your joystick would be.

Thank you both for your help.
This is what I coded:


This works fine for trimming up/down and left/right. But not for the rudder left/right. In fact, even the keystrokes entered from the keyboard do not work for the rudder anymore. Only the Z and X keys for full rudder.
I must have overlooked something but what????

It even gets more confusing. As said, the rudder does not move on trimming. But the light in the cockpit does!

check if the things perform the same way when using a "real keyboard".

Sorry that I don't understand your question.
I ran the script, started FC2, started the mission. The HAT trimming for UP/DOWN & LEFT/RIGHT worked fine. But using the HAT did not trim the rudder. The throttle axis worked for the rudder worked fine.
So I checked using the keys on the keyboard. The rudder reacted normally to Z & X but not to L-Ctrl+Z/X.
The lights in the cockpit reacted to all input, even the HAT trim. Only the rudder itself did not move on trim.

In my other post SU-25 tmc file you can see the script I used, except for the HAT function because I changed it to your advice.

well if when using the real physical keyboard
"The rudder reacted normally to Z & X but not to L-Ctrl+Z/X."

there's no way to obtain something different using the TARGET Keystrokes. I will check on my side.