Curtis L. Olson writes: > > Here's what I get sitting still at the default location, no panel or > > hud, with a GeForce2Go, 32MB, 800x600x32, with the latest Linux > > drivers (I'm using the latest plib CVS, but I assume you are as well): > > > > no dynamic objects: ~40fps > > dynamic objects (latest code): ~34fps > > dynamic objects (old code): ~32fps > > My frame rate trends typically are more in line with yours. However, > with the latest cvs code, default startup aiport, no hud, no panel, > I'm seeing: > > dynamic objects (latest code): ~23-24fps > no dynamic objects (latest code): ~75fps > > So I am seeing a huge difference with dynamic objects on vs. off.
Trying fresh this morning, I can see a bigger difference, though not so big as yours. For consistency, I'm using the following command line (substituting false where appropriate): fgfs --start-date-gmt=2002:07:18:20:00:00 --disable-panel --prop:/sim/rendering/dynamic-objects=true As soon as FlightGear starts, I hit Shift-B to hold the plane in place. dynamic objects: ~28fps no dynamic objects: ~41fps Note that the plane is not moving, so the new object loading/unloading code should have little effect after the first couple of seconds. I have a couple of hypotheses: 1. Removing per-object LOD tests and using only per-triangle LOD tests has hit us harder than expected, possibly because of some large triangles. 2. Bypassing culling for empty object branches is more expensive than expected. I'm going to experiment with #1 first, since it's simpler to change. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
