BJS Imports some GLBS with Multiple Duplicate Skeletons, while Three jsEditor and Blender Sees One?

[bghgary]

@Pryme8

If the user exported from blender its not a problem… Its from services like facebooks FBX to GLB that makes the issue.

Might be an FBX thing? The Alien head one is exported using an old Unity exporter that I wrote a long while back. It definitely had duplicate skeletons in that. IIRC, my export already tries to remove duplicates if it can, but only if the skeleton matches exactly and not subsets.

@Pryme8

But blender sees those split skeletons and merges them into one, so effectively it fixes that data problems for when we import. We should technically be doing the same thing one would imagine. It does not break any of the data, it simply consolidates it.

Just kinda figure we would want to match the main content creation tool for Babylons import export handling as opposed to doing our own thing.

We can maybe add something to the export or just a custom function to do the consolidate, but I don’t think it’s a good idea for import to do automatically. Maybe it’s okay as a flag in the import if it’s cheap?