except a bit of 'time' i.e. the 2D Panel is likely to be a bit faster due to simpler geometry, esp if your 3D instruments have things like bezels etc..
You can still use a single textured triangle (or rectangle) with a transparent background for the bezel with the 3D code if you want -- in fact, that's how most people making 3D instruments do it. In general, you use geometry for big, obvious things like 1 cm knobs, and textures for smaller, flatter details.
Again, the 3D animation code does all the same kind of animations that the 2D code does (except text, for now) -- converting an instrument involves only a few changes to the XML config file. However, the 3D code is well integrated with the plib scene graph and runs efficiently, while the 2D code is not integrated with plib and makes some expensive changes in the OpenGL state.
All the best,
David
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
