![]() |
Update available
Changes - added depth info functions - added support for oodle 2.9.0+ functions - fixed data patching bug - updated oodle codec - updated command line parser Changes between 0.3.9 to 0.3.11 Code:
ES_R11 (0.3.11)I updated the command line parser Code:
[External compressor:xtool] |
@Everyone
The oodle precompressor in xtool is now more aggressive (means slower), I'll add aggression parameter to control how much time it should spend finding more and more streams however this only applies to kraken, mermaid, selkie and hydra. Leviathan is still problematic and you'll have to rely on plugins for data compressed using this codec. Here are a few benchmarks that show what I am talking about: 0.99 GB (1,066,131,456 bytes) > 1.52 GB (1,638,079,260 bytes) [took 2 minutes, 9 seconds] (xtool 0.3.9) 0.99 GB (1,066,131,456 bytes) > 1.84 GB (1,977,644,853 bytes) [took 4 minutes, 56 seconds] (xtool 0.3.12) 0.99 GB (1,066,131,456 bytes) > 1.53 GB (1,649,308,007 bytes) [took 8 minutes, 52 seconds] (oo2reck) As you can see, version 0.3.12 is now slower but it found more streams than 0.3.9 or the oodle precompressor side project. This is a sample from Cyberpunk 2077 and since the game does have a plugin these are the results if you had use the plugin 0.99 GB (1,066,131,456 bytes) > 2.26 GB (2,432,780,012 bytes) [took 41 seconds] (plugin) So what do these results mean? Well the newer version of xtool traded speed for more ratio in an attempt to beat the side project while still being faster. Also if a plugin for a specific game is created, it shows that the plugins will constantly be superior to the universal precompressor as it's not only faster but produces better results. :) In conclusion, try to run tests with other games to see if the new xtool produces better results than oo2rec and if a plugin for a game exists then it's best to just use it. |
I am now even more fired up for FIFA.
Thanks for these updates. |
For FIFA and all these other frostbite games, 0.3.13 update is needed
|
Crash Bandicoot 4 Comparison - For zlib streams
0.3.12 Code:
Compressed 1 file, 19,665,315 => 91,532,563 bytes. Ratio 465.45%Code:
Compressed 1 file, 19,665,315 => 98,920,152 bytes. Ratio 503.02%Those FIFA's after 19 are such a pain... |
Quote:
FIFA after 19 isn't a problem, I don't have samples for these games so I am limited by the little samples that I have. |
Quote:
Assuming that zlib had a parameter -m3 for example (just to specify the debt): For example, assuming that zlib had a parameter -m3 (just to specify the debt) would it look like this? Code:
"-mxtool:zlib,m3+ue4,m1,k0x115E..."to use zlib+ue4 (Borderlands 3) it would not be necessary to send the -d1 parameter to XTool. How can I pass or not the -d1 if I use the command like the arc.ini information reported above? |
Code:
[External compressor:xtool]Code:
-mxtool:zlib,m3:ue4,m1,k0x115E...Code:
[External compressor:xtool]Code:
-mxtool:d1:mzlib,m3:mue4,m1,k0x115Ethen -d1 -mzlib+ue4:m1:k0x115E when it reaches xtool |
Might hook you up with some samples, once i get to testing it. If you would like.
Yes it was the dedup. Without dedup : Code:
Compressed 1 file, 19,665,315 => 98,946,941 bytes. Ratio 503.15% |
Bethesda plugin does not work with xtool 0.3.12
Code:
0.3.9 |
Quote:
|
Update available
Changes - updated lz4 codec - updated library structure - updated depth info functions - updated depth feature |
XTool LZ4:
8:20:52 PM - Overall input size: 6.54 GB 8:20:52 PM - Overall output size: 3.91 GB 8:20:52 PM - Overall conversion time: 00:00:52 XTool 2020 LZ4: 8:22:33 PM - Overall input size: 6.54 GB 8:22:33 PM - Overall output size: 6.54 GB 8:22:33 PM - Overall conversion time: 00:01:02 Is this normal or a bug? I'm using the same settings with the same dataset yet one LZ4 gives good compression and the other gives no compression. |
If i wanted to use Oodle with xtool
would this be correct with the latest verison of xtool [External compressor:xtool] header = 0 packcmd = xtool\xtool.exe precomp -moodle -c256mb -t22 --dbase --dedup - - <stdin> <stdout> cause it doesnt work for me... get a disc full error thanks ScOOt3r |
Quote:
Quote:
Edit: the parameter you used will require about 6GB ram if no streams are found and it will require even more if they are found (256mb x 22 threads) + 256mb = 5,888MB ram usage and if the average inflation ratio is 200%, you're looking at 12GB+ ram usage by xtool. I'm letting you know before hand that the parameter you have input will make xtool use a lot of memory. |
| All times are GMT -7. The time now is 00:51. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
FileForums @ https://fileforums.com