OTOY Forums

Otoy® is proud to announce the availability of a new OctaneRender™ for Maya® Version 2020.2
The world's fastest and most feature-rich unbiased render engine that integrates completely into Autodesk® Maya®.

Maya® Version Requirements

This release will work with Maya® Versions 2017, 2018, 2019 and 2020 64-bit on Windows, Linux and OSX operating systems.

To use this version, you need a GPU of compute model 3.0 or higher. Support for Fermi GPUs (like GTX 4xx and 5xx) has been dropped. Also make sure you use a driver of version 419.17 or higher and if you are working on Mac OS that have a CUDA driver installed that supports at least CUDA 9.1.

Octane for Maya masterclass:
https://www.youtube.com/watch?v=fANBzifhSow&list=PLTqdDmFtprFkzaBM7cmp8ZipQCNupDD0H


Changelog and the installers for Octane Standalone are here:
OctaneRender Standalone 2020.2.1


Changes since version 19.11:

• Integrated the 2020.2.3 engine.
• Improved the Octane lights' presentation in Maya's viewport, to make them better visible from sides.

=================================
Subscription Enterprise Downloads
=================================

OctaneRender for Maya Enterprise [Windows]

OctaneRender for Maya Enterprise [Linux]

OctaneRender for Maya Enterprise [MacOS]


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

OctaneRender for Maya Studio [Windows]

OctaneRender for Maya Studio [Linux]

OctaneRender for Maya Studio [MacOS]


=================================
DEMO Downloads
=================================

OctaneRender for Maya DEMO [Windows]

OctaneRender for Maya DEMO [Linux]

OctaneRender for Maya DEMO [MacOS]

Hi!

What's about Maya 2022 support?

Cheers!

Vyoor wrote:Hi!

What's about Maya 2022 support?

Cheers!

Hi Vyoor,

Thank you!!
Unfortunately, we are in the middle of reworking for OFM's Octane render passes which is a high priority task for us.
We are planning to add support for Maya 2020 with OctaneRender 2021 and keep the 2020.2.x branch for production.

We hope to get it done ASAP!!

cheers

Oh, yeah =) Finally =) Thank you very much for this update!

Exposure setting in octaneColorCorrectTexture should be 0 default. 1 equals a change from current value in texture color.

Is the universal camera vignette broken? I was randomly trying to use it last night and it didn't seem to have any affect at all

g0ll4m wrote:Exposure setting in octaneColorCorrectTexture should be 0 default. 1 equals a change from current value in texture color.

Hi G0114m,

Thank you for reporting this!
We have fixed it for the next release.

Cheers

itsallgoode9 wrote:Is the universal camera vignette broken? I was randomly trying to use it last night and it didn't seem to have any affect at all

Hi Itsallgoode9,

Thank you!! It seems to be working on our side.

The workflow we did is to change the Octane Camera type as Universal from the dropdown.
Then increase the Opt. vignette distance value.

Ah sorry! we did find there are two Abberation rollouts. This will be fixed for the next release!!


cheers

Thanks for the update Guys!

I was checking something about universal camera the depth field options and the split focus "diopter focal depth" should be the same unit then the "depth field" default 100 and diopter default 1.110 looks like the option is set in meters so we can't type similar number and offset if we want we have to calculate manually which is terrible specially when we use scene scale at "0.01" to have scene in CM as defaut maya units most be something weird on the code I think.

Because if my depth is set at 100 for example and I want split my focus at 150 if type 150 doesn't work I need actually type 1.50 can be really confusing to use the tool.

Cheers,
JO

I've never noticed this before, probably because I've never looked...

But on my 32 core threadripper I'm getting 100% CPU usage across all cores when I enable Octane in the viewport. It actually doesn't seem to cause problems with other apps; am I to assume that the Octane plugin takes whatever it can get of spare CPU cycles or something? Or is this a bug with the current build? Maybe this is old news and I've just never paid attention. As soon as I switch back to Viewport 2.0, CPU usage returns to normal.

Not seeing this CPU usage with OctaneRender standalone.