https://bugs.winehq.org/show_bug.cgi?id=53718
Bug ID: 53718 Summary: WoW Beta/PTR get "Your 3D accelorator card is not supported" Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: mckittrick.kaminski@gmail.com Distribution: ---
Created attachment 73148 --> https://bugs.winehq.org/attachment.cgi?id=73148 Collection of Retail and Beta logs.
I had be playing/testing the new Dragonflight expansion for WoW recently, and after this week's update, the game no longer launches, with the age old "Your 3D accelerator card is not supported" error. Research on previous occurrences of this error have been fruitless, usually having something to do with multiple GPUs and having the wrong one assigned.
Being that the WoW client updating was the only change to cause this issue, and native Windows clients seem to have no issue, I can't help but think this lies somewhere in wine, dxvk, or vkd3d namespace.
For information on my environment, I'm running via Lutris, and have tried both Lutris and Wine runners, a few releases from 5.x, 6.x, and 7.x, up to 7.17 staging. I'm using dxvk v1.10.3 and vkd3d v2.6. My graphics card is 3060Ti, and I get the error with both the 470xx and 515 nvidia drivers. The 3060Ti is the only VGA controller in my system, and I'm running Arch 5.19.9. Manually setting the 'gxApi "D3D11"' config line in Config.wtf doesn't change the behavior, which applies to D3D11, D3D11_LEGACY, as well as D3D12.
I'll note that this error only occurs with Beta and PTR clients. (PTR is open to everyone, if you'd like to test, not sure if you need gametime). Retail and Classic both work just fine and haven't any issue, although, I've noticed the in-game option to use D3D12 has disappeared, leaving me with only D311 options. It used to be there, and I'm unsure when the option left.
I've attached logs from both Beta and Retail, let me know what else I can provide/test for y'all.
https://bugs.winehq.org/show_bug.cgi?id=53718
mckittrick.kaminski@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mckittrick.kaminski@gmail.c | |om
https://bugs.winehq.org/show_bug.cgi?id=53718
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |oneofone@gmail.com
--- Comment #1 from Zeb Figura z.figura12@gmail.com --- *** Bug 53722 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #2 from Zeb Figura z.figura12@gmail.com --- DXVK is not supported in this bug tracker; can you reproduce the issue with plain wine (wined3d)?
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #3 from Ahmed W. oneofone@gmail.com --- Created attachment 73153 --> https://bugs.winehq.org/attachment.cgi?id=73153 log without any dlls set to native
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #4 from mckittrick.kaminski@gmail.com --- Created attachment 73157 --> https://bugs.winehq.org/attachment.cgi?id=73157 Fresh wine prefix
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #5 from mckittrick.kaminski@gmail.com --- I have an update, and I know it may not fall in scope of this bug reporting site, but I've been able to get past this issue. WoW Beta/PTR are successfully seeing the Graphics card, and running at 60fps max settings just fine with the following setup.
Using Bottles caffe-7.15 runner dxvk-1.10.3 vkd3d-proton-2.6-1-5b73139 dxvk-nvapi-v0.5.4
I installed vkd3d-proton on my system via the AUR (arch obv) using the `vkd3d-proton-git` package. I'm not sure if Bottles is using my system vkd3d or its own.
I intend to try to drop caffe-7.15 runner into my non-working prefix under lutris soon.
https://bugs.winehq.org/show_bug.cgi?id=53718
nerzhul loic.blot@unix-experience.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |loic.blot@unix-experience.f | |r
--- Comment #6 from nerzhul loic.blot@unix-experience.fr --- Thanks for reporting, exact same issue on Archlinux and RX 6800 AMD card since their weekly build from this week
https://bugs.winehq.org/show_bug.cgi?id=53718
Chris Sutcliff chris@sutcliff.me changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chris@sutcliff.me
--- Comment #7 from Chris Sutcliff chris@sutcliff.me --- It works for me on 7.18 wine-staging but not on older wine versions (dxvk 1.10.3)
https://bugs.winehq.org/show_bug.cgi?id=53718
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #8 from joaopa jeremielapuree@yahoo.fr --- As already pointed previously, dxvk is not supported in this bugzilla, so reports with used dxvk are pointless. Does the bug still occur with a fresh wineprefix?
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #9 from Chris Sutcliff chris@sutcliff.me --- (In reply to joaopa from comment #8)
As already pointed previously, dxvk is not supported in this bugzilla, so reports with used dxvk are pointless. Does the bug still occur with a fresh wineprefix?
well it doesn't work at all without dxvk, with or without latest staging.
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #10 from Chris Sutcliff chris@sutcliff.me --- Created attachment 73170 --> https://bugs.winehq.org/attachment.cgi?id=73170 plain wine-staging output
This is the output from running it in a fresh wine-staging prefix.
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #11 from Ahmed W. oneofone@gmail.com --- I still can't launch it with or without dxvk on a clean prefix.
https://bugs.winehq.org/show_bug.cgi?id=53718
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #12 from Zeb Figura z.figura12@gmail.com --- How easy would this be for a Wine developer to reproduce? Can you by chance provide instructions?
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #13 from Ahmed W. oneofone@gmail.com --- You will need to install battle.net, then under World of Warcraft select "Public Test Realm" then hit play.
I'm not 100% sure if you need a subscription or not to download it.
Also once downloaded you can try to start it directly from path/to/World Of Warcraft/_ptr_/WowT.exe
https://bugs.winehq.org/show_bug.cgi?id=53718
pphop jondotsb@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jondotsb@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #14 from nerzhul loic.blot@unix-experience.fr --- Note: i just go working on wine-staging. You need DXVK and run on Wayland, not X11. I don't know where is the difference on game detection, maybe wine side ?
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #15 from Ahmed W. oneofone@gmail.com --- @nerzhul can you post `Logs/gx.log` from the ptr/beta folder?
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #16 from nerzhul loic.blot@unix-experience.fr --- I have a second discussion here on official forum where you have mine and another user with similar setup
https://eu.forums.blizzard.com/en/wow/t/dragonflightptr-launch-broken-on-lin...
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #17 from Chris Sutcliff chris@sutcliff.me --- I'm that other user
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #18 from Ahmed W. oneofone@gmail.com --- I can't post on the beta forums, can you guys confirm it works on ptr as well? (wine on wayland).
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #19 from nerzhul loic.blot@unix-experience.fr --- i confirm on PTR it works also with wine-staging, wayland and dxvk
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #20 from Ahmed W. oneofone@gmail.com --- I can't reproduce on plasma wayland at least :-/
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #21 from nerzhul loic.blot@unix-experience.fr --- the fix is somewhere between wine-staging 7.0 and 7.18, but it's pretty huge to read (20k lines diff), if someone has idea on which file to search, i read 2k of them already but i'm n,ot very inspired about the changes on it :)
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #22 from nerzhul loic.blot@unix-experience.fr --- sorry ignore my previous commit, wine 7.18 (non staging) works also on my side, it's not a staging patch which fix the detection on Linux. I don't know what is the difference with proton-ge or wine-ge for this part
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #23 from Ahmed W. oneofone@gmail.com --- I still can't get it to run with neither plasma wayland nor gamescope, however you can always try to run a bisect (https://git-scm.com/docs/git-bisect) to see which commit fixed it.
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #24 from nerzhul loic.blot@unix-experience.fr --- i'll try to test various wine packages bisecting version fixing it this weekend
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #25 from nerzhul loic.blot@unix-experience.fr --- i just did some tests on Archlinux packages from archive (https://archive.archlinux.org/packages/w/wine/) (with DXVK)
Works on: * wine-staging 7.12 * wine-staging 7.4 * wine-7.1 * wine-6.11
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #26 from nerzhul loic.blot@unix-experience.fr --- regarding previous comment, didn't tested with X11, only wayland
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #27 from nerzhul loic.blot@unix-experience.fr --- i didn't tested yet with all wine but i work again with Proton with this weekly build (proton-ge-custom 7.37), then as it was the worst situation compared to vanilla wine, i think it should re-work with all wine versions
https://bugs.winehq.org/show_bug.cgi?id=53718
--- Comment #28 from Ahmed W. oneofone@gmail.com --- As of today, the beta runs fine on normal wine and wine-tkg.