>>Using Shared models helps saving memory. That way, only one model is >>loaded, and it is displayed multiple times. With static objects, every >>instance is loaded in memory, with duplicates on geometry and >>textures. Changing OBJECT_STATIC to OBJECT_SHARED helped having a >>decent fps over Paris, as well as reducing texture size to avoid GPU >>memory saturation.
Arnt Karlsen wrote: > ..an idea: Can an hangar model be used to make the EAA Museum at KOSH > http://sleepyhollowfarm.com/OshkoshAerialLarge.jpg by using the hangar > model several times and overlapping at corners to produce the EAA Museum > model? Is this a bad idea? Of course it can be and it's not a bad idea, but it wont look good. I prefer modelling those peculiar buildings from scratch 'cause that technique gets much better visual results. Take a look at http://fgfsdb.stockill.org/modeledit.php?id=277 and http://fgfsdb.stockill.org/modeledit.php?id=263 , you will get what I mean. Modelling something that look close to reality makes much more fun to me :-) And I've found a few nice picks of that Museum in the meanwhile. That will help me in modelling that in a manner which will not look completely different from reality. Your idea is quick and easy, and can be applied when no other solution is at hand IMHO. With such an approach I wouldn't care about z-buffer flickering, it would be the latest visual imperfection people will notice at all. Roberto _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
