20,741
edits
Failure Manager: Difference between revisions
Jump to navigation
Jump to search
→Status (06/2014)
| Line 115: | Line 115: | ||
|author=<nowiki>Algernon</nowiki> | |author=<nowiki>Algernon</nowiki> | ||
|date=<nowiki>Thu Jun 12</nowiki> | |date=<nowiki>Thu Jun 12</nowiki> | ||
}} | |||
}} | |||
{{cquote | |||
|I have tested most of it.<br><br>New failures:<br>McbfTrigger, TimeoutTrigger, MtbfTrigger, AltitudeTrigger, set_unserviceable, set_readonly all works.<br><br>Old failures:<br>Engine, gear, flaps, electrical, aileron, rudder, elevator, asi, altimeter, attitude still works.<br><br>I have yet to write a custom trigger or actuator, but I would say this system seems good designed, and very powerful. | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=212462#p212462 | |||
|title=<nowiki>Re: How does serviceable and failures work?</nowiki> | |||
|author=<nowiki>Necolatis</nowiki> | |||
|date=<nowiki>Thu Jun 12</nowiki> | |||
}} | |||
}} | |||
{{cquote | |||
|We will talk about this a bit later on when the FGUK guys have played with the module as well. But one thing that aircraft developers are demanding in one way or another, is to go one step further and do a more complex system damage/wearing, where failures influence each other, i.e. a structural failure here produces a system failure there and so on.<br><br>This kind of modeling is likely to be fairly aircraft specific, but we will see. I have given some thinking to a next evolutionary step in this direction, and it is quite tricky to organize in a clean way actually. | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=212474#p212474 | |||
|title=<nowiki>Re: How does serviceable and failures work?</nowiki> | |||
|author=<nowiki>galvedro</nowiki> | |||
|date=<nowiki>Fri Jun 13</nowiki> | |||
}} | |||
}} | |||
{{cquote | |||
|A fired triggerd remains fired until removed, or rearmed by using trigger.reset()<br><br>Custom triggers will not play well with the gui at the moment. For this first release I just squeezed the new engine underneath the existing gui, and the compatibility layer responds to it by emulating the former behavior (if it doesn't, it is a bug). That means that only Mtbf and Mcbf triggers are currently supported through the gui. | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=212516#p212516 | |||
|title=<nowiki>Re: How does serviceable and failures work?</nowiki> | |||
|author=<nowiki>galvedro</nowiki> | |||
|date=<nowiki>Fri Jun 13</nowiki> | |||
}} | }} | ||
}} | }} | ||