OctaneRender 2023.1 for Houdini production (2023.1.0.2) Tweet

[PDivision1]

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

Houdini production builds supported by this release: 19.0.720, 19.5.534, 19.5.569, 19.5.605 - 19.5.805, 20.0.506.

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 compatibility Houdini 20 build is supported (gcc9.3).
It can only be installed by downloading it from the downloads page since it's not visible in the Launcher:
https://www.sidefx.com/download/daily-b ... ction=true
or direct download link: houdini-20.0.506-linux_x86_64_gcc9.3.tar.gz
We are looking into supporting the gcc11.2 build.

New features
To learn more about the new features and improvements of OctaneRender 2023.1, please check out the 2023.1 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.

Downloads

Release 2023.1.0.2 Studio+ license
Windows Houdini 19.0.720 - https://render.otoy.com/customerdownloa ... _Win64.zip
Windows Houdini 19.5.534 - https://render.otoy.com/customerdownloa ... _Win64.zip
Windows Houdini 19.5.569 - https://render.otoy.com/customerdownloa ... _Win64.zip
Windows Houdini 19.5.605 - https://render.otoy.com/customerdownloa ... _Win64.zip
Windows Houdini 19.5.805 - https://render.otoy.com/customerdownloa ... _Win64.zip
Windows Houdini 20.0.506 - https://render.otoy.com/customerdownloa ... _Win64.zip

Linux Houdini 19.0.720 - https://render.otoy.com/customerdownloa ... dio%2B.zip
Linux Houdini 19.5.534 - https://render.otoy.com/customerdownloa ... dio%2B.zip
Linux Houdini 19.5.569 - https://render.otoy.com/customerdownloa ... dio%2B.zip
Linux Houdini 19.5.605 - https://render.otoy.com/customerdownloa ... dio%2B.zip
Linux Houdini 19.5.805 - https://render.otoy.com/customerdownloa ... dio%2B.zip
Linux Houdini 20.0.506 - https://render.otoy.com/customerdownloa ... dio%2B.zip

Release 2023.1.0.2 macOS Prime license
MacOS Houdini 19.5.534 - https://render.otoy.com/downloads/48/b7 ... _Prime.zip
MacOS Houdini 19.5.569 - https://render.otoy.com/downloads/a5/07 ... _Prime.zip
MacOS Houdini 19.5.605 - https://render.otoy.com/downloads/7d/36 ... _Prime.zip
MacOS Houdini 19.5.805 - https://render.otoy.com/downloads/e8/3e ... _Prime.zip
MacOS Houdini 20.0.506 - https://render.otoy.com/downloads/ce/86 ... _Prime.zip

Release 2023.1.0.2 Demo version
Windows Houdini 19.0.720 - https://render.otoy.com/plugindownloads ... _Win64.zip
Windows Houdini 19.5.605 - https://render.otoy.com/plugindownloads ... _Win64.zip
Windows Houdini 19.5.805 - https://render.otoy.com/plugindownloads ... _Win64.zip
Windows Houdini 20.0.506 - https://render.otoy.com/plugindownloads ... _Win64.zip

Linux Houdini 19.0.720 - https://render.otoy.com/plugindownloads ... x_Demo.zip
Linux Houdini 19.5.605 - https://render.otoy.com/plugindownloads ... x_Demo.zip
Linux Houdini 19.5.805 - https://render.otoy.com/plugindownloads ... x_Demo.zip
Linux Houdini 20.0.506 - https://render.otoy.com/plugindownloads ... x_Demo.zip

