David Luff said: > "Curtis L. Olson" <[EMAIL PROTECTED]> writes: > > > I have also seen > > some wierdness in the tile scheduling/caching lately too. I'm not sure > > what's going on there. I started to investigate, but ran out of time the > > day I was looking at it. It seems like at times we get into a situation > > where the tile cache isn't big enough for the set of local tiles and it > > thrashes. That shouldn't happen, but there are some wierd view manager > > dependencies in there that I'm not even close to understanding. > > > > That could be my fault. The new AI traffic determines ground elevation in the same manner as the fdm, and can probably significantly pollute the tile cache since much of the traffic still exists out of visual, but within radio, range. I've been testing a patch whereby the AI traffic simply uses the airport elev when out of visual range, and switches to 'proper' elevation if it comes within visual range, which should significantly alleviate this problem. >
That would help a lot. I'm trying to recall the ground level test, but I'm wondering if it would just make sense to have a variation of the function that simply returned the ground elevation from the primary FDM whenever the tile below was missing. We should be able to have a query will never trigger a tile load. Maybe two or three options for default responses when the tile isn't there (e.g. FDM ground elevation, starting airport elevation, or invalid value like -999999.99) Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
