-
-
Notifications
You must be signed in to change notification settings - Fork 35.2k
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
Store both original and sanitized node names in FBXLoader #26637
Comments
Would you be okay if the loader stores the additional information in the Other loaders rely on |
Thanks for the quick response!
Yes, sounds good to me. |
Would you like to file a PR? |
OK, I will do that. |
Description
I've noticed that the FBXLoader does not include the original node names when loading FBX files. The current implementation only provides sanitized node names, which makes it difficult to identify and manipulate specific nodes in the loaded FBX file based on their original names.
Solution
I would like the FBXLoader to store both the original node names and the sanitized node names from the FBX file and make them accessible in the resulting three.js objects. This would allow users to easily identify and manipulate specific nodes in the loaded scene using either the original or sanitized node names, depending on their needs.
Alternatives
One possible alternative is to modify the FBXLoader source code and create a custom version that includes the original node names in addition to the sanitized names. However, this is not an ideal solution because it requires maintaining a separate version of the loader and manually updating it when new versions of three.js are released.
Additional context
Including both the original and sanitized node names in the FBXLoader would provide a more complete representation of the FBX file structure and improve usability for developers working with FBX files in their projects. This feature would give developers more flexibility in choosing how they want to identify and manipulate nodes in the loaded scene.
The text was updated successfully, but these errors were encountered: