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)

So, to clarify, do we need an older version of XTool for Unity/LZ4 files? I've noticed it doesn't seem to work with recent versions.

Quote:

Originally Posted by KaktoR (Post 509588)

Send sample

No problem - attached

OK, it's fixed in 0.9.4. Thanks, Razor12911.

New Release: XTool v0.9.4 (17.03.26)

Quote:

Changes

- Added internal version check when dragging liblz4, libzstd and oodle dlls onto xtool

- Added cls config

- Fixed an issue with plugins not being loaded correctly

- Updated library checker when using UI

- Updated leviathan codec

https://www.patreon.com/posts/xtool-v0-9-4-153238519

im trying xtool 0.9.4 on latest version of no man's sky but it keeps failing. zlib also doesnt work.
test on NMSARC.MeshPlanetDESERT.pak (0.41kb) -

Code:

[0] Processing zstd stream at 0000000000009E50 (909 >> 65536 >> 987) using l16:f0:w0:b0 has failed

[0] Processing zstd stream at 0000000000009E50 (909 >> 65536 >> 936) using l17:f0:w0:b0 has failed

[0] Processing zstd stream at 0000000000009E50 (909 >> 65536 >> 922) using l18:f0:w0:b0 has failed

[0] Processing zstd stream at 0000000000009E50 (909 >> 65536 >> 921) using l19:f0:w0:b0 has failed

[0] Processing zstd stream at 0000000000009E50 (909 >> 65536 >> 922) using l20:f0:w0:b0 has failed

[0] Processing zstd stream at 0000000000009E50 (909 >> 65536 >> 922) using l21:f0:w0:b0 has failed

[0] Processing zstd stream at 0000000000009E50 (909 >> 65536 >> 922) using l22:f0:w0:b0 has failed



Streams: 0 / 3

Time: 00:00:00 (CPU 00:00:00)



Size: 0.04 MB >> 0.04 MB



Done!!!

edit:
fixed by replacing old libzstd.dll with a new one from https://github.com/facebook/zstd/

New Release: XTool v0.9.5 (21.03.26)

Quote:

Changes

- updated DirectStorage gdeflate and nvCOMP libgdeflate codecs

Notes:

This is a complete implementation of both libraries meaning compression level can be specified and as such, the game Ninja Gaiden 4 now requires you to specify the correct level for precompression which is level 6 because stream patching takes place. Don't mind the streams that get left behind for that game because they are just too small to be patched without incurring negative ratio.

https://www.patreon.com/posts/xtool-v0-9-5-153584845

dd3 instead of srep

i compressed using "dd3" parameter in xtool , but got error in decompression , need help or a tuto for how to use/configure correctly "dd3" instead of srep!thx

Quote:

Changes

- added tracking for sizes of stream patches

- added stream coverage tracking

- added option to specify multiple oodle libraries to use (-oodl#)

- fixed issues with reassign stream feature

- fixed minor issues with DirectStorage codecs

Notes

Patreon now seems to have virus scanner in attachments that I upload and has false detected xtool, this has delayed the 0.9.6 update because I was stuck in a situation where I wondered, should I add a password to the archives to prevent scanners from blocking the post? But then that would raise suspicions to some people using this tool especially with some programs like cpu-z and such getting malware recently (it's good to have trust issues) and so, I want to make it clear. The software is provided as is and I shall not be held liable for any damages.

With that out of the way,

xtool now tells you how many streams were patched and how big the patches are that way you can play a bit more with -df parameter to maximise ratio for imperfect streams.

Streams: 5359 / 5547 (95,43%)

Patched: 5359 (0,15 MB)

It also tells you the stream coverage in percentages, 95,43% as an example for that input means 95% of the file had streams and 5% was something else, this is good feature that tells you if said file contained something else other than streams, maybe audio, video or encrypted data.

Streams: 17850 / 17850 (7,72%)

ForzaHorizon6\media\Tracks\Brio\GeoChunk0.minizip

This file is 37GB, only 7% contains zlib streams, what is the remaining 93%? That's for you to investigate...

I've also added the feature that allows you to specify multiple oodle libraries for precompression, if one fails the next one is attempt because there's some games that seem to use more than one dll which makes complete precompression in one go not possible, requiring multiple passes of xtool which can be slower and use more memory.

Keep in mind, that the same parameters for oodle dlls is required when decoding and the primary oodle dll -oodle### should be a newer version meaning, do not use oo2core_4_win64.dll for the first one and oo2core_6_win64.dll for -oodl2###

gameresources_20_patch2.streamdb

xtool.exe precomp -mkraken:l6 -c32mb -oodleoo2core_9_win64.dll -oodl2oo2core_9_win64_2.dll - -

with one library

Streams: 1045 / 1154 (96,90%)

Size: 356 MB >> 534 MB

with both libraries

Streams: 1150 / 1154 (96,90%)

Size: 356 MB >> 605 MB

https://www.patreon.com/posts/xtool-v0-9-6-159873167
Password: 123

New Release: XTool v0.9.7 (27.06.26)

Quote:

Changes

- reassign stream feature separated from -m, now uses -r

- minor optimisations

https://www.patreon.com/razor12911/p...-9-7-162247232

New Release: XTool v0.9.8 (30.08.26)

Quote:

Changes

- fixed issues with fast-lzma2

- fixed issues with some plugins not working

- fast-lzma2 dll requirement reverted

- memory optimizations

Notes

fast-lzma2 is back to requiring dll to be present to work, reason? well, there's been a bug dating back to 0.6.1 with fast-lzma2 where they'd be decompression errors and I thought the bug was caused by including compiled code within the exe but it wasn't and when I had fixed the issue, I just felt like it's best to require the dll in cases where there's still more bugs with the library itself and the user can fix it themselves by replacing dll.

I also figured out the reason why Patreon has been acting up with xtool attachments as of late and the reason I had to password protect them. The x86 builds some people have been requesting me to include for whatever reason keep getting false detected as malware so if you're making repacks for the public to use, I strongly advise against using x86 (32-bit) binaries, this also applies to the cls as well.

https://www.patreon.com/razor12911/p...-9-8-165278028