OTOY Forums

Refractive Software®/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 and 2013 / 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://www.refractivesoftware.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 179€

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:

• It seems that "not smoothed material wrong normals" bug is fixed in new engine...
• SynSky node transform is named accordingly after SunSky node is created.

NEW FEATURES SINCE LAST RELEASE:

• New engine 3.03 version with Kepler support (previous GPUs are supported too).
• "Movable proxy" attribute is added to Meshes and Octane Light nodes. Now by default all scene geometry (including particles and instances) is loaded to octane engine as one common big mesh. It improves the renderspeed very much, but raises the GPU memory consumption and voxelizing time (in the case of particles or instances are present). If you set the "Movable proxy" attribute - this mesh (and all its particles and instances) will be loaded to the engine as separate mesh. It will lower the GPU memory consumption and voxelizing time (in the case of particles or instances are present), and lower the render speed. And in next version it will let to load this mesh separately during the IPR session, so you will not need to reload full scene geometry when changing this "Movable proxy" mesh.
• Triangles count and Meshes count are added to render statistics info.
• Added sliders to Octane Sun direction attributes.

KNOWN ISSUES IN THIS VERSION:

• "Partial scene refresh" in IPR mode will be added in next version: I just want to release this version as fast as possible for those who already have Kepler cards and can't use previous versions at all...
• The strange "low light" issue still exists. As I found - the power of light is cut if the emissive object is loaded as "Movable proxy", other words "as separate object". If it is loaded the "old way" (as part of common mesh) - it has the same power as in 2.58 branch. I already posted the question to engine developers, trying to find the reason of it, and I will release the fixed version immediately after the reason will be found. So far, you can just not set the new Movable proxy attribute in Octane Light nodes and emissive Meshes, or play with ISO or exposition in Imager...

DOWNLOAD

New version HERE.


Yours,
The OctaneRender™ Team.

Thanks JimStar! I've quickly tested everything mentioned above and all seems good. I think we now have a useable version of the 3.xx branch.
Awesome work!

T.

JimStar wrote:And in next version it will let to load this mesh separately during the IPR session, so you will not need to reload full scene geometry when changing this "Movable proxy" mesh.

Awesome!

THANKYOU JIMSTAR!

Fantastic news! Thank you JimStar!

thank you.
Great release.
There is a small bug with the color slider.
Lets say you apply a RBG spectrum node to a glossy / specular input. Then you assign a red color for example. If you pull the color slider to the left it gets black as expected but if you pull it back to the middle the color is gray and not red like it should be.

I have a scene that keeps on crashing. Unfortunately I can not give away the scene for NDA reasons but is there a other log file somewhere that I could hand out to you JimStar?

Refracty wrote:I have a scene that keeps on crashing. Unfortunately I can not give away the scene for NDA reasons but is there a other log file somewhere that I could hand out to you JimStar?

After the crash you can look into the directory c:\Users\<User Name>\AppData\Local\Temp\ for the last files MayaCrashLog*.dmp and MayaCrashLog*.log. These will be very helpful.
And you can enable Octane verbose mode, open the script editor (if you can do it before crash), and take the screenshot of its content after crash. It may be helpful too...

About color slider issue - I will check it, thank you!

Hi Jim!
About color by speed, age and ect.

It is not implemented so far...

It is you work or Octane Team? (:

Can you ask me how to do it, not for octane? May be for lambert material or blinn? (: Thanks! I mean, when I do box or any poly object is instans for nParticles

Thanks! (:

Refracty wrote:There is a small bug with the color slider.
Lets say you apply a RBG spectrum node to a glossy / specular input. Then you assign a red color for example. If you pull the color slider to the left it gets black as expected but if you pull it back to the middle the color is gray and not red like it should be.

Checked it.
It is the Maya's bug in its UI color control. Just try to create standard Maya's "lambert" and play with its "Color" attribute... You will get the same...
I will try to hack it some way later (I think I know how to do it), added it to my TODO...