search

UPC-ViRVIG / MMVR

Repository for the SCA 2022 paper "Combining Motion Matching and Orientation Prediction to Animate Avatars for Consumer-Grade VR Devices"
https://upc-virvig.github.io/MMVR/
Other
58 stars 7 forks source link

Custom Database - Two legs going up #6

Closed tejaswiniiitm closed 1 year ago

tejaswiniiitm commented 1 year ago

Hi @JLPM22

To start working with custom DB, as first step, I have created a MotionMatching DB with custom animations( .bvh files). I am using direction predictor network given by you only in this initial step.

When ran in Unity with custom generated DB and with the direction predictor model given by you, the skeleton drawn by gizmos was rendering okay. But the legs meshes are going up.
To understand the issue better , I have attached the screenshot of it.

Do you have idea of what is causing the issue? After going through some part of the motionmatching code, got to know that SkeletonTransforms are computed in MotionMatchingController.cs, and those SkeletonTransforms are applied to the transforms of avatar's Animator in MotionMatchingSkinnedMeshRenderer.cs. Since it looks like its working correct till computation of SkeletonTransforms, not able to understand why avatar's mesh rendering is not proper!

NOTE:

  1. These bvh animations were not recorded, but were made using tools like MotionBuilder and exported as .bvh, at this first level. Made sure that skeleton bone names match with the names given in your bvh files.
  2. And I viewed the .bvh file if it's playing as expected using this online tool. The skeleton was animating as expected using the bvh files.
  3. While generation motion matching DB, I just added custom .bvh files, and didn't change any other parameters of the asset. (used the same parameters you used in the project incl. skeleton to mecanim, Hips fwd local vector (0,0,-1) etc.

debug Thankyou!

.

tejaswiniiitm commented 1 year ago

This issue is resolved. I was using the t-pose given in this project, which has rotation axis order different from the custom bvh files. After I used t-pose also with the same axis order as that of the remaining custom bvh files, the issue resolved.