On Sun, 9 Jun 2002, David Bronaugh wrote:

> Hey all,
> 
> I was playing quake3 on my laptop here (which has a 3D Rage Pro chip)
> and noticed a few problems with the rendering. Here are comparison shots
> (taken with identical settings) on my TNT2 and on the Mach64-based card:
> 
> http://bronaugh.linuxboxen.org/q3dm1_tnt2.jpg
> http://bronaugh.linuxboxen.org/q3dm1_mach64.jpg
> 
> This is with the latest CVS (downloaded last night).
> 
> Map was q3dm1. Lightmap lighting was enabled, GL extensions were
> enabled, texture detail was the same (second from highest), geo. detail
> was medium. High quality sky was off (it just distracts).
> 
> You can see clearly the major rendering glitch with the mach64 on the
> walls - the texture just isn't integrated as it should be.

I've noticed those particular textures as well.  My guess is that it could
be a result of the card not being able to modulate alpha values for the
GL_MODULATE texture environment.  This is a conformance problem that can't
be worked around without essentailly making all textured polygons software
fallbacks.  In most games I've tested with, GL_MODULATE is the most used
texture environment (Quake3 uses it almost exclusively, I think).  The
more recent builds of Quake3 have some workarounds for the RagePRO that
fix transparency problems with smoke trails and such which were evident in
the demo, however.  Having said all that, I haven't actually verified that
this is the problem in this particular case, but I have seen texture
transparency problems in UT that I know are because of this hardware
limitation.

I think once we merge in the current Mesa fixes from the DRI trunk, we can
look at fixing any remaining GL compliance problems (there are still
failures with glean tests at the moment).  However, some compliance
problems like the one with GL_MODULATE are hardware limitations that we'll 
have to live with if we want hardware acceleration.
 
> Also, there's no mipmapping, but that's less of an issue.

Mipmapping is broken on mach64, unfortunately.  ATI's Windows drivers 
don't support mipmapping either.
 
> Any ideas? I'd love to help here, but I don't know where to start.
> 
> David Bronaugh
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas - 
>http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> 
> _______________________________________________
> Dri-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/dri-devel
> 

-- 
Leif Delgass 
http://www.retinalburn.net





_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - 
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to