OctaneRender® for Maya® beta 2.58g [OBSOLETE]

[JimStar]

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:

• Fixed bug when the sets with invalid triangulation stopped render of entire scene. Improved warning message about it.
• Fixed lost "frame number zero-padding" in the animation sequence file name.
• Fixed "backup image" file naming issue that sometimes led to not saved backup images.

NEW FEATURES SINCE LAST RELEASE:

• Big rework was made to add the "Batch render" mode running from "Render" menu. Note though, that in Windows Maya can't start "native" batch-render on the external computers from "Batch render" menu...
• Improved "Command render" mode support, see additional flags by:

  Code: Select all

  "c:\Program Files\Autodesk\Maya2013\bin\Render.exe" -renderer octane -help

DOWNLOAD

Next version HERE.


Yours,
The OctaneRender™ Team.

[Slimshader]

Batch rendering is working well for me and the frame number padding bug fix is nice to see.
Being able to render so quickly and so completely in the background on one machine is something I've been waiting a long time for.

From the last thread I'll mention again that the renderer restarts in IPR when I change settings in the octaneBlackBodyEmission and the sun/sky node.
It also happens when they're selected in the hypershade.

[JimStar]

From the last thread I'll mention again that the renderer restarts in IPR when I change settings in the octaneBlackBodyEmission and the sun/sky node.

But it is the "LIVE-mode", it must restart if you change some node settings... It just does not reload the mesh automatically, so it is the quick-restart... Perhaps I did not understood what you mean?

It also happens when they're selected in the hypershade.

And that I can't reproduce... I start IPR mode, then open Hypershader, select SunSky - nothing restarted, select BlackBody - nothing restarted...
What for scene? The new one, or already saved? Can you please descript in detail what you do, so I can reproduce it?..

[Slimshader]

Right!
My Mistake.
It needs to re sample when you make changes.
I guess the response seems slower when i change these settings compared to what I'm used to in standalone so I thought it was a bug.

But it is annoying that when I'm in live mode and I select the sun sky node or blackbody in hypershade to look at its settings, the samples restart from 1.

I think it used to do that in standalone too but it happened when anything was selected like a material for instance.
I think they fixed it but I'm not sure.

So you don't get the render starting from 1 sample again when you want to look at the settings on either or those nodes?

[JimStar]

But it is annoying that when I'm in live mode and I select the sun sky node or blackbody in hypershade to look at its settings, the samples restart from 1.

I think it used to do that in standalone too but it happened when anything was selected like a material for instance.
I think they fixed it but I'm not sure.

So you don't get the render starting from 1 sample again when you want to look at the settings on either or those nodes?

Yes, if you just select the node, the render should not restart. If it does - I need some more detailed description (and perhaps the scene), as I can't reproduce it. On my scenes all is OK, when I select any node - the IPR does not restart...

[Slimshader]

I'll look closer at the problem and send a simple scene later this afternoon over here to see what steps are taken.

EDIT: The problem doesn't seem happen at all in this version. Rendering even seems to be snappier when I tweak any light settings in general.

Thanks for all these excellent updates!

[JimStar]

Thank you! I've reproduced it.
It seems that it happens when "Image Texture" is used in node... I'm checking it...

[Slimshader]

Ah yes right.
It does that when there's a file texture on the blackbody node or on the sun sky node.
Glad you could recreate it.

[Slimshader]

I found a bug in the batch renderer from the menu.
It's not seeing the start frame in the Render Settings gui and instead is getting the start frame from the time line.


EDIT: I've got the same problem with the command line rendering.

[JimStar]

I found a bug in the batch renderer from the menu.
It's not seeing the start frame in the Render Settings gui and instead is getting the start frame from the time line.

It was rather not the bug, but "by intention"... I did such a way starting from Octane toolshelf - from the current frame. But I agree that in Batch render it is not the right way, I will change it in Batch to not look at the current frame...
But I still don't know, how about starting the render from Octane toolshelf... How it is more convenient for Maya users: respect the current frame when starting from toolshelf or not?

EDIT: I've got the same problem with the command line rendering.

Strange... I will check it...

I have already fixed the bug with IPR refresh when selecting some nodes. But I'm working at LiveDB now, so all these fixes will be in the next version when it will be ready... I think one-two days...