-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MAYA-114041 - As a user, I'd like my pulled Maya object to inherit visibility #2964
Conversation
// Remember the path for which we are accumulating the callbacks | ||
MDagPath ancestorPath; | ||
MDagPath::getAPathTo(obj, ancestorPath); | ||
_ancestorCallbacksPath = ancestorPath.fullPathName(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What will happen if the proxy shape node is renamed? Or any of its ancestors are renamed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just tested: renaming proxy shape node or any of its DAG ancestors works fine, as in this case we call updateAncestorCallbacks on the next dirty callback. However, after renaming a USD ancestor of a pulled node we loose the connection inside ProxyAcessors and this is a general problem that exists for all proxy accessors, including relaying the 3d transform. I think we may need to create a Jira ticket for that one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about the behaviour when nodes are renamed.
…validation - Fixing proxy accessor autotests by doing strict filtering of dirty plugs.
- Fixing build for older Mayas
Add a custom attribute "combinedVisibility" to proxy accessors to output combined visibility to maya pulled prims