OctaneRender for Maya 2019.2xb3-16.0 [OBSOLETE]

[JimStar]

Forum rules:
NOTE: The software in this forum thread is not 100% reliable, this is a development build and is meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release.

!!! THIS IS THE BETA VERSION OF OctaneRender PLUGIN, IT IS RELEASED FOR INITIAL BUG HUNTING ONLY !!!
!!! PLEASE DON'T USE IT FOR PRODUCTION & DON'T SAVE THE SCENES FROM THIS BETA VERSION FOR FUTURE USE AS THERE ARE HIGH CHANCES TO LOSE THEM !!!
!!! SCENES SAVED IN THIS BETA VERSION ARE NOT GUARANTEED TO WORK IN SUBSEQUENT VERSIONS !!!
!!! THE RENDER ENGINE IS YET TO BE STABLE, SOME CRASHES & BUGS ARE EXPECTED FOR THIS TEST VERSION OF THE PLUGIN !!!


Otoy® is proud to announce the availability of a new test version of OctaneRender™ for Maya® Version 2019.2
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 387 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 2019.2 are here:
OctaneRender Standalone 2019.2


Changes since versions 15.X:

• Integrated the 2019.2 XB3 rendering engine.

KNOWN ISSUES:

• The Octane SDK 2019.2 XB3 is only released for Windows, so - no other OSes supported by this plugin release.
• Possible "CUDA error 700", crashes and freezes: these are the rendering-engine bugs. Wait for the more stable Octane SDK to be released if you get annoyed with them.
• Broken render result when up-sampling is enabled and the render-width requested is not a multiplier of up-sampling value selected. This is the rendering-engine bug.
• Due to some inconsistency on the rendering engine level the builtin-scriptgraph nodes are not going to be present in the plugin. At least at this stage.

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

OctaneRender for Maya Studio [Windows]


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

OctaneRender for Maya Enterprise [Windows]


=================================
Downloads for users with a regular V4 license
=================================

OctaneRender for Maya [Windows]

[Rikk The Gaijin]

I've been waiting for this, thanks, I'm gonna give it a spin.

[Braca]

Weird thing, getting exact same results with RTX ON and OFF. Running it on RTX 2080Ti

[Rikk The Gaijin]

This version is basically unusable. If I try to load ANY of my scenes saved with Octane 2018, none of it works. I don't see any material preview in the viewport, and if I try to render, nothing gets rendered. It looks like it's completely incompatible with 2018 assets.

[Jolbertoquini]

Hi Jim,

Thanks I need give some test, just one quick thing this the XB"2" right not XB "3" cause XB3 is not release for beta yet.

Cheers,
JO

[Jolbertoquini]

Hi Jim,

what is the procedure to add shader on xgen hairs?? is working really well load and etc, but I can add shader I'm connecting on the "transform" node at Octane hair material but is ignore completely any advise?

Cheers,
JO

[hgarrou]

I'm getting the same results as Rikk The Gaijin above.
I have no visual result from ipr or viewport using the Octane XB3 plugin.

FYI
I Tried with the XB2 standalone installed since this is the most recent one available for download.
Perhaps the XB3 plugin works when XB3 standalone is installed.

Thanks again for all your hard work.

[Jolbertoquini]

Hi Jim,

One other bug displacement vertex is crashing Maya when connected to the shader. on a particular scene here while I replace the older displacement node. please find scene attached

best,
JO

[JimStar]

I'm getting the same results as Rikk The Gaijin above.
I have no visual result from ipr or viewport using the Octane XB3 plugin.

FYI
I Tried with the XB2 standalone installed since this is the most recent one available for download.
Perhaps the XB3 plugin works when XB3 standalone is installed.

Thanks again for all your hard work.

This version is fully compatible with any previous versions' scenes. If you experience some rendering errors - these are most likely the rendering-engine bugs mentioned in the "known issues" section of this beta-version description.

KNOWN ISSUES:

• The Octane SDK 2019.2 XB3 is only released for Windows, so - no other OSes supported by this plugin release.
• Possible "CUDA error 700", crashes and freezes: these are the rendering-engine bugs. Wait for the more stable Octane SDK to be released if you get annoyed with them.
• Broken render result when up-sampling is enabled and the render-width requested is not a multiplier of up-sampling value selected. This is the rendering-engine bug.
• Due to some inconsistency on the rendering engine level the builtin-scriptgraph nodes are not going to be present in the plugin. At least at this stage.

Could you please share some scene with me where you have this issue?
And please describe exactly what is happening on your machine: how do you start the rendering, what do you see in the render result, attach here the content of the messages-output in the Script Editor, etc... Maybe some screenshots...
Please switch on the "Verbose mode" in Octane globals before testing - to have more output in the Script Editor from Octane.

Jolbertoquini
The crashes and CUDA errors are completely expectable with this beta - as mentioned in the description, these are the rendering-engine bugs that should be fixed in later beta-SDK versions... I've already reported many of them to the engine team.
The crashes may behave differently on different machines - e.g. your scene renders OK and does not crash on mine...

And yes, this is an XB3 version: the XB3 SDK is already released while the XB3 standalone is still in development...

[BK]

This version is basically unusable. If I try to load ANY of my scenes saved with Octane 2018, none of it works. I don't see any material preview in the viewport, and if I try to render, nothing gets rendered. It looks like it's completely incompatible with 2018 assets.

Hi Rikk,

Thank you for reporting this. Could you please check the error message from the Script editor?
The material preview issue could be related to a known CUDA 700 error.


cheers