OctaneRender™ 2020.1.5 [current 2020.1] Tweet

[mojave]

Dear all,

We are happy to share a new release of Octane.

Octane 2020.1.5 is our latest maintenance update and the version currently recommended for production use.

This version introduces support for the new Ampere family of NVidia GPUS for Windows and Linux, including the already existing A100 and all new hardware to come in the next few months. We maintain support for all previously supported hardware on all platforms.

Make sure to use a NVIDIA Studio driver with version at least 451 on Windows or 450 on Linux to use this version. No driver updates are required for macOS.

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.4:


Bugfixes:

• Fixed increased memory usage after loading multiple projects.
• Fixed artifacts produced by stacking multiple GGX lobes together with low roughness
• Fixed bug causing dirt to not to be evaluated when used with medium nodes.
• Fixed issue with random walk SSS causing invalid pin access errors.
• Fixed crash with some Octane module node graphs.
• Fixed issue causing the furnace test to fail when layer opacity was less than one.
• Fixed composite material not updating while changing some child material's float pins.
• Fix UV mapping of light sources on quad lights.
• Fixed OSL code generation for vector equality tests.
• Fixed self illumination on quads lights.
• Fixed incorrect illumination on surfaces in proximity and parallel to quad lights.
• Fixed volume depth passes when no volumes are used.
• Fixed issue causing wrong values to be displayed in the timeline with some FBX archives.
• Fixed issue causing render errors when large scenes were compiled under low memory conditions.
• Fixed rendering of animations when using a universal camera.
• Fixed scene exports when using universal cameras.
• Fixed issue causing a crash when clicking on "Show in graph editor" on a pin.
• Fixed issue causing auto-bump map not properly working with composite materials.
• Fixed export of empty mesh nodes.

Other changes:

• Added support for NVidia Ampere cards.

Under investigation:

• Denoiser is a limitation on Ampere due to performance issues we have encountered while updating to the required cuDNN library which would affect all GPUs.
• Auto-bump disappears in some cases using a mix of RTX and non-RTX GPUs with RTX on.
• Octane fails to start in some machines with old dual Xeon CPU setups (affected known models are ES-2687, EX645).
• CUDA error in some scenarios when using NVlink due to mismatching barriers.

Downloads for Enterprise subscription users:

OctaneRender Enterprise 2020.1.5 Standalone for Windows (installer)
OctaneRender Enterprise 2020.1.5 Standalone for Windows (ZIP archive)
OctaneRender Enterprise 2020.1.5 Standalone for Linux
OctaneRender Enterprise 2020.1.5 Standalone for macOS (CUDA)

OctaneRender Enterprise 2020.1.5 Render Node for Windows (installer)
OctaneRender Enterprise 2020.1.5 Render Node for Windows (ZIP archive)
OctaneRender Enterprise 2020.1.5 Render Node for Linux
OctaneRender Enterprise 2020.1.5 Render Node for macOS (CUDA)

Downloads for Studio subscription users:

OctaneRender Studio 2020.1.5 Standalone for Windows (installer)
OctaneRender Studio 2020.1.5 Standalone for Windows (ZIP archive)
OctaneRender Studio 2020.1.5 Standalone for Linux
OctaneRender Studio 2020.1.5 Standalone for macOS (CUDA)

Happy rendering
Your OTOY NZ team

[Kalua]

Thanks, team!

[funk]

Thanks team

[Lewis]

Nice, thanks, now we just need someene with Ampere GPU to test results .

[jimho]

I have some trouble on the nvidia 450 drivers,
I installed the latest 452.06 and 451.77 (both studio version, clear install with ddu) but with both version the system could not get into SLI mode, though in the GPU topology it shows the nvlink is connected, just the SLI do not appear in the page of the nvidia contol panel.
Without SLI enabled, the Octane render do not recognize the nvlink peers.

So I get back to the 442.92, the SLI appears, but Octane 2020.1.5 cannot find any GPU.

