OctaneRender for Nuke (Linux) 2.24.1 [TEST]

[face_off]

This thread has been merged with the Windows release version. Pls navigate to viewtopic.php?f=91&t=45763.

[JohnMesh]

Hey face,

thanks for this awesome plugin in nuke.
Installation went well face, i installed this to a custom location /usr/OFX/Plugins/OctaneForNuke/. After that i edited the init.py inside nuke's /usr/foundry/Nuke9.0v5/plugins/ folder and add this:

Code: Select all

    nuke.pluginAddPath("/usr/OFX/Plugins/OctaneForNuke", addToSysPath=False)

Nuke 9.0v5 start and loads the plugin fine.
When i try to start OctaneRender i got the following:

Code: Select all

    /usr/foundry/Nuke9.0v5/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by /usr/OFX/Plugins/OctaneForNuke/OctaneRender.so)

Is it correct that liboctane.so is also placed into /usr/OFX/Plugins/OctaneForNuke/ ?
I have the following files inside this folder:

Code: Select all

    /usr/OFX/Plugins/OctaneForNuke$ ls
    liboctane.so 
    ocsWriter.so               
    OctaneRenderLogo.png
    menu.py       
    octane.dat                 
    OctaneRender.so
    MeshLogo.png 
    OctaneReferenceGeometry.so 
    RendertargetLogo.png

[face_off]

Hi John - did you include the LD_PRELOAD environment variable? http://render.otoy.com/universe.php#43Installation

And yes, lboctane.so needs to be in the same folder as OctaneRender.so.

Paul

[JohnMesh]

Thanks face for this headup,

LD_PRELOAD included now for

Code: Select all

env LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 /usr/foundry/Nuke9.0v5/Nuke9.0

Code: Select all

/usr/foundry/Nuke9.0v5/Nuke9.0: /usr/foundry/Nuke9.0v5/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/x86_64-linux-gnu/libstdc++.so.6)

[face_off]

Thanks John. The LD_PRELOAD is required because whilst both Nuke and Octane are compiled with the same version of the C++ compiler, the libraries shipped with Nuke are earlier that those required by Octane. The LD_PRELOAD is working for me because I have installed the correct libraries, but they are probably not on your system. This is a serious impediment to running Nuke on Linux which I think TheFoundry need to address. It's been an issue for many years. There are quite a few threads on it - including http://community.thefoundry.co.uk/discu ... 1&t=104371 and http://community.thefoundry.co.uk/discu ... ld_preload.

I think the solution is to add libgcc_s.so.1 to tge LD_PRELOAD environment variable.

So it will be something like:

Code: Select all

setenv LD_PRELOAD "/usr/lib/libstdc++.so.6:/lib64/libgcc_s.so.1"

You can also just rename "/usr/foundry/Nuke9.0v5/libstdc++.so.6" and "/usr/foundry/Nuke9.0v5/libgcc_s.so.1".

Good luck.

Paul

[JohnMesh]

You can also just rename "/usr/foundry/Nuke9.0v5/libstdc++.so.6" and "/usr/foundry/Nuke9.0v5/libgcc_s.so.1".
Paul

That solved the issue. I will test the plug now and reply here if i found something

[JohnMesh]

One last thing before i dig into it...
I see its already available as BETA license, so can i just purchase it and use it permanently for nuke?

[face_off]

I see its already available as BETA license, so can i just purchase it and use it permanently for nuke?

Yes John - the same plugin license will work with either the Windows or Linux version (and the OSX version too if I can ever get it to compile).

Paul

[JohnMesh]

I already throwed some bucks over
Keep on the good linux support!!

[face_off]

Thanks John