Viper TQS, using new Alt Launcher vs. the old launcher?
-
Need some advice from more experienced BMS users.
Currently I am using 4.37U2, old style Launcher, HOTAS is FSSB/ultra and old Cougar TQS, and multiple goflight modules for various switches and knobs. Saitek Rudders/brakes. TM MFD’s and use RTT to show data.
I have made several key changes to the BMS-Full.key to get my goflight modules to work.
I have saved that keyfile with a new name.
Hotas is assigned with DX.I am considering buying the new Viper TQS from TM. Reading all the post here, I see that now I will need to use the AL.
In the drop down-menu for keyfiles in AL, will I see my modified keyfile in the list?
If so, can I click on it and use it?
I think ,from what I see from YouTube on this topic, I may have to select the BMS-Full key and create a new Auto key. This sound right?Airtex has mentioned in another post that future version of AL may allow using inported keyfiles?
Thanks for anyone taking the time to read this.
Not sure if it is worth the time/expense to mess with my setup just to use the new TQS.
To be able to use the idle detent and AB detent, like the RL F16, is why I am considering this.Huffer out <salute>
-
Hello
Don’t change a thing.
If you’re comfortable with the old system, switching to Alternate launcher will give you nothing more and you’ll spend a lot of time redoing everything for nothing.@huffer2 said in Viper TQS, using new Alt Launcher vs. the old launcher?:
To be able to use the idle detent and AB detent, like the RL F16, is why I am considering this.
You don’t need AL to use the idle cut off and afterburner step with the viper tqs, just like with any other HOTAS with physical stops.
For the cut off you just need to think about this:
-
@Rouge1512
Thank you for for input.
I will hold off for now.pertaining to the “useanalogidlecutoff” , I think what it says is that BMS as the default, uses the red line as the idle cut position when setting up the idle axis in the UI. This is how I see it in my UI. The red line is at the very bottom of the axis. If I set this config value to 1, then BMS will only go to cutoff if the Viper TQS is put in the cutoff position, which activates that btn press in the Viper TQS.
I think what you are saying is you then donot need to use AL for a press/release for cutoff.
But from what I read, there may need to still use a press/release for the DF/MLM/OVRD switch to work.
Anyone who is reading this AND has purchased the Viper TQS, when testing the DX keys in windows/controllers, when moving the DF switch to the 3 positions, do you get THREE DX btn presses? If so, I would think programming the TQS with the old launcher should work.Thanks again for bringing this up.
-
One Big difference for me, in alt Launcher you can assign unpressed dx, i think this is inpossible in old Launcher.
Other difference is the capability to assign axis: in AL you use the axis and It appears in the bix (awaiting input); in old Launcher you have to look for the axis you want yo assign
If you use both you’ll see the diference quickly
-
@Skorp
Are you pleased with the AL? -
@huffer2 AB detent doesn’t works
-
@huffer2 a lot
-
@huffer2 as far i’m made mi pit, for me is the way to configure much if my switches as DX
-
@Skorp I am still tossing around the idea of buying the Viper TQS. Seems like you need AL to get the DL/MLM mode to work
-
@huffer2 if you only need to assign horas as DX, you can make It with new or 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)