From: <fiers...@zo...> - 2010-11-20 10:33
> I have done two  tests, directly after eachother. Same conditions, same METAR.

One thing to note here is that, prior to yesterday's update, the size
of the scenery area loaded/rendered at start-up did _not_ depend on
the visibility (weather/METAR), neither on any visibility configured
manually (command-line etc). FG would always load the same number of
tiles at start-up - no matter what the weather/configuration was. This
was a bug, since the tile manager didn't bother about visibility
changes - and METAR/manually configured visibility was only set
_after_ the initial scenery was already scheduled.
This has changed yesterday: now, once visibility increases
considerably (METAR is received, weather configured) this, as
expected, causes an immediate update and loading of all required
scenery.

So, even if you have configured the same conditions/METAR, this may
not be a fair comparison. It's possible that METAR specifies 10nm
visibility, but an older FG build would still render only 5nm at
start-up (meaning only a quarter of the actually required scenery
tiles). With older FG builds, you should wait for METAR to be
received, then fly (or reposition) your plane several miles away from
the initial location. This location change triggers the scenery
scheduler which only then takes the correct visibility into account.
I doubt though that this could cause such a severe drop of framerate.
And which plane are you using for this comparison?

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

Reply via email to