Ramp start problems

[ScEBlack1]

Each time I try the ramp start whether it is in a mission or not I follow the steps exactly as the training tutorial and others do, but after I hit the APU button it fires and then settles down after a few seconds (rpm/fan settle) then I turn on the APU generator to power and when I go to move my throttle to idle it does nothing to start the engines, I actually need to move the throttle (both) up to half way, then slowly bring them back and then and only then my right engines starts up followed by my left soon afterwards, what am I doing wrong here? I follow the startup to the T but does not work for me.

[636_Castle]

Post a track so we know what you're doing exactly.

[aerick911]

If you have the throttle a little above idle and attempt to start the engines, I've had issues where they won't fire up. I walk the throttles back all the way down(to idle), and then fire em up.

 

I'm pretty noobish to ramp starts though, I've only done about a dozen of them. (half the time I screw up EAC aligning, only to notice it midflight).

[Raven68]

Each time I try the ramp start whether it is in a mission or not I follow the steps exactly as the training tutorial and others do, but after I hit the APU button it fires and then settles down after a few seconds (rpm/fan settle) then I turn on the APU generator to power and when I go to move my throttle to idle it does nothing to start the engines, I actually need to move the throttle (both) up to half way, then slowly bring them back and then and only then my right engines starts up followed by my left soon afterwards, what am I doing wrong here? I follow the startup to the T but does not work for me.

 

I'm struggling as well Jessi1. My issue is after I hit the start button for my left engine(Ralt/Home) my throttle position travels about 1/3 up in the cockpit. I then have to step it down (Ralt/Page Down) to get the engine to spool up. I notice that if I move the throttle up on my controller the cockpit throttle returns back to the position that it had when I pushed the start button sending the RPM's way over idle.

 

Another thing I am having issues with in this whole process is that I cant get the right engine to start at all when I press the start button(RCntrl/Home). I am sure it another one of those user ignorance issues that I keep having. :helpsmilie:

[WarriorX]

Are you guys forgetting the Left and Right Main and Wing Boost Pumps to the ON position?

 

Also, when you do start one of the engines, look at the top left button in the Warning Lights Panel (Caution Panel) It will say something like Eng Start Cycle. When the Engine Start Cycle lamp goes out, you can go ahead and start the second engine.

Edited March 14, 2011 by WarriorX

[JEFX]

I suggest recalibrating your throttle so that it goes really from 0 to max (if, by any chance, your throttle is badly calibrated and when you start your engine it is already up by a certain %, despite it being physically at the minimum, you may have problems).

 

JEFX

[Zenra]

@jessi1: As aerick said, you may need to pull the throttle lever a bit back into the idle stop. Using the TM Warthog HOTAS I find that it works best when I pull the throttle lever back gently against the stop right after advancing it over the hump. This might have something to do with individual axis calibrations or slight differences between joystick / throttle hardware.

 

@Raven68: It sounds like your throttle is reading an above idle value at start and the program isn't being updated until you move it. Have you tried "exercising" it before attempting the engine start (i.e., before the APU is running)?

 

Also, for both, you might want to try the more realistic start procedure of switching each engine to "MOTOR" first, letting the fan reach 30%, and then moving the throttle to idle and returning the engine switch to "NORM". This gives you control over when the engine ignition sequence starts as well.

[ScEBlack1]

"Are you guys forgetting the Left and Right Main and Wing Boost Pumps to the ON position?"

 

Yes Warrior I have those set, strange that my keyboard input for left engine idle is Ralt + page up and not Home, but it still moves the throttle to idle so I am pretty sure it is not that. I also understand the engine start up lamp on the right console up front lighting up and stopping when ready to fire up the second engine, my problem is nothing happens when my throttle goes to idle, I need to move both engine throttles up then slowly back for my right engine to start followed by my left.

 

I will save my track then post if someone can tell me how to post it here, thanks.

[ScEBlack1]

"you might want to try the more realistic start procedure of switching each engine to "MOTOR" first, letting the fan reach 30%, and then moving the throttle to idle and returning the engine switch to "NORM".

 

and then hitting APU switch?

[WarriorX]

"and then hitting APU switch?"

 

No, APU + APU GEN first....then Boost Pumps...etc

[ScEBlack1]

Ok this is strange, when I set myself up in mission editor for a ramp start I can start the jet no problem, simple as can be and just like the tutorial, but, when trying to ramp start Dragons JTAC day mission it does not work the same.

 

When I do a ramp start by my own in the mission editor I need to dis-engage my TM Hog hotas throttle so they are separate (each throttle moves interdependently) and then the throttle to idle button is Ralt + HOME and the engines fire up, BUT, when I go to Dragons mission and do the exact same thing the throttle does not move to idle by Ralt + HOME only to Ralt + page up, and the engines do not fire, actually the APU dial for rpm only goes to 60% were as in my created mission ramp start it goes to 100%, strange.

[WarriorX]

Jessi, why are you using the keyboard assignments for throttle movement when you have the Warthog? You should only be using the throttle for engine starts.

[ScEBlack1]

"You should only be using the throttle for engine starts"

 

You mean as far as pushing the throttle forward to idle instead of using keyboard assignment? it should not matter right? I could be wrong of course but I would think not. Either way I have tried in Dragons mission simply moving my throttle to idle physically and still not getting the engines to start. It seems that in his mission compared to my editor ramp start mission the APU rpm gauge only goes to 60% then starts going down to 0, were as in mine it goes to 100% then drops a little but still stays strong and loud.

[Scabbers]

no if you have a warthog you should not be doing the keyboard shortcut. it can create an error in the hardware telemetry

[Raven68]

Thanks fellas for the advice it was indeed bad calibration for me. Everything spools up accordingly now and I appreciate you all that chimed in. Also thanks for the other method of start up also. :thumbsup:

[El_Roto]

@jesse1: I'm inferring from your post that you keep the WH throttles linked except when starting up (definitely stop using the keyboard shortcuts, btw). I strongly suggest that you get used to flying without the linkage. If you have an inflight emergency it takes too long to get the throttles separated.

 

I started flying with the throttles linked but stopped after an engine failure caused me to rethink that course of action. It takes a little getting used to but once you have the hang of it you'll forget that rod ever existed; only use it when you're flying sims that don't recognize dual throttles or single engine a/c.

[ScEBlack1]

" I strongly suggest that you get used to flying without the linkage. If you have an inflight emergency it takes too long to get the throttles separated."

 

 

Thanks will try this out.

[lobo]

" I strongly suggest that you get used to flying without the linkage. If you have an inflight emergency it takes too long to get the throttles separated."

 

 

Thanks will try this out.

 

The throttle inkage on the TM WH was put there by TM so that if you are flying a single engine airplane you can link the throttles to become one solid throttle. In a twin engine plane the throttles are always separate. ie not linked.