Jump to content

Recommended Posts

Posted

When you tick this option, what does it mean in practice? That in every flight there is a slight chance that you will have a random failure and if so - does anyone knows what is the %? Or does it mean that something will happen? IIRC in mission editor you can set a random system failure with a given chance, but that is via the trigger. I would like to add such option to my campaign (depending on time the crews would have to service the aircraft it would be from 2% to 15%), but I also wanted to know how does this work if ticked in options menu.

For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel.
Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.

Posted

Random System Failures. Check this box to allow randomized aircraft system failures to occur during the mission. These failures are automatically generated to simulate mean time between failures of different systems and are not based on the scripted aircraft failures included as part of a mission.

 

But

 

The FAILURES Panel allows you to set the aircraft's failures. . The list of failures depends of aircraft type.

Your aircraft might be damaged in combat as the result of a missile or shell hit. To be ready for such a situation and to be able to fly the aircraft when onboard systems have failed, this tool allows you to simulate such failures. Select the Failures button and specify in the failures panel the device you want to fail. Specify the exact failure time for the device or a Time Between Failure (TBF) if you wish to simulate failures without an exact failure time, but will occur within that specified time frame. For example: if you specify 30 in the Within field for the left engine, this means that your left engine will fail within the next 30 minutes. If you were to specify 0:15 in the After field, the failure will occur with set probability within the next 30 minutes after 15 minutes after takeoff.

Additionally, you can adjust the probability of failures by adjusting the Probability (%) field using the arrow buttons. The Probability ranges between 0% (no chance) to 100% (certain failure). Note that failure(s) only apply to the Player aircraft.

 

Along the left side of the window is the DEVICE list that can be used to set an in-mission failure.

To the right of each device line is a set of fields that allow you to set a time frame from mission start that the failure will occur and the probability that the failure will occur.

 AFTER (hh:mm). Input the hour and minutes from mission start that the failure will occur.

 WITHIN (mm). Use the third field to determine the time that the failure may happen.

 The PROBABILITY (%) field allows you to enter the probability as a percentage (0 – 100) that the failure will occur in the mission.

The steps needed to set aircraft failures include:

1. Check the checkbox of the desired failure.

2. Set the time at or after which the failure is to take place (hh:mm).

3. Set the time within which the failure is to take place (mm).

4. Set the probability for the failure to occur (%).

For example, to set a left engine failure an hour into the flight within a 15-minute time span and a 50% probability, check the L-ENGINE Device box, enter 01:00 in the After field, enter 15 in the Within field, and enter 50 in the Probability field.

At the bottom of the window are two additional controls:

 RAND. Pressing the random button will randomly select devices to fail and set random time windows and probabilities.

 

 CLEAR. The clear button will disable all failures and set all time windows and probabilities to zero.

  • Like 1

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted

Many thanks! ED could just add one button that would enable us to have a specific chance for a random system failure at a random time. But I think I will add a slight probability of failures to the campaign...

For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel.
Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.

Posted

Beware bird strikes show no failures in debrief

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...