NOTE: The software in this forum thread is not 100% reliable, this is a development build and is meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release.
!!! THIS IS THE BETA VERSION OF OctaneRender PLUGIN, IT IS RELEASED FOR INITIAL BUG HUNTING ONLY !!!
!!! PLEASE DON'T USE IT FOR PRODUCTION & DON'T SAVE THE SCENES FROM THIS BETA VERSION FOR FUTURE USE AS THERE ARE HIGH CHANCES TO LOSE THEM !!!
!!! SCENES SAVED IN THIS BETA VERSION ARE NOT GUARANTEED TO WORK IN SUBSEQUENT VERSIONS !!!
!!! THE RENDER ENGINE IS YET TO BE STABLE, SOME CRASHES & BUGS ARE EXPECTED FOR THIS TEST VERSION OF THE PLUGIN !!!
Otoy® is proud to announce the availability of a new test version of OctaneRender™ for Maya®: OctaneRender™ 2020.1
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 387 or higher and if you are working on Mac OS that have a CUDA driver installed that supports at least CUDA 9.1.
Changelog and the installers for Octane Standalone 2020.1 are here:
OctaneRender Standalone 2020.1 XB1
Changes since versions 17.3:
- Implemented the support of Maya 2020.
- Implemented the full support of Maya presets for Octane shaders (including Octane OSL shaders' code).
- Implemented the support of array-multi-attributes' UI in Attribute Editor for Octane nodes.
- The Octane SDK 2020.1 XB1 is only released for Windows and Linux. Thus OSX is not supported by this plugin release.
- "CUDA error 700" and other CUDA errors are expected to happen from time to time: these are the Octane engine's bugs. Should be fixed with later SDK/Standalone versions...
- Due to some inconsistency on the rendering engine level the builtin-scriptgraph nodes are not going to be present in the plugin. At least at this stage.
Subscription Enterprise Downloads
OctaneRender for Maya Enterprise [Windows]
OctaneRender for Maya Enterprise [Linux]
Subscription Studio Downloads
OctaneRender for Maya Studio [Windows]
OctaneRender for Maya Studio [Linux]
Some notes regarding the new Autodesk Maya 2020 version:
While implementing the Octane's image-tiles texture for Maya 2020 I've found out that Autodesk has released Maya 2020 with a bug in its "file" texture: if in Attrubute Editor you switch its "UV Tiling Mode" to "Explicit Tiles", add some tiles, and later would try to delete some tile from the list (trash-can button next to it in AE) - Maya throws an error and doesn't delete it.
Octane image-tiles texture does not have this bug.
So if you often use explicit tiles in Maya's "file" texture - you can fix this Autodesk bug by changing one of Maya 2020 scripts (if you decided to do this, you do this on your own risk, I'm not responsible for your possible mistakes):
- Exit Maya 2020 if it is running.
- Find the
c:\Program Files\Autodesk\Maya2020\scripts\AETemplates\AEfileTemplate.melscript (you may have different Maya 2020 installation directory).
- Copy this file somewhere to the safe place, to have a backup of it just in case (you can always place it back later to have your Maya bug back).
- Open the initial file (not a backup-file!) in a text editor.
- Go to the line 524, which initially contains:
symbolButton -edit -command ("AEremoveMultiElement " + $baseAttrName + "; " + $propertyPanelUpdateCmd) textureUvTilingExplicitTrash;
- Replace this whole 524 line by:
symbolButton -edit -command ("python(\"maya.internal.common.ae.multi.removeMultiElement('" + $baseAttrName +"')\"); " + $propertyPanelUpdateCmd) textureUvTilingExplicitTrash;
- Save the file.
- Now you can run Maya 2020.
Don't do this for any Maya versions other than Maya 2020.