Hi,
thank you very much for your support request.

Looks like the rig/skeleton of your character is not compatible with Unity's humanoid animation system or your humanoid avatar wasn't configured correctly. This should be a UMotion independent problem. Double check your humanoid configuration (select the character in Unity's project window, then click on the "Configure.." button in the "Rig" tab of the inspector window). All bones should be displayed in green. There should also be no error/warning messages displayed in the "Rig" tab of the inspector window. Try to verify your setup by playing any arbitrary humanoid animation on your character.

This is the related Unity video tutorial: https://youtu.be/pbaOGZzth6g

This Unity manual page describes the required bone structure: https://docs.unity3d.com/Manual/UsingHumanoidChars.html

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

Best regards,
Peter

Hi Janooba,

thank you very much for sharing your idea. I really appreciate that.

I've added your idea to my "ideas for the future" list, so that I can consider implementing it in a future update.

Best regards,
Peter

Hi,
thank you very much for your support request.

An animation that contains bones/rotations instead of the humanoid "muscle" rotations is a "generic" animation. Afaik "generic" animations can not be played by Unity's animator component of a character that is configured as "humanoid".

Anyway, there are two ways how you can export your animation as "generic" (so that bone rotations are used) from UMotion:

1. Export your animation as *.FBX. I highly recommend setting "Write Mode" to "Update Existing File" in the export settings and to select your character's *.fbx file (or a duplicated version of it) as destination file. This ensures that the exported animation is fully compatible with your character.
2. Create a new UMotion project of type generic. Duplicate your "humanoid" character and configure it as "generic". Assign an instance of the "generic" character to UMotion's Pose Editor and then import the animations from the "humanoid" project.

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

Best regards,

Peter

Hi,
thank you very much for your support request.

All UMotion files are "editor only", meaning that nothing of UMotion (except the exported animation's) end up in your built game. The error that you see here is a false alert generated by Unity's dll loading code. It is never going to show up in your built game and it has no negative impact on the functionality of UMotion or the Unity editor.

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

Best regards,
Peter

Hi,

thank you very much for your support request.

For an introduction on how to use UMotion to animate various things, please follow the video tutorials. Please check out the chapter "Video Tutorials" in the UMotion manual for a comprehensive list of all available video tutorials.

Please let me know in case you want to know anything specific.

Best regards,
Peter

Hi,
thank you very much for your support request.

This warning is just informational. UMotion runs through all scripts that are not in a custom assembly (i.e. are not using an assembly definition file) and checks if it finds a method with the name that you've entered. If it does not find it, it shows this warning. Unity can still invoke this method if it is in a different assembly, it's just UMotion that doesn't check other assemblies.

In order for animation events to be triggered correctly, just make sure that you've assigned your script to the animated GameObject and that the event name and parameter type that you configured for the animation event in UMotion is exactly the same (case sensitive!) as in your script. When changing something in UMotion, you always need to re-export your animation.

Here is the UMotion animation event tutorial:

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

Best regards,
Peter

Hi,
thank you very much for your support request.

You need to change the rotation interpolation mode of your finger joints to "Euler Rotation".

By default, all joints use quaternions to represent the rotation (this is a 4 dimensional representation of an orientation, hard to imagine and thus makes no sense to manipulate one coordinate of it directly via a custom property constraint).

Here is a detailed video tutorial covering this topic:

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

Best regards,
Peter

Hi,

thank you very much for your support request.

Try the following:

1. Click on "Clear" to remove the model from the UMotion Pose Editor.
2. Try to find and select the same bone that you just selected in Unity's Hierarchy Window.
3. Use the rotation tool to rotate that bone in Unity.

In case the arm's mesh also doesn't move with the bone, the bone you are trying to move has no vertices applied (i.e. it is not skinned). You need to fix this in a 3D modeling application.

In case the mesh moves with the bone now, please send the model to me (without textures if you want) so that I can further investigate as in that case it might be a UMotion bug. You can send it to me via the email support form.

Best regards,
Peter

Hi,

thank you very much for your support request.

If you move the keys of certain bones into an (override) animation layer you can mute/and even gradually fade the influence of the whole layer. Please note that muting means that the whole layer is disabled, thus also the first frame in that layer is disabled. UMotion is then going to apply the keys that are in the layers below (n case there are no other keys existent, the reference pose defined in Config Mode is applied).

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

Best regards,

Peter