Question about automating generation of start & end file offsets for stored archives

[Masquerade]

Originally Posted by Dragonis40

Good morning, how can I use this instructions for videogame repacking? I mean, to reimport files into .pck file, I need the original one. I think it's better to create a new .pck file without the original one, otherwise it's useless in terms of installation videogame.
So, starting from the extracted files from .pck file, how can I "reduild" a new .pck file without the original one?

PCK archives don't use compression, so what you can do is the following:

- use Bincat by Aluigi to concatenate the output wems into one large file

- use hdiffz to make a patch between the original PCK and the concatenated data

Then, in your repack installation, concatenate the wems with bincat and apply the patch you made with hpatchz to restore the original PCK.

[Dragonis40]

Originally Posted by Masquerade

PCK archives don't use compression, so what you can do is the following:

- use Bincat by Aluigi to concatenate the output wems into one large file

- use hdiffz to make a patch between the original PCK and the concatenated data

Then, in your repack installation, concatenate the wems with bincat and apply the patch you made with hpatchz to restore the original PCK.

Thank you for your reply! Once all .pck files have been decompressed with quickbms, the output files are: .wav, .bnk, .dat files and no .wem files.
So how can I correctly use Bincat and hdiffz procedure?

[Masquerade]

Originally Posted by Dragonis40

the output files are: .wav, .bnk, .dat files and no .wem files.
So how can I correctly use Bincat and hdiffz procedure?

No need to worry about the different file types, just make sure all of the extracted files are in the same folder. Then, in cmd do:

bincat extracted_data\* new.pck
hdiffz-x64 new.pck old.pck patch.diffz

To apply the patch in your repack installation, do:

bincat extracted_data\* new.pck
hpatchz-x64 new.pck patch.diffz old.pck

[Dragonis40]

Originally Posted by Masquerade

No need to worry about the different file types, just make sure all of the extracted files are in the same folder. Then, in cmd do:

bincat extracted_data\* new.pck
hdiffz-x64 new.pck old.pck patch.diffz

To apply the patch in your repack installation, do:

bincat extracted_data\* new.pck
hpatchz-x64 new.pck patch.diffz old.pck

Hello! I've done what you suggested me, but I can see no improvement at all in terms of file compression. The resulting files from hpatchz have exactly the same size of original .pck file. So, what' the advantage?

[Dragonis40]

Originally Posted by Dragonis40

Hello! I've done what you suggested me, but I can see no improvement at all in terms of file compression. The resulting files from hpatchz have exactly the same size of original .pck file. So, what' the advantage?

Hello everybody! what I don't understand is how to correctly compress these pck files. I'm talking about "A Plague Tale: Requiem". There's a file called "VO_MEDIA.PC.PCK"; using WWise.bms and quickbms, I can extract all files inside and they are, of course, .wem files. Then, I've tried to compress them using WemTool.exe, but the resulting compression is very poor. So, I've used bincat.exe to create a concatenated file with all .wem files and hdiffz-x64.exe to create a patch between the original PCK and the concatenated data.
Which file do I have to use in my repack? Only patch.diffz file? I don't think so, because, in order to create the original "VO_MEDIA.PC.PCK" file, I need patch.diffz file and .wem file or the file create by bincat.exe. So I increase the final .bin file, instead of reducing it. So, how can I do?