Simen Andresen

After doing some digging in the source I managed to get the sub_obj name with the following: ``` javascript // initial setup const decoder = new dracoDecoder.Decoder(); const buffer =...

Happy to help! :smile: Btw. there seems to be a problem mapping the names to the right sub objects. (Seems to be a problem with `decoder_webidl_wrapper.cc`'s use of unordered_map ->...

#408 should fix getting the correct name for each sub_obj's face

For completeness (with the fix from #408), this is how one could the relationship between a mesh's faces and corresponding sub object name: ``` javascript // initial setup const decoder...

> and i meet the same problem: there is an extra name named name, and those names are not mapped with subObject_id... yep, found that too, and as you mention...

Thanks for your reply @FrankGalligan . Not sure why, but with your code I only seem to get the material names, e.g. `surface-style-408402` as in the example obj in https://github.com/google/draco/issues/401#issuecomment-393126211....

@FrankGalligan see this fiddle: https://jsfiddle.net/turbowhale/h0t179pa/25/ where I'v tried without using my patch. Notice that only the material names are written out The original obj file looks like this: ``` mtllib...

Here's a fiddle with my patch https://jsfiddle.net/turbowhale/h0t179pa/42/ Notice that the object names are logged `cube-object` etc..

I got the same problem when migrating from Webpack to Vite. @berry4u did you solve this in the end?