OctaneRender 2018.1 for Houdini Production build 2018.1.3.0 Tweet

[ptunstall]

standalone renders fine I even pulled down that orbx I sent you on the other thread and it rendered without issue. I'll check the freeglut thing!! Thanks so much for the assistance Juanjo!

[ptunstall]

FREEGLUT!!!! OMG you are so wizardly amazing!!! Many thanks for helping out a linux noob!!!

[pixelstuff]

Hi I just can't seem to get any 2018 versions to work, are there specific requirements? I'm getting a beachball on mac and a black screen in mplay, is there a log file to find out whats happening? I have tried this on 3 different 2018 releases.

HOUDINI_DSO_ERROR = 2
HOUDINI_PATH = "Octane_2018.1.3.0_Houdini_17.5.173_OSX;/Applications/redshift/redshift4houdini/17.5.173;&"

Nvidia 387.10.10.10.40.105

Cuda 410.130

Is there any conflict with the info above?

[juanjgon]

Hi I just can't seem to get any 2018 versions to work, are there specific requirements? I'm getting a beachball on mac and a black screen in mplay, is there a log file to find out whats happening? I have tried this on 3 different 2018 releases.

HOUDINI_DSO_ERROR = 2
HOUDINI_PATH = "Octane_2018.1.3.0_Houdini_17.5.173_OSX;/Applications/redshift/redshift4houdini/17.5.173;&"

Nvidia 387.10.10.10.40.105

Cuda 410.130

Is there any conflict with the info above?

Hi,

Well, I suppose that in the HOUDINI_PATH variable you should write the full path to the plugin directory, not only its name, but I'm not sure if this is the problem because in this case, you should not get the Octane plugin menu, shelf or nodes. What is the full path to the Octane plugin?

Thanks,
-Juanjo

[pixelstuff]

Hi Its

/Users/macpro/Octane_2018.1.3.0_Houdini_17.5.173_OSX

it does the same thing with the full path, I tested it just incase

I have v4 in the same directory and that works, but would it be better to place it in another location? permissions maybe?

[juanjgon]

Nope, I don't think that this problem could be related to the permissions at all. So do you say that v4 plugin works fine, but the v2018.1 not? ... weird, because your drivers seem the right version. Do you know if Octane Standalone 2018.1 works fine on this system?

In the plugin options panel, you have the debug log options. Can you please enable the log to file option and attach the log that you get after rendering one scene?

Thanks,
-Juanjo

[pixelstuff]

Here is the log file. Houdini scene with a pig head.
https://we.tl/t-78LELpcLGs

I tested the 2018.1 standalone, it works when I opened the screws example scene.

[juanjgon]

Hmm, a crash at that point, while the scene is being extracted, makes no sense at all. Can you please attach the exact same scene that you are trying to render?

Thanks,
-Juanjo

[pixelstuff]

The link contains the simple test file(its the same on the project I'm working on also) and a screen recording when the mouse is outside of the mplay window it's beachballing frozen, but doesn't show in the recording just a cursor. Then requires a force quite crash.

https://we.tl/t-KvD3T2IixV

[juanjgon]

What a weird issue! Let me try to reproduce it here, but I don't understand why it happens only on MacOS, and while extracting the scene.

Thanks,
-Juanjo