Hi,
thank you very much for your support request.

The easiest workaround would be to unlock the corresponding bones temporarily for the sake of importing. Go to config mode, select the locked bones from the hierarchy window. Open the "Properties" tab and set "Visibility" to "Show". After importing the animations, go back to config mode and set "Visibility" back to "Locked".

Or you confirm the dialog with yes and then reset the visibility manually afterwards.

I'm going to add a "No to all" button to this dialog in the next update. Thanks for reporting this issue.

Please let me know in case you have any questions or if the above workaround doesn't work for you.

Best regards,
Peter

Hi Hrohibil,

thanks for your support request.

Now if I want to create a specific animation/pose , should I just modify one of the ones I don’t use?

You can also just create a new one. If the existing animation is already very similar to the animation you are trying to create, then I would recommend modifying the existing one as it might be easier/faster. If the animations are very different, it might be better to start with a new animation.

Save it as fbx and then drag into my animator, connect it from the Any state node so I can call this animation anytime from my AI controller when needed.

Yes, export to *.fbx or *.anim and then assign the animation to a new state in your animator controller. Making a transition from the Any state to your new state is a good start, but the right way to do it might be depending on your AI controller so I recommend checking it's documentation.

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 import an (external) humanoid animation into your UMotion project, the animation has to be re-sampled thus additional key frames can get created. Generic animations on the other hand don't need to be re-sampled on import (the original keys are used).

If you want to tweak an animation previously created by UMotion, re-open the related umotion project, do the changes and then re-export your animation. Don't create a new UMotion project and re-import the exported *.anim file again for tweaking. Especially with humanoid, you would loose quality with every import/export loop. Furthermore *.anim (or fbx files) can't store the UMotion editing data (rig setup, animation layers, IK handle curves etc.) so if you are not using the original umotion project but instead re-import the exported *.anim file you would loose all of that editing data.

If you need to transition from one UMotion project to a new UMotion project (this is only necessary in very specific situations), make sure to import the animation directly from the old UMotion project (by selecting the old UMotion project *.asset file as animation clip you want to import). This copies all the editing-only data and doesn't need to do any re-sampling.

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 is possible with UMotion Pro. Here's how:

1. Make sure that your animation and your character are both configured as humanoid.
2. Create a new UMotion project of type humanoid and assign your (humanoid) character to the pose editor.
3. Import the humanoid animation.
4. In the export settings, set the export file type to FBX. Then select your humanoid character's *.fbx file as destination FBX file.
5. Export your animation.

Your animation is now written into the FBX file of your character and is thus using your characters rig/skeleton. Import that character in 3ds max.

Let me know in case you have any questions.

Best regards,
Peter

Hi,
thank you very much for your support request.

Looks like the RobotKyle.fbx wasn't imported correctly in your project because it already existed in your project (from the screenshot I can see that it's named TCP2_DemoRobotKyle even though in the UMotion package it's called "RobotKyle.fbx"). Search for "robotkyle" in Unity's project window and delete every occurrence. Then re-import UMotion from the asset store and see if that fixes the issue.

You could also import UMotion in a fresh Unity 2020.3 project just for playing with the examples.

I just tried importing UMotion in a fresh Unity 2020.3 project and I did not get that results, so this shouldn't be a general issue. Unfortunately Unity's package importer isn't really good at dealing with such conflicts, but I'm afraid there isn't much I can do against this.

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 doesn't have any limits in this regards, you can animate any type of 3D model/character. So if you want to animate a full body, you can do that with 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.

If you take a look at this screenshot (taken from your video):

You can see that the offset is also in the preview. How Unity treats root motion offsets (rotation and translation) depends on this settings:

It depends on what you want to achieve exactly but I would suggest trying to remove the "Bake Into Pose" check-mark from "Root Transform Rotation" and maybe also from the "Root Transform Position (XZ)". More information about root motion can be found in the Unity manual: https://docs.unity3d.com/Manual/RootMotion.html

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

Best regards,
Peter

Hi Cristian,

thank you very much for your support request.

Yes this is possible. The humanoid animation system does support the following face-rig bones natively:

• Left Eye
• Right Eye
• Jaw

You can have more bones in your face rig, but those are going to be treated as "generic" bones that means they are not part of the animation re-targeting. Animation re-targeting is a humanoid exclusive feature that allows the animation to be created for one character, but then be played on any other humanoid character (something that does not work for generic animations). In other words, your generic bones are not going to be played on other characters.

If you have updated your characters rig but already had a UMotion project, create a new UMotion project for your updated character. You can then import all animations from your old UMotion project by using File --> Import Clip (in the clip editor) and select the old UMotion project *.asset file as file you want to import.

Generic bones are not visible by default in a humanoid UMotion project. You can make them visible by switching into config mode, select the bone you want to enable from the rig hierarchy tree view. Then under "properties" set "visibility" to "show". More information about config mode:

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

Best regards,
Peter

Hi,
thank you very much for your bug report. I really appreciate your time.

Unfortunately this is a Unity bug that was already reported during the 2021.2 beta but wasn't fixed yet. Please disable the tool assistant for now or downgrade to Unity 2021.1. I'm sorry.

Best regards,
Peter