Open donmccurdy opened 1 year ago
Helpful test case for attribute-aware simplification:
https://sketchfab.com/3d-models/bananya-birbo-900ce1ec328e486296cfee70b9b13a45
It looks like there are breaking changes planned for the simplifyWithAttributes API, which is still experimental:
https://github.com/zeux/meshoptimizer/pull/601
I think the rest of this task – supporting simplifyWithAttributes — will need to wait for a 4.1+ release.
v0.21 is released: https://github.com/zeux/meshoptimizer/releases/tag/v0.21 So when adding new features requiring new version, is there a fallback for old versions to keep them working, or sonething like a compatibility matrix for users to help them choose or update versions of 3rd party dependency?
There's only one such feature today, simplifyPoints
, handled by skipping point simplification if the meshopt version doesn't support it:
If compatibility becomes more complicated in the future, we could either provide a compatibility matrix or add a meshoptimizer
version range to optionalDependencies
.
Another thing to nominate is the change to useWorkers in v0.20, it can be used to avoid memory leak at the cost of being async (could be a breaking change). Also, can simplify
and other meshopt-based functions run multi-threaded?
We'll have to check if the workers are supported in different environments (web, Node.js, and Deno) but I think that would be a good addition, yes. glTF Transform generally does not spawn threads or workers itself (KTX compression is an exception) but dependencies certainly could.
From https://github.com/zeux/meshoptimizer/releases/tag/v0.20 —
Related:
822
1335
992