It doesnt work like that. FC2/3/4 uses LZOPRO while FC5 uses LZ4HC.

looks like someone is going to have to break down and get LZOPRO for razor...
i will check my monthly budget..

Fc234 do not use lzopro ;)

Thank you Simorq for this solution but as KaktoR says it's slower.
What is surprising is that Pzlib V3 does not have this problem for this game.
I only created a new "xtoolslow" entry in the arc.ini for archives that have this problem.

Thanks for confirming :) Then its probably some other problem.

Thanks, I figured out the solution to the problem after posting :)

Call of Duty IW test

europa_fatty_tr.ff:
ZTool: 38,489,248 => 85,959,469 => 39,719,836 bytes // negative ratio
XTool: 38,489,248 => 66,390,558 => 27,577,712 bytes

assetfile17.pak:
ZTool: 104,595,492 => 178,560,871 => 54,821,086 bytes
XTool: 104,595,492 => 139,027,892 => 33,859,574 bytes

thanks for xtool, diskpan.

I hope that soon you can compress the call of duty games....
thanks-thanks-thanksthanks-thanks

xtool v0.5 on doom file's gameresources.patch & gameresources.resources
e:precomp:c256mb 9.20 > 19gb
e:precomp:c128mb 9.20 > 18.6gb
e:precomp:c64mb 9.20 > 16.6gb
e:precomp:c32mb 9.20 > 14.4gb

*for optimal setting for doom use xtool only on gameresources.patch & gameresources.resources
need hif2raw_dll.dll, raw2hif_dll.dll

[External compressor:xprecomp]
header = 0
packcmd = xtool.exe e:precomp:c160mb,t4:zlib - - <stdin> <stdout>

9.20gb > 19gb > 4.41gb , srep+lolz

*decompression seems to be very slow almost 20 min, xtool most of the time use only 11% with 438mb of ram...

unpackcmd = xtool.exe d:precomp:t100p - - <stdin> <stdout>

i get appcrash with xtool even in FA_example but randomly.it's weird but sometimes xtool is working but mostly it's give error.arc.exe stopped working and fault module is msvcrt. i formatted pc in windows 10 it gives memory could not be read in windows 7 it gives appcrash.any help?

that is a runtime file if i am not mistaken...
wich msvcrt is it? there are more than one

I've the same error. But it was only with cls-diskspan and razor's original batch (drag&drop bat). Custom works perfectly. Only sometimes it doesn't work, then i just have to spam the batch :D

Is there a option to skip the "CRC is broken" message and just left the CRC corrupted file there and unpacking next file? I aking because i could just use xdelta afterwards without all the hassle to find the one-working-option for every file. In my tests all xdelta dif files are just about 15-30kb in size.

I guess, FA will not allow u to do it. howver u can just use bat file to unpack xtool files and then use xdelta.

BTW, u will get crc errors, if u pack a file with xtool (say a zlib file) while cryla, liblz4 etc are also present during packing around xtool. and unpack with only xtool + zlibapi (excluding others).

Mhh too bad. Thanks anyway.