Re: Preloading of textures

New Message Reply Date view Thread view Subject view Author view

Angus Dorbie (dorbie++at++bitch.reading.sgi.com)
Thu, 16 May 1996 18:54:42 +0100

More RM's doesn't add texture capacity, just framebuffer memory & pixel fill.
The previous post was about RM5's (16Mb texture no matter how many).

Same rules apply to iR.

Rgds,
Angus.

On May 16, 12:39pm, Stephen Maher wrote:
> Subject: Re: Preloading of textures
>
> > Hi,
> > I'm running on an Onyx RE/2 (5.3) with 2 RM5s. I've experienced problems
> > with preloading textures (in GL). I understand that an RM4 has 4 Meg of
>
> I recently observed the same thing and was about to ask the Net!
>
>
> We have an Onyx RE2 (5.3) with 2 RM4s. Instead of calling
> istexloaded(), I simply timed (gettimeofday) how long each
> successive texdef/texbind took. (I also actually drew
> the texture to prove to me it was there :) I did NOT use
> TX_FASTDEFINE.
>
> As soon as I hit 4MB of textures - whammo! - about an order of
> magnitude slower - telling me paging had kicked in. (2 RM4's is
> 8MB of textures, supposedly ;).
>
> The kicker was when I tried it on an Onyx RE2 with *1* RM4 (4 MB);
> I got the same results!
>
> What gives?
>
> Steve
>
> --
> Stephen.Maher++at++gsfc.nasa.gov (301) 286-3368
> Scientfic Visualization Studio (f) (301) 286-1634
> Code 932 NASA Goddard Space Flight Center
>
>
>-- End of excerpt from Stephen Maher

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:52:53 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.