Ûber shader and the shader mixer

jergenoman_b33d4209f8

Hello

I stumbled upon an annoying problem: I used the über shader dial in a volumetric water material that i am quite pleased with but i need to customize the volumetric behaviour a bit. However the shader mixer doesn't seem to handle the über shader well. If i import the shader into the shader mixer and then immediately apply it to the surface again the shader is corrupted. The preview is wrong, the volumetric behaviour is gone, etc...

Is this normal behaviour? I have tweaked the über shader with my own MDL scripts many times using the "PBR Metallicity Base" node with good result. I can't see any obvious problem with the shader in the shader mixer. Everything is there including the "PBR Specular Base" node. All connections seem ok and valid.

/Jörgen

UncannyValet

jergenoman_b33d4209f8 said:

If i import the shader into the shader mixer and then immediately apply it to the surface again the shader is corrupted.

Do all the settings of the Shader still look the same as that of the surface you imported into Shader mixer? it's just the preview that isnt showing correctly? 

jergenoman_b33d4209f8

The order of the parameters in the "Surfaces" pane changes to the order of the parameters in the "User Parameters" brick in the shader mixer. All parameters are correct when i go through them. It seems that the problem is isolated to the volumetric behaviour.

"Transmission Measurement Distance" and "Scattering Measurement Distance" are both multiplied with 0.01 in the shader mixer. I assume that is a rescaling from centimeter to meter?

jergenoman_b33d4209f8

Success! I replaced the "Uber add volume" brick with a new one and the volumetrics snapped back in. The only change is that i bypassed the scaling from cm to m (specifying 6m instead of 600cm instead).

As soon as i try to reconnect the scaling it fails again, even if the scale factor is set to 1.0. Could this be a bug?

Bejaymac

Never import a shader into the SM that wasn't built in it, and of the shaders DAZ supply with DS4 only AOA's SS shader was built in it.

Other shaders either wont import, or you will get a rough representation of the shader, which always has major issues when you apply it back to a surface.

jergenoman_b33d4209f8

Bejaymac said:

Never import a shader into the SM that wasn't built in it, and of the shaders DAZ supply with DS4 only AOA's SS shader was built in it.

Other shaders either wont import, or you will get a rough representation of the shader, which always has major issues when you apply it back to a surface.

 

I know, but i have been quite lucky tweaking the uber shader so far. I don't have the knowledge make my own shaders from scratch and simply not enough free time to learn.

Padone

This is interesting, I didn'd even dare to imagine that we can load uber in the shader mixer. Thank you.

UncannyValet

Bejaymac said:

Never import a shader into the SM that wasn't built in it, and of the shaders DAZ supply with DS4 only AOA's SS shader was built in it.

Other shaders either wont import, or you will get a rough representation of the shader, which always has major issues when you apply it back to a surface.

Oh, could you explain that further? How are shaders for DS built if not in the Shader Mixer? 

Richard Haseltine

UncannyValet said:

Bejaymac said:

Never import a shader into the SM that wasn't built in it, and of the shaders DAZ supply with DS4 only AOA's SS shader was built in it.

Other shaders either wont import, or you will get a rough representation of the shader, which always has major issues when you apply it back to a surface.

Oh, could you explain that further? How are shaders for DS built if not in the Shader Mixer? 

Directly coded in RSL or MDL, or for 3Delight (RSL) using Shader Builder.