Created attachment 101017 [details] Incorrect weapon rendering Hi! I try to play Serious Sam 3 BFE using Mesa and r600g driver, and I get incorrect rendering of the weapon - it's rendered "diagonal" (see the screenshot). Linux kernel is Debian's 3.14.4-1.1, but most of the system is i386. Mesa is 10.1.2 from Debian repos. Card is ATI Mobility Radeon HD 4670. OpenGL renderer string: Gallium 0.4 on AMD RV730 OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile Is it a known issue?
The bug also reproduces on newer mesa 10.1.4 (just updated).
Just built 10.2.1 - the bug also reproduces on it.
(In reply to comment #0) > Linux kernel is Debian's 3.14.4-1.1, but most of the system is i386. Mesa is > 10.1.2 from Debian repos. I've meant "Linux is 3.14.4-1.1 amd64, but most of the system is i386"
Anyone?
Linux 3.16.5, Mesa 10.4.0-devel git, the bug still there.
Can you try with sb disabled, set then envvar "R600_DEBUG=nosb".
Created attachment 109305 [details] OK with R600_DEBUG=nosb It seems it's OK with nosb (although the frame rate seems lower)
(In reply to Vitaliy Filippov from comment #7) > It seems it's OK with nosb OK, this is maybe related to issue I have : https://bugs.freedesktop.org/show_bug.cgi?id=86165 (In reply to Vitaliy Filippov from comment #7) > although the frame rate seems lower Yes, "sb" is the enhanced r600g GLSL compiler. So disabling it decrease the performance.
Maybe... so the only thing that is left is to get response from someone who can fix it? :) It's also interesting that the same commit e9822f77a9cc024f528d30382fd5ad21c73a173b is also mentioned in bug 77288...
(In reply to Vitaliy Filippov from comment #9) > Maybe... so the only thing that is left is to get response from someone who > can fix it? :) Absolutely.
The bug does not reproduce anymore with current mesa 11.3
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.