Hi tecd,

thank you very much for your support request.

If you're doing your offset in an additive animation layer, it should work by copy and pasting the key(s) from the one animation's additive animation layer to the other animation's additive animation layer (I just double checked that). Keys in an additive animation layer are stored as "offsets".

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

Best regards,
Peter

Hi Tabornok,

thank you very much for your support request.

The timeline does not work in a humanoid project.

You mean Unity Timeline? Unity Timeline does support humanoid characters. What makes you think that Unity Timeline does not support humanoid characters?

Animation cannot be convert to humanoid to generic or gen. to human.

You can convert animations with UMotion. Exporting to FBX is one way to do it (you can then decide in the FBX settings if you want the animation to be generic or humanoid).

When you want to directly export to *.anim, this is the way to go:

1. Duplicate your humanoid character's FBX file.
2. Change the rig of the duplicated character to "generic".
3. Instantiate your generic character in the scene and assign the gun to it (at the same place in the hierarchy as in the original humanoid character).
4. Create a new generic UMotion project and assign your new generic character + gun setup.
5. Now import the animation clips of your humanoid UMotion project by selecting your humanoid UMotion project instead of individual *.anim clips.
6. Now you have your humanoid animations imported in your generic project thus converted to generic and you can now export them to a generic *.anim.

There are two different animators, one for the weapon, one for the character, so I need a generic and human.

I recommend to only use two separate animators when the animations don't interact with each other. As in your case, the character and it's hands interact a lot with the gun, it's counter intuitive to use two separate animators. Try to use only one animator instead.

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

Best regards,
Peter

Hi,

thank you very much for your support request.

While there is no feature to lock the rotation axis, you could use "euler rotation mode" for the bones you mentioned (e.g. the lower leg bone). As you only rotate the knee around one axis (if the rig is setup correctly), you're not going to suffer from gimbal lock (gimbal lock is the downside of euler). In euler mode you would see it in the curves view if you've accidentally rotated around a wrong axis axis (onle one axis should contain actual data, the other 2 should be completely flat).

More information on the different rotation modes can be found in this video tutorial:

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

Best regards,
Peter

Thanks for sending me the example project. It was very well structured and made it easy for me to investigate, thanks for that.

From your email:

I think this could be related to the bow having the bones parent called "Armature" as well (Which also gives a warning). I sadly can't change the name, as blender does this automatically for rigs.

Yes that's exactly what's causing the issue. The de-optimize method thinks that the bow's "armature" is the same as the "armature" of your character. Thus the de-optimized setup ends up with a different rig hierarchy (where the bow is a child of the character's "armature" bone instead of the "Wrist1" bone).

Unfortunately this isn't something that I can fix in UMotion's code as this problem is coming from within a Unity API method called AnimatorUtility.DeoptimizeTransformHierarchy(). Luckily the fix for you is rather easy, just rename the "armature" bone of the bow to something unique (e.g. "armature_bow"). You can do this in your prefab in Unity, no need to do this in Blender.

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

Best regards,
Peter

Hi,

thank you very much for your support request.

Doing an "aim" inside an animation means that it is baked into the animation and won't adapt at the target's position at real time. That's why usually a real-time IK solution is used for this (on top of the regular animations) which calculates the pose at real time based on the current target position. This for example is final IK's aiming solution:

Link: Final IK - Asset Store

If you have a special case where you want to bake the result into an animation clip (because you're targets don't change at realtime) you can extend UMotion's functionality by (e.g. Final IK's Aiming solution) using the UMotion callback mechanism. That way you can preview and key the behavior inside UMotion. For more information regarding the UMotion callback mechanism and how to use it with Final IK, please check out the UMotion manual at ("Pose Editor / Options" headline "Extending UMotion").

Don't hesitate to contact me in case you have any follow-up questions.

Best regards,
Peter

Hi Woodyy,

thank you very much for your support request.

Ok so the face rig is using blend shapes for the facial expression or is it using bones? Are you sure this isn't a problem with your character / your import pipeline? You can verify if the blend shapes on your character are working by dragging your character to the Unity scene. Then look for the GameObject that has the SkinnedMeshRenderer component and open the "Blend Shapes" foldout in the inspector. Here you can play with the blend shape weights (100 means full influence of the blend shape):

If the blend shapes also don't work in that case, you might want to double check your setup in blender and your import/export settings. If they do work using the method mentioned above, it might be a problem with UMotion not previewing the blend shapes correctly for some reason. If that is the case, I would love to take a look at it. Please send me your character (without textures if you want) and your UMotion project file via email support form (or request a link to my dropbox if file size is too big for email transmission).

Please let me know if you need any further assistance. I'm happy to help.

Best regards,
Peter

With UMotion V1.26 I introduced an easier way to update a custom transform to a real transform:
Create new empty GameObjects in your character's hierarhcy (outside of UMotion) that are named like the custom transform inside UMotion and are located at the same position in the hierarchy.

When you then assign the character to the pose editor, UMotion is automatically going to ask you if it should convert the custom transform definitions to real transform. All other steps mentioned in my previous post are not necessary anymore in this case.

The animation data for those transforms is then automatically included in the exported animation.

UMotion V1.26 is shipping in the next one or two days via the asset store.

Please let me know in case you have any questions.

Best regards,
Peter

Hi Antoine,

thank you very much for your support request.

Let's narrow down the cause of this issue:

1. Select one of the exported animations (that you use in Timeline and that jitters) in Unity's project window. In the inspector preview section at the bottom, play the animation. Does it also jitter in the preview window?
   
2. You can also try to drag & drop the character you use in Timeline from Unity's scene into the preview window. This is going to preview the animation using the correct character. Does the jitter appear in that case?
3. If the problem is not present in point 1 or point 2, does it happen if you scrub through the Unity timeline (when not being in play mode)?

Please let me know the results of your investigations, so that I can further assist you.

Best regards,
Peter