Idle detent issues
-
Hey fellas
I have been trying the cold start procedure and done so according to the letter, but when I have stable 25% RPM and want to move past the IDLE DETENT nothing happens
I know from before that the trick was to have the throttle at 50%, then press the idle detent (alt-i) and the retard the throttle, but I cannot seem to get it to
workI have checked my keyfile with PSkey, and while using Morhpeus Warhtog Target profile I even have it mapped to a button on my throttle console
Even so, pressing it does not cause the engine to ignite, either when advancing or retarding the throttle afterwards
I have read up in the 3,33 manual- but apparently I am missing something,
Any help would be greatly appreciated:)
-
theres an option to bypass that so when you start the engine it auto clicks in the idle
Configuration > Hardware > Idle Cutoff
hope that helps
-
Wathog user without making use of the IDLE-OFF button? Now I have seen everything. I can help you with the old-style of “over the hump” but please consider using the cutoff position as per the aircraft. To miss out is like to buy a sports car but only use the trunk to put your clean clothes for storage; it hurts a little to read about.
You say “50%” which is fine but I remember it was “>X%” where X was maybe 30 or so. Of course 50>30 but the lesson is that if you are having problems, don’t be shy and go straight for 100%. At least this was true 4.32 and before.
Also the “alt-i” maybe is unreliable. Maybe the callback has changed or there is a keyfile error. For less chance of a mistake of this type, use the click zone in 3D cockpit as it must work without regard for control setup. You can doubly check the detent behavior by going into instant action (or any other time the engine is running) and try to turn the engine off like normal. If “Alt-I” won’t turn a running engine off with minimum axis input then we know more.
There is a chance that you already have “idle cutoff” behavior selected in options which makes for a new situation. Check the “Set AB” are in Setup. The green line is afterburner threshold. If you see a red line that is for the idle cutoff feature (right click sets) then I think it is on. If there is no red line then the idle cutoff feature is disabled (I think).
I would think that Morpheus’s TARGET profile (I don’t have it to read) would make use of the idle-cutoff feature. It is well within his scripting abilities and a normal thing to code when using TARGET and BMS. Maybe you are running something like this already and 4.33 is having trouble with your elevated idle and the old-style idle detent logic. For me my throttle axis looks like:
//Throttle Axis (4%-100% w/ detent pause) //THROTTLE AXIS OR SLIDER0 MapAxis(&Throttle, THR_LEFT, DX_THROTTLE_AXIS); 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));"));You see the “0,4” means that 0 input = 4% output. This is IDLE. When I go to OFF on the controller it shifts the axis by 82/2048ths (4.00390625%) which makes 4%-4%=0% output. Then releasing the OFF button it erases this shift. With the red line set at 4% in setup (idle cutoff feature flagged as (1) on) I never worry about the idle detent command because it is built in to moving the throttle axis.
-
Wathog user without making use of the IDLE-OFF button? Now I have seen everything. I can help you with the old-style of “over the hump” but please consider using the cutoff position as per the aircraft. To miss out is like to buy a sports car but only use the trunk to put your clean clothes for storage; it hurts a little to read about.
You say “50%” which is fine but I remember it was “>X%” where X was maybe 30 or so. Of course 50>30 but the lesson is that if you are having problems, don’t be shy and go straight for 100%. At least this was true 4.32 and before.
Also the “alt-i” maybe is unreliable. Maybe the callback has changed or there is a keyfile error. For less chance of a mistake of this type, use the click zone in 3D cockpit as it must work without regard for control setup. You can doubly check the detent behavior by going into instant action (or any other time the engine is running) and try to turn the engine off like normal. If “Alt-I” won’t turn a running engine off with minimum axis input then we know more.
There is a chance that you already have “idle cutoff” behavior selected in options which makes for a new situation. Check the “Set AB” are in Setup. The green line is afterburner threshold. If you see a red line that is for the idle cutoff feature (right click sets) then I think it is on. If there is no red line then the idle cutoff feature is disabled (I think).
I would think that Morpheus’s TARGET profile (I don’t have it to read) would make use of the idle-cutoff feature. It is well within his scripting abilities and a normal thing to code when using TARGET and BMS. Maybe you are running something like this already and 4.33 is having trouble with your elevated idle and the old-style idle detent logic. For me my throttle axis looks like:
//Throttle Axis (4%-100% w/ detent pause) //THROTTLE AXIS OR SLIDER0 MapAxis(&Throttle, THR_LEFT, DX_THROTTLE_AXIS); 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));"));You see the “0,4” means that 0 input = 4% output. This is IDLE. When I go to OFF on the controller it shifts the axis by 82/2048ths (4.00390625%) which makes 4%-4%=0% output. Then releasing the OFF button it erases this shift. With the red line set at 4% in setup (idle cutoff feature flagged as (1) on) I never worry about the idle detent command because it is built in to moving the throttle axis.
Strange one to read simply because (I think he MEANT to say Morphine’s profile and not Morpheus or are we getting a marriage of The Matrix and BMS code?
) if he is using Morphine’s WH config it DOES have the idle cutoff code installed. I stoles it to use in my config as it makes the WH behave EXACTLY like the F-16 for start up and shut down. -
Hehe- yeah- Morphine- not Morpheus-, and to the answers above, I have tried wiggling the throttle back and forth while using both IDLE DETENT commands(Both the one mapped to the WARTHOG HOTAS TARGET script, AND the one from the keyboard keyfile) while juggling my throttle back and forth from min to max, Gonna continue testing tomorrow
If people get bright ideas, please share them, though be advised: I am a BMS newbie
-
Hehe- yeah- Morphine- not Morpheus-, and to the answers above, I have tried wiggling the throttle back and forth while using both IDLE DETENT commands(Both the one mapped to the WARTHOG HOTAS TARGET script, AND the one from the keyboard keyfile) while juggling my throttle back and forth from min to max, Gonna continue testing tomorrow
If people get bright ideas, please share them, though be advised: I am a BMS newbie
Not sure what you did as I use his idle detent code verbatim in my TARGET setup and it works just fine in 4.33 too. You do not have to wiggle anything during the start process. I just make sure to move the throttle in the middle range ish and bring it back to cutoff so that BMS “sees” it’s position. At that point I can have the JFS running at 25% and not going anywhere until I bring the throttle out of cutoff and at that point the engine spools up. No need to bring it to midrange or whatever with this code. Right to idle detent works just fine.
You have the idle detent checked in the BMS config correct?
Also with Morphine’s code you do NOT enter an idle detent command you simply bring it out of cutoff. You also set your red line on the throttle bar correct?
-
Thanks for the input guys. I managed to sort it out by setting the detent line. Alt-I did not work because I had selected the detent option under hardware. Up and flying now- thanks for the help:)