XTool 2020 (Main Project)

[KaktoR]

No. However the file is smaller than 256 bytes, so this shouldn't be a problem.

[LILU]

Good afternoon. The questions are as follows.
1. For which algorithms (for “uncompressing”) (Zlib,Kraken,Leviathan,Mermaid,Selkie,ZL4F,ZSTD,Cr ilayla,Reflate,Preflate) can GPU be used?
2.Which Gpu's are supported? AMD,Nvidia? How much video memory?
3.Do you need any additional Windows customization(software installation etc.)?
4. What version of Xtool has GPU support?
Thanks in advance.

[Masquerade]

^^
Hi, none. This was a cancelled feature.

[LILU]

Originally Posted by Masquerade

^^
Hi, none. This was a cancelled feature.

Are you talking to me?

[KaktoR]

No, he was talking with himself, don't worry.

...

Yes, he was talking to you. GPU feature was canceled, at least for AMD gpus.

[LILU]

Originally Posted by KaktoR

No, he was talking with himself, don't worry.

...

Yes, he was talking to you. GPU feature was canceled, at least for AMD gpus.

Okay. Which Nvidia models are supported?

[ZiLATAN]

Can anyone give me the download link of SREP, LZMA/Lolz Please?

[dixen]

Originally Posted by ZiLATAN

Can anyone give me the download link of SREP, LZMA/Lolz Please?

https://fileforums.com/showthread.php?t=104866

[mosath]

What is the difference between xtool 2019 / 2020 / 2020 extended support?

[Hexagon123]

Originally Posted by mosath

What is the difference between xtool 2019 / 2020 / 2020 extended support?

Compatibility improvements?

Unreal support and others.

[aman71711]

Hello everyone, I'm trying to create a repack for Cricket 24 using the method provided by masqurade in this forum and have a quick question. I have the full game folder, libzstd.dll, and all the necessary xtool files. This guide https://fileforums.com/showpost.php?...postcount=3768 specified using the parameters -mzstd:l3 -df5p -dd5, and since that didn't work directly, I used the precomp command to run it like this: xtool.exe precomp -mzstd:l3 -df5p -dd5 "CRICKET 24" "CRICKET_24_PRECOMP". The process started, but my 90 GB game folder is creating an output CRICKET_24_PRECOMP folder that has already grown to over 190 GB. As I'm new to this, I just wanted to ask if this massive increase in size is normal for the xtool precomp process and what the correct next step is after this finishes. Thanks in advance for any guidance!

[Masquerade]

^^
Seems to be working correctly, the precompression process is removing the existing zstd compression and writing the decompressed data to disk.

[naxil]

exist a way to use it under linux?

[NERV]

New Release: XTool v0.9.1 (12.01.26)

Changes

- minor code optimisation and fixes to prevent errors in certain scenarios

- fixed issues with reassign stream feature

- fixed issues library config based plugins

- removed recompress stream feature

Notes:

Reassign stream was added because of inconsistent game engines like Unreal Engine because you could write a program/library to work on a list of games then a few months later, they change something in how the files are stored which renders your tool outdated because it no longer works on the newer games. unreal.dll is a plugin to support ue3-5 games and for as long as I remember, ue3 games were compressed with lzo then came mass effect legendary edition and it used leviathan, so I updated the plugin and then Gears of War Reloaded came out and it used lz4hc so rather than updating the plugin (I've lost source code), you can reassign all those ue3 streams to lz4hc, this feature was bugged but now it is fixed and should work like so:

Usually, you'd use -mue3 to precompress the game but it doesn't work because now the game uses lz4hc so, you need to notify xtool that streams need to be reassigned to a different codec and the new method becomes -mue3+ue3=lz4hc:l9.

Library config based plugins were added in 0.8.8 because I'm a person who seems to always lose their source codes due to hard drives dying, so what I've done is allowed dlls to be imported through ini which xtool can make use of, so rather than write code internally in xtool or through a plugin which is bound to have its code lost, I can just share a ini just like other config based plugins and if there's something that needs changing or updating, either the user can do it themselves or I can just use notepad to provide a quick solution. I've provided a sample.

Recompress stream was removed because it was an overly ambitious feature I thought of added, the idea behind it was that since some compression algorithms, zlib, zstd, lz4, and oodle to a certain extent do not error out if the incorrect compressed size was provided. So what does this mean? It means if a game could not be precompressed at all, like some special edition of zstd or oodle was used and let's assume it was compressed using level 6, recompress feature was meant to allow you to recompress the streams with a stronger level, let's assume level 7 and by doing this, you ensure that your new stream will be smaller and could replace the level 6 stream that could not be precompressed, a new game file is produced and that will be your new game files and then you can use xtool normally to precompress the game and repack it.

So, what's the problem? Well by doing this, you're opening a can of worms because you now have to test if the game works without issues (maybe from start to finish) because the game files were "modified", it is lossless but it is no longer bit-perfect and you might as well use other tools to rebuild the game files after unpacking them because that's even safer due to headers being updated too and this is why it was removed. 0.9.0 is the last version to have this so if you want to use it, then look for that version here.

https://www.patreon.com/posts/148017425

[Butza]

Tell me how to scan oo2scan_7_win64.exe files when they are encrypted (unreal)