cannot reproduce Random Engine Flameout

[MoppleTheWhale42]

For several months now, random engine failures have been occurring repeatedly on the A-10C II. Without any external cause, one engine is on fire. This can be the left or right engine. If you are unlucky, even both within one mission. It does not always happen to the same A-10 within the mission.
Birds are turned off in the missions, as is the random failure of system components (I checked this in the mission file). There is no strafing either.

So I don't see any reason why one engine keeps going up in flames. Are there any other reasons for the engine failure listed above?

  

[Iron Sights]

I’ve heard of this before, but I don’t know why either. I have not been able to get this to happen, other than when random failures were on and it seems the engine would always be the failure. 

[ASAP]

Are fuel flows override? did you put the motor switch in motor and leave it there? Fuel boost pumps turned off? (I know the engines SHOULD suction feed but that's not an absolute under all flight regimes). I'm not sure to what level all those switches are modeled, but those could potentially cause issues if its a simulated jet issue.... Or its a bug in the game I dunno.

[MoppleTheWhale42]

Thanks for your hints. Fuel flow is set to NORM. Fuel pumps are running.

If it would happen to the same player all the time, I would assume an individual error. However, it appears to happen randomly, it appears at a random time and the affected player also seems to be "selected" randomly.

[razo+r]

Please attach a track or the mission in which this is happening.

 

[MoppleTheWhale42]

Please find attached the trk-File, which contains the mission. Pig-1-1 suffered from two engine failures. I had to put the trk-file into an archive, otherwise it would have execeeded the 50 MB file size limit.

Bambini_Caucasus_Standard_v4-20231013-203656.zip

[razo+r]

1) Are birds enabled in your game settings (Your actual own game settings, not the mission settings (or whoever created that mission))?

2) Is it only engine failures or other failures aswell?

3) Does it happen in this mission only or are other missions also affected?

When I look into the mission file I can see that birds are set to 500 (no idea what value it is but it's not 0). And if you only see engine failures happening, then there is a good chance that this is the issue.

Edited October 15, 2023 by razo+r

[Iron Sights]

One thing I did find is running negative G’s can cause a flameout. Seems like about 10 seconds, so you would have to be pushing it. Just thought it was worth adding.

[MoppleTheWhale42]

razo+r, thank you for looking into this issue. Yes, birds are enabled in my setting, and I think I get your point. It looks like birds are not forced off in the mission and this is why bird strikes can happen.

To answer your other questions: The only failures that happen are engine flameouts. The problem occurs in different missions.

I will make sure that the next missions we fly will have birds forced to 0 and hope that this solves the problem.

 

 

[Sn8ke]

I have had this happen once. 

[MoppleTheWhale42]

Since all pilots have set the number of birds to 0, the problem has not occurred. I'll wait a few more weeks, not that it was just a coincidence, but it looks like it was the angry birds.

[MoppleTheWhale42]

Looks like the problem was caused by birds as the number of birds was not set to 0 in the missions and therefore the individual settings of the DCS installations defined the number of birds.
Thank you for all your comments!