Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Full Body Tracking on Custom Avatar in Unity 2022.3.16f1 #51

Closed
LoganLane opened this issue Jan 7, 2024 · 3 comments
Closed

Comments

@LoganLane
Copy link

Hello,

I'm currently working with Unity version 2022.3.16f1 and Movement version 4.0.1, and I've encountered an issue related to full body tracking on a custom avatar, initially designed in Blender. Following the guidelines provided in the documentation (link), I've imported the avatar into Unity as an FBX file.

After setting the animation type to Humanoid and enabling Translation DoF for the avatar configuration, everything appeared normal under the "Muscles & Settings" options, with all avatar parts moving correctly.

The problem arises when implementing full body tracking. Using my Quest Pro, I observed that the arm movements of the avatar are not tracking accurately. This issue persists even after testing with Unity's standard Robot Kyle avatar, suggesting that the problem may not be exclusive to my custom model.

I am including a video clip demonstrating the specific tracking issue, along with the avatar file I've been using. Any insights or suggestions to resolve this tracking issue would be greatly appreciated.

Thank you for your assistance.

Avatar.zip

bug.mp4
@andkim-meta
Copy link
Contributor

Hello, we have reproduced this issue on Unity 2022.3.16f1 and can confirm that it is present in Unity 2022, but not in Unity 2021. It looks like there is a change in how animation jobs work when root motion is enabled on the animator. We are currently looking into the issue, but for now, please try disabling the "Apply Root Motion" option on the Animator component of your character.

@LoganLane
Copy link
Author

Disabling "Apply Root Motion" resolved the issue. Looking forward to the future fix. Thanks!

@sohailshafiiWk
Copy link
Contributor

The fix for this specific root motion issue has landed in the #dev branch, and it will be merged into #main in the near future. If you run into more problems please create a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants