https://bugs.winehq.org/show_bug.cgi?id=44682
Bug ID: 44682 Summary: Kingdom Come: Deliverance, The Witcher 3: low performances Product: Wine Version: 3.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs@winehq.org Reporter: ben@tokidev.fr Distribution: ---
Using the nvidia latest proprietary drivers and wine-3.3, it seems there are low performances on both Kingdom Come: Deliverance and The Witcher 3 (despite, for the later at least, bug #42592 being marked as fixed in 3.3). This is using CSMT (by explicitly enabling it in the registry), and with __GL_THREADED_OPTIMIZATIONS=0 (as suggested by the aforementioned bug report).
Yet when using wine-2.21-staging with CSMT, performances are much better. Using wine-3.3-staging (the new 3.x rebased staging fork by alesliehughes@github) with CSMT does not seem to produce good results either (that is, not better than normal 3.3).
As an example, for Kingdom Come: Deliverance with details set to high on a 1070TI and in the exact same conditions:
* Wine 3.3 produces ~5 to 10 FPS. * Wine 3.3-staging produces roughly the same. * Wine 2.21-staging produces ~20 to 30 FPS.
The results are similar in The Witcher 3 (3.3 is pretty laggy in ultra, although almost playable; 3.3-staging is the same; yet 2.21-staging makes the game completely playable at the same level of details and performances are better by at least twice).
There are no explicit messages in the log that may suggest an easily identifiable cause.
https://bugs.winehq.org/show_bug.cgi?id=44682
duozerk ben@tokidev.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian
https://bugs.winehq.org/show_bug.cgi?id=44682
duozerk ben@tokidev.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3dx11 |directx-d3d
https://bugs.winehq.org/show_bug.cgi?id=44682
Shmerl shtetldik@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |shtetldik@gmail.com
--- Comment #1 from Shmerl shtetldik@gmail.com --- Is it a dup of bug 44315?
https://bugs.winehq.org/show_bug.cgi?id=44682
--- Comment #2 from duozerk ben@tokidev.fr --- Possibly, although if it's the same that bug report suggests the issue *should* occur in 2.21-staging as well. I'm currently compiling a 3.3 with wine-pba (as per the bug report you linked) to confirm if it helps or not.
https://bugs.winehq.org/show_bug.cgi?id=44682
--- Comment #3 from duozerk ben@tokidev.fr --- After testing with 3.3-staging + all patches from wine-pba, I can confirm that the issue almost disappears (I say almost because I get around ~20 FPS compared to ~25 FPS with 2.21-staging; but the game is clearly playable).
So I think this is indeed a dupe; would you kindly close the bug report/mark it as a dupe (seems I can only set it as resolved) ? I've already linked both apps to #44315.
https://bugs.winehq.org/show_bug.cgi?id=44682
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=44682
Neko-san nekoNexus@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nekoNexus@protonmail.ch