[Bug 104549] [radeonsi] [wine] [apitrace] Silent Hunter 3 2D texture artifacts / corrupted 3D redering on Polaris
https://bugs.freedesktop.org/show_bug.cgi?id=104549
Bug ID: 104549 Summary: [radeonsi] [wine] [apitrace] Silent Hunter 3 2D texture artifacts / corrupted 3D redering on Polaris Product: Mesa Version: 17.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: banana_banana_banana@gmx.net QA Contact: dri-devel@lists.freedesktop.org
Silent Hunter 3 under wine (2.21 staging / 3.0rc4 as well) renders flickering corrupted textures that seem to be UI elements all over the place for some of its rendered frames, also 3D scene gets trashed every now and then.
Game worked fine on my previous hardware (intel Haswell HD4600) and same mesa version 17.3.1, replaying the trace recorded while using polaris hardware renders correctly on intel HD4600 (it is noteworthy however, that replaying the trace throws more fragment shader errors on intel, so it could be possible it renders with no errors because of missing shaders?).
Apitrace: https://drive.google.com/open?id=1182dA2LQp91izaPf0vOf9yS1ZZMz246F
https://bugs.freedesktop.org/show_bug.cgi?id=104549
--- Comment #1 from _archuser_ banana_banana_banana@gmx.net --- Trying some stuff and stumbled on a strange side effect: when preloading 32bit build of mesa master branch of radeon_dri.so the trace runs without glitches, however wine can not be started this way as ts excepet 64bit libs.
https://bugs.freedesktop.org/show_bug.cgi?id=104549
--- Comment #2 from _archuser_ banana_banana_banana@gmx.net --- ommit my last commit , apparently something changed and my build script produces a 64bit radeon_dri.so that somehow works , will investigate this further,
https://bugs.freedesktop.org/show_bug.cgi?id=104549
_archuser_ banana_banana_banana@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #3 from _archuser_ banana_banana_banana@gmx.net --- Kernel update (4.15.6-1 -> 4.15.7-1) fixed the issue, was a possible drm driver issue/regression.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org