Daz Studio lacks some NvAPI methods for iRay rendering

[PetitMote]

Hello there,

It’s been a while, but some update (from Daz Studio) broke iRay rendering on nvidia GPU through Wine. I’m only a recent user, so I don’t know how it used to work or if dxvk_nvapi was needed, but I think it used to work before the first releases of dxvk, when wine-staging was needed. Rendering works fine on CPU, but it’s much slower.

I’ve checked the logs and tried with and without dxvk_nvapi. Here are the logs from dxvk_nvapi:

---------- 2022-01-04 18:46:40 ----------
NvAPI_QueryInterface 0xad298d3f: Unknown function ID
DXVK-NVAPI v0.5-20-ge23d450 (DAZStudio.exe)
NVML loaded and initialized successfully
NvAPI Device: NVIDIA GeForce RTX 3060 (495.46.0)
NvAPI Output: \\.\DISPLAY1
NvAPI_Initialize: OK
NvAPI_QueryInterface 0x33c7358c: Unknown function ID
NvAPI_QueryInterface 0x593e8644: Unknown function ID
NvAPI_GetInterfaceVersionString: OK
NvAPI_EnumLogicalGPUs: OK
NvAPI_EnumPhysicalGPUs: OK
NvAPI_QueryInterface 0x1efc3957: Unknown function ID
NvAPI_EnumNvidiaDisplayHandle 0: OK
NvAPI_GetPhysicalGPUsFromDisplay: OK
NvAPI_QueryInterface NvAPI_GetAssociatedNvidiaDisplayName: Not implemented method
NvAPI_GetErrorMessage -3 (NVAPI_NO_IMPLEMENTATION): OK
NvAPI_EnumNvidiaDisplayHandle 1: End enumeration
NvAPI_EnumNvidiaUnAttachedDisplayHandle 0: End enumeration
NvAPI_QueryInterface NvAPI_GPU_GetBusType: Not implemented method
NvAPI_GetErrorMessage -3 (NVAPI_NO_IMPLEMENTATION): OK
NvAPI_GPU_GetFullName: OK
NvAPI_GPU_GetVbiosVersionString: OK
NvAPI_Initialize: OK
NvAPI_SYS_GetDriverAndBranchVersion: OK
NvAPI_EnumPhysicalGPUs: OK
NvAPI_EnumLogicalGPUs: OK
NvAPI_QueryInterface NvAPI_EnumTCCPhysicalGPUs: Not implemented method
NvAPI_GetErrorMessage -3 (NVAPI_NO_IMPLEMENTATION): OK
NvAPI_GetPhysicalGPUsFromLogicalGPU: OK

I’ve started by reading the logs from Daz Studio, and there isn’t more, but I can still provide the log file if needed. Also, when dxvk_nvapi is disabled, I get the error on the NvAPI_Initialize method (3 times), and not on these 3 methods.

I believe the issue is due to these methods not being implemented on dxvk_nvapi. I would sincerely love to help and try to add them, but I’m merely a python beginner and c++ looks like sorcery to me (and, well, we’re talking about some low level coding). But I’d be happy to help or try if someone can point me in the right direction.

Also, DazStudio physic simulation, dforce, used to work, but now it only says "no OpenCL 1.2 compatible device found". I have absolutely no idea if it’s related, there is no information in the logs about it, but well, maybe if we fix the NvAPI issue we’ll get something.

Thank you guys for your work, it’s still pretty amazing.

[jp7677]

Could you please describe what do you mean with “broke”? Do you get an actual error message or anything that might hint what that application is missing? Did you also tried to spoof an AMD card in DXVK? The DXVK logs should tell you the effective setting.

Looking at the logs itself, I would say the application handles the missing methods just fine and the actual issue is somewhere else.

[PetitMote]

Hello,
Sorry, it lacked indeed some precisions. So if I allow only the GPU in the render settings, it starts compiling the shaders, but it won’t render. Daz considers the render over and presents an empty image to save.

It may be better with some logs
dazstudio-logs.txt
dxvk-nvapi.log

