ATI R600g Gains Mip-Map, Face Culling Support

[nanonyme]

I demand that this bug gets fixed in r300g!

*cough* There's a bug in that screenshot too.

[rohcQaH]

geartrain with nvidia (mobile, Quadro NVS 145M, basically a 8xxxM):


I demand that this bug gets fixed in r300g!

[netkas]

btw, latest mesa borked q3

[nanonyme]

(and otherwise too, vertices were just my first guess)
ps. I hate the one-minute edit window.

[nanonyme]

somebody need to check it on nvidia linux drivers.

This would prove nothing. Someone (more competent in OpenGL than I) needs to read geartrain.c and check the vertices.

[netkas]

somebody need to check it on nvidia linux drivers.

[marek]

Yeah, we are damned lucky that the hardware doesn't lock up (that's what usually "undefined" means).

[nanonyme]

This is most probably not a driver bug. swrast, llvmpipe, softpipe, r300c, and r300g render it the same as is on your screenshot.

My eyes claimed swrast rendering differed a bit but was still incorrect. Hence why I started wondering about invalid polygons since rendering is undefined there and might even be unexpected in a different way in all drivers.

[marek]

Well, found a bug, hope Glisse reads this thread sometimes

This is most probably not a driver bug. swrast, llvmpipe, softpipe, r300c, and r300g render it the same as is on your screenshot.

[nanonyme]

Actually it looks a bit odd with Software Rasterizer as well. Could someone check whether or not geartrain polygons are valid? (edges not allowed to intersect, region must be convex) If some are invalid, it would explain strange rendering. I'm not experienced enough to just see validity by scanning through the code.