Created attachment 119662 [details]
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=sharing
Seems to replay ok on nvc0 and nv50 with mesa 11.0.4 and master.
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=sharing
swkotor, AA enabled on start: https://drive.google.com/file/d/0B42CQY2wGHumOFZDeWJlanFfTlE/view?usp=sharing
X3TC, AA disable on start: https://drive.google.com/file/d/0B42CQY2wGHumZVYyT1JhNkZUSk0/view?usp=sharing
X3TC, AA enabled on start: https://drive.google.com/file/d/0B42CQY2wGHumazNhVmpKVFBaZ3c/view?usp=sharing
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.
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.
Replays fine on Redwood XT (5670) with mesa 11.0.5.
As I already stated, the apitrace trace did not cause the problem to trigger. I am sorry for the misleading information.
The pp_jimenezmlaa options enable post processing AA options which may not be compatible with MSAA.
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.