OctaneRender 2023.1.3.2|OctaneSolaris - RC13[OBSOLETE]

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

OTOY® is proud to announce the availability of the new DCC plugin OctaneRender 2023.1.3.2|OctaneSolaris - RC13.

The world's fastest unbiased GPU rendering engine on CUDA and Metal now integrates completely with Houdini 19.5, Houdini 20.0 &Houdini 20.5 Solaris.
OctaneSolaris builds supported by this release: 19.5.805, 20.0.724, 20.0.751, 20.5.278.

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

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


- Change log since last release
  • - Included **MakePackage_Solaris.bat** for automatic Package installer.
  • - Fixed a crash when rebuilding the instance colors.
  • - Fixed instance colors when multiple meshes are instanced together.
  • - Updated the lights and their UI to fix the directional and toon lights.
  • - Added the Force up vector vertical option for Thin lens and Universal cameras.
  • - Fixed instances in Houdini 20.5.x due to changes in Hydra.
  • - Unreferenced meshes, particles and volumes now have their nodes cleared so they are not left stranded in the Octane node tree.


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-
- Deep AOV is yet to support!

Important: if using macOS, we strongly recommend that you update to version 14..

Linux Note
On Linux only default Houdini builds are supported.
This means that for Houdini 20.0 and 20.5, gcc11.2 builds are supported, and for Houdini 19.5, gcc9.3 build is supported



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

OctaneSolaris [Windows]

OctaneSolaris [macOS]

OctaneSolaris [Linux]


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

OctaneSolaris [Windows]
OctaneSolaris [Linux]



Happy GPU Rendering !!



Your team
OTOY
Kind Regards

bk3d
EyasArraf
Licensed Customer
Posts: 37
Joined: Fri Sep 13, 2019 8:57 pm

Thanks for the update.
Can you add for the next release an option - to choose a solid color for the "Camera Environment" instead of only choosing a file? Like the case under the "HDRI Environment" tab.
User avatar
akvahouse
Licensed Customer
Posts: 30
Joined: Wed Apr 02, 2014 5:29 pm
Location: Ukraine, Kyiv
Contact:

Good day, tell me please, what could be the reason for such an error?
Attachments
Error_octane.jpg
Win 11 x64 | Amd threadripper 1950x | 128gb | Rtx 3090ti
BK
OctaneRender Team
Posts: 1436
Joined: Mon Oct 31, 2016 7:54 pm

EyasArraf wrote:Thanks for the update.
Can you add for the next release an option - to choose a solid color for the "Camera Environment" instead of only choosing a file? Like the case under the "HDRI Environment" tab.

Hi EyasArraf,

Thank you for this idea.
We have created a feature request ticket on our system.

cheers
Kind Regards

bk3d
BK
OctaneRender Team
Posts: 1436
Joined: Mon Oct 31, 2016 7:54 pm

akvahouse wrote:Good day, tell me please, what could be the reason for such an error?
Hi akvahouse,

Thank you for the post.

Would you please let us know the Houdini version and OctaneSolaris version?
Does Houdini work when OctaneSolaris is disabled?

Could you please send a ticket via our support [email protected]?

cheers
Kind Regards

bk3d
madssigurd
Licensed Customer
Posts: 7
Joined: Sun Oct 24, 2021 4:59 pm

I still get crashes the instant i try to render, on the last update the same happened and i was told it was because of the newest nvidia driver, is this still the case? If so i thought that would be pretty high priority for a fix? But cheers on the pretty timely updates lately guys, doing good work!
User avatar
akvahouse
Licensed Customer
Posts: 30
Joined: Wed Apr 02, 2014 5:29 pm
Location: Ukraine, Kyiv
Contact:

BK wrote:
akvahouse wrote:Good day, tell me please, what could be the reason for such an error?
Hi akvahouse,

Thank you for the post.

Would you please let us know the Houdini version and OctaneSolaris version?
Does Houdini work when OctaneSolaris is disabled?

Could you please send a ticket via our support [email protected]?

cheers
Houdini 20.5.278, Octane 2023.1.3.2|OctaneSolaris - RC13
Houdini works well only before I start using octane, and when I switch to solaris and choose Octane for viewport rendering it crashes. But the strange thing is that octane works in a normal context without any problems
Win 11 x64 | Amd threadripper 1950x | 128gb | Rtx 3090ti
adrianr
Licensed Customer
Posts: 50
Joined: Sat Jan 25, 2020 3:31 pm

Can someone please sanity check for me that the Override output image parameter on the USD Render LOP is working? I'm just getting a black EXR (Looks suspiciously similar in size to whatever file is now output from that new path on the AOV tab?). I can only get an actual rendered image from the path set on the Octane node.

Sorta took for granted that this worked in the prior versions where the USD Render LOP was embedded in the Octane LOP but since they've been split apart I can't fire off renders with Prism anymore, which needs the ability to set an output path override on the USD Render LOP. In previous builds it seems internally this was set to 'md', which is now even more confusing how it worked before at all, but doubly so now that it doesn't.

Also haven't been able to export an animated ORBX with this new workflow, so any pointers there would be appreciated.
User avatar
akvahouse
Licensed Customer
Posts: 30
Joined: Wed Apr 02, 2014 5:29 pm
Location: Ukraine, Kyiv
Contact:

Deapth of field doesn`t work in this build?
Attachments
Screenshot_5.png
Win 11 x64 | Amd threadripper 1950x | 128gb | Rtx 3090ti
BK
OctaneRender Team
Posts: 1436
Joined: Mon Oct 31, 2016 7:54 pm

adrianr wrote:Can someone please sanity check for me that the Override output image parameter on the USD Render LOP is working? I'm just getting a black EXR (Looks suspiciously similar in size to whatever file is now output from that new path on the AOV tab?). I can only get an actual rendered image from the path set on the Octane node.

Sorta took for granted that this worked in the prior versions where the USD Render LOP was embedded in the Octane LOP but since they've been split apart I can't fire off renders with Prism anymore, which needs the ability to set an output path override on the USD Render LOP. In previous builds it seems internally this was set to 'md', which is now even more confusing how it worked before at all, but doubly so now that it doesn't.

Also haven't been able to export an animated ORBX with this new workflow, so any pointers there would be appreciated.
Hi Adrian,

We can confirm the Override output image was broken.. We have fixed the issue.
Will get a build out asap..

Cheers
Kind Regards

bk3d
Post Reply

Return to “Releases”