Hi, just an idea: Most nasal code is done once a frame. Is this even true for frame rates greater than the internal update rate (120Hz)? If yes, the calculated delta t is zero, maybe this case was not considered when writing the code. Maybe we should not execute the nasal stuff, if no internal update was performed?
Maik Frederic Bouvier schrieb am 24.09.2007 23:11: > Selon Forums Virgin Net : > > >> Hi, >> I recently upgraded to 2 GB of memory, and also a much better Nvidia AGP >> Gigabyte 7600 GS card the old version of flightgear 0.9.10 flies now >> sometimes I get 150fps but the new OSG and concorde's latest updates have >> left it almost un-usable for me, at start up it often starts on it's side >> other times is spends 90% of the time at 0 fps, before I have even taxied or >> flown anywhere :( >> >> I was hoping to include the new concorde in part 3 of my movies but this does >> not look realistic now as their is no overhead at all for video capture. >> > > You should try to limit your frame rate to a reasonable value, either by > configuring the "Sync to Vblank" feature of your graphic driver, or by > enabling > the frame rate throttle inside FG ( --prop:/sim/frame-rate-throttle-hz=75 for > example ) > > -Fred > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
