Compressing Stalker Gamma gives impossible compression rate
digitalfrost84 opened this issue · comments
I compressed a Stalker Gamma folder, if I analyze it after it says size increased by 405%
If you check the folder's properties in Windows Explorer, what values do you see for Size and Size on Disk?
Can you open the folder in Windows explorer, then open Powershell from inside the folder (Right click any blank space > Open in Terminal/ Open in Powershell) and type compact and see what that says?
Mainly interested in the last two lines which will say something like:
134,980,464 total bytes of data are stored in 81,350,656 bytes.
The compression ratio is 1.7 to 1.Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows
PS F:\Gamma> compact
Listing F:\Gamma\
New files added to this directory will not be compressed.
0 : 0 = 1,0 to 1 .Grok's Modpack Installer
191488 : 94208 = 2,0 to 1 X boost_python38-vc142-mt-x64-1_75.dll
0 : 0 = 1,0 to 1 crashDumps
0 : 0 = 1,0 to 1 dlls
0 : 0 = 1,0 to 1 downloads
49 : 49 = 1,0 to 1 dump_running_process.bat
0 : 0 = 1,0 to 1 explorer++
28160 : 16384 = 1,7 to 1 X helper.exe
3433984 : 1581056 = 2,2 to 1 X libcrypto-1_1-x64.dll
32792 : 20480 = 1,6 to 1 X libffi-7.dll
686592 : 299008 = 2,3 to 1 X libssl-1_1-x64.dll
0 : 0 = 1,0 to 1 licenses
0 : 0 = 1,0 to 1 logs
0 : 0 = 1,0 to 1 loot
4704256 : 2478080 = 1,9 to 1 X ModOrganizer.exe
5952 : 4096 = 1,5 to 1 X ModOrganizer.ini
0 : 0 = 1,0 to 1 mods
0 : 0 = 1,0 to 1 NCC
122880 : 57344 = 2,1 to 1 X nxmhandler.exe
28 : 28 = 1,0 to 1 nxmhandler.ini
0 : 0 = 1,0 to 1 nxmhandler.log
0 : 0 = 1,0 to 1 overwrite
0 : 0 = 1,0 to 1 platforms
0 : 0 = 1,0 to 1 plugins
0 : 0 = 1,0 to 1 portable.txt
0 : 0 = 1,0 to 1 profiles
4997632 : 2600960 = 1,9 to 1 X python38.dll
0 : 0 = 1,0 to 1 pythoncore
2462270 : 2462270 = 1,0 to 1 pythoncore.zip
0 : 0 = 1,0 to 1 QtQml
0 : 0 = 1,0 to 1 QtQuick.2
591344 : 339968 = 1,7 to 1 X QtWebEngineProcess.exe
0 : 0 = 1,0 to 1 resources
1042885 : 1042885 = 1,0 to 1 splash.png
0 : 0 = 1,0 to 1 styles
0 : 0 = 1,0 to 1 stylesheets
0 : 0 = 1,0 to 1 translations
0 : 0 = 1,0 to 1 tutorials
934912 : 417792 = 2,2 to 1 X uibase.dll
891392 : 483328 = 1,8 to 1 X usvfs_proxy_x64.exe
711680 : 405504 = 1,8 to 1 X usvfs_proxy_x86.exe
1566208 : 827392 = 1,9 to 1 X usvfs_x64.dll
1363968 : 737280 = 1,9 to 1 X usvfs_x86.dll
0 : 0 = 1,0 to 1 webcache
Of 44 files within 1 directories
15 are compressed and 29 are not compressed.
23.768.472 total bytes of data are stored in 13.868.112 bytes.
The compression ratio is 1,7 to 1.
PS F:\Gamma>
Sorry, I gave you the wrong command.
Can you try: compact /S
That will show the size of the whole directory including subfolders.
I only need the last few lines.
me too
amaziiing()
This seems to be related to the file to be compressed, especially when it contains compressed files. And when there are only a few compressed files inside, it seems more inclined to crash....
I downloaded Gamma and I can't replicate the issue. I haven't gone through the full installation process because far out that's a painful set of steps and it's a total of ~50GB
I can't replicate the issue with Gamma folder on my end.
If you can drill down into exactly which subfolder is causing the issue, then list the files in that folder, that would be a great help :)
I can still replicate it even with the latest version I just downloaded (3.0):
Compact /s output is attached as file.
The compact /S output isn't helping sadly, it all looks normal.
Do you mind opening each of the subfolders in compactGUI and seeing which ones look normal and which ones go crazy?
It's the mods folder.
I look at biggest folders with the tool and others randomly. With a single folder inside I cannot replicate it, but I haven't looked at all (it's a lot).
If it helps I could upload the whole folder somewhere. I also copied the folder to a different drive just to check for any file system issues.
Maybe this is related? Both are NTFS...
If I analyze this copied folder.
Excellent detective work there, I think you're getting closer to the issue.
The file paths being too long is a good hint actually.
Can you try following these steps here: https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/
And see if that helps the mods folder report accurately at all?
I'll also start downloading the full setup today just in case that's not the issue
I already have the key LongPathsEnabled set to 1.