Thrustmaster T.A.R.G.E.T. Compatibility

[blur]

I've found that regular key mappings work fine with T.A.R.G.E.T. But mappings with modifiers e.g. shift, alt, etc. don't work correctly. It seems that the inputs are possibly broken up e.g. Shift-C becomes Shift and C. I haven't had this problem with other sims. Has anyone found a work-around for this?

[Sokol1]

Use delay in the code, between key press.

Edited December 29, 2018 by Sokol1

[blur]

I analyzed this issue a little more. I set a joystick button for LShift-A (level autopilot) in game only an "A" (autopilot) is being seen. I set up a delay but in game this only delays when the "A" is received.  If I run the event analyzer it shows:

Key Press: LSHF

Key Press: A

Key Release: A [32ms]

Key Release: LSHF [34ms]

 

So the shift is being held down while the "A" is pressed and released. This mimics a manual keyboard entry which appears correct to me.

It's unfortunate the software doesn't allow introducing a delay between LSHF press and A press.

I can get around this by assigning unmodified keys. The only downside is that there's a limited number. Also, it's tough to determine if a key is already used so they have to be manually tracked.

 

Thanks for the tip.

 

[blur]

I believe I found a solution to this issue. Instead of defining a command to pulse LShift-A, it can be broken down into three separate commands;

LShift press, "A" pulse and LShift release. This is slowing things down enough so that the sim can detect the key presses.

 

Make sure to not select the sequence button as it will only send one of these commands per button press.

 

?

Edited December 29, 2018 by blur

[Hoss]

You need to use the "Press" and "Release" functions in the Assignments not Pulse or Hold.

 

For flaps up you would use LSHF + F, it's a "HOLD" type key press not a "PULSE"

 

Choose button FLAPS - UP/MR/DN, Click on UP position (FLAPU) and name UP position Flaps UP in EVENT NAME, first key command will be LSHF, save key command, in TYPE, select "Press" ADD EVENT, SAVE EVENT, then choose key command F save key command, still under "Press" in TYPE, ADD EVENT, SAVE EVENT  This will start your flaps to move up, now we need to get it to stop, using the same TM button moving backwards to the MR (NULL) position we will release the UP Flaps hold function of the button.   With the button still in the UP position will start the release phase by selecting key command "F", save key command, choose TYPE "Release", ADD EVENT, SAVE EVENT.  Choose key command "LSHF" still with Type "Release" function, ADD EVENT, SAVE EVENT.  I use the Flaps button on the Throttle for this because the center is a Null command, it the other command in keyboard page that's always lit up.  So on the other side the Down Flaps is the same sequence if needed.  But down flaps is just an F, so just map it like you would any other key  There is confusion with the F function and the LSHF + F function the up flaps in my game, and this solves it. So now when you move the switch from MR to UP you will generate a LSHF + F hold command, when you release the switch command by moving the switch from UP to MR will stop movement of the flaps. 

 

I use this for Autopilot three position switch

Path

Alt/Hdg

Alt

This is a three position switch, the center position is a "Null" function and is just a no command switch position used as a place for the switch to go on release and no command is generated in the physical position.  Autopilot uses the A command too many times and the game does not see it correctly and will cause commands you don't want, i find the same thing with the "B" command, I want to use speed brakes and it drops bombs, so I use this sequence for the "Pulse" press of a button.

 

Choose the Altitude position for the Switch, (ALT).  EVENT NAME = Autopilot, or level Stab which ever you want.  The KEY COMMAND is LSHF + A, so we will choose KEY CMD "LSHF" , under TYPE select "Press" function ADD EVENT, SAVE EVENT, then choose "A" still under "Press" function, add event, save event.  Now we are still going to use the "Press" command and leave "A" in the keystroke window, and add event, save event.  Now we will choose the Key command LSHF in keystrokes, ADD EVENT, SAVE EVENT so essentially we have used four commands to Press "LSHF", then "A" and then it simulates a release of "A", then "LSHF".  all under the Press TYPE command, because we move the switch from the center "Null" position rearward to the "Altitude" position where we are going to leave it until we want to come out of Autopilot/Level Stab.  Now when we want to stop Autopilot we do the same sequence LSHF + A but under the "Release" Type of control movement.  You may want to play with the Delay function so add some separation between command presses.  After the first command "LSHF" I use 10ms between it and "A", and 20ms between the next press of "A" and 10ms between "A" and 'LSHF" .  This solved all my problems of confusion in game of button presses seeing certain Alpha characters and their modifiers triggering the wrong game command. 

 

Hope this helps

 

Cheers

Hoss

[blur]

I tried your flap settings and they work very well, Thanks.

[mrgrey63]

i found this thread while looking for that problem

i am using a t16000m with tcs -> no switches

the solution did not work for me, and is some effort

 

my two cents (and solution): for the unresponsive key combinations, set a DXxx button and assign ingame

 

(p.s. when finished "show script" and save as .tmc for processing in target script editor which adds some nice methods)

[FlyingH]

@325th_Hoss, are these tips for use in the target gui or i the script editor? If in the gui how can I use them in the script editor?

@mrgrey63, same questions to you.

[mrgrey63]

gui, but that's fine because of visualisation.

when finished assigning keys click "view script" and save that file as .tmc for script editor use.