OctaneRender® for Maya® v1.20 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.20 engine.
• Fixed the issue when the GPU memory was not freed before the batch render start (if there were some IPR or "one frame" renders made before starting batch).
• Fixed the mesh compilation bug (TBFX reported).
• Fixed the orthographic camera scale matching.
• Added the "Enable LiveDB refresh" checkbox to Octane global settings (disabled by default). For those who does not have the network connected.
• Added the "Render priority" to Octane global settings.

DOWNLOAD

OctaneRender for Maya v1.20 beta (49.4MB autoinstaller file)


Yours,
The OctaneRender™ Team.

[cyrillweiss]

Thx jim

[RickToxik]

Hey Thank you Jimstar for the offline option, I really appreciate. Keep up the good work! Btw my new employer was really impressed with my octane-renders ; )

[xtrm3d]

thank you,
would jump on it tonight ...
any news about motion blur ?

[TBFX]

Thanks JimStar,

All good here. Have you looked into the renumber frames issue at all?

T.

[JimStar]

any news about motion blur ?

It should be asked to engine developers, not to plugin developers. As the true 3D motion blur is the render engine feature.
If it will be added to the engine (and to the SDK of course) - it will be added to the plugins.
I will look what I can do from the 2D side, perhaps I will be able to fake the true motion blur using few frame-images merging...

PS. Please, always send me the "*.dmp - *.log" file pairs which Maya creates in user's Temp folder in case you get Maya crashes (and some info about plugin-Maya versions you use). As I can't fix these things if I have no detailed reports about them, I even don't know what module crashes - the plugin or Octane engine...
You should have some of these reports still sitting in your Temp folder.

[JimStar]

Thanks JimStar,

All good here. Have you looked into the renumber frames issue at all?

T.

I will look at it, just a little later...

[TBFX]

I will look at it, just a little later...

Cheers.

perhaps I will be able to fake the true motion blur using few frame-images merging...

That would be awesome if you could. It'd be great if we could set the number of time samples and shutter speed as a percentage of frame length and the plugin would automatically drop the Max samples, render the appropriate sub frames and average the output back into the final frame. This would give true MB and work for all geometry including deforming at very little render time cost and without the need to render extra frames that get discarded as with the brute force method I described in this thread http://render.otoy.com/forum/viewtopic. ... ber+frames using the renumber frames feature. There would of course be the extra overhead of scene compilation per sub frame but this would be minimal in most cases if you manage the geo in the scene well with movable proxies etc.

Would still be good to get renumber frames working in any case as there are uses for this other than MB.
T.

[xtrm3d]

perhaps I will be able to fake the true motion blur using few frame-images merging...

this is already a lot more than what i did expect ...
i was more thinking about camera motion blur .. but yes.. if you manage to do real motion blur i would consider you a genius

[JimStar]

i was more thinking about camera motion blur ..

As I already wrote - it is not supported by Octane SDK... So, the only way for the plugin - fake it in 2D mode...