Lastly I installed 451.48, and finally SLI and octane both working...
I hope it is not that nvidia will take out the support for SLI in the future version of drivers for Geforce 20 series. Seems the quadro's SLI appears differently to 2080ti's in the latter two version of drivers, hope this would not be the nvidia's new stratagy and only just a bad luck.

[mojave]

I have some trouble on the nvidia 450 drivers,
I installed the latest 452.06 and 451.77 (both studio version, clear install with ddu) but with both version the system could not get into SLI mode, though in the GPU topology it shows the nvlink is connected, just the SLI do not appear in the page of the nvidia contol panel.
Without SLI enabled, the Octane render do not recognize the nvlink peers.

So I get back to the 442.92, the SLI appears, but Octane 2020.1.5 cannot find any GPU.

Lastly I installed 451.48, and finally SLI and octane both working...
I hope it is not that nvidia will take out the support for SLI in the future version of drivers for Geforce 20 series. Seems the quadro's SLI appears differently to 2080ti's in the latter two version of drivers, hope this would not be the nvidia's new stratagy and only just a bad luck.

Hi, I have confirmed you do need drivers of version 451 on Windows and updated the original post accordingly. Thank you.

[jimho]

I have some trouble on the nvidia 450 drivers,
I installed the latest 452.06 and 451.77 (both studio version, clear install with ddu) but with both version the system could not get into SLI mode, though in the GPU topology it shows the nvlink is connected, just the SLI do not appear in the page of the nvidia contol panel.
Without SLI enabled, the Octane render do not recognize the nvlink peers.

So I get back to the 442.92, the SLI appears, but Octane 2020.1.5 cannot find any GPU.

Lastly I installed 451.48, and finally SLI and octane both working...
I hope it is not that nvidia will take out the support for SLI in the future version of drivers for Geforce 20 series. Seems the quadro's SLI appears differently to 2080ti's in the latter two version of drivers, hope this would not be the nvidia's new stratagy and only just a bad luck.

Hi, I have confirmed you do need drivers of version 451 on Windows and updated the original post accordingly. Thank you.

Hi Mojave,yes sure I saw it, I get back to 442 just to make sure the issue is not coming from the hardware itself, your statement is clear enough.

If anyone could use SLI on the latest 452 driver for 20 series please let us know, hope it is just me that have missed anything.
I just mean in future if nvidia is not going to support SLI on the turing game cards on studio driver, it will be a problem we do not want to see...

[jimho]

This new version runing very stable here.
I turned on rtx, there is one master and 2 slaves(one is fully rtx support another is fully not), rendering nearly 6 hours,all the three machine are working on almost full speed and very stable,
for my testing scene rtx is 20% faster just as Goldorak had mentioned somewhere else,
I guess this version might be one of the most stable one.

Thanks Otoy team for the hard work!

[whersmy]

This new version runing very stable here.
I turned on rtx, there is one master and 2 slaves(one is fully rtx support another is fully not), rendering nearly 6 hours,all the three machine are working on almost full speed and very stable,
for my testing scene rtx is 20% faster just as Goldorak had mentioned somewhere else,
I guess this version might be one of the most stable one.

Thanks Otoy team for the hard work!

What type of scene are you rendering? Lots of instances?

[jimho]

What type of scene are you rendering? Lots of instances?

There are a piece of grass land(instance),a few trees ,carpet made of ornatrix fur(7200k hairs),the total triangle number is 2.26M,
File size: geometry is about 1.4GB texture 1.6GB
Since there is god ray from sun light(daylight environment+fog medium) and lightings from ineterior, the max samples is set to 35000, no denoiser,image size 4000x5500,
the scene do consume a lot(for 1, the fog; 2, the fur),so maybe good for test of stablize...
the network rendering configuration: master: RTX 2070x1+RTX 2080ti x2 + quadro RTX 6000 x2; slave1: RTX 2080ti x4, slave2:GTX 1080tix4