CompactGUI VS Zpng

CompactGUI

Also, check out CompactGUI. It's a more user-friendly and efficient way of using Windows' built-in compression to cut the game's file size almost in half. It makes load times marginally longer (like 5-10%) and needs to be redone every few updates to keep the size down, but it works.

You can chuck compact.exe at it by hand (use the /exe option), or if you'd prefer to avoid the command line there's my Compactor tool, or the venerable CompactGUI.

You can also just use compactGui smaller filesizes without having to remove dialogs or cutscenes or anything. Obviously how much space is regained depends on how well it was compressed originally. With triple A titles perhaps getting 10% back, while things like ark can literally be shrunk by hundreds of gigs.

Not really related to your question but if you want to try and save some space you can give this a go, I've used it before and never had any issues. https://github.com/IridiumIO/CompactGUI

Meet you new best friend. https://github.com/IridiumIO/CompactGUI

> You'd probably get even better results by using PNG's filters instead of QOI

Did anybody ever try this? It would be quite interesting and does not seem too difficult.

The only thing I could find is https://github.com/catid/Zpng which does not use the normal PNG filtering.

Also, Chris Taylor published an experimental PNG library with Zstd hardwired in.

- I feel like the benchmark suite is lacking. For better overview you probably should include libpng results with max compression level and lowest compression level. Lossless modes of AVIF and WEBP would be nice. (also could throw similar project to yours like https://github.com/catid/Zpng) Not saying the benchmark is bad, but IMHO doesn't paint the full picture. From quick test I got significantly better compression on libpng, ofc in expense of time, but you didn't optimize it for speed either. So we have some results, but they are not really representative imho.