Discussion in 'Windows OS and Software' started by sm2596, Oct 14, 2017.
Nice find! gonna give that a try.
The program is build into windows 10, its called compact but that is with command lines. Compact GUI is more user friendly.
Gonna test it, sounds like a dream to me.
This one https://github.com/ImminentFate/CompactGUI/wiki/Compression-Results:-Games?
yea that one
There must be some penalty? Extra CPU use and some delay.
Are there any issues when Steam updates the game files?
Agree with HTWingNut, there's gotta be some penalty, though I doubt it would be as bad as loading times with encrypted games like Forza Horizon 3 (yeesh).
I just used windows to compress (Windows 7). Go to Program files (x86) right click the file you want to compress, properties, advanced, and check compress files to save space. Seems to work. I think I saved about 7 gb on BF1 this way.
When Steam updates the game files, it will save the uncompressed version of any files it changes, so you'll have to recompress afterwards.
That method uses the old LZNT1 compression, and is inferior with respect to performance in games and programs, as it is single-threaded and prioritises compression ratio over runtime performance. The "/EXE" flags in the compact.exe tool are designed around use on executable files, so they're optimised for performance over compression ratios but still do a really good job.
Even the basic "compact.exe /c" option is better than the right click menu option, as it's still LZNT1(I think) but it's multi-threaded so the performance hit should be lower
I find it really hard to believe any type of real-time data compression wouldn't affect performance. Idea is great though
Separate names with a comma.