Re: Texture problems

New Message Reply Date view Thread view Subject view Author view

Rob Jenkins (robj++at++quid.engr.sgi.com)
Mon, 11 May 1998 10:53:21 -0700

On May 11, 12:08pm, Jarrett Coffman wrote:
> Subject: Texture problems
> We have 3 Indigo2 MAX IMPACT machines, and on 2 of the 3 machines we are
> having trouble displaying textures. Grayscale textures look pinkish or
> distorted. We tried upgrading one of the "bad" machines from 2.0.4 to
> 2.2 and had the same problem.
>
> We think that it might be either an X server or OpenGL bug. When we run
> the program over the network and display it on another machine (O2) the
> textures look good.
>
> Anyone run across this before?

I have heard of exactly this when High Impact machines were upgraded to Max
Impact machines incorrectly. A Max Impact is essentially 2 High Impact pipes in
parallel ( parallel GEs and TRAM ) so the TRAM is duplicated internally. In
short a Max Impact with 4M TRAM actually has 2 X 4TRAM inside ( more texture
throughput rather than capacity ). If a High gets upgraded to Max but only has
one set of TRAM then this effect happens.

If it's not that then you could just have a dodgy TRAM board, even though it's
2 machines with the same problem it might be the same/similar HW problem on
both, one test would be to pull swap the system disk from a good machien to a
bad machine, if the problem follows the disk ( which I doubt ) then it's SW, if
the problem stays with the HW then I suggest you log a HW support call.

Cheers
Rob

-- 
________________________________________________________________
Rob Jenkins mailto:robj++at++sgi.com
Silicon Graphics, Mtn View, California, USA
=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer/
            Submissions:  info-performer++at++sgi.com
        Admin. requests:  info-performer-request++at++sgi.com

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:57:23 PDT

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