FileForums - XTool 2020 (Main Project)

FileForums (https://fileforums.com/index.php)

- Conversion Tutorials (https://fileforums.com/forumdisplay.php?f=55)

- - XTool 2020 (Main Project) (https://fileforums.com/showthread.php?t=102832)

Quote:

Originally Posted by seryogakms (Post 496004)

File Patch.bin from "Horizon zero dawn" (last version).
5 434 479 154 bytes → 360 912 358 bytes (xtool_0.3.9 ONLY). Compression time — 36 minutes. Unpacking time — 18 minutes.

Intel core i5-3550, 20 GB RAM.

oo2reck+srep+lolz - 340 mb
Decompression time - 4 min:cool:

Quote:

Originally Posted by seryogakms (Post 496004)

Code:

arc.exe a -ep1 -r -ed -s; -i2 -w.\temp -mxtool+srep+lolz Packs\data.bin "H:\06. 1.0.11.9 (1.11)\Packed_DX12\Patch.bin"

Code:

[External compressor:xtool]

header = 0

packcmd = xtool precomp -mkraken -d3 -c64mb -t100p - - <stdin> <stdout>

unpackcmd = xtool.exe decode -t100p - - <stdin> <stdout>



[External compressor:srep]

header = 0

packcmd   = srep64 -mem512m -l512 -m5f $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

unpackcmd = srep -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp



[External compressor:lolz]

header = 0

packcmd = lolz_x64.exe -d128 -mc1023 -dtb1 -tt4 -mtt1 -mt8 -mtb128 -fba1024 -oh14 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

unpackcmd = lolz_x86.exe $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

No other version of xtool gives such results under any settings.

xtool_0.4.2 with the same (and other) settings:
5 434 479 154 bytes → 2 738 426 574 bytes. Compression time — 3 hours and 56 minutes. Unpacking time — 18 minutes.

Sample?

Quote:

Originally Posted by ScOOt3r (Post 495998)

well i got it working compressing and decompression as someone posted above to remove libzstd.dll.. i did that and it works just fine now.. weird that it was that file
not sure how important libzstd.dll is...

ScOOt3r

https://imageup.ru/img160/thumb/13887671.jpg

arc.exe a -ep1 -r -ed -s; -i2 -w.\temp -mxt22+srep+lolz Packs\data.bin "DATAS\*"

[External compressor:xt22_zstd]
header = 0
packcmd = xtool\zlib\xt22.exe precomp -mzlib+zstd:l19,l22 -c32mb -t100p $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = xt22.exe decode -t100p - - <stdin> <stdout>

[External compressor:lolz]
header = 0
packcmd = lolz_x64.exe -d128 -mc1023 -dtb1 -tt4 -mtt1 -mt8 -mtb128 -fba1024 -oh14 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = lolz_x86.exe $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

[External compressor:srep]
header = 0
packcmd = srep64 -mem512m -l512 -m5f $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = srep -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

Quote:

Originally Posted by dixen (Post 496006)

oo2reck+srep+lolz - 340 mb
decompression time - 4 min:cool:

В очередной раз спасибо за подсказку, но у меня комп «немного» слабее твоего. ):

Quote:

Originally Posted by seryogakms (Post 496009)

В очередной раз спасибо за подсказку, но у меня комп «немного» слабее твоего. ):

shhh. english only in post...
Razor12911
Hi)
What about *.bdt from Elden Ring? It encrypted oodle streams?

Quote:

Originally Posted by dixen (Post 496010)

shhh. english only in post...

Sorry, I didn't think of that...

Quote:

Originally Posted by dixen (Post 496010)

shhh. english only in post...
Razor12911
Hi)
What about *.bdt from Elden Ring? It encrypted oodle streams?

sample?

Quote:

Originally Posted by Razor12911 (Post 496012)

sample?

Smallest bdt is 2.4 gb..Uploading..

https://drive.google.com/file/d/1UDb...ew?usp=sharing

Quote:

Originally Posted by Razor12911 (Post 496007)

Sample?

