TT Games Error Lego Star Wars TFA

[RC-3197]

Hi, i've successfully used quick bms on many games but lego star wars the force awakens seems to be having issues. It keeps saying "Alert: the CRC of the file ... has not been found I extract the current file" on pretty much every file (in the dat) and the end result is partially legible files, with lots of garbled nonsense in the beginning. Luckily the first (most of the actual game.dat files are having this problem) one of the files having the issue is only 484MB so here is a link to it Game.dat hopefully this can be sorted out quickly.
P.S. I've also tried it with the 4gb version and an older version of quickbms

[aluigi]

Download the current script 0.9.11, open it with a text editor and set FORCE_CRC_BITS from 0 to 32.
This is one of those cases in which auto-guessing fails.

[RC-3197]

Download the current script 0.9.11, open it with a text editor and set FORCE_CRC_BITS from 0 to 32.
This is one of those cases in which auto-guessing fails.

This worked great, thanks for the help!

[RC-3197]

Update:
A few files are still corrupted (ex ADMIRALACKBAR.TXT in \CHARS\MINIFIGS\ADMIRALACKBAR along with one other directory) but way better than before. It had the same error as before but only on the files in three directories admiral ackbar, macetrooper, and PZ-4CO. They are towards the end of the dat file. I'm not the only one with this issue, someone in a steam discussion (response #26, and #27) specifically mentions Admiral Ackbar and the Macetrooper being corrupted after extraction, and I'm pretty sure they experienced the same issue.

[aluigi]

The file is not corrupted due to a bug, it's just the first filename available since no other names matched the hash.
The alternative was not extracting the file at all or using a dummy filename.
It's not a bug since the crc is correctly calculated using the full filename in capital letters with backslashes, in fact only 9 files have this problem on the thousands available in the archive.

[Strudicious]

Know this post is 2 years old however I am having the same problem and have no Idea what you mean by Download the current script 0.9.11 I'm probably just stupid but can someone post a link of the download please?

[Acewell]

http://aluigi.altervista.org/bms/ttgames.bms

[Strudicious]

http://aluigi.altervista.org/bms/ttgames.bms

Thanks Worked Fine!

[GMatias]

Hi! I'm having a similar problem with this game (and in case it matters, this is the NTSC-J version of the PS3 version of LSW:TFA). I'm also using this software for the first time, so might be missing something SUPER obvious.

I have run the latest ttgames.bms script using quickbms_4gb on it and while it will extract the three smaller .dat/.hdr files (~1.5gb each), it chokes when it gets to the 19gb PAD.dat file. There is no corresponding .hdr file for PAD like there is for each of the other .dat files. The error message I get is:

Error: incomplete input file -1:
Can't read 4 bytes from offset 0000000000000000.
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.


Last script line before the error or that produced the error:
114 get TYPE_BOH signed_long MEMORY_FILE
coverage file 0 0% 28 18770885377 . offset 0000000000000008

Any help would be appreciated! Thanks!

[aluigi]

Wow 19 Gb!
The code in that part of the script does the following if there is no hdr file:
- check if the dat file is compressed, in this case it will be decompressed in a new temporary file
- get a 32bit field and convert it to a longer 48bit number
- get another 32bit field
- use the former field as a position and the latter as a size

The error you get means that the size field is zero since the MEMORY_FILE can't be accessed at offset 0.
You correctly used quickbms_4gb_files, so it's all ok.

Unfortunately I don't know why that field is zero since it never happened with my samples.

If you want you can upload the two files generated by the following script when used on that huge dat file so I can check what's wrong there:
http://aluigi.bms/file/filecutter.bms

[GMatias]

I've attached the two files generated from running filecutter.bms on the big DAT file. I added the dat extensions so that they could be uploaded to the forum (the original filenames were identical except for the .dat at the end).

Thanks!

[aluigi]

PAD.dat has no content, it's just a sequence of zeroes and indeed the name suggests that's it's a totally useless file ("padding").