Jump to content

Engine do not start anymore after update


Go to solution Solved by MiGCap1,

Recommended Posts

Posted

Before the update, it worked smoothly. Starter engaged, stabilizing at 700 rpm, moving mixture to auto lean, waiting a little bit, moving to auto rich, disengage the starter and it runs perfectly.

Now it stops working after a few seconds at 700 rpm, at mixture cut-off, auto lean or auto rich, starter still engaged or disengaged after some seconds. Nothing works. I tried everything. 

All controls move into the right direction visually.

Posted

Nothing different on my end.  Same procedure as before.  You didn’t mention whether or not you prime the engine and open the throttle 1 inch before starting.  Those steps need to be done.  I also take fuel from the reserve, not sure if it matters for startup, but that’s what the procedure calls for takeoffs and landings.  
 

After priming 5 seconds, both mags on, battery on, fuel pump on, throttle 1 inch open, RPM max, mixture idle cutoff, and fuel tank set to reserve, my crank procedure is as follows:

Hold starter until RPM gets around 500, wait a second, go straight to auto rich, wait another second, release starter.  Works every time.  Sometimes I gently pump the throttle forward just a bit immediately when releasing the starter and then set it to 750 RPM, just in case it wasn’t getting fuel. 
 

 

My DCS Missions: Band of Buds series | The End of the T-55 Era | Normandy PvP | Host of the Formation Flight Challenge server

 

Supercarrier Reference Kneeboards

 

IRL: Private Pilot, UAS Test Pilot, Aircraft Designer, and... eh hem... DCS Enthusiast

Posted

I executed the start procedure exactly as described in the EA Guide, and it worked. Except I never saw the "Engine primed" message, maybe I was not looking where I should.

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Posted

I recall reading that info about that "primed" message in EA guide is a leftover from earlier development phase, and you will not see it in current game verion.

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

  • Solution
Posted

Problem solved.

I deleted the config folder where I added the new trim reset after the recent update and replaced it with the safety folder (I save my config after every change).

And everything worked perfectly again: The engine started without problems the way I started it always.

Then I again  added the trim reset (to the same button as before) and the engine start routine still worked.

I have no logical explanation for this bug besides "It's just DCS, what do You expect". :clown_2:

Thank You for trying to help me!

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...