Viper TQS, using new Alt Launcher vs. the old launcher?
-
@Skorp
If you own the Viper TQS, is there a DX btn for each position for DF/OVRD/MLM? -
@Skorp
I DO use DX for the HOTAS. -
You can also use the old launcher, make/keep your usual keystroke modifications using the keystrokes editor and finalise under Target. In this case, there’s no problem with press/release, as Target handles this perfectly.
And as for CUT OFF/IDLE it easy too.
Just assign TQS: CUTOFF RELEASE - Idle Detent - Off à QBTN 18 (see picture) with press and TQS: CUTOFF RELEASE - Idle Detent - Idle with release.
But I’ll look later to see if when moving the DF switch to the 3 positions, I get THREE DX btn presses
-
@huffer2 there is an option in config options to implement that.
Sorry, I don’t remember which, look for it
-
@Rouge1512 Thanks
-
@huffer2 sorry, once again I haven’t seen this is a Viper Tqs post
-
Bad news : when moving the DF switch to the 3 positions, you get TWO DX btn presses (7 and 8).
.
But again no PB with TARGET. If you have to change from old launcher, keep in mind that TARGET is much more powerful and user-friendly than AL (and it doesn’t destroy your old .key file that you like as AL does).
-
There will definitely be improvements and bug-fixes for AL coming with U3 (as always, in 3-4 falcon weeks).
I hope it will help folks setup their new Viper TQS, but there’s no ready-made template for it (yet).
As already said, ofc you don’t need AL to do anything. It’s a self-described “Alternative” after all.
If you want to config the 3-way press/release by hand, the magic keyfile syntax will look something like this:
SimSelectSRMOverride 6 -1 -2 0 0x0 -1 SimDeselectOverride 6 -2 -2 0x42 0x0 -1 SimSelectMRMOverride 7 -1 -2 0 0x0 -1 SimDeselectOverride 7 -2 -2 0x42 0x0 -1
(The ‘6’ and ‘7’ correspond to button numbers 7 and 8, respectively… assuming TQS is first device in your DeviceSorting.txt order… add +128 for each row ahead of it…)
You can apply the same trick for the idle-detent back/forward callbacks, if necessary.
-
Thanks.
-
@Skorp said in Viper TQS, using new Alt Launcher vs. the old launcher?:
AB detent doesn’t works
What’s the bug? (seems to work ok for me)
-
@huffer2 There is not a DX for the middle button you must use the button release function to get that to work.
-
@airtex2019 sorry, I’m refereed to my ab detent message post, but is possible I’ve misunderstood your answer 🥴
-
@Rouge1512
Thanks for the checking this out.
BTW, are you using the VIPER TQS ? Did you use AL to assign the DX btns, or just use Target software.
My experience with target is fair. I found it confusing and difficult to work with my HOTAS.
I guess I could work more on learning how to use it if I have no other choice. -
Yes, I’m using the Viper TQS, but unfortunately not with DX : TARGET only.
-
@Rouge1512
That helps me out knowing you have it working with target. -
@huffer2
Did you try the “g_bHotasDgftSelfCancel” options. This one was used with the old TM HOTAS Cougar. May be a solution, but I didn’t try it already.Description provided in BMS technical Manual, in Hardware section of BMS Config User.cfg:
Section: Hardware
Option: g_bHotasDgftSelfCancel
Desc: Dogfight/Missile override Self-CancelFor DX programming joysticks. When enabled the Dogfight/Missile Override callbacks (DGFT/SRM/MRM) will call “override cancel” automatically upon release. This can be used for joysticks like the TM HOTAS Cougar, where the override switch on the throttle is a 3-position switch, but only the 2 outwards positions actually create a DX button input. This option enables the centre position in case of DX programming. If set to disabled, the centre position will need to be programmed with callback. Available options: 0/1.
-
@101-Spyder
Thanks Spyder. Another tip that may be very usful. -