Thrustmaster TARGET problem

[Kenta]

Ok!

 

I have the TM Warthog HOTAS.

So I have this little problem... I've configured the throttle and joystick in TARGET and it should work perfectly, but something is weird. For example I've binded the Flight Director button onto the APU START switch on the throttle. So that when I flip it, it should turn on the FD and when I deflip it, it should turn it off. What in fact happens is... that sometimes it does work, when it doesn't... it strangely flips the Manual/Auto weapon system control switch.

 

And for example I've set the Cannon round selector switch HE/AP to the ENG OPER - L Button.

It works, but when it doesn't it switches the Cannon on the cyclic to the up position... so if I have Vihkrs set up... it switches to cannon...

 

This aren't the only examples, I have more, it seems that every button has a second function to it, even though it isn't set up this way...

 

HELP PLEASE! :helpsmilie:

[marrow]

I've had the same problem with TM TARGET.

 

Sometimes if a command involves modifier (e.g LCTRL+c for cannon round selector) the sim registers it randomly without the modifier (in this case "c", which is cannon select). I think the problem is that the command is too fast and thefore the sim might miss the modifier.

 

It's easy to fix if you are using text scripts for making the profiles. There you can set the duration of pulsed commands. It's this line:

 

SetKBRate(60, 70);

 

First number is duration of pulse (in ms) and second number is delay between chained commands. Default duration for pulse is 32 ms and it caused the problem you describe. I found that increasing pulse to 60 ms fixed the problem in my case. If you are using GUI I'm not sure it's possible to change the duration.

 

I suggest that you learn the basics of script language, it's much more versatile and even faster to make profiles after you learn it. Read the "TARGET_Script_Editor_Basics" and you are making your own scripts in no time.

[Kenta]

I've had the same problem with TM TARGET.

 

Sometimes if a command involves modifier (e.g LCTRL+c for cannon round selector) the sim registers it randomly without the modifier (in this case "c", which is cannon select). I think the problem is that the command is too fast and thefore the sim might miss the modifier.

 

It's easy to fix if you are using text scripts for making the profiles. There you can set the duration of pulsed commands. It's this line:

 

SetKBRate(60, 70);

 

First number is duration of pulse (in ms) and second number is delay between chained commands. Default duration for pulse is 32 ms and it caused the problem you describe. I found that increasing pulse to 60 ms fixed the problem in my case. If you are using GUI I'm not sure it's possible to change the duration.

 

I suggest that you learn the basics of script language, it's much more versatile and even faster to make profiles after you learn it. Read the "TARGET_Script_Editor_Basics" and you are making your own scripts in no time.

 

Yes, I've noticed that when I set the pulse to 33 ms which is max in GUI... the problem is less likely to occur, but 33 ms is max in GUI.

 

Ok, thanks, will try learning how to write a script.

[Kenta]

Thank you marrow!

 

Did what you told me to. Works as it should. :pilotfly:

[Home Fries]

I use SetKBRate(50,60) by default, and I've noticed that with DirectX mappings sometimes DCS needs the modifier before the primary button. I'll code something like this for the macro (DX30+DX2 for the cannon round select, using DX30 as a modifier):

 

MapKey(&HCougar, S2, CHAIN(DX30,D(10),DX2));

 

This tends to give DCS enough time to recognize the modifier before seeing the primary command.