OTOY Forums

Otoy® is proud to announce the availability of a new OctaneRender™ for Maya® Version 4
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 2016, 2016.5, 2017 and 2018 64-bit on Windows, Linux and OSX operating systems.

License upgrade

Unless you have a subscription license, you will have to upgrade your version 3 licenses to version 4. This upgrade is free and can be done via these 4 steps:

1. Go to https://home.otoy.com/render/octane-render/purchase/
2. Select "Upgrade" in the top menu.
3. Click on "UPGRADE NOW" next to "Upgrade existing licenses to OctaneRender 4".
4. Select the licenses you want to upgrade and confirm.

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 4.04

Please read the new features implemented from Octane Standalone 4 version our blog post.


Changes since version 13.44:

• Minor stability improvements...

Windows DOWNLOAD
OctaneRender for Maya 4.04-13.45
OctaneRender for Maya 4.04-13.45 Demo

Linux DOWNLOAD
OctaneRender for Maya 4.04-13.45
OctaneRender for Maya 4.04-13.45 Demo

MacOS DOWNLOAD
OctaneRender for Maya 4.04-13.45
OctaneRender for Maya 4.04-13.45 Demo



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

OctaneRender for Maya Studio 4.04-13.45 [Windows]

OctaneRender for Maya Studio 4.04-13.45 [Linux]

OctaneRender for Maya Studio 4.04-13.45 [MacOS]

OpenSubD level stopped working in my scene. It was working initially, but I noticed that something was weird: changing the subD value on one mesh, applied that value to all the meshes in the scene, at least in the Properties menu.
Now whatever value I input as subD, nothing happens, it doesn't even restart the render. Manually refreshing the render does nothing.

Just to be clear, this is not a bug introduced in this specific version, I was using 4.04-13.44 when it happened, so I upgraded to this one hoping it would be fixed, but the problem persists.

Rikk The Gaijin wrote:Just to be clear, this is not a bug introduced in this specific version, I was using 4.04-13.44 when it happened, so I upgraded to this one hoping it would be fixed, but the problem persists.

Hi Rikk,

Thanks for reporting this.
We are unable to replicate it yet. would you please PM us a sample file for us to debug?

Hi Jim,

Could we have a quick engine update please for the 4.05 this a huge update on the lua api for us so to have maya plug will be better.

Cheers,
Jo

Hi, I am having a problem with the last 4 versions of the plugin, if I render any scene with a 780ti with the latest 430.86 driver, the gpu render about 100 or 150 frames and then it suddenly stops and sits there doing nothing while maya shows no error or crash, mayabatch.exe is running but is doing nothing, not computer hangs or anything, I have to stop the batch render, then restart maya, reopen the scene, send again the batch render and then the 780ti renders another 100 frames or so and again it stops, I dont have any problem with a 1080 or a 980ti in the same computer with an 7980xe, 128GB of ram with fresh install of windows 10 pro 64bits and maya 2016 sp6, please help

abeoctane
This is a known deadlock issue happening in the Octane engine: Maya batch process just gets frozen waiting for a next Octane engine's call to return, which at some random time never happens. The engine team has been aware of this for quite some time already, and they are still trying to investigate this...
Unfortunately the complex plugin-level workarounds I tried don't work for this bug, it must be investigated/fixed on the engine level which only the engine team is able to debug. But it should become OK in the plugin after the engine guys find the reason of it...
Sorry for that.