OTOY Forums

Unless Jules just ran out of time I did not see much mention of new (3.0) features in the Maya (or Max) plugin.

Should I assume that Maya 3.0 is also May 15th or will there be a sooner release to keep up with other plugins now that GTC will be behind you all soon?

Can someone give us an update on that as I am guessing a lot of us were quietly waiting until GTC to hear and I for one am now more confused regarding the Maya plugin development schedule not less.

I try not to bitch much regarding delivery dates on the forum as I assume you are all busting your asses anyway and it will be when it will be and I know I will be pleased when it comes out... in this case I thought we would hear someone though.... throw me a bone that I can dream of.

The man reason for asking is that there is no point in upgrading to standalone 3.0 if all the slaves and plugins require the same version. I'm ready to make that step as soon as that happens... May 15th???? Sooner????


Thanks

Maya 3.0 will be shipping as close as possible to SE. There was a nig effort put into getting the plugin ready to ship with OctaneEngine support from the start.

Goldorak wrote:Maya 3.0 will be shipping as close as possible to SE. There was a nig effort put into getting the plugin ready to ship with OctaneEngine support from the start.

Well, that's not so helpful with the confusing news .
Especially "...the plugin ready to ship with OctaneEngine support from the start". Which start ?
OctaneEngine seems to stand for 2 things: the plugin friendly API refactor and the subscription-based model .
As "OctaneEngine" lay in the news "beyond version 3.1" , one could guess this "start" won't be at least after summer...
Also reading the news, one can eventually think that the subscription-based model will replace the actual plugin license model (as there is no news about plugins)

But ok, at some point, Maya plugin releases will follow closely the same Road-map as standalone, that's good news.

Goldorak wrote:Maya 3.0 will be shipping as close as possible to SE. There was a nig effort put into getting the plugin ready to ship with OctaneEngine support from the start.

I'm not wanting to moan about the Maya plugin either, but we now have another developer for Maya, which is great, but there is no sign of a V3 beta for maya, or any details of the new features (alluded to in earlier forum posts).

I also hate to keep bringing up other plugins, but C4D for example, has had a test V3 version out for 4 months. That's 4 months. Similar thing with LW. If nothing else, the users have been able to work with the developer in ironing out any bugs or issues, helping to make the final plugin more robust.

We want to try to work with you guys on the Maya plugin, but it's hard when there's nothing to gone on.

Cheers.

I forgot to mention another confusing issue in News, "OctaneRender 3 will be available May 15th at a price of $399 for existing customers,..."
Shouldn't "existing customers" be replaced by "new customers" ?

Well I guess it speaks highly of Octane that I an considering moving to Cinema just to take advantage of the Octane 3.0 plugin... but if 3.0 for Maya is now waiting for Octane engine I have to consider the switch.

I may just be barking not biting... in the hope that somehow you care about this monumental decision (for me) and you will drop everything and change your whole plan of development round and suddenly put the resources into Maya to get a 3.0 ready plugin out 4 months after Cinema's all because of one users bark about switching plugins... but really why would you. It makes no difference to you guys which plugin I use. You actually sell more plugins cause if I do switch I have to turn my Maya plugins into Cinema. There lies some of my frustration.

I will repeat myself... I know you guys are all busting your asses... the end product is great... no argument there.

Confusion: Why repeatedly delay development/release of three of the biggest market share 3d apps in the world.

Just frustrated and barking!!! Put on the noise cancelling headphones and program you asses off! I'll send caffine if it helps.

Peter

p3taoctane wrote: ...
Confusion: Why repeatedly delay development/release of three of the biggest market share 3d apps in the world.
...

Peter

Hey Peter,
On the contrary this is what the OctaneEngine API is about, this is a new API to give us sooner a better plugin with much more possibilities, maybe sooner than the C4d one...as Max, Maya and Blender should be the first certified OctaneEngine plugins.
But until this, to support the OctaneEngine API, the Maya plugin is in heavy refactoring and this takes time especially as Octane-engine API itself is still under development as I understood.
The problem is more about how things have been announced so far in the NEWS section, which is even more confusing than before about the near future of these plugins...
But no doubt Goldorak will give us soon more clues about this.

Thanks man. I liked your clarification.

I understand that API is the way to go for the future... hopefully Goldrak will alleviate my skepticism that we could be waiting over another month to see it.

Thanks

Peter

'as Max, Maya and Blender should be the first certified OctaneEngine plugins'

Sorry, can you explain what you mean?

Cheers.

Well, the mysterious feature developed by JimStar for Max, Blender and Maya was in fact the "OctaneEngine API".
For these 3 plugins (and unlike other applications) the V3 is developed using this new, better and future proof API, giving the same access as standalone to all octane features, and bringing new possibilities.

For octaneEngine details see here the slideShare slide 49 to slide 56.
Slide 51 there is a 4 mn video from OctaneEngine in the alpha octane plugin v 3.06 for Max.
https://home.otoy.com/octanerender-3-an ... ap-update/