-
Notifications
You must be signed in to change notification settings - Fork 325
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
Preserve Mesh instancing #45
Comments
You're finding some prime bugs, @davilovick! Much appreciated. This is obviously a major deal; instancing is critical. We just never happened to use it in any of our past work, so it never came up. Adding to 1.0 release criteria. |
Thanks! Great work Best regards! |
Here I've created a PR that solves that issue :) |
Fantastic! Celebrating Thanksgiving here at the moment, but thanks so much for the PR; I'll look it over ASAP. |
Teapots work great! This .fbx however does not: Pretty tragic. I'm going to dig in a bit and see I can figure out what's going on. |
Oh -- of course. It's the node name collision bug again. That's on me to fix. I'll accept your PR & just do the little stye tweaks myself. Thanks again! |
glTF allows to have several Nodes sharing the same Mesh.
It would be great if FBX2glTF supports that feature :)
Several FbxNode instances can share the same FbxMesh (obtained by the getMesh() method), but right now the code allways creates a new mesh, instead of using the mesh created before in that cases (File: Fbx2Raw.cpp, line 895)
Best regards,
David Ávila Membrives
Wave Engine team member
The text was updated successfully, but these errors were encountered: