You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have had the opportunity the past days to finally test the latest release of maya-usd with our own implementation. One of the important features for us is support for importing blendshapes. While testing I noticed some weird behavior. Hopefully, it is either a mistake by me or something that could be addressed easily.
Describe the bug
when importing an USD asset with blendshapes and then re-exporting it, the blendshapes on the re-exported asset seem incorrect (for how to create the assets see the reproduction steps below).
The starting usd asset has the following blendshape definition:
trimmed down for clarity, original file is included below as example_export.from_maya_scene.usda
Note that there are blendshapes which are correctly set up through blendShapeTargets.
When we import this asset, and re-export without changing anything, the following warning is shown in Maya:
// Error: Duplicate item '/example_export_from_maya_scene_WiggleCube/example_export_from_maya_scene_WiggleCube_LOD0/example_export_from_maya_scene_WiggleCube_LOD0' not allowed for field 'targetPaths' on </example_export_from_maya_scene_WiggleCube/example_export_from_maya_scene_WiggleCube_LOD0.skel:blendShapeTargets>
// Warning: Blendshapes were requested to be exported, but no upstream blendshapes could be found.
// Warning: Invalid prim name 'example_export_from_maya_scene:WiggleCube'
// Warning: Cannot append child 'mtl' to path ''.
// Error: Path must be an absolute path: <>
// Saving stage
And the resulting usd contains the following blendshape data:
trimmed down for clarity, original file is included below as example_export.from_usda_import.usda
Note that we now only have a single blendshape, the blendShapeTargets has not been set correctly, and the tokens in blendShapes contain two duplicate values.
I would have expected values similar to the original usda file. I am assuming there is some difference between the way blendshapes are configured upon import that causes this issue, however I have not dug into the code to confirm that.
Steps to reproduce
Creating the initial usda file
Open example.usda in Maya 2023
Select the WiggleCube transform
Export selection to usda (I set the file to be a polygonal subdivision scheme and turned on all export options, including animation data and skelroots and skinning)
The produced file is included as example_export.from_maya_scene.usda
Importing the initial usda file
Create a new scene in Maya
Press the import and select USD Import
Make sure that "Animation Data" is enabled
Select the usda file and press import
The produced scene is included as example.import_usda.ma
note: If the Shape Editor window was open, it does not update upon importing, or selecting a mesh afterwards. It has to be re-opened in order to display the newly imported blendshapes. Not sure if that's related.
Re-exporting the asset
Select the WiggleCube transform (which now has a prefix depending on the import settings).
Export selection to usda with the same settings as previously. The produced file is included as example_export.from_usda_import.usda
Note the inconsistencies in the usda file.
Expected behavior
When I import an asset with blendshapes and re-export it, the blendshapes should be exported correctly without issue.
santosd
changed the title
Importing an asset with blendshapes and then re-exporting the imported asset will not yield correct blendshapes
[EMSUSD-1712] Importing an asset with blendshapes and then re-exporting the imported asset will not yield correct blendshapes
Oct 8, 2024
@BeardedPlatypus, I tested the fix on my end and I seem to be getting the expected results now. If you are able to build the latest MayaUSD, you can test the fix yourself otherwise, the fix will be available in an upcoming release. Not the next release, but the one after that. Let me know if you have any questions.
Hi all,
I have had the opportunity the past days to finally test the latest release of maya-usd with our own implementation. One of the important features for us is support for importing blendshapes. While testing I noticed some weird behavior. Hopefully, it is either a mistake by me or something that could be addressed easily.
Describe the bug
when importing an USD asset with blendshapes and then re-exporting it, the blendshapes on the re-exported asset seem incorrect (for how to create the assets see the reproduction steps below).
The starting usd asset has the following blendshape definition:
trimmed down for clarity, original file is included below as
example_export.from_maya_scene.usda
Note that there are blendshapes which are correctly set up through
blendShapeTargets
.When we import this asset, and re-export without changing anything, the following warning is shown in Maya:
And the resulting usd contains the following blendshape data:
trimmed down for clarity, original file is included below as
example_export.from_usda_import.usda
Note that we now only have a single blendshape, the
blendShapeTargets
has not been set correctly, and the tokens inblendShapes
contain two duplicate values.I would have expected values similar to the original usda file. I am assuming there is some difference between the way blendshapes are configured upon import that causes this issue, however I have not dug into the code to confirm that.
Steps to reproduce
example.usda
in Maya 2023WiggleCube
transformThe produced file is included as
example_export.from_maya_scene.usda
The produced scene is included as
example.import_usda.ma
WiggleCube
transform (which now has a prefix depending on the import settings).example_export.from_usda_import.usda
Expected behavior
When I import an asset with blendshapes and re-export it, the blendshapes should be exported correctly without issue.
Attachments
example.ma
example_export.from_maya_scene.usda
example.import_usda.ma
example_export.from_usda_import.usda
Specs (if applicable):
Additional context
Just putting out here, but thanks again for the work you guys are putting into
maya-usd
!The text was updated successfully, but these errors were encountered: