Created attachment 31208 [details] incorrect cubemap Git mesa/ddx & drm-next on rv670 AGP. I've only just tried this so don't know if it has ever worked. Pressing "f" several times to cycle through the filter types with mesa/progs/demos/cubemap reveals that some combinations result in incorrect rendering compared to swrast. example attached.
(In reply to comment #0) > Created an attachment (id=31208) [details] > incorrect cubemap > > Git mesa/ddx & drm-next on rv670 AGP. > > I've only just tried this so don't know if it has ever worked. > > Pressing "f" several times to cycle through the filter types with > mesa/progs/demos/cubemap reveals that some combinations result in incorrect > rendering compared to swrast. > > example attached. > This is now working for me. My testing hasn't been that regular recently, so I am not sure when the fix happened.
Created attachment 33765 [details] new cubemap corruption
(In reply to comment #1) > This is now working for me. Must have been a fluke - it seems like if other games/demos have been run first it has a chance of looking OK. If however it is the first thing I run then it's always corrupt, although I can't get it to look like the original screen shot I posted. Tried running several recent kernels,UMS,KMS,PCIE gart or AGP gart - all show the same corruption as attached. Once other apps have run the square is likely not to show, the black around the edges needs f pressing and only seems to show on filters involving nearest.
Created attachment 40333 [details] current 600c cubemap Have been using a rv790 for a while and cubemap rendered OK with that a couple of weeks ago. Testing current gits again with my rv670 AGP box, there is still corruption but things have changed a bit. Gallium shown no corruption. Classic only shows corruption around the red section on the sphere and only when the filter contains mipmap.
Working OK now with current git.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.