From: Adam K K. <ad...@vo...> - 2005-12-13 13:01:40
|
Roland Scheidegger wrote: > 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 > > Hello all. I've narrowed down this problem to something that changed in Mesa between the 5th of December and the 11th, when I first noticed this problem. I have a system at work with a 9800. I started up NWN (after first initializing the card with the fglrx driver, of course), and the textures looked just fine (though the fog problem still existed). The drivers were built from CVS on the 5th. I upgraded it to what's currently in CVS, started up NWN, and had the same texture problem. Adam |