OctaneRender® for Maya® 3.06 - 10.19 [OBSOLETE]

[gah5118]

you sir, have restored hope in this plugin.

Now, I'll wait to see it.


On a side note.... when dev of this happens, one issue with the previous "preview", there was a nasty amount of nodes that were created by maya or the plugin. It took an unnecessary amount of time to strip the nodes out. I suppose however, this may already be remedied by the "expand/collapse" items. Furthermore, It used to create an object node for every object in the scene.... my scenes have between 200-800 objects (fully detailed electronics). This creates a massive mess and is very unusable. there should be the option to translate as alembic nodes.

The best way I can explain this is our current process. For each major assembly, we export an alembic file. so if there are 3 major assemblies (monitor, desktop, keyboard for example) it would be 3 nodes. we connect them to a geometry group node and then to the render target. The alembic nodes are grouped to keep things tidy. The camera is exported as it's own node for easy updating without worrying about the rest of the geometry. This helps to keep things very organized and when a specific part of an assembly is updated, we are only having to be concerned about that group being exported.

another side note regarding expand/collapse, I just tried it with a material node... when i hit collapse... the entire node evaporated. bug?

[dsyee]

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...

Totally agree with you. The lack of communication and feedback on specifics is inexcusable. Seriously, how hard is it to actually list what has changed, instead of lazily copy/pasting "Minor fixes and improvements"? Most questions, some of them very important, are ignored. Most feature requests from users are ignored. The plugin continues to be buggy and unstable, missing key features, and having things added in a half-baked, buggy/difficult to use way that aren't requested. The last "Weekly Dev Update" was a month ago, and they never had anywhere close to an adequate amount of information, anyway. It's been a year since standalone v3 was released and there STILL isn't a fully-functional Maya version, despite the fact that the main page literally says "Fully Integrated Plugin" and charges full price for what's basically a half-finished, beta product.

I've been a customer since the 1.x days, upgraded to v2 and had to wait months before the Maya plug-in supported it, and now I cannot justify spending any more money to upgrade to v3 unless things really turn around in a big way. So many broken promises and mind-boggling decisions made with this product, I'm surprised anyone has stuck around with it for so long.

[haze]

another side note regarding expand/collapse, I just tried it with a material node... when i hit collapse... the entire node evaporated. bug?

Was the material node connected to some geometry? When collapsing unconnected nodes, they get deleted by default at the moment

[Goldorak]

Expanding the Maya team towards parity with the V3 Max team is our highest priority, full stop.

A prior roadblock - exposing the full V3 node system (where needed) to Maya - may be resolved through the 3.07 plug-in API's new node editting features. We plan to use this API to support cross-app ORBX intergation channels coming up in 3.x, such as univeral ORBX import across 3.07+ plug-ins (we'll have a better sense of how well this works beyond just SU and Unity in the coming weeks).

[calus]

Expanding the Maya team towards parity with the V3 Max team is our highest priority, full stop.

Just a reminder for the detailed questions on the same subject, waiting here : viewtopic.php?f=28&t=57370&start=20#p312105
and here : viewtopic.php?f=9&t=57250&start=30#p311831

[dsyee]

Thanks for the response, Goldorak, it's appreciated. I suppose we will have to wait to see if things work out as promised this time.

[renmaxhb]

Material lost textures allways when open a maya scence, the poly is defaut material, must click the texture reload button every time.

[itsallgoode9]

this version SHOULD NOT be labeled as "stable". This material but has been affecting every one of my scene as well. Manually hitting reload on tens or hundreds of textures is not a solution.

[BK]

must click the texture reload button every time

hi renmaxhb,

thanks for reporting on this issue. It is already on our bug tracking system and we will get it fixed in the next build. sorry for the inconvenience.

[itsallgoode9]

must click the texture reload button every time

hi renmaxhb,

thanks for reporting on this issue. It is already on our bug tracking system and we will get it fixed in the next build. sorry for the inconvenience.

Unless a build is getting released tomorrow, this version needs to be taken down ASAP. this is not a minor bug, like you guys seems to be treating it. This is flat out a scene breaking bug.