Logs please.
Are you using dxvk along side?

Edit: Or what mbriar wrote below. Keep forgetting about that

You probably forgot to install d3d12core.dll or to set an override to native for it

@mbriar that is already set, as stated, 2.8 works. Added log for 2.8 to my comment. Will install 2.9 and see if it generates a log.

@Blisto91 I do have dxvk installed for Classic.

Vkd3d-proton 2.8 didn't come with d3d12core.dll and thus didn't need it to be installed or overridden. Relying on d3d12core.dll is new in 2.9.

21 May 2023, 17:37 by @.***:

@mbriar https://github.com/mbriar> that is already set, as stated, 2.8 works. Added log for 2.8 to my comment. Will install 2.9 and see if it generates a log.

@Blisto91 https://github.com/Blisto91> I do have dxvk installed for Classic.

—
Reply to this email directly, > view it on GitHub https://github.com/HansKristian-Work/vkd3d-proton/issues/1565#issuecomment-1556209354> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A3G6J6PHGLYOBEXCS55RC73XHIZC7ANCNFSM6AAAAAAYJOAIFY> .
You are receiving this because you were mentioned.> Message ID: > <HansKristian-Work/vkd3d-proton/issues/1565/1556209354> @> github> .> com>

@mbriar Are you saying that 2.9 has a D3D12core.dll that I need to install? The override is set in wine.

Yes 2.9 ships both a d3d12.dll and a d3d12core.dll and both are required now

Edit: I checked that game with Proton and didn't have any issues.

gx.log

@Blisto91 When the install script ran, it looks like it copied the d3d12core.dll to wine. Do you think I need to remove DXVK?

attached gs.log, after installing 2.9

Removing DXVK to see if that helps.

