OctaneRender for HoudiniSolaris 2026.4.0.0

[frankserin]

Hi there,

I'm working on a scene where you can see the "Visibility" issues because the original scene couldn't be shared with you. I wiil send you very soon.

Meanwhile, I'm experiencing a new bug/crash with Octane and particles. The crash occurs every time I start the IPR in Solaris, before the first image is rendered. Houdini reports a Segmentation Fault and creates a recovery file.

The crash does not appear to originate from Houdini itself, but from Octane during IPR initialization, possibly while setting up the render target.

Scene about new bug/crash: https://drive.google.com/file/d/1fldFy0_zOF87b9RpzCP2rizWojPXaBg1/view?usp=drive_link

[frankserin]

Hi there again, sorry for posting so much, but I keep finding more things that I feel aren't working.

I've been spending more time exploring Octane for Solaris, and the more I use it, the more I find features that are missing or don't integrate well with the Solaris workflow.

One example is Copernicus. Houdini's native workflow relies on `op:` paths to reference COP textures directly, but Octane doesn't seem to support them. If `op:` isn't supported, how are we supposed to use Copernicus procedurally inside Octane for Solaris? Is there any workflow I'm missing?

Another limitation I found is the lack of basic HDRI color controls. There doesn't seem to be any way to adjust exposure, saturation, or other color corrections for an HDRI used in an Octane Dome Light.

In Karma, this can be solved using Light Filters, allowing artists to tweak the lighting without modifying the original HDRI. Octane doesn't appear to offer an equivalent solution.

It would be great if Octane could support these native workflows more completely. Right now these feel like unnecessary limitations in day to day production. Thanks!

[BK]

Hi there,

I'm working on a scene where you can see the "Visibility" issues because the original scene couldn't be shared with you. I wiil send you very soon.

Meanwhile, I'm experiencing a new bug/crash with Octane and particles. The crash occurs every time I start the IPR in Solaris, before the first image is rendered. Houdini reports a Segmentation Fault and creates a recovery file.

The crash does not appear to originate from Houdini itself, but from Octane during IPR initialization, possibly while setting up the render target.

Scene about new bug/crash: https://drive.google.com/file/d/1fldFy0_zOF87b9RpzCP2rizWojPXaBg1/view?usp=drive_link

Hi there,

Thank you so much for the scene.

We are able to replicate the Segmentation Fault issue with the latest release.
We have created an internal ticket for our developer to investigate.

It looks like we can import the cache but not the out node for some reason.
We hope to get this fixed asap..

Cheers

[BK]

Hi there again, sorry for posting so much, but I keep finding more things that I feel aren't working.

I've been spending more time exploring Octane for Solaris, and the more I use it, the more I find features that are missing or don't integrate well with the Solaris workflow.

One example is Copernicus. Houdini's native workflow relies on `op:` paths to reference COP textures directly, but Octane doesn't seem to support them. If `op:` isn't supported, how are we supposed to use Copernicus procedurally inside Octane for Solaris? Is there any workflow I'm missing?

Another limitation I found is the lack of basic HDRI color controls. There doesn't seem to be any way to adjust exposure, saturation, or other color corrections for an HDRI used in an Octane Dome Light.

In Karma, this can be solved using Light Filters, allowing artists to tweak the lighting without modifying the original HDRI. Octane doesn't appear to offer an equivalent solution.

It would be great if Octane could support these native workflows more completely. Right now these feel like unnecessary limitations in day to day production. Thanks!

Hi there,

No worries..
The `op` paths are already supported however, it requires to reload when we make changes.
We are aware of this issue and will get it resolved in future.

We are currently discussing if there is a workaround to support the Light Filters node.

For now, please use the HDRI color controls or use the Octane HDRI environment settings.
Our developer is doing his best to support the native nodes since the beginning.

cheers

[frankserin]

Hi there again, sorry for posting so much, but I keep finding more things that I feel aren't working.

I've been spending more time exploring Octane for Solaris, and the more I use it, the more I find features that are missing or don't integrate well with the Solaris workflow.

One example is Copernicus. Houdini's native workflow relies on `op:` paths to reference COP textures directly, but Octane doesn't seem to support them. If `op:` isn't supported, how are we supposed to use Copernicus procedurally inside Octane for Solaris? Is there any workflow I'm missing?

Another limitation I found is the lack of basic HDRI color controls. There doesn't seem to be any way to adjust exposure, saturation, or other color corrections for an HDRI used in an Octane Dome Light.

In Karma, this can be solved using Light Filters, allowing artists to tweak the lighting without modifying the original HDRI. Octane doesn't appear to offer an equivalent solution.

It would be great if Octane could support these native workflows more completely. Right now these feel like unnecessary limitations in day to day production. Thanks!

Hi there,

No worries..
The `op` paths are already supported however, it requires to reload when we make changes.
We are aware of this issue and will get it resolved in future.

We are currently discussing if there is a workaround to support the Light Filters node.

For now, please use the HDRI color controls or use the Octane HDRI environment settings.
Our developer is doing his best to support the native nodes since the beginning.

cheers

Hi there,

Thank you very much for looking into these issues and for taking the time to investigate my reports. I really appreciate how responsive the team has been to my feedback.

I hope the next releases will bring a much more stable and complete Solaris experience, as it's a workflow with a lot of potential. Thanks again for your time, patience, and all the effort you're putting into improving the plugin. It's greatly appreciated.

Cheers!