The minimum game size is 30 GB
Most likely your version is without multiplayer files:rolleyes:

Ah thanks for that, with multiplayer files I got a final size of 11.5 GiB (the MP files clocked in at ~600 MiB). It's possible and I'd wager likely a smaller size can be achieved, should both the main + multiplayer files be packed together, but I had the multiplayer files as an optional component.

For anyone interested, with MSC I only saw a ~9 MiB reduction. Upon testing I wasn't able to successfully decompress these files. It's hard to say whether this is within variance of running the data through LOLZ, or pure gains due to MSC, however since I wasn't able to get a valid result, I don't think I can comment much on the matter.

God of War (2018) potential Oodle streams?
 

Hi all,

Does anyone know if there are any tools/methods to ID Oodle streams? The only means I know of, is identifying the 0x8c byte in a given sample, but at least in the sample "*.lodpack", "*.texpack" and "*.wad" files that I tested against, I had no luck in finding any streams, when running the sample separately through oo2reck/m/s, and against 3 different "oo2core_7_win64" libraries.

The reason for my testing is this off-hand note in the readme for one of the more popular modding/unpacking suites for the title, which I was using to determine if any additional assets could be ripped and packed separately for further gains.

https://fileforums.com/showthread.php?t=102453

This comes with oodle scanner, just drag and drop file.

Isn't the 2018 God Of War a PlayStation exclusive? That explains why its using Oodle.

I know the PC re-release in 2022 uses no compression.

I feel like a right rube again, I contacted the developer and got a message back, just before reading the responses here, the developer also confirmed there isn't any compression used, if I'd taken the time to read through the github release notes I would've seen they officially noted this.

It seems odd the developers wouldn't use Oodle on the PC release given how many folk still have older and slower hardware akin to a PS4's specs.

Perhaps I am missing the point, but wouldn't it make more sense for the developers NOT to use Oodle for the PC release? Older hardware would offer poor decompression speed compared to being able to just read game data from disk straight into memory and have it ready to use.

I was thinking more so about read operations from the disk being less intensive if the data was compressed but yes I'll admit I wasn't thinking about the fact it'd be more intensive on a user's memory and processor!

i try still got error bro, stuck in decomp, now i excluded of error files

Sorry, the version is wrong
You should use XTOOL 1908 R3.

The "Xatab Repack" also has used the XTOOL 1908 R3 to pre-compress the game.

Tortuga: A Pirates Tale (v1.0.1.46268)
 

xtool 0.3.21 + srep + lolz

(Non-Eng. Loc. Ripped)

4.97 GiB >>> 2.58 GiB

Note: Perhaps others will have better luck than me but every bank dumping utility I tried to run this title's "*.banks" through failed on every account.

Use the FSB5 quickbms script.

+ the devs included a full copy of the movies folder inside the largest .FUK file so you can XTool erase it.

Ah cheers I'll check out the quickbms script, I noted the duplicate movies but I'm fairly sure srep picked them up. I might be missing something but is there a point in blanking out the duplicates, since it'd still be the same amount of data written to disk.

Now that I think about it I didn't actually test to see if deleting the loose files would cause the packed duplicates to be used in their place, or if the loose files were used at all, I'll definitely have to have another quick crack at this one.

Ghostwire: Tokyo (10.10.2022)
 

Method #1
__________________________________________________ ______

Method #2

CT: 2H
DT: much longer + high memory usage

Martha Is Dead (1.1028.0) (BUILDID 9853789)