OTOY Forums

This is a Beta release of the OctaneRender™ 2024.1.Beta_3.1 for Houdini™ plugin compiled with the Octane 2024.1 Beta 3 core. This 2024.1.Beta_3.1 release is available for the latest Houdini production builds on Windows x64, Linux, and macOS arm64.

Houdini production builds supported by this release: 19.5.805, 20.0.724, 20.0.751, 20.5.278, 20.5.332.

If you are not sure if your Houdini version is compatible with the plugin - just run it and you will see an error message in case of incompatibility.

Linux Note
On Linux only default Houdini builds are supported.
This means that for Houdini 20.0 and 20.5, gcc11.2 builds are supported, and for Houdini 19.5, gcc9.3 build is supported.

New features
To learn more about the new features and improvements of OctaneRender 2024.1 Beta 3, please check out the 2024.1 Beta 3 release post

Known bugs
On Linux, MPlay IPR may not be working. If you are having problems with it, please switch to QT5 IPR and disable "Render to MPlay" in ROP nodes.
Octane is still working on supporting OCIO V2.3 (the version that Houdini 20.5 uses). The workaround for now is to use the Houdini 20.0's OCIO files when you use Houdini 20.5. e.g. You can use 20.0.751's OCIO file by adding the below line in your houdini.env file for Houdini20.5. Downloads

Release 2024.1.Beta_3.1 Studio+ license
Windows Houdini 19.5.805 - https://render.otoy.com/customerdownloa ... _Win64.zip
Windows Houdini 20.0.724 - https://render.otoy.com/customerdownloa ... _Win64.zip
Windows Houdini 20.0.751 - https://render.otoy.com/customerdownloa ... _Win64.zip
Windows Houdini 20.5.278 - https://render.otoy.com/customerdownloa ... _Win64.zip
Windows Houdini 20.5.332 - https://render.otoy.com/customerdownloa ... _Win64.zip

Linux Houdini 19.5.805 - https://render.otoy.com/customerdownloa ... _Linux.zip
Linux Houdini 20.0.724 (gcc11.2) - https://render.otoy.com/customerdownloa ... _Linux.zip
Linux Houdini 20.0.751 (gcc11.2) - https://render.otoy.com/customerdownloa ... _Linux.zip
Linux Houdini 20.5.278 (gcc11.2) - https://render.otoy.com/customerdownloa ... _Linux.zip
Linux Houdini 20.5.332 (gcc11.2) - https://render.otoy.com/customerdownloa ... _Linux.zip

Release 2024.1.Beta_3.1 macOS Prime license
MacOS Houdini 19.5.805 - https://render.otoy.com/downloads/66/04 ... _macos.zip
MacOS Houdini 20.0.724 - https://render.otoy.com/downloads/a8/69 ... _macos.zip
MacOS Houdini 20.0.751 - https://render.otoy.com/downloads/ea/17 ... _macos.zip
MacOS Houdini 20.5.278 - https://render.otoy.com/downloads/42/1a ... _macos.zip
MacOS Houdini 20.5.332 - https://render.otoy.com/downloads/8a/0f ... _macos.zip

Release 2024.1.Beta_3.1 Demo version
Windows Houdini 19.5.805 - https://render.otoy.com/plugindownloads ... _Win64.zip
Windows Houdini 20.0.751 - https://render.otoy.com/plugindownloads ... _Win64.zip
Windows Houdini 20.5.332 - https://render.otoy.com/plugindownloads ... _Win64.zip

Linux Houdini 19.5.805 - https://render.otoy.com/plugindownloads ... _Linux.zip
Linux Houdini 20.0.751 (gcc11.2) - https://render.otoy.com/plugindownloads ... _Linux.zip
Linux Houdini 20.5.332 (gcc11.2) - https://render.otoy.com/plugindownloads ... _Linux.zip

Release Notes
=============================================
RELEASE 2024.1 Beta_3.1
=============================================
* PLUGIN FEATURES AND FIXES:
- Hotfix: Stop rendering instances if it's display flag is off

Common Issues and Solutions
- If the plugin doesn't work at all, set HOUDINI_DSO_ERROR = 2 in houdini.env and check for messages in the terminal.
- If you're missing libglut.so.3, install the freeglut package.
- If you are having any issues with the Deadline - please submit a support ticket to the AWS.

Happy rendering,
Your OTOY Team

Been curious for a while, will we ever be able to navigate in the live viewer, similar to Aoaktar's setup for C4D?

Thanks!

