Angus Dorbie (dorbie++at++bitch.reading.sgi.com)
Tue, 31 Oct 1995 23:13:35 +0100
I've noticed that when loading flight format files into performer 2.0 on
High IMPACT + TRAM option the Iris GL implementation seems to use 8 bits
per component but the Open GL implementation uses 4 bits per component
(eye balling). 5 bits per component internal on ONYX would use less
memory, it depends what your loader is doing.
Also a mipmapped minifacation filter would use more texture memory than
one without mipmaps, although possibly a smidgen less than you are seeing.
Could this be some minification filter default issue?
Just a couple of wild guesses.
Rgds,
Angus.
On Oct 31, 5:23pm, bmcquear++at++dw3f.ess.harris.com wrote:
> Subject: Textures
>
> Hi,
>
> We recently accquired an Impact (High AA Impact / TRAM Option Card) and
> are trying to run an application that previously ran on an Onyx, and
> Indigo 2 Extreme.
>
> Our application is implemeted in Performer 2.0, but linked with Iris GL
> (temporarily). The problem is that I'm trying to read in a large
> textured database (dwb format), and the texture is not being loaded in.
> One strange thing is that I can telnet to the Impact from an Indy, run
> the application, and all the textures are loaded and displayed.
>
> I also tried to load the application with perfly on the Impact, but
> again the textures were not displayed. The output from notify indicates
> that the total texture use goes above 100% of the RM (for example
> "Total Texture Use = 137 % of 4 MB Raster Manager" ).
>
> Any ideas or explanations would be greatly appreciated.
>
> Thanks,
> Bruce McQueary
>
>
>-- End of excerpt from bmcquear++at++dw3f.ess.harris.com
-- Angus Dorbie, Silicon Graphics Ltd, UK dorbie++at++reading.sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:51:59 PDT