Hi,

thank you very much for your support request.

When dropping the Gameobject into the pose editor I get the 'Hips' already defined.

That happens when you drop a humanoid character into a UMotion project initially created for a different humanoid character. A separate UMotion project has to be used for each of your characters. If you're character is of type humanoid and you want to use/edit a humanoid animation you created for a different humanoid character, just export said humanoid animation from the UMotion project A and import it in UMotion project B (with the correct characters assigned to the pose editor respectively).

For IK rigging, you can use the IK Setup Wizard in UMotion. It automatically creates IK chains for the legs and arms. Unless you're doing something like a "playing the piano" animation where precise finger movement is very important, I would recommend not to use IK for the fingers. It's usually easier to just use the finger sliders in the muscle tool assistant. Another trick is to select each finger bone, then use the rotation tool which will equally apply the rotation on all finger bones at once making it bend nicely.

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 working with humanoid, I highly recommend setting "Write Mode" to "Update Existing File" (in the UMotion export settings). Then select the fbx file of the character that you have assigned to the pose editor as destination file. When you now export, your animation is written into the FBX file of your character. Meaning that it is imported with all the correct settings automatically.

For more information, please check out the manual (click on the question mark button in the export settings to open the corresponding manual page).

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

Best regards,
Peter

Hi Scott,

thank you very much for your feedback.

I'm sorry to hear that you are having such a hard time working with UMotion and Unity Timeline.

When you want to modify a timeline animation, you need to make sure that you export into the correct directory so that the animation that is used in Unity Timeline is updated/overwritten. If you select an animation clip in your Unity Timeline and then click on the animation clip field shown in the Inspector window (and if you have Unity's project window opened), Unity is going to highlight you the file in your project window.

Then open UMotion and make sure that in the export settings, the export directory points to the exact same directory. In order to avoid confusions, I also recommend that you use unique names for your animation clips throughout your whole Unity project.

If the export directory is not correctly setup in your UMotion project, UMotion is going to export the animation to a different location in your project. Unity Timeline is then still using the old animation.

In addition, the animation clip which was modified with a weapon does not work on the original character which has not the weapon because of rig differences.

Humanoid animations are rig independent (due to animation re-targeting). So if you create a humanoid animation for humanoid character A, it can be played on humanoid character B as well. But please note that none humanoid bones (e.g. additional weapon bones) might not translate well between characters because re-targeting only works on humanoid bones.

If you just want to edit an animation of your character with the weapon, you should be able to directly work on that character (and his weapon) within UMotion. There should be no need to remove the weapon before working with UMotion. What problem did let you think that this is necessary?

I hope this sheds some light into your situations. If you have any further questions, please let me know.

Best regards,

Peter

Hi Elsiehar,

thank you very much for your support request.

Yes this is expected, that's how IK works. The IK rig (the blue bones) are controlled solely by the IK algorithm. This algorithm automatically adjusts the rotations of the individual leg bones in such a way, that they reach the IK handle of the corresponding foot. So if you select the IK handle (this is the wired cube at the ankle) and move it with the move tool, your legs are going to bend/rotate so that they end up at the IK handles position (FK/IK Blend needs to be at 1). By moving the pole target, you can define where the knee is pointing to.

The FK rig on the other hand gives you full control by allowing you to rotate every bone manually with the rotation tool. As you might already think, both methods have their advantages that's why the FK/IK Blend control exists which allows you to switch between them (even during an animation) so that you can use the best fitting solution for your animation scenario.

I recommend that you play around by moving the IK hande/pole handle so that you get the hang of how things behave. Btw. rotating the IK handle is going to rotate the foot bone.

For more information, please check-out the IK video tutorial:

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

Best regards,

Peter

Hi Superip,

thank you very much for your support request.

Make sure you are using the latest version of Unity Timeline (you update Unity Timeline via the Unity Package Manager). Also make sure that your UMotion Version is 1.15p02 (there was a bug fix that fit's the symptoms you described in 1.15p02). You can see what version you have installed by clicking on "Help --> About Umotion..." in the UMotion Clip Editor. You can update UMotion via the Asset Store. After performing the update, please verify that the version shown in "Help --> About Umotion..." reads 1.15p02.

If that does not help, please show me a video illustrating your problem so that I can take a closer look.

Best regards,
Peter

Hi,
thank you very much for your support request.

The project file contains all the rig configuration (e.g the IK setup) of your character, all the animations you create, etc. The project file is "per character" and should/can not be used with other characters. So you would create one UMotion project file per character.

Escpecially when working with characters that are configured as humanoid, you should not create a fresh UMotion project every-time you want to make changes to the same animation (as that would require to import the animation every time into the UMotion project, make your changes then export again,...). Not only would it be tedious, but as the humanoid animation system requires re-sampling of the animation on every import/export, this will also loose information --> reduce quality if you repeat this step multiple times.

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 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