Guillermo E. Gutierrez (ggutierr++at++hisd.harris.com)
Tue, 26 Jan 1999 18:33:57 -0500
Phil, I think you're right. Perfly must have been doing (in older versions)
some texture decimating to load in bigger textures. I just ran perfly with
that geometry (and texture) on an Indigo2 MaxImpact with the TRAM option card
and here's the output I got...first from the 2k tex file, then from the 1k tex
file. The actual texture looked identical both times. Also xv loaded both
textures and while reporting that one was indeed 1024x1024 and the other
2048x2048, they both looked identical as well. BTW, the Indigo2 is running
IRIX 6.2 with performer_eoe 2.0.1 and performer_eoe.sw32.ogl_performer 2.2. I
guess my only issue now is why the new performer_eoe (2.2.1) and
performer_eoe.sw32.ogl_performer (2.2.3) on 6.5.2f won't automatically decimate
the textures like before. Instead I get this big "blank" texture.
Thanks for clearing things up.
-gg
ggutierr++at++harris.com
----------2k texture--------
PF Loading texture:
PF File name = scanned/wickham_2k.rgb
PF Image size (SxTxR) = 2048x2048x1
PF Download size = 1377 pages
PF Total hardware texture use =2234 Pages
PF Download size = 8388608 bytes
PF Download time =5787.475 ms
PF Download rate = 1.382 MB/sec
PF Total texture use = 12.188 MB
PF This texture uses = 200.000% of 4MB memory
PF Total texture use = 304.688% of 4MB memory
----------1k texture--------
PF Loading texture:
PF File name = scanned/wickham_1k.rgb
PF Image size (SxTxR) = 1024x1024x1
PF Download size = 349 pages
PF Total hardware texture use =1206 Pages
PF Download size = 2097152 bytes
PF Download time = 265.547 ms
PF Download rate = 7.532 MB/sec
PF Total texture use = 6.188 MB
PF This texture uses = 50.000% of 4MB memory
PF Total texture use = 154.688% of 4MB memory
This archive was generated by hypermail 2.0b2 on Tue Jan 26 1999 - 15:32:38 PST