OctaneRender™ 4.01 for Houdini™ - production build 4.01.1.1

[juanjgon]

thank you for you suggestions.
I append the env. file.
As you can see I don t set variables for the Gamedevelper Toolkit there.
I use the houdini version that is specified in the plugins folder name.

The behaviour is kind of weird, because the Octane IPR shelf loads, but the buttons dont function.
The regular shelf does nt load at all.
I can create Octane materials in the shop context, but it gives errors. In the mat-context no nodes are avaible.
An Octane ROP can be selected in the Render menu but it gives an error...

The previous version works fine, as it is loaded by the other line in the file.
Setting the PATH variable does nt help either.

Hmm, so do you say that the 4.00.0.21 build was working fine and the new 4.01.1.1 doesn't work on the same system? This is something really weird, and I wonder why you can't load the regular shelf. What Linux version do you have installed on your system?

The only thing that comes to my mind is something broken inside the plugin /home/user/Octane_4.01.1.1_Houdini_16.0.736_Linux_gcc6.3.1 directory or a problem with the user $HOME Houdini cache folders. You could try to unzip the plugin again to be sure that all the plugin files are there, and you could also try to clean your Houdini $HOME folder directories (the $HOME folder is usually ~/houdini16.0 on Linux).

Thanks,
-Juanjo

[rohandalvi]

Hi,

Is it possible to load an Orbx file into Houdini Indie. Is there an importer?

It would be a nice option to have. If I have a fully shaded model in Octane stand alone then I use the orbx imported to load it into Houdini.

regards
Rohan

[juanjgon]

Hi,

Is it possible to load an Orbx file into Houdini Indie. Is there an importer?

It would be a nice option to have. If I have a fully shaded model in Octane stand alone then I use the orbx imported to load it into Houdini.

regards
Rohan

This is a planned feature in the short term. It should be ready along next month, after the holiday break, in the upcoming 2018.1 plugin builds.

Thanks,
-Juanjo

[Ferdinand13]

Hi Juanjo,

I'm considering to purchase a Houdini Indie license, once the Octane Render Studio license includes the additional plugins early next year (I'm currently on Cinema 4D). However, one of my biggest question is, will this combination allow me to make use of the additional render slave that comes with the OctaneRender Enterprise All-Access Annual subscription? I've been using this feature successfully within Cinema 4D so far and it's a real time saver.

The reason I'm asking is that the fine print for the Houdini plugin mentions "When using with Houdini Indie, the plugin will have a 4k limited resolution while rendering sequences, and the scene export and cloud rendering features will be disabled" and I don't know if this means, the render slave feature won't work when using the Houdini Indie version.

Would be great, if you could clarify. Thanks!

[juanjgon]

Hi,

The Octane native network rendering feature using local nodes should work without problems. The restrictions are related to the cloud or offline rendering only (exporting to uploading to the cloud .orbx files)

Thanks,
-Juanjo

[Ferdinand13]

Hi Juanjo,

Thanks for the quick reply! Yes, it's the local network rendering feature that I'd like to use. When you say that it "should work without problems", does that mean that you or one of your team has seen it in action? Sorry to be so 'verbatim' here, but I'd really kick myself, if I'd invest the $399 for the two year license and then it doesn't work

Best, Ferdinand

[acc24ex]

omg, having a hard time installing this, houdini noob, so

On Linux, Mac OS X and macOS systems, append a single line to enable OctaneRender for the user:

HOUDINI_PATH = "/path/to/octane;&"


On Windows systems, you need to set the PATH to point to the plugin bin folder as well:

PATH = "C:/path/to/octane/bin;$PATH"

... i've put it here at "C:\Octane_4.01.1.1_Houdini_17.0.416_demo_Win64"

so I've put up the path environemnt.. C:\Octane_4.01.1.1_Houdini_17.0.416_demo_Win64;$PATH
and the houdini.env HOUDINI_PATH = "C:\Octane_4.01.1.1_Houdini_17.0.416_demo_Win64;&"


.. seemed logical, got octane panel but error message when trying to create octane node
..been using the max version since the beta and this is a bit way too much work for first time users, why no installer?, and can someone help pls

EDIT
..
instruction unclear my phallus got stuck in the oven ..

sooo.. now it works
HOUDINI_DSO_ERROR = 2
PATH = "C:\Octane_4.01.1.1_Houdini_17.0.416_demo_Win64\bin;$PATH"
HOUDINI_PATH = "C:\Octane_4.01.1.1_Houdini_17.0.416_demo_Win64;&"

..this was supposed to all got into the .env file.. as I understood the path goes to the windows environment settings usually .. how did I confuse that (cause I'm old school?)

Gonna put this here for posterity .. anyway, update the manual and put in an actual example like this above?

[juanjgon]

Hi Juanjo,

Thanks for the quick reply! Yes, it's the local network rendering feature that I'd like to use. When you say that it "should work without problems", does that mean that you or one of your team has seen it in action? Sorry to be so 'verbatim' here, but I'd really kick myself, if I'd invest the $399 for the two year license and then it doesn't work

Best, Ferdinand

If you have this additional license for the render node, it is going to work with Houdini Indie version for sure. The plugin doesn't have any restriction related to the Octane native network rendering while working inside the Houdini Indie version.

Thanks,
-Juanjo

[Ferdinand13]

Thanks a lot for confirming this Juanjo! Things should be fine then. The Octane Render Studio render slave works flawless with the C4D plugin, so that means it should work in Houdini as well then. I’m pumped Can’t wait until all the plugins are made available in January.

Best, Ferdinand

[Stefan]

Happy new year Juanjo!
I just want confirm that the problem was solved with a fresh extraction.