Release Notes
=============================================
RELEASE 2023.1.0.2
=============================================
* PLUGIN FEATURES AND FIXES:
- Fixed Deadline submission issues (revereted change in the HO_img_fileFormat parameter)
Note: you may get incorrect output files extension when using TIFF or JPEG formats (these formats were recently added and Deadline scripts are not aware of them yet). If it happens to you, please send a ticket to the Deadline support so that they fix it in the next release.
Since the parameter was reverted, you may see the error message when opening files saved with plugin version 2023.1.0.0 (ROP's image file format will be reset to png).
- Fixed bug with ROP's file format being always reset to PNG when opening files
- Fixed a crash when switching multiple ROPs
- Fixed tessellate ngons produces additional polygon from curves
- Fixed regression in gradient ramps when the first and last control point wasn't working correctly
- When changing "interpolation type" dropdown, it will also change the "interpolation" of all the gradient control points to the closest one (only affects the gradient preview so that it looks closer to what you would see in the octane standalone)

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

[Renbry]

While I was able to submit to the farm again, this build exhibits the issue of working in a GUI and not in batch mode (on the farm) which I believe we saw in a previous Linux build/s

Screenshot showing this strange situation.

Reverting back down to 2023.1.0 as no time to Beta test while delivering.

Houdini 19.5.773

[PDivision1]

While I was able to submit to the farm again, this build exhibits the issue of working in a GUI and not in batch mode (on the farm) which I believe we saw in a previous Linux build/s

Screenshot showing this strange situation.

Reverting back down to 2023.1.0 as no time to Beta test while delivering.

Houdini 19.5.773

As far as I can tell from your screenshot, the problem here is OctaneRender plugin isn't loaded when running hython.
There should be some octane logs when you run hython, here is an example of running hython on linux:

Code: Select all

/opt/hfs19.5.805/bin/hython

[Octane]      Octane Render for Houdini. Build 2023.1.0.2 (Build date: Nov 22 2023 21:34:24)
[Octane] Octane API: 2023.1
[Octane] HDK API: 19.5.805
[Octane] Houdini host version: 19.5.805
[Octane] Initializing Octane API
Authorization required, but no authorization protocol specified
[Octane] Octane API ready. Initialization time: 2.780 seconds
[Octane] No valid OCIO config found in the 'OCIO' environment variable
[Octane] Octane network rendering enabled. Initialization time: 0.001 seconds
[Octane] Loading preferences from: /home/username/houdini19.5/octane.pref
17:29:36 INFOR: [nodes] -------------  Registering Octane VOP nodes
[Octane] 17:29:36 INFOR: [nodes] -------------  Registering Octane VOP nodes
17:29:36 INFOR: [nodes] -------------  Octane VOP nodes registered
[Octane] 17:29:36 INFOR: [nodes] -------------  Octane VOP nodes registered
17:29:36 INFOR: [nodes] -------------  Registering the plugin custom VOP nodes
[Octane] 17:29:36 INFOR: [nodes] -------------  Registering the plugin custom VOP nodes
17:29:36 INFOR: [nodes] -------------  Plugin custom VOP nodes registered
[Octane] 17:29:36 INFOR: [nodes] -------------  Plugin custom VOP nodes registered
Python 3.9.10 (main, Sep 15 2022, 18:00:44)
[GCC 9.3.1 20200408 (Red Hat 9.3.1-2)] on linux
Houdini 19.5.805 hou module imported.
Type "help", "copyright", "credits" or "license" for more information.


And here is a screenshot of the worker logs with octane properly initialized:


Here you can see that octane is initialized before "Detected Houdini Version:" message. In your screenshot there is no errors before this line, which means octane didn't fail to initialize but rather wasn't found in the path so no loading was triggered.
Could you please make sure octane plugin is initialized successfully when you run hython? It may be related to paths in the environment.

To be clear: running this command on your linux worker machines (not only the machine that's submitting work) should output octane plugin initialization logs:

Code: Select all

/opt/hfs19.5/bin/hython

[Renbry]

Yes, that's the case. Hython isn't picking up the plugin reliably even after a System reboot however swapping back to the older plugin has them working perfectly.

The way we have Octane setup is to use a 'current version' folder on the network which allows me to swap in/out versions as they release; so the system is always LIVE and either works or doesn't.

Not sure why your Hython likes this and mine reacts badly but it's part of the mystery I can't afford to diagnose right now. I'll sit back for a while, get this massive job delivered and see where things stand in a while.

[galleon27]

You need to change the default file path from $HIP/render/$HIPNAME.$OS.$F4.$OCTANE_PASS to $HIP/render/$HIPNAME.$OS.$OCTANE_PASS.$F4
You can't import as a sequence with the default one.

[PDivision1]

You need to change the default file path from $HIP/render/$HIPNAME.$OS.$F4.$OCTANE_PASS to $HIP/render/$HIPNAME.$OS.$OCTANE_PASS.$F4
You can't import as a sequence with the default one.

Thank you for reporting, this will be changed in the next release

[SilentPartnersStudio]

NT_BIT_MASK_DL __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_15
NT_BIT_MASK_DL __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_17
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_15
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_17
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_15
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_17
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_15
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_17
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_15
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_17

When I am working in houdini 20.0.506 I am getting a lot of messages that popup in the console about invalid parameter names.
Also when I first open a scene I get a big readout of errors

Load warnings for C:/Users/SPS/Desktop/particle_01.hip

Warning: Problem while synchronizing child node:
Warning: Skipping unrecognized parameter "borderMode".
[/shop/octane_rendertarget_dl1/octane_vopnet1/DaylightTexture]

Warning: Unknown channel(s) "oldVolumeBehavior" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_KERN_PATHTRACING1]

Warning: Skipping unrecognized parameter "borderMode".
[/shop/octane_rendertarget_dl1/octane_vopnet1/EnviroTexture]

Warning: Unknown channel(s) "oldVolumeBehavior" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_KERN_PMC1]

