https://bugs.winehq.org/show_bug.cgi?id=55140
--- Comment #6 from Krzysztof Bogacki saancreed@gmail.com --- Your attachment doesn't seem to contain your logs :(
Recent versions of DXVK apparently require Nvidia driver 510.47.03 or newer, so 470 might not be enough, but if that's not it then one last thing I can think of would be exporting `DXVK_ENABLE_NVAPI=1` in the environment which, if not done, causes DXVK to report NV GPUs as AMD ones and cause NVAPI to fail to initialize:
info: DXGI: NvAPI workaround enabled, reporting AMD GPU NvAPI_Initialize: NVIDIA or other suitable device not found or initialization failed
So, if the application indeed doesn't attempt to enter its NVML code path on your machine, there's still some difference between our setup and unfortunately I'm running out of ideas why exactly is that the case here.