Hi,

thank you very much for your support request.

Just equal bone names is not enough for a rig to be identical. You also need to have the exact same scaling (on the whole hierarchy) and the same local position/local rotation values on all bones.

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

Best regards,
Peter

Hi,

thank you very much for your support request.

I think the reason you're having so much trouble is because you included the shoulder bone in your IK chain. That's not really an ideal setup because with the more bones you add to the IK chain, the less individual control you have.

I would recommend using the IK setup wizard for automatic setup of your human like character. It automatically generates a 2 bone IK solver for your arms and legs. Because your elbow joint is a one dimensional joint anyway, with the IK handle (for end-point position) and the IK pole handle for elbow orientation (= rotations around the shoulder joint) you have control over all degrees of freedom that are meaningful possible by this character. Using FK, you can control the shoulder bone.

Hope this makes sense. Please let me know in case you have any follow-up questions.

Best regards,
Peter

Hi,

thank you very much for your support request.

In a first step, let's try to get your animation working with your character in a default Unity scene (without involving UMotion at all). If your animation is stored inside your character's fbx file, you can leave the rig type as generic if you want. If your animation is stored in a separate fbx file than your character, the animation might use a different rig than your character so you might have to use humanoid on both of them.
There are a few Mixamo + Unity tutorials on youtube that might help you in this process.

As soon as you have a character in your scene that plays the animation correctly, we can continue with UMotion:

1. Create a new UMotion project and make sure to select either humanoid or generic, depending on how you configured your character.
2. Assign the character from the scene view to the pose editor's "Animated GameObject" field and confirm the appearing dialog.
3. Click on "File --> Import Clips" in the clip editor and select the fbx file that contains the animation clip that you've previously assigned to the character in your scene.
4. Click on import --> your animation should now be ready to use.

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

Best regards,
Peter

Hi,
thank you very much for your support request.

There is currently no native implementation of a "Look-At" constraint in UMotion but by using the UMotion callback system you can add that functionality with just a few lines of code. I've created the script for you, please create a file named "UMotionLookConstraint.cs" in your Unity project and copy & paste the following code. Then follow the comments in the code to learn how to use the script:

using UnityEngine;

// Outside of UMotion, assign this script to both the left and right eye bone of your character.
// Create a new empty transform, name it something like "Eye Target" and assign it to the "Eye Target Transform" field in the inspector.
// Pro tip: Use one separate target per eye and one parent empty transform to move both at the same time. That allows you to animate/control eye convergence.
public class UMotionLookConstraint : MonoBehaviour
{
    public Transform EyeTargetTransform = null;

    // Open the "Options" tab in the clip editor and in the "Extending UMotion" foldout add "UMotionCallback" into the "Callback Name" input field.
    // Documentation: https://www.soxware.com/umotion-manual/Options.html#ExtendingUMotion
    public void UMotionCallback()
    {
        // Assumes that the z-axis is the forward axis of the eye.
        // Use ".right" (x-Axis) or ".up" (y-Axis) in case a different axis is the eye's forward axis.
        // Put a minus in front of the parenthesis if the axis is pointing in the opposite direction.
        transform.forward = (EyeTargetTransform.position - transform.position);
    }
}

If you have any questions how to use the script, please let me know. I'm happy to help.

Best regards,
Peter

Hi,

thank you very much for your support request.

Unfortunately, such a feature does not exist in UMotion at this point. I've added it to my "ideas for the future" list so that this feature is considered for future updates.

Manually copy & pasting currently is the only way to achieve this.

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

Best regards,
Peter

Thanks again for reporting this issue and for the time you've spent investigating this. That helped a lot and I really appreciate that.

This issue is fixed in UMotion V1.28p01.

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

Best regards,
Peter

Hi,
thank you very much for your support request.

Humanoid animation clips always need to be "well-formed". That means a humanoid animation clip always has to define keys for all body parts. Use an avatar mask in your animator controller to mask away other parts of your animation:

When using "generic" or "legacy" as animation type, things would behave like you expected it (only the keyed parts are included in the exported 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.

Key frames are addressed using transform paths. An example of a transform path would be: "Root/Hips/Spine0/Spine1/ShoulderL". This path would address a bone/transform named "ShoulderL" that has a parent named "Spine1". If you copy a key frame in one project and try to paste it in another, the transform paths must match in order for the pasting to be successful. Otherwise UMotion cannot know, where the key frames belong to.

What you could try, if you do know a bit about Unity C# scripting is using the UMotion API to craft a tailored solution for your situation:

1. In the first step, create a script that loops through the whole animation clip and stores all the world space position/rotation values of the IK handles.
2. In a second step, create another script that then writes the previously stored world space position/rotation values to the other model's IK handles. Simply hardcode the names of the IK handles in your script to map them correctly.

Here is some further information regarding the UMotion API: https://www.soxware.com/umotion-manual/UMotionAPI.html

https://forum.unity.com/threads/umotion-animation-editor.490618/page-13#post-7801521

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

Best regards,
Peter

Hi Robin,

thank you very much for your support request.

Have you watched the IK video tutorial (at 2:36 of the video tutorial, the manual IK setup is shown which is necessary in your case)?

Here is the related page in the manual: https://www.soxware.com/umotion-manual/InverseKinematics.html

I recommend trying to setup IK for one leg, and if that works repeat the process for the other legs.

Please let me know in case you need further assistance.

Best regards,

Peter

Hi,

thank you very much for your support request.

hi you need to rig first

That's correct, rigging and skinning needs to be done in an external 3D modeling application. You could also try using mixamo.com, a free online service that automatically rigs and skins human like characters.

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

Best regards,

Peter