Programing the TM TQS with Alternative Launcher
-
Hi this post should help the TM TQS Viper Pack owner to get Combat ready in no time
-
First thing to do is to activate the “virtual buttons” in the TM Software
-
Secound thing is you start the Alternative Launcher and start binding your TQS as usual
-
Some Switches 2/3 -Way Switches / Knobs are not getting assignable when your are moving them physically
-
To get them working you can use the function “release” insted of “press”, for example the 3 Way Switch Master ARM/OFF/SIM
- or for the CMDS Knob “OFF”
- same goes with the CUTOFF Release - Idle Detent -Idle / off because this is a dx button, but check if you got following set g_bUseAnalogIdleCutoff 0 in the “falcon bms.cfg” set
Hope this helps
Thx for the input @airtex2019, @Skorp, @cougar56th, @Tomcattwo, @Zwingli and @r00t
-
-
Have you been able to get the zoom-in, zoom-out and zoom-reset working when binding them to the small slider-button next to the Speed Brake switch?
I’ve tried assigning in the Alt-Launcher and in the old config screen and the feature isn’t working when flying. I do have the Virtual Buttons active. -
-
@Echo / @airtex2019
Do you know of a way to get a “held” key using AL?I use F8 as my Push to Talk key for Voice Attack. Previously (before Viper TQS) on my old Cougar HOTAS (stick and throttle) I just set it up in Foxy to have the Throttle T2 (shifted - S3 IN) held. Worked fine.
With the new Viper TQS, I want to map it to the SHIFTED UHF Comms key on the Viper TQS (SHIFTED T2 UP), but it needs to be held rather than just pushed once. So far, I have tried mapping the F8 key to an unused callback (Winamp Stop playback), then mapped the SHIFTED T2 (UHF Comms) on the Viper TQS to that Winamp callback. Since I don’t have Winamp installed, it won’t do any interaction with BMS directly, but should press the F8 key. However, I need F8 to be held rather than just pressed.
I am using Win 11, so TARGET software is not an option without disabling my Core Security Protection in Windows (a bridge too far for me right now). Any help would be appreciated.
Can I do it by making both a Press and Release on the T2 UP? Maybe I can program the auto keyfile manually?
Any help would be greatly appreciated.
Regards,
Tomcattwo
(VoiceClone) -
@Tomcattwo I’m a little confused by all that, but I don’t think cross wiring the callbacks like that will result in the F8 key being pressed on your behalf.
I don’t use VA. Does it only support keyboard or can you not bind its ptt to a hotas button?
-
@airtex2019
Thanks for the reply! Yes, VA does support keybinding, and I will try that today. Between VA and AVCS (which also supports a PTT feature made specifically for BMS), I should be able to get the functionality.The more general question still remains - is there a way to do a “held” key (I.e. keypress repeatedly sent as long as button is held down keypresses stopped when button released), using AL?
Regards,
Tomcattwo
(VoiceClone) -
@Tomcattwo isnt this the case already? If I use COM switch (DX2) on TQS and bind it to the appropriate callback, I see transmit is on as long as I hold the button. Exact the same behavior as for the SPD BRK up (DX9). Or is that just because the configured release hasn’t been triggered?
-
@r00t
Thanks for the reply. Sounds like it works as it should. I am still in the midst of programming keystrokes to peripherals and had based my question on what I saw in AL. I think my question has been answered. I need to finish up the keybinding and test in game to see what functions and what does not.This is my first time using AL. For over 20 years I have been making my own keyfiles and using the “old” launcher successfully. When I installed 4.37U3 on my (brand-new system) and found I could not use Thrustmaster TARGET software, I decided to bite the bullet and try AL. I am still learning to use it. I appreciate your patience (and @airtex2019 's as well) in answering my questions. Good fly!
Regards,
Tomcattwo
(VoiceClone) -
@Echo ,
Thank you so much for posting this thread - it’s been of great value so far to me.In your first post, you provided a great example of how to use AL to program Viper TQS 3-way switches. Could you provide a similar example for programming knobs? I am having particular trouble getting the CMDS Mode knob programmed properly. I can’t seem to get AL to allow me to even set a DX for the “Off” position. And, from what I can tell in AL, when moving the knob backwards (for example from Auto to Semi-Auto) the position being switched to does not seem to trigger the correct DX press.
If you can find the time, could you post an example of programming that knob? Any help would be greatly appreciated aand thanks in advance.
Regards,
Tomcattwo
(VoiceClone) -
@Tomcattwo works for me when setup like this:
“Mode Knob - OFF” is basically DX29 RELEASE because DXC59 (the virtual DX button) isn’t catched in the “awaiting input” dialogue (like mentioned for other DX by the OP).
Don’t get confused by whether or not the DX PRESS event is “highlighted” in AL and / or shown in “ASSIGNMENTS” in the lower left when switched back and forth. There is a lengthy discussion about that here: https://forum.falcon-bms.com/post/384319 It isn’t always the case because of reasons, but it works in the sim (at least for me).
-
@r00t
Thank you! Perfect! Another question: Have you been able to map the RDR CURSOR(s) (Up, Down, Left, Right) to TQS microstick in AL? If so, how did that work? If not, perhaps I can assign them in Game Setup.
Thanks again for all your fantastic help!
Regards,
Tomcattwo
(VoiceClone) -
Launcher -> AXISASSIGN -> FLight Control & Avionics
Large Deadzone on Cursor X and Y and Cursor Y inverted.
-
@r00t
Many thanks - I just overlooked this - I had actually done it last night - rookie mistake
Regards,
TC2 -
-
@Echo To make HDG Button on the TQS usable as such, I needed to modify g_nKnobAccelerationDelta in user.cfg to:
set g_nKnobAccelerationDelta 350
The default value wasn’t usable in terms of scrolling performance. I use the 5 degrees callback which even does 1 or 2 in/decrements depending on how fast you turn the knob here:
Couldn’t find a satisfactory combination of delta and 1 degree callback. YMMV. Might be a useful hint for a TQS-101
-
@r00t if memory serves … the 1° callbacks are always 1° … while the 5° callbacks are either 1 or 5° depending on g_nKnobAccelerationDelta > (timeBetweenConsecutiveClicks)
-
-