OTOY Forums

Guys, Can you do it?
I think,
what need to add string option input texture node,
where we can write a path to img context



in VEX example for understanding my question

The problem is that Octane always reads the textures from image files at scene extraction and loading time, so this kind of operators are not going to work. Perhaps you could try to output your ramp texture to a physical file (a bmp or jpg file, for example), that the Octane texture image node can read.

Anyway let me check if for the future I could add some kind of rasterization node to import in Octane image data available from other Houdini image operators.

-Juanjo

Thanks for answer,
no problem about ramp, its only example
The big strantgh of houdini manage context's inside file
and will be good add this function to your octane library

juanjgon wrote:Anyway let me check if for the future I could add some kind of rasterization node to import in Octane image data available from other Houdini image operators.

-Juanjo

This would be amazing, if octane could read the output of a vop/cop/shop from a bind export.
If all else fails, maybe having mantra render out bitmaps as a preprocessing stage that octane automatically would read could be a workaround?
You're doing an amazing job considering what standalone supports/doesn't support.