OctaneRender for Maya 4.02.1-13.36 [OBSOLETE]

[JimStar]

Otoy® is proud to announce the availability of a new OctaneRender™ for Maya® Version 4
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.

License upgrade

Unless you have a subscription license, you will have to upgrade your version 3 licenses to version 4. This upgrade is free and can be done via these 4 steps:

1. Go to https://home.otoy.com/render/octane-render/purchase/
2. Select "Upgrade" in the top menu.
3. Click on "UPGRADE NOW" next to "Upgrade existing licenses to OctaneRender 4".
4. Select the licenses you want to upgrade and confirm.

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 4.02.1 are here:
OctaneRender Standalone 4.02.1

Please read the new features implemented from Octane Standalone 4 version our blog post.


Changes since version 13.35:

• Fixed a camera mapping issue.
• Minor improvements in ORBX-proxy functionality.

Windows DOWNLOAD
OctaneRender for Maya 4.02.1-13.36
OctaneRender for Maya 4.02.1-13.36 Demo

Linux DOWNLOAD
OctaneRender for Maya 4.02.1-13.36
OctaneRender for Maya 4.02.1-13.36 Demo

MacOS DOWNLOAD
OctaneRender for Maya 4.02.1-13.36
OctaneRender for Maya 4.02.1-13.36 Demo



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

OctaneRender for Maya Studio 4.02.1-13.36 [Windows]

OctaneRender for Maya Studio 4.02.1-13.36 [Linux]

OctaneRender for Maya Studio 4.02.1-13.36 [MacOS]

[Jolbertoquini]

Hi Jim,

We are receive a lot messages for every time we render , batch render and etc...this message "ORC user subscription status could not be retrieved: The server returned a client-side error with HTTP code: 401"
I understand is due the subscription, but this OC4 is not for subscription right? so why we have this messages? or I didn't understand. we are using the normal permanent licenses.

Also before we could save with Trial which was great at studio cause animator can open and animated the files without loosing or getting bug because they don't have license why is changed that now? There is no comments on that from Jules anywhere?

We really confused with this little changes. As subscription is supposed to be linked to new version but people with the permanent should be like before right?

Anyway this was two different points, One was the Trial is changed now then before which make problems to us at the studio.
and second is this error on the normal install about subscription when we already have a "special Install file for subscription" should not be on this normal install.

Cheers,
JO

[Jolbertoquini]

Also one little bug.

If you have on the scene "denoiser passes activated" and for some reason you denoiser is off at imager, it won't save any render output , is sampling saying complete but is not saving this can be a problem in some cases and people will think doesn't work.

Cheers,
JO

[Jolbertoquini]

Hi Jim,

We are receive a lot messages for every time we render , batch render and etc...this message "ORC user subscription status could not be retrieved: The server returned a client-side error with HTTP code: 401"
I understand is due the subscription, but this OC4 is not for subscription right? so why we have this messages? or I didn't understand. we are using the normal permanent licenses.

Also before we could save with Trial which was great at studio cause animator can open and animated the files without loosing or getting bug because they don't have license why is changed that now? There is no comments on that from Jules anywhere?

We really confused with this little changes. As subscription is supposed to be linked to new version but people with the permanent should be like before right?

Anyway this was two different points, One was the Trial is changed now then before which make problems to us at the studio.
and second is this error on the normal install about subscription when we already have a "special Install file for subscription" should not be on this normal install.

Cheers,
JO

Oh.. Is about ORC subscription? I see but do we need this error appear which time we render open scene or do batchrender that should happen only when we actually use ORC?

Cheers,
JO

[Braca]

I am also confused about this new license policy. I got info from OTOY support that we should now upgrade all our permanent licenses to "OctaneRender Enterprise All-Access Annual Extension (1 Year) for 199$".
So I would need to upgrade a PERMANENT license, pay 200 USD more and only be able to have it for 1 year? This does not make any sense, please tell me that I got something wrong.
We have around 10 licenses so that would be a big expense for just a year, and then need to do it all over again next year...

[Jolbertoquini]

I am also confused about this new license policy. I got info from OTOY support that we should now upgrade all our permanent licenses to "OctaneRender Enterprise All-Access Annual Extension (1 Year) for 199$".
So I would need to upgrade a PERMANENT license, pay 200 USD more and only be able to have it for 1 year? This does not make any sense, please tell me that I got something wrong.
We have around 10 licenses so that would be a big expense for just a year, and then need to do it all over again next year...

Hi Braca,

Same here we have close to 75 licenses, But I guess is to be able to provide better support and more feature on the Future. (finger cross) , But Just a quick point Octane 4 licenses is free, you can update anytime to 4 and your permanent license is there the only need for subscription is if you use the new Octane 2018 and 2019 or more new coming. Those ones you need subscription is no permanent licenses anymore. ( a lot render engines now days is like that, I'm not a big fan but I guess is for better development ).

So this version 4.02.1 you still have access is just for the new Octane and new features on the future. I know can be confusing with all this versions. on that transition.

Cheers,
JO

[Braca]

Yeah I understand that 4 will be permanent, however 2018 is the one with the features we actually need, like round edges, procedural displacement and similar. Time to look into Blender again I guess

[calus]

Yeah I understand that 4 will be permanent, however 2018 is the one with the features we actually need, like round edges, procedural displacement and similar. Time to look into Blender again I guess

Actually these features are not in Octane 2018 but in Octane 2019.1 which doesn't have a Maya plugin yet.

[Dennyuel]

Hi Jim,

We have a common problem for a while now.
The relative file paths of our textures are randomly corrected to fix paths on saving the scene with different computers.
This entails a creation of a random locations depending where each machines project folder is.
If someone else opens the scene on another computer sometimes the texture shows incorrectly because of this.
This makes missing textures on our network render as well as it doesn't look properly in the network drive.

We don't know how to reproduce the issue specifically. As we only see this once someone else uses the file again. And it happened already on every computer in the office multiple times.
We have a hunch the loading process of the file creates it. But it is also possible the saving.

Can you look into the matter please. This is the most detailed I could explain.

In simple example:

sourceimages\texture.png

turns to ..

Q:\UserDir\ProjectDir\sourceimages\texture.png

when we reopen the scene on an other computer...

Thanks,
Dennyuel

[JimStar]

Dennyuel
Please define "turns to". Do you get this full path shown in your attribute editor of the image texture node as the filename's attribute value? Or you just get some errors while the attribute still holds the relative file path?..

I've just had a look at the image texture code - there is no place where the filename attribute would be rewritten by the plugin, the plugin never changes its value on its own.
Most likely when you experience this you just have the current workspace set to "Q:\UserDir\ProjectDir" on the computer where the scene is being opened, while the filename attribute still holds the proper relative file path (which means relative to current workspace). If the scene is an .ma file - you can open it by the text editor (before saving it) and check the exact filepath string Maya sets to this image texture's attribute.
Unfortunately your description is too vague, lacking many important little details (like this "turns to" for example, or not mentioning is the user in "Q:\UserDir\ProjectDir" the user who is opening the scene or the previous user the scene came from) - so I can't use it to understand what exactly is happening in your case...