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, 2015, 2016, 2016.5 and 2017 64-bit on Linux operating systems, and 2016, 2016.5 and 2017 64-bit on OSX operating systems (including and above 10.9).

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 Octane Render™ Standalone on your machine.

For network slave and daemon please download the Standalone installer here:
viewtopic.php?f=24&t=60772


CHANGES SINCE THE PREVIOUS VERSION

• New Engine 3.06 integrated
• Minor fixes and label change...

Windows

DOWNLOAD

OctaneRender for Maya10.19

OctaneRender for Maya DEMO 10.19


Linux

Installation:
- Just run the installer to see its command line keys.

DOWNLOAD

OctaneRender for Maya - 10.19 Linux

OctaneRender for Maya DEMO - 10.19 Linux


OSX

Installation:
- Just run the auto installer file.

DOWNLOAD

OctaneRender for Maya - 10.19 OSX

OctaneRender for Maya DEMO - 10.19 OSX

Why do we have only a SDK update release ?
are we back to the old Maya plugin development style, with zero development or information for months apart from updating the Octane SDk ?

This is becoming ridiculous, Bikram why do you make the release post instead of JimStar ?
Why can't we have any information on the road-map or what is going on with development?
And why no users are never consulted before implementing features in such an absurd way, and with absurd priorities,
we users are stuck for ever with these non-sens workflows and these half implemented unusable features in the Maya plugin.

Or did JimStar gave-up again on the Maya plugin and will only update the Octane Core SDKs like 2 years ago ?

Obviously having more than one developer working on the plugin as Otoy was hoping never hapent for some reason,
So do we have zero developer now ?


We would appreciate if Otoy for once was honest about the Maya plugin development difficulties before it's too late and users are too angry...

Hello Otoy developers. I a, agree with @calus@!!!

Maya powerful software for CGI and film production. But why octane plugin dont work correct? Z-depth dont work. Motion Blur. When in my scene more than 2 mil. polygons in render my vram load on 6-7 gb? without textures? on gtx 1080

What going is scene measures?? In scene physically correct object octane render with errors. http://joxi.ru/Y2L0EJQS9gj1o2
http://joxi.ru/brR6pWKFJ1lqpr after this change rendering correct but maybe physically dont correct?

Why after 5 years octane dont support XGEN?

Why very long render in exterior? Vray 3.5 now render more faster. But I like Octane and want continue rendering with octane.

Thanks.

yeah, this is getting bad again, for real.

No feature implementations for things that are missing in maya. Not much communication to let us know what's going on.

There are other viable options for GPU rendering out there nowadays. Sorry but if this crap keeps happening some of us are off of the Octane train.

hey guys !!!!

We plan to implement the new feature as soon as there is a stable Version. I apologize for any delays, sometimes few things takes longer than we anticipate. We truly appreciate your understanding and patience

BK wrote:hey guys !!!!

We plan to implement the new feature as soon as there is a stable Version. I apologize for any delays, sometimes few things takes longer than we anticipate. We truly appreciate your understanding and patience

Well as usual you didn't answer any questions.

Why can't we have any information on the road-map or what is going on with development?

Why users are NEVER consulted before implementing features in such an absurd way, and with absurd priorities ?
because of this we users are stuck for ever with these non-sens workflows and these half implemented unusable features in the Maya plugin.

Why is there still only one developer working only part time on the Maya plugin ?

[quote="calus"][quote="BK"]hey guys !!!!

Jim Star as left with the development of 3ds max everything began to work, we did not receive a year of steel release, some bugs.
Releases were such, added a function but the renderer did not work, the renderer could not be repaired, the fix was fixed, the textures did not work, the renderers did not fix the renderers. That's how we 3d max users suffered the whole year

I'm still on Octane 2; never upgraded. I posted last July (2016) that the 3.0 Maya plug-in release would be a nightmare and I felt sorry for early adopters. I have checked in every 3 months or so and noticed nothing's any better.

It's been 9 months - that's literally enough time to develop and release a fully-functional human being.

How you guys have not asked for your money back and moved on to better product is beyond me, but I applaud your incredible levels of patience (or willingness to get repeatedly screwed).

_Mike

mverta wrote: It's been 9 months - that's literally enough time to develop and release a fully-functional human being.

mverta wrote: How you guys have not asked for your money back and moved on to better product is beyond me, but I applaud your incredible levels of patience (or willingness to get repeatedly screwed).

To be honest the situation is a lot improved compared to 9 nine months ago,
but we were starting from so far that, well, the plugin is still in a bad shape globally, because its big flaws were never tackled.

The promised additional developer that never arrived was really needed,
the truth is that JimStar alone despite all of his efforts is just not enough to catch-up the enormous Maya plugin delay.
Ironically Octane Core development alone is still too fast for the Maya plugin to just follow its rate ...

And on top of that, there is so much development time loosed because of bad decision and absurd priorities,
this could be avoided by just asking users's input BEFORE implementing features, not once its done.
And this situation is not going to be improved as JimStar is not even reading user's feedback anymore (as he is not doing the release post anymore).

just buy more 5 lisences