Jump to content

Recommended Posts

Posted

A feature I believe will add quite a bit more immersion to this sim would be to add component and systems reliability. This could be as simple as a probability based model for things like the electrical, avionics, hydraulics, fuel etc. Some of the items done on the start up checklist includes component checks like the built in tests on the A-10C and the fuel quantity gauge check on the black shark. To me these checks don't currently feel very important because I know that the system is 100% okay unless someone shoots at me or I damage the aircraft myself. It would be great to have component reliability modeling put in place because then you feel like these checks are actually somewhat necessary to provide you feedback on whether the systems function correctly. Other systems I think can benefit from this include engine health (hot starts, flameouts, fire suppression system tests). Because system failures can already be set as an option within the mission, I don't believe adding a realistic probability based reliability feature to be a large task to implement. Not only could components fail from the start but they can also fail during the flight therefore keeping an eye on everything becomes more important, even when on a peaceful flight back to base.

 

Of course this mode could be a simple checkbox "Realistic Component Reliability" that you can disable if you prefer not having.

 

This can also tie into the crew chief functionality. If you find something wrong with the aircraft you can then tell him what system is pertains to and he can repair it before you fly out, or you can maybe get the option of getting in another aircraft.

 

Other features that can later be added but would take more effort for implementation include aircraft use and component life on campaigns. If you fly the aircraft in an abusive manner, aka hard landings, running the engines in emergency power, overspeeding the rotor, over G the aircraft, this can affect the component performance and reliability for the next mission. A crew chief briefing could even provide you a status of repairs and state of the aircraft before mission. Richard Burns Rally, the rally racing sim does a great job in implementing repairs between races and adds quite a bit of immersion to the racing series events. The crew chief could tell you that certain components are inop for the mission and requires you to think creatively of what alternative means you have to complete the mission, or you can choose to delay your mission and have him fix the aircraft which can impact other things within the mission and the campaign. I'll admit, these are far fetched but I believe things like this could add quite a bit more immersion to DCS.

 

Let me know what you guys think.

  • Like 1
Posted

Shame on me, there is a checkbox in the mission editor labeled "random system failures". Any details on this feature and how it works?

Posted

Depends on the specific aircraft in question. Each aircraft is unique in what can fail, and some aircraft are modeled more in-depth in terms of potential failures than others. For instance I think the P-51D has the most potential failures. Looking at the failures list in the editor is an indication of what can fail. It can range from relatively minor failures like a back-up system or radio failing to the more flight ending failures like hydraulics, engine, or in the case of an A-10C, a digital clock failure.

 

It is implemented via being completely random. I honestly don't know the code behind it, so it is possible that failures will occur at any time with any severity throughout a flight.

The right man in the wrong place makes all the difference in the world.

Current Projects:  Grayflag ServerScripting Wiki

Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread)

 SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum

Posted

I always like the idea of "what if" the game could tell whether you did the proper check or not and if you didnt then that system will have a greater chance to fail.....making stupid bit check important because you dont want a 10% fail chance added to that system....but proper startups and safety checks will result is a normal 100%er

 

 

the current random failure setup is so random that it makes no sense....it needs a chain of events leading to failure.....not just a "oh look, random event, main hyro fail"....."oh wow, left front tire need air"...."oh snap, cupholder just broke spilling rum and coke on the autopilot"....

 

we need a "excessive engine heat, excessive engine heat, excessive engine heat, engine fire"....or ...."electrical flicker, electrical flicker, electrical flicker, generator blinks out for 1 full second and all computers enter reboot phase".....a fault in a system is in reality a chain of events....a random failure system should reflect this....

It only takes two things to fly, Airspeed and Money.

  • Recently Browsing   0 members

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