OTOY Forums

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 2015, 2016, 2016.5 and 2017 64-bit on MS Windows operating systems, 2015, 2016, 2016.5 and 2017 64-bit on Linux operating systems, and 2016, 2016.5 and 2017 64-bit on OSX operating systems (including and above 10.9).

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 Octan eRender™ Standalone on your machine.

For network slave and daemon please download standalone installer here:
viewtopic.php?f=24&t=58640


CHANGES SINCE THE PREVIOUS VERSION

• Added "All available slaves for batch" setting to Octane globals. Allows the batch rendering process to occupy all available Octane render slaves, no matter which of them are enabled in the locally stored net-rendering setting. Disabled by default.

Windows

DOWNLOAD

OctaneRender for Maya 9.35

OctaneRender for Maya DEMO 9.35


Linux

Installation:
- Just run the installer to see its command line keys.

DOWNLOAD

OctaneRender for Maya - 9.35 Linux

OctaneRender for Maya DEMO - 9.35 Linux


OSX

Installation:
- Just run the autoinstaller file.

DOWNLOAD

OctaneRender for Maya - 9.35 OSX

OctaneRender for Maya DEMO - 9.35 OSX

I already test
All available slaves for batch funtion

Deadline Concurrent Tasks Still NOT WORK

Hope .. You fix soon ,, Thank you so much

zurakan wrote:I already test
All available slaves for batch funtion

Deadline Concurrent Tasks Still NOT WORK

Hope .. You fix soon ,, Thank you so much

Are you sure this is not to be updated on the Thinksbox side ?
As I read here : http://deadline.thinkboxsoftware.com/fe ... -rendering
"Please note that not every plugin supports concurrent tasks, but every plugin that does will have a “Concurrent Tasks” option in their In-app Submitter as well as in the above Monitor option."

Also did you try "concurrent task" with deadline and Octane Standalone V3 ? does it works ?

calus wrote:

zurakan wrote:I already test
All available slaves for batch funtion

Deadline Concurrent Tasks Still NOT WORK

Hope .. You fix soon ,, Thank you so much

Are you sure this is not to be updated on the Thinksbox side ?
As I read here : http://deadline.thinkboxsoftware.com/fe ... -rendering
"Please note that not every plugin supports concurrent tasks, but every plugin that does will have a “Concurrent Tasks” option in their In-app Submitter as well as in the above Monitor option."

Also did you try "concurrent task" with deadline and Octane Standalone V3 ? does it works ?

Last version i use (7.xx) concurrent task It work
I jump update to 9.XX not work
I already Check uninstall 9.xx rollbakc to 7.xx i can use concurrent task option

zurakan wrote: Last version i use (7.xx) concurrent task It work
I jump update to 9.XX not work
I already Check uninstall 9.xx rollbakc to 7.xx i can use concurrent task option

Yes I understand that, and maybe it's a bug in the plugin,
but maybe if a renderer change its way to use MayaBatch ( modifications of the tags in the command line renderer) , Deadline should be updated to be compatible with the new version of the plugin, don't you think ?

Also did you try to render concurrent task with last Standalone ? so exporting your Maya scene as ORBX and then : http://docs.thinkboxsoftware.com/produc ... ctane.html

If this doesn't work either with Standalone maybe the Deadline inside scripts needs to be updated for Octane V3 for some reason.

Added "All available slaves for batch" setting to Octane globals. Allows the batch rendering process to occupy all available Octane render slaves, no matter which of them are enabled in the locally stored net-rendering setting. Disabled by default.

Please, it will be very useful if this can be activated in a command line parameter, also.

Because, at render time you can decide what stations to use, and this way can have backwards compatibility with older scenes, when slaves by default where activated no matter what.

Thanks.

Hi Jim, my render with octane v3 hangs randomly with the next error: CUDA error 700 on device 2: an illegal memory access was encountered
-> kernel execution failed(report)
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to launch kernel(ptBrdf2)

I dont have this problem with V2, all my scenes render till the end without problems.

abeoctane wrote:Hi Jim, my render with octane v3 hangs randomly with the next error: CUDA error 700 on device 2: an illegal memory access was encountered
-> kernel execution failed(report)
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to launch kernel(ptBrdf2)

I dont have this problem with V2, all my scenes render till the end without problems.

Hi Abe,
I guess you should give more information if you want your issue to have a chance to be solved,
what is your OS ? what exact version of the plugin do you use? what Maya version ? what is your hardware config ?
do you have the same issue with previous V3 version ? do you use network rendering ?
Do you have this problem with all scene ? if not can you provide a sample scene where you have the issue ?

Anyway I think plugin developer can't do much for this kind of problem "CUDA error 700",
but can you reproduce this error in last Octane Standalone (just export your maya scene as ORBX ) ?
similar issue: viewtopic.php?f=24&t=58640&p=302873&hil ... 00#p302873
maybe a solution here:
viewtopic.php?f=30&t=58710&hilit=CUDA+error+700

Hi callus, thanks for your response , I am on windows 7 64 bits pro, the machine I am using have a 1x1080 and 3x780ti, the weird part is that I deactivated the second card in the render settings and then sent the render, well it looks like now its going normally without hangs, but I looked at nvidia inspector and all the gpus are working at full speed

abeoctane wrote:the weird part is that I deactivated the second card in the render settings and then sent the render, well it looks like now its going normally without hangs, but I looked at nvidia inspector and all the gpus are working at full speed

That's very strange , that looks like a mistake in the plugin code then (per GPU option is a very new feature in Maya).