20,741
edits
Failure Manager: Difference between revisions
Jump to navigation
Jump to search
→Status (06/2014)
| Line 22: | Line 22: | ||
|This is being worked on by galvedro, who's hoping to have most of this finished in time for 3.2 - it's basically a framework for registering triggers and allowing different types of failures to be modeled. | |This is being worked on by galvedro, who's hoping to have most of this finished in time for 3.2 - it's basically a framework for registering triggers and allowing different types of failures to be modeled. | ||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=207598#p207598 | |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=207598#p207598 | ||
|title=<nowiki>Re: Engine wear</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Wed Apr 30</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | |||
|A generalized wear/failure system is a good thing because this goes beyond just engine wear. With a generalized system we should be able to model things like brake, tire, propeller wear just to name a few. | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=207639#p207639 | |||
|title=<nowiki>Re: Engine wear</nowiki> | |||
|author=<nowiki>hvengel</nowiki> | |||
|date=<nowiki>Wed Apr 30</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | |||
|the other advantage is that this is going to be agnostic to the way it is controlled, i.e. there's a concept of a dedicated "failure manager", so that this can be hooked up to different front-ends, including a telnet/web-based front-end (e.g. instructor console), or even just an integrated Canvas/GUI dialog. | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=207640#p207640 | |||
|title=<nowiki>Re: Engine wear</nowiki> | |title=<nowiki>Re: Engine wear</nowiki> | ||
|author=<nowiki>Hooray</nowiki> | |author=<nowiki>Hooray</nowiki> | ||