OctaneRender® for Maya® 3.08.3 - 12.52 [ OBSOLETE ]

[Vyoor]

Thank you so much for the information and attaching the log file.
We have reported this issue to our developer.
Are you driving anim curve Set driven Key or any script? Could you please provide a sample scene or the steps to replicate?
It would be much faster for us to resolve.

No, it's just anim curve. I can't send the scene because of NDA, but i'll try to reproduce this issue in new one.

We have confirmed the octane material parameters issue is related to Autodesk Maya 2017 API bug and the issue doesn't happen in 2018.4 !!
Also, please try to update Maya 2017 update 5 and see if the issue still happens.
We would try to get it fixed as soon as possible. I will keep you up to date.

Our pipeline is set on 2017 so I'm stuck on this version, but i will check what's going on in the update 5.

And another thing - when using any image sequences response in maya viewports became very slow when scrolling the timeline, even if there no active render view or opened hypershade. It's happening even after "use image sequence" is unchecked. This is also happening when there are any animated parameters in materials - for example opacity or mix materal's amount.

Thanks.

Cheers!

[BK]

Ther is a bug in this version. When trying to change diffuse color from attribute editor, while running IPR, the color gets reset to previous value, so you are unable to change the color.
Changing it from Hypershade though, works. Running Maya 2018.4

Regards.

Hello Braca,

Thank you for reporting the bug. We are able to reproduce this issue and we have created a ticket on our bug tracker system to investigate.


cheers

[BK]

Hi Vyoor,

No, it's just anim curve. I can't send the scene because of NDA, but i'll try to reproduce this issue in new one.

Thank you again!! A sample file would be a great help just to double check.

Our pipeline is set on 2017 so I'm stuck on this version, but i will check what's going on in the update 5.
And another thing - when using any image sequences response in maya viewports became very slow when scrolling the timeline, even if there no active render view or opened hypershade. It's happening even after "use image sequence" is unchecked. This is also happening when there are any animated parameters in materials - for example opacity or mix materal's amount.

Our developer is investigating on this issue now and as soon as its resolved, we would try to get a build out for you ASAP.

Cheers

[Vyoor]

Our developer is investigating on this issue now and as soon as its resolved, we would try to get a build out for you ASAP.

Hi!

I've sent You PM with sample scene.


Next things:

1. Sometimes it's not possible to assign material to geometry Its happenng after copy/paste, rename, or delete materials. // Error: line 1: No object matches name: internal_standInSE //

2. "Remove unused nodes" in hyparshade is removing only octane materials. If it could clean all octane nodes like textures, etc. that it would be nice.


Sorry for this one by one reporting

[Jolbertoquini]

Hi Bikram,

I was testing this version and I find some issues with the float sliders on the shader, while I'm using IPR they don't update I have to connect a float texture to make work the slider add on the shader seems broked.

Also the Timewarp should be fix is a major issue for us cause we use in all projects here to.

Please let us know when we will have a update on this.

Cheers,
JO

[BK]

Our developer is investigating on this issue now and as soon as its resolved, we would try to get a build out for you ASAP.

Hi!

I've sent You PM with sample scene.


Next things:

1. Sometimes it's not possible to assign material to geometry Its happenng after copy/paste, rename, or delete materials. // Error: line 1: No object matches name: internal_standInSE //

2. "Remove unused nodes" in hyparshade is removing only octane materials. If it could clean all octane nodes like textures, etc. that it would be nice.


Sorry for this one by one reporting

Hi Vyoor,

Thank you so much for the sample file. We are having a look into it.

Please try using Ctrl+D for duplicating an Octane node and Copy/paste for Octane Shading Network and let us know if it still throws the same error.

We would plan to contact Autodesk developers to resolve the Remove unused nodes in hypershade as it is Maya internal functionality and Octane plugin does not participate in it.

cheers

[BK]

Hi Bikram,

I was testing this version and I find some issues with the float sliders on the shader, while I'm using IPR they don't update I have to connect a float texture to make work the slider add on the shader seems broked.

Also the Timewarp should be fix is a major issue for us cause we use in all projects here to.

Please let us know when we will have a update on this.

Cheers,
JO

Hi Jo,

Thank you for reporting this.
The Timewarp issue has been resolved with a workaround and it was confirmed that the new Maya API .

Cheers

[Braca]

The previous bug actually exist both in attribute editor and hypershade, and is not limited just to diffuse color. I am trying to change the parameter of color correction texture node bot from attribute editor and hypershade and it cannot change just resets to previous value.
I gues it is the same for all similar nodes where you can input a value.

[BK]

The previous bug actually exist both in attribute editor and hypershade, and is not limited just to diffuse color. I am trying to change the parameter of color correction texture node bot from attribute editor and hypershade and it cannot change just resets to previous value.
I gues it is the same for all similar nodes where you can input a value.

Hi Braca,

Thank you for the report. The previous bug was related to Maya API and it has been resolved.
We plan to release a new build as soon as possible.

cheers

[Braca]

Also found out that motion blur is not consistent and not working stable with meshes that are deforming in some way (wire deformer, joints, etc..), and also rendering out image sequence seems that it is failing. No images get written to disk.
This is far away from "stable" version, it would be fair to mark it as "in development" or something.


*** UPDATE

This version needs a Passes node created in render settings in order to save the file if you have "Save composite EXR" checked. Otherwise uncheck that. By doing this batch renderer is saving the files. Thanks Andre Pascal for clarifying this.