Hi, from what I understand, the crunch compression is an option to optimize the build size, at the cost of more gpu load at runtime to decompress the textures.
As you can see in the screenshot, I have two webgl build:
- one with 2 sprite atlas, each one of 8MB
- the other is the same build but the 2 sprite atalas has crunch compression enabled, reducing the size from 8MB to 0.6MB
So the expected result is a second build with a redecued size of 14-15 MB, or something near to it. But as you can see, the final size is pretty much the same; and in this case, the crunch compression seems to be useless.
What am I missing? Thanks
Ignore the build reports, it will always report uncompressed sizes. Instead check the folder size, and either create builds in separate folders or perform a clean build.
1 Like
Thanks for suggestion, i tried to build it with BuildOptions.CleanBuildCache and moved the first build in another folder before start the second build. But the results are still not expected.
The version is Unity 2021.3.27
Any ideas? I cannot really understand the purpose of crunch compression if the resuls is this
encountered this now. file size on disk on a webgl build is only a few kb less with crunch compression enabled.
quality of texture in game is worse but build is the same size
I’ve found the crunch compression for web builds to be really wonky too, I think they’re kind of experimental right now. TONS of options. I think you might be able to see the size per file after doing the compression.
(165.8 KB)
These are the settings I ended up using. I THINK that it was the format that made the biggest difference, and the compression quality was negligible.
So instead of thinking of the compression bar being quality, I view 4x4 to be low quality up to full quality at the ASTC 12x12 block
well the file size is the same even if the texture shows 165kb like in your example, if it was 1mb without crunch then it will be packed at 1mb but it will look way worse
1 Like
