On Fri, 27 Feb 2004 11:25:00 -0600, "Curtis L. Olson" <[EMAIL PROTECTED]> wrote in message <[EMAIL PROTECTED]>:
> David Luff wrote: > > Whilst on the subject of initialisation order, currently the tile > > manager gets initialised before an initial position is set. This > > means that it loads a set of tiles centered on lat/lon of 0,0, and > > then loads a set of tiles at the correct location. In conditions of > > limited visibility, this can result in forced tile deletion messages > > and a stutter during forced deletion at some point in the flight > > since the tilemanager thinks it can't keep up with deletion, but is > > in fact due to having twice as many tiles as necessary (exacerbated > > by the fact that visibility doesn't get picked up properly for > > several iterations). Moving the tile manager init to occur after > > the view manager init would be a good thing IMHO, to prevent the > > loading of bogus tiles. (I've been testing this for a while, and it > > doesn't seem to break anything). > > Hmmm, the tile manager *needs* to be initialized before the FDM > because the FDM *needs* to know ground elevation for ground trimming, > and we can't determine that until the local tile is loaded. ..ok, "the FDM needs to put its feet on something", but _does_ FG need to _show_ that first tile? Or, can FG "close its eyes", as in "Is there enough visibility"? ..ignore my dumb question if it doesn't help weed out red herrings. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
