Thank you for the explanation.

I'm following slightly, here's what I understand:

Data1.bdh contains the sound folder, so you can use sfk to remove it (effectively removing the duplicated data) then after installing you can patch the sound folder back in by using sfk again.

So from this I gather that in the hex editor, it will show address "17f332aa" and then you go to address "1b898ca9" and replace all of the data between these 2 addresses with 0s so that it essentially becomes empty - leading to a deduplicated file with more efficient compression - yes?

Are all of these blocks in Data1.bdh or are they scattered over the 5 data files?

So If you didn't know what parts of a file to remove and reinject, how would xdelta help? I thought xdelta can only create a patch based on an old file and a new file (by creating a patch with changed data betweeen the 2) - this part confuses me, because how will you be able to know which part of the file to remove?

I see the method would be create an xdelta patch using the modified, smaller file, and the original file then apply it after installing.

you select the block of the data then right click fill block with zeroes :D

i think i posted a how to on the forum. and i will likely pop a video at some point but i am bad at videos!!

even if you pack the game itslef entirely it will cost you 8 GB with all languages.

Hi Razor
do you have any plan to add leviathan and hydra?

yeah but it will be part of xtool, currently busy with the project so you're gonna have to wait.

Death Stranding
 

this game seems use oodle but i tested some files and there is no expand
Is it encrypted or i miss something:confused::confused:

It's encrypted, I took a look at it and tried to make decryption tool

will you continue to make this decryption tool ?

It will be great !

Lel you'd have to wait for these guys
https://forum.xentax.com/viewtopic.p...21829&start=45

I don't have this game, only have a few samples and I have never dealt with the encryption used in the game so wait for the people in that forum to come up with ideas and I may use their findings to make decryption tool for freearc.

Sure, we all will wait for them and you too :)
Thanks

Sorry to revive an old topic with a rather silly lot of questions, but what exactly should the arc.ini and resource folder structure look like, when attempting to use more than one of the available Oodle pre-compressors? The title I'm attempting to apply these pre-compressors too is the GOG release of "Wolfenstein II (2): The New Colossus", the Oodle stream scanner tool indicates both Oodle Mermaid & Selkie are used.

I've only ever compressed titles using the Oodle Kraken precompressor included with XTool 2020 and have never used this project before (out of both a lack of understanding and a lack of need). My arc.ini currently looks like this, with the string of compressors to use (Tiny Compressor), looking like this.

Two areas of confusion that I have is how exactly does oo2rec(k/m/s).exe know where to look for the oo2core..._win64.dll, and where should this .dll be located relative to the compressor's .exe? The current structure I have looks like this (oo2core_5_win64.dll is the same .dll present in the "Wolfenstein II: The New Colossus" root directory.).

I've gone through the included arc.ini in the attached tool on this topic as well as the pack/unpack.bat files but I still can't seem to understand how to operate these tools. If anyone is willing to help me out and requires any additional information I am happy to do so. Thank you for reading through the entirety of this rather lengthy post, any help anyone can offer will be greatly appreciated!

Your arc.ini is incorrect.

This is the packcmd given. {compressor} translates the name of the method into the exe file used for the method.

Put the oodle core in the same folder as the oodle precompressor. It will automatically use it.

Then your method: oo2recm+oo2recs+srep+lolz

Thank you very much for your speedy response! Unfortunately I'm still unable to compress the files of "Wolfenstein II (2): The New Colossus". My arc.ini now looks like the following, and the folder structure for the Oodle pre-compressor tool now looks like the following. When attempting to compress the files, however, I recieve this error. The same error is received regardless of the order of the Mermaid & Selkie Oodle pre-compressors used. I'm honestly rather confused why this tool refuses to play nicely.

Brother, I have mentioned it before, that you have to use <stdin> <stdout>.

Here, for your satisfaction i have tested it on your favourite tool.

$$arcdatafile$$.tmp $$arcpackedfile$$.tmp :
<stdin> <stdout> :
Arc.ini :
Note : All test are performed using Tiny Compressor v1.4 and always use <stdin> <stdout> when using constants.

Ah, I assumed that and could be used interchangeably, thank you for clearing this up!

This is true only in some cases. E.g. XTool and SREP can either run in stdio or $$arc$$ mode. It's best not to deviate from whatever is given to you in the packing example unless you are prepared ro sit and test various methods.