Bugs
export fbx wrong animation crack
i export walk animation made by u motion the leg alway swing side wrong direction
Answer
Hi,
thank you very much for your support request.
Please update your UMotion version to the latest version from the asset store. Please also check out the "Exporting Animations FAQ". It contains a collection of the most common mistakes when exporting an animation. Usually when exporting to FBX, the "Update Existing File" mode is recommended (and is the default in the new UMotion versions; see FAQ for more info).
In case this doesn't solve your issue, provide some further information (a screenshot of your export settings, a screenshot showing the problem, are you using humanoid or generic,...).
Thank you very much.
Best regards,
Peter
delete umotion editor folder and press import button but version still = 1.22p14 and my fixfbx clip lost all key
delete umotion editor folder and press import button but version still = 1.22p14
Import is going to import the last downloaded version (which is 1.22p14 in your case). You need to click on "update" first, which is going to download the latest version. Then click on import.
and my fixfbx clip lost all key
That can happen if the Unity project wasn't saved before hand (File --> Save Project). Please always use a version control system (GIT, SVN, ...) when doing game development or software development in general to always be able to go back to a previous version of your project.
Best regards,
Peter
can i upload 126 mb vdo file to this forum i can't upgrade and found unwanted many bone motion
If this video is exceeding the file limit of the forum, you can either upload it to youtube (as private, if you have an account) or you can send me an email via the email support form. I can then respond to you with a link to my dropbox where you can upload your video.
Best regards,
Peter
Thank you very much for sending me the video.
The reason you're not able to update your UMotion version might be due to a Unity package manager bug. This happens in rare cases to some users where the "downloaded" version of your asset is still an old version while package manager thinks its the new one. In order to fix this, delete the downloaded UMotion version from the package manager cache and re-download it again:
You can find the cached/downloaded version at this location:
- macOS:
~/Library/Unity/Asset Store - Windows:
C:\Users\accountName\AppData\Roaming\Unity\Asset Store
Delete the UMotion version there. Then open package manager in Untiy again. It should now show the "Download" button instead of the "Import" button. Click on "Download" to download the asset again. In the meantime, remove your previous UMotion installation from your Unity project by deleting the "UMotionEditor" folder. Then click on "Import" in the package manager to import the latest version.
Please verify if UMotion is now up-to-date by click on "Help --> About UMotion" in the clip editor. The version displayed should be V1.26p02.
---
Once you're on the new UMotion version, we can tackle the export issue. In the export settings set "Write Mode" to "Update Existing File" and select your character's *.FBX file as destination file. This is writing the animation into your characters FBX file. Unity then uses the correct humanoid avatar when Unity imports the animation from the FBX thus should be fixing the issue you're having.
In the new V1.26p02 the "Update Existing File" mode is the default export mode (for new UMotion projects) for that reason.
Best regards,
Peter
Customer support service by UserEcho
Hi,
thank you very much for your support request.
Please update your UMotion version to the latest version from the asset store. Please also check out the "Exporting Animations FAQ". It contains a collection of the most common mistakes when exporting an animation. Usually when exporting to FBX, the "Update Existing File" mode is recommended (and is the default in the new UMotion versions; see FAQ for more info).
In case this doesn't solve your issue, provide some further information (a screenshot of your export settings, a screenshot showing the problem, are you using humanoid or generic,...).
Thank you very much.
Best regards,
Peter