http://bugs.winehq.org/show_bug.cgi?id=35776 Bug ID: 35776 Summary: Crysis is extremely slow in Wine 1.7.14 Product: Wine Version: 1.7.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: kol(a)MV8660.spb.edu Wine 1.7.14 brings an extreme slowdown in Crysis and I found that this is caused by two regressions. 1) With Crysis under plain Wine 1.7.14 I see constant flickering and the game shows less than 1 FPS. This is a regression introduced by the commit commit 4c4552c5a1910a9d5adf8eccff0ac62d89ffe376 Author: Ken Thomases <ken(a)codeweavers.com> Date: Wed Feb 19 16:14:53 2014 -0600 wined3d: Restore the pixel format of the window whose pixel format was actually changed. A similar problem is considered in Bug#35767 and patches suggested there do not help as well as for that bug. This commit also affects some old games (TES3:Morrowind, TES4:Oblivion) but slightly: it gives about 5 FPS less than in Wine 1.7.13. 2) But after reverting the above commit I see nevertheless that Crysis shows significantly less FPS than with Wine 1.7.13 (average 30 FPS with 1.7.14 versus 45 FPS with 1.7.13). The second problem is caused by commit c1032e977bb9f850e3aea28dd79e3d7c2244cd6c Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Tue, 4 Mar 2014 10:21:33 +0100 wined3d: Filter redundant WINED3D_MAP_DISCARD buffer maps. After reverting both commits in Wine 1.7.14 I see the same framerates as in 1.7.13 in all games. It is interesting that Wine with Command Stream patches by Stefan Doesinger encounters only the first problem but the second commit does not cause slowdowns. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.