OTOY Forums

A clean install. Like a new fresh drive. Nothing has been installed before.

That is a petty, I thought that would be it: Another active python script interfering.

Does the previous plugin have the same problem?

wimvdb wrote:That is a petty, I thought that would be it: Another active python script interfering.

Does the previous plugin have the same problem?

I just tried with v. 3.6.2.82. That one works! I get no errors.
There's some double clicking happening to get the checkbox checked, but I don't get any errors and I can edit the Nodegraph.

I have updated the Windows TEST build at the top of this thread with:

3.08.0.86 (8-Mar-2018)
- Compiled with Octane 3.08 RC1 (see https://render.otoy.com/forum/viewtopic.php?f=33&t=63219 for details)
- Added Toon and Metallic materials
- Toon shading only works in Camera Light toon lighting mode.
- You can use OSL Textures by changing the Material Node Type to a NodeGraph and then adding an OSL Texture
- Added Custom Lut pin to the Imager node. Load .cube file into this node
- Changed the plugin version number to make it clearer which Octane release it uses

I will post an OSX build once the OSX libraries are available from OTOY.

Thanks

Paul

Whoop whoop! Thank you for the update

Thanks Paul!

Is there any sample out there which uses the anisotropic reflections? So far using it (with rotation) does not seem to make any difference with normal reflection (no difference from normal reflections, highlight does not change shape)

Is it possible to add the feature in the plugin to read the physical root node and use those maps for the metallic material? I know there probably is not really a 1 to 1 mapping for all features, but it would be a good starting point.

Is there any sample out there which uses the anisotropic reflections? So far using it (with rotation) does not seem to make any difference with normal reflection (no difference from normal reflections, highlight does not change shape)

Is it possible to add the feature in the plugin to read the physical root node and use those maps for the metallic material? I know there probably is not really a 1 to 1 mapping for all features, but it would be a good starting point.

May I suggest exporting your scene to Standalone and testing there too to ensure the plugin is actually handling these reflections in the same fashion. I am not sure exactly which Poser Material settings you want to convert to Octane, but if you provide some more details, and the rough conversion equation, I can take a look.

Paul

I figured it out,
The BRDF node should be set to another model as Octane (like Beckman) and roughness needs to be non-zero.

One bug/design issue for the plugin - Could the new Index of refraction nodes (the n, k ones) be set to linear? Now it is very difficult to set any value higher as 1 with the dial.

I think we have this "Normal 0.0" bug back.
The image shows two identical, glossy, spheres.
The left one has the "Normal" node disconnected and for the right one it's set to 0.0. Which then screws up the surface of the sphere.

No biggie, just wanted it to mention anyway.

EDIT: I forgot to mention, this happens when you first plug the Node Type -> "Greyscale color" into the "Normal" channel, and then set it to 0 for the render.

I think we have this "Normal 0.0" bug back.
The image shows two identical, glossy, spheres.
The left one has the "Normal" node disconnected and for the right one it's set to 0.0. Which then screws up the surface of the sphere.

No biggie, just wanted it to mention anyway.

Hi Wim. I think a "zero" normal is 0.5, 0.5, 0.5, so a Normal value of 0, 0, 0 is actually a value normal heading in the -X, -Y, -Z direction. So potentially this is the correct behavior. I'm not sure in what situation the plugin would plug a 0 float texture value into a Normal pin, so I'm unsure how you are getting that. Perhaps the material conversion is not working correctly?

Paul