4.34: Enabling Warthog idle detent (without TARGET)
-
Where can I find that AL keymapping? do you mean the setup, controllers menu?
-
AL = Alternative Launcher
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases
Highly recommended
-
Good Day, All,
I wanted to share something I just set up that addresses this issue, using the BMS alternate launcher.With many thanks to those who got me pointed in the right direction with this.
-1) put throttles at idle position( just forward of the the rear physical detent)
2) in the AL go to keymapping ,then to TQS:CUTOFF RELEASE-Idle Detent-off. It’s about 1/3 down the list. Left click on it. On the little window that appears , press Invoke both until it changes to “invoke keydown”. The inner window should day “awaiting input” .Pull the throttles fully aft over the hump, and the AL will give it a dx assignment.Mine is 29, and the command looks like DX29 INV DN… Click Save and put throttles back to idle’
3) Now go to TQS:CUTOFF RELEASE-Idle Detent-idle. Left click on it, Select “release” and “invoke keydown”. Pull the throttles full aft to off. It will give it another Dx assignment, looking like Dx29 REL INV DN. Click Save
And that it.
NOTES:1) I don’t know if your setup will give you the same Dx number on not, but be sure the commands look like what I wrote above(ie: DX## INV DN and Dx## REL INV DN)
2) Normally in the AL, when you press a switch or button you’ve set up. it will go to that command on the list. It does not do that for these idle commands, but I’ve tested it twice. It does work in the cockpit, and seems stable.
Enjoy!
Update: I should mention that I’m using the BMS Full keyfile. That’s the one, apparently, that AL works withI think there has been a change to the most recent Alternative Launcher release. It no longer has the option of “Invoke both/keydown” (for me at least).
Instead in Step 2, select “Press”
In Step 3, select “Release” -
Good Day, All,
I wanted to share something I just set up that addresses this issue, using the BMS alternate launcher.With many thanks to those who got me pointed in the right direction with this.
-1) put throttles at idle position( just forward of the the rear physical detent)
2) in the AL go to keymapping ,then to TQS:CUTOFF RELEASE-Idle Detent-off. It’s about 1/3 down the list. Left click on it. On the little window that appears , press Invoke both until it changes to “invoke keydown”. The inner window should day “awaiting input” .Pull the throttles fully aft over the hump, and the AL will give it a dx assignment.Mine is 29, and the command looks like DX29 INV DN… Click Save and put throttles back to idle’
3) Now go to TQS:CUTOFF RELEASE-Idle Detent-idle. Left click on it, Select “release” and “invoke keydown”. Pull the throttles full aft to off. It will give it another Dx assignment, looking like Dx29 REL INV DN. Click Save
And that it.
NOTES:1) I don’t know if your setup will give you the same Dx number on not, but be sure the commands look like what I wrote above(ie: DX## INV DN and Dx## REL INV DN)
2) Normally in the AL, when you press a switch or button you’ve set up. it will go to that command on the list. It does not do that for these idle commands, but I’ve tested it twice. It does work in the cockpit, and seems stable.
Enjoy!
Update: I should mention that I’m using the BMS Full keyfile. That’s the one, apparently, that AL works withOK, I’m a BMS newbie in controller hell.:mad2: Was able to ramp start without issue a month ago. Now I’m revisiting the sim and get a hot start every time.
I have a TM Warthog joystick/throttle (plus Logitech rudder). Windows 10 Pro. The Windows joystick control dialog shows the Warthog working fine (axes and buttons).
Currently, I’m using the Warthog without any TARGET file/script running.
I’ve got the “BMS - Full.key” file selected (the controller setup page in the native BMS application shows this as the loaded keyfile).
I’ve configured the controllers using the Alternative Launcher (“AL”). I can set the idle detent in the AL axis assignment set-up for the TQS. Operation appears correct; when the throttle is in the cutoff area, the axis bar says “idle cutoff” and when the throttle is pushed forward past the detent, the axis bar appears to increment/decrement smoothly. Nonetheless, I still get a hot start.
I’ve also tried removing the idle detent from the axis assignment and using the keymapping approach outlined in your post instead. I think I’ve got it right. The KeyMapping display says “DX29 RELEASE” for the “Idle Detent - Idle” callback, and “DX29” for the “Idle Detent - Off” callback. Again, I can verify in the Windows diagnostic dialog for the throttle that DX29 and DX30 are both pressed when the throttle is in the cutoff area, and that the two buttons are not pressed when the throttle is pushed forward of the idle detent.
Despite the apparently correct keymapping, I still get a hot start. I’ve also tried both foregoing approaches simultaneously (i.e., assigning idle detent in the AL Axis Assignment feature AND using the keymapping). No luck.
And just to rule out other things, I’ve been using an abbreviated startup procedure:
Ensure throttle in cutoff position;
ENG FEED–>NORM;
MAIN PWR–>BATT;
AIR SOURCE–>NORM;
MAIN PWR–>MAIN PWR;
Close canopy
JET FUEL–>START2
Yet, when engine RPM reaches ~15%, FTIT increases past 700deg, and even moving throttle back to idle cutoff doesn’t help.
As an initial thought, I think the sim may start me with the throttle in the idle position; not cutoff position. Would this cause the overheat condition (feeding a bit of fuel to the engine before 20% RPM is attained?)
Should the virtual throttle image in the cockpit move forward a bit when the Warthog throttle is moved from cutoff to idle? The virtual throttle does move when I move the Warthog throttle from idle to AB, but it does not move when I transition the Warthog from cutoff to idle.Also, I certainly mucked around with setting the idle detent in the native BMS app (i.e., not AL) when I was previously attempting to set up my controllers. Is there some hidden setting somewhere that needs to be undone?
Sorry for the long post. Any ideas would be appreciated.
-
Good Day, All,
I wanted to share something I just set up that addresses this issue, using the BMS alternate launcher.With many thanks to those who got me pointed in the right direction with this.
-1) put throttles at idle position( just forward of the the rear physical detent)
2) in the AL go to keymapping ,then to TQS:CUTOFF RELEASE-Idle Detent-off. It’s about 1/3 down the list. Left click on it. On the little window that appears , press Invoke both until it changes to “invoke keydown”. The inner window should day “awaiting input” .Pull the throttles fully aft over the hump, and the AL will give it a dx assignment.Mine is 29, and the command looks like DX29 INV DN… Click Save and put throttles back to idle’
3) Now go to TQS:CUTOFF RELEASE-Idle Detent-idle. Left click on it, Select “release” and “invoke keydown”. Pull the throttles full aft to off. It will give it another Dx assignment, looking like Dx29 REL INV DN. Click Save
And that it.
NOTES:1) I don’t know if your setup will give you the same Dx number on not, but be sure the commands look like what I wrote above(ie: DX## INV DN and Dx## REL INV DN)
2) Normally in the AL, when you press a switch or button you’ve set up. it will go to that command on the list. It does not do that for these idle commands, but I’ve tested it twice. It does work in the cockpit, and seems stable.
Enjoy!
Update: I should mention that I’m using the BMS Full keyfile. That’s the one, apparently, that AL works withOK, I’m a BMS newbie in controller hell.:mad2: Was able to ramp start without issue a month ago. Now I’m revisiting the sim and get a hot start every time.
I have a TM Warthog joystick/throttle (plus Logitech rudder). Windows 10 Pro. The Windows joystick control dialog shows the Warthog working fine (axes and buttons).
Currently, I’m using the Warthog without any TARGET file/script running.
I’ve got the “BMS - Full.key” file selected (the controller setup page in the native BMS application shows this as the loaded keyfile).
I’ve configured the controllers using the Alternative Launcher (“AL”). I can set the idle detent in the AL axis assignment set-up for the TQS. Operation appears correct; when the throttle is in the cutoff area, the axis bar says “idle cutoff” and when the throttle is pushed forward past the detent, the axis bar appears to increment/decrement smoothly. Nonetheless, I still get a hot start.
I’ve also tried removing the idle detent from the axis assignment and using the keymapping approach outlined in your post instead (including Pegasus82’s point about the updated AL functionality). I think I’ve got the keymapping right. The KeyMapping display says “DX29 RELEASE” for the “Idle Detent - Idle” callback, and “DX29” for the “Idle Detent - Off” callback. Again, I can verify in the Windows diagnostic dialog for the throttle that DX29 and DX30 are both pressed when the throttle is in the cutoff area, and that the two buttons are not pressed when the throttle is pushed forward of the idle detent.
Despite the apparently correct keymapping, I still get a hot start. I’ve also tried both foregoing approaches simultaneously (i.e., assigning idle detent in the AL Axis Assignment feature AND using the keymapping). No luck.
And just to rule out other things, I’ve been using an abbreviated startup procedure:
Ensure throttle in cutoff position;
ENG FEED–>NORM;
MAIN PWR–>BATT;
AIR SOURCE–>NORM;
MAIN PWR–>MAIN PWR;
Close canopy
JET FUEL–>START2
When engine RPM reaches ~15%, FTIT increases past 700deg, and even moving throttle back to idle cutoff doesn’t help.
As an initial thought, I think the sim may start me with the throttle in the idle position; not cutoff position. Would this cause the overheat condition (feeding a bit of fuel to the engine before 20% RPM is attained?)
Should the virtual throttle image in the cockpit move forward a bit when the Warthog throttle is moved from cutoff to idle? The virtual throttle does move when I move the Warthog throttle from idle to AB, but it does not move when I transition the Warthog from cutoff to idle.Also, I certainly mucked around with setting the idle detent in the native BMS app (i.e., not AL) when I was previously attempting to set up my controllers. Is there some hidden setting somewhere that needs to be undone?
Also, I should note that this is occurring in “Training Mission 1: Ground Ops”, so it’s the F-16B.
Sorry for the long post. Any ideas would be appreciated.
-
Hm, it sounds like your throttle is in the idle position when you enter the jet.
Have you tried clicking on the hook on the virtual throttle in 3d? This should definitely move the virtual throttle back into the correct cutoff position, and this should also be visible in the 3d cockpit.
All the best,
Uwe
-
Hm, it sounds like your throttle is in the idle position when you enter the jet.
Have you tried clicking on the hook on the virtual throttle in 3d? This should definitely move the virtual throttle back into the correct cutoff position, and this should also be visible in the 3d cockpit.
All the best,
Uwe
Thanks for the quick response. Clicking the throttle hook didn’t work (good idea, though….I hadn’t even thought of that!). However, I did manage to find the problem. In the configurator app (the “Config” tool that you can launch via the AL or via the native BMS startup screen), I had previously ticked the “Idle Cutoff” box under the “Hardware” settings. I guess that was conflicting with the keymapping via AL. In any event, I unticked that box, and the FTIT gauge and I are good friends again.:drink:
Thanks again!
-
Good to hear you managed to fix the issue. I have made that mistake too, btw (enabling idle cutoff in the BMS config tool :))
All the best & clear skies!
Uwe
-
I think there has been a change to the most recent Alternative Launcher release. It no longer has the option of “Invoke both/keydown” (for me at least).
Instead in Step 2, select “Press”
In Step 3, select “Release”Thx for this Pegasus, you are exactly right. I thought I’d revisit this thread when I saw what you wrote what about the 2 DX assignments for “OFF” . Mine are 29( Right ) and 30(left). I had set them up that way because at the time I was trying to give myself the capability to start and stop the engines individually. Mainly, to start the right first, as in RL. Unfortunately, it doesn’t work. It must be a BMS “it’s a Viper thing”. There are not individual left and right cutoffs. Also, you can set either 29 or 30 to idle, but not both. My Idle is on the right. In the cockpit, even if you only move the right throttle, both engines start.
Has anyone by chance figured out a way to do this?
BTW, Paladin, don’t feel bad, I had the same issue way back when. -
Check this as it’s a possible solution. https://www.benchmarksims.org/forum/showthread.php?34805-WH-Throttle-functionality-some-may-not-know-about&p=556564#post556564