Hi,
thank you very much for your support request.

A well formed humanoid animation file (*.anim) always contains curves for all humanoid muscles. If you don't wont to animate certain bones, you can delete all keys of that bone in your UMotion animation clip. The exported *.anim file does then contain a constant animation curve for the related muscles.

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

Best regards,
Peter

Hi Shayan,

thank you very much for your support request.

For humanoid, it is not possible to animate two characters at the same time. It is only possible to animate one and preview the animation of other(s) at the same time using the sync feature.

Please check out this answer I gave to a similar question: https://support.soxware.com/en/communities/1/topics/160-how-animate-2-characters-at-the-same-time#comment-194

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

Best regards,
Peter

Fixed in UMotion V1.23 (available in a few days via the asset store). Thanks again for reporting this issue.

Best regards,
Peter

Hi,
thank you very much for your support request.

If your model's mesh does not follow the bones, then your model might not be skinned correctly (skinning is the process of assigning bones to the mesh vertices). You can verify if this is the case by clicking on "Clear" in UMotion's pose editor (to unlock the character). Then in Unity's hierarchy window, expand the whole hierarchy of your model (ALT + left click on the arrow). Select the upper arm bone (in the hierarchy) and use the rotate tool to modify it. If your model's arm mesh does not follow, then the skinning of your model is incorrect. This problem is then unrelated to UMotion and needs to be fixed in your 3D modeling application.

I'm changing this to "not a bug" for now.

Please let me know in case this doesn't explain your issue or you have any follow-up questions.

Best regards,
Peter

Hi,
thank you very much for your support request.

Please try to update to the latest UMotion version from the asset store and see if that helps (1.22p14 is the most recent one).

This could be due to floating point imprecision (this can happen if your character is far away from the scene's center or if it's scale is very big or very small). To verify, click on "Clear" in the UMotion pose editor to unlock the character. Then set it's position to 0, 0, 0. Verify that it isn't scaled up/down in an extreme way (I recommend using 1 unit = 1 meter). Then assign the character to the pose editor again and see if that helped.

If that does not help, may I ask you to send me a Unity package that includes just everything I need to reproduce your situation (i.e. your character without textures, the related UMotion project file)? You can send the files to me via the email support form (or request a link to my Dropbox via said form).

Best regards,
Peter

Hi,
thank you very much for your support request.

Yes the other features are supported on Linux.

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

Best regards,
Peter

Hi,
thank you very much for your support request.

What type of animation do you have (humanoid or generic/legacy)?

1. For humanoid, you can adjust the rotation of the source animation by selecting the *.anim file in Unity's project window.
2. Then in the inspector window, adjust the rotation offset:
   
   
3. Then import the animation into UMotion.
4. Repeat for all rotation offsets required.
5. Then combine the clips with the different rotation offsets by copy & pasting all keys of one animation into the other.

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

Best regards,
Peter

Hi,
thank you very much for your support request.

Have you been using IK Pinning or the child-of constraint? Keys that are in "IK Pinned" state are using a different coordinate system (i.e. they are relative to the world) in respect to keys that are not pinned (they are relative to their parent bone). When you transition from pinned to not pinned, you need two key frames right after each other to correctly transition from one coordinate space to the other. UMotion creates this extra key automatically for you (that's probably the key you thought that you've accidentally created). If you delete this extra key, then the position/rotation curves interpolate between two completely different coordinate systems thus resulting in unwanted positions/rotations.

More information:

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

Best regards,

Peter

Hi,
thank you very much for your support request.

In euler rotations mode, the rotation in of a bone/transform is defined by the 3 values (i.e. the rotations around the 3 main axis). This is easy to imagine, but suffers from a mathematical problem called gimbal lock. That's why UMotion also supports quaternion based rotations (i.e. the rotation is defined in a 4 dimensional space). Quaternions are hard to imagine and it's thus not allowed to manipulate its rotation properties directly. This video tutorial explains the different rotation modes and shows you how to switch between them:

In order to control a rotation via a custom property constraint, the rotation needs to be using the euler rotation mode (that's what the error message is indicating).

Btw. if your character is of type humanoid, you get grouped fingers automatically. You can control those groups via the muscle tool assistance displayed in the scene view window when no bone is selected:

Seriously though, can we get some quality of life improvements on the animated properties list? Like grouping all the properties based on what objects they're from and adding some dropdown arrows? Unity does that by default and it's much easier to navigate!

Yes I'm with you, this is something that can be improved. For now, I recommend to go the other way (select the bone in the scene view and UMotion automatically selects the corresponding animated property for you). So in most cases, you don't have to seek in the animated properties list as of instead you select the easier to spot bone in the scene view.

On a side note, is there a way to force the IK FK to always be synced to each other? Depending on which one you've moved? Like moving FK, will update IK position and vice versa. It's disorienting when the FK bones don't move with the leg.

You can disable the FK bones completely (in case they annoy you and you are just working with IK anyway) via the rig layers:

You can manually sync FK/IK bones using this buttons:

Usually you only need to sync them at those frames in your animation where you transition from IK driven to FK driven (or the other way around). So in other words, there shouldn't be the need to have them synced each frame.

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

Best regards,

Peter

Hi,

thank you very much for your support request.

When you select the exported *.anim and preview it in the inspector window, does it play correctly then?

If yes, then you need to check your Animator state machine setup (maybe you altered the animation speed there).

If not, please post some additional information so that I can help you: A video demonstrating your problem or even better a unity package that includes your character, the UMotion project and the exported animation so that I can look at it. You can send me the package via email support (or request a link to my dropbox via said email).

I tried as fbx but it doesn't work

Please check out the chapter "Exporting Animations FAQ" in the UMotion manual. Use the "Update existing file" mode when exporting a humanoid animation.

Best regards,
Peter