Page 1 of 1

Instance deforming..

Posted: Wed Sep 23, 2015 11:05 am
by Maestrorobertus
Hi there, our workflow is based almost entirely on instances, references and replicators, however it seems Octane comes with a few limitations. One of the worst is that there is no deformer support on instances. If you have many characters in a scene that can lead to problems. But also if you want to deformer groups with instances its needed.

Any Idea why it get supported ???

Re: Instance deforming..

Posted: Wed Sep 23, 2015 11:27 am
by Maestrorobertus
Another thing I ran into is that the visibility or render ability of group layers are not ported to Octane. Thats not a good thing. Without controlling of scenes get difficult

Re: Instance deforming..

Posted: Wed Sep 23, 2015 11:45 am
by Maestrorobertus
That limitation is stupid:
Only material assignments to polygons by “Material” Polygon Tag Type is supported. Material assignments by “Part” and “Selection Set” Polygon Tag Types are not supported.
It ruins Modo's shader tree and makes Octane less attractive.
Also UVS and procedurals need to be supported. A simple box/cubic mapping should work.. it does in other Octane plugins.

Re: Instance deforming..

Posted: Wed Sep 23, 2015 1:33 pm
by face_off
I know you have some answers on these already - but responding to all in case others have the same questions.
Only material assignments to polygons by “Material” Polygon Tag Type is supported. Material assignments by “Part” and “Selection Set” Polygon Tag Types are not supported.
These are supported in the latest TEST release.
Also UVS and procedurals need to be supported. A simple box/cubic mapping should work.. it does in other Octane plugins.
UV's are supported. Procedurals are not - and this is because the Modo API does not support accessing the Modo procedural bitmaps. Box mapping is supported by the plugin. https://docs.otoy.com/#42Projection%20Mapping
Another thing I ran into is that the visibility or render ability of group layers are not ported to Octane. Thats not a good thing. Without controlling of scenes get difficult
I will see if there is a fix for this.
Hi there, our workflow is based almost entirely on instances, references and replicators, however it seems Octane comes with a few limitations. One of the worst is that there is no deformer support on instances. If you have many characters in a scene that can lead to problems. But also if you want to deformer groups with instances its needed.

Any Idea why it get supported ???
Deformed Mesh Instances are not currently supported, since only the transform of a Mesh Instances is stored in the Octane Scatter node. Support for this may be possible in the future with the Modo Render Cache API.

Paul

Re: Instance deforming..

Posted: Sat Sep 26, 2015 5:42 pm
by Maestrorobertus
Thanks for clearing the questions, very helpful. I'm very happy partIDs now supported.

Hope you find a way to support motion blur for the Modo plugin, it would be cool to preview it right there.

Re: Instance deforming..

Posted: Sat Sep 26, 2015 10:32 pm
by face_off
Hope you find a way to support motion blur for the Modo plugin, it would be cool to preview it right there.
It is my number 1 priority at the moment. You can get Object motion blur in the Viewport (if you tick Load All Frames Into Octane) - however getting vertex motion blur too is the goal.

Paul