https://bugs.freedesktop.org/show_bug.cgi?id=92952
Bug ID: 92952 Summary: Enabling Anti-Aliasing in swkotor causes screen to corrupt Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel@lists.freedesktop.org Reporter: EoD@xmw.de QA Contact: dri-devel@lists.freedesktop.org
Created attachment 119662 --> https://bugs.freedesktop.org/attachment.cgi?id=119662&action=edit glxinfo
When I start swkotor.exe via wine and I enable AA I get a totally corrupted screen: http://imgur.com/95HHd6v and after alt-tabbing: http://imgur.com/QzqGJfA
Here is an apitrace: https://drive.google.com/file/d/0B42CQY2wGHumalllYjVqQ1NJSEk/view?usp=sharin...
https://bugs.freedesktop.org/show_bug.cgi?id=92952
--- Comment #1 from Ilia Mirkin imirkin@alum.mit.edu --- Seems to replay ok on nvc0 and nv50 with mesa 11.0.4 and master.
https://bugs.freedesktop.org/show_bug.cgi?id=92952
EoD EoD@xmw.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |timon37@gmail.com Summary|Enabling Anti-Aliasing in |Enabling Anti-Aliasing |swkotor causes screen to |causes screen to corrupt |corrupt |
--- Comment #2 from EoD EoD@xmw.de --- I just found another game with the same issue: X3 Terran Conflict When I enable AA it behaves the same way as swkotor with AA enabled
swkotor, AA disabled on start: https://drive.google.com/file/d/0B42CQY2wGHumalllYjVqQ1NJSEk/view?usp=sharin... swkotor, AA enabled on start: https://drive.google.com/file/d/0B42CQY2wGHumOFZDeWJlanFfTlE/view?usp=sharin...
X3TC, AA disable on start: https://drive.google.com/file/d/0B42CQY2wGHumZVYyT1JhNkZUSk0/view?usp=sharin... X3TC, AA enabled on start: https://drive.google.com/file/d/0B42CQY2wGHumazNhVmpKVFBaZ3c/view?usp=sharin...
https://bugs.freedesktop.org/show_bug.cgi?id=92952
--- Comment #3 from EoD EoD@xmw.de --- I should have mentioned that the apitrace replays just fine on both 32bit and 64bit apitrace executables.
The 3rd game with probably the same issue is Borderlands 2. Same screen garbage while all the replays are fine.
https://bugs.freedesktop.org/show_bug.cgi?id=92952
--- Comment #4 from EoD EoD@xmw.de --- I found the cause of the issue. It only happens if both of the following options have a value>0 in the .drirc:
<option name="pp_jimenezmlaa" value="0" /> <option name="pp_jimenezmlaa_color" value="0" />
I am not sure if this is a bug or if the error was on my side. If it is not bug, feel free to close it.
https://bugs.freedesktop.org/show_bug.cgi?id=92952
--- Comment #5 from Christoph Brill egore@gmx.de --- Replays fine on Redwood XT (5670) with mesa 11.0.5.
https://bugs.freedesktop.org/show_bug.cgi?id=92952
Christoph Brill egore@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Enabling Anti-Aliasing |[APITRACE] Enabling |causes screen to corrupt |Anti-Aliasing causes screen | |to corrupt
https://bugs.freedesktop.org/show_bug.cgi?id=92952
EoD EoD@xmw.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|[APITRACE] Enabling |Enabling Anti-Aliasing, |Anti-Aliasing causes screen |when pp_jimenezmlaa and |to corrupt |pp_jimenezmlaa_color are | |set, causes screen to | |corrupt
--- Comment #6 from EoD EoD@xmw.de --- As I already stated, the apitrace trace did not cause the problem to trigger. I am sorry for the misleading information.
https://bugs.freedesktop.org/show_bug.cgi?id=92952
Alex Deucher alexdeucher@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NOTABUG
--- Comment #7 from Alex Deucher alexdeucher@gmail.com --- The pp_jimenezmlaa options enable post processing AA options which may not be compatible with MSAA.
https://bugs.freedesktop.org/show_bug.cgi?id=92952
--- Comment #8 from EoD EoD@xmw.de --- Can't you disable the postprocessing AA when MSAA is enabled? Or at least give a huge warning/error message in such a case?
It took me a very long time to figure the problem out (neither an error, nor any other way of telling me the correlation) and I am pretty sure there are many more people out there encountering the bug.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org