OctaneRender 2022.1 for Houdini beta build 2022.1.0.2 XB3

[juanjgon]

Hi,

This is a beta release of the OctaneRender™ 2022.1 for Houdini™ plugin compiled with the Octane 2022.1 XB3 core. This 2022.1.0.2 release is available for the latest Houdini production builds on Windows x64 and Linux gcc6.3.1.

Houdini production builds supported by this release: 18.0.597, 18.5.759, 19.0.589, 19.0.622, 19.0.657 and 19.5.303

As with all experimental builds, we advise to not use this release for production purposes. We are trying to, but we can't guarantee that scenes saved with this version will be compatible in future releases.

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


Release 2022.1.0.2Enterprise subscription license
https://render.otoy.com/customerdownloa ... rprise.zip
https://render.otoy.com/customerdownloa ... rprise.zip
MacOS version: WIP

Release 2022.1.0.2 Studio subscription license
https://render.otoy.com/customerdownloa ... studio.zip
https://render.otoy.com/customerdownloa ... studio.zip
MacOS version: WIP

Standalone 2022.1 XB3 version for the network rendering nodes
viewtopic.php?f=15&t=80156


Release Notes
=============================================
RELEASE 2022.1.0.2 XB3
=============================================
* PLUGIN FEATURES AND FIXES:
- Added H19.5.303 plugin build.
- RenderTarget HDA "Exposure" parameter range updated to 1..10
- Fixed a problem with several parameters in the texture image VOP nodes.
- Support of animated attributes while rendering in update scene mode.
- Fixed the "Premultiplied Alpha" ROP option.
- New option "MPlay bake color correction" in the ROP node, disabled by default to let MPlay manage the color correction. This option also affects the MPlay IPR and the IPR snapshots.
- IPR system updated to remember the latest ROP node used.
- Added support for the output sop.

* OCTANE 2022.1 XB3 NEW FEATURES:
- Improved dithering for overlapping tiles to avoid visible noise at seams.
- Reduced artifacts with saturated highlights if using both highlight compression and saturate to white.
- Improved hair rendering to fix various artifacts that could happen in some corner cases.
- OSL shaders can now be named using metadata.
- Fixed issue with the denoiser producing blurry results when using the photon tracing kernel.
- Fixed issue causing dispersion to render incorrectly.
- Fixed issue causing photon tracing kernel to never reach the maximum number of samples.
- Fixed issue causing wrong type to be displayed in OSL compiler warning.
- Fixed issue causing RTX to effectively be disabled even when enabled in the device settings.
- Fixed a few scenarios where mix material would cause wrong output with nested dielectircs.
- Fixed render regression with noise pass with scenes with volume or environment medium.
- Fixed application crash when exporting a mesh without material assignments to Alembic.
- Fixed performance regression causing some Vectron instances to render significantly slower.
- Fixed render hang in scenes using the dirt or curvature shaders.
- Fixed artifacts produced when using environment medium with a custom AOV.
- Fixed issue causing texture emission visibility flags misbehave when using the photon tracing kernel.
- Fixed issue with autobumpmap not rendering correctly when RTX was on.
- Fixed issue causing partial scene exports into ORBX to not to work.
- Fixed crash on render nodes using more than one GPU when switching kernels.
- Fixed laggy imaging/tone-mapping while rendering is progressing.
- Fixed regression causing nested dielectrics material priority no longer to work with non-specular materials.
- Fixed standard surface extra roughness slider range so it scroll from -1 to 1
- Fixed issue causing slow updates when using AI light.
- Fixed a bug that caused custom AOVs to get darker when the single scatter amount is changed.



Happy rendering,
Your OTOY Team

[tripledistilled]

Yay. Cheers for this.

I was also hoping for a macOS version too. Any chance there is a rough ETA? Curious if I should be thinking days/weeks/months.

[juanjgon]

Yay. Cheers for this.

I was also hoping for a macOS version too. Any chance there is a rough ETA? Curious if I should be thinking days/weeks/months.

Sorry, I'm still working on it. Anyway, I'm afraid that the macOS build won't be available until I'm back from my just-started vacation break, that is, early September.

Thanks for your patience,
-Juanjo

[vurt]

Sorry, I'm still working on it. Anyway, I'm afraid that the macOS build won't be available until I'm back from my just-started vacation break, that is, early September.

Thanks for your patience,
-Juanjo

hope it will include the new Apple Silicon native build for Houdini

[HandcraftedMedia]

What do I need to do for stuff to show up in the "Ocio Look" section under the Octane ROP or the "ocioViewName" on the Ocio view node? Am having a super hard time getting the right colorspace in Octane. I have OCIO setup in Houdini using the 1.2 config https://acescentral.com/knowledge-base- ... nfig-file/. Attached some reference pictures of what I see.

[coresign]

Add the QT5 IPR to auto-update the newly created objects and material path change in sop level please!
And expand the function of "Octane_IPR_updateSelectedObjects"

[juanjgon]

What do I need to do for stuff to show up in the "Ocio Look" section under the Octane ROP or the "ocioViewName" on the Ocio view node? Am having a super hard time getting the right colorspace in Octane. I have OCIO setup in Houdini using the 1.2 config https://acescentral.com/knowledge-base- ... nfig-file/. Attached some reference pictures of what I see.

As far as I know, a lot of OCIO configs don't have any look. The color space display and view parameters should be enough.

Thanks,
-Juanjo

[HandcraftedMedia]

Ah well the issue is that my view field is empty also... Do you know why that is?

[WhyGee]

same here. I have to manually fix it every time

[juanjgon]

same here. I have to manually fix it every time

You need to select the ocio display to populate the views menu, even if it has by default the right display. As soon as you select the display, the views menu should be ready.

-Juanjo