Warning: Unknown channel(s) "oldVolumeBehavior" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_KERN_DIRECTLIGHTING1]

Warning: Unknown channel(s) "premultiplied_alpha, maxUpsamplingInterval" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_IMAGER_CAMERA1]

Warning: Skipping unrecognized parameter "borderMode".
[/shop/octane_rendertarget_dl1/octane_vopnet1/CamEnviroTexture]

Warning: Unknown channel(s) "borderMode" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/DL_AO_Texture]

Warning: Unknown channel(s) "distortionTexture[rgb], customAperture[rgb]" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_CAM_UNIVERSAL1]

Warning: Skipping unrecognized parameter "distortionTexture".
Skipping unrecognized parameter "customAperture".
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_CAM_UNIVERSAL1]

[PDivision1]

NT_BIT_MASK_DL __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_15
NT_BIT_MASK_DL __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_17
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_15
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_17
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_15
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_17
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_15
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_17
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_15
NT_BIT_MASK_PT __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name globalLightIdMask_17

When I am working in houdini 20.0.506 I am getting a lot of messages that popup in the console about invalid parameter names.
Also when I first open a scene I get a big readout of errors

Load warnings for C:/Users/SPS/Desktop/particle_01.hip

Warning: Problem while synchronizing child node:
Warning: Skipping unrecognized parameter "borderMode".
[/shop/octane_rendertarget_dl1/octane_vopnet1/DaylightTexture]

Warning: Unknown channel(s) "oldVolumeBehavior" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_KERN_PATHTRACING1]

Warning: Skipping unrecognized parameter "borderMode".
[/shop/octane_rendertarget_dl1/octane_vopnet1/EnviroTexture]

Warning: Unknown channel(s) "oldVolumeBehavior" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_KERN_PMC1]

Warning: Unknown channel(s) "oldVolumeBehavior" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_KERN_DIRECTLIGHTING1]

Warning: Unknown channel(s) "premultiplied_alpha, maxUpsamplingInterval" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_IMAGER_CAMERA1]

Warning: Skipping unrecognized parameter "borderMode".
[/shop/octane_rendertarget_dl1/octane_vopnet1/CamEnviroTexture]

Warning: Unknown channel(s) "borderMode" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/DL_AO_Texture]

Warning: Unknown channel(s) "distortionTexture[rgb], customAperture[rgb]" converted to spare parameter(s).
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_CAM_UNIVERSAL1]

Warning: Skipping unrecognized parameter "distortionTexture".
Skipping unrecognized parameter "customAperture".
[/shop/octane_rendertarget_dl1/octane_vopnet1/NT_CAM_UNIVERSAL1]

As for the second part - error messages when you load a file for the first time - it's normal, should go away when you re-save the scene. It's complaining about deprecated properties that no longer exist in the plugin but were present when the scene was saved in the previous plugin version.

As for the "Invalid parameter name globalLightIdMask_17" messages: it's supposed to be handled by the version conversion when you open the old scene. In OctaneRender 2023.1 light mask ids up to 20 were added. This error indicates that you have an object with old number of light id properties.
What you can try:
- make sure you click "Accept" in the scene conversion prompt (with all the options selected which is by default):


- If scene conversion doesn't handle this, you can try finding what nodes in your scene have missing light ids, then remove and add again the ObjParm:

Or you can delete the node and create it from scratch. You'll need to setup the node and it's octane parameters from scratch unfortunately.

If the scene conversion doesn't handle you case well, it would be helpful if you could reduce the scene to only contain the problematic nodes and send it over to me for investigation.
Hope this helps!

[SilentPartnersStudio]

I can try this.
Although this is on a brand new scene with a fresh octane install
Happens every time I open the file, and every time I start a render

[PDivision1]

I can try this.
Although this is on a brand new scene with a fresh octane install
Happens every time I open the file, and every time I start a render

If the scene was created in the plugin version 2023.1, there should not be problems like that. It would be helpful if you could share this scene with me so that we investigate and fix it.
Doesn't have to be the whole scene (just delete nodes that don't contribute to the error).
But from what I see in the error messages - the scene seems to be created in the previous plugin version.