Implement damage

[gilbertohasnofb]

Create damage model:

• gear collapse
• wings light damage
• wings heavy damage (broken wings)
• engine crash (e.g. hitting the propeller in the floor)
• airplane crash

[gilbertohasnofb]

@wlbragg would you be interested in this?

[HHS81]

I'm not happy with the way the c172p it does. I always notice a hit on the framerates and a short hicup when a damage occours.

My priority would be to make the aircraft fly like the real one - here making the engine let start and idle realistic. Then we should proceed to most common failures: tire blow, surface effects on braking, front gear collapse, engine damage, prop strike, icing. Flightgear is not a crash simulator. But things which will lead to a crash should be simulated.

[gilbertohasnofb]

Yeah, I kind of agree with you. But right now if we hit the ground the aircraft will just bounce as if nothing happened. I think at least killing the engine or something like that should be implemented.

[HHS81]

Depending on the impact angles and strength there are many things happening: Magnetos stops, fuel lines breaks, ... . Sometime a real aircraft just slides, sometimes they break into thousand parts. It isn't simulated good enough anywhere. I don't like the behavior of the DR400 as an example. I will think about how to solve this.

[hbeni]

@HHS81 Do you already have an idea how this could be implemented?

[HHS81]

Yes, but: I have still issues open and since I don't live from my work here, there is no rush!

[hbeni]

I was just asking because i may give you a hand here. Maybe i can start a new branch and work on the XML infrastructure and you add the modelling part later?

[HHS81]

Sorry, but I want to have it different like the c172p. There are some things I don' t like it there, that's why it doesn't make sense to add any xml structure or anything like that right now. Thanks for your offer, but not needed right now here.

[hbeni]

Okay! No Rush!

[HHS81]

collection of ideas/ things to pilot induced damage:

• gear collapse
• tyre blow
• wings light damage
• wings heavy damage (broken wings)
• flap overspeed (loss and jam)
• prop strike (using a more realistic method than c172p - already in the pipeline)
• fuel line damage due g-force (hbeni?)
• electric failure due to lightning strike
• forest collision (by detecting scenery ground materials and checking agl)
• influence of rwy condition (ice/ wet) to braking action (code already written! 😃 )
• hypoxia above 12500ft

[hbeni]

I would drop in:

• tank leakage
• fuel pumps damage
  Both already supported in the fuel system, as well as fuel pipe leakage/stoppage

Just to comment on my reference to the failure issue, i think most if this could be implemented using the failuremanager code quite easily.

[HHS81]

Tank leakage and fuel pump damage would be failure, and not pilot induced damage

[hbeni]

Yes, we should separate this, but also lightning strike is not pilot induced.

As far as i understood, tbe failuremanager framework could be used for damages too:
For example the case with flaps overspeed could be a specific trigger acting on speed and flaps state.

[HHS81]

lightning strike is not pilot induced.

It is, as you should never fly in thunderstorms or near to such

[hbeni]

Currently stroke my kind so i write it down:

• engine failure due to misuse (too high cht for too long, and others? maybe simulated by a persistent engine-condition property that simulates weardown over time, maybe also feed by the Implement proper oil friction Simulation #264 implementation simulating friction, probably the main source besides of age?)

[hbeni]

Close by #328