OTOY Forums

Otoy® is proud to announce the availability of a new version of OctaneRender™ for Maya®
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 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 Octane Render™ Standalone on your machine.

For network slave and daemon please download the Standalone installer here:
viewtopic.php?f=24&t=61365


CHANGES SINCE THE PREVIOUS VERSION

• Implemented New Engine 3.06.1 SDK integrated.
• Implemented Octane VDB file support in Maya
• Implemented IES distribution visualization in Maya viewport
• Implemented color picking support for Light node
• Implemented Octane menu bar
• New improved Maya viewport support - (DirectX, Legacy, and V2.0)
• Label changes on Emission node similar to SA
• Fixed lost material on alembic files
• Fixed memory flush with duplicate nodes
• Fixed naming convention for Render passes, render layer and info passes.

Bug fixed for:

viewtopic.php?p=313728#p313728
viewtopic.php?p=313519#p313519
viewtopic.php?f=110&t=61422




Windows

DOWNLOAD

OctaneRender for Maya11.3

OctaneRender for Maya DEMO 11.3


Linux

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

DOWNLOAD

OctaneRender for Maya - 11.3 Linux

OctaneRender for Maya DEMO - 11.3 Linux


OSX

Installation:
- Just run the auto installer file.

DOWNLOAD

OctaneRender for Maya - 11.3 OSX

OctaneRender for Maya DEMO - 11.3 OSX

@Bikram,
Ok now we can see in this release what JimStar was working on since 2 months,
but I still can't see any good reason why you never answered about what was going on.

This was a huge mistake to stop any relevant communication during these 2 months :
As expected this was a complete waste of time, most of the new features and improvement are not the priorities,
and the new implementations are terrible, it try to reinvent the wheel instead of using Maya API mechanisms and conventions,
too bad Maya user feedback and priorities are totally ignored
(because of the lack of Otoy dialog with experienced Maya users.)

As I was afraid, current OctaneForMaya development "plan" doesn't make any sens,
please someone from Otoy contact me to stop this complete waste of time for everyone, and work on a proper development prioritization plan.

Listen to calus plz

BK wrote:

• Implemented Octane VDB file support in Maya

This feature is very importatant but was no more a priority as ORBX proxy is supposed to come with octane 3.07,
also this is just copy of the feature develloped for 3Dsmax, Maya and 3DSmax are different software with different workflows...

BK wrote:

• Implemented IES distribution visualization in Maya viewport

Again just a copy of a bad 3Dsmax feature, it was not at all a priority and was never asked ...

BK wrote:

• Implemented color picking support for Light node

don't waste time on octane light, the light itself need a new proper implementation from scratch instead of patching bad initial implementation.

BK wrote:

• Implemented Octane menu bar

Ok this one should have been in Maya since years, but it doesn't solves the problem that each command in the menu is very badly implemented,
this should have been worked while thinking again the Octane commands not following any Maya convention...

BK wrote:

• New improved Maya viewport support - (DirectX, Legacy, and V2.0)
• Fixed lost material on alembic files
• Fixed memory flush with duplicate nodes

This was not the good way to fix these problems, JimStar needs first to ditch Octane Material custom attribute and the Octane "texture" data type,
then use standard maya attributes instead with all the builtin Maya mechanisms coming with them (proper View port 2.0 support comes almost for free if you use maya API as it's supposed).
What a waste of time by trying to re-invent the wheel ....

artdanylov wrote:Listen to calus plz

"Hire Calus plz" <--- fixed that for you

WE WANT CALUS

For subscribers can we get an OctaneVR release of this build ASAP!!!

Hi guys,

Thank you so much for your comments..

Hi,Jim,BK


Thank for your jobs.It works well.

I can render maya abc file with any number deadline task by my seven renderfarmers.

Happy rendering

Hi Renmaxhb,

Thank you so much for letting us know that it is working well now