The way it was calculated was to look for the hex sequence 0xa1a1a1a1 and subtract the size of the file table to get the start, but this didn't always work. The file table usually starts at 0x394 in GAME.XEPACK, 0x368 in GAME.PCPACK, somewhere after the string of 0x01 bytes. In LOCATION_BLACK_CAT_1...

Having looked at the other samples, some of them don't fit the logic of my script. Some of them have the file table starting in a slightly different place. There's no obvious offset to the start of this table because the logic used doesn't always work, so I'm stumped on how to calculate it accurate...

You shouldn't need to change the file data at all - it looks like you've swapped every 4 bytes in the whole file, as all of the texts etc. are the wrong way round. This definitely won't work as Big Endian only applies when reading numbers; any strings should remain the same, although there are expe...

Yes... If the format is identical, then it might be enough just to set any scripts to read Big Endian instead of Little Endian on the PC version. Hello again! So I found the way to swap endianness from big- to small-. But now *36 script-extractor says that offset if wrong: Wrong offset, so we try a...

Yes, everything is mirrored because the XBox format is Big Endian, so numbers and strings are the other way around compared to the PC version. Any scripts that reads those files need to take into account the difference and read them accordingly. If the format is identical, then it should be a case ...

Yeah, it looks like the original Python script had the extension in hex, so just a quick modification to my script: s3.zip So interesting.. *36 files from PC and XBOX seem to be similar, but all words and strings in XBOX file looks like.. Mirrored? Do you know how to fix it? https://sun9-35.userapi...

DKDave wrote: ↑Sat May 01, 2021 8:17 pm Yeah, it looks like the original Python script had the extension in hex, so just a quick modification to my script:


s3.zip

Hmm. I really got now *36 file instead *54, thanks! But classic 36-extractor script still doesn't extract this file. It's so odd

I'm not sure from looking at the script. I've rewrote a QuickBMS script using the same logic that should work for both file versions, if you want to give this a try: s3.zip OMG MAN YOU'RE AMAZING! It's really works! :D Now we got important file with extension *54 that contains textures, meshes and ...

The reason it doesn't work is because the XBox 360 files use Big Endian format for storing numbers, so the script as it is will only work on PC. Assuming the file structure is identical, you should be able to change the following line and see if it works: bs = NoeBitStream(file.read(fileLen)) Chang...

Hi everyone! There are different topics that solved two problems: how to extract PCPACK archives from Spider Man 3 and Spider Man: Web Of Shadows on PC. But there are no topics with description of how to extract XEPACK files. It's the same files but from XBOX360 game directory. Also these files got ...

he was just demonstrating how to make an extraction script in python for Noesis, extraction is already taken care of here with a modified bms script though :D http://forum.xentax.com/viewtopic.php?p=129063#p129063 the python script in mario's video is also reading the wrong integer for the file cou...