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 2011, 2012, 2013 and 2013.5 / 32-bit & 64-bit on MS Windows operating systems.

Notes regarding features/functionality

OctaneRender™ for Maya® implements almost full functionality of OctaneRender™ standalone inside Maya®. Materials from the Live DB are currently not available.

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 279€

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

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.


This is the "quick-fix" version.

BUG FIXES SINCE LAST RELEASE:

• Fixed the bug when the wrong materials rendered in particles in some circumstances.

DOWNLOAD

Next version HERE.

Yours,
The OctaneRender™ Team.

JimStar,

many thank you again, all is well now.

Thank you, JimStar!
Sometimes I need to render images without dof. It would be pretty well to make min value of camera aperture equal to 0.0.
I think it is possible since engine has been changed.
So I can set min value using addAttr: But if I won't use scriping it will be impossible to set the value of Aperture less than 0.01 by hand.

great new features

hm, i was hoping the broken batch render had been fixed now

I am still getting the Error: OctaneRender is not activated!
And i just deactivated it and waited for over an hour before activating it again.
i hope it will get fixed soon..

anyway, still love the octane render so far

Andrew88 wrote:I am still getting the Error: OctaneRender is not activated!
And i just deactivated it and waited for over an hour before activating it again.
i hope it will get fixed soon..

Is the mayabatch.exe executed on the same machine where the plugin was activated in the Maya itself?

Yes i am rendering from the machine that the plugin has been activated on.

Hmm, this version and the previous one don't work on my machine at all... it simply wont render anything....

weird! I get no errors either, and nothing comes up in verbose mode, it just doesn't seem to do anything at all when I try and render?

Win 7 64bit with 2 GeForce GTX 260's

skywxp3d wrote:Hmm, this version and the previous one don't work on my machine at all... it simply wont render anything....

weird! I get no errors either, and nothing comes up in verbose mode, it just doesn't seem to do anything at all when I try and render?

Win 7 64bit with 2 GeForce GTX 260's

OK - so I tried the latest standalone build, and it says it does not support GTX 260's right in the dialog box - so I guess that answers my question.

Will they be supporting these cards anymore or am I out of luck?

Thanks!
Sky

Thank you JimStar!

I have a question. Does this act like a demo also, or I have to install dedicated "maya v1.0 RC3c beta demo" instead?