Loading...
Aisha Mohammed
I've been running game assets through the compress tool and getting mixed results. Some models go from 15MB to 3MB (80% reduction), others barely shrink at all.
What factors determine how much compression you get? Is it mostly about the mesh complexity or the textures? And is there a way to control the compression level — like choosing between quality vs file size?
Marcus Rivera
41d ago
The compression ratio depends mostly on two things:
1. Mesh geometry — Draco compression works best on dense meshes with lots of vertices. A 100K triangle model will compress much more than a 5K triangle model because there's more redundant data to compress.
2. Textures — If your GLB has large uncompressed PNG textures, the compress tool converts them to JPEG or WebP which gives huge savings. But if your textures are already optimized, there's less to gain.
Models that barely shrink usually have already-optimized textures and low-poly meshes. That's actually a good thing — it means the original was already efficient.
Jake Thompson
41d ago
Also worth noting: Draco compression adds a decode step on the client side. The Three.js Draco decoder is about 300KB extra JavaScript. For a single model on a page it's totally worth it, but if you're loading lots of tiny models, the decoder overhead might outweigh the savings.
For game assets specifically, I'd compress anything over 5MB and leave smaller models uncompressed.
سجل دخولك للرد
سجل دخولك للرد