trogers wrote:Hi Juanjo,
I've been struggling to get this feature to work in Octane. I was banging my head against the wall as using the COP texture path (the parent network path)in a Mantra Principled Shader works without issues, but was causing my geo to render as all black in Octane. I had been trying to use "op:/img/test_cop/" (the parent network path) in my Octane texture file path as I had in Mantra and resorted to writing you here to see if there was some trick I was missing. Half way through explaining the issue I decided to go back and try adding the final COP network node name to the end of the file path "op:/img/test_cop/colorcorrect1" and it worked!!
Out of curiosity, particularly given that the documentation around this level of functionality is non existent, is there a reason why the final node in the network needs to be included in the path? It would make things easier to tweak if we could just specify the parent network and then whatever node has the render flag set within that network would show as opposed to having to go back into the material and change the path to the node name if we modify the COP. Just a thought. I'm happy to see at least that this functionality exists and works with Octane!
Thanks in advance!
Users browsing this forum: No registered users and 5 guests