Arseny Kapoulkine

It's been a little while since I've looked at three.js so I'm not sure what the jsm/js situation is; this change for now just updates the jsm version. Feedback on...

Right - the startup latency is less of a problem here since the workers will be started eagerly when `useWorkers` is called, so it will likely overlap with the latency...

Note that in r110, morph targets weren’t included into the bounding box calculation at all in expandByObject, so the result could be too small. r111 computes the conservative maximum that...

Just to clarify that #17940 is not at fault; before that change the bounding box was computed irrespective of morph targets, What is causing this is that in this model,...

I guess, although since GLTF files can specify arbitrary starting values for morph weights, ignoring morph targets seems wrong even for the existing editor.

Mesh splitting isn't too complicated so it could be implemented I think. Are you sure the limit is 32767 vertices as opposed to 65535?

I would probably look into https://github.com/donmccurdy/glTF-Transform for this kind of involved processing - I don't know OTOH if it supports mesh splitting, but it tends to be better when you...

gltfpack doesn't do coordinate system transforms; similarly to above, this seems to be a task better suited for glTF-Transform (unsure if it already supports it or not).

The intent here is that you really don't need to change these except for once at startup, just like the memory allocation function.

... in fact it's really time to change the defaults so that you just don't need to call these functions in general unless the application is doing something incredibly specific.