-
Notifications
You must be signed in to change notification settings - Fork 2
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
gltf node.name are not unique #50
Comments
Problematic cases are now fixed since it is now possible to not relay on gltf node names. (02013c3)
|
I avoided the issue for now by renaming the relevant nodes with a prefix. Here's how I use it for multiple animations: |
Actually, that should not be necessary anymore (the repo README.MD is outdated since it has not been updated in almost a year). There might be bugs with it but the expected behavior is that every gltf.animation entry in the gltf creates one "anim_{i}.rdm" file. |
I haven't tried as the name collision stopped me there. |
The code currently assumes that node names are unique which causes bugs with a gltf created by blender.
This problematic gltf has an animation channel that targets a node that is not even part of the mesh skin or otherwise part of the scene (
glTF Validator: NODE_EMPTY
) and thus could not even be animated. Problem is that there is a second node that has the same name and that node is part of the mesh skin.But since only the name is the same between these two nodes but not their TRS properties resolving to the wrong node breaks the animation.
The text was updated successfully, but these errors were encountered: