OctaneRender® for Maya® 2.26.1 - 7.20.2 Win [OBSOLETE]

Sub forum for plugin releases

Moderator: JimStar

Post Reply
User avatar
JimStar
OctaneRender Team
Posts: 3812
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

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.

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.


CHANGES SINCE THE PREVIOUS VERSION
  • Implemented support of Maya's "archive scene" functionality for Octane nodes referencing files.
  • Fixed coordinate space parameter in projection nodes.
  • A couple of minor fixes and improvements...
DOWNLOAD

OctaneRender for Maya 2.26.1 - 7.20.2

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


Yours,
The OctaneRender™ Team.
Last edited by JimStar on Mon Nov 14, 2016 11:52 pm, edited 1 time in total.
calus
Licensed Customer
Posts: 1308
Joined: Sat May 22, 2010 9:31 am
Location: Paris

Well, that was fast, thanks !

About the "coordinate space" fix in projection node,
I must warn people for scene made in previous version,
the textures using projection node may look different,
as the default is "local space" but was actually using "world space",
it's going to really use "local space" now so the projection will be changed.
(you just have to change the coordinate space to "world space" to have the same result as before).

Now "archive scene" includes the Octane dependencie files in the archive,
that's very nice but this functionnality is more than that,
the Octane pathes should also be included with other maya dependencies when listing them with mel or python,
this is especially important for pipeline TD.
And we should be able to make the File Path Editor work with Octane pathes also (first we have to register Octane nodes using the command : filePathEditor -registerType ).
Pascal ANDRE
calus
Licensed Customer
Posts: 1308
Joined: Sat May 22, 2010 9:31 am
Location: Paris

Arf, I was talking too fast about the File Path Editor, I still can't make it work with Octane file path.

It seems the Octane "File" attributes still miss one thing, the MfnAttribute propertie "usedAsFilename".

Code: Select all

filePathEditor -registerType "octaneImageTexture.File" -typeLabel "Octane" ;
// Error: line 1: filePathEditor: Attribute 'octaneImageTexture.File' is invalid or is not designated 'usedAsFilename'. //
The "usedAsFilename" tag may also be important for other Maya builtin functionnalities:
for example the auto-expand feature, Maya can read path with environment variables (ex: "$PRODUCTION_DIR/myScene.ma"),
but still doesn't work with Octane File attribute. ( important feature for managing pipeline)
Pascal ANDRE
Post Reply

Return to “Releases”