OctaneRender® for Maya® v1.18 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, 2013.5 / 32-bit & 64-bit and 2014 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.


CHANGES AND FIXES SINCE LAST RELEASE:

• New 1.18 engine.
• Maya 2014 support.
• New "Aperture Edge" and "Distortion" attributes in camera.
• New "Spectral Intensity" and "Spectral Shift" attributes in postprocessor.
• Fixed non-interactive "one frame" render-mode status refresh.

DOWNLOAD

OctaneRender for Maya v1.18 beta (49.5MB autoinstaller file)


Yours,
The OctaneRender™ Team.

[TBFX]

Thanks JimStar,

I have tested this in Maya 2014 and all seems good. I also no longer get hypershade crashes in my current scene with this version running in Maya 2014. In fact the hypershade seems far more responsive than it did in Maya 2013. It's possible that it was simply a Maya issue in 2013 that I hadn't picked up as I mostly use the node editor now.

T.

[kayze]

Hey jimstar just a heads up.
The Daylight Environment comes in with almost black sky and a greyish ground as default.

[ypolyz]

Hi JimStar,
I had installed OctaneRender for Maya v1.17 in Maya2013, today I want to install v1.18 in Maya2014.
I deactivated OctaneRender for Maya v1.17 in Maya2013 and tried to activate v1.18 in Maya2014 but received: "Error activate Octane plugin:password attribute is not set!".
Please, help me.

PS: where did Custom Area?

Thanks,

[ypolyz]

JimStar,

I have successfully activated Octane for Maya v1.18 in Maya2014.

[JimStar]

Hey jimstar just a heads up.
The Daylight Environment comes in with almost black sky and a greyish ground as default.

It seems like some ancient Maya's version issues - as I see you still use 2011?..
Just have checked it in 2013 - all is OK...

[JimStar]

Hi JimStar,
I had installed OctaneRender for Maya v1.17 in Maya2013, today I want to install v1.18 in Maya2014.
I deactivated OctaneRender for Maya v1.17 in Maya2013 and tried to activate v1.18 in Maya2014 but received: "Error activate Octane plugin:password attribute is not set!".
Please, help me.

PS: where did Custom Area?

Thanks,

Maya's user interface is some ugly - it does not change the attribute's value if you have not changed the keyboard focus from the field where you have entered it. Moreover, it does not change this focus automatically from just filled field after you have clicked the button in the form (it is common behavior in every normal GUI). So, you have to press "Enter" or "Tab" after you have entered the login or password field before pressing "Activate", otherwise the attribute value will not be set before trying to use it in activation process... Ugly, but it is how Maya's GUI works...

[ypolyz]

Thanks JimStar.

[TBFX]

Hi JimStar,
I have found a bug in this version. I have a scene (a cut down version is attached) that will render fine in IPR mode but as soon as you try to render in standard render mode or batch render it errors out when it tries to compile the instanced geometry. The geo is manually instanced and not particle instanced.
The error in verbose mode is as follows:
Octane: Object "grillSection_1|grillSectionVerticals_2|pCylinder182_3|pCylinder_Shape102" is instanced //
// //
// 0:01 Setting Mesh data of mesh: pCylinder_Shape102 //
// ****************************** MESH DATA ****************************** //
// Number of vertices: 14 //
// Number of normals: 14 //
// Number of UVs: 28 //
// Number of polygons: 18 //
// Number of vertex indices: 60 //
// Number of normal indices: 60 //
// Number of UV indices: 60 //
// Number of material indices: 18 //
// 0:01 ...done setting Mesh data in 0:00 //
// 0:01 Voxelizing... //
// 0:01 ...voxelized in 0:00 //
// Error: Octane: error compiling mesh "pCylinder_Shape102" (instance 1) //
// Error: Octane: Error mesh export. Octane render stopped. //

This bug may have crept in to a version before this one as I haven't rendered this scene in a while but it is definitely present in v1.18 and the scene did render fine in v1.0

T.

[renmaxhb]

TBFX,

All versions have the bug you found.