You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Possibly showing incorrect estimated saving from database #543
I'm a little confused, the estimation numbers being displayed don't match neither the data found in the "Compression DB" tab or the database json.
Example:
A Short Hike
It's mixing the numbers:
Estimated saving percentage for XPRESS8K (27%) in database -> Shown under LZX in folder scan
Estimated saving percentage for LZX (31%) in database -> Shown under XPRESS16K in folder scan
Adiditionally, in the database json only one estimation is available:
242310177 bytes -> 231.1MB (I think ?)
"CompType":1 -> XPRESS8K
From the information above, I think that:
The data found in the Compression DB tab is correct, although I don't understand where the LZX data is coming from, unless the program uses a different data source
The estimated savings for game scans is assigning the incorrect estimates data to compression types
Good catch, I think it's because I'm using two different mappings throughout the program (which I really shouldn't do) and got them wrong for the buttons. The buttons should use CompressionMode but I've incorrectly used WOFComperssionAlgorithm
Activity
darklinkpower commentedon Jul 4, 2025
I think this is an example that can clearly tells what is incorrect:
Iridium-IO commentedon Jul 4, 2025
Good catch, I think it's because I'm using two different mappings throughout the program (which I really shouldn't do) and got them wrong for the buttons. The buttons should use
CompressionModebut I've incorrectly usedWOFComperssionAlgorithmWindows uses the second one internally so I need to convert between the two and I keep mixing them up haha. I'll fix this soon :)
Fix compression buttons not showing the correct estimation values. Fixes