OctaneRender 2022.1.1.0 Solaris 19.5.569 RC1-[OBSOLETE]

[peteg]

Cryptomattes aren't written out when using "Override Output Image" in the USD Render ROP (Other passes seem to work correctly, might need to test more to make sure I'm not missing something)

Cryptomattes work correctly when using the Octane > Output > Output Picture option in Render Settings

hi Peter, thanks for reporting this.

It seems the cryptomatte AOVs are created on the Octane side, however, all the AOVs are flattened with USD Render ROP.

Is it okay to use Octane's Output while we investigate the "Override output image"?

cheers

Thanks BK, Octane Output makes it easy enough to work around for now, so no problem there.

Is this the same reason cryptomattes display all black in the Solaris "Render Outputs" view mode?

[BK]

Hi,
When I try to render out animations from Solaris, it doesn't render. Render Current frame works fine - opens Mplay and renders. The Render sequence fro Octane LOP does nothing, and if I connect a USD render LOP it saves empty frames. May be I am doing something wrong?

Another question, do you plan to release a Linux version?

Hi Vurt,

Thanks for the post.
We are unable to replicate the issue. Have you tried the Render Specific Frame range?
Is it possible to send your scene for us to investigate if it still does not work?

cheers

[peteg]

Running into some color space issues -
No combination of ACEScg settings in "Intermedia Oct Color Space" and "Color Space" in the Render Settings gives an output that matches what's in the Solaris viewport when imported into a compositing program without additional steps(color profile converter after extracting the exr pass in After Effects, for example) that aren't required when using the main Houdini plugin or Karma. None of these settings seem to have any effect on the Solaris view either (Same with the Camera Imager OCIO options).

Settings that work as expected in the main Houdini plugin -
"Automatic Intermediate Color Space"
Color Space - "ACEScg (EXR Only) or (OCIO - ACEScg)
Imager - ACES(ocioDisplayName) > sRGB(ocioViewName)

[vurt]

Hi,
When I try to render out animations from Solaris, it doesn't render. Render Current frame works fine - opens Mplay and renders. The Render sequence fro Octane LOP does nothing, and if I connect a USD render LOP it saves empty frames. May be I am doing something wrong?

Another question, do you plan to release a Linux version?

Hi Vurt,

Thanks for the post.
We are unable to replicate the issue. Have you tried the Render Specific Frame range?
Is it possible to send your scene for us to investigate if it still does not work?

cheers

Hi, here is the simplified file
https://www.dropbox.com/sh/9rk74m33zjgh ... iyRQa?dl=0

thank you

[peteg]

The Material Node and Object Node Cryptomattes change each frame within the same render. Material Node Name works correctly.

Is there a way to set the Object Node Name? This seems to add everything into a single matte.

[peteg]

ObjectID AOV changes each frame within the same render when objects are animated.

[BK]

Hi,
When I try to render out animations from Solaris, it doesn't render. Render Current frame works fine - opens Mplay and renders. The Render sequence fro Octane LOP does nothing, and if I connect a USD render LOP it saves empty frames. May be I am doing something wrong?

Another question, do you plan to release a Linux version?

Hi Vurt,

Thanks for the post.
We are unable to replicate the issue. Have you tried the Render Specific Frame range?
Is it possible to send your scene for us to investigate if it still does not work?

cheers

Hi, here is the simplified file
https://www.dropbox.com/sh/9rk74m33zjgh ... iyRQa?dl=0

thank you

Hi Vurt,

Thank you for the sample file.
It looks like the AOV Settings are unchecked in the Octane node.
Once we enable it, the scene rendered fine.

Are you rendering via the Octane or the usdrender ROP?
Please try from Octane node!


cheers

[BK]

ObjectID AOV changes each frame within the same render when objects are animated.

Hi Peter,
sorry for the late response.
Is the rendering done with *Render All Frames With a Single Process* option enabled?

Would you please share a sample file for us to investigate?


cheers

[ChrisDWW]

Hi there, I'm having some trouble getting this working on my system.

Info:
Houdini FX 19.5.569 (Py3.7)
Windows 10

It's the first time I've tried getting the Solaris version of Octane working, so it's possible I'm doing something wrong here. I've set up my houdini.env and the packages JSON files as per the instructions in the post.

I've enabled HOUDINI_PACKAGE_VERBOSE in the env file to see if something isn't coming into Houdini correctly. (see attached image for package log)

Once Houdini is loaded up, the regular (non-Solaris) functionality of Octane seems to work fine, without error.

but when I switch into the Solaris workspace and added an Octane node and try to render it just comes up with the following error:

[10:52:40] Can't find Hydra plugin 'HdOctaneRendererPlugin'. Choose one of:
[10:52:40] - GL (HdStormRendererPlugin)
[10:52:40] - Houdini GL (HD_HoudiniRendererPlugin)
[10:52:40] - Karma (BRAY_HdKarma)
[10:52:40] - Octane (HdOctaneRendererPlugin)
[10:52:40] Unable to load render plugin: HdOctaneRendererPlugin

error_message.png (11.02 KiB) Viewed 2027 times

When switching to Octane in the Solaris viewport it does nothing, and afterwards the Octane option just disappears from the list.

Perhaps I'm missing something glaringly obvious here..? Any help would be very greatly appreciated. Thanks!!

Chris

[BK]

Hi there, I'm having some trouble getting this working on my system.

Info:
Houdini FX 19.5.569 (Py3.7)
Windows 10

It's the first time I've tried getting the Solaris version of Octane working, so it's possible I'm doing something wrong here. I've set up my houdini.env and the packages JSON files as per the instructions in the post.

houdini_env_file.png

packages_json.png

I've enabled HOUDINI_PACKAGE_VERBOSE in the env file to see if something isn't coming into Houdini correctly. (see attached image for package log)

package_log.png

Once Houdini is loaded up, the regular (non-Solaris) functionality of Octane seems to work fine, without error.

ui.png

but when I switch into the Solaris workspace and added an Octane node and try to render it just comes up with the following error:

[10:52:40] Can't find Hydra plugin 'HdOctaneRendererPlugin'. Choose one of:
[10:52:40] - GL (HdStormRendererPlugin)
[10:52:40] - Houdini GL (HD_HoudiniRendererPlugin)
[10:52:40] - Karma (BRAY_HdKarma)
[10:52:40] - Octane (HdOctaneRendererPlugin)
[10:52:40] Unable to load render plugin: HdOctaneRendererPlugin

error_message.png

When switching to Octane in the Solaris viewport it does nothing, and afterwards the Octane option just disappears from the list.

Perhaps I'm missing something glaringly obvious here..? Any help would be very greatly appreciated. Thanks!!

Chris

Hey Chris,

Thanks so much for the great post. It helps a lot.
OctaneSolaris require the Python 3.9 version of Houdini.

Would you please try installing SideFX Houdini built with py3.9 and let us know if it still crashes?
Please also disable the plugin loading via the .env since you have assigned the paths with .json.

cheers