XTool 2020 (Main Project)

[Razor12911]

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.

[doofoo24]

@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>" ...

[dixen]

Originally Posted by doofoo24

@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>" ...

ME2 Textures7.tfc

FreeArc 0.67 (March 15 2014) creating archive: data.arc
Compressed 1 file, 519,052,402 => 1,490,583,040 bytes. Ratio 287.17%
Compression time: cpu 0.56 sec/real 16.36 sec = 3%. Speed 31.72 mB/s
All OK

Tested 1 file, 1,490,583,040 => 519,052,402 bytes. Ratio 287.17%
Testing time: cpu 0.47 sec/real 13.01 sec = 4%. Speed 39.90 mB/s
All OK

XTool v0.3.18 + UE-Plugin R5

[doofoo24]

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 ...

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...