OctaneRender 2022.1.0.6 Solaris 19.5.493 - 022423[OBSOLETE] Tweet

[BK]

OTOY® is proud to announce the availability of the new DCC plugin OctaneRender for Solaris V2022.1 - for Houdini 19.5.493.

The world's fastest unbiased GPU rendering engine on CUDA and Metal now integrates completely with Houdini 19.5 Solaris.

What is OctaneRender for Solaris?
The OctaneRender for Solari's 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.





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,
        },
            //location to your octane folder (example below)
            "OCTVERSION": "PATH\TO\OCTANESOLARIS\Win64FOLDER",
        },       
     
        {
            "HOUDINI_PATH" :
            {
                "value": "$OCTVERSION",
            },

            "PATH" :
            {
                "value": "$OCTVERSION/bin",
            },
            "PXR_PLUGINPATH_NAME" :
            {
                //if you have the solaris version installed
                "value": "$PATH\TO\OCTANESOLARIS\dso\usd_plugins",
            },
        }
    ]
}

- Then Save as OctaneSolaris.json
- Please make sure to disable the .env paths

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


- Change log since last release[Test]-

• - Fixed mesh update optimizations
• - Fixed multiple environment maps (dome lights) that caused them to reload on every update

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

-Known Issues-
- Solaris rendering extra beauty AOV with Octane node and currently investigating
- Light Linker is yet to be supported as we are investigating if we could assign the Octane light IDs internally.
However, the usual Octane light linking works as expected.
- Deep AOV is yet to support!


===================================
Studio+ Subscription Downloads
===================================
2022.1.0.6 - Houdini 19.5.493

===================================
macOS build Downloads for ARM64
===================================
2022.1.0.6 - Houdini 19.5.493

===================================
macOS build Download
===================================
2022.1.0.6 - Houdini 19.5.493




Happy GPU Rendering !!



Your team
OTOY

[tripledistilled]

Cheers for this. Is it also possible to get a build for 19.5.534 (the first stable release of Houdini for Apple Silicon)?

I'm having an issue with Octane's Solaris /Render/RenderSettings node changes not being picked on an M1 Mac. It works great on the PC version, so I'm guessing that running .493 on .534 is causing the issue.

[snakeboxmedia]

Yes, where is the build for the latest production build??

[statostado]

Hello, I'm trying to install the Solaris Version but I'm getting this error when switchting to Octane in the vewport...
Unable to create Usd Render Plugin: HdOctaneRendererPlugin
HdOctaneRendererPlugin not supported - removing from renderer list
The standard version works fine, but no the Solaris. IT seams to lead, but it automatically desapears when I switch to Octane.

[Terryvfx]

Thank you for the update! I Hope we can have a new version soon supporting the latest production release.

[HandcraftedMedia]

This seems to be a special case but I am getting this error:

Code: Select all

...
Octane Error: Invalid mesh: float2 index out of range (172/0 at offset 0)
Octane Error: Invalid mesh: float2 index out of range (128/0 at offset 0)
Octane Error: Invalid mesh: float2 index out of range (0/0 at offset 0)
Octane Error: Invalid mesh: float2 index out of range (0/0 at offset 0)
Octane Error: Invalid mesh: float2 index out of range (0/0 at offset 0)
...

Now removing some of the attributes or not loading them in fixes it, but since I didn't encounter this issue on earlier versions, I assume it's a bug.

File attatched.

[HandcraftedMedia]

Material assignment on packed primitives is messed up in this version.
If you apply a material to a packed primitive that is imported as "native instance" or "create point instancer" it assigns the material and rounded edges even work but all the other material parameters are ignored. Only if you import as "Create Xforms" (which basically disabled instancing) the material assignment works correctly. When testing with Karma this works fine, so it's definitely just an octane error. This also was not an error previously.

Example file attached.

[HandcraftedMedia]

When rendering with packed primitive set to "Create Xforms" some of the elements pop in and out of place. If you set it to "Create Point Instancer" that doesn't happen, but also the materials don't work.
Example attached (needs Mops to be installed).

[HandcraftedMedia]

Went back and checked and none of these issues exist for 19.5.403 combined with the 19.5.435 octane build.

[HandcraftedMedia]

Also tested it with 19.5.493 with the 19.5.435 octane build and also none of those issues show up.

The only thing that's buggy with the houdini builds after 19.5.403 (that's for the .435 octane build and the new one too) is that this window stays open after completion/gets stuck on the last element, vs before it would close and you could see the renders in the render scheduler window. Not a massive problem, but a little bit of an inconvenience, as you can't see your render times and it locks up the houdini window.

Screenshot_47.png (32.19 KiB) Viewed 1366 times