You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to convert BabylonJS's glTF loader to 2.0 and I'm running into an issue.
It looks like there is a conflict between using array indices and the way glTF references joints. Skins references joints by name via a jointName property on a node. But now that we are using array indices, I'm not sure how this should work. Is the intention to continue to reference by name? Should this become a joint node index that points to the node index? Or a separate joint index perhaps?
The schema currently uses integers for node.jointName and skin.jointNames which doesn't make much sense. Names are not integers :)
The text was updated successfully, but these errors were encountered:
There are some pending changes from #723 (comment) that are already on the TODO list of #826 - I think that the core of your question is already addressed there.
I'm trying to convert BabylonJS's glTF loader to 2.0 and I'm running into an issue.
It looks like there is a conflict between using array indices and the way glTF references joints. Skins references joints by name via a
jointName
property on a node. But now that we are using array indices, I'm not sure how this should work. Is the intention to continue to reference by name? Should this become a joint node index that points to the node index? Or a separate joint index perhaps?The schema currently uses integers for node.jointName and skin.jointNames which doesn't make much sense. Names are not integers :)
The text was updated successfully, but these errors were encountered: