https://bugs.winehq.org/show_bug.cgi?id=49233
Bug ID: 49233 Summary: World of Wacraft (WoW) slow fps with the dx11 modern renderer Product: Wine Version: 5.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: blue-t@web.de Distribution: ---
Created attachment 67238 --> https://bugs.winehq.org/attachment.cgi?id=67238 Output with the legacy renderer
Since 8.1.5 the game has 3 renderers dx11, dx11 legacy and a modern dx12 renderer.
With my amd rx480 it is impossible to use the dx11 modern multi-threaded renderer to play. It results in single digit fps. The single threaded legacy renderer works.
Based on comparing the attached logfiles the only obvious difference is fixme:d3d11:d3d11_device_CreateDeferredContext1 iface 0000000013850120, flags 0, context 000000014293F108 stub!
https://bugs.winehq.org/show_bug.cgi?id=49233
--- Comment #1 from Ker noa blue-t@web.de --- Created attachment 67239 --> https://bugs.winehq.org/attachment.cgi?id=67239 Output with the modern renderer
https://bugs.winehq.org/show_bug.cgi?id=49233
Sveinar Søpler cybermax@dexter.no changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax@dexter.no
--- Comment #2 from Sveinar Søpler cybermax@dexter.no --- The renderer called dx11 legacy is the renderer used prior to 8.1.5, and was renamed and kept for compatibility. The new one utilizes multithreading and possibly other tweaks.
It is the same for my nVidia RTX2070, so it is not driver/gpu dependant.
https://us.forums.blizzard.com/en/wow/t/new-graphics-apis-in-8-1-5/121542
https://bugs.winehq.org/show_bug.cgi?id=49233
Ker noa blue-t@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #67239|0 |1 is obsolete| |
--- Comment #3 from Ker noa blue-t@web.de --- Created attachment 67487 --> https://bugs.winehq.org/attachment.cgi?id=67487 Crashlog
Now it isn't just slow with the modern renderers d3d11&d3d12, but it crashes before the loading screen is reached. Something regarding the multi threading changed in 5.10-staging
https://bugs.winehq.org/show_bug.cgi?id=49233
--- Comment #4 from Ker noa blue-t@web.de --- Created attachment 67488 --> https://bugs.winehq.org/attachment.cgi?id=67488 Crashlog with the d3d12 renderer
https://bugs.winehq.org/show_bug.cgi?id=49233
Ker noa blue-t@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|World of Wacraft (WoW) slow |World of Wacraft (WoW) |fps with the dx11 modern |crashes with the dx11/12 |renderer |modern renderers
https://bugs.winehq.org/show_bug.cgi?id=49233
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #5 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Ker noa from comment #3)
Created attachment 67487 [details] Crashlog
Now it isn't just slow with the modern renderers d3d11&d3d12, but it crashes before the loading screen is reached. Something regarding the multi threading changed in 5.10-staging
Hello,
Open a new bug for the new issue (if there isn't one already), and put the new bug number in the depends on field.
And for the new issue, a regression test between 5.9-5.10 would help.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49233
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|World of Wacraft (WoW) |World of Wacraft (WoW) slow |crashes with the dx11/12 |fps with the dx11 modern |modern renderers |renderer
--- Comment #6 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Also, don't change issue when the older one may still be present, hidden by the new issue.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49233
--- Comment #7 from Ker noa blue-t@web.de --- I wouldn't call it a regression. d3d11_device_CreateDeferredContext1 was a stub in 5.9-staging https://github.com/wine-staging/wine-staging/commit/0db92c336fcea4c383a15056... extended that function and now we probably moved on from being slow due to not being multi threaded to a buffer overflow because the implementation is not complete.
The underlying issue is still incomplete multi-threading so it is justified to keep the issue and change the symptoms accordingly.
https://bugs.winehq.org/show_bug.cgi?id=49233
--- Comment #8 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Ker noa from comment #7)
I wouldn't call it a regression. d3d11_device_CreateDeferredContext1 was a stub in 5.9-staging https://github.com/wine-staging/wine-staging/commit/ 0db92c336fcea4c383a150560f1034cd9cf76366 extended that function and now we probably moved on from being slow due to not being multi threaded to a buffer overflow because the implementation is not complete.
Ok, then it's not a regression.
The underlying issue is still incomplete multi-threading so it is justified to keep the issue and change the symptoms accordingly.
I still think that it should be separate bugs.
The low fps issue is a more generic issue that will get fixed when multi-threading gets implemented properly. That's the main reason why multi-threading is needed.
Fixing the crash may not be sufficient to fix the low fps.
The crash is only a temporary issue that will get resolved when the implementation becomes more complete.
There could be more implementation issues while multi-threading gets implemented (crashes, things not working properly). Those should be reported as separate bugs so that we can keep track of them individually without touching the main bug.
Otherwise, this will be a 'multi-threading' metabug with a big mess of multiple issues and metabugs should be avoided when possible.
Also, valid bugs should not be recycled.
Regards.
-
WineHQ Bugzilla