[Dev]XTool

[ShivShubh]

Originally Posted by darkwolves

i been repacking crilayla games for some time now its funny this is like the third time someone has said i was wrong and razor came in later and told them i was right lol

Or maybe there was just a misunderstanding ? Because I can't properly understand what you are trying to say by this :-

the cpk.bms has nothing whatsoever to do with actual inflation it is designed to extract and decompress the file hence the bigger size that is not inflation that is just a result of decompiling the data..

CPK bms by aluigi has the algorithm (comtype cpk) decompression function, the compressed streams are actually decompressed during the extraction process which is equivalent to the inflation done by XTool.

Originally Posted by Andu21

Razor, why this happens? Shouldn't the compressed output be less?

TombRaider_Beginning.pcf 4.92 GB > 491 MB
TombRaider_Beginning.xtl 4.99 GB > 660 MB

Originally Posted by Razor12911

Can you rerun the test using 0.2, thanks in advance

Results made using XTool 0.2 on TombRaider_Beginning.pdf (904 MB)

PDF (904 MB) --> precomp (4.92 GB) --> 4x4:b32m:t4:lzma (550 MB)
PDF (904 MB) --> xtool, c32m (4.98 GB) --> 4x4:b32m:t4:lzma (710 MB)
PDF (904 MB) --> xtool, c256m (5.05 GB) --> 4x4:b32m:t4:lzma (686 MB)

Seems like other pdf files will produce similar differences. Precomp has inbuilt PDF scanner so it is able to properly scan and inflate all the PDF streams hence the better output.

[darkwolves]

because it is designed to decompile and extract once extracted it no longer even reads as a cpk file until it is recompressed and encrypted with a cpk tool it would take razor forever to be able to read through all that data and try implementing it into xtool

[ShivShubh]

Originally Posted by darkwolves

because it is designed to decompile and extract once extracted it no longer even reads as a cpk file until it is recompressed and encrypted with a cpk tool it would take razor forever to be able to read through all that data and try implementing it into xtool

Why would it be able to read as cpk file after extraction ? Its obvious it wont be read as CPK. And as far as I think XTool's crilayla is based on cpk bms thats why there's no x64 build for it.

[darkwolves]

Originally Posted by ShivShubh

Why would it be able to read as cpk file after extraction ? Its obvious it wont be read as CPK. And as far as I think XTool's crilayla is based on cpk bms thats why there's no x64 build for it.

if it is extracted it needs to be recompressed by a cpk tool the way razor is making it is were the file inflates not extracts he even said above
how exhausting it is to have to translate all of that

[ShivShubh]

Originally Posted by darkwolves

he even said above how exhausting it is to have to translate all of that

You understood that incorrectly, he meant to say it is exhausting to translate CPK's BMS language into Delphi which is a totally different thing.

[darkwolves]

Originally Posted by ShivShubh

You understood that incorrectly, he meant to say it is exhausting to translate CPK's BMS language into Delphi which is a totally different thing.

oh no i understood that very correctly considering... i have done that enough myself trying to develop my own tool for it his way is faster and its easier so him using a cpk bms would only hinder him and make the project take longer.... and it would only work to a point because some cpk games will not even work with the bms i began using a different tool that extracts all cpk files as well as viewing the content within deeming the cpk bms unreliable