Improvement proposal: Random failures - Missions does not force it to be off

[Rosly]

On Mission 6 I got right engine failure. There was flame ans stuff  and I could not ignite engine back.
I needed to abort the mission.

Latter on I noticed I have "random failures" set to ON in my options and it seems I was unlucky enough that it fired during the campaign mission.
Also it seems missions from this campaign does not force it to be off (I checked mission 6 in editor and it seems to be so).

 @baltic_dragon was this  overlook in mission setting which does not force random failures to be off?

Improvement proposal:
If users have this setting to be on, there should be an option to abort the mission if a failure occur and does not allow to finish the mission.
Or the mission should overwrite the user setting and force it to be off if the mission does not implement such mechanism.

Edited January 1, 2024 by Rosly
spelling

[baltic_dragon]

Hey, thanks. The problem is I cannot detect that it happened and on top of that adding such option to all 21 missions will take a LOT of time - and I am very low on DCS time in general plus lately I've been using most of it to update old missions that stopped working due to some new features implemented in DCS Forcing random failures OFF might do the trick, but ultimately it is up to each player what they want - some want to have random failures because it makes the campaigns more challenging and realistic - so I think I'll leave it as is now, hoping that those that don't want surprises will remember to turn them off  but thanks a lot for the suggestion and hope you will enjoy the rest of the campaign!

[Agim]

I've had similar problems with A-10 recently. The culprit was bird strikes settings. Setting it to 0 in ME solve the problem.