OTOY Forums

Otoy® is proud to announce the availability of a new version of OctaneRender™ for Maya®
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 2015, 2016, 2016.5 and 2017 64-bit on MS Windows operating systems.

COMPATIBILITY AND OCTANERENDER STANDALONE REQUIREMENT

To run OctaneRender™ for Maya®, you need to also have an activated OctaneRender™ Standalone copy activated on the machine you wish to install the plugin onto.
You cannot purchase and use only the Maya plugin and use it without also owning an activated copy of OctaneRender™ Standalone on your machine.

CHANGES SINCE THE PREVIOUS VERSION

• Implemented motion blur for "Reshapable" hair nodes.

DOWNLOAD

OctaneRender for Maya 2.26.1 - 7.20.4

For network slave and daemon please download standalone installer here:
viewtopic.php?f=24&t=57368


Yours,
The OctaneRender™ Team.

per my thread on one of the earlier Maya versions that was pascal compatible, I was only seeing a 15-20% speed increase from my non Ti, non overclocked 780 to my current 1080 FTW.


since then I updated to this version..

I tested both the Ms/sec and also time to reach a set sampling level. both results were consistent in the relatively lacking speed increase. any clue about this?

Is there a test scene you could upload with a known, expected result and let me try and see if my results match?

itsallgoode9 wrote:per my thread on one of the earlier Maya versions that was pascal compatible, I was only seeing a 15-20% speed increase from my non Ti, non overclocked 780 to my current 1080 FTW.

I tested both the Ms/sec and also time to reach a set sampling level. both results were consistent in the relatively lacking speed increase. Is there a test scene you could upload with a known, expected result and let me try and see if my results match?

Wow, that doesn't seem right.

There was some problem with PMC kernel in 2.26 of octane, but that was fixed in 2.26.1. I saw your post in the octane release thread also. It seems there might be a problem with the PT kernel too.

i haven't heard anybody else mention this though, so i'm not sure what to think. maybe it was just my scene? i dunno. I tested in the "hacked" octane bench for v3 and got 137.81, so it seems my card IS functioning correctly.

itsallgoode9 wrote:i haven't heard anybody else mention this though, so i'm not sure what to think. maybe it was just my scene? i dunno. I tested in the "hacked" octane bench for v3 and got 137.81, so it seems my card IS functioning correctly.

I think also it was your scene, I saw topics for other DCC V3plugins about specific Pascal GPU issue in special cases.
If you are allowed, if you upload the ORBX and send the link privately to Abstrax or anyone from the Standalone team, it could help to debug the issue.

Thanks Jim,

For the fix

calus wrote:

itsallgoode9 wrote:i haven't heard anybody else mention this though, so i'm not sure what to think. maybe it was just my scene? i dunno. I tested in the "hacked" octane bench for v3 and got 137.81, so it seems my card IS functioning correctly.

I think also it was your scene, I saw topics for other DCC V3plugins about specific Pascal GPU issue in special cases.
If you are allowed, if you upload the ORBX and send the link privately to Abstrax or anyone from the Standalone team, it could help to debug the issue.

I will do that to make sure i'm not crazy. It was a scene with liquid in glass, with displacement on the glass with lots of caustics as well as mix materials on labels and stuff, so i'd say it's definitely not a "normal" scene. I guess first i'll try it on a simple scene to see how that looks between the two cards.

Since version 7.19, the Z-depth max attribute of the Z-depth pass is broken (has no effect).
I just found that it's not a Maya plugin problem, actually this attribute seems broken in Standalone V2.
(I checked exporting from Maya, in standalone 2.24.2 and 2.26.1 it's broken, and works in V3 )

@JimStar, I wrote somewhere that you introduced the bug in 7.19,
I can't believe I didn't noticed sooner it was an Octane core bug !
Sorry for that

What mislead me is the fact it was working in plugin 7.14 and broken in plugin 7.19.
Both versions use the 2.24.2 sdk so how is this possible ?

EDIT :
I double checked , and for other scene not coming from the Maya plugin, in Standalone 2.26.1, Z-depth max in the Z-depth pass works !!!
This is so confusing, I not sure anymore what's coming from plugin or core.

calus wrote:Since version 7.19, the Z-depth max attribute of the Z-depth pass is broken (has no effect).
I just found that it's not a Maya plugin problem, actually this attribute seems broken in Standalone V2.
(I checked exporting from Maya, in standalone 2.24.2 and 2.26.1 it's broken, and works in V3 )

@JimStar, I wrote somewhere that you introduced the bug in 7.19,
I can't believe I didn't noticed sooner it was an Octane core bug !
Sorry for that

What mislead me is the fact it was working in plugin 7.14 and broken in plugin 7.19.
Both versions use the 2.24.2 sdk so how is this possible ?

EDIT :
I double checked , and for other scene not coming from the Maya plugin, in Standalone 2.26.1, Z-depth max in the Z-depth pass works !!!
This is so confusing, I not sure anymore what's coming from plugin or core.

Hi calus,

For me is working when I have "tonemapping" activacted, and max depth is working well with no problem, also make sens to me, to use max options is because we want clamp the range if I render 32bit I get full depth all good for me...I've got any issue on that, with any version.

Best,
Jo

Hi Jim,

One bug would be great to be fix is the IES lights when I render a animation with the scene scale at "0.0100" the IES lights flicker between frames,
This is a bug for a long time now on the plug.

Best,
JO