Hello,
> > > Hmm, that depends. If those textures should be displayed > all the time (like a > livery), then yeah, I agree, one big texture is better than > many smaller ones, > also depending on your texturing needs. On the other hand, > if you're not > displaying half the texture most of the time, I think > that's wasted VRAM, that > could be freed for another texture of the same size. This > might seem just a > bit of wasted memory, but when you have 10-15 different > buildings with such > textures things start to add up, and you'd be using as much > memory as for > 20-30 different buildings, and where you have a detailed > village you could have > two or more. > > Just my o.o2RON on the matter :P > Emilian > Yes, interesting thought, I understand. But I always thought that the process of loading and unloading textures settles down the perfomance and that'y why it is better to have them only loaded once and keep them in VRAM. But maybe this only true when you not use any .dds-textures. I guess with .dds-textures it would make sense to have them then seperated. Cheers Heiko ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
