As the original author of the 2D instrument code, I *strongly* advise
against building 2D instruments. Since I switched to an all 3D panel in the
plane I'm working on, my framerate has gone from 10-15 fps to 20-30 fps
(admittedly on a low-end card), even with larger textures. I think that the
only thing missing from the 3D animation code now is text, and that should
be easy to add.
For the FPS Flat Panel Display System that I'm trying to make, a text feature is almost essential.
We'll need to support the 2D code for a while because there are so many
existing instruments that use it, but it's a serious mistake to start a new
2D instrument at this point. The 2D code still requires 3D rendering (since
the instruments appear in a 3D scene graph), so there are no gains, but I'm
guessing that the texture stacking for 2D instruments causes OpenGL state
changes that are expensive, at least with my graphics card (GeForce2Go).
Alright then. I'll convert my intrument(s) to 3D.
-- Roy Vegard Ovesen
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
