Ahh interesting. Well, hopefully, the branch that I created can at least provide a framework for the correct dataset.
Upon further testing, I also received the 404 on /ThirdParty/draco_decoder.wasm error. I suspect that this is a Webpack related issue. Essentially, our configuration does not have the draco decoder necessary to process the dataset that we have provided. Does that seem reasonable to you?
Unfortunately, I do not know of a solution for this issue. Any input from the rest of the community?
A few relevant threads:
-
1.4 release throws RuntimeError in the browser console · Issue #653 · google/draco · GitHub
Can't Load GLB model as draco_decoder.wasm and draco_wasm_wrapper.js not found - Questions - three.js forum
Looking forward to learning more.
Best,
Sam