>> You can enable a better property to compare performance using "View" => >> "Show worst-case frame delay". It shows the longest delay in between two >> frames within the last second of simulation (lower left corner). The >> lower the number, the better. In order to maintain an acceptable 25Hz >> simulation, the frame delay must never exceed 40ms. >> Is anyone capable of running FlightGear with either global or local >> weather enabled with a frame spacing not exceeding 40ms?
Quick test at KSEA with the F-16 and current METAR, cloud visibility range 20 km, dynamical weather off (as I said, that is indeed much slower): Local 25-48 ms, 48 fps indicated Global 25-50 ms 40 fps indicated I hold to what I stated earlier... * Thorsten ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
