OctaneRender™ 2020.2.3

Fri Apr 09, 2021 7:36 am

Hi all,

This is a quick bugfix release 2020.2.3 to sort out some easy to fix but annoying problems found in 2020.2.2. Apologies for the hassle of having to update again.

You can find an overview of the changes between 2020.1.5 and 2020.2 in the release notes of 2020.2.

Make sure to use a NVIDIA Studio driver with version at least 456.38 on Windows or 455.23 on Linux to use this version. No driver updates are required for macOS 10.13 (CUDA).

This version supports the NVIDIA Ampere architecture (compute model 8.x) on Windows and Linux. As a consequence, Kepler GPUs with a compute model lower than 3.5 are only supported on macOS (which doesn't have Ampere support) and needed to be discontinued on Windows and Linux.

Changes since OctaneRender 2020.2.2:

Bugfixes:

Fixed missing render update if a toon ramp is modified.
Fixed superfluous geometry updates when an input of a volume node got changed.
Fixed specular transmission "leaking" into the indirect reflection render pass.
Fixed crash when you authenticate more than once in a session.
Standalone: Fixed crash when rendering a geometric primitive that just had at least one of its inputs collapsed into its pin.

Mon Apr 12, 2021 6:03 am

Thanks team. We appreciate the quick fixes

Fri Apr 16, 2021 11:50 am

Somehow the "OctaneRender Enterprise 2020.2.3 Standalone for Windows (installer)" does not seem to be working on Windows 10. The EXE does not seem to be doing anything. Any ideas?

Fri Apr 16, 2021 9:38 pm

Please take a look
viewtopic.php?f=30&t=77459

Sat Apr 17, 2021 11:32 am

aoktar wrote:Please take a look
viewtopic.php?f=30&t=77459

I suppose you were not referring to my question or maybe the link was wrong? As the link covers the topic "Triplanar mapped bump problem - gamma issue?"

Sun Apr 18, 2021 8:27 am

we need cinema 4d S24 of octane

Sun Apr 18, 2021 11:20 am

shenl9024 wrote:we need cinema 4d S24 of octane

viewtopic.php?f=85&t=77426

Wed Apr 21, 2021 12:46 pm

BUG: Regression in transform node breaks projections

There seems to be a regression caused by transform nodes that breaks projections.

The attached orbx renders fine in 2020.1.5, but breaks in 2020.2.3

1. Load the attached orbx in 2020.2 and select the rendertarget to start rendering. Notice the sphere has no texture in 2020.2.3!
2. Select the "test" nodegraph > rgb image
3. Change the UV transform > scale Z to 1 instead of 0. It now renders like 2020.1.5

oct_2020_2_uv_transform_bug.png

Thu Apr 22, 2021 8:06 am

Is that a real issue?
The default values for Scale, for all Transform nodes, is 1. In this specific case a 2D Trasnform node should be used, which only offers X and Y transform options.

Thu Apr 22, 2021 8:34 am

Lino unfortunately this node graph is generated automatically by the modo plugin when converting modo's own projections. The user has no control over it.

It works in all previous Octane versions though, so I don't see a good reason for breaking it.

Users with existing ORBX exports would need to manually edit every transform node that has this issue.