OctaneRender® for Maya® 1.55 - 3.5 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, 2013.5 / 32-bit & 64-bit, 2014 64-bit and 2015 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 359€

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 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 AND FIXES SINCE LAST RELEASE:

• Fixed broken displaying of textures in viewport and UV-editor.
• Fixed sunset color bug.
• Minor fixes and improvements...

DOWNLOAD

OctaneRender for Maya 1.55 - 3.5 (28.8MB autoinstaller file)
OctaneRender for Maya 1.55 - 3.5 Demo (26.7MB autoinstaller file)


Yours,
The OctaneRender™ Team.

[prodviz]

Awesome, cheers Jim.

[Slimshader]

Nice thanks!

[Vyoor]

Wow!

Thank you JimStar!
Now SunSky works perfectly
Can't wait for 2.0

Cheers!

[matrix2012]

Thank you for all of your hard working JimStar

[p3taoctane]

Upon loading PLugin

AutoLoad selects... Loaded does not

Been using the previous version o problem for weeks...

Standalone 1.5 and 2.02 both load and run with registered authorization

Get error
//Error: Unloading Octane... //
//Error: Line 1: initializePLugin function failed (OctanePlugin) //
//Warning: line 1: waitCursor stack empty

Any ideas

[p3taoctane]

I removed all my prefs
Reloaded plugin

choosing loaded first.... then autolaod and it worked

all good

[churumbela]

Hi,
I'm currently in the middle of a rendering process and I'm stucked with a strange error.
Batch render starts normally and indicates to be rendering each frame as usual. However, no file is written afterwards.

The maya render log shows this:
Error saving frame x ("png" image to "(my folder structure)"): (kFailure): Unexpected Internal Failure
it does so for every frame and it doesn't indicate anything else.

Any help will be much appreciated, since these renders are due quite soon.
(I'm using render layers, dunno if it has something to do with this).

thanks!

[JimStar]

churumbela
I think it may be something with the save-path itself - perhaps access rights to folder for batch process... I can't say more precisely without having the scene... But it is unlikely that render layers are the reason: your issue appears already on the rendered image saving stage.
Did you try different paths and/or file names to save the images? Did you try different image types (including .exr)?..

[churumbela]

Hi JimStar, thanks for your quick response!
the full error says:

ERROR, Cannot open file C:/Users/etc/filename_0010.png; ensure that it exists and is of type "PNG"
ERROR, No more internal memory
Error: line 0: Failed to open output file: C:/Users/etc/filename_0010.png
Error: Octane: Error saving frame 10 ("png" image to "C:/Users/etc/filename_0010.png"): (kFailure): Unexpected Internal Failure

I've created a test scene using renderlayers and saving images to the same path and in the same PNG format and it worked, so you're right, render layers are not the problem, but also isn't the file format nor the file path.

I've tried rendering the original scene in another format with no luck.
The "no more internal memory" message makes me think maybe it has something to do with the very large textures I'm using?
gonna try downresing them to see what happens.