OTOY Forums

Maya 3.03.2-8.02_Demo Plugin not work
You mentioned that you're using new octane with titan
and its ok . I cant even load that plugin with same gtx titan
some people refering that to compute capability , but I dont think that's an issue here.
Frankly , I dont even know what it might be ,
here is my stats :
Maya 2017
GTX titan (Not black) - latest 372.70 Drivers
Octane standalone demo 3.03.03 and OctaneRender_for_Maya_3.03.2_-_8.02_Demo Plugin

Standalone workks well , but maya pluging gives me this :

// Error: line 1: Unable to dynamically load : C:/Program Files/Autodesk/Maya2017/bin/plug-ins/OctanePlugin.mll
The specified procedure could not be found.
//
// Error: line 1: The specified procedure could not be found.
(OctanePlugin) //

you also said that it might be experimental pascal issue
but as you see its not
hope you can help ,
best regards

So, It is almost October ... if you lost your track of time....

Because of the v3 plugin overhaul being a much bigger task than we anticipated, we redirected resources to upgrading the V2 plugin for Maya 2017, and unfortunately a lot has changed in Maya 2017. We even had to submit an issue to Autodesk. We are now working through feedback from internal testing and hope to release it shortly.

Well, at least Next Limit is releasing Maxwell Render V4, with GPU rendering by the end of the month.

Well.
To be honest i think new devs more like need some support, and not a non-stop bashing.
Developing plug-in from scratch is really not a simple task, especially taking into account, how many technologies involved at once: Maya API, Octane API, shading languages, realtime shaders for Maya, and easily dozen of others.

And while company itself could bring some apologies for the way V3 Maya connection was "released"(i wouldn't actually mind to have a 2nd license for waiting), still - it's not a new devs fault in any way. And these guys actually trying to bring you better quality plug-in.
Prev. plug-in has been in development for how long...2? 3 years?
And new guys had just 2 or 3 months.
So, hold your horses a bit?

PS: You really might wanna read somewhere on how first version of Maxwell was delivered. In short words - it was a nightmare:
they've collected money from all the beta customers, then in the middle of the development they've decided to totally rewrite the engine since they wasn't able find the way to solve famous "fireflies problem", and with that rewrite they've lost that magic "photoreal" look they had with the first beta.
And after that i completely lost any interest to that render, but still: then they've made a "closed beta group" within beta testers group(who are actually paid money to be beta-testers, ok?), missed every possible deadline by at least a few months, and then released half-done renderer that was almost impossible to use.
As a compensation they gave me 8 licenses of half-done renderer.
Cool, isn't it?
Maxwell became more of less usable just to V2, and guess what: it wasn't a free upgrade. TA-DAA!
Yes, i'm ex-Maxwell customer as well(and i believe few more people on these forums too).
Exactly the same story happened to the FryRender.

PPS: I'm not affiliated with Otoy in any way, i just don't like when crowd bashing ppl, who are actually didn't deserve that.

PPPS: Sorry, sometimes i'm being too straightforward.

Joss wrote:Well.
To be honest i think new devs more like need some support, and not a non-stop bashing.
Developing plug-in from scratch is really not a simple task, especially taking into account, how many technologies involved at once: Maya API, Octane API, shading languages, realtime shaders for Maya, and easily dozen of others.

And while company itself could bring some apologies for the way V3 Maya connection was "released"(i wouldn't actually mind to have a 2nd license for waiting), still - it's not a new devs fault in any way. And these guys actually trying to bring you better quality plug-in.
Prev. plug-in has been in development for how long...2? 3 years?
And new guys had just 2 or 3 months.
So, hold your horses a bit?

PS: You really might wanna read somewhere on how first version of Maxwell was delivered. In short words - it was a nightmare:
they've collected money from all the beta customers, then in the middle of the development they've decided to totally rewrite the engine since they wasn't able find the way to solve famous "fireflies problem", and with that rewrite they've lost that magic "photoreal" look they had with the first beta.
And after that i completely lost any interest to that render, but still: then they've made a "closed beta group" within beta testers group(who are actually paid money to be beta-testers, ok?), missed every possible deadline by at least a few months, and then released half-done renderer that was almost impossible to use.
As a compensation they gave me 8 licenses of half-done renderer.
Cool, isn't it?
Maxwell became more of less usable just to V2, and guess what: it wasn't a free upgrade. TA-DAA!
Yes, i'm ex-Maxwell customer as well(and i believe few more people on these forums too).
Exactly the same story happened to the FryRender.

PPS: I'm not affiliated with Otoy in any way, i just don't like when crowd bashing ppl, who are actually didn't deserve that.

PPPS: Sorry, sometimes i'm being too straightforward.

Thanks for the history lesson buddy, I've used Maxwell Render since v1.2. Otoy is not handling this situation well. We haven't even had support for v2 since April. Even in the standalone, they didn't release most of the features they originally promised and instead went talking about V4 release even before V3 was fully out.

I agree.
But i think it's more question to management, not Maya devs.
Personally i'm still waiting for Octane for Maya to be usable.

Not a biggie tho, since i'm using MtoA meanwhile anyways

I'm just really frustrated because I want to continue to use Octane render but Otoy is making it very difficult to justify waiting around any longer and giving them any more money. I know it's not the dev's fault specifically and is more Otoy's fault.