How to Idle-detent on the TM warthog?
-
So I made a very good (for me) profile for my new warthog. It’s a mesh of a TARGET profile for the throttle (so I can use all the buttons) and the normal DX mappings I did directly in the falcon UI for the stick.
I’m only stuck with the idle detent part.
The throttle has no axis response past the idle detent, but it acts as a DX button. For now I set the DX detent correctly, and I can hear it “clicking” when I move the Warthog throttle past the detent, but the engine doesn’t start.
Any ideas on how to set it up so it works properly? Where should I set the idle detent in the UI?Thanks
-
So I made a very good (for me) profile for my new warthog. It’s a mesh of a TARGET profile for the throttle (so I can use all the buttons) and the normal DX mappings I did directly in the falcon UI for the stick.
I’m only stuck with the idle detent part.
The throttle has no axis response past the idle detent, but it acts as a DX button. For now I set the DX detent correctly, and I can hear it “clicking” when I move the Warthog throttle past the detent, but the engine doesn’t start.
Any ideas on how to set it up so it works properly? Where should I set the idle detent in the UI?Thanks
What is the detent setting set to in the launcher config options (F4 patch)? If you have it set so you don’t need to press alt + i, then you need to ensure the detent option is ticked in there. Then, within BMS, I think you need to set the software detent location to where you have your physical detent set to.
-
There’s a dx button there when you pull the warthog all the way back. I haven’t actuated it to anything yet, but you might need target to recognize when it is /not/ pressed… and on the un-press event, give keystroke at i, if that makes sense.
Something I have been thinking about but haven’t done yet -
You might want to download Morphine’s Target script and see how it’s done in that one, I use it and have no issues with idle detent on it.
IIRC, you move throttle to the idle position, and in the control setup right click on the Set AB for the throttle and it will set the idle cutoff.
Once you move above it the engine should spool up. Like Planehazza stated, you need to check the idle detent option in BMS configuration. -
you need to check the idle detent option in BMS configuration.
The launcher config (check box for enable hardware idle iirc), AND ensure you have right clicked to set the red “line” on the throttles UI. (been awhile and computer is offline at the moment if someone can make that description a little clearer, much appreciated)
-
This post is deleted! -
The launcher config (check box for enable hardware idle iirc), AND ensure you have right clicked to set the red “line” on the throttles UI. (been awhile and computer is offline at the moment if someone can make that description a little clearer, much appreciated)
Yea I was off the gaming PC at the time too.
The actual config setting you need to check the box is under “Hardware”, and is labeled as “Idle Cutoff”/
Then go into the sim, and configure the idle point by setting the throttle hardware to the idle point, and then right click on the throttle bar that same as you would for setting the afterburner point. If done correctly there will be a red line at the idle point. -
+1 for Morphine’s script, it works perfectly fine. DL it and look for yourslef how he did it
-
So I made a very good (for me) profile for my new warthog. It’s a mesh of a TARGET profile for the throttle (so I can use all the buttons) and the normal DX mappings I did directly in the falcon UI for the stick.
I’m only stuck with the idle detent part.
The throttle has no axis response past the idle detent, but it acts as a DX button. For now I set the DX detent correctly, and I can hear it “clicking” when I move the Warthog throttle past the detent, but the engine doesn’t start.
Any ideas on how to set it up so it works properly? Where should I set the idle detent in the UI?Thanks
Here is the post where I described the how/why of the idle detent using the TARGET software:
-
I wrote my script to adjust the throttle axis to 0 and the working range of the axis is 4-100%. Pressing the off button trims the axis value to 0% and that is enough below the cutoff range to trigger the off behavior.
You may ask why not 1% 2% 3%, why 4%? Well I tried those and found that 4%->0% was the smallest jump possible that triggered the behavior. If I tried to make it 1%->0% the engine remained off despite being below the line.
-
I used the Target GUI to make it work. I think it’s close to what it should be but not to sure. But it does work. I set the Alt i comand with a delay of .5 sec. Just enough time so you get the throttle over the detent and a little past idle before you here the ‘tick’ that you here when the key press.is made. It works but not sure if it’s correct. Starts the engine though. And shuts it down when pulled back over the detent.
-
I used the Target GUI to make it work. I think it’s close to what it should be but not to sure. But it does work. I set the Alt i comand with a delay of .5 sec. Just enough time so you get the throttle over the detent and a little past idle before you here the ‘tick’ that you here when the key press.is made. It works but not sure if it’s correct. Starts the engine though. And shuts it down when pulled back over the detent.
There is no need to use the artificial Alt-I with a TH WH. Just use either Morphine’s profile or do like I did and blatantly steal the code to plug it into your own .tmc file. The code works 100% to simulate what you would be doing in the real aircraft to start or stop the engine.
-
I used the Target GUI to make it work. I think it’s close to what it should be but not to sure. But it does work. I set the Alt i comand with a delay of .5 sec. Just enough time so you get the throttle over the detent and a little past idle before you here the ‘tick’ that you here when the key press.is made. It works but not sure if it’s correct. Starts the engine though. And shuts it down when pulled back over the detent.
//Both throttle axes are 4%-100% w/ detent pause, 0% in OFF. MapAxis(&Throttle, THR_LEFT, DX_THROTTLE_AXIS); //THROTTLE AXIS (Throttle) SetCustomCurve(&Throttle, THR_LEFT, LIST(0,4, 65,90, 75,90, 100,100)); MapKey (&Throttle, IDLELON, EXEC("TrimDXAxis(DX_THROTTLE_AXIS, 82);")); MapKeyR (&Throttle, IDLELON, EXEC("TrimDXAxis(DX_THROTTLE_AXIS, SET(0));"));
Here’s a different way to do this only with axis values (idle detent config is set, cutoff line is set). The throttle minimum is 4% but pressing the IDLEON trims 82 points off the axis value (82/2048ths ~4%) and releasing IDLEON removes this trim. There’s also a pause between 65-75% input so the mechanical afterburner range doesn’t prevent setting of any desired throttle position.
-
After enabling in the configuration, I just set the idle cut-off right clicking in the throttle setup in Falcon. No additional settings or setup in Target. Never had any problems, works as advertised.
Send from my Xperia X using Tapatalk
-
Thank you stubbies, frederf, and terminator! I will try all of these solutions. Although with regards to setting the detent in the falcon setup screen. My throttle does not register past the physical detent on the throttle. So if I set the detent alittle above the bottom of the graphic wont the engine shut down if I pull the throttle back to the physical detent but not over?
-
Below IDLE isn’t part of the axis for the Warthog. It registers as 0 throughout the range from off to idle. The only change is a button press.
That’s the point of the script snippet above. It produces axis-like behavior based on whether that button is pushed or not. At OFF the button is pushed and the axis is 0; the script outputs 0%. At IDLE the button is released and the axis is 0; the script outputs 4%.
Setup is one would go into the setup screen, set idle position which will show 4% on the bar, and right click to set the cutoff line. Shifting to off pushes the button and the script changes the output to 0 and the bar vanishes. This of course only works if that code snippet is running (device is Thrustmaster Combined).