Sounds like this issue: https://github.com/doitsujin/dxvk/issues/2316
We already have a workaround that's supposed to disable all the CUDA-specific stuff if device creation fails once, but if that no longer works on current drivers, there's not much we can do and you'll need to manually load the kernel module in question prior to running games outside of Steam.
well until 1.9.2 i could play without installing cuda and just the basic binary driver. Why is it required now?
Cuda interop is required for DLSS support. You don't need Cuda installed for DXVK to work.
The problem is that the Nvidia Vulkan driver just fails to create a device with these extensions enabled if nvidia_uvm.ko isn't loaded. Since this is a well-known issue, DXVK detects that and tries to create a Vulkan device without those extensions, but for some reason it still fails to create a device on your system.
nvidia_uvm is loaded here. any more debug information i can provide?
I have all my dxvk dlls linked to a "latest" directory so i can easily switch between dxvk versions by just updating the latest directory symlink.
That's weird, what distro are you on and are you running this inside a container or something?
openSUSE Tumbleweed.
no container. but apparmor. though there are no violations logged. The only thing I do is blocking of the execution of nvidia-modprobe. It feels wrong that every wine app should be able to do that.
I just did a double check "hey lets see if all dlls are actually linked properly"
find -type l -name "d[3x]*.dll" -ls | sed -e "s|${HOME}/Games/||g"
547061200 0 lrwxrwxrwx 1 darix users 46 Jan 13 13:29 ./drive_c/windows/system32/d3d9.dll -> dxvk/latest/x64/d3d9.dll
547060669 0 lrwxrwxrwx 1 darix users 51 Jan 13 13:29 ./drive_c/windows/system32/d3d10core.dll -> dxvk/latest/x64/d3d10core.dll
546681677 0 lrwxrwxrwx 1 darix users 47 Jan 13 13:29 ./drive_c/windows/system32/d3d11.dll -> dxvk/latest/x64/d3d11.dll
547427906 0 lrwxrwxrwx 1 darix users 45 Jan 24 18:51 ./drive_c/windows/system32/dxgi.dll -> dxvk/1.9.4/x64/dxgi.dll
1077226325 0 lrwxrwxrwx 1 darix users 46 Jan 13 13:29 ./drive_c/windows/syswow64/dxgi.dll -> dxvk/latest/x32/dxgi.dll
1077226339 0 lrwxrwxrwx 1 darix users 46 Jan 13 13:29 ./drive_c/windows/syswow64/d3d9.dll -> dxvk/latest/x32/d3d9.dll
1077226340 0 lrwxrwxrwx 1 darix users 51 Jan 13 13:29 ./drive_c/windows/syswow64/d3d10core.dll -> dxvk/latest/x32/d3d10core.dll
1077226341 0 lrwxrwxrwx 1 darix users 47 Jan 13 13:29 ./drive_c/windows/syswow64/d3d11.dll -> dxvk/latest/x32/d3d11.dll
while in the dxvk directory i see a lot more dlls. a reinstall with setup_dxvk.sh install --symlink did not change the find output.
d3d10_1.dll is not symlinked.
Same with Gentoo , dxvk latest . I can fix it by running first Blender and render a model then closing it . After that game works fine no error .I dont know what blender does caparing env vars no changes.
Happens in RDR2 game also Fail to create device wine + native vulkan only .
Same with Gentoo , dxvk latest . I can fix it by running first Blender and render a model then closing it . After that game works fine no error .I dont know what blender does caparing env vars no changes. Happens in RDR2 game also Fail to create device wine + native vulkan only .
maybe check if any kernel modules got loaded during the blender step
@TURING-V2
I can fix it by running first Blender and render a model then closing it .
lol
If you can't (or don't want to) load nvidia_uvm on system boot or use modprobe (for some reason),
you can just "ping" cuda or opencl on linux + nvidia. Driver will load nvidia_uvm by itself.
#include "cuda.h"
int main() {
return cuInit(0);
}
#include <CL/cl.h>
int main()
{
cl_platform_id id;
cl_uint platforms;
return clGetPlatformIDs(1, &id, &platforms);
}
Compile and use like $ init-dlss && wine game.exe or init-dlss && %command% in steam.
uvm was loaded. but the cuda part apparently wasnt when i last time tested this.
plus couldnt dxvk include this init code above to trigger it?
nvidia-modprobe -u -c=0, fixes this
@darix Did you figure out your issue? Or is it still a problem
d3d10_1.dllx1 2022-01d3d10core.dllx1 2022-01d3d11.dllx1 2022-01d3d9.dllx1 2022-01dxgi.dllx1 2022-01
dxvk output during startup