This morning, I checked in some patches to optimize random objects a little more. These changes should help in all circumstances, but should be especially useful for high-altitude, high-visibility, high-speed situations, where the tile loader is very busy. I just tried taking the a4 from KSFO to KSEA on autopilot at 20,000ft and --visibility=40000 with random objects enabled, and there were no serious lockups (at least, none long enough to confuse the autopilot while I was having lunch elsewhere).
These changes may also cut memory usage a little more, bringing it closer to the memory usage with --disable-random-objects. There is also a (smaller) chance that these changes will improve framerates somewhat for people with faster cards, since they reduce the amount of CPU work in each frame. On the down side, no randomly-placed object will ever be visible when you are further than 20,000m (20km) from the center of the tile where it is located, no matter what range you specify for it -- we can fiddle with that number later. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
