4.34: Enabling Warthog idle detent (without TARGET)
-
Here is video of momentary cutoff keystroke and two POVs on separate Warthog devices.
-
These are good callback additions. Since left default cutoff button for left throttle is I think #31 then key file would look something like:
SimThrottleIdleDetentBack 30 -2 -2 0 0x0 -1
SimThrottleIdleDetentForward 30 -2 -2 0x42 0x0 -1When button 30 (e.g. #31) is pressed it goes to cutoff. When button 30 is release (0x42) then it goes from cutoff. I haven’t tried it though.
-
Anyone who has a Warthog throttle and wants to be able to utilize the idle detent on the throttle to start and stop the jet should do this. It works well!!! Funny that its a link already in BMS forum but a little buried. Maybe this should get a sticky!! It is very useful
https://www.benchmarksims.org/forum/printthread.php?t=34805&pp=10&page=1
-
If your Warthog throttle is the second DX device in devicesorting.txt:
SimThrottleIdleDetentBack 60 -2 -2 0x0 0 “TQS: CUTOFF RELEASE - Idle Detent - Off”
SimThrottleIdleDetentForward 60 -2 -2 0x42 0x0 0 “TQS: CUTOFF RELEASE - Idle Detent - Idle”Works like a charm, don’t even need to warm up the throttle, start in the off position with the throttle all that back over the hump, just slide it to 50% and back when ready to start.
Idle Detent needs to be turned OFF in the Hardware section of BMS Configuration.Haven’t had a hot start since setting this up.
If only we could get BMS to recognize the POV hat on the throttle we could have a full DX setup on the throttle.
-
I managed to solve my issue, too. Will try the IdleDetendBack thing as well!
Uwe
o DISABLE the HW “idle detent” in the configurator
o Make sure the throttle is in “idle detent” position before switching on anything (clicking on the little hook on the throttle in the 3d pit)
o map the physical button on the throttle when moving over the hump to the IdleDetentForward function
SimThrottleIdleDetentForward 61 2 -2 0 0x0 0 “Throttle Warthog : TQS: CUTOFF Release”
o start up the jet normally
o once RPM reaches 20% and FTIT is nominal move the phys. throttle over the hump -
PS: Will I have to re-enable the Hardware idle cutoff patch? I have it disabled at the moment.
thanks,
Uwe
-
PS: Will I have to re-enable the Hardware idle cutoff patch? I have it disabled at the moment.
thanks,
Uwe
Kept mine disabled and it’s working as it should.
You can use either dx 60 or 61 since there 2 cutoffs left/right on the throttle. -
PS: Will I have to re-enable the Hardware idle cutoff patch? I have it disabled at the moment.
thanks,
Uwe
No, idle cutoff option is when you want to control throttle off position by axis position. These callbacks to change state is not axis control so you don’t want the idle cutoff option enabled.
-
Hi.
I`ve been following this thread trying different setting finally got it to work perfectly by adding :-
SimThrottleIdleDetentBack 61 -2 -2 0 0x0 -1
SimThrottleIdleDetentForward 61 -2 -2 0x42 0x0 -1
SimThrottleIdleDetentForward 314 0 0XFFFFFFFF 0 0 0 1 “TQS: CUTOFF RELEASE - Idle Detent - Idle”
SimThrottleIdleDetentBack 314 0 0XFFFFFFFF 0 0 0 1 “TQS: CUTOFF RELEASE - Idle Detent - Off”
Idle Cutoff off in config.
Thanks for all the help
Mick Worsnup -
Found this thread by chance and it’s appreciated !!!
What I don’t understand is why the throttle back written in the Kolbe xls and the throttle forward is not.
All one needs to do is add the callback backward in the xls file at its assigned ready location and copy paste manually only the forward callback.One data to note…the sound file used is 314 and not -1 (the last number in the code).
Thanks again !
-
Sorry to have to dumb this down, but I am not the sharpest knife in the drawer….
Would anybody be willing to combine all of this info on this post into a simple “step-by-step” instruction on how to make this work?
I have a TM Warthog.
When I slide the throttle back and up over the “hump” it registers as a button in the game setup as button 93.
I push it forward and pull it back to bring it back over the hump again, it registers it as button 94.So I see the game recognizes the lift of the throttle, but what I don’t understand is which “TQS Detent” action/command it should be assigned for those two keys.
PLEASE - if you could guide me through this with instructions and specific “Button Assignment” to the specific “Action” I would be most grateful.
Thanks,
Fubar -
It shouldn’t. There are two throttle buttons one for each throttle lever. They are buttons 29 and 30 for the right and left handle respectively. Be careful that you aren’t moving both handles locked together since you will be pressing and releasing these two buttons almost but not exactly at the same time. So separate the two handles and I recommend only binding the left one to the first and only engine of the F-16 (for dual engine operations set up the right handle for the second engine).
First, bind the “move to shutoff” command to the left handle button (30, although it will be 29 in the key file because button 1 is “0”). Once that is done you have to edit the .key file manually to assign the “move to idle” callback to the release context of button 29. It is impossible to do this or see that it has been done from within the game itself. This can be done by copying the line for “move to off” then inserting a line return, pasting the text into this new line, then editing the context and callback parts of your copied text to finalize the second line.
Example:
Find the callback and bind for the button 29 made from within the game
SimThrottleIdleDetentBack 92 -2 -2 0 0x0 -1Copy that line to create a duplicate
SimThrottleIdleDetentBack 92 -2 -2 0 0x0 -1
SimThrottleIdleDetentBack 92 -2 -2 0 0x0 -1Edit the second line to activate on button release
SimThrottleIdleDetentBack 92 -2 -2 0 0x0 -1
SimThrottleIdleDetentBack 92 -2 -2 0 0x42 -1Edit the second line to invoke the correct callback
SimThrottleIdleDetentBack 92 -2 -2 0 0x0 -1
SimThrottleIdleDetentForward 92 -2 -2 0 0x42 -1If you load a key file in the game in this way and then save it, the act of saving will erase all of these release lines or any comments. So be careful using the save button if you have any lines which BMS UI cannot understand.
-
Thank you Frederf - this is clear and easy to understand. For the record, I the “aha” moment was realizing the Warthog I have has always been locked with the two throttles. Understanding now that Left and Right Throttles are mapped as two different “Buttons” as seen in the Setup==>Controllers page of BMS made it all clear to me.
I have it working now and it is a beautiful thing….thank you! -
Frederf - Just as an FYI and perhaps you can tell me if this is right or wrong…or perhaps it is duplicated, but this is where all the “Detent” settings are located in my keymap file:
Line 292: SimThrottleIdleDetent 314 0 0X17 4 0 0 1 “TQS: CUTOFF RELEASE - Idle Detent - Toggle”
Line 293: SimThrottleIdleDetentForward 314 0 0XFFFFFFFF 0 0 0 1 “TQS: CUTOFF RELEASE - Idle Detent - Idle”
Line 294: SimThrottleIdleDetentBack 314 0 0XFFFFFFFF 0 0 0 1 “TQS: CUTOFF RELEASE - Idle Detent - Off”
Line 1166: SimThrottleIdleDetent 82 8 -2 0 0x0 -1
Line 1171: SimThrottleIdleDetent 88 8 -2 0 0x0 -1
Line 1175: SimThrottleIdleDetent 92 8 -2 0 0x0 -1
Line 1176: SimThrottleIdleDetentBack 93 8 -2 0 0x0 -1
Line 1177: SimThrottleIdleDetentBack 95 8 -2 0 0x0 -1 -
Since you’re using the forward/back callbacks you don’t need the toggle idle detent (and certainly not 3 of them). You probably don’t want any DX binds for the toggle detent (82, 88, 92). So I’m suggesting erasing lines 1166, 1171, 1175, and then editing 1176 & 1177 like so:
SimThrottleIdleDetent 314 0 0X17 4 0 0 1 “TQS: CUTOFF RELEASE - Idle Detent - Toggle”
SimThrottleIdleDetentForward 314 0 0XFFFFFFFF 0 0 0 1 “TQS: CUTOFF RELEASE - Idle Detent - Idle”
SimThrottleIdleDetentBack 314 0 0XFFFFFFFF 0 0 0 1 “TQS: CUTOFF RELEASE - Idle Detent - Off”
SimThrottleIdleDetentForward 93 8 -2 0 0x42 -1
SimThrottleIdleDetentBack 93 8 -2 0 0x0 -1Button 95 is Button 32 on the 3rd controller which I think is Right Engine Ignition on the Warthog which you probably don’t want as a duplicate. As you see I’ve changed “93” (button 30, 3rd device) to be detent back when pressed and detent forward when released (0X42).
-
For those of us using the alternative launcher:
(I turned off the hardware idle in the config)
-
For those of us using the alternative launcher:
(I turned off the hardware idle in the config)
I think your attachment’s borked
-
I think your attachment’s borked
Yeah most of the attachments I have seen in other posts are as well. Lets try it this way:
-
If your Warthog throttle is the second DX device in devicesorting.txt:
SimThrottleIdleDetentBack 60 -2 -2 0x0 0 “TQS: CUTOFF RELEASE - Idle Detent - Off”
SimThrottleIdleDetentForward 60 -2 -2 0x42 0x0 0 “TQS: CUTOFF RELEASE - Idle Detent - Idle”Works like a charm, don’t even need to warm up the throttle, start in the off position with the throttle all that back over the hump, just slide it to 50% and back when ready to start.
Idle Detent needs to be turned OFF in the Hardware section of BMS Configuration.Haven’t had a hot start since setting this up.
If only we could get BMS to recognize the POV hat on the throttle we could have a full DX setup on the throttle.
Sorry for necromancing the thread, only got around to trying this now.
I’ve now mapped button 61 to move the throttle into cutoff when going backwards over the hump and to IDLE when going forward over the hump. So far, so good, the throttle now correctly reflects those positions.
However the problem is I cannot move the throttle forward any more; whenever I move it forward from idle the 3d handle in the pit goes forward a tiny bit and then immediately jumps back to the idle position. The throttle axis is correctly assigned and works fine in the setup screen.
I’ve tried reversing the DX lines like so and as suggested above:
SimThrottleIdleDetentBack 60 -2 -2 0 0x0 0
SimThrottleIdleDetentForward 60 -2 -2 0x42 0x0 0which allows me to see the correct axis movement of the handle in the 3d pit, however when I pull the throttle back to “IDLE” it immediately jumps all the way back to the CUTOFF position (while the physical throttle is still in the IDLE position). I’ve verified “idle cutoff” is disabled in the config editor.
Do I need to assign any other “IDLE” or “CUTOFF” dx functions?
Thanks in advance and all the best,
Uwe
EDIT @Frederf: Are you saying that you don’t have your two throttle handles locked together on the Warthog when using it in BMS?
EDIT2: these are all the lines with throttle & detent in my keyfile I’m working on right now:
$ grep Thrott hoover20191117.key | grep Det | sort
[font]SimThrottleIdleDetent 279 8 -2 0 0x0 314[/font] [font]SimThrottleIdleDetent 314 0 0X17 4 0 0 1 "TQS: CUTOFF RELEASE - Idle Detent"[/font] [font]SimThrottleIdleDetent 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF RELEASE - Idle Detent"[/font] [font]SimThrottleIdleDetentBack 60 -2 -2 0 0x0 0[/font] [font]SimThrottleIdleDetentBack 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF RELEASE - Idle Detent - Off"[/font] [font]SimThrottleIdleDetentForward 60 -2 -2 0x42 0x0 0[/font] [font]SimThrottleIdleDetentForward 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF RELEASE - Idle Detent - Idle"[/font] [font] [/font]
-
Handles locked in use. I only mean to treat them separately when doing setup to keep button events separate.
What you’re doing looks good. I would review joystick output behavior outside the game environment. Then I would break down the issue into small parts. Have just the axis bound and operate the forward back callbacks by keyboard. Start simple and what functions changing only one thing at each step.