I've had just occasion to compare performance of a GIT binary compiled on Nov 24th with a GIT binary compiled Nov 13th in one of my standard benchmark tests (which I described a while ago), and the test confirmed an impression I had yesterday in just test-flying - I've lost almost 1/3 of available framerate.
The flags are --enable-fullscreen --geometry=1920x1200 --disable-real-weather-fetch --enable-auto-coordination --timeofday=noon --airport=KINS --aircraft=ufo followed by spawning a cold sector tile and observing framerate upon loading and when fully loaded. Multitherading support is 'Automatic'. With empty sky (in otherwise default condition) I get 180 fps with the Nov 13th binary and 130 fps with the new one. With the cumulus clouds fully spawned, I get 80 fps with the Nov 13th binary and 55 fps with the recent one. Less formal, my impression from yesterday was that I get 20 fps where I used to have 30 which ties in well with the above numbers. The only difference is the binary - fgdata/ and the set of comandline options are completely identical. Am I the only one? Cheers, * Thorsten ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
