Created attachment 2658 [details]
rendering errors in foobillard

could you try with the patch from this bug:
I noticed missing triangles in some demo. That demo worked well with this patch.

https://bugs.freedesktop.org/show_bug.cgi?id=2195

(In reply to comment #2)
> could you try with the patch from this bug:
> I noticed missing triangles in some demo. That demo worked well with this patch.
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=2195
> 

I wish I could, but I can't compile.

You need to get Mesa sourcecode out of CVS and then apply the patch.
http://mesa3d.org/cvs_access.html

I made a new one against todays Mesa-CVS.

(In reply to comment #4)
> You need to get Mesa sourcecode out of CVS and then apply the patch.
> http://mesa3d.org/cvs_access.html
> 
> I made a new one against todays Mesa-CVS.
> 

Unfortunately it didn't help.
I think that the flickering may have something to multitexturing or lighting.
(when I disable rendering reflections for the balls, they are drawn properely
but the table still flickers)

> Unfortunately it didn't help.
> I think that the flickering may have something to multitexturing or lighting.
> (when I disable rendering reflections for the balls, they are drawn properely
> but the table still flickers)
Since you mention reflections, this could potentially be caused by the app using
GL_SPHERE_MAP for texcoord generation. This will cause a tcl fallback (since the
original radeon chips can't handle that), and might cause rendering errors if
the application assumes the fragments generated are the same as without using
texgen. If that's the case (not sure if the errors shown in the screenshot could
be caused by that), try disabling tcl (use driconf or tcl_mode=0).

> try disabling tcl (use driconf or tcl_mode=0).

this also didn't help

This does sound like an app bug.  While I couldn't reproduce on an rv200 with
foobillard 3.0a, I was able to produce similar problems by zooming way in on the
cue ball, and there was obvious z fighting.

Grzegorz Nimoski
Do you still experience this issue with newer drivers ?
Please check the status of your issue.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/263.