-
Notifications
You must be signed in to change notification settings - Fork 323
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
Imported armature issues #324
Comments
I don't think there is any issue here.
I will set this issue as "enhancement", because we probably could fake some rotation on created bones to have them visually better aligned. |
Thank you, I do hope it will it will be improved, so it's easier to see the structure of the bones and work with them more easily. Right now it's a bit difficult. If you need more gltf files like this i have a bunch more. |
Bones are rotated and sized plausibly in gltf-blender-importer. At least non-leaf bones Basically, we pick a rotation cr(b) for each bone b, and the local-to-parent T(b) for that bone is replaced with T'(b) = cr(pb)^{-1} T(b) cr(b) where pb is the parent of b. Then when you compose with the parent, T'(pb) T'(b), the cr(pb)^{-1} at the left of T'(b) is cancelled out by the cr(pb) on the right of T'(pb), and so on up the tree, so it doesn't end up affecting the end result of skinning. Then you just need to pick a cr(b) that will look good. You have to maintain the relation between T'(b) and T(b) when you animate pose bones too. This is probably the most annoyingly complicated thing in that importer, but see this comment about picking the edit bones and this comment about picking the pose bones during animation. |
Thank you so much! I have tried the importer and everything works fine, even the animations! Now i can work with it alot easier. Kind regards, Quinten |
Thanks for pointing me to that algo. Julien |
Hummingbird_Gltf.zip
Whenever i import this gltf file the armature comes out weird. Bones are uncorrectly sized, unconnected to the parent, and rotated.
The text was updated successfully, but these errors were encountered: