TT Games (LEGO) .DAT Extraction Issues

[ProfBrickkeeper]

I'm currently working on extracting the .DAT files from TT Games' LEGO Dimensions for PS3, but the current ttgames.bms script seems to be having issues with a few of the archives.

When trying to extract DLC30.DAT, I receive the following error:

Code: Select all

Alert: the crc of the file ADDITIONALCONTENT\OPUS_TAGCHARSWAVES\ICONS\CHARACTERS\TI_TTG_BEASTBOY_3_NXG.TEX has not been found, I extract the current file SIZE (442110) and ZSIZE (59575) differ at offset 0x048fe087, contact me

Separately, trying to extract DLC8.DAT, I get the error:

Code: Select all

Error: [myfseek] the offset 0x00400100 in the file -1 can’t be reached

Last script line before the error of that produced the error:
   258 goto NAME_OFF MEMORY_FILE

Furthermore, from the few files the script does seem to extract, it appears there’s an additional layer of obfuscation in the archives, with the extracted files unintelligable.

Here’s a link to the files in case anyone is interested in trying to take a closer look at the issues I’m having. Thanks!

[aluigi]

Try using quickbms_4gb_files.exe
The reason is that some TT games use 64bit hash algorithm for their filenames and quickbms.exe isn't able to handle them due to its 32bit integer limitation.

[ProfBrickkeeper]

Try using quickbms_4gb_files.exe
The reason is that some TT games use 64bit hash algorithm for their filenames and quickbms.exe isn't able to handle them due to its 32bit integer limitation.

I just tried using quickbms_4gb_files.exe on the files and received the same errors. Evidently there's some larger issue at play here, which may require some closer examination.

[aluigi]

I checked the files and DLC8.HDR has no sense, I mean that it's not a ttgames format.

Instead DLC30.HDR is a ttgames format but there is something really weird, maybe it's just a corrupted file.
First of all the problem of the filenames crc can be bypassed by setting the FORCE_CRC_BITS variable at the beginning of the script to 32.

And then it happens what is really senseless, see here:

Code: Select all

...
. 000008bd
. 00087308 get     OFFSET     0x00106e9d 8
. 00087310 get     ZSIZE      0x000064b3 4
. 00087314 get     SIZE       0x000064b3 4
.
. 000008be
. 00087318 get     OFFSET     0x045be825 8
. 00087320 get     ZSIZE      0x00003d43 4
. 00087324 get     SIZE       0x00003d43 4
...

They are two sequential entries in the TOC, the first one is correct as you can see with a hex editor on DLC30.DAT while the second one points to a wrong location probably in the middle of a file.

Therefore I can do absolutely nothing with corrupted files, the script is correct.