Re: [Flightgear-devel] 0.7.8 precompiled for win32

[Curtis L. O. <cu...@fl...>]

David Megginson writes:
> I'm running an Nvidia GeForce2 Go (a stripped-down, low-power notebook
> version with 32MB texture memory), and using AGPGART, and I also see a
> bit of a hit from JSBSim, though nothing like yours.
> 
> To run my tests, I renamed ~/.fgfsrc so that FlightGear would not use
> any hidden settings, and unset the FG_SCENERY environment variable so
> that it would use the default scenery in the base package rather than
> one of my custom builds.  Logging is disabled for all of these, but
> output is not redirected.
> 
> Here are the results (FlightGear defaults to an 800x600 window):
> 
> fgfs --start-date-lat=2001:07:25:12:00:00 --aircraft=c172 --fdm=larcsim --disable-intro-music --disable-panel
> 
> Unpaused: 51-53fps
> Paused:   52-54fps
> 
> fgfs --start-date-lat=2001:07:25:12:00:00 --aircraft=c172 --fdm=larcsim --disable-intro-music --disable-panel
> 
> Unpaused: 45-46fps
> Paused:   51-52fps
> 
> I also tried reducing the model-hz (the number of times the model is
> run per second) from 120 to 60.  JSBSim still handles OK, and there is
> a slight framerate improvement:
> 
> fgfs --start-date-lat=2001:07:25:12:00:00 --aircraft=c172 --fdm=larcsim --disable-intro-music --disable-panel --model-hz=60
> 
> Unpaused: 48-49fps
> Paused:   52fps
> 
> Curt: where did your profiling show the greatest hit?

If I recall it was in JSBSim/FGMatrix ...  Jon sent me an update to
that file which didn't seem to change things too much.  I need to
build another profiling version and look again.

Curt.
-- 
Curtis Olson   Human Factors Research Lab       FlightGear Project
Twin Cities    cu...@hf...                cu...@fl...
Minnesota      http://www.menet.umn.edu/~curt   http://www.flightgear.org