David Megginson said: > On Sat, 1 Jan 2005 21:44:35 +0000, Dave Martin <[EMAIL PROTECTED]> wrote: > > > > http://www.diamond-air.at/Pressebilder/DA42TwinStar/Panel/tn/DA42panel_high > > >.jpg.html > > > The visual model is easy enough but the panel is a different matter. > > We can probably manage the left display. The right display (moving > map with elevation shading) would be extremely difficult, but it's > appearing in so many planes that we'll have to bite the bullet some > day. > > > That kind of complexity of systems is probably impossible for a 3d cockpit > > (lack of usable font system?). > > The 3D part is easy -- there are relatively few moving parts to > animate. The challenge will be creating dynamic textures to show on > the displays, and that's going to require rolling up our sleeves and > doing a lot of C++ OpenGL coding. >
Wouldn't it make sense to start with something like the atlas generated data? I mean, we'd probably want to cache it to disk anyway...dynamic updating of that data could be added later. Best, Jim _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
