Hi Dave,

thank you very much for sharing your ideas.

- deselect multiple keyframes shortcut

That's already possible: CTRL + D

You can change the shortcut under "Edit --> Preferences --> General" in the Clip Editor:

- Option to isolate selected animated properties
- add selection and deselection of keyframes to undo stack

Yes these are valid points and I already have them on my to-do list. Both require some bigger internal changes so they won't land in the next update (V1.29) which is scheduled to be released in the next 1-2 days. But on the positive side, some of your previous ideas are going to be included in V1.29 so stay tuned :-)

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

Best regards,
Peter

Hi,
thank you very much for your support request.

If you animate the facial expressions manually, then yes:

1) Create a Unity timeline sequence with the sound file and your animation

2) Sync UMotion to Unity timeline to edit the animation file

3) Make sure that in Unity timeline you have audio preview enabled (to actually hear the sound file while playback)

There is no automated way to do this in UMotion.

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

Best regards,
Peter

Hi,

thank you very much for your support request.

What export settings do you exactly use? I would recommend using the "update existing file" mode and have your character's FBX file selected as destination file.

Another thing to consider, humanoid gives you less degrees of freedom in animating than generic. Looks like you've applied a tilt on your upper leg bones in UMotion which is something real-life humans are not capable of doing. UMotion let's you correctly preview your animation but once your animation is exported to FBX and then imported as humanoid by Unity, it discards that rotation.

If you want 100% artistic control over your character in your animation, use generic instead of humanoid.

The only reason to choose humanoid over generic is when you have lots of characters that should all use the same animation. If that is not the case, generic is recommended. More information on what humanoid actually is, can be found in this blog post: https://blog.unity.com/technology/mecanim-humanoids

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

Best regards,
Peter

Hi,

thank you very much for your support request.

After looking at the API again this might actually be a feature request: Would it be possible to get a TrySetComponentProperty to go along with TrySetFkLocalPosition/etc.? With that making the transform handle work with UMotion would be no problem at all.

I'm currently working on a new UMotion version that comes with an updated/extended UMotion API. I've already implemented your requested method today. The new version should be available in a few days.

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

Best regards,
Peter

Hi,
thanks for your support request.

1- the size on windows is not the same as the size in unity. Size in unity is around 200kb while in windows explorer its 8 mb

This is the correct answer. More details here: https://support.soxware.com/en/communities/1/topics/350-umotion-multiplies-x9-my-animation-size-what-can-i-do#comment-397

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

Best regards,
Peter

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