Jump to content

Call of Duty: Vanguard (PS4) - "KAPI" *.xsub

Recommended Posts

Unpack is possible, but repack will be pain in ass. There is table which has some values but they are somehow converted or manipulated in a way which doesn't make any sense to me.

Compression is oodle.

Here's guessed struct.

//--- 010 Editor v14.0 Binary Template
//      File: 
//   Authors: 
//   Version: 
//   Purpose: 
//  Category: 
// File Mask: 
//  ID Bytes: 
//   History: 

local uint32 i,j,k;

struct HEADER {
    char Magic[4];
    uint16 Flag,Version;
    uint32 Unknown_0,Unknown_1,Unknown_2,Unknown_3;
    uint32 FileSize,Unknown_4;
    uint64 FileHASH64;

struct INFO {
    uint32 Files,Unknown_0,BaseOffset,Unknown_3;
    uint32 DataSize,Unknown_4,FilesTmp,Unknown_5;
    uint32 TableOffset,Unknown_6,Unknown_7;


struct TABLE {
    uint64 NameHASH64;
    uint32 Offset,Size;// These values are most probably modified by something

I checked first file at BaseOffset and it has another 44 bytes header describing something + compressed size/decompressed size

  • Like 1
Link to comment
Share on other sites

Or you can do it by a dirty way. But i think you won't be able to reimport. Also qbms doesn't have oodle compressor so you must compress it manually with external compressor.

comtype oodle
get BaseFileName basename

	findloc BaseOffset string "\x00\x00\x01\x00\x00\x00\x01\x0E"
	goto BaseOffset
	getdstring Dummy 0x8
	get ZSize long
	get Size long
	getdstring Dummy 0xC
	savepos Offset
	string Name p= "%s/0x%08x.dat" BaseFileName Offset
	clog Name Offset ZSize Size


Link to comment
Share on other sites

In the TABLE struct, where you have Offset, Size - the second value is the Offset which needs to be multiplied by 0x80 to get the correct value.  The first value is the total size of the data - bit 0 is a flag for compression, and the rest needs to be shifted right by 1 to get the total size.

For compressed files, the 0x2c header for each file seems to start with 0x1df0, then the 8-byte hash value from the file table, ZSIZE at 0x18, SIZE at 0x1c, relative offset to compressed data at 0x20.

The uncompressed files seem a bit more random, they start with a table of offsets, but no item count.



  • Thanks 2
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...