-
Notifications
You must be signed in to change notification settings - Fork 57
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
Animated transforms not properly backed to its own xform prim path when exporting to USD #1642
Comments
Issue synced internally to ARNOLD-14016 |
If I understand well, you're using the Arnold-USD export from Maya ? That's one of the reasons why you should instead use the MayaUSD export with the "Arnold" plugin configuration enabled. This will let mayaUSD export the generic maya data, including transforms, meshes, etc... and arnold will just add its additional data on top of it |
Thank you for your rely, I have tried this method later, but when I import a scene using MayaUSD export with Arnold plugin and read in Katana, Katana UsdIn or AnorldIn node still have problems and can't get the correct result. |
ok, which problem did you have exactly with the mayaUSD way ? That would be something we want to fix. |
@frankchen211 are you able to still provide more information regarding the issue you faced with a Maya-USD export instead? Otherwise this issue will remain lingering. |
Describe the bug
If we have animation on parent xforms, but no visible meshes under the parent transfrom node, those transfrom node won't be write to usd xform prim, or instead all animation xfrom data are baked to mesh.
We would like to reference or add more assets into that parent xform to share the animation based on the expored usd stage, but how to do that if animation is not recored in the correct prim path?
The text was updated successfully, but these errors were encountered: