OctaneRender for Maya 2018.1-14.24 [OBSOLETE]

[JimStar]

Otoy® is proud to announce the availability of a new OctaneRender™ for Maya® Version 2018.1
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 2016.5, 2017, 2018 and 2019 64-bit on Windows, Linux and OSX operating systems.

To use this version, you need a GPU of compute model 3.0 or higher. Support for Fermi GPUs (like GTX 4xx and 5xx) has been dropped. Also make sure you use a driver of version 419.17 or higher and if you are working on Mac OS that have a CUDA driver installed that supports at least CUDA 9.1.


Changelog and the installers for Octane Standalone 2018.1 are here:
OctaneRender Standalone 2018.1


Changes since version 14.23:

• Integrated the fixed Octane SDK build: was broken for Enterprise Linux flavours.
• Implemented the support of Ornatrix' "Viewport Count Fraction" attribute.

=================================
Subscription Studio Downloads
=================================

OctaneRender for Maya Studio [Windows]

OctaneRender for Maya Studio [Linux]

OctaneRender for Maya Studio [MacOS]


=================================
Subscription Enterprise Downloads
=================================

OctaneRender for Maya Enterprise [Windows]

OctaneRender for Maya Enterprise [Linux]

OctaneRender for Maya Enterprise [MacOS]


=================================
DEMO Downloads
=================================

OctaneRender for Maya DEMO [Windows]

OctaneRender for Maya DEMO [Linux]

OctaneRender for Maya DEMO [MacOS]

[teammach]

i have major problems with the all octane maya 2018.1 releases and Maya 2019.
Batchrendering is still a lottery if its getting stuck or not. And also it seems that everytime i open a scene the image format is set back to *alias pix* format.
And once i switch back to exr the frame doesnt get written out. script editor gives me a sucess but the frame is missing...sometimes when i toggle between compression type
and 16/32 bit i works. This is just a mess...please fix!

[JimStar]

Batchrendering is still a lottery if its getting stuck or not.

One important thing I need to know: does this batchrendering issue only happen for you in Maya 2019?

[JimStar]

I can't reproduce anything of it... Could you please elaborate some more?.. The scene and the exact step-by-step reproduce description would be appreciated: sometimes some things you had done before look not important for you, but they may be the reason you get this issue while I have everything working OK on my side...

[calus]

I can't reproduce anything of it... Could you please elaborate some more?.. The scene and the exact step-by-step reproduce description would be appreciated: sometimes some things you had done before look not important for you, but they may be the reason you get this issue while I have everything working OK on my side...

To reproduce (partially) the file format bug, just switch to another renderer and come back to Octane :
for example if you use EXR in octane, switch to software render, come back to Octane the image format is now IFF...
if you switch from Octane to Arnold or Redshift, when coming back to Octane, the image is always changed to alias PIX.
I think this happen with all Octane plugin version, and locking the image format doesn't solve the issue as it brakes the UI of the common tab.

On the other side this problem doesn't occur when switching to Vray and back to Octane...

[calus]

There's a problem with Octane Cryptomatte pass in Maya :

- EXR with Cryptomatte layers produced by the Maya plugin crash the Cryptomatte plugin in Blackmagic Fusion 9, like if the EXR was corrupted or with wrong metadata.
- While if I export the same scene to ORBX and render the EXR from standalone there's no issue and the cryptomatte layers and labels are as expected.

Please check the attached sample files:

cryptoTest.zip

(4.16 MiB) Downloaded 268 times

https://www.blackmagicdesign.com/fr/products/fusion/
https://github.com/Psyop/Cryptomatte/tree/master/fusion


_

[Jolbertoquini]

Hi Jim,

Ornatrix is not correct I think you didn't understood the all purpose of the "Viewport count Fraction" this is NOT for rendering is only for preview in Maya (the name says Viewport) but render engine (Octane) should follow only "Render Count".

What you have set is completely point less and was the same as before is actually a mistake. If you check Arnold, Vray, Redshift and maxwell, you can see the support you have set is all wrong, and also "I point out the last time" no changes???.

maybe you did something else to actually work? or a option in Particular? Do you mind to let us know how to use this feature then?

Cheers,
JO

[Maskeline]

A problem that is giving me pain.
When you animate the "power" value of a black body emission, the maya slows down a lot ... If you have several objects with light emitters that have different animations, it is practically impossible to work.
When you export this maya scene with animated emitters to octane standalone it sometimes works, other (randomly) is not animated. Also the export is tremendously slow.
In Maya 2018 with octane 4.02 there is the same problem

[JimStar]

Maskeline
If I understood correctly - you can see a clear difference before just one "power" attribute gets animated and after... Could you please PM me the scene where you get this issue? I'll have a look on Monday...

[Joss]

I don't have any subscriptions, I have a permanent license, what's I'm supposed to download?
Can you guys put some information about licensing into FAQ, there's none now.