OctaneRender™ 2.2 for Houdini™ build 2.24.0.0

[juanjgon]

Hi,

This is the fourth beta release of the OctaneRender™ 2.2 for Houdini™ plugin. This 2.24.0.0 build is available for the last build of Houdini 13.0, all the Houdini 14.0 current production builds, and the release candidate of Houdini 15.0, in Windows x64, Linux gcc4.8 and OSX 10.10

Downloads
Links removed due to incompatibility introduced in current versions of Houdini, please contact [email protected] for further information.

Documentation
http://render.otoy.com/manuals/Houdini/



=============================================
RELEASE 2.24.0.0
=============================================

* NEW FEATURES:
- New parameter "Instancing MB computed from velocity attribute" in the Octane OBJ custom spare parameters. Can be enabled in the OBJ instance nodes to compute the instances motion blur using the "v" velocity attribute. Useful when instancing over particle system or other OBJ nodes with variable ptnum IDs, or when only the instances translation motion blur is useful in the scene.
- Instancing over particle systems or other OBJ sequences without a constant topology is now detected and a error message is displayed to warn the users.
- Support of the Octane LiveDB. New icon in the shelf to open the LiveDB asset database and import the material to a new SHOP node.
- New "LiveDB" tab in the plugin options panel. In this tab you can set the directory to store the downloaded LiveDB textures and the LocalDB path.
- Added the Octane "Transformation Value" and "Value Enum" nodes.
- New CTRL+click function in the IPR to pick a material and open it in the Octane native node editor. This function must be used only to export the material to the LiveDB/LocalDB databases. EDITING THE MATERIAL IN THIS NODE EDITOR IS DANGEROUS AND CAN CRASH HOUDINI.

* BUGS FIXED:
- Fixed an internal architecture problem with the Octane attribute names translated to the Houdini VOP nodes. This change should not affect the old scenes.
- Fixed the network rendering bandwidth test.
- The version number of slaves is printed in the network render dialog.
- Fixed fully transparent planes behaving incorrectly in scattering media.
- Fixed a problem with the Octane OBJ spare parameters tab, that sometimes was not add at the end of the available parameters in the OBJ nodes.
- Fixed the crashes due to instancing over particle systems or OBJ sequences without variant ptnum or variant particle counts.


-Juanjo

[fellowla]

Awesome work Juanjo!

I noticed when you import materials from the liveDB, every parameter of the nodes within are promoted (or have a corresponding octane float/bool/grayscale value node plugged into them) but there are no linked corresponding channels on the material node (Only the default OGL settings) to any of them, and none of them are named after what they represent. Would it be possible to create a corresponding parameter on the top level material node that links to a promoted channels node whenever it is created? Basically mimicking the default behavior of how a parameter node works inside a vop network?

-Nathan

[juanjgon]

Let me think about it Nathan. I will try to simplify the node tree from LiveDB if possible, or at least rename the final attributes nodes. I could also promote parameters to the root SHOP node, but the question is what parameters the plugin should promote ... a lot of this materials are very complex, and promote all the nodes parameters is not really very useful.

-Juanjo

[juanjgon]

There is a problem in the RenderTarget HDA in this build. The texture environments are not working due to a change in the Octane VOP nodes parameters names, not updated in the HDA. Attached to this message is the fixed "octane_rt.otl", you only need to replace it in your plugin/otls folder.

[juanjgon]

I have updated all the 2.24.0.0 .zip files to fix the render target HDA issue in all the builds.

The new .zip files for Linux and Windows also includes a build for the current Houdini 15.0 release candidate, and a build compatible with the last release of Houdini 13.0.

Thanks,
-Juanjo

[Techie]

It's working great, thanks a lot Juanjo!

[Angelos]

Hi
I have a problem with submission Octane job to Deadline

Code: Select all

Traceback (most recent call last):
  File "//spbvis2/dlrep7/submission/Houdini/Main\SubmitHoudiniToDeadline.py", line 1373, in SubmitJobCallback
    paddedOutputFile = GetOutputPath( renderNode ).eval()
AttributeError: 'str' object has no attribute 'eval'

Could you fix it please?

Thanks

[juanjgon]

Hi
I have a problem with submission Octane job to Deadline

Code: Select all

Traceback (most recent call last):
  File "//spbvis2/dlrep7/submission/Houdini/Main\SubmitHoudiniToDeadline.py", line 1373, in SubmitJobCallback
    paddedOutputFile = GetOutputPath( renderNode ).eval()
AttributeError: 'str' object has no attribute 'eval'

Could you fix it please?

Thanks

Hi,

Have you tried to report this issue to the Deadline team to know what they think about it? Really I have no idea about the meaning of this error, I think that it is not related to the Octane plugin itself. I am not sure how Deadline is managing the render tasks and if it is compatible with the Octane plugin out of the box ... perhaps there is something wrong in our plugin, or perhaps Deadline could need a new script to work with the Octane plugin.

Feel free to send them also my contact ([email protected]) in case the Deadline team could need to know something about the Octane plugin to make it compatible with Deadline. I have no problems in try to make the Octane plugin compatible with Deadline, but this error seems a problem in the controller side, and I need to know the origin of the issue to try to fix it.

-Juanjo

[Angelos]

I believe the problem that the Deadline don't know the output path values that use your Octane plugin.
Here's the python submission file to Deadline:
https://dl.dropbox.com/s/ts52qygxiz8rj6 ... eadline.py

I think I can add this values manually in this file just need to know "outputFile = node.parm" values

[juanjgon]

The Octane ROP image files output path parameter is "HO_img_fileName", so you could try to add to the script these lines, in def GetOutputPath( node ): function

Code: Select all

elif type == "Octane":
        outputFile = node.parm("HO_img_fileName")

(The type of the node can be also reported as elif type == "Octane_ROP": ... I am not sure)

Let me know if it works. If you need to know more parameter names of the Octane ROP, you could also get them sliding the cursor over the parameter, as you can see in the attached screen grab.

-Juanjo