OTOY Forums

This is a TEST version, so be prepared to have some issues. Don't use it for production.

Maya® Version Requirements

This release will work with Maya® Versions 2015, 2016, 2016.5 and 2017 64-bit on MS Windows operating systems, 2015, 2016, 2016.5 and 2017 64-bit on Linux operating systems, and 2016, 2016.5 and 2017 64-bit on OSX operating systems (including and above 10.9).

COMPATIBILITY AND OCTANERENDER STANDALONE REQUIREMENT

To run OctaneRender™ for Maya®, you need to also have an activated OctaneRender™ Standalone copy activated on the machine you wish to install the plugin onto.
You cannot purchase and use only the Maya plugin and use it without also owning an activated copy of Octan eRender™ Standalone on your machine.

For network slave and daemon please download standalone installer here:
viewtopic.php?f=33&t=60015


CHANGES SINCE THE PREVIOUS VERSION

• New 3.06 TEST 3 engine integrated.
• Implemented export of selected objects.
• Implemented rendering engine's level multiple UV support. The active one plus additional two of Maya's multiple UVs are now loaded into Octane engine.
• Minor fixes and improvements...

Windows

DOWNLOAD

OctaneRender for Maya 10.1


Linux

Installation:
- Just run the installer to see its command line keys.

DOWNLOAD

OctaneRender for Maya - 10.1 Linux


OSX

Installation:
- Just run the autoinstaller file.

DOWNLOAD

OctaneRender for Maya - 10.1 OSX

can i use it in my project?

renmaxhb wrote:can i use it in my project?

Please read the post...

JimStar wrote:This is a TEST version, so be prepared to have some issues. Don't use it for production.

Best,
JO

Hi Guys,

I have some issue with the scenes related at UVsets. I attach the scenes here I have Maya 2017 update2 with windows...basically for some reason is crashing.

Cheers,
JO

Jo's scene also crash for me in Maya 2016,
but if I reload the texture path, delete unknown nodes, save to maya binary, reload the scene, I don't have the crash anymore.
So I'm not sure where this crash comes from.
Also I'm not able to reproduce this problem from scratch, but anyway this is a crasher so must be fixed.

Lots of improvements in this version, in plugin and core, thanks
I found it relatively stable in my tests,
adaptive sampling works fine.

thanks for fixing the disable partial alpha label,
and for fixing the materials normal map attribute,
though it's not fixed everywhere, Octane lights still have the problem,
I guess when translated to mesh light at rendertime, a greyscall texture is used as normal map, so light material/normal is wrong.

JimStar wrote:

• Implemented rendering engine's level multiple UV support. The active one plus additional two of Maya's multiple UVs are now loaded into Octane engine.

Thanks for this important improvement, secondary UVsets can be used for a lot more than texturing (to get around some Octane core limitations).
Nice work on the implementation.

JimStar wrote:

• Implemented export of selected objects.

Thanks a lot for this, this is huge workflow improvement.
Can still be improved, if possible export selection should not add a render-target in the ORBX. (but maybe this is a limitation of the SDK ?)

Actually the render selected objects only feature in render-view behaves the way export selection should work,
selected geometry is rendered but with default octane render target,
(so no camera/settings exported except if you select also a Camera and the OctaneSettings node).

Ideally behaviors must be swapped, render selected objects only should automatically extract the current camera and render settings on top of selection,
and export selection should not export any Camera and Settings if no camera is selected.

The triplanar projection node is missing.