-
Notifications
You must be signed in to change notification settings - Fork 75
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
FBX output #7
Comments
@alighofrani95 , Hi, in this repo, output pose:(n_frames, 24, 3, 3) is rotation matrix format. Actually, in the VIBE repo output .fbx scripts, need to transform the Axis-angle format(n_frames, 24, 3) to rotation matrix format(n_frames, 24, 3, 3), so, you can directly use the rotation matrix format output to do you want, just not use https://github.com/mkocabas/VIBE/blob/03ed50d3121c37a4abfcc25dc995f08b63fd7f1f/lib/utils/fbx_output.py#L81.
Hope that is useful to you! |
@CvHadesSun Thank you for your reply.When I transform the rotation matrix format to fbx by use my own method,I find the results is upside down,how to overturn the Axis-angle format or rotation matrix format. |
Could you please change the README.md so that it reflects this nuance? Currently it says the poses output will be in the shape (num_frames, 72), not (num_frames, 24, 3, 3) |
I really thank you for sharing this state-of-the-art model.
I just try to export the .fbx file (from vibe implementation) by it seems that there are some differences between vibe and pare in the SMPL pose parameters shape.
the shape of pose in vibe is (n_frames, 72)
but in pare is pose (n_frames, 24, 3, 3)
How can I export .fbx from the .pkl file generated via PARE?
Best regards,
The text was updated successfully, but these errors were encountered: