Slow to run in Chrome? about gltf-compressor HOT 4 OPEN

Thank you for your use and report on glTF-Compressor. The glTF-Compressor tool was designed to be an investigative support tool. It does have limitations with respect to large/complex models or production runs. Those were out-of-scope of the project. Khronos felt that it was important to get a tool like this out as open source, but did not want to get to the realm of supporting production (either volume or model size). If glTF-Compressor does not meet your needs, we suggest you use a Khronos member tool such as RapidCompact or Needle Tools.

from gltf-compressor.

I would just add that Needle Tools is using glTF Transform (https://gltf-transform.dev/) for texture compression and other optimizations, which in turn uses KTX Software (https://github.com/KhronosGroup/KTX-Software). You may find it helpful to use glTF Compressor to identify the quality/compression settings that work best for your content, and then to instrument the final production compression pipeline with one of these other tools.

from gltf-compressor.

You may find it helpful to use glTF Compressor to identify the quality/compression settings that work best for your content, and then to instrument the final production compression pipeline with one of these other tools.

Yep that's the workflow I am using, just wanted to feed back that the web compressor previewing does feel very slow by comparison to Needle Tools compression which makes previewing almost faster in Needle when I do a build and test there alone. I would like to use the web GLTF compressor to get fast previews of compression but the speed of compressing holds me back from doing that.

from gltf-compressor.

I'd been hoping to move glTF Transform over to a WebAssembly KTX2 encoder at some point, so it's helpful to hear that there's a major performance cost there, at least in the current WASM encoders. I'll keep that in mind, thanks!

from gltf-compressor.