Erik Hofman writes: > If it would be 27Mb only, there wouldn't be a problem for me because > FlightGear without dynamic objects leaves 39Mb spare memory.
The problem seems to be that there are a lot of extra SSG nodes attached to every tile in the cache (one ssgTransform and one ssgRange for every dynamic object, whether currently visible or not). The solution, I think, will involve using callbacks under the group LOD node to manage things so that SSG nodes are created only when needed. During a high-speed cross-country magic carpet ride, the memory usage got as high as 180MB before stabilizing (vs. 80MB without dynamically-placed objects). 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
