Hi,

thank you very much for your support request.

When you assign a character to UMotion for the first time, it stores all the position/rotation/scale values of all bones/transforms of that character (as reference pose). When you then re-assign the character another time, UMotion applies these stored reference pose. In your case, this "old" values seem to not be in-line with the characters current values. Thus the skinning produces this weird mesh that you see. This happens if the model was changed outside of Unity (using an external modeling application) or if you e.g. changed the scale in Unity's import settings or some other cases...

Please try the following:

1. Backup your UMotion project.
2. Assign your character to UMotion.
3. In the pose editor, open config mode.
4. In the "Configuration" fold-out click on "Apply Bind Pose".
5. Your model should look normal again.
6. Now click on "Save Reference Pose" to save your changes.
7. Go back into pose mode.
8. Unless you keyed position values, your animations should be working again. Existing position keys would still be scaled like your character was before so they might still be off by that factor.

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

Best regards,
Peter

Hi Scott,

thank you very much for your support request.

At frame 5, I dragged the red guide of pevis down. However, if you look at the UMotion curve graph, the blue curve changed. If I modified the red guide, doesn't the red curve need to be changed? It doesn't fit my concept, so it's very difficult to understand what the curve graph coordinates means. In some cases, my understanding is correct. It's going to be very crazy.

The red, green, blue in the curves correspond to the x, y and z axis of the local position coordinates. This are the same local position coordinates as shown in UMotion's channels view and (in case of default Unity) as shown in the inspector window.

The reason why the move tool gizmo colors do not line up is because the gizmo is rotated by the local rotation. The local position though is applied without being affected by the local rotation. That means that if you have 90° or more local rotation, then the colors are reversed. If you have rotations that are not a power of 90, you even have the gizmo pointing in completely other directions. This is default Unity behavior and UMotion is just staying in line with that.

You can test this yourself by creating a cube in unity. Set the local rotation y to 45. Notice how the move tool gizmo (in local mode) rotates 45 degrees with the cube. Now increase the local position x value and notice how it does not move along the red line of the move tool gizmo.

I cannot drag keys on curve graph, but sometimes I can move.

You should be able to drag all position and scale keys (except when they are greyed out). If you have rotation keys, you can only drag horizontally. In order to drag them vertically, you need to be using euler angles (because the values of quaternion based rotations are not directly editable because quaternions are 4 dimensional values that are hard for humans to directly interact with as you can't really imagine 4 dimensional values). More information regarding the different rotation modes can be found in this video tutorial: 

If you can't drag/move your keys in cases where you should be able to according to my description above, then this might be a bug and we should take a closer look. In that case, please show me a short video demonstrating the issue.

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 export to an FBX file (using "update existing one") it either adds a new animation clip to the existing FBX file or if  there is already an animation clip with the same name present in the FBX file, it overwrites that one. That's how it works on a FBX file level. Then the Unity importer comes into place importing this FBX file. It considers all the animation clips that exist in your FBX file as one large combined animation clip. You can then define which section of this "combined" animation clip you want to import as a separate animation clip defined by a start and end frame. So chances are, that the start/end frame in your import settings aren't correct (thus you're getting parts of a different animations mixed together).

For more information about how the animation import works in Unity, please checkout the related Unity manual chapter: https://docs.unity3d.com/Manual/class-AnimationClip.html#ClipProperties

If this doesn't help you solve your issue, please show me a video of what you're trying to do step-by-step. Then I get a much deeper insight into your issue and can provide a less generic answer.

Best regards,
Peter

Hi Scott,

thank you very much for your support request.

How does the position curve of the hips of your character look like? Maybe you haven't offset the position of all key frames of the hips (that's why it jumps back at some frames). You can use the curves view to easily adjust multiple keys at a time. Tip: Use the eye icon shown in the animated properties list view to hide all but the Y curve.

Btw. if you want to add offsets to an existing animation that has a lot of key frames (e.g. a mocap animation), instead of having to offsetting each key frame manually, you can use an additive animation layer to add an offset curve on top of the existing animation. Please check out the animation layer chapter in the manual for more information. There is also a video tutorial in which I'm using this feature in practical use-cases: 

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

Best regards,
Peter

Hi,
thank you very much for your support request.

Exporting as a fresh FBX file does only include the rig and the animation (not the mesh), that's intended. If you want to export your animation together with the mesh, then you have to use the "Update Existing File" mode and select your character's FBX file as destination file.

You mentioned that you've already did that, please verify that your settings are correct (e.g. that you've really selected your character's FBX file as destination file). Also check if there are any warning/error messages shown in the export log window. Before importing the FBX into an external modeling application, you can verify if the animation was added correctly to the character's FBX file in Unity. If the animation shows correctly in Unity, then the issue must be related to the import settings of your 3D modeling application.

For more information, you can also take a look at the related chapter in the manual (simply press on the question mark button in the export settings window to open the related manual page). You might also want to check out the FAQ section in the manual.

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

Best regards,
Peter

Hi Elsiehar,

thank you very much for your support request.

This might be an issue with how the IK is setup. Please try the following:

1. Creat a new UMotion project
2. Assign your character
3. Open config mode and make sure that your character is in a T-Pose (standing straight, both arms stretched to the side). If it is not, you might want to try pressing the "Apply Bind Pose" button. If that doesn't help either, you can also manually rotate the bones. Once you fixed the pose, click on the "Save Reference Pose" button. For more information about config mode, see this video tutorial).
4. Execute the IK setup wizard.
5. Import your animation and convert it to IK again.

Does this fix your issue? If not, please send me your character, the animation you are importing and the related umotion project file as a *.unitypackage via the email support form (or request a link to my dropbox via said email form if file size is too big). That way I can make further investigations.

Best regards,
Peter

Thanks for posting the video.

Your UMotion version is very dated. Please try to update to the latest version from the asset store which should be V1.25p03 as of the time of writing.

Please let me know if you need any further assistance.

Best regards,
Peter

Hi Fatih,

thank you very much for your support request.

I'm not 100% sure I understand your question so I'm giving you some general information in the hope that it answers your question:

IK pinning a foot means that it's IK target stays at the current world space position. So even when you move the hips, the pinned foot stays in place. When you un-pin the foot, it again moves with the hips.

If your hips move when you move your foot, then you have made something wrong when creating your character (as that would mean that the hips are a child of the foot and not the other way around).

For more information regarding IK pinning, you might want to watch the IK pinning video tutorial:

Does that answer your question, if not, please show me a video or explain in further detail what problem you have. I would be happy to help.

Best regards,
Peter

Hi Peter. Thanks for the speedy response. On further testing, it now seems that the problem lies with Speedtree. When I export the tree as an .st model specifically for Unity, the rig is missing and there is no option to include it. However, when I export as an .fbx model, I have the option of including bones. And voila, the rig is imported and can be configured for animation with UMotion. Thanks for your help!

Hi,

thank you very much for your support request.

In UMotion bones are always oriented in such a way, that they point to the next child joint in the hierarchy. You can not rotate the visual representation of the bone in UMotion. If you want to make adjustments to your rig (like adding new bones, adjusting vertex weights, etc.) you have to use a 3D modeling software in order to do so. But that doesn't mean that you have to redo the whole rigging, it's enough to make the adjustments that you want. Mixamo only works with human like chracters, yes.

Yes you can add new "helper" bones that are not binded to the mesh of your character in UMotion. There are also a few settings related to the visualization of bones/transforms that can be useful to get a cleaner looking rig. Both is explained in this video tutorial:

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

Best regards,
Peter