JavaScript example should likely use webworker like OpenCTM example. about draco HOT 7 CLOSED

Are there any known technical barriers to this being implemented?

From reading how the dracomodule is used within the dracoloader, there doesnt look like there is anything that would prevent implementing it in the ctm code pattern.

If no one knows of any reason it wouldnt work, I'm probably going to take a crack at it.

The direction I'm thinking about initially taking is to split up convertDracoGeometryTo3JS so it send back the attributes as {} of transferable attributes (probably just the ArrayBuffer) and fix it up to build the BufferGeometry in the worker's onmessage. That way the worker doesnt need to import three.

Any suggestions are also welcome.

Thanks.

from draco.

Strong +1 for this. If nobody else had done it in a month or so, we'd planned to tackle it ourselves.

So, @zynga-jpetersen, go forth and do battle!

from draco.

Update on this, I tried the simplified approach, where I import the three js and draco into the worker. That both significantly increased the load times (I'm guessing from both sending data back and forth, but also all that code) and didnt result in good data since of course the THREE.Geometry wasnt transferable (I didnt necessarily expect this to work, just for a test). So as a second attempt at this I'm breaking up convertDracoGeometryTo3JS into 2 phases, 1) where it inflates the data from draco, and then 2) builds the three geometry out of the results. Once I've got that working, I should be able to take phase 1 and move it off into a worker and reuse the same code by doing the same writing the worker source trick that Obj2Loader is doing.

from draco.

Check out Babylon.js implements:
babylon.dracoCompression.ts
KHR_draco_mesh_compression.ts

And you can even use draco_decoder.wasm in Web Worker.

from draco.

I should have updated this sooner, my apologies.

I've been moved onto another project so I haven't had time to complete my refactoring.

from draco.

FYI, I've cross-filed this issue on three.js: mrdoob/three.js#13648. There is some infrastructure in three.js's examples/js/* to support workers. But currently I don't think anyone is actively working on adding worker support to THREE.DRACOLoader.

from draco.

three.js added web worker support. That can be used as an example.

from draco.