Export Workflow Improvements #31
Replies: 2 comments 2 replies
-
|
Yea we could probably add some bulk export functionality. Like a list of actions or something. For the body, it shouldn't matter since the MetaHuman in Unreal should have a post-process blueprint that will be evaluating the RBFs after the animation keys are applied. I guess currently the exporter should either prune those bone curves from the animations, or there be a setting to bake the evaluated values. (This might be something we add later) However to answer your question now, you shouldn't need the RBFs evaluating for exporting your animations if you are importing your animations onto a normal MetaHuman with a post process animation BP enabled. |
Beta Was this translation helpful? Give feedback.
-
|
If anyone else is having issues exporting animations (my FBX was exporting as an empty file), here's what worked for me. I imported the original MetaHuman rig and used a simple Python script (generated with ChatGPT) that adds Copy Location and Copy Rotation constraints from the original MetaHuman skeleton to my target skeleton. I definitely wasn't going to add all those constraints manually lol. To make the script work:
Once the constraints are added, just Bake Action on the target skeleton, then export the FBX. That completely fixed the issue for me, and the animation exports correctly now. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Thank you all for creating this system, it works beautifully and has been a lifesaver.
Something that I think would speed up workflows even more is a way to configure a consistent path for exporting an FK animation to Unreal. Currently every time you export, you have to set the path manually (and it doesn't remember the previous location). Something similar to what collection exporters provide, where you can list a single path and re-export easily, would be incredibly useful for rapid iteration.
Currently I'm just running the following as a workaround:
Even though it's as simple as it gets, it would be nice to have something similar natively.
One other question, is it necessary to enable bone evaluation and RBFs for exporting animations, or does the plugin handle this automatically? If it doesn't, would it be possible to include in a future update?
Thanks for your time! Keep up the good work. :)
Beta Was this translation helpful? Give feedback.
All reactions