Cannot get BMS to Recognize Viper TQS cutoff button
-
The Viper TQS uses button 18 as the throttle cutoff button, but I cannot get BMS to recognize it. I do not have idle detent selected for the throttle axis. My button assignments are as follows:
TQS:CUTOFF RELEASE - Idle Detent - Idle DX18 Release
TQS:CUTOFF RELASE - Idle Detent - Off DX:18I start the mission with the Viper TQS throttle in the Idle cutoff position which should have the throttle in the Idle Detent Off position, but when I enter the cockpit, before starting the engine, the throttle is in the Idle position.
I do not have this issue in DCS, just BMS.
-
This works for me…
-
@Nurse When I go into key mapping, I do not have the option in the Profile drop down window to select BMS -Auto nor in the Category dropdown window is there an option to select HOSTAS THROTTLE as is shown in the video. I’m using the latest version BMS 4.37.
-
I figured out the solution and a bug on the configuration page.
On BMS configuration page there is an option in the Hardware section called “Idle Cutoff” and the description states that checking this box enables the OFF-IDLE throttle position. The description is incorrect. Checking this box disables the OFF-IDLE throttle position.
My throttle idle cutoff now works. Thanks for the help.
-
@RTS0610 said in Cannot get BMS to Recognize Viper TQS cutoff button:
I figured out the solution and a bug on the configuration page.
On BMS configuration page there is an option in the Hardware section called “Idle Cutoff” and the description states that checking this box enables the OFF-IDLE throttle position. The description is incorrect. Checking this box disables the OFF-IDLE throttle position.
My throttle idle cutoff now works. Thanks for the help.
No the option enables a analog Idle position set for a certain point on the throttle axis and disables the use off the idle cutoff button assingments
-
@RTS0610 it’s not a bug, you’re misunderstanding it
-
Just to be clear, for anyone else stumbling upon this – if your throttle device signals a dx button as pressed, when it’s in the cutoff position, and the axes properly report 0% when at the detent… then you probably don’t want to set g_bUseAnalogIdleCutoff in cfg or set an idle-detent in AL/BMS at all – just map the button signal(s) to the command callbacks.
You can define separate press/release invocations, as demonstrated in the youtube video, or you can use the confusingly-labeled callbacks designed specially for this purpose – map these to the dx button numbers that are signalled, when the respective throttle axes are in the cutoff range.
These callbacks shutoff fuel to the left/right engine, when signalled. (viz: if you have a single-axis throttle and only flying single-engine jets, just map the “left” one)
SimThrottleIdleDetentLeft 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF RELEASE - Left Engine" SimThrottleIdleDetentRight 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF RELEASE - Right Engine"
Final thought – for a single-axis throttle device like TQS… if you plan on flying dual-engine jets like F-15 (and want to be able to ramp-start the engines) you will probably not want to do either of those things – in this case, it’s probably best to map keyboard presses to toggle the left/right engine cutoff states.
-
@airtex2019 Thanks for the clarification.
-
Hi have the same problem, as i said in an other post, i had to install a new ssd where i have configured windows 10. So in my last ssd i had not any iusses following video procedure, but now bms can’t find the relase for the idle position