Hi,

thank you very much for your support request.

The FBX export (due to being native code), does not support native M1 yet. Future versions of UMotion might add support for M1 macbooks, but I do not have an ETA for that yet.

Afaik there is some kind of compatibility feature to run legacy intel based programs on M1 macbooks. Maybe using Unity in that mode could workaround this issue?

Best regards,
Peter

Hi,

thank you very much for your patience. I've fixed the issue in UMotion V1.28p03.

You can download the new version via the asset store.

Thanks again for reporting the issue.

Best regards,
Peter

Hi,

thank you very much for your support request.

Animations in Unity can only address things that are in the hierarchy below (i.e. a child) of the the Animator controller that is actually playing the animation. In other words, your sphere needs to be a child of your character (in case of humanoid, the sphere needs to be a child of the hips or something lower in the hierarchy).

In the UMotion Examples folder, there is an example scene included. The character on the very right in the example scene shows you how to use the child-of constraint.

PS: In case of picking up stuff from the scene, a common approach to circumvent this limitation is by using an empty transform as "mount point". The mount point is part of your character's hierarchy and can thus be manipulated by the animation. A custom script triggered by an animation event is using "Transform.SetParent()" to make picked up objects a child of the mount point at runtime.

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 UMotion's Pose Editor, go into config mode. Select the "CS_Jacket_14097.Shape", open the constraints tab and resolve the error by removing the duplicated custom property (by clicking on the X).

Here is the documentation of the custom property constraint: https://www.soxware.com/umotion-manual/CustomProperty.html

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

Best regards,
Peter

Hi,
thank you very much for your support request.

Select the source *.anim file that you want to import. In the inspector window, change the "Root Transform Position (Y)" setting to this:

Do the same for the exported animation.

Btw. in UMotion, you can also flatten the y curve of the root bone (hips). Select the hips in the animated properties list, open the curves view and hide the x and z curves by clicking on the eye icons (in the properties list). Then select the first y key, and take a note of the value. Then select all y keys, right click on one and select "Edit Key". Then type in the value you've previously noted.

If you have some intended y movement in between, only ensure that the first and last key frame have the same value. Might also need some correction of the values of the last few frames to smooth out a potential hick-up.

Please let me know in case you have any follow-up questions or if this does not solve your issue.

Best regards,
Peter

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