Array Attr inside a Compound are not evaluated : Maya 2018 Update 4

Array Attr inside a Compound are not evaluated : Maya 2018 Update 4

ACOLTEL
Contributor Contributor
3,784 Views
14 Replies
Message 1 of 15

Array Attr inside a Compound are not evaluated : Maya 2018 Update 4

ACOLTEL
Contributor
Contributor

Hello,

I'm testing the Update 4 of Maya 2018 and I noticed a bug.

when we have a custom node with an Array inside a Compound, the value a the attr is not transferred anymore when we connect it to another node.

 

I my case, it's a node holding our export parameters and the array contains the threshold values of our LOD.

I reproduced the issue on a simpler node. I toke a sample node from the DevKit (circleNode.py) and just added an Array inside a Compound. For the example, I connected the array to the radius of a Polysphere.

Everything is Ok with the Update 3 and previous versions of Maya.

With the Update 4, we can see that the Attr is not affecting the value of the radius (see the screenshot in attachment).

 

I can avoid this problem by changing the structure of my nodes but to me, it looks like a major issue for the Update 4.

 

 

0 Likes
Accepted solutions (1)
3,785 Views
14 Replies
Replies (14)
Message 2 of 15

cheng_xi_li
Autodesk Support
Autodesk Support

Hi,

 

I could reproduce this problem. It looks a major issue. I am asking our engineers about it(e.g. if there are any undocumented changes related to this one). I'll be back once I've got feedbacks from our engineers.

 

Yours,

Li

Message 3 of 15

cheng_xi_li
Autodesk Support
Autodesk Support

Hi,

 

Our engineers thought it is a defect too. They will work on it.

 

Yous,

Li

0 Likes
Message 4 of 15

ACOLTEL
Contributor
Contributor

Hi,

If it is confirmed as a defect, I will advice my users to not install the update 4 for now on.

Thank you for investigating this issus,

Anthony

0 Likes
Message 5 of 15

BigRoy
Advocate
Advocate

We are hitting the exact same issue and are considering this a major/urgent defect. Did you happen to have a defect number from Autodesk Support?

 

This issue also caused problems with Houdini Engine, see: https://www.sidefx.com/forum/topic/57616/
Likely for their plug-in it is also a major issue.

0 Likes
Message 6 of 15

BigRoy
Advocate
Advocate

Reported this too, it's Case ID: 14610096 Array Attr inside a Compound are not evaluated : Maya 2018 Update 4

0 Likes
Message 7 of 15

Anonymous
Not applicable

It seems like this is the reason that some connections can't be made to MASH array attributes. The documentation describes such connections however they are not possible in 2018.3 or 2018.4. 

 

 

0 Likes
Message 8 of 15

BigRoy
Advocate
Advocate

That could be from the same problem - but I think this issue wasn't in 2018 Update 3.

 

Are you able to link the example from the documentation that fails to work for you? Having it linked here might help the developers to test whether any fix they do solves that problem - or if it is not the same bug it might help others to aid you on how to do it in a different manner.

0 Likes
Message 9 of 15

ACOLTEL
Contributor
Contributor

Hello,

my Case Id is : 14615312

according to the support, the defect is still under investigation

 

0 Likes
Message 10 of 15

Anonymous
Not applicable

Hi,

 

any news for this bug? You can see in the attached file, MASH is supposed to drive the curvature of the bend deformer connected to the cube. (rot.x of the breakout connected to the bend1handleshape.curvature, but nothing appens. The same scene in maya2017.update5 works fine. (also attached). I just noticed in Maya 2017 if you double clic on bend1HandleShape (Attribute editor/MASH1_Breakout/Connected Nodes windows), the MASH1 signal will show up. But in Maya 2018, the same double clic will open the bend1HandleShape. I don't know if it's a lead?...

 

Best regards,

 

Christophe

0 Likes
Message 11 of 15

shaik.sadiq
Autodesk
Autodesk

Hello @Anonymous This currently being aimed in the next Major release of MAYA.

Message 12 of 15

BurkhardRammner
Collaborator
Collaborator

Sooo...this bug is known at least since august 29.

And I would say its a major bug.

May I add that I have a tight deadline and that, until I realized the weird behavior I got was not my fault it may be now to late to meet that date?

Actually I expect an update to fix things, not to produce new bugs. Thats why I installed update 4.

Normally I never complain about software problems, but in this case it will hurt me hard...

So, sorry for that post...

Message 13 of 15

petr_zloty
Contributor
Contributor

Has it been fixed in 2018.5 release?

0 Likes
Message 14 of 15

cheng_xi_li
Autodesk Support
Autodesk Support
Accepted solution

Yes, this issue has been fixed.

 

Yours,

Li

Message 15 of 15

ACOLTEL
Contributor
Contributor

Hi,

I tested the Update 5 few hours this morning and I confirme that the issue seems to be fixed.

It's a good news!

Next week, I will continu to test more intensively the Update 5 to determine if it's ready for production.

 

Thanks for the BugFix.