Right Engine won't kick on

[nomdeplume]

I have a similar problem; engines won't start because my throttle won't move. I know the controls are mapped fine because if I do any training where the engines are started already I can use my throttle but for a cold start, they won't move. I am using the checklist provided by Konkkussion but for whatever reason no movement on the throttle.

The real throttles have an 'off' position, and then a hump you have to lift the throttle over to get up into the 'idle' position. If you have the ThrustMaster Warthog HOTAS then you'll have the same setup, but if you have any other throttle you probably won't have the separate 'off' and 'idle' positions.

 

If you have another HOTAS, then you need to use the keyboard shortcuts (or some other binding) to move the throttle from the 'off' position over the hump to 'idle'. At that point the engine will start spooling up through the normal auto-start sequence.

 

Simply moving your throttle while the game's throttle is in the 'off' position will have no effect. I believe that's what you're experiencing. You need to use the keyboard bindings (which I think are RightAlt+Home to move the left throttle to idle, and RightCtrl+Home to move the right throttle to idle). You also need to make sure your physical throttle is all the way back in the idle position, as the engine start sequence won't run if it's not at idle. If I recall correctly, in the betas the game would ignore the 'move to idle' command if your HOTAS throttle wasn't at idle. Not sure if it still does.

 

Similarly to fully shut the engine down, you need to move the throttle from the idle position over the hump to the off position. Keyboard shortcuts are RightAlt+End and RightCtrl+End.

 

You can of course bind these to other buttons, although you don't start and stop the engines very often so there's probably more useful functions you can bind to your limited HOTAS buttons. They're listed as "Engine Start Left/Right" and "Engine Stop Left/Right" in the controls page.

Edited May 30, 2011 by nomdeplume

[battguano]

thank you very much nomdeplume, that seems to be exactly the case. Since I just bought two thrustmaster MFD's I might use a couple of those buttons for my engine start.

 

~S

[Blackghost]

Your throttle is too far forward. It needs to be in the idle position for the engine start cycle to operate.

 

Make sure your physical throttle is all the way back before you use the keyboard shortcut to put it over the hump from off to idle.

 

I also noticed it was twitching so you might want to verify your controller is calibrated properly and the throttle can hold a steady position. Also, the RightCtrl+Enter keys within the sim will open a dialog showing the input state of your controllers.

 

A re-install fixed this, although the problem has come back, I don't think that I mentioned either that with the APU on, neither engines will motor (switch next to throttle) I think its a bug, I also am inclined to think that it has some connection with TARS, as I tabbed out, took TARS off standby or enabled the plug-in on Teamspeak (whatever) and then the problem started again.

today I have done many re-installs and this has not solved the issue, its definatly not me or my flightstick as I frequently start up and fly with others.

I'm going to remove all the engine start/stop bindings, re-install then see what happens, I'll do this tomorrow and post the results in an edit to this post.

 

 

 

The re-install has fixed nothing, the engines won't even motor :'(

Edited June 9, 2011 by Blackghost
follow up

[Turbine]

Old topic, but this issue still exists and I found the cause, at least for me.

 

TrackIR. No idea why, but I've been using both together for some time with 0 issues. Early last this all of a sudden started happening to me, where just my right throttle wouldn't do anything. It wouldn't budge. My key mappings haven't changed at all in a while and neither has TIR, my controllers, comp, nothing (haven't even run windows update in over 300 hrs of game time).

 

Anywho, I confirmed several different shortcuts, both hardware and software for my unlatching of the right throttle and nothing. I then started tried killing processes, 8 hours worth, nothing. Finally I tried it without TrackIR(5), and it works 100%. I confirmed this several times with many reboots. I can reproduce it every time.

 

Before the obvious is asked, no, I do not have the controller configured in TrackIr, again this has been working 100% for a while now, until last night.

So if you (the OP), or anyone else has this anomaly, I finally got them both working together again. Maybe it was a corrupt profile? I removed the one I had assigned to it and it now works great again.

 

PS. Also take note of this (if you don't know). Due to how DCS A10 and TrackIR seems to be set up, you need to set this profile for both "Black Shark" (which I never owned), and also "DCS: A-10" in your titles page. No idea why the two are there and no idea why that was never fixed but if you don't do that, then TrackIr defaults back to default all the time.

Edited February 26, 2012 by Turbine

[Fleshpiston]

Due to how DCS A10 and TrackIR seems to be set up, you need to set this profile for both "Black Shark" (which I never owned), and also "DCS: A-10" in your titles page.

 

Here: http://forums.eagle.ru/showthread.php?t=85795

[VladimirSputnik]

I noticed after the patch the fuel pumps are already switched on after spawning.

Seems aircraft has been tweaked a bit, must wait for engine 1 to complete start cycle (light out on warning panel), otherwise No 2 will only reach 40% or so and gets stuck.

[Yurgon]

Seems aircraft has been tweaked a bit, must wait for engine 1 to complete start cycle (light out on warning panel), otherwise No 2 will only reach 40% or so and gets stuck.

 

In what way was that tweaked? As far as I can tell, it's always been like that. I guess one APU can't start two engines simultaneously.

 

Also, pointing out the obvious: nice necro. ;)