OTOY Forums

Hi Paul,

I am curious to ask if octane 2.0 and plug in will support modo particles, and if not if there is a work around to render clouds.

I am curious to ask if octane 2.0 and plug in will support modo particles, and if not if there is a work around to render clouds.

Octane 2.0 does not included particle support. Particles is an area of Modo I have not yet investigated deeply, so not sure what level of support the plugin can provide yet. But I will look into this in more detail once 2.0 is done.

Referenced items does not appear in the render in octane.
It looks like octane plugin now does not know how to read these items.

I will investigate this.

Also when I transfer a object from a scene to an other, the octane materials are note translated. I think the groups are not copied, because I see the octane overide nodes coppied, but the I get an error that says ... Items x not found.

How are you transferring the object from one scene to another? Are the Modo materials being transferred correctly?

Paul

Yes Paul,
Modo materials are transferred corctly, and the octane nodes are transfered, but I think the octane plugins also is using some item groups that are not in the shader tree and this might be the problem.

Modo materials are transferred corctly, and the octane nodes are transfered, but I think the octane plugins also is using some item groups that are not in the shader tree and this might be the problem.

Yes, any channel modifiers that are connected to the Octane Material node will most probably not be in the Shader Tree for that material (since adding them was crashing Modo). Can you give me your exact workflow for transferring object pls?

Paul

Hi Paul,

Thank you for the fast reply.

Here is my Modo workflow:

Step 1: Open a scene with octane materials overrides defined.
Step 2: Select the Items I want to transfer into the new scene and drag them into the new scene tree.
Step 3: A dialog window appears and asks if I want to transfer childerns and shaders. I answer Yes Please
Step 4: I check the shader tree and all the items from the previous scene are there.
Step 5: I open Octane render viewport, the octane overides materials are not working, color is default difusse.
An execption dialog appears with the message : No workspace could be found for this Octane Override. Click 'Edit in Schemetic" to create a workspace.

Cheers,
Vlad

PS: I got this error also when I was trying to use Octane Live DB materials in past. I will check to see if this is fixed.

Here is my Modo workflow:

Step 1: Open a scene with octane materials overrides defined.
Step 2: Select the Items I want to transfer into the new scene and drag them into the new scene tree.
Step 3: A dialog window appears and asks if I want to transfer childerns and shaders. I answer Yes Please
Step 4: I check the shader tree and all the items from the previous scene are there.
Step 5: I open Octane render viewport, the octane overides materials are not working, color is default difusse.
An execption dialog appears with the message : No workspace could be found for this Octane Override. Click 'Edit in Schemetic" to create a workspace.

With that workflow, I can understand some of the items required by the Octane Override might not be copied. I am in the middle of a major code change, but once that's done in a day or two, I will see if it's possible to move things around a little so this workflow works for you.

Paul

Hi Paul,

I found a " perception bug on the plugin".

In modo in component mode, verts, edges and polygons there is a principle of modo that when nothing is selected all components are selected. This was added in order to simplify adding materials with scenes with big numbers of polys i think.

The bug If i define a material using this method (not selecting any polygons, ) modo assign a material to all the polygons. Octane plugin get confused and it does not recognize the material selection.All work if I go manual and select the polys and add the material in the other software classic way.

Not a bug, just a modo principle.

Hi Paul,
The supposed bug I mention in the post above is false.

The problem that occurs is with Modo 801, and his UDIM (multiple UV areas) workflow. I believe this is not supported in the present plugin. The default is 1001, I think this case is not treaded the in the plug in for 801, and this is why images and colors textures do not appear in modo 801 octane render window.

Cheers,
Vlad

The problem that occurs is with Modo 801, and his UDIM (multiple UV areas) workflow. I believe this is not supported in the present plugin. The default is 1001, I think this case is not treaded the in the plug in for 801, and this is why images and colors textures do not appear in modo 801 octane render window.

Hi Vlad. Images and colors are translating correctly for me in 801. I'm not sure I completely understand the problem you are having. Octane does not support multiple UV's, so the plugin uses the UV's from the "Texture" vertex map attached to each mesh. Is the problem you are having specific to 801? Can you give me a set of steps or sample scene which enables me to reproduce the issue pls?

Thanks

Paul

face_off wrote:

The problem that occurs is with Modo 801, and his UDIM (multiple UV areas) workflow. I believe this is not supported in the present plugin. The default is 1001, I think this case is not treaded the in the plug in for 801, and this is why images and colors textures do not appear in modo 801 octane render window.

Hi Vlad. Images and colors are translating correctly for me in 801. I'm not sure I completely understand the problem you are having. Octane does not support multiple UV's, so the plugin uses the UV's from the "Texture" vertex map attached to each mesh. Is the problem you are having specific to 801? Can you give me a set of steps or sample scene which enables me to reproduce the issue pls?

Thanks

Paul

Hi Paul,

Here is what I did.
I made a new cylinder object. I assigned to it a material, and yes the material works in 801.
Step 2. I have added a procedural wood texture. Step 3. I baked the texture as an image. (octane does not support procedural textures, it can doing this method , modo baking system ) Step 4. Save the texture. Step 4. Reopen the octane viewport render and see how the material behaves. No texture assigned. Step 5. I made an octane over ride, all look there, but no texture rendered in the octane viewport.
I made sure the texture exist, and are assigned correctly. Modo shows the material, octane does not.

Please look to my test scene file, maybe this will help.