Hi,

thank you very much for your support request.

From a game design perspective, I would recommend to completely decouple the VR camera (VR head) from the animated head bone so that the variations of the idle animation don't add artificial movement to the VR camera (this is going to make players nauseous). Jerky camera movement can make even the most experienced VR users nauseous (see climbing physics of "Boneworks").

In UMotion, you could scale down the curves to reduce the variations (make sure that your rotation curves are in euler rotation mode for this to work). Just select all keys of an animation curve, then use the box tool (i.e. the blue bar appearing next to the selected keys) to scale down the curve.

You are going to need UMotion Pro to import an existing animation.

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

Best regards,
Peter

Hi,
thank you very much for your support request.

This keys are automatically created by the Child-Of constraint (which is used by the IK Rig by default). Please check out the following two video tutorials to learn more (it also explains the purpose of this keys):

If you don't need the IK Pinning feature, you can remove the Child-Of constraints from your IK rig. No additional keys are going to be created in that case.

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

Best regards,
Peter

Hi,
thank you very much for your support request.

There is currently no way to build a custom property controller that drives multiple channels at the same time (in your case the rotation of the elbow and the blend shape weight). You could either adjust the blend shape manually according to the current rotation value or you could write your own driver script that does that for you.

For the scripting approach, add a new MonoBehaviour to one of the transforms of your GameObject that looks something like that:

public class ElbowMorphDriver : MonoBehaviour

{

   public float InputValue = 0f; // Access this property via a "Custom Property" constraint from UMotion

   [SerializeField]private Transform ElbowJoint;

   [SerializeField]private SkinnedMeshRenderer BlendShapeSmr;

   // This method is going to be called every time UMotion re-calculates the current pose.

   public void UMotionCallback() // Let UMotion call this method (enter callback name at Pose Editor --> Options -->

                                                   // Extending UMotion --> Callback Name; check out manual by clicking on the black info button)

   {

      // According to the InputValue, set elbow joint rotation and blend shape weight

   }

}

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

Best regards,
Peter

Hi,
thank you very much for your support request.

To learn more about the humanoid avatar, please read Unity's blog post about the humanoid animation system: https://blogs.unity3d.com/2014/05/26/mecanim-humanoids/

It basically defines the T-Pose for each character and uses that as the reference pose for all the animation re-targeting. The less accurate the T-Pose of your humanoid avatar is, the more re-targeting error you are going to get.

Bind-pose is the pose that your character had in the 3D modeling application when the bones have been bound to the mesh (skinning). The reference pose is just used internally by UMotion (it is used as initial pose when an empty animation clip is created or by the IK Setup wizard to correctly create the IK rig). When you're animation has keys for all bones, none of these poses is used when the animation is exported.

To get good results when working with Unity's humanoid system, make sure that your character's avatar is setup correctly. Try use some animations (that are working well) to test if everything re-targets nicely. Then use that character for creating/editing your animations (in UMotion). When exporting to *.FBX, always export using "Update Existing File" to write the animation into the *.FBX of your character. This ensures that Unity imports the animation with the correct humanoid avatar.

And always remember: If you don't need animation re-targeting, don't use "humanoid" (but "generic" instead). Re-targeting adds additional complexity and thus issues that you can simply avoid when using "generic" instead. "Generic" also has better performance (on the CPU).

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

Best regards,
Peter

Hi,
thank you very much for your support request.

Please make sure that in the "Rig" tab of the import settings (shown in the Inspector when selecting your character's source file in the "Project Window"), you have set "Avatar Definition" to "Create from this model". This is to ensure that Unity generate's a humanoid avatar from your character.

UMotion requires a humanoid avatar that has been generated by Unity's model importer as it contains more information (needed to guarantee correct humanoid *.anim export) then a humanoid avatar generated via script.

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

Best regards,
Peter

Hi,
thank you very much for your support request.

If you just started your UMotion Project, the easiest way would be to create a new one. Make sure that you only drag one character into the Pose Editor (per UMotion Project). Don't modify the hierarchy of your character's transforms afterwards.

If you need to fix your existing UMotion Project, try to delete the duplicated "custom properties". You can delete constraints in config mode by selecting the bone they have been assigned to and then under the "Constraints" tab, click on the "X" button.

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

Best regards,
Peter

Hi,

thank you very much for your support request.

UMotion has two rig layers. The grey bones are on the Forward Kinematic (FK) rig layer. They can be selected and can only manipulated directly. Bones on a humanoid character can only be rotated (translation would mean that the bone would jump out of the joint, which is usually not preferred ^^).

The blue bones are on the Inverse Kinematics (IK) rig layer. These bones are driven by an IK constraint and can not be directly manipulated. To manipulate an IK bone you need to manipulate the IK Handle (the wired cube) or the IK Pole Target if existent.

To decide which rig layer the mesh should follow, use the "FK/IK Blend" channel (shown in the Channels view of each IK Target).

The quick start tutorial goes over this topic real quick, the IK video tutorial covers this topic in greater detail:

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 animate any type of rigged model. If your model is not rigged, you can animate all the separate parts (i.e. all transforms you see in Unity's Hierarchy window).

Here is a video where I'm animating a gun that has no bones but is split into separate parts:

In this video tutorial UMotion is with 4 legged models (dog/cat):

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

Best regards,
Peter

Hi,
thank you very much for your support requests.

These errors are happening because in some cases Unity is validating *.dll referenes to script files before those script files finished compiling. They are false alerts and can be ignored.

If these errors annoy you, select the UMotion dlls and disable the "Validate References" checkbox in the Inspector. Then click "Apply".

The UMotion *.dlls can be found at:
"Assets/UMotionEditor/Plugins/Application"
"Assets/UMotionEditor/Plugins/Editor"

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

Best regards,
Peter