Our coder says should demonstrate the issue.
Playground Link
1 Like
The metadatas are available on the parent transformNode
cc @bghgary to confirm it is the expected behavior
Yes, this is currently the expected behavior. When there n primitives of a mesh in the glTF, the loader will create a transform node with n meshes representing each primitive. The glTF extras will end up on the transform node in this case.
2 Likes
After investigating that path, we made it work with that in mind by accessing the parent being the TransformNode to grab the metadata.