OctaneRender® for Maya® 2.23.2 - 7.6 Win [OBSOLETE]

[JimStar]

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 2013.5, 2014, 2015 and 2016 64-bit on MS Windows operating systems.

Notes regarding features/functionality

OctaneRender™ for Maya® implements almost full functionality of OctaneRender™ standalone inside Maya®.

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 OctaneRender™ Standalone on your machine.


HOW TO PURCHASE LICENSES

Go to our online shop here: http://render.otoy.com/shop/

If you do not own an OctaneRender™ Standalone Edition License yet:
You can purchase both the OctaneRender™ Standalone Edition and the OctaneRender™ for Maya® Edition as a reduced price bundle, purchase the bundle priced at 459€

If you already own one or more OctaneRender™ Standalone Edition licenses you want to pair the plugin with:
Purchase an "OctaneRender™ for Maya® License" priced at 199€

You can also purchase a 3, 5 or 10 pack of OctaneRender™ for Maya® licenses, just like OctaneRender™ Standalone Edition packs.


OCTANELIVE

Just like OctaneRender™ Standalone, the Maya® plugin product also needs an additional OctaneLive license and be activated on a machine.
This has to be done in the plugin interface panel in Maya, and is covered in the included PDF manual.
It can only be done after an OctaneRender™ Standalone license is already activated on the machine in question.


CHANGES SINCE THE PREVIOUS VERSION

• Maya 2016 support is implemented.
• Fixed the Octane renderview resolution bug.

DOWNLOAD

OctaneRender for Maya 2.23.2 - 7.6 (12.3MB autoinstaller file)
OctaneRender for Maya 2.23.2 - 7.6 Demo (10.8MB autoinstaller file)

For network slave and daemon please download standalone installer here:
http://render.otoy.com/forum/viewtopic.php?f=24&t=46125


Yours,
The OctaneRender™ Team.

[sirenesoong]

Thanks! Beautifull!

[zurakan]

it slow than 6.1

[dsyee]

Hi Jim - Thanks for Maya 2016 support! However, I'm noticing some odd behavior in the Hypershade. I set up a simple Octane material with a file texture, like this:

Then:
1. Change a float attribute (e.g., set material's Specular to 1.0).
2. Click on another node.
3. Click on the original node. The float attribute is reverted back to what it was before step 1.

If I click on the "Toggle between Lookdev/Attribute view" button in the Hypershade's Property Editor before step 1, it seems to work fine. It seems like maybe Octane isn't "remembering" changes in Lookdev view, but it does in Attribute view.

This is related to a second issue, which is that I can't seem to tell if an Octane node is in Lookdev or Attribute mode, because there's no visual indication of a difference. The standard Maya Phong looks like this in Lookdev (lower right):

and this in Attribute view:

Hope this could be a quick fix! It's hard going back to the "old" ways after working with the new Hypershade...

[Jolbertoquini]

Hi Jim

I have this problem with the displacement really weird results on the UV, subdiv and etc ... on this version http://render.otoy.com/forum/viewtopic. ... 10#p233284 so how we apply the fix from the standalone guys but on maya?

Thanks
JO

[Andrew88]

Hi i was wondering why there is no longer support for maya 2013 ?
could you please make support for v 2013 ?

thanks

[churumbela]

Hi, we're currently using this plugin version on Maya 2014 and we've run into an important issue:

When using Octane lights and doing an IPR, everything goes fine until we change to another frame in time.. then some of the lights randomly disappear from the render.
It seems that they're somehow being left out of the voxeling, since changing the missing lights' attributes doesn't reset the IPR.

This problem becomes quite serious because the same thing happens when doing a batch render: the first rendered frame is ok, but the rest of them will have some of the lights turned off.
Here is an example:



Any advice on how to solve this would be very helpful, since we're working on a project within a limited time frame.

Thanks in advance,
Oscar.

[gabrielaraujo712]

Where is the ISO and F-stop?

[JimStar]

Next version HERE.