It doesn't look encrypted. You'll need to figure out the format of the vertex data, etc.

The file isn't exactly an archive; it's a collection of strings with a bit of metadata. QuickBMS can probably do operations to dump everything to text, but you're really better off finding a more general purpose scripting language to use for exporting and importing.

The format seems straightforward enough... struct header { char magic[4] = "TRES"; int version; int entryCount; int unknown; // 16 }; struct entry { int messageIndex; int keyTextOffset; int type; int valueTextOffset; int reserved1; // always 0? int reserved2; // always 0? }; struct main { ...

-Keywords such as Skyline, Battle, Chal(lenge missing) and text strings about 'Microsoft Shader Compli 2.0' (which got repeated an awful lot) were found Sounds like a bunch of compiled shaders, possibly XMem compressed. Notice how the word "Compiler" contains "er", which is also...

Looks like the files have shitton of junk at the beginning instead of a valid DDS header. It seems the header's just XORed with a string or something. Search for a string that contains "ancalsdh#@$%92875ey134591243".

Edit: See this.

The DGTEFF over at the Xentax Wiki is a great place to start learning about reverse engineering game archives. If you can follow that guide, you've learned the most basic skills needed for figuring out archives. http://wiki.xentax.com/index.php?title=DGTEFF Something else to keep in mind are common ...

I'm not sure if there's a catch-all localization app. In any case, the minimum tool you need is a hex editor. With a hex editor, you can explore binary files. If you state what game you're working on, maybe we can track down the file for you.

Localization data are commonly stored in XML, CSV, text flat file, or a custom binary format. The first three are easy to modify, while the last is harder. To find those files, first you'll have to extract whatever archive the files are in, if applicable. Then, use a file searching program to search...

Papipone wrote:

Code: Select all

int unyakuza(unsigned char *in, int insz, unsigned char *out, int outsz, int check_head)

Do you know what the "unsigned char* out" argument of the function is symbolizing ? (It is from the unyakuza.h file provided with quickbms).

Isn't it just a pointer to the output buffer?

I think someone just used a .WAV extractor or something.

Valve seems to have something similar for Dota 2 called a shader mask. While the masks differ from game to game, you may find some similarities. See this PDF file for details.

You haven't answered the most basic of questions: what game is this file from? Also, what path is this file from (so we know what type of contents it might contain)?

If you want to extract CustomPaks, use the CustomPak extractor. It's the most straightforward way of getting the files out. Otherwise, get comfy with a hex editor and study the format.

Step through the decompression code with a debugger.

Huh, I thought all the wave files were packed into one big wave file. Apparently they're still doing the "join the data together" thing they were doing previously. Names are in the segments chunk, I believe.