Moderator: face_off
It will be some time before this is useable of the OctaneRender for Modo plugin, however I though I would post some progress shots here for those interested.SDK: Adds the Rendercache API (beta implementation), allowing SDK developers to access the same rendering data as the internal MODO renderer, exposing the geometry cache and shading information.
Shader Support - no. But I think all 3rd party render plugin developers have asked for this, so hopefully it is on TF todo list. Gradient is supported in the next release of the plugin - although you manually set it up.Question: does the render cache API open up any doors for additional shader tree item support, such as native MODO procedurals, gradient drivers, etc? There's some very handy tools in there that I don't see Octane adding on its own anytime soon. I.e: wanted to create a random output of three fixed colors. Impossible in Octane, easy in MODO.
It appears I already have the Gradient 2 node in 2.22, but perhaps you're adding more to it?face_off wrote:Shader Support - no. But I think all 3rd party render plugin developers have asked for this, so hopefully it is on TF todo list. Gradient is supported in the next release of the plugin - although you manually set it up.Question: does the render cache API open up any doors for additional shader tree item support, such as native MODO procedurals, gradient drivers, etc? There's some very handy tools in there that I don't see Octane adding on its own anytime soon. I.e: wanted to create a random output of three fixed colors. Impossible in Octane, easy in MODO.
Paul
No - the version put through yesterday in the TEST version is the version I was referring it. There is probably an option for a Gradient 3 node too, which allows up to 10 control points (pins that a texture or rgb color could be plugged into) and 10 position floats. But not sure of people would use it or not.It appears I already have the Gradient 2 node in 2.22, but perhaps you're adding more to it?
The Octane gradient node is LINEAR - and the Gradient 2 node samples it every 10 percent (rather than extracted the actual control points from the Modo gradient control). So I don't think it will do exactly what you are trying to achieve.I think the trouble I'm having in this particular scenario is coming from possibly two things: even when using MODO's "stepped" slope, there's still a slight transition between the colors, and also there's no way to clamp Octane's random color float value output. If it could be clamped to two decimal places, that would translate to whole percentages in the gradient input and would skip over transition areas. Either that or something else completely different is going on, like Octane isn't receiving MODO's input slope type properly.
