Hi,
thank you very much for your support request.

Looking at the error message in your screenshot, it just looks like the humanoid avatar of your imported animation does not have bones setup for the eyes, the jaw and the left ring finger bones. You can check this by selecting the animation's *.fbx file in Unity's project window. Then in the inspector, open the "Rig" tab and click on "Configure".

This is going to show you the avatar definition and if you check the slots for eyes, jaw and left ring finger you should see that they are empty. If you need theses bones (eyes and jaw are usually not needed), assign the corresponding bones there.

If you have problems with your humanoid animation not playing correctly, it's also most likely an issue with an invalid humanoid avatar setup. Make sure that the humanoid avatar (shown in the avatar config editor that we've accessed above) of your character and the animation you want to import is in a perfect T-Stance and that all bones are displayed in green.

After adjusting the avatar of your character, you need to re-export your animation from UMotion for the changes to be applied. If you've changed the avatar of the animation you want to import, you need to re-import it into UMotion for the changes to take affect.

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

Best regards,
Peter

Hi José,

thank you very much for your support request.

The traditional visualization of the colliders is only drawn when the GameObject is select (which UMotion doesn't let you). 

But there is a different way to show the colliders:
In Unity's main window, click on "Window --> Analysis --> Physics Debugger" to open the physics debugger. In the scene view's lower right corner, there is now a small floating window named "Physics Debug"  (UMotion's tool assistant window might overlap this window by default, make sure to drag it away). Make sure to set the check mark for "Collision geometry". This is going to show all colliders in your scene even when not selected.

If you have "Preview" enabled in the "Custom Property" constraint, you can now see your collider changing live.

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

Best regards,
Peter

Hi David,

thank you very much for your support request.

Yes this can be done but is a semi automatic process. The following video covers exactly your use case (the copy to other side part starts at 10:13 but you might want to watch it as a whole as it is also showing how to fix mocap animations):

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

Best regards,

Peter

Hi,
thank you very much for your support request.

Yes via the pose editor. Under the "Animation" foldout, click on the "Key Selected" button (shortcut "Enter") then a context menu opens and then you can select if you want to create keys for position, rotation, scale (or all of them).

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

Best regards,
Peter

Hi,

thank you very much for sharing your idea. New ideas are always welcome.

I've took a note on my "ideas for the future" list. I use this list to decide/prioritize new features.

Best regards,
Peter

Hi Toni,

thank you very much for your support request and for purchasing UMotion Pro.

By default, non-humanoid bones/transforms are locked  in a humanoid UMotion project (i.e. they don't draw a gizmo in the scene view, are not included in the exported animation and are not shown in the clip editor). You can unlock a bone/transform by selecting it in config mode (in the Rig Hierarchy), then under "Properties" set "Visibility" to "Show".

By clicking on the black info icon on the upper right corner of the "Configuration" foldout, you get linked directly to the corresponding page in the manual that explains all the different "Visibility" options.

If you have any further questions, don't hesitate to ask.

Best regards,
Peter

Hi,
thank you very much for your support request.

Yes you can exclude those files from your version control.

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

Best regards,
Peter

Hi Megakeep,

thank you very much for reaching out.

I honestly wouldn't approach this situation like this. If you are creating this for a static cut-scene or a movie, make your character "generic". "Humanoid" only has advantages if you want to use one animation on multiple characters (animation retargeting) but comes with the additional difficulties and lower animation quality. Generic plays an animation exactly as you authored it (best quality) and works very straight forward. Then create an empty "Root" GameObject and attach an Animator component to it. Make the character and the car a child of the new "Root" and remove the Animator components from the character/car. Now create a "generic" UMotion Project for and assign your "Root" to the Pose Editor. You can now animate both the car and the human and they still move independently.

For more information regarding IK, Child-Of and IK Pinning, please check out the related video tutorials in the video tutorial chapter of the manual.

Another way would be to animate both objects (the car and the character) independently and use Unity Timeline to synchronize them. UMotion's "Sync" button allows you to edit animations in the Unity Timeline context (demo video). More information can be found in the "Unity Timeline Integration" chapter in the manual.

If you are doing a game where the player controls the character at runtime (i.e. walks near to the car, then presses a button to enter the car), this is a whole different story and can't be approached very well with regular "static" animations. You would need path finding to move the character close enough to the door, then use runtime IK solutions like Unity's new IK rigging package to adapt the animation to any offsets that result in different player positions etc. Inspect the way how the GTA titles approach this problem.

Let me know if you have any follow-up questions.

Best regards,
Peter

Hi Quintin,

thank you very much for your support request.

You can set "visibility" to "locked" in the config mode (for the props). This ensures that the props are not included in the exported animation data and that there is no visible representation of the props transform in the UMotion editor.

If you really don't want it to be included in the project, then you can use the UMotion callback system to write a short script that just moves the prop as if it would be parented to the hand (but is not an actual child in the hierarchy). More information regarding the callback system can be found in the manual at "Pose Editor --> Options" headline "Extending UMotion".

public class PropPreview : MonoBehaviour
{
    public Transform Prop = null;
    
    private void UMotionUpdate() // <== Use this name in the UMotion callback settings
    {
        Prop.SetPositionAndRotation(transform.position, transform.rotation);
    }
}

(Wrote the script out of my head --> untested.)

Assign this script to your UMotion prop anchor and assign the prop you want to preview to the "Prop" field. Make sure that the prop is a separate GameObject and NOT a child of the actual character. Feel free to further improve this preview script (e.g. to contain references to all props and show them as needed).

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

Best regards,
Peter