ryanaexavier wrote:Been curious for a while, will we ever be able to navigate in the live viewer, similar to Aoaktar's setup for C4D?

Thanks!

Thanks for bringing this up. Yes, we are looking into it. Hopefully this will be implemented in the next release.

That would be a nice feature to have, however having the viewport update more intelligently would also be really nice to have, for heavy scene every-time one needs to do a full-scene reload it's painful.

I think either Beta 3.0 or Beta 3.1 broke the z-depth info AOV.
(Edit: Just checked Beta 3.0, and the problem exists there too)
I've switched back and forth between 3.1 and 2.0, and z-depth outputs correctly in 2.0 (writing to exr files), but is missing in this version, while any other AOVs selected appear to output correctly.

This is using the 19.5.805 build.

I checked the contents of octane_mat_renderTarget1, and in both cases they appear to be wired up correctly.

vortexvfx wrote:I think either Beta 3.0 or Beta 3.1 broke the z-depth info AOV.
(Edit: Just checked Beta 3.0, and the problem exists there too)
I've switched back and forth between 3.1 and 2.0, and z-depth outputs correctly in 2.0 (writing to exr files), but is missing in this version, while any other AOVs selected appear to output correctly.

This is using the 19.5.805 build.

I checked the contents of octane_mat_renderTarget1, and in both cases they appear to be wired up correctly.

Is this difference the same as in Standalone? if you get the same result in Standalone 2024.1 Beta3 then it is core and not the plugin itself.
Can you post screenshots of the difference / or scene file? thanks!

ricky_otoy wrote:

vortexvfx wrote:I think either Beta 3.0 or Beta 3.1 broke the z-depth info AOV.
(Edit: Just checked Beta 3.0, and the problem exists there too)
I've switched back and forth between 3.1 and 2.0, and z-depth outputs correctly in 2.0 (writing to exr files), but is missing in this version, while any other AOVs selected appear to output correctly.

This is using the 19.5.805 build.

I checked the contents of octane_mat_renderTarget1, and in both cases they appear to be wired up correctly.

Is this difference the same as in Standalone? if you get the same result in Standalone 2024.1 Beta3 then it is core and not the plugin itself.
Can you post screenshots of the difference / or scene file? thanks!

Hey, thanks for responding. I'm neck-deep in a project at the mo... I'll try and find time over the weekend to check standalone.
The scene is as simple as chuck a cube in the middle, switch on the Z-Depth Info AOV, and render to an exr... under beta 3.0/3.1, the Z-Depth layer is simply missing from the exr, while under beta 2.0 it's present.

vortexvfx wrote:

ricky_otoy wrote:

vortexvfx wrote:I think either Beta 3.0 or Beta 3.1 broke the z-depth info AOV.
(Edit: Just checked Beta 3.0, and the problem exists there too)
I've switched back and forth between 3.1 and 2.0, and z-depth outputs correctly in 2.0 (writing to exr files), but is missing in this version, while any other AOVs selected appear to output correctly.

This is using the 19.5.805 build.

I checked the contents of octane_mat_renderTarget1, and in both cases they appear to be wired up correctly.

Is this difference the same as in Standalone? if you get the same result in Standalone 2024.1 Beta3 then it is core and not the plugin itself.
Can you post screenshots of the difference / or scene file? thanks!

Hey, thanks for responding. I'm neck-deep in a project at the mo... I'll try and find time over the weekend to check standalone.
The scene is as simple as chuck a cube in the middle, switch on the Z-Depth Info AOV, and render to an exr... under beta 3.0/3.1, the Z-Depth layer is simply missing from the exr, while under beta 2.0 it's present.

Thanks, no need to check Standalone. It isn't that it isn't exporting more as there seems to be an issue within the Render Target sub-graph. For now you can get around it by setting the AOV count 1 higher to 26. Because the assignments shifted down, Z-Depth is effectively unassigned by sharing the pin with wireframe. (That should show the Z-depth AOV in IPR afterwards too)

Note that this issue will affect all last connected AOV pins (somehow things shifted).

Appreciate the report!

ricky_otoy wrote:Thanks, no need to check Standalone. It isn't that it isn't exporting more as there seems to be an issue within the Render Target sub-graph. For now you can get around it by setting the AOV count 1 higher to 26. Because the assignments shifted down, Z-Depth is effectively unassigned by sharing the pin with wireframe. (That should show the Z-depth AOV in IPR afterwards too)

Note that this issue will affect all last connected AOV pins (somehow things shifted).

Appreciate the report!

Hah, y'know, I almost tried doing that on a hunch too.
Much thanks for looking into it!