It took even longer. I apologize for the encoding in cmd.

xtool_0.4.2

https://imageup.ru/img119/thumb/113887693.jpg

ELDEN RING

Oodlerec Used

Code:

Compressing 1 file, 2,655,357,776 bytes

  Compressing Data3.bdt

Compressed 1 file, 2,655,357,776 => 4,549,448,231 bytes. Ratio 171.33%

Compression time: cpu 3.81 sec/real 615.49 sec = 1%. Speed 4.31 mB/s

All OK

From Masquerade.
use oodle core from Martha is Dead

@dixen

use oo2core_8_win64.dll

Attachment 31310
Attachment 31311

Quote:

Originally Posted by seryogakms (Post 496014)

It took even longer. I apologize for the encoding in cmd.

xtool_0.4.2

https://imageup.ru/img119/thumb/113887693.jpg

upload the file from the game for me to take a look at.

You can use this oodle core to boost the ratio a little bit more
https://bayfiles.com/55bfieKbx4/oo2core_4_win64_7z
Credits to FitGirl for the dll

From a 100mb sample data0.bdt

Code:

xtool:kraken

Compressed 1 file, 104,857,600 => 213,800,403 bytes. Ratio 203.90%

Compression time: cpu 0.09 sec/real 15.75 sec = 1%. Speed 6.66 mB/s



xtool:kraken,l6

Compressed 1 file, 104,857,600 => 214,235,226 bytes. Ratio 204.31%

Compression time: cpu 0.09 sec/real 10.01 sec = 1%. Speed 10.48 mB/s

Quote:

Originally Posted by Razor12911 (Post 496016)

upload the file from the game for me to take a look at.

LINK ON FILE

xtool_0.3.9 ONLY
https://imageup.ru/img34/thumb/23887702.jpg

Thanks to DIXEN for the hint.

UPD:
https://imageup.ru/img242/thumb/3333887736.jpg

https://imageup.ru/img193/thumb/4443887752.jpg

Update available

Changes

- added verbose mode
- added feature that allows you to enforce a different library to be loaded
- fixed issues related to imperfect stream patching
- fixed issues with old libraries with missing functions that cause xtool to crash on startup
- updated oodle codec
- updated reflate codec
- updated zstd codec

Notes

You can now enforce xtool to use a specific library rather than renaming the library for it to picked up by xtool.

Code:

[External compressor:xtool]

header    = 0

packcmd   = xtool.exe precomp { -moption} -c32mb -t100p --zstd=libzstd148.dll - - <stdin> <stdout>

unpackcmd = xtool.exe decode -t100p - - --zstd=libzstd148.dll <stdin> <stdout>

Available parameters for this are:
--zlib=filename, --lz4=filename, --lzo=filename, --zstd=filename, --oodle=filename

You can also use this to run multiple tests to see which zstd or oodle library gives the best output by running these commands on a small sample:

Code:

xtool.exe precomp -mkraken -c32mb -t100p --oodle=oo2core_7_win64.dll - - < %1 > %1.out1

xtool.exe precomp -mkraken -c32mb -t100p --oodle=oo2core_7_win64_2.dll - - < %1 > %1.out2

xtool.exe precomp -mkraken -c32mb -t100p --oodle=oo2core_8_win64.dll - - < %1 > %1.out3

xtool.exe precomp -mkraken -c32mb -t100p --oodle=oo2core_fifa22.dll - - < %1 > %1.out4

Then you can pick whichever produces the best results

___

Oodle code has been updated, if you having issues with stream detection you can use the parameter n1 (kraken,n1), where the old code will be used. it can also be n2 or n3, depending on how many times each stream should be redetected (for improved results but at a cost of speed)
If this doesn't help then use the side project.

___

Verbose mode was added to give information about input, as to what parameters are used for streams within the input and if you see a common trend then you directly use these parameters to speed up xtool and also give it the opportunity to patch streams if there are any invalid streams.

Verbose mode will enforce xtool to 1 thread thus it should not be used by default as it will slow now precompression.