4.34: Enabling Warthog idle detent (without TARGET)
-
Hi folks,
can somebody walk me through enabling the idle detent position in 4.34 on the warthog throttle without resorting to TARGET scripting?
I’m a bit confused about what needs to be set exactly.
o the config editor has an “enable idle detent” entry in the hardware section.
o Moving the throttle from the detent to idle generates a keypress that can be assigned in the setup screen or via keyfile. What function needs to be set here? I’m not seeing a buttonpress event tough when I go over the hump from the idle to the “detent” position. Is this normal?
o do I need to set the “idle detent” position on the throttle axis (right click) for this to work?
When I did some setup tests yesterday I noted that I get a flame out immediately when moving the throttle to “idle”, that went away after enabling the “idle detent” in the configuration editor.
Thanks much in advance & all the best,
Uwe
-
when you enable the idle detent in the config, you actually do not need to use the idle detent keystroke at all
on the other hand you must set the idle point on the UI controller throttle axis, just as the same way as you assign the AB detent, but you do that with the other mouse button.
You end up with a red line and a green line on your throttle axis, one is the AB spot, the other is the idle spotObviously for that to work you need a mechanical stop in your throttle course to stop your throttle at both relevant points
if you Don’t have a mechanical stop at the idle point you will shut donw your engine in flight everytime you moive the throttle further down than the set idle point.Check BMS technical manual chapter 13 (hardware section)
Dash-1 pg 28 -
There is no easy way without Target currently as Warthog idle cutoff position is actual button not part of analog axis like on Cougar.
I have Warthog as well so I added new momentary Cutoff keystroke that can be mapped to Warthog throttle cutoff. Lets see if it finds way into 4.34 U1. As bonus also Throttle and Stick Warthog POVs can be used and mapped as well with little setting via falocon cfg variables that I added as well. As default Falcon can only use POVs on flight device - that is Warthog stick and can’t map POV on separate throttle device. Now it will be possible.
-
Thanks RD! The warthog has such a stop for the throttle in the “idle” position, you have to lift it over a “hump” and then the throttle settles down in the “detent” position.
However I’m not seeing movement on the throttle axis display when the the throttle is in “detent”, so I guess, I’d have to move the throttle all the way back (until I would have to lift it over the hump) and assign the “idle” position there?
Cheers,
Uwe
-
Yes, because past cutoff, Warthog throttle axis reads always zero and cutoff is indicated by pressed Warthog idle buttons (and that you will map to new Cutoff momentary keystroke so as long as throttle is held in cutoff position throttles in-game will be in cutoff as well). I read there is some way to enable analog axis beyond that cut off with some calibration trickery but I recommend wait for U1.
I will try record demo of this new features for Warthog owners when arrive home today.
TBH I never though about this until I got Warthog (had X52 before that has physical idle detent as part of throttle axis) recently and was in same dead-end with cutoff a POVs like you.
-
Thanks ataribaby, looking forward to your demo!
uwe
-
There are 2 callbacks already that split in 2 the ‘alt-i’ callback : one acts as if it goes from IDLE to OFF and the other from OFF to IDLE.
If you couple that with assigning a callback at a DX button press and another callback at the same DX button release (as described in the keyfile manual), you can use the DX button used by the warthog OFF DX button. However, I think it will only work for single engine operations.
I don’t have the name of the callbacks right there but that should do the trick.
-
There are 2 callbacks already that split in 2 the ‘alt-i’ callback : one acts as if it goes from IDLE to OFF and the other from OFF to IDLE.
If you couple that with assigning a callback at a DX button press and another callback at the same DX button release (as described in the keyfile manual), you can use the DX button used by the warthog OFF DX button. However, I think it will only work for single engine operations.
I don’t have the name of the callbacks right there but that should do the trick.
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”See three in there but haven’t had time to play with them.
-
Yep I saw em Cruz, they should work for selected engine combination.
I just added momentary new cutoff keystroke for each engine that ca be mapped via in-game controls setup.
-
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