OctaneRender™ 2020.1.2 [superseded by 2020.1.3]

Thu Jun 11, 2020 9:02 am

Dear all,

We are happy to share a new release of Octane.

Octane 2020.1.2 is a maintenance update and the latest version recommended for production use.

Make sure to use a NVIDIA Studio driver with version at least 435.80 for Windows or 435.12 for Linux to enable support for RTX hardware acceleration. There are no OSX drivers that currently support RTX.

OctaneRender 2020.1.3 has superseded this build.

Should you find any issues with this release please report using this thread so we can make sure we provide you with the best feedback.

Changes since OctaneRender 2020.1.1:

Bugfixes:

Fixed CUDA error happening after switching from a universal camera node to any other camera types.

Thu Jun 11, 2020 2:53 pm

Sorry for the beginner question but I couldn't find an answer by googling: If I only use the C4D plugin do these standalone releases effect me? Should I just wait until the plugin is updated? I installed standalone & the plugin at the same time because it seemed to be a good idea, but do I need to do that?

Otherwise I appreciate the bug squashing! Coming from Redshift I love to see stability improvements

Thank you

Thu Jun 11, 2020 3:45 pm

You need the standalone and the plugin to use octane in any app.
A plugin version works with a specific standalone. It could work in some case but it's not recommended.
So, check for the last released plugin and use the recommanded standalone (check changelog).
Usually, few days after a stable standalone release, new plugins are released.

Thu Jun 11, 2020 7:34 pm

james_conkle wrote:Sorry for the beginner question but I couldn't find an answer by googling: If I only use the C4D plugin do these standalone releases effect me? Should I just wait until the plugin is updated? I installed standalone & the plugin at the same time because it seemed to be a good idea, but do I need to do that?

Otherwise I appreciate the bug squashing! Coming from Redshift I love to see stability improvements Thank you

Standalone and Octane plugins work independently from each other so you do not need to have standalone installed on your machine for plugins to work.

Just take into account you do need to match the version of your plugin to a given slave version.

Having said that, as a plugin user standalone allows workflows that might be interesting such as testing your ORBX exported from any plugin before uploading them to ORCor using them in RNDR.

Thu Jun 11, 2020 10:25 pm

Oups sorry...was thinking C4d was working the same way houdini plugin does. My bad.

Beppe OctaneRender™ Italia Blue Sky · Fri Jun 12, 2020 6:26 am

As Arturo said, Standalone is not necessary, with any plugin, but I always suggest to install it and keep it updated.

Over than checking your scene for ORC or RNDR, other advantages are that Standalone installer changes some Windows registry that maybe plugin does not change (c4doctane does not), and if you keep it updated, you can save and edit .orbx objects with one click from plugin, to be reused as xref/proxy like objects, importing them back into plugin.
Standalone is also useful for managing the LocalDB, or if you are close to finish system RAM, you can export to Standalone, close the host app to save some RAM, and finish to render in Standalone.

The confusion probably comes from the fact that Standalone license is always necessary to be able to run the plugin, since Standalone and plugin licenses are always working together for the activation.

ciao Beppe

Fri Jun 12, 2020 7:37 am

I couldnt get this build running on my machine either.

I even went so far as to install a new copy of windows 10 on a separate SSD. I have posted screenshots and details to mojave in PM.

On a fresh install, 2020.1.2 crashes on launch (before any splash screen). I also tried installing newer nvidia drivers, but nothing changed.

2020.1.0 runs fine on the same fresh install.

After a google search, I found some info related to the event log errors, showing people having issues running AVX instructions on a CPU that doesnt support AVX. I have an old CPU that doesnt support it.

Fri Jun 12, 2020 3:26 pm

If i connect a mix material with displacement to a base layered material, the dispacement disappear!

Fri Jun 12, 2020 3:36 pm

funk wrote:I couldnt get this build running on my machine either.

I even went so far as to install a new copy of windows 10 on a separate SSD. I have posted screenshots and details to mojave in PM.

On a fresh install, 2020.1.2 crashes on launch (before any splash screen). I also tried installing newer nvidia drivers, but nothing changed.

2020.1.0 runs fine on the same fresh install.

After a google search, I found some info related to the event log errors, showing people having issues running AVX instructions on a CPU that doesnt support AVX. I have an old CPU that doesnt support it.

probably you may try turn off window 10's antivirus when installing...

Fri Jun 12, 2020 5:21 pm

I am having 2020.1.2 crash on open on my 2010 mac pro (tower) running OSX High Sierra and the latest (not new) nVidia drivers that work on this machine (web driver -387.10.10.10.40.130... CUDA driver 418.163)
Is this the first version that simply will not work with my older setup?