Re: Texture problems
Rob Jenkins (robj++at++quid.engr.sgi.com)
Mon, 11 May 1998 11:53:54 -0700
On May 11, 2:47pm, Hansong Zhang wrote:
> Subject: Re: Texture problems
> >
> > 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.
> >
>
> Here at UNC we've been having problems with texture mapping on MaxImpacts
> since day one. One of the problems is that texture can appear interleaved
> with black or gray lines. Since Max users here don't seriously use textures
> the problem not got high priority and remains still there.
>
> Recently a network guy working on a MaxImpact happened to notice that a
> board was only loosely plugged in, so he proceeded to push it home - and
> therefore solved the texture problem on that machine :-) We have yet to
> check whether boards in other Impacts are really in their slots.
>
> Hansong
>-- End of excerpt from Hansong Zhang
That sounds like badly seated TRAM boards, the most common cause of texture
funny business on TRAM. Do be careful about touching this stuff your self
though as it's super sensitive to static, if in doubt, have an SGI SE check the
HW out.
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
This archive was generated by hypermail 2.0b2
on Mon Aug 10 1998 - 17:57:23 PDT