Hi,
thank you very much for your support request.

Your request is very similar to another one I received in the past so I'm linking my answer here: https://support.soxware.com/communities/1/topics/529-tail-bones-weight#comment-691

As mentioned in my answer linked above, the IK solver's primary use-case is for 2 bone IK situations. More than 10 bones is unfortunately not a use case the solver has been designed for and is thus not supported. Please note that you can of course extend UMotion with any 3rd party (or custom written) IK solvers specifically made for tails using UMotion's callback system. More information can be found in the manual at "Pose Editor / Options / Extending UMotion".

If you have any further questions, don't hesitate to comment in this thread.

Best regards,

Peter

Hi,
thank you very much for your support request.

This is already possible. Create your pole target transform outside of UMotion (by adding GameObjects to the Hierarchy of your character). Then in the IK constraint of UMotion, select the just created transforms as pole targets.

The IK video tutorial goes in-depth with the IK constraint:

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 toggle the "IK" button shown in the preview window. Humanoid is a "lossy" animation format (like jpeg is a lossy image format). That means that the end-result is always expected to have small differences. If you aim for animations that are precisely equal to the authored version, use generic instead (it is the lossless format, similar to how bmp is a lossless image format). Humanoid has the advantage of being capable of playing an animation on different characters (at the expense of animation quality).

More information about humanoid (it also explains the IK feature mentioned above): https://blogs.unity3d.com/2014/05/26/mecanim-humanoids/

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

Best regards,
Peter

Hi,
thank you very much for sharing your idea.

Aborting the "Export All Clips" process is indeed something that can be handy when the process is accidentally started. I've added this to my to-do list for an upcoming update.

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

Best regards,
Peter

Hi Sebastien,

thank you very much for your support request.

Sure, you can change the overall bone size in the "Options" tab of the pose editor window:

The size of individual bones can be changed in config mode ("Properties" tab).

You furthermore have the option to change the bone rendering style to "sticks" or "wired" in the "Display" foldout.

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

Best regards,
Peter

Hi,
thank you very much for sharing your idea.

If looping is enabled or not for the current clip is already displayed in the clip editor:

Is that what you've been looking for?

Best regards,
Peter

Hi,
thank you very much for your support request.

Please note that the size of the *.anim file shown in the windows explorer is not the size the *.anim file is going to have in your built game. The build size is shown in the inspector of the *.anim file. The authored *.anim file contains lots of editor only data that increases the file size in your project, but this data is stripped as soon as you build your game.

Never the less you are right, exporting to *.fbx can bring the file size even further down.

What you're seeing here is that the humanoid avatar generated for your exported fbx isn't created correctly, thus the animation re-targeting has more offset/error than usual. There are two ways you can overcome this issue:

1. In the UMotion export settings, set "Write Mode" to "Update Existing File". Then select your character's *.fbx file as destination file (you can also duplicate your character's *.fbx file first if you want). This ensures that Unity uses the correct humanoid avatar for converting your fbx animation to humanoid.
2. If you want to keep "Write Mode" to "Export As New File" you need to create a T-Pose in the first frame of your animation. Go into Config Mode and make sure your character is in T-Pose there. If not, click on the "Apply Bind Pose" button and then click on "Save Reference Pose". Your character should now be in T-Pose. Back in edit mode, move all keys of your animation clip one frame to the right. Move to the first frame, click on "Apply Reference Pose" to apply the T-Pose. Then create key frames for all bones. Now delete your previously exported *.fbx and re-export. Usually this ensures that Unity generates a correct humanoid avatar for your character (but this can depend on the character rig). In the inspector of your fbx animation, you can adjust the timing so that the first frame is skipped.

Let me know if this works for you.

Best regards,
Peter

Hi,
thank you very much for your support request.

You can only re-target your humanoid animation to your generic character if your generic character can be configured as humanoid. In that case you would just need to duplicate your character and configure the duplicated version as humanoid. Create a new UMotion project of type humanoid and then import the humanoid animation clip. Then create a generic UMotion project for the generic version of your character and import the humanoid UMotion project (via regular clip import) into the generic project. Now you can export the animation as generic.

My Animation Converter asset does it in a similar way but it has an optimized workflow for this conversion and is thus faster (requires less clicks).

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

Best regards,
Peter

Thank you very much for explaining your situation. I've took a note on my ideas for the future list, so that this feature is considered for new versions.

Best regards,
Peter

Hi,

thank you very much for your support request.

Correct, IK Pinning doesn't work on an additive layer (as you can't really add up IK Pinning in a meaningful way). You can only adjust IK Pinning in the base layer or in an override layer. I'll try to make this clearer in the docs.

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

Best regards,
Peter