Auto-start broken in latest 2.1 Nevada map

KA 50 auto-start seems to be broken (don´t know if this is a new issue or an old one.... because I recently installed KA50 on this map).

Auto-start brings left engine to life but not the right one. Manual starting the right engine thereafter with APU of course works.

If you believe it to be an issue of the module, pls look into it.

Thank you very much!

Same here. The autostart is not starting the right engine in 2.1 Nevada

From external view, notice there is no heat blur from right engine.

Well, it's an old thread and only about Nevada, but I'm wondering if it's a general problem? I tried Autostart on Caucasus in the 4th mission of the "Memories of the Hero" campaign and the right engine also didn't start.

I think it's trying to start the right engine before the left engine has started up completely?

Can confirm broken autostart in Caucasus map in MP. Left engine running, right engine needs to be cranked and then started with APU.

Georgia Reign - Dynamic PVE WAR - v3.0.77-20190907-080645.zip

https://forums.eagle.ru/showthread.php?t=239623&page=2

Page 2 has an explaination of what is happening (basically autostart timing doesn't account for some weather variables) and further on is a quick guide to manually starting the right engine. Looks like the autostart script logic should be condition rather than time based to alleviate this issue.

Hope this helps.

Hi all

 

I am unable to reproduce.

 

Can you please attach a short track from MP showing this happen, I will be happy to take a look.

 

thanks

Added a Trk-file to my first post. But I bet you can reproduce it on the Fraternity Server, Ka-50 slot at FARP Paris ;) Everytime the right engine starts to soon and drowns.

Hope this helps.

Haven't tried in a while, but I had it happen on PGAW every time ( the right engine failing to start ) when I was there regularily. Not on other busy servers ( like the somewhat related GAW ).

The engines take longer to spool up in hot/cold climate + at high altitudes, but the auto-start uses fixed timings. The right fuel cutoff gets switched too early, the engine will not ignite and stick around 20% RPM.

Just a slight variation in weather or altitude can cause this to occur, which explains why it can't be reproduced reliably. It has nothing to do with PG or any other maps.

The only proper fix would be making the auto-start dynamic so the cutoff is only being engaged at 19% engine RPM.

So, not really a bug. Just a shortcoming of the auto-start script.

Finally a good bug. Lol. What a shame to auto start such a fine chopper. ;)