OctaneRender2023.1.2.0Solaris19.5.805&20.0.590-RC7[Obsolete] Tweet

[BK]

OTOY® is proud to announce the availability of the new DCC plugin OctaneRender 2023.1.2.1 Solaris 19.5.805 - RC7 and Solaris 20.0.590 .

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

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.





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


- Change log since last release[Test]-

• - Merged with latest OctaneRender for Houdini [(2023.1.2.1)]https://render.otoy.com/forum/viewtopic.php?f=102&t=83043

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..

Linux Note
On Linux-only compatibility Houdini 20 build is supported (gcc9.3).
It can only be installed by downloading it from the downloads page since it's not visible in the Launcher:
https://www.sidefx.com/download/daily-b ... ction=true
or direct download link: houdini-20.0.590-linux_x86_64_gcc9.3.tar.gz
We are looking into supporting the gcc11.2 build.

===================================
Studio+ Subscription Downloads
===================================
2023.1.2.1 - Houdini 19.5.805
2023.1.2.1 - Houdini 20.0.590
===================================
macOS build Downloads for ARM64
===================================
2023.1.2.1 - Houdini 19.5.805
2023.1.2.1 - Houdini 20.0.590
===================================
Linux build Download
===================================
2023.1.2.1 - Houdini 19.5.805
2023.1.2.1 - Houdini 20.0.590

===================================
Demo build Download
===================================
2023.1.2.1 - Houdini 19.5.805
2023.1.2.1 - Houdini 19.5.805

2023.1.2.1 - Houdini 20.0.590
2023.1.2.1 - Houdini 20.0.590



Happy GPU Rendering !!



Your team
OTOY

[galleon27]

Using lights mixed with distant light doesn't work.

With distant light

Without distant light

[adrianr]

Hope I'm just missing something obvious, but the visibility parms on the Dome Light don't appear to be doing anything? If I use a Render Geometry settings LOP to disable the Environment in the Light pass mask I also end up loosing contribution from an emissive texture I have in the scene.

Also seems the tool gradient bug of the starting two keys not doing anything has returned.

[BK]

Using lights mixed with distant light doesn't work.

Screenshot 2024-02-16 140640.png

Screenshot 2024-02-16 140616.png

Hi galleon27,

Thank you so much for reporting this issue.
We have created an internal bug ticket for our dev to resolve this asap!

cheers

[BK]

Hope I'm just missing something obvious, but the visibility parms on the Dome Light don't appear to be doing anything? If I use a Render Geometry settings LOP to disable the Environment in the Light pass mask I also end up loosing contribution from an emissive texture I have in the scene.

Also seems the tool gradient bug of the starting two keys not doing anything has returned.

Hi Adrian, thanks for the post.

Do you mean the Camera visibility param?
How about disabling the dome light node? Maybe try using the Octane HDRI from the Environment drop-down.

cheers

[adrianr]

Hope I'm just missing something obvious, but the visibility parms on the Dome Light don't appear to be doing anything? If I use a Render Geometry settings LOP to disable the Environment in the Light pass mask I also end up loosing contribution from an emissive texture I have in the scene.

Also seems the tool gradient bug of the starting two keys not doing anything has returned.

Hi Adrian, thanks for the post.

Do you mean the Camera visibility param?
How about disabling the dome light node? Maybe try using the Octane HDRI from the Environment drop-down.

cheers

Hey BK. I mean all of the visibility parms on the Dome Light (attached). I'm guessing that because it's a light it's getting the Octane tab with all the standard light visibility parms, despite them not actually working with HDRI's? (Could that ever happen? That would be brilliant). I guess there needs to be some parity/consistency between the Dome Light parms and assigning the HDRI on the render settings LOP. It's been really nice to assign HDRIs in a Dome Light again - I think it makes so much more sense than assigning it on the render settings LOP.

The emissive texture dropout issue seemed to be a bug. I rebuilt a fresh scene and didn't see the issue when disabling the Environment light on a Render Geometry Settings LOP. Will chalk that one up to bad luck.

[adrianr]

Auxiliary Noise AOV isn't working, among others. Is this to be expected or is this a bug?

Also is 'Ambient Light' in the Light AOV section supposed to be 'Environment Light' as per a normal Octane Render target? If so, this also doesn't work, and is a pretty reliable way to cause a segmentation fault by switching it off after turning it on. Turning it on seems to override all other lights and only shows the environment light. Tried with both Dome Light and setting the HDRI directly on the Octane render settings.

[BK]

Auxiliary Noise AOV isn't working, among others. Is this to be expected or is this a bug?

Also is 'Ambient Light' in the Light AOV section supposed to be 'Environment Light' as per a normal Octane Render target? If so, this also doesn't work, and is a pretty reliable way to cause a segmentation fault by switching it off after turning it on. Turning it on seems to override all other lights and only shows the environment light. Tried with both Dome Light and setting the HDRI directly on the Octane render settings.

Hi Adrian,

Thank you for the post.

Would you please check if AOV render output seems to work for you?
We will get the viewport render fixed for Noise AOV in the next release.

The Ambient and Environment lights AOVs are organized based on Octane Standalone. We just ran a test using Octane node and they seem to work fine.
Are you using the OctaneAOV>Rendersettings>USDRenderRop? Please PM me a sample file for us to investigate.

We can replicate the light issue and it has been fixed!

cheers

[adrianr]

Hey BK - Having it work in the renderview is what I was asking. Best to be able to see it live for tweaking adaptive sampling. Admittedly I've not rendered any of this to disk yet, so good to know the fix is in for the next release.

The Ambient and Environment lights AOVs are organized based on Octane Standalone. We just ran a test using Octane node and they seem to work fine.
Are you using the OctaneAOV>Rendersettings>USDRenderRop? Please PM me a sample file for us to investigate.

We can replicate the light issue and it has been fixed!

Sorry not sure I follow. Are you saying you did find an issue with Ambient/Environment lights and they have been fixed - Or was the light issue related to my previous post? All I have to do is turn on the 'Ambient light' AOV and the render view will basically make that pass priority, but also the beauty looks the same as the Ambient Light AOV (IE, it turns off all other light sources). Then turning it off the AOV will create a seg fault.

Regarding the naming, when I say 'normal Octane render target' I mean in Houdini. It sounds like that should be changed to Ambient light for consistency with standalone.

Can't send the file I'm working in but if I get a sec I'll try and make a repro.

[adrianr]

Seems that W coordinate isn't working correctly in Solaris. Same geometry rendered in sops/solaris with the same material (bumped up the width to make it obvious). W coord in Solaris seems to be interpolating between the curve cvs and not the length of the prim. Even if you feed it a prim with just 2 end points it still doesn't appear to generate a linear ramp end to end.

Reminder also in case it got lost above that the gradient tool is broken. Starting Black/White keys will not adjust the incoming value. Need to add additional keys for it to work. This bug came up in the regular Houdini Octane plugin but was later fixed.

Edit: I realise this is the release thread and not the bug forum, but sometimes bugs are release specific, so it's easier to call them out here. Let me know if you would rather I just make a thread per issue in the bug forum