After re-reading the logs, I’m not as sure as before… There is a cuda error.

[jp7677]

Looking at those logs, I think this is the actual error:

The version of your CUDA driver is 0.0, but 11.0 is the required minimum

CUDA module initialization failed with error 'CUDA driver version is insufficient for CUDA runtime version' (0x23); iray photoreal can only run in CPU mode. Please update your NVIDIA driver (www.nvidia.com).

So I guess the cuda implementation in wine-staging is no longer sufficient for this application.

[PetitMote]

Yeah, that seems more like it. Although, that’s strange how it finds only a "0.0" version, and not an actual version of cuda.

[jp7677]

Yeah, I agree, also looking at https://github.com/SveSop/nvidia-libs/blob/master/dlls/nvcuda/nvcuda.c#L1031 (not the actual wine staging source, that is here https://github.com/wine-staging/wine-staging/tree/master/patches/nvcuda-CUDA_Support), the driver version call is just passed through, so the question is indeed how that application determines the cuda version.

[jp7677]

Could you take a look at wine logs with enabled nvcuda channel (and loaddll? This should give an indication if cuda is loaded at all.

[PetitMote]

Yep, I’ve tried looking at the actual version, but I’ve a hard time reading C++ + patch notes + I don’t understand how it works.

Here is the log. I found an error while importing nvcuda and nvcuvid:

0534:err:module:import_dll Loading library nvcuda.dll (which is needed by L"C:\\Daz 3D\\Applications\\64-bit\\DAZ 3D\\DAZStudio4\\libs\\iray\\nvcuvid_video_decoder.dll") failed (error c000000f).
0534:err:module:import_dll Loading library nvcuvid.dll (which is needed by L"C:\\Daz 3D\\Applications\\64-bit\\DAZ 3D\\DAZStudio4\\libs\\iray\\nvcuvid_video_decoder.dll") failed (error c000000f).

wine-log.txt

But I need to make sure there isn’t any dll from all my tries and retries!

[jp7677]

Mmh, may be it is an idea to stub EnumTCCPhysicalGPUs in dxvk-nvapi, since this is related to cuda, I can take a look tomorrow.

[jp7677]

Yep, I’ve tried looking at the actual version, but I’ve a hard time reading C++ + patch notes + I don’t understand how it works.

Here is the log. I found an error while importing nvcuda and nvcuvid:

0534:err:module:import_dll Loading library nvcuda.dll (which is needed by L"C:\\Daz 3D\\Applications\\64-bit\\DAZ 3D\\DAZStudio4\\libs\\iray\\nvcuvid_video_decoder.dll") failed (error c000000f).
0534:err:module:import_dll Loading library nvcuvid.dll (which is needed by L"C:\\Daz 3D\\Applications\\64-bit\\DAZ 3D\\DAZStudio4\\libs\\iray\\nvcuvid_video_decoder.dll") failed (error c000000f).

wine-log.txt

But I need to make sure there isn’t any dll from all my tries and retries!

Thanks. Do you actually have nvcuda in your wine environment? I think you can use GPU Caps Viewer in you prefix to get some info about cuda.

[PetitMote]

Sorry, I think I need to do a clean setup of Daz, because I might have a bit messed-up my environment 😅 Just a few minutes

[PetitMote]

Ok, got it!
wine-log-2.txt

Now it loads, also I looked into the Daz log and found this:

2022-01-04 23:21:44.392 Initializing NVIDIA Iray...
2022-01-04 23:21:44.393 Iray [INFO] - API:DATABASE ::   0.0   API    db   info : Loaded "C:\Daz 3D\Applications\64-bit\DAZ 3D\DAZStudio4\libs\iray\libneuray.dll"
2022-01-04 23:21:44.393 Iray [INFO] - API:MISC ::   0.0   API    misc info : Iray RTX 2020.1.6, build 334300.9558, 27 Mar 2021, nt-x86-64
2022-01-04 23:21:44.393 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(480): Could not add path: "C:/users/timothee/AppData/Roaming/DAZ 3D/Studio4/shaders/iray". Due to unknown error -2
2022-01-04 23:21:44.393 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(480): Could not add path: "C:/users/timothee/AppData/Roaming/DAZ 3D/Studio4/temp/shaders/iray". Due to unknown error -2
2022-01-04 23:21:44.413 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - GPU:RENDER ::   0.0   GPU    rend error: NvAPI call NvAPI_GetAssociatedNvidiaDisplayName returned an error:
2022-01-04 23:21:44.413 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - GPU:RENDER ::   0.0   GPU    rend error:   NVAPI_NO_IMPLEMENTATION
2022-01-04 23:21:44.413 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - GPU:RENDER ::   0.0   GPU    rend error: NvAPI call NvAPI_GPU_GetBusType returned an error:
2022-01-04 23:21:44.414 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - GPU:RENDER ::   0.0   GPU    rend error:   NVAPI_NO_IMPLEMENTATION
2022-01-04 23:21:44.414 Iray [INFO] - GPU:RENDER ::   0.0   GPU    rend info : Found 1 GPU with vendor's API.
2022-01-04 23:21:44.438 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - CUDA:RENDER ::   0.0   CUDA   rend warn : CUDA module initialization failed.
2022-01-04 23:21:44.438 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - CUDA:RENDER ::   0.0   CUDA   rend warn : cudaRuntimeGetVersion returned with error 'initialization error'
2022-01-04 23:21:44.438 NVIDIA Iray Rendering Configuration:
2022-01-04 23:21:44.438 	CPU Fallback: enabled
2022-01-04 23:21:44.438 	GPU Detection: enabled
2022-01-04 23:21:44.438 	GPU Driver Version Check: enabled
2022-01-04 23:21:44.438 Loading NVIDIA Iray Plugins...
[…]
2022-01-04 23:21:44.658 Iray [INFO] - IRAY:RENDER ::   1.1   IRAY   rend info : NVIDIA display driver version: 495.46
2022-01-04 23:21:44.658 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - IRAY:RENDER ::   1.1   IRAY   rend warn : CUDA module initialization failed with error 'initialization error' (0x3); iray photoreal can only run in CPU mode. Please update your NVIDIA driver (www.nvidia.com).
2022-01-04 23:21:44.658 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER ::   1.1   IRAY   rend error: NvAPI call NvAPI_EnumTCCPhysicalGPUs returned an error:
2022-01-04 23:21:44.659 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [ERROR] - IRAY:RENDER ::   1.1   IRAY   rend error:   NVAPI_NO_IMPLEMENTATION
2022-01-04 23:21:44.659 Iray [INFO] - IRAY:RENDER ::   1.1   IRAY   rend info : Using iray plugin version 5.1, build 334300.9558 n, 27 Mar 2021, nt-x86-64-vc14.
2022-01-04 23:21:44.659 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - IRAY:RENDER ::   1.1   IRAY   rend warn : There is no CUDA-capable GPU available to the iray photoreal renderer.
2022-01-04 23:21:44.659 Iray [VERBOSE] - IRAY:RENDER ::   1.1   IRAY   rend stat : Environment cache size capacity: 5.
[…]
2022-01-04 23:21:44.661 NVIDIA Iray GPUs:
2022-01-04 23:21:44.661 	GPU: 1 - 
2022-01-04 23:21:44.661 	Memory Size: -1 bytes
2022-01-04 23:21:44.661 	Clock Rate: -1 kHz
2022-01-04 23:21:44.661 	Multi Processor Count: -1
2022-01-04 23:21:44.661 	CUDA Device ID: -1
2022-01-04 23:21:44.661 	CUDA Compute Capability: NA
2022-01-04 23:21:44.661 	PCI Bus ID: -1
2022-01-04 23:21:44.661 	PCI Device ID: 260
2022-01-04 23:21:44.661 	TCC Mode: disabled
2022-01-04 23:21:44.661 	Display: attached
2022-01-04 23:21:44.662 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - IRAY:RENDER ::   1.0   IRAY   rend warn : There is no CUDA-capable GPU available to the iray photoreal renderer.
2022-01-04 23:21:44.662 Iray [INFO] - IRT:RENDER ::   1.0   IRT    rend info : Resource assignment for host 0 has changed.
2022-01-04 23:21:44.662 NVIDIA Iray Scheduling Configuration:
2022-01-04 23:21:44.662 	CPU Load Limit: 12
2022-01-04 23:21:44.662 	CPU Thread Affinity: disabled
2022-01-04 23:21:44.662 	GPU Load Limit: 1

Obviously, I had fucked up my wine prefix 😬 I guess it showed "0.0" because there was some formatting around the get version function. But it still won’t work, sadly :(

[PetitMote]

Ok, maybe we did all this just to be stuck at the same point we were before. According to Cuda-z, the runtime dll version is 6.5, which means a dinosaur.

Well, still, thank you very much! It was really kind of you to help me.

[Saancreed]

@PetitMote That 6.50 you see in your screenshot is just the version of the library CUDA-Z was linked to (obtained using cudaRuntimeGetVersion), it will always report 6.50 unless you recompile and link it with newer runtime libraries because that's the version the latest binary release of CUDA-Z ships with.

Fwiw this is what CUDA-Z says on my machine, on the left is the Linux version and on the right is the Windows one running in Wine.

So your problem is most likely related to application failing to load Wine's nvcuda.dll and nvcuvid.dll. Actually, after taking a look at your latest log, it seems that application loads the library correctly, but fails to use it. But it's hard to say if that's because of DXVK-NVAPI missing implementation of some functions or Wine's CUDA library not supporting newer interfaces.

[PetitMote]

Hello again,
Indeed, I agree with all you said. In fact, I checked Daz Studio requirements, and they only say it needs 2.0 Compute Capability. I’m guessing there might lack a function, or there could be a bug, either in wine’s cuda or dxvk-nvapi. Or, maybe there is a fundamental difference between Cuda windows and Cuda Linux?
Either way, I need more logs to know about it. Do you know to get them?
There isn’t a nvcuda channel for WINEDEBUG, so I don’t know to get more informations? Also, I’ll try to get in touch with Daz Studio to see if they can give a debug version of their software.

[Saancreed]

There isn’t a nvcuda channel for WINEDEBUG

Actually there is, which is why we can see the following in the log:

04d0:trace:nvcuda:DllMain (0x7f0798320000, 1, (nil))
04d0:trace:nvcuda:wine_cuDriverGetVersion (0x145103e0)
04d0:trace:nvcuda:wine_cuInit (0)
04d0:trace:nvcuda:wine_cuGetExportTable (0x145103b8, 0x144e53c0)
04d0:fixme:nvcuda:cuda_check_table WARNING: Your CUDA version supports a newer interface for Unknown1 then the Wine implementation.
04d0:trace:nvcuda:wine_cuGetExportTable (0x145103c0, 0x144e53a0)
04d0:trace:nvcuda:wine_cuDeviceGetCount (0x145189c0)
04d0:trace:nvcuda:wine_cuDeviceGet (0x101ee80, 0)
04d0:trace:nvcuda:Unknown1_func1_relay (0x14518be8, (nil))
04d0:trace:nvcuda:wine_cuDeviceGetName (0x14518c28, 256, 0)
04d0:trace:nvcuda:wine_cuDeviceTotalMem_v2 (0x14518d48, 0)
04d0:trace:nvcuda:wine_cuDeviceGetAttribute (0x14518d90, 75, 0)
…

But it's not enough to tell if Wine has all the stuff Daz Studio needs. I think implementing NvAPI_GetAssociatedNvidiaDisplayName, NvAPI_GPU_GetBusType and NvAPI_EnumTCCPhysicalGPUs could maybe tell us more. Or attempting to use DXVK and DXVK-NVAPI with Nvidia's nvcuda.dll on Windows somehow, assuming we can make it load our own nvapi64.dll to see if CUDA still works.