http://bugs.winehq.org/show_bug.cgi?id=34495
--- Comment #4 from Ben thebenj88@gmail.com 2013-09-20 02:57:41 CDT --- (In reply to comment #3)
Then it's likely a directx-d3d bug ( see http://bugs.winehq.org/describecomponents.cgi?product=Wine ).
As we don't know if it is an nvidia binary driver bug, could you try the following:
- How does it look if you use mesa software rendering?
- How does it look with nouveau?
- Does the demo have the same issue (if it could get running)?
Did you rate the app "Platinum"? Have you tried wine 1.5.17 as in the test? Every user (also me) who looks in the appdb thinks the game should run without any issues with that version? So should be pretty easy to find the regression, shouldn't it? What did you change between that test and now?
Were there some game updates?
I've attempted to run the game with the Nouveau driver, but it was unable to make it to the main menu (d3d call failed (0x8876086c) : D3DERR_INVALIDCALL).
I've not tried the demo yet, I'll get onto that soon.
As for the review I submitted (Wine version 1.5.17), I was using an AMD card at the time with the Catalyst driver. Using wine 1.5.17 with the NVIDIA drivers has not solved the problem.
However, there have been a number of small game updates since that test. So it's possible that the game updates are causing the issue, or it could be a NVIDIA driver problem.
The earlist NVIDIA test data that I can find is using wine 1.5.4 and NVIDIA 302.07. The test did not mention this issue, had a platinum rating. Unfortunately, I have no details from any other AMD users, so I don't know if this is a NVIDIA-specific issue.