OctaneRender for HoudiniSolaris 2025.3.0.0

Sub forum for plugin releases
Post Reply
BK
OctaneRender Team
Posts: 1471
Joined: Mon Oct 31, 2016 7:54 pm

OTOY® is proud to announce the availability of the new DCC plugin OctaneRender for HoudiniSolaris 2025.3.0.0 release.

The world's fastest unbiased GPU rendering engine on CUDA and Metal now integrates completely with Houdini 20.0, Houdini 20.5 & Houdini 21.0 Solaris.
OctaneSolaris builds supported by this release: 20.0.896, 20.5.613, 20.5.654, 20.5.684, 21.0.440.

What is OctaneRender for Solaris?
The OctaneRender for Solaris plugin is based on Pixar’s USD (Universal Scene Description) and Pixar’s Hydra API to empower artist workflows across look development, scene layout, lighting, and final rendering.

Image

Image

Pixar's USD pipeline
https://renderman.pixar.com/stories/pixars-usd-pipeline


-Installation steps-

Insert the OctaneRender® plugin folder path to the houdini.env file. Houdini®creates this file after launching it for the first time.
On Linux and macOS® systems, append a single line to enable OctaneRender®:

HOUDINI_PATH = "/path/to/octane;&"

On Windows® systems, you need to set the PATH to point to the plugin bin folder as well:

PATH = "C:/path/to/octane/bin;$PATH"


Setting this environment variable outputs any error related to loading the OctaneRender® plugin on the command line for diagnosing installation problems:
HOUDINI_DSO_ERROR = 2

-Houdnin Packages/json installation steps-

- Please create a folder inside Documents\houdini19.5 and name it as Packages
- Open notepad or any text editor and use these lines

Code: Select all

{
    "enable": true,
    "env": [
        {
            "OCTANE_AUTOSPAREPARAMS": {
                "value": 1
            }
        },
        {
            "OCTVERSION": "PATH_TO_OCTANE_SOLARIS_Win64 FOLDER"
        },
        {
            "HOUDINI_PATH": {
                "value": "$OCTVERSION"
            },
            "PATH": {
                "value": "$OCTVERSION\\bin"
            },
            "PXR_PLUGINPATH_NAME": {
                "value": "$OCTVERSION\\dso\\usd_plugins"
            }
        }
    ]
}
- Then Save as OctaneSolaris.json
- Please make sure to disable the .env paths

- Please run **createPackageFileForOctane.bat** for automatic Package installer for Windows OS.

New features
To learn more about the new features and improvements of OctaneRender 2025.3.0 and the Render Node app, please check out the 2025.3.0 release post


Change log since last release
  • -Unified with OctaneRender 2025.3.0 for Houdini production (2025.3.0.0)
  • -Implemented exporting all cameras for Orbx export
  • -Added Denoised Albedo, denoised normal, camera mask, and alpha
  • -Fixed postFX media AOV


Note: Click the link below to refer to the Important SOP to USD attribute conversion
https://www.sidefx.com/docs/houdini18.5/solaris/sop_import.html


Important notes:

[*] The minimum NVIDIA driver version required has been raised to R528 (R572 for GeForce RTX50 Series).
[*] The GPU version of Open Image Denoise is supported on Volta and Ada GPUs currently. The CPU version is used on devices with other models, and on macOS..
[*] The minimum version of macOS required is 14.5.[/b]

Linux Note
On Linux only default Houdini builds are supported.
This means that for Houdini 20.0, 20.5 and 21.0 gcc11.2 builds are supported.

Note: Please do not use Houdini 21.0.440 build for production yet. We are releasing it as an experimental and to collect bug reports.


=================================
Subscription Studio+ Downloads
=================================

OctaneSolaris [macOS](Link)

OctaneSolaris [Linux](Link)

OctaneSolaris [Windows](Link)


=================================
OctaneSolaris for Houdini 21.0
=================================

OctaneSolaris [macOS](Link)

