OctaneRender™ 2020.2.4

by **mojave** » Thu Jun 10, 2021 8:43 pm

Hi all,

This is a new maintenance release to sort out some problems found in 2020.2.3.

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 does not have Ampere support) and needed to be discontinued on Windows and Linux.

Changes since OctaneRender 2020.2.3:

Bugfixes:

Fixed application crash happening when loading some Alembic files containing an invalid topology.
Fixed application crash when dragging the time slider while using some Alembic files.
Fixed possible application crash during a render initialization.
Fixed render failure when using dirt with infinite plane primitives.
Fixed render failure when using a stereo panoramic camera with a focal depth set to zero with RTX on.
Fixed render issue with microfacet models not calculating reflectance on total internal reflection.
Fixed rendering regression with hair rendering in 2020.2 builds compared to 2020.1.5.
Fixed shadow catcher material not responding to the opacity pin value.
Fixed image texture transform conversions loading very old materials.
Fixed case in which OSL textures would not be compiled upon being created or loaded.
Fixed memory leak when using the baking texture node.
Fixed incorrect texture mapping when the Z component of a UV transform is zero.
Fixed issue causing UV transforms being ignored with plane primitives.
Fixed flickering and brightens with the Hosek-Wilkie daylight model when using small sun sizes.
Fixed possible application crash when using SDF/Vectron shaders which expose multiple materials.
Fixed volume contribution for Cryptomatte passes which were counted twice.
Fixed motion vector pass for triangles with deformation.
Fixed issue with the denoiser causing an output color difference from the original pass.
Fixed color blend and alpha operation combinations using output AOVs.
Fixed differences between composite AOVs and the beauty pass.
Fixed some unnecesary render restarts.
Fixed issue causing ORBX packages to miss some data when being overwritten.
Made renaming from temporary ORBX package file name more robust.
Fixed the AI denoiser and upsampler for macOS.
Fixed upsampling when the alpha channel is enabled.
Fixed performance issue when resizing the LocalDB panel

by **funk** » Fri Jun 11, 2021 6:11 am

Thanks team

by **PolderAnimation** » Fri Jun 11, 2021 9:50 am

Thanks for the release and fixing the focus length issue!

by **glimpse** » Fri Jun 11, 2021 1:23 pm

Thanks for these fixes!

by **Jolbertoquini** » Tue Jun 22, 2021 8:31 am

Hi Guys,

Spend a while can we have Maya plug updated? so we can actually use those fixes, is better that then beta plugs to be honest.

Best,
JO

by **Powel2097** » Wed Jun 23, 2021 2:43 pm

H there,

I was told taht this is a core issue and I should post it here.

In all scenes, when rendering with all GPU´s, I get a flickering in the rendering when motion blur is turned on.

I have 3 x 2080ti and 1x 3080ti in my system.

When rendering the scene with only 2080ti´s there is no flickering.
Same goes when I render with only the one 3080ti.

But when I use them combined, I get this result.
When I switch off motion Blur, and use all cards, the flickering s gone.

When rendering a still frame, I also get two different results, depending on which card I use. See image attached.

I also noticed, that the speed increase isnt as good as it should be when rendering with all cards together.
Octane Benchmark shows the correct points for each card.
When using them seperately, they perform as expected. Only when combining them, the speed gain is much lower than it should be.

All drivers are up to date. I also checked previous octane versions.

I am working on WIN10 Cinema 4D.

Attaches you will find the rendered clip to show the flickering.
In this scene you see the flickering on the pot on the left side. It is getting brighter and darker. Same on the white area on the packaging on the side.

Here is the wetransfer link to the ORBX file:
https://we.tl/t-M0Cr2AwED2

Best regards
Powel

by **Powel2097** » Wed Jun 23, 2021 5:41 pm

I´ve forgot to attach the difference in rendering with the two cars seperately.

by **mojave** » Thu Jun 24, 2021 4:19 am

Powel2097 wrote:I´ve forgot to attach the difference in rendering with the two cars seperately.

Are you able to reproduce this issue also with the ORBX you shared with us? I have just tested it on a few different cards using various settings using Octane 2020.2.4 but cannot see anything like what you are showing either using the beauty or denoised passes. Assuming you are using all local GPUs too (i.e. not using network rendering), is that correct?

by **Powel2097** » Thu Jun 24, 2021 9:42 am

Somehow I cant reproduce it in a new scene.
And yes, all local GPU´s.

by **mojave** » Thu Jun 24, 2021 8:52 pm

Powel2097 wrote:Somehow I cant reproduce it in a new scene.
And yes, all local GPU´s.

Thank you. We will take another look and hopefully can reproduce it here. If you are able to see this again, all details you can share about your setup will be very useful.

OctaneRender™ 2020.2.4

Tweet

OctaneRender™ 2020.2.4

Re: OctaneRender™ 2020.2.4 [current 2020.2]

Re: OctaneRender™ 2020.2.4 [current 2020.2]

Re: OctaneRender™ 2020.2.4 [current 2020.2]

Re: OctaneRender™ 2020.2.4 [current 2020.2]

Re: OctaneRender™ 2020.2.4 [current 2020.2]

Re: OctaneRender™ 2020.2.4 [current 2020.2]

Re: OctaneRender™ 2020.2.4 [current 2020.2]

Re: OctaneRender™ 2020.2.4 [current 2020.2]

Re: OctaneRender™ 2020.2.4 [current 2020.2]

Who is online