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
Describe the bug
When importing a specific FBX model, there are three aimeshes referencing bones. However, when trying to match those bones to the scene hierarchy, we discover that the names for the bones are not unique - multiple scene nodes have the same name, making it impossible to match the bone to the node
To Reproduce
Steps to reproduce the behavior:
Import the model
Check the node graph and mesh bones
notice there are multiple nodes used as part of bones such as J_Lumbar
Expected behavior
The documentation states that node names that are used as part of bones must be unique
Because they are not unique, you cannot recover the correct rigs for the different models
Screenshots
If applicable, add screenshots to help explain your problem.
CarpetHead
changed the title
Bug:
Bug: Specific FBX Node names that are part of bones are not unique
Apr 4, 2024
CarpetHead
changed the title
Bug: Specific FBX Node names that are part of bones are not unique
Bug: Specific FBX File contains Node names not unique, but are used in bones. Multiple bones reference different nodes with the same name
Apr 4, 2024
Describe the bug
When importing a specific FBX model, there are three aimeshes referencing bones. However, when trying to match those bones to the scene hierarchy, we discover that the names for the bones are not unique - multiple scene nodes have the same name, making it impossible to match the bone to the node
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The documentation states that node names that are used as part of bones must be unique
Because they are not unique, you cannot recover the correct rigs for the different models
Screenshots
If applicable, add screenshots to help explain your problem.
Man Woman Kid UVCompleteFBX.zip
The text was updated successfully, but these errors were encountered: