When we import animation from a USD file, we need to have control over what’s going to be imported, because it is going to be used in later pipeline processes.
We don’t really want to rely on heuristics inside the USD plugins to decide what would be the best way to import them. That can be used with an auto flag or similar for some users. However, when we are using this processes in a pipeline production, we need control over what’s going to happen.
In the case of USD we are missing the ability that we had with the alembic import to force the creation of geometry caches.
We found that the USD import process tries to be smart about what he is creating, but it would be helpful in some situations to be able to override those decisions because we know the result we want to get.
Is there a way that we can control that process?
[Attachment Removed]
Steps to Reproduce
Import an animation from USD
Depending on a number of conditions it will create a skeletal mesh, or static mesh or a geometry cache.
[Attachment Removed]
Do you have USD files with animation without skeleton that are imported as skel animation instead of geometry caches?
Could you detail the expected output:
As far as I understand, alembic file contains static mesh and cache animation but no skeleton or skin information
If a USD contains a mesh with time sampled vertices position we could expend the importer to do like the alembic importer and either just import the mesh, or make a geometry cache as it is done now, or force it to make a simple skeleton with curves controlling morph targets.
However if the USD contains a skeletal mesh with skin data, what is the expected behavior? Alembic files do not contains this kind of information so there is no conversion of skeletal mesh bone animation or morph animation to a geometry cache.
Do you have C++ dev in your team?
[Attachment Removed]
Hello Flavien!
Maybe I’m doing something wrong and missing something. I export an animated mesh into USD without skeleton, but when I import it in Unreal I don’t have a way to force creating a Geometry Cache asset, so sometimes (I haven’t investigated in which situations) it creates a skeletal mesh with a skeleton even though there was not a Skel in the usd file.
Maybe there is a way to export the geometry into USD that makes the importer always create a geometry cache that I have missed.
It would be ok if the usd contains a skeletal mesh it imports a skeletal mesh, but if it doesn’t contain a skeleton it doesn’t create one to “simulate” a skeletal mesh and instead create a geometry cache, but I couldn’t find a reliable way to do that.
Thanks!
[Attachment Removed]
Hello Diego, is it a USD you generated yourself? Did you get it from a DCC? which one? How do you build you animation?
Would you be able to share one of the USD file with us, I can share a space on a box folder.
Bests,
Flavien.
[Attachment Removed]
It was created from maya exporting a character rigged with the custom rigging system that we have at the studio.
I’ll try to build something that I can share when I get some time that can reproduce the problem.
Thanks a lot!
[Attachment Removed]
Hello Diego, just following up to check if you would have a sample data for us to test.
Bests.
[Attachment Removed]