Wrong rendering result by V3.08

[calvados]

V3.08 Screen Shot, Becuase save fuction dose not work.

V3.07 Rendering

I meet wrong rendering result and error by V3.08.
Show result sample.
Those picture has same setting, it user redspec SSS with V4 Figure.

I meet following trouble.
1. Wrong rendering result.
2. Dose not save rendering result by save function, this picture is clip from screen shot.

How to solve this prob rem ?

My environment.
Windows10 Pro 32Gmemory
1070 * 3;
Octane 3.07
Octane 3.08

[face_off]

This is due to having a Greyscale Color node plugged into the Normal pin, set to 0. You need to disconnect 0 value Greyscale Color nodes from Normal pins.

Paul

[calvados]

Thank you for your response.

Sorry, it can do by Poser for Octane render ?
It do by Octane node directory ?

And why dose not save this image by Octane Rendering window ?

[face_off]

Sorry, it can do by Poser for Octane render ?
It do by Octane node directory ?

And why dose not save this image by Octane Rendering window ?

I am sorry - but I don't understand what you are saying here.

Paul

[calvados]

> I am sorry - but I don't understand what you are saying here.

I'm sorry

How to "Greyscale Color node set to 0 / disconnect 0 value Greyscale Color nodes from Normal pins" ?
It can operate under Octane for Poser or Octane stand alone shader panel ?

[face_off]

In the OctaneRender for Poser plugin, select the material->select the Normal pin->if it is set to Greyscale Color select a new node type of "Disconnect".

Paul

[calvados]

Problem solved
Thank you.
"Greyscale Color node set to 0 -> change to disconnect" as new specification ?

[face_off]

"Greyscale Color node set to 0 -> change to disconnect" as new specification ?

Yes, Octane 3.08 requires this.

Paul

[calvados]

I agree

Thank you for your support!

[gsfcreator]

Paul, I had this issue as well, using the redspec shaders for M4F. had to go through the process of disconnecting all the normal nodes (which takes up to 20-30 minutes, since there's multiple materials), and I'll have to do it all over again for any other V4 based character that I use.

I understood from the creator of the shaders that you guys are working on a fix for this. any idea as for when we might see an update with the fix?

kind regards and thanks,