![]() |
Thank you Razor12911, thanks for the breakdown
I will edit my arc.ini file and correct that. cheers ScOOt3r |
Update available
Changes - minor bug fixes Changes between 0.3.13 to 0.3.15 Code:
ES_R15 (0.3.15) |
Quote:
|
Update available
Changes - fixed multi-threading bug Quote:
I only have a few samples of Automobilista 2 and it seems to work there, but I was more interested in the first project cars game. |
@Razor12911
any benefit from adding embedded deduplication feature (--dedup) [makes temps during encoding] ??? game like gta v it unpack to xtool.vm then just copy to arc $$$ while using all ram and ssd write cycle... so is it better to disable --dedup ??? |
Update available
Changes - fixed depth bug - fixed library plugin bugs @doofoo24 I'll look into the issue but you can use xtool without deduplication, someone has already made comments regarding xtool's memory hungry behaviour when using the feature as this is not supposed to happen. |
@Razor12911
does xtool 0.3.18 work with mass effect legendary ? only xtool in New folder (7) work "packcmd = xtool.exe precomp -mue3:m2 -t100p - - <stdin> <stdout>" ... |
Yes it works but you need the unreal plugin and oodle library from the game.
|
Quote:
Quote:
Quote:
|
yea my mistake i used unreal.dll from "New folder (7)" with xtool 0.3.18 having the same size as unreal.dll from R5 i thought both the same ...:o
so i compress all of mass effect 1+2+3 super fast during install on r9 5950x... around 9min install 71gb without bik... xtool set to 100p but most of the time around 60% during install unlike during compress xtool was using all 32 thread so i guess there is bottelneck lolz or srep ? to test it i need to use only xtool to see if it can use 32 thread in decode... |
Is there any way you can pass ue3:m2 command line parameters to arc.exe with "standard" arc.ini provided with xtool?
Code:
[External compressor:xtool]When I modify arc.ini packcmd to xtool.exe precomp -mue3:m2 .... it is working ok, but with { -moption} it fails. |
@infovs
-mxtool:ue3,m2 |
Update available
Changes - updated lzo codec |
Is there anyway to analyse a file to see which version of LZ4 it was compressed with?
I have a few unity asset bundles, 506MB worth. When decompressed using Asset Bundle Extractor, they decompress to 2.78GB. If I try to throw these into XTool, it will make an archive of 693MB (~136% ratio). I get the same whether I use the 2017 lz4 dll, 2018 (v1.8.1.2 / v1.8.2) lz4 dll or the latest dll from Nov 2020. https://1fichier.com/?hcsaopws7sfrktfka4z2 Here's the sample |
Here's some more info on that unity sample I shared above:
Code:
Compressing 4_trialislands_scenes_4d_bunker.unity.bundle |
| All times are GMT -7. The time now is 23:33. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
FileForums @ https://fileforums.com