encodeGeometry #667
Replies: 2 comments 1 reply
-
@RyugaRyuzaki Usually Meshoptizer's compression is applied to an already-quantized mesh, downloaded to the client compressed, then decompressed before rendering. It looks like you're trying to both filter/compress and then render on the client device in one step, but the compressed data cannot be rendered without being decompressed first, so that may be a mistake. The geometry remains quantized after decompression, and so uses 25-50% the size of default float32 geometry in three.js. Meshoptimizer assumes the user quantizes mesh data themselves. If you'd like help with a three.js / meshoptimizer integration, the three.js forums (https://discourse.threejs.org/) would be the best place to ask. This thread does give an example of using three.js + glTF Transform + Meshoptimizer to optimize a glTF model exported with THREE.GLTFExporter, but as mentioned above, that's not something you'd want to do immediately before rendering the model. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I have a gemetry, anyone has any idea for this 👍
Beta Was this translation helpful? Give feedback.
All reactions