Hotstarts With Viper TQS
-
Hello everyone,
I have been working for two days now to get my new Viper TQS to properly do the startup sequence. Here is the situation:- Fresh install of BMS 4.37U3 (FULL)
- Running Win 11 on a brand-new PC
- Viper TQS installed properly, shows complete operation in Windows Control Panel. Virtual Buttons Active. Buttons DX18 (Idle Detent) and DX 19 (Afterburner Detent) work correctly.
- Programming keyfile using Alternative Launcher (AL). My first time using AL.
- In BMS.cfg, via AL, I have in Hardware: “Idle Cutoff” checked and installed.
- Using the following Peripherals:
- HOTAS Cougar Stick/Elite Rudder Pedals (Joystick 3)
- Viper TQS (Joystick 4)
- Simgears ICP (Joystick 0)
- TM MFDs (Left = Joystick 2, Right = Joystick 1)
- DED/FFI (DeDuino)
- Here are the key assignments for the Idle Detent/Cutoff and Axis Assignment (full AB):
Note: Keys SHIFT+i assigned to Idle and CTRL+i to OFF.
-
In AL, when throttle moved from Idle to Cutoff, AL shows: DX18: Viper TQS / TQS:Cutoff Release - Idle Detent - Off"
-
In AL when moved from Cutoof to Idle, AL shows: DX18: Viper TQS / TQS:Cutoff Release - Idle Detent - Idle"
-
In BMS Setup\Controls page, when moving throttle from Idle to Cutoff, shows:
Note the movement input (DX18) shows input to Idle Detent - Off (as expected).
-
In BMS, when entering 3D in flight, Throttle motion works fine to control the engine. AB works fine as well. However, Moving the throttle from Idle to CutOff while in flight, using Viper TQS has no effect on the engine (which should shut down when this occurs). It is as though the sim is not sensing DX18 command.
-
In BMS when doing a ramp start, using the following procedure:
- Master Fuel NORM, EPU OFF, Air NORM, Throttle in CutOff
- Batt STBY - Test - Batt to MAIN
- Lower Canopy and Spider Lock
- Set ext lights, radios, Park Brake, Int Panel Lights, Anti-Ice ON
- JFS: START 2
(I’ve done hundreds of Ramp Starts in U@ and earlier while testing VCC4BMS, and never once saw a hot start)
I see the JFS light on, Elec lights doing what they should, RPMs and FTIT begin to rise, but instead of steadying out at about 25% RPM and around 450 deg F FTIT, FTIT continues to climb and hot start occurs. It is as though BMS is not sensing that the throttle is in CutOff at all.
Moving the throttle to idle at this point does nothing to stop the HotStart from occurring.
I have also tried taking out the DX18/DX18 Release assignments, and just using assigned keys (Keys SHIFT+i assigned to Idle and CTRL+i to OFF), and the result was the same - a hot start on the RampStart (neither Alt+i nor Shift+i resulted in setting throttle from OFF to IDLE), and failure to shut down the engine in flight when selecting CTRL+i.
I know this must be a setting issue or a config issue because the throttle does function smoothly during flight, and indicates normally in Windows Control Panel. I am baffled as to why BMS does not seem to be responding to the DX18/DX18 Release pulses from the throttle or the keys.
Only thing I can think to do at this point is uninstall 4.37U2 and reinstall it, importing the AUTO keyfile to avoid having to plug everything in back to AL again. I am trying to avoid that if possible.
Sure would appreciate any suggestions from anyone as to what I might be missing (@r00t , @airtex2019 , @Echo ). Thanks in advance,
Tomcattwo
(VoiceClone) -
@Tomcattwo try
set g_bUseAnalogIdleCutoff 0
in user cfg? -
@Tomcattwo
I am baffled also. -
In Config the idle cutoff should be inactive (unticked). It is not for the TM Viper TQS, but for throttles that the axis goes below idle. In our throttle, cutoff is a switch, so your key assignment you have should do the job, as it does for me.
It looks strange though that the AB works in your setup, since it does not seem set correctly to me (in the AL, ingame looks ok). -
@skippermike
Thanks for the reply. I thought I tried that during my flailing around so far but I will sure give it another shot.
R/
TC2 -
@airtex2019
Thanks Airtex219. I’ll give that a go also. I think that line is in BMS.cfg, but it won’t hurt to try it in User.cfg.
R/
TC2 -
@skippermike
I owe you a cold one, shipmate!
After taking the Idle Cutoff out of BMS.cfg (via AL) I was able to complete a proper engine start!!You have saved me from a trip to the funny farm, as this was driving me nuts (particularly the thought that maybe the Viper TQS needed to be RMA’d).
Re: Afterburner - the detent is set correctly. The screenie I took of the Axis Setting had the throttle itself all the way into afterburner (Nozzle full open). In AL, it shows up as that green bar with “Afterburner” in it once the throttle is past the afterburner detent. Works fine in game.
I GREATLY appreciate that you took the time to share this solution with me!
Mark this one "Solved’!
Regards,
Tomcattwo
(VoiceClone) -
@Tomcattwo
YIPEE!! -
@Tomcattwo thanks for followup – one could easily argue AL should be settings this cfg flag, properly, on your behalf – based on whether you set an idle-detent on your throttle axis or not.
I’ll add that to the backlog.
-
Great testing i could add this info to the “Quickstart guide”
-
@Echo said in Hotstarts With Viper TQS:
Great testing i could add this info to the “Quickstart guide”
Echo, great idea to add in the quickstart guide to ensure Idle Detention in configuration hardware is unticked.
Regards,
TC2 -
Hey,
I used AL to map the idle detent then edit my .key file to add the two lines created.
In my case with set g_nButtonsPerDevice 64 and my TQS in second position in the DeviceSorting.txt i add this two lines :
SimThrottleIdleDetentBack 81 -1 -2 0 0x0 314
SimThrottleIdleDetentForward 81 -2 -2 0x42 0x0 314Works fine for me,
I hope this could help !