PBR shader skin shade problem.
icemage1993
Posts: 69
in The Commons
Hello everyone, Iam trying out the PBR skin shader that comes with G8.1F for the first time and run into this problem. Here you could see on the picture below, I tried to apply the PBR shader on a regular character using regular Iray uber skin, and it changes the skin shade completely. The skin lost it blue shade and turned white. I want to use the PBR shader for it skin details feature, but also want to keep my character's skin shade, what did I do wrong?
Comments
If changin shader to Skin PBR, you should expect changes, you will have to modify.
You might get this https://www.daz3d.com/1-click-pbrskin
Else, how is the blue skin obtained in Iray Uber (e.g. Base color or Translucency color)? You might tweak that channel in Skin PBR.
Or else you can just modify the skin settings to give a bluish tone, independant of the original tone.
I have that character - Nikki on Renderhub - and also have 1-click-pbrskin. The result is worse than manually changing to pbrskin and enabling the various material layers like OP has done. 1-click PBR messes up the transmitted colour and transluency colour and weight.
The base colour is a blue texture, but the transluency colour is beige with a 0.22 0.22 0.52 purple-ish tint.
After messing around with the shader for a while my best way to fix this is just adjust the translucency weight :/
There is more to this Iam sure, but thats all I can do.
@franky85 and @icemage1993 - 1-Click PBRSkin was primarily designed for non fantasy skin tones, hence why the default conversion color won't look quite right. It should however speed up the manual PBRSkin conversion process, as for this particular character only transmitted color should need adjusting.
For this skin in particular I would usually recommend the 'Create Translucency' script as the default base and translucency maps are different skin tones, but curiously the script isn't replacing the existing maps with LIE versions, it's behaving like the 'Keep Translucency' script.
I've attached an image of what the default 'Create Translucency' conversion should look like - this is the only skin that hasn't converted as expected thus far so we will need to look into whether that's a fault with the script or something unique about this character - stay tuned!
@franky85 and @icemage1993 an update for you - Josh has found the cause of the issue and has swiftly updated the scripts and will be submitting an update soon. Look out for an update in DIM in due course!
For info, the problem is due to spaces in the filenames - it's a rare occurrence as usually underscores or hyphens are used.