Hi,

thank you very much for your support request.

Unfortunately only the FBX export can make use of Unity's animation compression pipeline. One thing you could do would be to export your animation twice (once as *.anim and once as *.fbx). Then you can copy the compressed animation data from the fbx into the *.anim that also contains the blend shape data. You can copy and paste the keys using Unity's animation window. Unfortunately there isn't a more comfortable way I'm aware of.

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 found the discrepancy. The model jumps to position 0,0,0 when the Unity animation preview button is pressed. When game play is pressed the model stays in its position and the animation takes place at that new relative position of the model placement instead of snapping to 0,0,0.

You mentioned that you're using the animation in Unity Timeline. There are dedicated settings in Timeline that define how the start offset should be handled. If you select the animation track, you get this choices shown in the inspector:

And if you select the animation clip (in Timeline), you have this settings:

Hope this helps. If there is still something unclear, let me know.

Best regards,
Peter

Hi,

thank you very much for your support request.

1: Why does it automatically connect the two child top bones to the main one ? ("bone" to "Bone.001" and "Bone.002")

Because the FBX file does not store any information about which bones should be visualized as "connected" and which bones should not. You can change such visualization things in UMotion's config mode. If you want to hide the connection of a joint to it's parent, set the "Parent Link" property to "Hidden":

The only thing left now is to figure out why are the end bones disappearing in Umotion

In your first picture, you can see that the end joints have been imported by Unity (the cubes) but the end joints are not bound to the mesh (thus not displayed as bones but as regular transforms). If you want them to be imported correctly, you need to make sure that the end joints are also skinned.

In your second picture the end joints are completely gone (due to changed export settings in Blender?). 90% of the time, this is how a model is imported into Unity. So this is a common situation. There are two ways you can deal with this:

1) You can select this joint whenever you want to rotate the last bone:

2) Or if you really want the last bone to appear, you can also create custom joints for the end joints inside UMotion. This is covered in this video tutorial:

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

Best regards,
Peter

Hi,

thanks for your support request.

Op answered his question by himself:

Oops. My bad. I did not have this gameobject in the Pose editor.

Best regards,
Peter

Hi,

thank you very much for your support request.

Yes the way you described it should work. As soon as you exported to *.anim (or *.fbx) from UMotion, the animation is a regular animation (like any other). You need to make sure that the character in both projects is also configured the same way (e.g. configured as humanoid in both projects). You can't use a "generic" animation on a "humanoid" character for example.

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

Best regards,
Peter

Hi,

thank you very much for your support request.

By default, the rotation of the last joint in your IK chain is driven by the IK handle's rotation. You can change this to use the local FK rotation of the joint itself in the IK constraint settings:

This setting is also available via the IK setup wizard:

If I recall correctly, the default value was changed in the past that's why it might be different in the video 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.

I would start with the general quick start video tutorial (and the following in-depth tutorials) to learn the basics of UMotion. Check out the "Video Tutorials" chapter in the UMotion manual. It gives you a nice overview of all the video tutorials available.

There is also a dedicated video tutorial on how to animate first person arms + a gun. The same principle would apply no matter if it's only just arms you're animating or if you're character has a complete body.

For doing stuff like walking animations etc. I recommend starting with an existing animation (e.g. from the asset store) and try to adjust it to your needs. Using animation layers / masks in your Unity animator controller, you would then mix e.g. the walking animation (affecting the whole body) with the gun related animation (only affecting the arms and the weapon).

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

Best regards,
Peter

Hi,

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

I also do think that double clicking to add a key would be good addition to the current workflow. I've taken a note on my "ideas for the future" list. This list is taken under consideration when deciding on new features for every new version.

Don't hesitate to contact me in case you have any questions or any further ideas.

Best regards,
Peter

Hi,

thank you very much for your support request.

The UMotion IK constraint can be used on any type of bones. It's just that the IK setup wizard does not create IK for the spine. You can add IK to your spine manually.

Please watch the IK video tutorial to learn how IK constraints can be setup manually (first part of the video covers the IK setup wizard, second part the manual setup):

I personally prefer using FK for the spine though. When you select all the spine bones and use the rotation tool, the rotation is automatically smoothly distributed between all selected bones. That creates a really smooth bending while still maintaining full control over each and every individual bone (due to FK), something you loose when using IK instead.

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

Best regards,

Peter