Bone components that are assigned to bones that aren't in the top level of the hierarchy aren't imported #123
Comments
Exairnous
added a commit
to Exairnous/hubs-blender-exporter
that referenced
this issue
Sep 19, 2022
This fixes bone components not being imported if they aren't in the top level of the hierarchy. Note: The gltf bones aren't in the same order as the armature bones, this is by design. I considered using the bone order to map the gltf bones to the armature bones (potentially faster), but decided it would be too fragile, and mapping it would have potentially been slower anyway. I loop through the bones in the armature and access the gltf bones by name rather than the other way around because Blender's internal data structures are mostly based on linked lists, so looping over it is much more performant than doing lookups for each item.
keianhzo
pushed a commit
to keianhzo/hubs-blender-exporter
that referenced
this issue
Nov 7, 2022
This fixes bone components not being imported if they aren't in the top level of the hierarchy. Note: The gltf bones aren't in the same order as the armature bones, this is by design. I considered using the bone order to map the gltf bones to the armature bones (potentially faster), but decided it would be too fragile, and mapping it would have potentially been slower anyway. I loop through the bones in the armature and access the gltf bones by name rather than the other way around because Blender's internal data structures are mostly based on linked lists, so looping over it is much more performant than doing lookups for each item.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Bone components that are assigned to bones that aren't in the top level of the hierarchy aren't imported
The text was updated successfully, but these errors were encountered: