Can TARGET fix multiple inputs?

[VC]

I've had a T.16000M for years and it's always served me well without any additional software. However, the trigger sensor is starting to go and giving multiple inputs when pressed, last night I fired 4 missiles at the same time without meaning to (I only wanted one!). I don't really trust myself to take it apart and clean it, I'm looking at buying a new joystick but not sure when and need a fix in the meantime.

 

If I get TARGET, does it have the capability to de-dupe inputs? E.g. some control to ignore repeat inputs of the same button within a certain amount of time? Anything else I can do about this?

[Ant0ine]

For my latched switch I use a little chain that include a sort of sleep. It allow me to switch the position of the switch twice physically within 300ms while virtually it would move only once. That allow me to re-sync physical/virtual switch. That might work for you..

 

Only for short trigger pulsation however. No idea how we can make long press work properlly again.

 

//APU (APU) = Automatic RPM regulator = (DX52;DX53) =  
MapKey(&Throttle, APUON, CHAIN(DOWN+DX52, D(300), UP+DX52));
MapKeyR(&Throttle, APUON, CHAIN(DOWN+DX52, D(300), UP+DX52));

DX52 being mapped to Automatic RPM regulator cycle switch. 2 positions switch on the 109, 190 I fly.

 

So for your T16K trigger it should be :

 

MapKey(&T16000, TS1, CHAIN(DOWN+DX1, D(300), UP+DX1));

 

Adjust delay duration as needed.

 

Edit : We could change the delay duration on the fly..

 

MapKey(&Throttle, APPAT, EXEC("MapKey(&T16000, TS1, CHAIN(DOWN+DX1, D(64), UP+DX1);"));

MapKey(&Throttle, APAH, EXEC("MapKey(&T16000, TS1, CHAIN(DOWN+DX1, D(1000), UP+DX1);"));

MapKey(&Throttle, APALT, EXEC("MapKey(&T16000, TS1, CHAIN(DOWN+DX1, D(2000), UP+DX1);"));

Edited December 15, 2019 by Ant0ine

[VC]

Thank you, I'll have to work out how to use all that (never used TARGET before), but it seems like it does what I want.

 

I have no problem with long press. In FC3 aircraft that require trigger hold, I always launch one missiles no problem. It's only in some planes e.g. F/A-18C that launch missiles immediately, where I get accidental multiple launches. I just need to make this trigger more stable, so if in initial press there are 2 or 3 accidetal inputs in first 200ms or so, it only sees one. After that it's fine.

Edited December 13, 2019 by VC

[Ant0ine]

Thank you, I'll have to work out how to use all that (never used TARGET before), but it seems like it does what I want.

 

I have no problem with long press. In FC3 aircraft that require trigger hold, I always launch one missiles no problem. It's only in some planes e.g. F/A-18C that launch missiles immediately, where I get accidental multiple launches. I just need to make this trigger more stable, so if in initial press there are 2 or 3 accidetal inputs in first 200ms or so, it only sees one. After that it's fine.

 

The problem is with my code you won't be able to hold trigger as long as you hold the button which is what you would want for some ordonnance delivery. My code simply do a single pulse, no matter how long you hold the trigger. With your buggy trigger the pusle would certainly loop until you release the trigger.

Edited December 13, 2019 by Ant0ine

[Svend_Dellepude]

MapKey(&Throttle, APUON, DOWN+DX52);

MapKeyR(&Throttle, APUON, TEMPO(0, UP+DX52, 500));

 

Used like this you have a 500 ms delay from trigger release, until the virtual button is released. Use any timing you find suitable. This will prevent flicker from the twitchy trigger.

 

This also means that you have to have a 500 ms pause between trigger presses.

[VC]

Thanks for the extra code. I'm having some other issues with TARGET not merging my stick and I haven't had time to look into this but will give it a go when I get around to it.

[Svend_Dellepude]

Try to unplug and replug your devices after windows has booted. That did it for me. I now have my ™ stuff connected to a USB hub that I turn on after windows has booted.

[VC]

I just tried that, it makes it get detected for about 5-10 seconds, then drops off again.

Edited December 16, 2019 by VC

[Ant0ine]

Oh, maybe windows send it to "bed" to save energy?

 

https://helpdeskgeek.com/how-to/prevent-windows-from-powering-off-usb-device/