FileForums - XTool - Successor of ZTool

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

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

- - XTool - Successor of ZTool (https://fileforums.com/showthread.php?t=101729)

Is it for even v11

Uh sorry to irritate but is v11 of the tool even stable to do things?I mean to unpack archives which has been packed with v9 of xtool

Wishing for an exact answer and thanks in advance

last time i used different xtool for pack/unpack i got error...
better to use the same xtool ver for pack/unpack...

I have many archives with xtool 0.9 and i can unpack them with 0.12 without problems.

if i remember correctly it was on mass effect 3 i got error during install after checking i noticed that xtool was different ver form the one during packing...
but i don't remember which ver, maybe the opposite of what you did i packed with newer ver and using old ver for unpack...

I had a problem with
Ghost Recon Wildlands (.Forge files)
i have check it with GFS, then i found the game had lzo streams. But when i try xtool: lzo on game files,
it won't decompress and I don't know how to decompress it.
ANYONE CAN HELP ME PLEASE?

Quote:

Originally Posted by Razor12911 (Post 480125)

the headers are placed elsewhere bro. The files you gave me do have signs of lz4hc being used but there are no headers for me to reference for information as to where streams start and where they end. This will be a job for a universal lz4 precompressor but not at the moment because lz4 is a piece of shit when it comes to that department, as you can see in the screenshot I uploaded.

gives two byte header "F2 00" that I have no idea what it means then followed by parts of the original data, "44 44 53 20" which is a header for a dds texture which means lz4hc was indeed used but that's it. no game engine headers located or anything that could help for me to be able to add support.

headers are at the end of file
zenhax.com/viewtopic.php?f=9&t=1663
and pak files are splitted
like:
Textures.pak
Textures_1.pak
Textures_2.pak
it is one big archive

whe i try to pack the files arc.exe get crash
how to solve this issue :(

Quote:

Originally Posted by IgorKolesnik (Post 480181)

help please solve the problem. When using xtool for large files, this error occurs during installation.
I use this method: xtool+srep+delta+lolz
options xtool:
[External compressor:xtool]
header = 0
packcmd = xtool e:precomp:t2:zlib - - <stdin> <stdout>

bat file:
arc.exe a -w.\ -ep1 -dses --dirs -s; -lc- -di -i2 -r -mxtool+srep+delta+lolz data1.bin "packeddata2\*"

xtool v011

https://i1.imageban.ru/out/2019/03/1...b3b81b57d7.jpg

I'm having the same error when using zlib, I have tried all xtool versions x86/x64, all combinations old+new/same versions, compressing with only 1 thread, with different chunk sizes.

Any ideas ?

my compression cmd:

Code:

arc a -ep1 -ed -r -w.\ Data\Setup-1.bin -mxprecomp+srep_x64:m3f+lolz:d256m:mtb256:mc1023:mtt1:mt8 "D:\TEST\TESTGAME\*"

my arc.ini:

Code:

[External compressor:xprecomp]

header = 0

packcmd   = xtool.exe e:precomp:c128mb,t1:zlib $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

unpackcmd = xtool.exe d:precomp:t1 $$arcpackedfile$$.tmp $$arcdatafile$$.tmp



[External compressor:srep_x64]

header = 0

packcmd   = srep_x64 {options} -s907374182400 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

unpackcmd = srep_x64 -d -s $$arcpackedfile$$.tmp $$arcdatafile$$.tmp



[External compressor:lolz]

header     = 0

packcmd    = "lolz_x64" {options} $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

unpackcmd  = cls-lolz_x64.exe $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

datafile   = $$arcdatafile$$.tmp

packedfile = $$arcpackedfile$$.tmp

Try percent instead of threads for xtool

Code:

packcmd = xtool.exe e:precomp:c128mb,t50p:zlib $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

From 1 to 100

Same thing, using xtool v.012 x86 for packing and unpacking

Did not help, same error..

This are my tools and setup, uploading test files too.