Hi Toni,

thank you very much for your support request and for purchasing UMotion Pro.

By default, non-humanoid bones/transforms are locked  in a humanoid UMotion project (i.e. they don't draw a gizmo in the scene view, are not included in the exported animation and are not shown in the clip editor). You can unlock a bone/transform by selecting it in config mode (in the Rig Hierarchy), then under "Properties" set "Visibility" to "Show".

By clicking on the black info icon on the upper right corner of the "Configuration" foldout, you get linked directly to the corresponding page in the manual that explains all the different "Visibility" options.

If you have any further questions, don't hesitate to ask.

Best regards,
Peter

Hi,
thank you very much for your support request.

Yes you can exclude those files from your version control.

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

Best regards,
Peter

Hi Megakeep,

thank you very much for reaching out.

I honestly wouldn't approach this situation like this. If you are creating this for a static cut-scene or a movie, make your character "generic". "Humanoid" only has advantages if you want to use one animation on multiple characters (animation retargeting) but comes with the additional difficulties and lower animation quality. Generic plays an animation exactly as you authored it (best quality) and works very straight forward. Then create an empty "Root" GameObject and attach an Animator component to it. Make the character and the car a child of the new "Root" and remove the Animator components from the character/car. Now create a "generic" UMotion Project for and assign your "Root" to the Pose Editor. You can now animate both the car and the human and they still move independently.

For more information regarding IK, Child-Of and IK Pinning, please check out the related video tutorials in the video tutorial chapter of the manual.

Another way would be to animate both objects (the car and the character) independently and use Unity Timeline to synchronize them. UMotion's "Sync" button allows you to edit animations in the Unity Timeline context (demo video). More information can be found in the "Unity Timeline Integration" chapter in the manual.

If you are doing a game where the player controls the character at runtime (i.e. walks near to the car, then presses a button to enter the car), this is a whole different story and can't be approached very well with regular "static" animations. You would need path finding to move the character close enough to the door, then use runtime IK solutions like Unity's new IK rigging package to adapt the animation to any offsets that result in different player positions etc. Inspect the way how the GTA titles approach this problem.

Let me know if you have any follow-up questions.

Best regards,
Peter

Hi Quintin,

thank you very much for your support request.

You can set "visibility" to "locked" in the config mode (for the props). This ensures that the props are not included in the exported animation data and that there is no visible representation of the props transform in the UMotion editor.

If you really don't want it to be included in the project, then you can use the UMotion callback system to write a short script that just moves the prop as if it would be parented to the hand (but is not an actual child in the hierarchy). More information regarding the callback system can be found in the manual at "Pose Editor --> Options" headline "Extending UMotion".

public class PropPreview : MonoBehaviour
{
    public Transform Prop = null;
    
    private void UMotionUpdate() // <== Use this name in the UMotion callback settings
    {
        Prop.SetPositionAndRotation(transform.position, transform.rotation);
    }
}

(Wrote the script out of my head --> untested.)

Assign this script to your UMotion prop anchor and assign the prop you want to preview to the "Prop" field. Make sure that the prop is a separate GameObject and NOT a child of the actual character. Feel free to further improve this preview script (e.g. to contain references to all props and show them as needed).

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

Best regards,
Peter

Hi David,

thank you very much for your support request.

Please refer to the UMotion manual at "Clip Editor --> Import/Export". There is a nice table that compares the features each animation format supports. As you can see on the table, the FBX file format does not support animating Unity specific component properties (like the blend shape weights which are a sub property of Unity's renderer components).

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

Best regards,
Peter

Hi Peter,

Many thanks you for your kind offer of additional help.  I finally had time to get back to this project today, and I find that I am unable to recreate the problem.  This means that either I am unknowingly doing something different that's critical to getting it right, or the latest update of Unity has somehow had a positive impact on clearing up the problem.  If I find myself having this "problem" again, I will re-check this post for advice and ask for your kind help if needed.

Regards - Owen

Hi,
thank you very much for your support request.

This is very easy:

1. Create a new UMotion project for your sub machine gun. Usually you would just temporarily create an instance of your sub machine gun in your Unity scene. Then create a new "generic" UMotion project and drag & drop the sub machine gun (scene instance) into the pose editor's "Animated GameObject" field.
2. Import the animations you want to edit into UMotion ("File --> Import Clips"). You can either select the whole *.fbx and then use the ticks next to each animation clip to select which animation you want to import. You can also drag & drop separate animation clips from Unity's Project Window into UMotion's import window.
3. Edit the animation to your liking.
4. Open the settings by clicking on the gear icon. Change export type to FBX (binary or ascii is totally up to you). Set "Write Mode" to "Update Existing File". Then under "Destination File" select the "SubmachineGun_Animations.fbx" file.
5. Export your animations ("File --> Export --> ..."). The changes are automatically written into the *.fbx file.

Here are some related video tutorials for completeness:

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

Best regards,
Peter

Hi Kev,

thank you very much for reporting.

This seems to be a Unity bug in older releases of Unity 2020.2. Please update to the latest Unity 2020.2 release (I just verified that this issue does not appear in Unity 2020.2.6f1).

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

Best regards,
Peter