20,741
edits
Canvas MFD framework: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→Design) |
No edit summary |
||
| Line 76: | Line 76: | ||
|title=The making of the Queen | |title=The making of the Queen | ||
|author=Hooray |date= Mon Oct 14, 2013 5:02 am}}</ref>|Hooray}} | |author=Hooray |date= Mon Oct 14, 2013 5:02 am}}</ref>|Hooray}} | ||
{{cquote | |||
|<nowiki>Canvas & Nasal are still fairly low-level for most aircraft developers, to come up with good -and fast displays (code)- people still need to be experienced coders, and familiar with FlightGear scripting and Canvas technologies/elements and the way performance is affected through certain constructs. So far, we now have the means to create the corresponding visuals, but there's still quite some work ahead to re-implement existing hard-coded displays - but to implement a compelling jet fighter, including a credible cockpit, you would need more than "just" the visuals, i.e. lots of handbooks/manuals, building blocks for creating systems and components, and scripting-space frameworks to help with the latter. | |||
The best option to pave the way for this is to keep on generalizing existing code, so that instruments support multiple instances, multiple aircraft, and multiple "sensors". Here, galvedro's work is really promising. But for the "visual" side of this, we really need to generalize our NavDisplay code much more - so that we can factor out MFD related functionality, and reuse it on fighters like the m2000-5.</nowiki> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211061#p211061 | |||
|title=<nowiki>Re: Does FlightGear has Multiplayer Combat mode?</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Thu May 29</nowiki> | |||
}} | |||
}} | |||
<references/> | <references/> | ||