Hi,
thank you very much for your support request.

I'm afraid what you're looking for is currently not really possible with UMotion. I'm sorry.

Please let me know in case you have any further questions.

Best regards,
Peter

Hi,
thank you very much for your support request.

The short answer: In your scenario you should be using generic, not humanoid. Humanoid is only the right choice if you don't care about fine details being wrong (like some bones being slightly off). For your FPS scenarios, you should be using generic as small details (like the thumb rotation) are very prominent to the player.

Unity's generic animation system plays an animation 1:1 as authored by the artist. Unity's Humanoid animation system on the other hand performs so called "animation re-targeting" (i.e. it tries to mimic the original look of the animation, but doesn't guarantee 1:1 results). The big benefit of humanoid is that animations can be applied on any other character configured as humanoid while maintaining a kind of similar look (but not 100% the same look). Generic animations need to be played on the exact same character the animation was originally created for.

More information about humanoid: https://blog.unity.com/engine-platform/mecanim-humanoids

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

Best regards,
Peter

Hi,
thank you very much for your support request.

If the facial expressions are done using extra bones, you might need to unlock them in UMotion. UMotion only displays the default humanoid bones (in humanoid projects) and hides any non-default humanoid bones. Go into config mode, select the bone you want to enable. Then click on the "Properties" tab and set "Visibility" to "Show".

Blend shapes are also supported and can either be automatically setup (UMotion asks you to do that when you first assign a character to the pose editor) or can be manually setup by creating custom property constraints for each blend shape.

See: https://www.soxware.com/umotion-manual/CustomProperty.html#ComponentProperty

Please let me know in case you need any further assistance.

Best regards,
Peter

Hi Elsiehar,

thank you very much for your support request.

IK has less "degrees of freedom". Meaning not every FK pose can be converted into the 100% same IK Pose. This is simply due to the fact that you can rotate bones in FK in a way you can't do with IK (e.g. rotate a bone around it's own axis).

Furthermore the FK to IK algorithm has to do some guessing work in order to get a similar looking pose but it won't always be 100% perfect.

So best is to not transition between FK to IK in situation where this transition is very noticeable.

Best regards,
Peter

Hi,
thank you very much for your support request.

Please check out the quick start video tutorial. It shows you how to manipulate the IK skeleton:

https://www.soxware.com/umotion-manual/QuickStart.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.

After the export to Unity, then UMotionPro, these bones are no longer present? How can I prevent this?

You've probably configured your character as "humanoid". Humanoid by default only supports the following bones:

https://docs.unity3d.com/ScriptReference/HumanBodyBones.html

More information about humanoid: https://blog.unity.com/engine-platform/mecanim-humanoids

So to solve your issues, you should either configure your character as "generic" (in the rig tab of the inspector window when you have your character's fbx file selected).

OR you can enable generic bones in a humanoid UMotion project by going into config mode, selecting the hidden bones and click on "visibility" - "show". But this more or less destroys the only real benefit of using humanoid (over generic), namely animation re-targeting won't work anymore, so you're often better of choosing generic in the first place and avoid all the problems people usually have when using humanoid.

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

Best regards,
Peter

Hi,
thank you very much for your feature request.

What you are looking for is a so called "look-at constraint". I've put this on my list of feature ideas for the future so that it's considered when defining features for future updates. Thanks a lot.

Best regards,
Peter

I found the problem. I use Opsive Ultimate Character Controller. It requires animations as Root Transform Y baked. I selected it and exported animations work fine now.

Hi,
thank you very much for your support request.

UMotion by itself does not feature animation compression, but you can export your animation as FBX and then in the FBX's import settings use Unity's built in animation compression. When exporting to FBX (especially when using humanoid), make sure to select the character's fbx file (or a copy of it) as destination file.

PS: Your UMotion version is already pretty dated. Please update to the latest version from the asset store. Newer versions usually contain several bugfixes.

Best regards,
Peter

Hi,
thank you very much for your support request.

There is no technical dependency on the original FBX animation. You can safely delete it.

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

Best regards,
Peter