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
The importer could have toggles to choose how to import some features:
Bones
Animations
Combine primitives
Materials
Textures
In my case I don't want to import animations, nor bones. I added those options myself, but it's not that good since I want to receive your future updates without trouble. Also, your GLTFSceneImporter could be splited by module like (MaterialImporter, MeshImporter, HierarchyImporter, TextureImporter, AnimationImporter) that way it would be easier to maintain the code, the class now has 2000+ lines of code.
Thanks for the good work, you're doing an amazing job!
The text was updated successfully, but these errors were encountered:
Thank you for the suggestion! We have a proposed architecture #259 that does show how we want to split the classes up easier. We may have some time coming up to implement it!
The importer could have toggles to choose how to import some features:
In my case I don't want to import animations, nor bones. I added those options myself, but it's not that good since I want to receive your future updates without trouble. Also, your
GLTFSceneImporter
could be splited by module like (MaterialImporter, MeshImporter, HierarchyImporter, TextureImporter, AnimationImporter) that way it would be easier to maintain the code, the class now has 2000+ lines of code.Thanks for the good work, you're doing an amazing job!
The text was updated successfully, but these errors were encountered: