Since 1.5.7 some planes resistent to engine failures

[discwalker]

I tested my fixed wing planes for preprogrammed failures with 100%probability in single player missions.

Engines can fail in: Su-25A, Su-25T, MiG-29A+S+G, Su-33

Resistent FC3 planes: Su-27, F-15C, A-10A

Resistent non FC3 planes: F-5E-3, L-39C

 

Despite the logged engine failure events (" ' " view),

the warnings, black smoke... engines can be functioning normally.

 

((L-39C track replay still show telemetrics graph 1.5.7.9411.361))

(((track replay and SP mission not force to start with apostrofe view off:state is swappable)))

 

In my investigation 1.5.6.5199.291 was able to fail all my fixed wing planes engines.

 

(In 1.5.6 F-15C why don't have windmill mode for gererators in failing state?

RPM is set to 0 immediately when the fail raised.)

NOengine_ALBA.miz

oneengine_f5.miz

a10a-DOUBLEENGINEFAILURE.trk

F15DOUBLEENGINEFAILURE.trk

[discwalker]

the new PFM Su-33 is resistant to engine failures

 

Tested with OpenBeta: 1.5.7.9891.374

In the two track the two Flanker performs flawlessly after double engine failure.

After landing ground crew fix the error lights. Engines not needed to fixing anything.

su33_ob_DOUBLEENGINEFAILURE.trk

su27_ob_DOUBLEENGINEFAILURE.trk

[discwalker]

1.5.7.10872.388

 

Nothing changed in current update.

I tested Ka-50 and resistant to engine failures as "player".

[tintifaxl]

If the thread title misses [REPORTED] chances are slim that the bug gets fixed. Maybe you should pm a moderator and point him to this thread.

[Redglyph]

*EDIT*

 

If the thread title misses [REPORTED] chances are slim that the bug gets fixed. Maybe you should pm a moderator and point him to this thread.

 

That's a fair point. I'll create a new thread to revive this bug report as I'm not sure PM'ing possibly the wrong person would be the way to go.

Edited November 20, 2017 by Redglyph

[Hammerhead]

I have the same problem and could only find this thread.

 

I disabled my mods to be sure and executed "repair DCS". In the A-10C I cannot program an engine failure. The score window does make an entry of the failed engine though. Other failures are bugged too. So basic flight training campaign by Maple Flag is broken too due to this (or at least the missions involving triggered failures).

[discwalker]

open beta 1.5.8.12162.404

 

There are improvements: engines now can fail in Su-33, Su-27, A-10A, Albatros (has telemetry on track replay)

resistant to engine failures: F-15C, F-5E-3, Ka-50

[swimbody]

Any word on this fix? Wish I had known this or I wouldn't have downloaded the Maple Flag missions.....again 3 years later.

[Redglyph]

Any word on this fix? Wish I had known this or I wouldn't have downloaded the Maple Flag missions.....again 3 years later.

 

This has been silently fixed in 2.2, I haven't tried in 1.5.8. Do you still have this problem? Which version?

[swimbody]

This has been silently fixed in 2.2, I haven't tried in 1.5.8. Do you still have this problem? Which version?

 

Yes still an issue in version 1.5 open Beta. I just tried it last night about 4 times in a pre programmed engine failure exercise. It did not trigger.

[Redglyph]

Yes still an issue in version 1.5 open Beta. I just tried it last night about 4 times in a pre programmed engine failure exercise. It did not trigger.

 

It was reported here, but never acknowledged, so I don't know if it was repaired by "luck" in 2.2, or if we can expect it to be repaired in the next 1.5 beta too... I'd say yes, probably, hopefully! But that's just a guess ;)

[Redglyph]

Yes still an issue in version 1.5 open Beta. I just tried it last night about 4 times in a pre programmed engine failure exercise. It did not trigger.

 

I confirm, DCS/1.5.8.12667 (x86_64; Windows NT 6.1.7601), the bug is still there.

 

 

Screenshot of debriefing, mission and mission log in attachment. Mission triggered multiple failures once in the air, but nothing really happened and no actual failures were endured by the airplane. Still, they are shown in the debrief.

 

 

 

EDIT: apparently the log was again rejected by the upload... hope it's not critical

failure2.miz

Edited December 21, 2017 by Redglyph

[exnihilodub]

I hereby confirm that the bug is still present in 2.5

[canned_fire]

Now that the F-18 is out, could you please fix this? It has been a while...