Page 1 of 1
Using Octane in TOP
Posted: Mon Nov 23, 2020 8:10 pm
by LucaPrassoGoogle
I've a simple Houdini 18.5 scene with one model, a camera, an Octane material and an Octane ROP
Triggering the single Octane render from the Octane ROP works as usual.
I've setup a simple TOP wedge node to alter the geometry shape.
I want to render short sequences with Octane for each model wedge.
I'm not able to trigger the render from a ROP Fetch.
Checking the TOP log I see errors for not finding libHoudiniUI.so
Code: Select all
Houdini DSO error on '/netapp/Octane/Octane_2020.1.5.2_Houdini_18.5.351_Linux_gcc6.3.1/dso/Houdini_Octane_18.5.351.so'
libHoudiniUI.so: cannot open shared object file: No such file or directory
I'm not sure what am I doing wrong or what am I missing...
Re: Using Octane in TOP
Posted: Mon Nov 23, 2020 9:33 pm
by juanjgon
Hi,
Hmm, the TOPs are executed using hython, so this seems some kind of problem with this command. It is like the system PATH variable didn’t include the path to the Houdini system libs, that are needed by the Octane plugin. What happens if you try to use hython in this system, and using the same user? You should get some information about the Octane plugin loading just after executing hython from the console.
Thanks,
-Juanjo
Re: Using Octane in TOP
Posted: Mon Nov 23, 2020 10:01 pm
by LucaPrassoGoogle
I opened a new terminal and sourced my Houdini 18.5.391 environment
I typed 'hython' and got the same error
Code: Select all
hython
Houdini DSO error on '/netapp/Octane/Octane_2020.1.5.2_Houdini_18.5.351_Linux_gcc6.3.1/dso/Houdini_Octane_18.5.351.so'
libHoudiniUI.so: cannot open shared object file: No such file or directory
Python 2.7.15 (default, Mar 10 2020, 16:24:16)
[GCC 6.3.1 20170216 (Red Hat 6.3.1-3)] on linux2
Houdini 18.5.391 hou module imported.
I'll try to figure out what is causing this first...
This is happening on Houdini 18 as well...
I'm running this on a VM with Centos.
If someone has any idea what is happening feel free to chime in... thanks!
Re: Using Octane in TOP
Posted: Mon Nov 23, 2020 10:43 pm
by LucaPrassoGoogle
it turns out it was a mix-match between installed versions of Houdini on my VM.
Reinstalled 18.5.351 and everything seems to work as expected.
I should stop installing bazillion of beta versions on the same machine where I'm supposed to work...
