Skip to content
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

Closed
davilovick opened this issue Nov 22, 2017 · 6 comments
Closed

Preserve Mesh instancing #45

davilovick opened this issue Nov 22, 2017 · 6 comments
Labels
Milestone

Comments

@davilovick
Copy link
Contributor

davilovick commented Nov 22, 2017

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

@zellski zellski added the bug label Nov 22, 2017
@zellski zellski added this to the 1.0 milestone Nov 22, 2017
@zellski
Copy link
Contributor

zellski commented Nov 22, 2017

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.

@davilovick
Copy link
Contributor Author

Thanks! Great work
I'm working on integrating glTF as the 3D model pipeline in WaveEngine (www.waveengine.net). And we are dealing the FBX conversion with this awesome tool :)

Best regards!

@davilovick
Copy link
Contributor Author

Here I've created a PR that solves that issue :)
#46

@zellski
Copy link
Contributor

zellski commented Nov 24, 2017

Fantastic! Celebrating Thanksgiving here at the moment, but thanks so much for the PR; I'll look it over ASAP.

@zellski
Copy link
Contributor

zellski commented Nov 28, 2017

Teapots work great! This .fbx however does not:

fir.zip

It should look like:
screenshot 2017-11-28 01 01 36

but instead it looks like:
screenshot 2017-11-27 09 47 32

Pretty tragic. I'm going to dig in a bit and see I can figure out what's going on.

@zellski
Copy link
Contributor

zellski commented Nov 28, 2017

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!

@zellski zellski closed this as completed Dec 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants