Using Iray MDL in DAZ Studio Pro 

Thank you, this means a lot to me. Glad to be of help.

mdl::state::texture_tangent_u(int)_37258709 appears to be invalid whereas it was expected to a be a mdl::call mdl::state::normal()_42118210 appears to be invalid whereas it was expected to a be a mdl::call These are the kind of errors that appear when I try to export the MDL Material Module from Substance Designer

Using MDLs created with Substance is a bit more complicated than what I showed in the video. First, the generated files refer to MDL functions available only when SD is installed or that are available to the version of Iray installed with the Substance products. Second, the log file in question is the DAZ log file, which contains (sometimes rather cryptic) descriptions what went wrong. (I assume we are talking about DAZ here.) The "refreshing the shader" message just states that something went wrong, but not the reason. My gut-feeling tells me, that the MDL generated by SD refers to a directory which isn't listed in DAZ's MDL search path. Unfortunately, I'm not using Substance at the moment, so I can't check what's going on. Regarding DAZ's log file and MDL: DAZ is very "noisy" in regard to the log messages, so when you drag the MDL into Shader Mixer, then the errors are at the end of the file. This means you want to open the log right after the error message to check what Iray is complaining about. The important thing here is, that most errors are "cascading". Meaning the error description is spread over a couple of lines describing which function called what and the chain of commands leading to the error. One last thing: SD seems to create MDL for the Iray version in SD, which isn't necessarily the version that comes with DAZ. You can find the version the MDL is based on in the beginning of the MDL file, it looks like "mdl 1.4;" for example. Let me know whether this helped.

@@ErikMKeller thank you for you quick and complete response! So, to access the error log as soon as it appears in the shader mixer, I need to open on Notepad the MDL file that caused this error, and the error log will appear at the end of this file? Or are you talking about some other file? I didn't think about the "MDL Version" difference on Substance Designer and DAZ... So does that mean that it's not possible to build our own MDL materials on Substance Designer to use them in DAZ? 😞 That's sad, that could become quite an useful tool

@@ErikMKeller But the second error log with the "mdl::state::texture" etc that I quoted above was while "Exporting MDL Module" on Substance Designer. These errors appeared, but it saved the file anyway. On DAZ Shade Mixer, while importing this same file, that very simple error showed up, the first one that I quoted, just asking me to look at the logs, without details like the one on Substance Designer

@@Pitusha Sorry, access to the log file in DAZ is a bit hidden. On my Mac it's in the Help menu under "Troubleshooting" > "View Log File…". Just to make sure, the directory your MDL file is stored in is part of the MDL search path as shown in the video? Regarding the error messages during export from SD, it seems they are referencing to the mdl::state package which should be loaded when opening the shader (I checked one of my MDL experiments using SD and the necessary functions in the package are imported automatically). I just tried to import an MDL file I created in SD and couldn't make it work. It seems, that the problem, based on the log entries, lies with SD. I found this thread in the Substance forum, it should explain what you need to do: forum.substance3d.com/index.php/topic,36642.new.html?PHPSESSID=c0a4860c74c31a3cb6ee90a13c9b2bf6#msg136614 Unfortunately, I don't have the time to try these steps at the moment, but please let me know whether it worked. Cheers, Erik