OTOY Forums

Forum rules:
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.

!!! 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 LOSING 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 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, 2016.5, 2017 and 2018 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 2018.1 are here:
OctaneRender Standalone 2018.1 RC1


Changes since version 14.7:

• Implemented the "selected GPUs" logging for verbose mode.
• Implemented the option to skip saving the beauty pass ("additional" section in Octane global settings).
• Minor auto-conversion improvements.

Windows DOWNLOAD
OctaneRender for Maya 2018.1rc1-14.8 BETA

Linux DOWNLOAD
OctaneRender for Maya 2018.1rc1-14.8 BETA


MacOS DOWNLOAD
OctaneRender for Maya 2018.1rc1-14.8 BETA


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

OctaneRender for Maya Studio 2018.1rc1-14.8 BETA [Windows]

OctaneRender for Maya Studio 2018.1rc1-14.8 BETA [Linux]

OctaneRender for Maya Studio 2018.1rc1-14.8 BETA [MacOS]

Hi Jim,

Here my scene from Maya Plug and exported to Standalone (thanks Pascal to point out the wrong name on the projection node) As you can see there is a difference on the result.
With VDB "SDF" meshs please let me know more about it if anything set wrong. (Scene size is correct, based on Maya settings, and set scene scale at "1" is not solution and doesn't work aswel)

Cheers,
JO

Jolbertoquini
This is the OctaneRender RC1 engine bug, not a plugin's issue. Must be fixed in the next engine version...

JimStar wrote:Jolbertoquini
This is the OctaneRender RC1 engine bug, not a plugin's issue. Must be fixed in the next engine version...

Hi Jim,

Haze just explained me on the dev forum, Thanks for reply I need text but I realize some settings still not translated right on export like radius on AO and other settings. I can try to spot then precisely for help to get fix.

Cheers,
JO

Dear Jim

Thank you for the great updates so far. We would like to express our observation regarding another "Reference Issue".
This time we couldn`t really pinpoint the exact node which holds this issue. But we have some hunches.
The issue is that sometimes scenes which has references inside crash when loaded into a freshly opened maya.
Our solution is that, if we open up another octane scene which has no reference inside.
Then open the scene with the reference.
The maya is stable.

Most of the times the problematic scenes have parenting of referenced objects inside. But that is not always the case, and even scenes without parenting can cause this error.

Would be great if in any case the files would open without errors when we start the Maya.


Another Big Bug what we seen is that referenced objects materials don`t load in the texture.
First it seemd like the issue is with the texture/material names being the same. But this didn`t solved all the cases.
Also it seems some times Destroying and recreating the OctaneImageTexture and similar nodes solves the issue.. But this only works half of the times or less.
In any case it shows up in a way that when we open a scene, the material greys out in the viewport. Reloading the reference solves the problem. But its never known if the batch render renders it normally or loses the texture.
(Also Reloading the Textures Separately works too.)

Also another important thing. When we reference an object which is utilizing the Same OctaneTexture node for 2 materials usually makes one of the material not loading the texture properly.

Can you look into the matters?

Thank You!

Dennyuel wrote:Can you look into the matters?

Yes if you will stop ignoring my questions about the scene where you have the issues and the step-by-step reproduce-sequence description... The vague stories can't help with pinpointing the source of your problems...