Norman Vine said: > Ah... OK but keep in mind you are still drawing all of the Panel even if it is not > all in view, this includes all of the 'state changes' taking place in the 2D code that > aren't necessarily happening in the 3D code and SSG might also be smart enough > to optimize some of these 'state changes' to no-ops or at least minimal-ops. > AFAIK the 2D code doesn't do any 'OpenGL state' optimization. >
A. With the c172p in 3D mode on my lowly 32mb geforce2mx at KSFO: - View angle with panel in view 20 fps. - View angle slightly up so panel disappears below bottom of frustrum, but scenery still the same, 32 fps. B. With the c172p in 2D mode on the same lowly geforce2mx at KSFO: - 2D panel screen, 28 fps. - 2D panel screen off, 44 fps. C. With the pa28-161 3D Instruments: - 3D instrument panel at default view angle: 32 fps. - View angle slightly up: 38 fps. It looks like what everyone is saying holds true. The biggest savings here is with 3D instruments vs the 2D panels mapped to 3D cockpits (C vs A). No surprise. One interesting thing I picked up on that didn't occur to me before: it seems that the translucent prop disk object ends up costing 2-3 fps while in the cockpit view. I wonder if it is "worth the cost". Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
