A-20 Bug?

[[TWB]Sauerkraut-]

When starting the A-20 the virtual pilot automatically puts the mixture back to idle cutoff after the startup procedure is finished.

For any pilot not paying attention, and does not remember to manually increase the mixture right away, the engines will starve and shut off. I can't think of a reason the virtual pilot would do this, and I'm assuming its probably not intentional.

 

Feel free to correct me if I'm wrong (which is a very real possibility because I'm crap). If not, just letting the developer know.

[Finkeren]

Not really a “bug” per se, and it applies to all aircraft. 

 

Sometimes, if you start your engine without touching mixture control, the sim will get the idea, that your mixture control was at 0%. Then when the engine start-up sequence is finished, it simply resets the mixture to what it was before, which is 0% which promptly starves the engine and causes it to cut out. It doesn’t matter, if your lever/rotary/slider is actually at 100%, as long as you haven’t moved it, the sim hasn’t received control input and therefore thinks, that it is at 0%.

 

The solution is simple: Just set your mixture to 100% (or whatever you are going to use for taxi) before starting the engine, then the problem won’t occur.

Edited March 15, 2018 by Finkeren

[JaffaCake]

Very similar "bug" to 110 where the 1st engine would stop at 0% throttle while the 2nd engine is going through startup procedure. Setting it to 20-30% throttle prior to engine start does nothing - you actually have to actively select the engine during startup and keep nagging it to stay at 10-20%, frustrating.

 

Startup procedure should finish at "idle running" settings, not at "w/e was set by the pilot previously", so a bug in my book.

[Royal_Flight]

The Hs 129 does this too, its irritating and it's fair to consider it a bug tbh given the rest of the engine start-up procedure just involves pressin I and waiting, but as Finkeren says just set the mixture to 100% before startup and it can be avoided.