OctaneRender 2022.1.1.1Solaris 19.5.640 RC1-[OBSOLETE] Tweet

[BK]

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

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.1 and the Render Node app, please check out the 2022.1.1 release post


- Change log since last release[Test]-

• - Integrated with the latest OctaneRender for Houdini production build 2022.1.1.1
• - Fixed VDB rendering as SDF

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!


Important: if using macOS, we strongly recommend that you update to version 13.3. Prior to 13.3, there is an OS-related issue that causes a render failure consistently if you render for long periods of time.

===================================
Studio+ Subscription Downloads
===================================
2022.1.1.1 - Houdini 19.5.640

===================================
macOS build Downloads for ARM64
===================================
2022.1.1.1 - Houdini 19.5.640

===================================
Demo build Download
===================================
2022.1.1.1 - Houdini 19.5.640



Happy GPU Rendering !!



Your team
OTOY

[snakeboxmedia]

How do you load the point colors in a shader/texture in LOPs when loading instances in "point instance" mode?

if I sopimport my copy to points instances and apply a standard octane material with no other inputs, it will auto read the point colors, but if I want to mix that with a texture I'm out of luck.
The instance color node + the stupid annoying file on disk we still have to load... why is this? why can't we just get attribute support like every other engine?... doesn't work in LOPs, it works in SOPs but in lops point colors are called displayColor and not Cd, so im guessing that node converts Cd and then can't find the attribute in LOPs?

[BK]

How do you load the point colors in a shader/texture in LOPs when loading instances in "point instance" mode?

if I sopimport my copy to points instances and apply a standard octane material with no other inputs, it will auto read the point colors, but if I want to mix that with a texture I'm out of luck.
The instance color node + the stupid annoying file on disk we still have to load... why is this? why can't we just get attribute support like every other engine?... doesn't work in LOPs, it works in SOPs but in lops point colors are called displayColor and not Cd, so im guessing that node converts Cd and then can't find the attribute in LOPs?

Hi Snakeboxmedia,

Thanks for the post.

The texture instance color node is just a workaround to load the attributes from the native SOP workflow. Did you try renaming the Octane texture Instance color node as **displayColor**?
We already have plans to implement this feature from the engine side.
Would you please share the scene if it still does not work?

cheers