OctaneRender® for Maya® 3.03.2 - 8.02 Win [ALPHA]

Sub forum for non-production plugin releases
k.a.schubert
OctaneRender Team
Posts: 137
Joined: Mon Feb 22, 2016 2:52 am

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®.
mayalogo.png
Maya® Version Requirements
This release will work with Maya® 2015, 2016, 2016.5 and 2017 64-bit on MS Windows operating systems.

Notes regarding features/functionality
OctaneRender™ for Maya® implements almost full functionality of OctaneRender™ standalone inside Maya®.

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 619€

If you already own one or more OctaneRender™ Standalone Edition licenses you want to pair the plugin with:
Purchase an "OctaneRender™ for Maya® License" priced at 269€
You can also purchase a 3, 5 or 10 pack of OctaneRender™ for Maya® licenses, just like OctaneRender™ Standalone Edition packs.

LICENSE MANAGMENT
Just like OctaneRender™ Standalone, the Maya® plugin license activation is done at startup in the activation pop up window.
Deactivating the plugin license can be done from within Maya® (render settings window / octane license tab).

ALPHA DISCLAIMER
Please note there are known issues due to ongoing development.

V3 DOCUMENTATION
Documentation <- please read, there are some important workflow steps here!

CHANGES SINCE THE PREVIOUS VERSION

  • 1. Automatic creation of basic nodegraph with one click (shelf button)
    2. Automatic creation of volume related nodes between fluid shape and a geometry group (shelf button)
    3. Automatic connection of the currently used camera (cycleThrough in viewport, IPR select) and the camera transform converter
    4. Fixed the IPR crash (except for a reported maya bug in 2015 and 2016, fixed in 2016.5 and 2017)
    5. Fixed color/position attribute generation and UI
    6. Fixed naming in the nodes to use nice names for child attributes of compounds and colors
    7. Support for Pascal GPU's (1080's etc.), refer to Standalone 3.03.2
Reported Maya bugs
Appearing in Maya 2016 and below when switching from OctaneRender (tested as well with MentalRay) to Maya software in the Render view, while the node editor is open.
So make sure that the node editor is closed, before opening the IPR window, else Maya will crash with this bug, cause Maya software is the default renderer.

In Maya 2017 OctaneRender sometimes (for me always) does not get displayed in the combo box in the render view, only in the combo box in the render settings.
Solution: Reset Maya preferences: rename the prefs folder.

Not recommended for production!


DOWNLOAD

Links have been removed - apologies for any inconvenience. As there will be significant differences between the current alpha release and upcoming beta release, please do not use the alpha release for production work.


Yours,
The OctaneRender™ Team.
solomon
Licensed Customer
Posts: 343
Joined: Tue Mar 19, 2013 2:04 pm
Location: USA
Contact:

Woooohooooo!!! thank you :)
Solomon W. Jagwe
3D Artist/Animator/Modeler | Independent Film Director
http://www.sowl.com | http://www.galiwango.com | http://www.nkozaandnankya.com
renmaxhb
Licensed Customer
Posts: 226
Joined: Mon Dec 13, 2010 8:53 am

win10,GTX1070,
maya2015 2016 crash when load the pluin!
maya 2017 show errer warning when load the plugin!

:mrgreen:
k.a.schubert
OctaneRender Team
Posts: 137
Joined: Mon Feb 22, 2016 2:52 am

What error warning in 2017?
Did you execute the installer as admin?

Tested again on my machine, works okay. Files get placed in the right folders and loading the plugin works as well.

Still I'm taking a look at the installer script.

Most likely some file is missing which octane needs.

GPU should not matter for loading the plugin.
renmaxhb
Licensed Customer
Posts: 226
Joined: Mon Dec 13, 2010 8:53 am

maya2017 win10 gtx1070


(OctanePlugin) //
// Error: line 1: Unable to dynamically load : C:/Program Files/Autodesk/Maya2017/bin/plug-ins/OctanePlugin.mll
renmaxhb
Licensed Customer
Posts: 226
Joined: Mon Dec 13, 2010 8:53 am

another PC ,win7 gtx780ti,all is ok :mrgreen:
k.a.schubert
OctaneRender Team
Posts: 137
Joined: Mon Feb 22, 2016 2:52 am

Hmm, seems to be coming from the experimental support of Pascal GPUs...

When starting the Octane API it supposedly returns an error, but that should be displayed
in the script editor with something like "Error starting Octane engine: ..."

That's as far as the plugin is responsible.

Let me put a 1080 in my machine and see... (Tested with my Titan until now)
User avatar
ivankio
Licensed Customer
Posts: 103
Joined: Thu Nov 14, 2013 11:39 pm
Location: Curitiba - Brazil
Contact:

Interesting pace... It doesn't seem to prove as better to disdain voluntary help, but let's try to keep the optimism.
I began to expect nothing less than the most efficient and wonderful workflow I couldn't even imagine. I'm kidding, such pressure would do only harm.

Good luck, keep it up. We hope to see it production ready soon.
GTX 1080 8gb, GTX 970 4gb, I5 4590, Z97-E, 32gb RAM, Win 10 64bits, Octane for Maya
solomonfl
Licensed Customer
Posts: 51
Joined: Tue Jul 26, 2016 7:31 pm

hmm... what does this error mean?

// Error: Found no node Object of type: RenderTarget* / rendertarget* / RENDERTARGET* //

I using Maya 2017 and tested with Maya 2016, I got the same error. I have two 1080s for my gpu setup
solomonfl
Licensed Customer
Posts: 51
Joined: Tue Jul 26, 2016 7:31 pm

k.a.schubert wrote:Hmm, seems to be coming from the experimental support of Pascal GPUs...

When starting the Octane API it supposedly returns an error, but that should be displayed
in the script editor with something like "Error starting Octane engine: ..."

That's as far as the plugin is responsible.

Let me put a 1080 in my machine and see... (Tested with my Titan until now)
I have two 1080s, I am getting an error when I try to use IPR, any idea what could be causing it?

I also get an the same error when I try to manage licenses ~ so I am not sure if that's the problem

// Error: Found no node Object of type: RenderTarget* / rendertarget* / RENDERTARGET* //
Post Reply

Return to “Testing Releases (Non-Production)”