Hi,

thank you very much for your support request.

This error message indicates, that there is a transform in your animated 3D model in Unity / UMotion that does not exist in the FBX file you are trying to export to.

Sometimes if your FBX contains none unique names, Unity renames those transforms on import. UMotion knows nothing about that, but as soon as you try to export your animation into the FBX file, UMotion is not able to find the re-named transform in the FBX file because it uses a different name there. To fix this, open the FBX in a 3D modeling application of choice and correct the bone/transform names so that the naming is the same as in Unity.

Please let me know in case you have any follow-up questions.

Best regards,
Peter

Fixed. UMotion doesn't like multiple GameObjects in the Rig hierarchy to have the same name. 

Make sure every GO has a unique name.

Hi,

thank you very much for your support request.

There are only rare cases where it is useful to create keys only for one axis. That's why by default, UMotion chains the keys on all 3 axis together. You can change that behavior by going into the settings (click on the gear icon in the Clip Editor), then disable the "Chain Neighbor Keys":

Please let me know in case you have any follow-up questions.

Best regards,
Peter

Hi,

thank you very much for your support request.

Please update your UMotion version to the latest version from the asset store. Please also check out the "Exporting Animations FAQ". It contains a collection of the most common mistakes when exporting an animation. Usually when exporting to FBX, the "Update Existing File" mode is recommended (and is the default in the new UMotion versions; see FAQ for more info).

In case this doesn't solve your issue, provide some further information (a screenshot of your export settings, a screenshot showing the problem, are you using humanoid or generic,...).

Thank you very much.

Best regards,
Peter

Hi,

thank you very much for your support request.

There is currently no way to tell UMotion that a transform that was added outside of UMotion should be ignored when exporting to FBX. That's what the custom transforms in UMotion have been designed for (they are ignored when exporting as they only live inside UMotion). Unfortunately, you can't address these transforms from within your final IK components.

I see two possible workarounds:

1. Use Unity's FBX exporter to export your new character configuration (including the IK targets) into a fresh FBX file. You can get Unity's FBX exporter via Unity's package manager (don't use the FBX exporter from the asset store, it's deprecated). Then use UMotion to export the animation into that fresh FBX.
   
2. Use your 3D modeling application of choice and add the IK targets manually to the existing FBX file.
   

I hope that helps. Please let me know in case you have any follow-up questions.

Best regards,
Peter

Hi,

thank you very much for your support request.

Is there a way to update a UMotion project when non-rig child game objects inside the rig hierarchy are changed?

Yes this is possible. As you correctly assumed, UMotion stores the initial pose (position, rotation values of all bones and transforms) your character had when you first assigned the character to the pose editor. This pose is called the "reference pose". In order to manipulate/update the reference pose, go into config mode. Under the "Configurations" section, select the "Reference Pose" tab. Click on the "Apply Scene Pose" button to apply the latest changes you've made to the scene pose. Then click on "Save Reference Pose" to save the changes.

For more information about config mode, please check out the related video tutorial:

Please let me know in case you have any follow-up questions.

Best regards,
Peter

Hi,

thank you very much for your support request.

UMotion does not support pivot mode "center" yet. I've took a note on my to-do list to implement this in a future update. Thanks for pointing that out.

You can workaround this limitation by making the IK handles of the hands a child of a new custom transform (this can be done in config mode). You can then rotate both at the same time by rotating the new parent transform. More information about config mode can be found in this video tutorial:

Please let me know in case you have any follow-up questions.

Best regards,
Peter

Hi,

thank you very much for your support request.

This is a typical problem that people run into when using the humanoid animation system. It's a result of the humanoid avatar's initial T-Pose not being 100% correct.

1. Select your character's fbx file in Unity's project window.
2. In the inspector window, open the "Rig" tab and click on "Configure".
3. Make sure, that your thumbs are in the exact same pose as shown in this screenshot (carefully look at which direction the nail of the thumb is pointing):

(Source: https://blog.unity.com/technology/mecanim-humanoids)

The accuracy of the T-Pose has great impact on the accuracy of the humanoid animation.

If the animation you've created is only used on one character, you could also just change your character to "generic". This uses the authored animation 1:1 as it was authored thus avoiding such issues. Generic is also consuming slightly less CPU time.

Please let me know in case you have any follow-up questions.

Best regards,

Peter

Hi,

thank you very much for your support request.

Only if bones are skinned (i.e. vertex painted) they are going to be treated as bones by Unity (= Unity assigns a SkinnedMeshRenderer component and adds all bones to the "bones" array of that component). If the bones are just parents of separate meshes, then they are treated as regular transforms (with MeshRenderer components applied to each of the bones).

In the end, both works though and it's just a different visualization. Be aware that the later method uses one draw-call per separate mesh for rendering thus resulting in (little) higher performance cost (depends on your project if this is going to be a problem or not).

Please let me know in case you have any follow-up questions.

Best regards,
Peter