http://bugs.winehq.org/show_bug.cgi?id=32821
--- Comment #10 from Henri Verbeet hverbeet@gmail.com 2013-02-23 14:20:02 CST --- Created attachment 43685 --> http://bugs.winehq.org/attachment.cgi?id=43685 debug patch
(In reply to comment #8)
Created attachment 43683 [details] log from Star Wars Jedi Academy MP
WINEDEBUG="+tid,+d3d9,+d3d,+d3d_surface,+d3d_texture"
wine 1.5.24 mesa 9.1
Jedi Academy is an OpenGL application as far as I know, so wined3d doesn't have a lot of influence on performance there. The log seems to confirm that, all the D3D calls in there are just for getting hardware information like e.g. the amount of available video memory, it doesn't do any rendering using D3D. I'd say this one at least is purely a driver issue.
(In reply to comment #9)
Created attachment 43684 [details] log from Sims 3
Marek Olšák fixed some similar issues as my patches attached to those bugs did in commits 87f94e6f80dcdc3933edee24b1f7a6e355c4abaa and a0510fa7737eaaaafffd9748f603cf0231e8321a. (These should be in 9.1, but since my patches didn't help for you, these probably didn't either.) He also made the fallback quite a bit faster in commit ea63491629f48099371f725e7c3779f2982d7a52, but that's for Gallium3D based drivers only. Perhaps the attached (Mesa) debugging patch can give some more information about what formats are actually involved, but I really think the Mesa bugzilla is more appropriate for discussing this.
GLSL was disabled while creating a log, but with default options I have the same problem.
Disabling GLSL in general makes things worse for anything that isn't the proprietary NVIDIA driver, or cases where only reporting shader model 1 would improve performance. (And in the latter case there are other registry settings that are more appropriate.) But yeah, probably not the issue here.