Hi Maxxx,

thank you very much for your feature request.

While being useful in your use case, it's not guaranteed that everybody always wants the move tool to automatically be in global space (and the rotate tool to automatically be in local space). It really depends on the current situation but also on personal preferences. Unity for example is also not changing the editing space automatically when switching from the rotate to the move tool. I think in order to be consistent it's better to keep the current "manual" behavior.

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 should work, but I would recommend changing your character from "humanoid" to "generic". Humanoid is great when you want to share animations between multiple characters but is less precise (e.g. fingers can have slightly different poses in the exported animation, hands might not be exactly at the handle,...). Humanoid is also a bit more CPU intensive. Generic plays the authored animation directly (without converting it into the lossy humanoid animation format). Here is a detailed blog post about what humanoid is: https://blogs.unity3d.com/2014/05/26/mecanim-humanoids/

To animate your character, make it a child of the quad bike. Create a new UMotion project and then drag and drop your character (not the whole quad bike) into the Pose Editor of UMotion. If you want to keep the hands on the steering handles (that are controlled via physics/script), you need a runtime IK solution on top of the regular animations. Please note that UMotion is not a runtime IK solution (IK is only executed at authoring time in UMotion).

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 generation of the root motion curve for humanoid is a bit buggy in Unity (as the root position always seems to be based on the center of mass i.e. it is slightly different depending on the pose of the character, no matter what you have authored in the original clip initially or what you have configured in the clip Inspector settings).

That's why UMotion offers a feature to generate the root motion curves (instead of Unity) in the intended way. To enable this feature, open the clip settings in UMotion (the gear icon) and check the following checkbox:

If this doesn't solve your issue, please post a few screenshots showing your problem.

Best regards,
Peter

Hi,
thank you very much for your support request.

If the animation previews correctly, then UMotion exported the animation correctly (so the problem must be somewhere in the setup of your character/its animator/its avatar). It's hard to diagnose this with the current amount of information. A few guesses:

1. Maybe you've added a game object as parent of your character that scales the character (or offset's its position)?
2. Maybe the avatar setup of your character is not correct (select your character in Unity's project window, then in the Inspector click on the "Rig" tab and then on "Configure..."; all bones should be green; the rig tab should also show no errors)?
3. Toggle the "Apply Root Motion" checkbox in the Animator component and see if that changes something.
4. Toggle the "Root Motion Position(Y) - Bake Into Pose" in UMotion and see if that change something.

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 rotation modes, please check out the following video tutorial:

The dialog message you get indicates that the rotation mode of the copied keys is e.g. "euler interpolation" but in the destination animation clip the same rotation property is in e.g.  "quaternion interpolation" mode (and already has keys). UMotion is then asking you if you want to update the rotation mode so that they match:

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

Best regards,

Peter

Hi goldfire,

thank you very much for your support request.

What is the recommended approach to handling this type of workflow?

You're approach is correct. The question is, why are there at least two transforms named "ORG-thumb_01_R" in your character's hierarchy (at runtime)? Try to fix that and your approach should work fine.

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

Best regards,
Peter

Hi,
thank you very much for your support request.

Bones are only the connection between joints (joints are the spheres at the beginning and end of the bone). The joint is the thing that really manipulates the mesh when it is rotated and the bone (= the connection) is just a visual helper. UMotion draws bones between every joint <-> joint connection, so in your case this means that there are several joints (floating in the air) that are a child of the shoulder joint which UMotion then visualizes with a bone connection. You can select those individual joints by clicking just on the sphere (= joint) of the end of the bone.

In UMotion's config mode you can disable joints you don't need by setting the "Visibility" to "Lock" or "Hide" (see manual) in the properties tab. Use the "Parent Link" setting to configure the appearance of a bone connection between joints.

In case your joints are not used anyway, it's probably a cleaner approach to completely remove them from your character in a 3D modeling application. This safes you a bit of run-time performance (the less joints, the less work the CPU/GPU has to do when playing an animation on your character).

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

Best regards,
Peter

Fixed in UMotion V1.22p09 (currently pending asset store review, should be available in the next one or two days).

Thanks for reporting.

Best regards,
Peter

Hi,
thank you very much for your support request.

In case the bones/transforms do not exist anymore (on the actual character model), UMotion will show a "Cleanup" button in config mode. When pressed, it is going to remove all bones/transforms that can't be found in the character model anymore.

In case your character model still has the bones, you can't remove them completely from the UMotion project but you can tell UMotion to ignore them. Therefore, open config mode and select the bone/transform(s) you want to ignore. Then in the "Properties" tab set "Visibility" to "Lock". UMotion now won't show these bones/transforms in the scene view and animated properties list. Furthermore the bones are not included in the exported animation file.

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

Best regards,
Peter

Hi renel,

thank you very much for your support request.

Yes with UMotion you can animate humanoid animations (also generic/legacy animations). You can use UMotion also when pausing the game (this might be interesting in your situation, if you want to first pick up a sword in your game). With UMotion Community (free) you can create new animations and with UMotion Pro you can create new ones or edit existing ones.

As a starting point, check out the quick start video tutorial first:

This video might also go into your direction:

The FPS video tutorial is also a good starting point, yes.

I have to go into run time as the arms don't show until i pick up a sword...

You can check the "Hierarchy" window to see what model has been created for the arms. You can copy it and then paste it outside of play mode (then you can also animate it when not playing the game).

My tip: Use UMotion Community to check if you are able to create a new very basic animation for your hands. If that works, you can use UMotion Pro to edit your existing animations.

In case you have any questions/issues, don't hesitate to ask.

Best regards,
Peter