-
Notifications
You must be signed in to change notification settings - Fork 201
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
Prim parenting issues since maya-usd 0.23 #3237
Comments
Hi @jufrantz , |
Hello @santosd. Good to know. Thank you for the information and for testing this case. We'll try 0.24 soon. A bit unrelated, but to anticipate the way we would deploy next version : maya-usd 0.24 dropped support for Maya 2020. Is it the case even if we build maya-usd from sources. Or does it only mean that the prebuilt release packages are no longer targeting 2020 ? Sorry if I missed this information elsewhere. Thank you once again, |
You should be able to build your own 0.24 targeting Maya 2020 as support for it was removed after we released 0.24. Future releases will require at least Maya 2022. Sean |
I will go ahead and close this out since the issue is no longer in 0.24.0, but if you have any further questions on this feel free to reply and reopen or if a new issue comes up feel free to log it. |
Describe the bug
We encounter issues while parenting multiple prims with USD references. It seems to be a regression between maya-usd 0.22 and 0.23.
Also, very similar problems occur with group command /
Ctlr+G
. I can file another issue if needed.Steps to reproduce
In attached maya-usd-23_parenting_issues.zip, open maya scene
scene.ma
.scene.ma
contains amayaUsdProxyShape
created fromscene.usd
layer.scene.usd
defines a simple hierarchy with multiple references toasset.usd
.Select ufe items in this order
/World/Group1/Asset1
and/World/Group1/Asset2
(both referencingasset.usd
) and/World/Group2
(the wanted parent).Click on menu
Edit/Parent
or use shortcutP
Notice that
Group1
andWorld
to see the new parenting.Asset2
was not parented, parent action was only applied to first selected primAsset1
.undo
will issue this errorSpecs (if applicable):
The text was updated successfully, but these errors were encountered: