* Erik Hofman -- Friday 21 April 2006 09:29:
> Melchior FRANZ wrote:
> > Note that several textures are loaded multiple times! 

> The best way to handle this is to create a caching mechanism where the 
> absolute 
> path of the texture is the key and the texture-id is cached for future use.

Yes. And this would even be quite easy to do. We'd need to incorporate plib's
SGI loader into fg/sg, and make it the preference
 
  ssgAddTextureFormat(".rgb", fgLoadSGI);

etc. Then we can do whatever optimizations make sense. Of course, this would
suggest that we more strongly depreciate all other texture formats for the
time being. Maintaining our own SGI loader is really no problem. It's a very
stable and well understood process.

It's bad enough that the Nimitz consumes no less than 64,081,920 MB, but that
the Eisenhower uses *as* much, even though it's floating around in a different
part of the world is really irresponsible. (And to make it clear: that's not
Vivian's fault. The 512x512 super-high-res halo for the deck "mule"s beacons
seems to be an accident. And that it's loaded 28 times, well ...)

The texture list also uncovered one of my bugs:  empty.rgb -> 262144 Bytes!?
Huh? That's "empty"? Argh, I committed the wrong texture. The real one is
just 640 Bytes. (Heh, don't look into the false one -- it's secret!)

m.


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to