Howto:Extending Canvas to support rendering 3D models: Difference between revisions

Howto:Extending Canvas to support rendering 3D models (view source)

642 bytes added , 22 February 2015

m

20,741

edits

@@ Line 6: / Line 6: @@
 == Background ==
 There are several scenarios where we cannot currently use Canvas because we're lacking a means for rendering a 3D model to a texture - omega95 once mentioned that some modern avionics are increasingly using 3D representations [http://forum.flightgear.org/viewtopic.php?p=164243#p164243][http://forum.flightgear.org/viewtopic.php?f=71&t=17278&p=164260&]. Equally, a typical FlightGear GUI front-end will usually require a way for previewing aircraft 3D models.
 Currently, we cannot use Canvas for any of these use-cases because there's no way to load 3D models.
+Given the increasing focus on extending the Canvas-based [[Aircraft Center]], supporting 3D models via Canvas simply makes sense at some point:
+{{FGCquote
+  |As we move forward with FlightGear development and future versions, we will be expanding the "in app" aircraft center.  This dialog inside flightgear lets you select, download, and switch to any of the aircraft in the library.
+  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33451055/
+     |title=<nowiki>Re: [Flightgear-devel] Citation II for base package?</nowiki>
+     |author=<nowiki>Curtis Olson</nowiki>
+     |date=<nowiki>2015-02-17</nowiki>
+   }}
+}}
 == Approach ==