OTOY Forums

Hi everyone,

My name is Bikram, I am a seasoned Maya generalist and long time Maya user, and I am excited to join the Octane Maya dev team. I will be handling communication going forward on the weekly roadmap and will be responsible for ingesting user feedback on behalf of the devs. I'm looking forward to working with you to ensure your expectations are met. I will also assist with general support queries, and will be on these forums daily to answer questions, and assist where I can.

To kick things off, here is our first weekly development update:

Maya plugin version 2.26 will support Maya 2016.5 & 2017, with pascal GPU support.

We are also prioritizing plugin feature support for 3.04.3, and will be preparing a new release in the coming weeks which exposes all V3 functionality through high-level UI that is artist friendly. This will get 3.0 out of beta and production ready as soon as possible.

I am keen to hear any suggestions and criticisms.


Kind Regards

Welcome Bikram,
we are happy that you are on board.
Ciao
Nando

Welcome Bikram

Welcome Bikram! Glad to have more help on the Maya plugin!

Hi Bikram,
so I'm the first to shoot questions.


About the coming V3 beta:

I guess you're involved in this development, testing and giving feedback to developers,
while we are waiting for a release, can you tell us more about your impressions as a user with this current development ?


About the new 2.26.1_7.20.1 release :

Thanks to Jimstar there's also bugfixes in this release.
Will there be another release following with more bugfixes ?

If yes, I have some suggestions.

Easy fixes :
- z-depth pass is broken since 7.19, the "z-depth max" setting is not considered. ( z-depth still works in info kernel)
- Each time a transform is animated, keys are also created on the octMaterialR, octMaterialG and octMaterialB attributes.
This causes all kinds of troubles in Maya even if not using Octane, e.g. viewtopic.php?f=110&t=56652
These attributes must be set non-animatable when Octane create them.
- Octane Projection nodes don't respect "coordinate space", they always use "world space" even if "object space" is selected.
- Octane constant topology attribute should be on by default not off.

Major bugs :
- Internal motion-blur is deactivated on hairs,
(might be an easy fix if hair is only missing internally the "constant topology" tag set to on)
- broken animated particle/instancer,
motion blur crash maya instantly (no crash in 7.6 with legacy particles but MB was wrong anyway),
exportation is very wrong (duplicating every instance every frame),
particle/instance ids are mixed-up with time (random color node change colors every frame).
- The File attribute in imageTexture nodes doesn't work with most of the Maya builtin file-path functionalities,
to make it work: http://around-the-corner.typepad.com/ad ... chive.html

Hello,


Thank you, everyone, for your warm welcome

I am very excited to be a team member in OTOY.

Looking forward to hearing from everyone.


Regards

Hi, Brikam. Welcome!

Lately I'm not as active with Octane, but my suggestions and wishes were:
viewtopic.php?f=109&t=55117&start=40#p282177 (UI, cold start to render and usual setup)
viewtopic.php?p=279066#p279066 (attribute spread sheet)
viewtopic.php?f=28&t=53709&p=276279#p276279 (maya triangulation, compatibility of Octane material blind data, viewport 2.0 preview)
viewtopic.php?f=111&t=54008
Additionally, a built in roughness/metalness-to-Octane node or utility to take advantage of the crescent availability of that kind of PBR libraries and workflows.
I didn't mistake you for Santa Claus , I'm just casually dropping my wishlist that was already lying unseen .

The first and last wish of us all has come true (or so it seems): open communication. I don't thing you need to worry: we are a calm bunch that can workaround many bugs or missing features just fine. Octane itself is already very useful if the basic functionality is in place. Being misguided or left in the dark were the biggest issues.

calus wrote: About the coming V3 beta:

I guess you're involved in this development, testing and giving feedback to developers,
while we are waiting for a release, can you tell us more about your impressions as a user with this current development ?


About the new 2.26.1_7.20.1 release :

Thanks to Jimstar there's also bugfixes in this release.
Will there be another release following with more bugfixes ?

If yes, I have some suggestions.

Easy fixes :
- z-depth pass is broken since 7.19, the "z-depth max" setting is not considered. ( z-depth still works in info kernel)
- Each time a transform is animated, keys are also created on the octMaterialR, octMaterialG and octMaterialB attributes.
This causes all kinds of troubles in Maya even if not using Octane, e.g. viewtopic.php?f=110&t=56652
These attributes must be set non-animatable when Octane create them.
- Octane Projection nodes don't respect "coordinate space", they always use "world space" even if "object space" is selected.
- Octane constant topology attribute should be on by default not off.

Major bugs :
- Internal motion-blur is deactivated on hairs,
(might be an easy fix if hair is only missing internally the "constant topology" tag set to on)
- broken animated particle/instancer,
motion blur crash maya instantly (no crash in 7.6 with legacy particles but MB was wrong anyway),
exportation is very wrong (duplicating every instance every frame),
particle/instance ids are mixed-up with time (random color node change colors every frame).
- The File attribute in imageTexture nodes doesn't work with most of the Maya builtin file-path functionalities,
to make it work: http://around-the-corner.typepad.com/ad ... chive.html

Hi Bikram,

Welcome!, so same from us, as Calus just said, also please before release any OC3 plug please make sure we can open older scenes from the OC2 plug.
is no point to have version and we loose all older stuff, I know is something on the way.
as kai said " Had to change some scripts for the AE and its breaking the old hardcoded scripts for the old nodes, but they will be replaced in the next steps anyway"

This is really important cause we need start testing and see problem before a real release.

Also could we have a clear Roadmap of what your are doing and dates about the fixes on OC2 plug, Please??

Best,
JO

welcome aboard Bikram

so glad to see some activity in regards to Octane 3 for Maya.

look forward to the full release.

@Jolbertoquini V3 will be fully compatible with V2 from the outset - the changes you mention have been put aside in the interest of delivering v3 as fast as possible