OctaneSolaris [Linux](Link)

OctaneSolaris [Windows](Link)


=================================
Demo Downloads
=================================

OctaneSolaris [Windows](Link)

OctaneSolaris [Linux](Link)




Happy GPU Rendering !!




Your team
OTOY
Kind Regards

bk3d
adrianr
Licensed Customer
Posts: 56
Joined: Sat Jan 25, 2020 3:31 pm

Can I please sanity check something with the default behaviour now in H21 with Octane 2025.

When you add an Octane node it will now automatically add a USD Render LOP to the chain, but if you hit render to disk it won't actually make a file on disk? It will also create a Husk process that won't close, presumably because it thinks it hasn't finished rendering anything?
Windows 11 | 14900k | 2 x 4090 | 96gb DDR5.
BK
OctaneRender Team
Posts: 1471
Joined: Mon Oct 31, 2016 7:54 pm

adrianr wrote: Fri Oct 03, 2025 3:11 pm Can I please sanity check something with the default behaviour now in H21 with Octane 2025.

When you add an Octane node it will now automatically add a USD Render LOP to the chain, but if you hit render to disk it won't actually make a file on disk? It will also create a Husk process that won't close, presumably because it thinks it hasn't finished rendering anything?
Hi Adrian,

Thank you for the feedback.
The H21 is now using Hydra 2, causing instability. We are already working on fixing issues.
Btw, would you please share your scene or DM me if it has confidential?

cheers
Kind Regards

bk3d
adrianr
Licensed Customer
Posts: 56
Joined: Sat Jan 25, 2020 3:31 pm

Hey BK - Indeed I think that might have just been a bug. On a fresh scene it will produce an image now with the default Octane_raster to the path set on the Output tab. It seems that we can now get viewport AOVs with regular raster (was that the original limitation/reason? I can't quite remember :D ), and we still need that in order to use the override output path on the USD Render lop. Is there any reason for Octane_raster still existing? If you disable the checkbox it will output an EXR to the path on the AOV tab, so could we not just do away with this altogether and have one file path and one product type?

Separate bug - displacement breaks motion blur, at least with RBD procedurals. I think this has been a long standing bug as I'm still mostly working in Octane 2024 which also doesn't work. I'm submitting a repro scene to support.
Windows 11 | 14900k | 2 x 4090 | 96gb DDR5.
User avatar
galleon27
Licensed Customer
Posts: 299
Joined: Wed Jul 15, 2015 11:55 am
Location: Serbia
Contact:

Getting this bug when rendering leaves from megascans. I've attached a sample file. It should show the bug when you render. To fix it, go to /obj context > leaves_import and enable attribute delete.

Octane Error: Trying to set array in attribute of wrong type
Octane Error: Trying to set array in attribute of wrong type
Octane Error: Trying to set array in attribute of wrong type
Octane Error: Trying to set array in attribute of wrong type
Octane Error: Trying to set array in attribute of wrong type
Octane Error: Trying to set array in attribute of wrong type
Octane Error: Trying to set array in attribute of wrong type
Octane Error: Trying to set array in attribute of wrong type
Octane Error: Trying to set array in attribute of wrong type
Octane Error: invalid mesh: float1 index out of range (23/0 at offset 0)
Octane Error: invalid mesh: float1 index out of range (44/0 at offset 0)
Octane Error: invalid mesh: float1 index out of range (25/0 at offset 0)


Another bug thats related to the material:

Unsupported Octane node pin: typeName:A_FILENAME value type: AT_STRING
Unsupported Octane node pin: typeName:A_FILENAME value type: AT_STRING
Unsupported Octane node pin: typeName:octane_plugin_version value type: AT_STRING
Attachments
texturebug.zip
(11.97 MiB) Downloaded 8 times
Win 10 64bit // GTX 4090 + GTX 3090 // 5900x // 64GB // SideFX Houdini // C4D
Post Reply

Return to “Releases”