On Sun, Nov 21, 2010 at 12:37 PM, Heiko Schulz wrote: > The problem isn't while the splash screen- it occurs for several seconds > after splash screen dissapeared- this will be the problem.
Yes, that is understood. Still, at least showing 1-2fps in the >splash screen phase< can be avoided, since this makes little sense and we _explicitly_ limit fps there. The problem with the scenery loader influencing the sim rate (being after start-up or during run-time) is another issue - a more fundamental one - and definitely not new. I also see an influence here, but not so severe, though my machine is older (and still a single core without hyper-threading...). And as James pointed out, this will heavily depend on system performance (especially core count and cache size). And, not sure, it may also depend on the OSG version. And I think there is also an environment option to influence the thread priority of the OSG loader - I'll see what can be done there. And there are more performance issues. At FSweekend we even saw the 24-core-12GB-RAM-Xeon-server-beast had brief hick-ups whenever crossing scenery areas (noticable moments with a freezing display <1 second). I think Torsten and Martin did some tests about this. > After that fps is stable, and really good ( I'm just flying above the alps, > visibility 71km, all shaders incl. contrails enabeld- stable fps of 31!). And that is welcome news... :) cheers, Thorsten ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
