OctaneRender 2019.1 for Houdini Production build 2019.1.4.0

[motionskill]

You are right. I am moving from C4d to Houdini and forgot that Houdini doesn't create UV by default on objects like in C4D.

Anyway, I was afraid, that switching from C4D to Houdini Octane is hard. But no, I like Houdini version even more, And surprise - All my Local DB materials from C4D is 90% working in Houdini also. So, waiting for 2020 which must be even better.

But still one question is not clear. Many users and in many videos I saw that Octane Houdini has one problem - it doesn't support Point Attributes. But I see that 2019 version has Color Vertex Attribute Node, which is not described in documentation but it allows to get Point attributes. So, it's available in 2019 version?

[juanjgon]

Octane 2019.1 supports vertex attributes in the mesh objects. In the upcoming Octane 2020.1 plugin build, the point attributes support has been extended to the particle objects (and more to come)

Thanks,
-Juanjo

[modjtaba]

Hi
I've added this build to houdini 17.5.391 but it gets this error...
126 couldn't load in attachment ...
Thanks

[juanjgon]

Hi,

This can be a problem with the NVIDIA drivers version or a problem with the installation. It seems that you are installing the plugin inside the Houdini $HOME folder. This is usually not a good idea, because you could mix by mistake Octane plugins or system files from several Octane builds, breaking the installation. Perhaps you should fully clean this $HOME folder and install the plugin again.

Thanks,
-Juanjo

[modjtaba]

I'm just copying files to my documents Houdini version folder after cleaning it completely.
whats the better alternative?
where is $HOME?
sorry for the noob question.

[juanjgon]

$HOME is the main Houdini configuration folder, that yes, usually in Windows lives in Documents/houdini17.5. Although the plugin can work if you put all the plugin files and folder inside this directory, it is better to put them into another place and configure the houdini.env file with the PATH and HOUDINI_PATH variables, as you can see in the docs:
https://docs.otoy.com/HoudiniH/HoudiniP ... oudini.htm

In any case, inside a clean $HOME folder the plugin also should work, so if you still have this problem, you should check if you are installing the right plugin build for your Houdini version, and if Octane can work without problems on this system, perhaps checking if Octane Standalone works fine.

Thanks,
-Juanjo

[modjtaba]

its a clean installation and attachment obviously shows versions are same...

[juanjgon]

Hmm, do you know if Standalone 2019.1.4 can work fine on this system? If it works fine the problem is on the Houdini plugin installation time for sure.

Thanks,
-Juanjo

[juanjgon]

Hey so I'm assuming the orbx fix in this latest release doesn't fix orbx exporting for multiple frames on fullscene reload. Also we cannot use single frames exported orbx files because motion blur DOES NOT WORK. Is there any way to prioritize this functionality?

Hi,

The next Octane 2020.1 plugin build will add the support of mesh and hair objects with a non-constant topology while rendering or exporting sequences in update mode. This should help while exporting these kinds of scenes that only could be rendered in full scene reload mode before.

Thanks,
-Juanjo

[ptunstall]

You are beautiful!!!!