Ant0ine

Here is another one I really like. (Not my setup).

A chain is two event at the same time, if you set no delay between the two event. If I understand correctly you want to hold a key which will enable NWS, and apply left/right rudder at the same time? If so I don't think you need Target Script Editor. You can use Target GUI. IIRC rudder keyboard shortcut are w and x (Azerty) and NWS is hold S. So, on your button you want to create a chain that will hold both S and W or X at the same time. The resulting code should be : MapKey(&xxx, xxx, CHAIN('s', D(0), 'w'); MapKey(&xxx, xxx, CHAIN('s', D(0), 'x'); Edit : I'm not sure and can't test the the above code. We want the key to be held down as long as you hold the button. If the above code don't work that then try : MapKey(&xxx, xxx, CHAIN(DOWN+'s', D(0), DOWN+'w'); MapKey(&xxx, xxx, CHAIN(DOWN+'s', D(0), DOWN+'x'); MapKeyR(&xxx, xxx, CHAIN(UP+'w', D(0), UP+'s'); MapKeyR(&xxx, xxx, CHAIN(UP+'x', D(0), UP+'s');

Try : newTiming := 85 $Tab:: send {tab down} sleep, newTiming send {tab up} KeyWait Tab ; This is to avoid autorepeat. return Edit : If it work, then I rather advise you to use this technique, which does the same thing, prevent autorepeat, but doesn't use keywait which is problematic when use press multiple key at the same time. Tab_pressed := 0 newTiming := 85 $Tab:: { If (Tab_pressed) Return Tab_pressed := 1 Send {tab down} Sleep newTiming Send {tab up} Return } $Tab Up:: { Tab_pressed := 0 Return }

Please see this post, might be the same issue. https://forums.eagle.ru/showthread.php?t=255394 TL;DR : Try to increase keyboard shortcut pulse duration.

:thumbup: Does anyone know if this is a bug, or rather a feature? Like, for safety reason?

In this post I explain how to change the ministick so that it output a normal DX button. http://forum.vkb-sim.pro/viewtopic.php?p=40507#p40507 No idea for the light, note that after you update firmware/software, you should reset the stick to default, THEN load your profile again. If that doesn't solve the "problem?" then to know what those led means (how they are configured), you'll have to edit the zconfig.ini this way : [user] PartialWrite=0 User=Developer Then restart the software and now you should have acces to more panel, including the one that let us configure the led.

+1

To me the deadzone is a bug / error. However, you may have not realized yet that the idle position isn't the same depending if you have weight on the wheel or not. I noticed that while redacting this guide (and that isn't a bug but a feature.. Which we should be able to turn off btw because most throttle can't replicate that..), I also propose a solution : https://forums.eagle.ru/showthread.php?t=250033

No you can't control the led with Joystick Gremlin, however you could use Joystick Gremlin on top of a Target Profile to get both. In Target GUI we see the off position of the switch, so we can map them directly. To do that in Gremlin we have to use 'MACRO' and set 'condition'. Here is an exemple : https://imgur.com/a/T7y4gwx Another one here on the flap switch : https://imgur.com/a/96Hifh7

Note that you can use Gremlin on top of Target.:thumbup:

For DCS it is easy, because we do not need to hide physical controller. For other game it could be a "problem", until you learn how to hide controller properly thanks to HID Guardian.

Or use Joystick Gremlin and do everything within its UI :thumbup: Uhm.. How did you program that? In Target you remapped the axis to button/keyboard shortcut? If so, please share the script so we can check. Also tell us exactly what function you're mapping it to. I'm having trouble to follow. "things like climbing down and up canyons" WAT?:huh: Edit : "I,ve set up this directly inside DCS, but when I load target it dosen,t works." Make sure to map the axis AFTER the Target profile is loaded. Because if you do it before, you'll map the Warthog throttle axis. But if you do it after, you'll map the Thrustmaster combined virtual device axis, which is what you want.

They don't have the 16, 18, nor A10 yet, but they have the F14. And they sell a TM adapter so we could use Cougar, Warthog and Hornet grip from TM. THEY DO NOT ADVISE TO DO THAT ON GLADIATOR BASE. TM grip are to heavy for the plastic gimbal of the Gladiator. https://vkbcontrollers.com/?product=f-14-combat-grip-stand-alone

Correct, you can convert a script from Target GUI to Target Script Editor but you can't go the opposite way.

Sure. Go ahead, ask.

There is something wrong in your chain, you have a delay, and a press event. You need a press, then a delay, then a release. It should be like this : MapKeyIOUMD(&Throttle, APUON, CHAIN(DOWN+'l', D(300), UP+'l') Edit : And it should be exactly the same on APU OFF. So, here is what my Script in Target Script Editor would look like : MapKey(&Throttle, APUON, CHAIN(DOWN+'l', D(300), UP+'l'); MapKey(&Throttle, APUOFF, CHAIN(DOWN+'l', D(300), UP+'l'); Edit : You have multiple time the same thing because you're programming the same behavior in all layer and sub-layer. I(In) O(Out) U(Up) M(Middle) D(Down).

Ok that is normal. To do the chain in Target GUI I think you have to do the following : On APU ON : PRESS L Delay 300ms Release L On APU OFF : PRESS L Delay 300ms Release L Press and release are a "type" of event that you have to choose prior to add an event to the "queue".

To my knowledge, no, you could do that with Target Script Editor. Or Joystick Gremlin.

Yes, Gremlin is better than Target GUI that's for sure.

The new base will use Rev B connector. What is the connector type of your Warthog adapter? For it to work with the new base the pin should be on the adapter side.

Please post screenshots cause I don't really remember how we could do that with the GUI. I think we have to add several event following each other on a same input, which will create a macro (chain). You could also contact me (hon0#0570) on Discord so we could screen-share. Edit : In Target GUI, click on view script and copy past everything in here so we can check. Your APU line should looks similar to mine : MapKey(&Throttle, APUON, CHAIN(DOWN+DX52, D(300), UP+DX52)); MapKeyR(&Throttle, APUON, CHAIN(DOWN+DX52, D(300), UP+DX52)); Or MapKey(&Throttle, APUON, CHAIN(DOWN+DX52, D(300), UP+DX52)); MapKey(&Throttle, APUOFF, CHAIN(DOWN+DX52, D(300), UP+DX52)); Edit : See "Creating a chain" page 25/43. http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_User_Manual_ENG.pdf

On each physical switch flip, either up or down, I output a "long"(300ms) pulsation of a virtual joystick button. This way I can flip the switch twice while the game will only see one pulsation. This allow me to quickly resynchronise the physical switch with the one in the plane.

:thumbup: https://i.imgur.com/tNGMt0J.gif

I don't understand what you mean sorry. You want to make everything to load automatically as you run a game? If so I don't know how to do that.

https://flightsimcontrols.com/product/vkb-sim-gladiator-k/