Hi,
thank you very much for your support request.

I did a quick test in Unity 2020.1.0b5. I added an animation even to the "WalkRMAnimation.asset" animation in the samples and exported the animation clip. The animation event correctly shows up in the exported animation:

Can you double check if it is not working for you?

Here is the animation event tutorial for reference:

Best regards,
Peter

Hi,
thank you very much for your support request.

Two things are stored in the "UMotionData" folder:

1. Automatic backups
2. The undo/redo stack of your current editor session

It is recommended to ignore the whole folder in your source control. If you want you can also ignore the "Data" folder inside the "Assets/UMotionEditor" folder. It also contains information about the undo/redo stack and stores the "recently opened UMotion project's" - list.

Please let me know in case you have any other question.

Best regards,
Peter

Hi,

thank you very much for your support request.

To debug this, I recommend to divide your problem into two steps:

1) Let's see if your standing up animation correctly uses root motion. Enable looping (in the exported *.anim file's Inspector) and make sure "Apply Root Motion" is also enabled in the Animator component. Then play the animation twice: Your character should stand up, turn 180°. Then at the current position it should sit down (but keep the current position/orientation).

If this doesn't work, you may want to check the root motion settings in the Inspector of your *.anim file.

Setting everything to "Original" and disabling "Bake Into Pose" might work (haven't tested this though).

2) Once you got (1) working, add the transition to it. If the transition doesn't work, then chances are that your second animation's root motion settings are incorrect (check the *.anim file's Inspector).

Here is Unity's documentation of the root motion settings: https://docs.unity3d.com/Manual/class-AnimationClip.html#ClipProperties

If you have issues with small offsets of the root motion, use UMotion's experimental root motion export. Enabling Unity Mecanim/Animator IK can also improve the re-targeting quality (especially for the hands to reach the front seat precisely).

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

Best regards,
Peter

Hi,
thank you very much for your support request.

Yes this is possible. Generic bones are hidden by default in humanoid UMotion projects but you can make them visible:

1. Open Config Mode
2. Select the bone you want to make visible (in the Rig Hierarchy)
3. In the "Properties" tab set "Visibility" to "Show"

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

Best regards,

Peter

Hi,

thank you very much for your support request.

Yes you can of course create root motion for new or existing animation clips. The motion has to be manually created by moving the bone marked with "RM" (in case of humanoid it's the "Hips" bone). Auto-generating root motion from an in-place animation is not supported.

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

Best regards,

Peter

Hi David,

thank you very much for your support request.

The complete change log (since version 1.0) can be found in the manual's "Release Notes" chapter. The change log on the Asset Store only shows changes of the current version and its patch releases.

Edit: This is the forum post that highlights the changes of UMotion V1.21: https://forum.unity.com/threads/umotion-animation-editor.490618/page-9#post-5584264

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

Best regards,
Peter

Hi Jules,

thank you very much for your support request.

In mirror edit mode, when I rotate a single selected bone and its counterpart also rotates with it, pressing M to key modified bones does not key the mirrored bone unless it is also selected. Even if this is intentional, wouldn't it make sense to key the mirrored bones of the selected ones too?

This is intentional. As the button is named "Key Selected" it should only key bones that are currently selected (otherwise it might confuse users).

Also is there a quick button (and keyboard shortcut) to do the equivalent of Select All + Key Modified but keep the selection the same as it was? That would be a quick workflow!

Try this: [CTRL + Enter] and then [Enter]

This is going to open the "Key Dialog" (which lists all modified keys by default) and enter confirms keying them. Your current selected bones stay selected. You can change the key binding (if you don't like CTRL+Enter) if you click on Edit --> Preferences (in the Clip Editor).

Btw. if you want you can also enable "Auto Key". This would automatically create keys for everything you change. This feature also automatically keys mirrored bones.

Related to the above issue, if I key just the selected bone, it leaves the mirrored bone red, and then when I go to another frame it asks what to do with the modifications, but there is no option to simply key them before moving on to the other frame.

There are only 3 possible buttons that can be shown in this type of dialog window. So unfortunately I don't have the possibility to add this fourth option.

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

Best regards,
Peter

Hi,

thank you very much for your support request.

The main issue here is that one animator component (and thus the animations that are assigned to it) can only reference its child transforms.

Here are some ideas that might fit depending on what your goals are:

1. You can sync UMotion with Timeline or Unity's Animation Window to play the animation of the second character while editing the other one. You could manually sync the IK target by going through the whole animation frame by frame.
2. Sync with Timeline/Animation Window as in (1) but use a custom script to sync the IK target: Create a transform that is used as IK target outside of UMotion. Add a custom script to it that drives the position/rotation of that IK target based on the other characters shoulder bone. In UMotion, use the callback mechanism (see "Pose Editor/Options" --> "Extending UMotion" in the manual) to let UMotion execute your script. Setup the IK constraint to use your previously created transform as IK target (see IK video tutorial).
3. Configure both characters as generic. Create a new empty transform as parent of both and assign an animator component to it. Create a new generic UMotion project an drag the parent transform into the Pose Editor. Now you can animate both with a single animation clip. If you are doing a cut-scene or a movie, this is probably the preferred method.

If you have any follow-up questions, please let me know.

Best regards,

Peter

Hi Ben,

thank you very much for your support request.

Yes you can move keys in the curve editor vertically but only if the key type is capable of this type of editing. I guess you tried moving a rotation property's key vertically that is using "quaternion interpolation" or "progressive quaternion interpolation". 

Moving those keys vertically is not possible as it wouldn't generate any useful results. Switch to "euler interpolation" if you want to do this kind of editing.

This video highlights the differences between the 3 available rotation interpolation modes:

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

Best regards,

Peter

Hi ratbo,

thank you very much for your support request.

Your Unity version 5.5 is too old and not supported. UMotion requires Untiy 2017.4 or higher as mentioned on the Asset Store:

If you are still bound to Unity 5.5 for a project, you can use UMotion in a Unity 2017.4 project and export your animations to *.FBX for use in your older Unity 5.5 project.

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

Best regards,
Peter