Need Help extracting Lego Dimensions DLC xbox 360 dat files

[RyKen]

Hi quickbms with ttgames.bms is having problems extracting theses Lego Dimensions DLC xbox 360 dat files. Doses any one know a way to extract theses dat files with no errors?

Code: Select all

Alert: the crc of the file ADDITIONALCONTENT\OPUS_ADVENTURETIME\COMMONOBJECTS\CUT_VIKINGHELMET_NXG.NXG_TEXTURES has not been found, I extract the current file

[aluigi]

Open ttgames.bms with a text editor and replace the following:

Code: Select all

math FORCE_CRC_BITS = 0

with

Code: Select all

math FORCE_CRC_BITS = 32

The reason is that sometimes the autoguessing code for understanding the correct CRC format fails.
Hopefully one day I will find an automatic solution

[RyKen]

Open ttgames.bms with a text editor and replace the following:

Code: Select all

math FORCE_CRC_BITS = 0

with

Code: Select all

math FORCE_CRC_BITS = 32

The reason is that sometimes the autoguessing code for understanding the correct CRC format fails.
Hopefully one day I will find an automatic solution

you are the best!!! everything is extracting! Thanks!

i have been running into this error on GAME3.DAT what does this error mean? did the file extract fully? here's the file if you want to take a look at the file

Code: Select all

GAME3.HDR/file
GAME3.DAT/file

Error: incomplete input file 0: GAME3.DAT
Can't read 4 bytes from offset 000000007a04d391.
Anyway don't worry, it's possible that the BMS script has been written
to exit in this way if it's reached the end of the archive so check it
or contact its author or verify that all the files have been extracted.
Please check the following coverage information to know if it's ok.

coverage file 0 97% 1981061485 2040528896 . offset 000000007a04d391

Last script line before the error or that produced the error:
365 getdstring SIGN 4

Press ENTER or close the window to quit

[aluigi]

Very weird.
I didn't download the DAT file but I guess there are more referenced files than those really available, or maybe the last file has a size of zero bytes (so when it goes to that offset for reading the 4 bytes SIGN it fails).
The 97% coverage is very good btw.