Orbiter 2010P1 - Forensic tool?

emarkay

New member
Joined
Jan 3, 2011
Messages
34
Reaction score
0
Points
0
Location
Planet Earth
What about the possibility of inducing failure modes based on probable events?

For example, there's that way-cool red glow and sound on re-entry. What modifiable parameters can be used to simulate a hole in a RCC panel, which on a Shuttle, after a timeout, would remove an aerosurface? Or, where a new (but already existing) thrust mode was placed perpendicular to the velocity moment, and 2 seconds later every segment goes ballistic? Or maybe lightning is simulated and 15 seconds of "nothing I do makes any difference!" can be changed to 45 seconds, or even to loss of thrust, or a panel MFD failure?

Maybe an old Atlas with a stuck vernier, or a DeltaGlider with a malfunction in an engine, or with the result of a bad landing that has bent the wing, or maybe even some selectable "Damage, Faliure and/or Temporary Modification" dialog to do new and imagined "what-ifs"? How about the thrust from the pressure venting of an airlock failure or added atmospheric drag due to solar events in orbit, or an EMP pulse that inverts control inputs?

This was considered when I noticed the latest R7/Baikonour addon (I don't have the exact filename at the moment) has some pre-scripted launch failure type major blow-ups!

I am not one who "watches to see the crashes", but this could add a level of "what if" to Orbiter, and possibly have educational aspects.

Thanks!
MRK
 
Failure simulation can be programmed, but needs to be programmed into every module seperately. Add on developers have the capability of reading values from a configuration file to customize the failure.

An example is the DeltaGliderIV. You can customize the damage simulation...
 
To delve in this kind of problems, you need CFD code for thermal modelling, and FEM code for structural failures. It is going to be computationally intensive as well, not realtime as Orbiter.
 
Back
Top