OTOY Forums

Hi,
i can't make Octane work with embeded texture files into asset using the opdef structure.
Works great in SOP, mantra, etc.....can't make it work with Octane.
I'm using the not so new Matnet context inside a custom HDA. I"m calling texture at the HDA top level and link it too texture Image RGB filename.

Any advice ? Is it supported ?

Hi,

Hmm, nope, sorry. I think that this is not supported yet, but it is possible, so I'll try to add this feature to one of the upcoming builds.

Thanks for reporting this limitation!
-Juanjo

Thanks you for this quick reply.
In some way related :
Why can't we promote a file path from a texture node to the network level ?
Of course you can make expression manualy in order to sort this kind of problem but it can be a pain in a ass when you have tons of texture file name. This little gear next to any other parameter to promote it is so handy. Why not on file name ? Is it a limitation, a design choice, something else ?

Hi,

I've added the support of the opdef embedded textures to the just-released 2019.1.4.0 plugin builds. About your question related to the texture filename, the problem is that in Octane this parameter in these texture nodes is an attribute, not a texturable parameter. That means that it doesn't have an input pin to allow linking anything to it, so the parameter promotion is not possible.

Thanks,
-Juanjo

Good job it was fast like hell.

Trying to do exactly that. But can't get to load the texture.
Would you mind showing an example?
It would be much appreciate it.
Thanks a lot