No. dxvk (it's dxgi.dll) just needs to be 2.1 or above.

Can you run the game from a terminal and attach the output? As a extra you can run it together with WINEDEBUG=+loaddll so we can also see the dll's loaded.

@Blisto91 Apparently my DXVK was 2.0. Removed it and game runs now with 2.9. Going to upgrade to Geforce rtx 4060 as my family is getting me a father's day gift. I am happy to just continue, as I believe part of the issue is my older 950 that may part of the problem.

Glad do hear your got it working :+1:
Note that vkd3d-proton and dxvk development is somewhat tied together on some fronts and is the officially supported way, so i'd advise using it along side dxvk (2.1 minimum) if you run in to any issues. But if it's working now thats good ofc.

Vkd3d-proton 2.9 requires at least dxvk 2.1 as stated in the changelog.

I will install dxvk 2.1, just to be in compliance. Going to close this issue now, and appreciate all the help.

Notice that 2.8 and 2.9 were taking long time to load, and reverted to dx11. Installed 2.7 vkd3d-proton, and completely removed DXVK. Attached file shows that DX12 was used, and the login screen came up instantly.
Wow-gx-log-showing-dx12-with-version-2-7-vkd3d proton.txt

My question is why does an older vkd3d-proton let my card run dx12 but the newer ones do not?

5/21 16:37:17.366 Bad CM2Light*: 000000000607fc28 Could this be the root of the problem, and what does it point to?

Newer versions of vkd3d-proton need DXVK to be installed. The logs you posted look pretty useless because they contain no wine or vkd3d-proton output at all, if you're still having trouble, set WINEDEBUG="+loaddll" and VKD3D_DEBUG=warn and post a log with that.

Yeah somehow retail WoW really doesn't like 2.9

Running it on Manjaro KDE
6.3.x Kernel
530.41 NVidia 2060

Trying to run the game via Lutris with Lutris-GE-Proton8-6.

With 2.8 the game launches perfectly fine, with 2.9 it fatal errors after the blizzard launcher.

Started initial process 134630 from gamemoderun /home/node/.local/share/lutris/runners/wine/lutris-GE-Proton8-6-x86_64/bin/wine /home/node/Gaming/Games/Battle.net/drive_c/Program Files (x86)/Battle.net/Battle.net.exe --exec=launch WoW
Start monitoring process.
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
[0522/041828.557:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
[0522/041829.127:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0
[0522/041829.256:ERROR:dxva_video_decode_accelerator_win.cc(1405)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E)
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
[0522/041831.860:ERROR:angle_platform_impl.cc(40)] rx::SwapChain11::reset(615): Could not create additional swap chains or offscreen surfaces, HRESULT: 0x80004005
[0522/041831.861:ERROR:gl_surface_egl.cc(787)] EGL Driver message (Critical) eglCreateWindowSurface: Bad allocation.
[0522/041831.861:ERROR:gl_surface_egl.cc(1394)] eglCreateWindowSurface failed with error EGL_BAD_ALLOC
[0522/041831.861:ERROR:in_process_command_buffer.cc(450)] ContextResult::kSurfaceFailure: Failed to create surface.
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
wine client error:54c: write: Bad file descriptor
wine client error:43c: write: Bad file descriptor
Initial process has exited (return code: 0)
wine: Call from 000000007B013D6E to unimplemented function d3d12core.dll.D3D12GetInterface, aborting
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.

Could we get full logs please. Together with WINEDEBUG="+loaddll" and also VKD3D_DEBUG=warn if vkd3d-proton doesn't print anything.

Edit: @TerohsLab Also make sure you are using Lutris v0.5.13 (or beta2) else the extra vkd3d-proton dll isn't supported out of the box.

wine: Call from 000000007B013D6E to unimplemented function d3d12core.dll.D3D12GetInterface, aborting

This means that is issue is what I said in my very first reply and that you didn't install d3d12core.dll correctly.

Oh ok ... thats probably the issue then. I'm still on Lutris 0.5.12.

Did you guys figure this out? :slightly_smiling_face:

I'm launching WoW from Steam with Proton Experimental, the game also doesn't allow me to choose DX12 renderer. Arc A770 Mesa Git btw.

On Intel it's probably a different problem (but also very unlikely to be a vkd3d-proton bug) but post a proton log if you want something better than wild guesses.

On Intel it's probably a different problem (but also very unlikely to be a vkd3d-proton bug) but post a proton log if you want something better than wild guesses.

It is vkd3d problem, proton 7 does expose DX12 option in World of Warcraft, proton experimental does not.

Post the log.

WoW-Proton.log
Here, WoW doesn't allow it to launch in dx12 mode, it straight goes to dx11.

9258.862:0668:066c:err:vkd3d-proton:vkd3d_init_device_caps: Lacking support for single texel alignment.

It's because d2ad4f2532d68bd introduced more strict feature checks and that fails on Intel without: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/23263

Workaround for the Intel ANV issue
https://github.com/HansKristian-Work/vkd3d-proton/pull/1576

A new Proton Experimental has been pushed with the Intel ANV work around

A new Proton Experimental has been pushed with the Intel ANV work around

Thanks I tested it and it works, but I updated to latest mesa git where single texel alignment was enabled. Sadly the performance in dx12 is worse than in dx11 mode, I guess anv is not there yet compared to radv.

Also, sorry for a bit offtop but the game doesn't allow me to enable Variable Rate Shading. It says I need a capable of shader model 6 videocard. Is that a VKD3D problem or ANV?

Vkd3d-proton likely as the issue is known also with amd radv. We are not sure exactly what the game is looking for as we haven't gotten it working yet by faking various stuff.

There was a wow forum post recently where they said that the lack of "barycentrics" in the driver was causing the game to default to Shader model 5.0 There was a change on 24th May and it will now go to SM6.0 but not 6.5 which I believe is what is required for VRS?

my gx.log shows:

GpuInfo: sm:dx_6_0, rt:DXR 1.1, vrt:2, bary:0, mesh:1 pull:1

@csutcliff thank you for the hint. Will check it out.

@SteveEbey73742 @TerohsLab Friendly ping. Did you figure out your original issues?

@csutcliff Hey nice. Even without the radv barycentric MR it looks like with the new update i'm able to use RT Shadows and VRS out of the box now just with VKD3D_CONFIG=dxr11 RADV_PERFTEST=rt

@Blisto91 strange, that enables RT shadows for me but VRS is still "unsupported for graphics related reasons"

What is your GPU

Edit: You could try along with VKD3D_FEATURE_LEVEL=12_2 or VKD3D_SHADER_MODEL=6_6 or both just to see if that does anything.

What is your GPU

6900XT, currently mesa-git and vkd3d-proton git but same with latest release version of both.

You could try along with VKD3D_FEATURE_LEVEL=12_2 or VKD3D_SHADER_MODEL=6_6 or both just to see if that does anything.

Neither made a difference.

hm. odd

@Blisto91 nope, have not tried. I will be upgrading to GTX 4060 ti after father's day, june 18. I plan to install the latest versions of DXVK and VKD3D at that time, per the instructions given here, to see if that works. My current gtx950 is probably too old for some of the advanced features that seem to be enabled in 2.9. I am able to use 2.7 for DX12 in retail and classic. I may try VKD3D 2.7 with my new card, to have a baseline to start with, before I install the latest DXVK and VKD3D.

@Blisto91 For me it was because of an outdated Lutris install 0.5.12 which couldn't handle the new linking stuff.

I reverted back to 2.8 of vkd3d which fixed all my issues playing via Lutris.

Once 0.5.13 Lutris landed in my distro i've been playing on vkd3d 2.9 with no issues at all.

My RTX 4060 ti works with dxvk 2.2 and vkd3d 2.9 setting dxr11 does ray tracing and dx12.

Yay! 🎉