OctaneRender® for Maya® v1.0 RC3c beta [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 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.


BUG FIXES SINCE LAST RELEASE:

• Fixed "Caustic blur" attribute which did not affect the render when changed.

DOWNLOAD

Next version HERE.


Yours,
The OctaneRender™ Team.

[Elvissuperstar007]

super

[jmfowler]

Jimstar - thanks!

Elvis - I thought you were a max user?

[Elvissuperstar007]

Jimstar - thanks!

Elvis - I thought you were a max user?

yes I'm using max) but the development in Maya I wonder

[skywxp3d]

For some reason, since about 3 versions ago - I cannot use both GForce cards - I get this out of memory crash...

- Now it seems I'm crashing on just one card, and its a dead simple scene!

CUDA error 999 on device 0: An unknown internal error occurred. -> Failed to launch kernel (pmc)CUDA device 0: PMC failed

// Error: Octane: render failure, stopped //

[jacobkolady]

Hello Guys I just updated my maya plugin to this version and now when i render I get this error.

Octane: Error mesh export. Octane render stopped.

Can someone help me with sorting this out. The scene was rendering perfectly with the previous plugin.
Thank You

[JimStar]

Hello Guys I just updated my maya plugin to this version and now when i render I get this error.

Octane: Error mesh export. Octane render stopped.

Can someone help me with sorting this out. The scene was rendering perfectly with the previous plugin.
Thank You

Post all export log please.

[TBFX]

Fixed "Caustic blur" attribute which did not affect the render when changed.

Thanks JimStar, this attribute now works but I still have to refresh an IPR session to see it update. in the standalone changing it forces a refresh.
I have checked and I don't seem to be having the batch rendering issues others are having.

T.

[jmfowler]

For some reason, since about 3 versions ago - I cannot use both GForce cards - I get this out of memory crash...

- Now it seems I'm crashing on just one card, and its a dead simple scene!

CUDA error 999 on device 0: An unknown internal error occurred. -> Failed to launch kernel (pmc)CUDA device 0: PMC failed

// Error: Octane: render failure, stopped //

what cards are you using together?

[Refracty]

I have a question regarding to the animation modes.
I have a scene that contains only camera and texture animation.
If I set the scene to Camera Animation only the textures are frozen.
I need to render this out quick - So any voxiling will make the goal to reach the deadline impossible.

Isn't it possible to to set the animation mode to "camera movement" and still have the animated texture updates possible?

That would be perfect.