I solved it.

Generate was doing that.

Sorry.

Hi,
thank you very much for your support request. I'm glad to hear that you are enjoying working with UMotion so far.

1. Can we export humanoid animations into multiple single clip FBX? For organization purposes, I much prefer if each animation is a separate FBX (I also use the FBX curves and masks, so not being a clip makes this much easier) but attempting to do so gives a warning that it's not recommended for Humanoid Animations, and if you do so anyways, attempting to copy the avatar leads to errors about conflicting bones even though it should be the same model and rig.

Exporting into a separate FBX is going to add the bones exactly as they are in your UMotion project to the FBX. If you get errors regarding conflicting bones when copying the avatar, then there might be differences between the rig that's in your original character's FBX and the prefab you have assigned to the pose editor (reason can be that Unity modified the imported FBX or that something was added/removed in the prefab). I would recommend that you use a 3D modelling application to compare the original and the exported FBX files to further debug this.

I was able to export and update the existing FBX, but beyond just exporting a single clip at a time and constantly duplicating the FBX, I'm not sure ift this is possible?

There is currently no built in way to do this, but you can use the UMotion API to write your custom export procedure (if you know a bit of C# coding in Unity). Here is the link to the documentation: https://www.soxware.com/umotion-manual/UMotionAPI.html

Your custom script could automatically duplicate the original FBX file etc.

2. This is just a brainstorming thing, are we able to take a clip using it as a base layer, and then apply another clip ontop of it additively? For example, something I was thinking about is how Mixamo usually has a male and female run animation, and what I'd like to do is take one of those as a base, but then apply all of the keyframes of the other and use the resulting animation. The idea is for to help easily create a more unique animation.

UMotion does support additive and override layers. Here is the link to the documentation: https://www.soxware.com/umotion-manual/Layers.html

And here is a video tutorial that uses additive layers to adjust the look and feel of an existing animation:

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

Best regards,

Peter

Hi,
thank you very much for your support request.

The humanoid avatar is a file that is created when  Unity is importing the FBX of your character. It stores the transform paths of all the bones/transforms that have a human skeleton role assigned (in the humanoid setting). If you modify the transform hierarchy of your character or move the animator component to a different position in the hierarchy, the paths stored in the avatar might not be correct anymore. That's what the error message is indicating.

Make sure to use a version of your character, that has the same hierarchy as the original (imported) model of your character.

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

Best regards,
Peter

Hi Nory,

thank you very much for your support request.

The problem you are seeing here isn't really related to UMotion, but to how the humanoid animation system itself works. The humanoid animation system is an animation re-targeting system. When Unity imports an FBX file configured as humanoid, it converts the actual authored animation into a "normalized" format that can then be played by the humanoid animation system on any other humanoid character even if the animation wasn't made specifically for that character. The system is designed to make animations look similar to the original authored animation, but they won't be precisely the same.

Hands being at wrong relative positions is one such problem humanoid can introduce. In order to compensate that error, humanoid has an internal corrective IK pass implemented that can correct wrong hand and foot positions. It's just not enabled by default (but you can preview it's effect when previewing the animation in the inspector window by enabling the IK toggle button).

More information about humanoid: https://blog.unity.com/technology/mecanim-humanoids

This blog post also covers the issue you are seeing with your hands at headline ("IK Solver").

In order to enable the corrective IK pass at you're game's runtime, you need to use scripting (only the foot IK pass can be enabled via Unity's animator UI). You can use this script (make sure to have "IK Pass" enabled in your Animator window):

using UnityEngine;
using UnityEditor;
using System.Collections;

    public class AnimatorHumanoidIK : MonoBehaviour
    {
        //********************************************************************************
        // Public Properties
        //********************************************************************************

        [Header("In order to use this, enable \"IK Pass\" in your Animator Controller!")]
        [Space(15)]
        public bool EnableFootIK = true;
        public bool EnableHandIK = true;

        //********************************************************************************
        // Private Properties
        //********************************************************************************
        
        //----------------------
        // Inspector
        //----------------------
        
        //----------------------
        // Internal
        //----------------------
        private Animator animator = null;

        //********************************************************************************
        // Public Methods
        //********************************************************************************

        //********************************************************************************
        // Private Methods
        //********************************************************************************

        private void OnAnimatorIK(int layerIndex)
        {
            if (animator == null)
            {
                animator = GetComponent<animator>();
            }

            float footIKWeight = EnableFootIK ? 1 : 0;
            float handIKWeight = EnableHandIK ? 1 : 0;

            animator.SetIKPositionWeight(AvatarIKGoal.LeftFoot, footIKWeight);
            animator.SetIKPositionWeight(AvatarIKGoal.RightFoot, footIKWeight);
            animator.SetIKRotationWeight(AvatarIKGoal.LeftFoot, footIKWeight);
            animator.SetIKRotationWeight(AvatarIKGoal.RightFoot, footIKWeight);

            animator.SetIKPositionWeight(AvatarIKGoal.LeftHand, handIKWeight);
            animator.SetIKPositionWeight(AvatarIKGoal.RightHand, handIKWeight);
            animator.SetIKRotationWeight(AvatarIKGoal.LeftHand, handIKWeight);
            animator.SetIKRotationWeight(AvatarIKGoal.RightHand, handIKWeight);
        }
    }

----

If you do not plan to share your animation across multiple characters, I would highly recommend using "generic" instead. "Generic" is true "what you see is what you get" as the generic animation system plays the authored animation 1:1.

-----

My suspicion is that the culprit is most likely found in some interaction between IK and the root of the object being rotated, but I haven't been able to pinpoint it, so far.

Please note that the exported animation does not contain any custom IK code. The effect of UMotion's IK solver is completely baked into the final animation. Once exported, UMotion does not execute any IK code anymore. In order to preview what UMotion exported into your *.FBX file, you need to preview it as generic. Only generic shows you the actual authored animation. When configured as humanoid, Unity converts the actual animation of the FBX into it's humanoid format which can introduce imperfections like the ones you are seeing.

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

Best regards,
Peter

It works when Twist Bones are set to none, UMotion does not add twist bones itself?

That makes sense.

UMotion is not altering you're bone hierarchy. If you do not have twist bones in your character's hierarchy but want some, you need to add them in your 3D modelling application of choice.

Having wrong twist bone settings in the ik wizard explains why you get into a dependency loop. UMotion assumes that your arm's/leg's bone chains are longer than they really are. As a result the IK targets are placed at a wrong positions in the bone hierarchy which results in being dependent on each other --> loop.

Btw. you can click on the black "info" buttons (spread across the entire UMotion UI) to jump right to the related page in the UMotion manual. Stuff like how the "Twist Bones" setting exactly works is explained there: https://www.soxware.com/umotion-manual/IKSetupWizard.html#HumanIK

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

Best regards,
Peter

Hi Adrian,

thank you very much for your improvement suggestion.

I've noted your idea on my internal "ideas for the future" list. This list is used when considering which new features to ship in new updates.

Best regards,
Peter

Hi Dave,
thank you very much for your input and also thanks for your nice words. I'm glad you enjoy working with UMotion.

The problem I see with this feature is when people new to UMotion accidentally use it and then get confused why the pose doesn't update while scrubbing. Maybe a different but similar affective feature would be copy/paste buttons in the pose editor. What do you think?

Best regards,
Peter