Stephane Marchesin wrote:
Philipp Klaus Krause wrote:
Adam K Kirchhoff schrieb:
I'm sure this confirms what are already known issues with the r300
driver, but felt it'd be worth posting anyway. There's definitely
something bizarre going on with textures. They're much crisper with the
fglrx driver.
To me it looks like the fglrx driver does linear filtering, while r300
does nearest filtering.
It could be the mipmap selection offset that fglrx applies to textures.
There's a setting for this reg on r200 (see the
R200_EMIT_PP_TRI_PERF_CNTL reg), it probably applies to r300 too.
That setting doesn't affect mipmap selection - just how the transition
area from one to another mipmap looks like. You'd only get banding as
the worst thing possible.
Looks like nearest filtering to me too, and/or no mipmaps (so yes mipmap
selection offset (LOD setting?) could be an issue there but if so it
would be ways off).
No idea what's wrong with the inventory there - some issue with
transparent textures? Strange that not the whole inventory gets affected
exactly the same way though.
Roland
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
