Cut off/idle in Warthog -what to do to run, not burn engine (F 4.34)
-
First of all, I would like to thank you for the next super incarnation of Falcon.
But I have problem, could you help me please.
I use BMS - BasicDx TM Warthog_MFD file (Falcon BMS 4.34/Docs/01 Input Devices/03 Hotas Setup/TM Warthog.
All axes work fine in the setup screen.
During ramp start, I switch JFS switch to start2 position, observe RPM, at about 20%, the SEC caution light goes out, and I try to cut off/idle detent pushing L/G WRN SILENCE (gray button on the warthog throttle - according to BMS - BasicDx TM Warthog MFD profile file) and there is no reaction, soon the RPM goes to zero and FTIT increase and I burn the engine, pushing again the button when FTIT increase do nothing.
The same effect is when I use Alt+i, or even when I try to use throttle (right or left, or both, of course first I assigned the move from off to iddle in the setup screen).
I also try to move throttle all the way forward and then all the way backward as a first thing siiting in the cockpit - no effect.Of course in the setup screen all methods show that the cutt off/idle detent toogle works fine.
What is wrong, could anybody help me please. -
My guess is you are starting in battery and not in main power or you are messing with the canopy position while the JPS is running. Both no-nos in 4.34. Also when you do the cutoff are you leaving the JFS running to cool the engine down?
Some of this is just guessing as I run a WH as well but I don’t use DX for my assignments and have a realistic idle cutoff through Morphine’s excellent TARGET engine cutoff code.
-
I accidentally started in battery and didn’t have a hot start. I never tried changing canopy state during the start, makes sense that draws battery power.
What I have found is that early off-idle transition at ~15% maybe even up just less than 20% RPM is bad news. I wait until 25% and don’t have an issue. There’s no real downside to letting the RPM max out on the bottle before ignition. The bottle is finite but you can afford to sit against the maximum blown RPM for a few seconds before leaving cutoff.
Since you’re using the original “throttle up then idle detent” method you want to increase the throttle a lot before the command. I forget the exact threshold required but it’s at least 33% of the axis range. Make sure to wake the throttle up until the animation and your joystick axis match up. If you have any problem use lots of throttle, go MIL or MAX before sending the detent command. You’ll have enough time to retard to idle before jumping out of the chocks. The sim takes your throttle axis position as a clue what to do at the moment the detent callback is sent. If you’re at 20% or so it won’t jump from off to working range.
-
I was having this issue at first when I updated to 4.34.
I was moving the throttle into the idle cutoff at around 19-20% and after the SEC light had gone out. Every time I got a hot start.
It seems to work much better if you wait until RPM is around 22-25% to move the throttle into idle cutoff.
-
It is exactly what NERO said. you need to be above 20 percent RPM before going idle detent. I was also doing it just as the SEC light went out and that is too early wait until 22% and you
-
Thank you.
But I found solution. In Falcon BMS Config, under Hardware there is Iddle Cutoff position. And it was marked.
Now I changed it to unmarked and everything works fine