iray uber base shaders & parameter lock ?

chromchrom Posts: 260
edited June 2019 in Daz Studio Discussion

Hi,

I read & tried several things with shader under iray uber base.

Some shader presets effect not all aspects (e.g. only something like an overlay effect).

 

Can you see for presets before loading which IUB aspects it effects?

Can you force presets to avoid effecting specific IUB aspects when loading ?

(I only found ignoring the image.)

 

I locked parameters like base color and applied a shader preset. But locked parameters are also overwritten.

Can it be suppressed? What is the sense of "lock"?

 

Thank you

Post edited by chrom on

Comments

  • JonnyRayJonnyRay Posts: 1,744

    A few questions there. :)

    1. No, you can't "preview" what changes are going to be made before you load it. Part of the reason for this is that a "Shader Preset" may also be loading a new shader (other than Iray Uber Base); so the current shader may not have the parameters of the preset you're loading.
    2. I believe you're correct that you can only override the images from being loaded. I don't recall ever setting any other options for selective merging of settings. A big reason for that could be the same as #1, that not all Shader Presets are only affecting the Iray Uber Base; so you could get into weird scenarios where the properties you select wouldn't match the properties available in the shader you're using.
    3. Locking prohibits you from manually making changes to a parameter by accident. Studio assumes that if you're loading a preset, you want those properties to be adjusted by the preset; so locking isn't going to stop a preset from overwriting them. And the mismatched underlying shader thing could futher make things complicated and result in unwanted effects.

    One thing you could try if you want to experiment with "blending" shader presets would be to save your own Shader Preset and only select the parts that you want to make sure stay constant. Then you could load the 3rd party Shader Preset, and re-load yours to set those properties back the way you wanted them.

  • chromchrom Posts: 260

    Ah ok, thank you.

    Would it be an idea for minimize effort to put a primitive object into the scene, load the 3rd party shader on it and copy only wanted aspect/parameters to my real / target object (also e.g. for testing different single subsettings; then perhaps with a second primitive to copy paste the orignal as backup)?

    Or do I miss something in this "workflow"?

  • JonnyRayJonnyRay Posts: 1,744

    No, that should work too.

Sign In or Register to comment.