Quote:
Originally Posted by Masquerade
^^
With that amount of zeroes, that is almost certainly not the correct AES key for this game (or any game).
Run the oodle scanner over the pak or ucas file and you will see streams appear.
Code:
mmermaid,l7:mkraken,l7:9:mzlib
This is where things are going wrong. Just use kraken and mermaid and zlib algos without any extra arguments. |
It is. Take "Lords of the Fallen" as an example, where the key looks funny aswell
Code:
0x0200000003000000020000000200000002000000020000000300000003000000
With that key you will get almost all streams and output is better than without. I was surprised aswell.
Furthermore if using DSG, you have to set correct oodle library as parameter (which is just a fake parameter for xtool). In this case the correct parameter should be as follow:
But I said you have to use the other v2.9.10 library, and even in this case there is a fake parameter possible, namely
which just tells DSG which library to copy near xtool.exe for compressing/decompressing (in this case "oo2core_9_win64_2.dll", which will be renamed to "oo2core_9_win64.dll" from "core_2.9.10" folder).
Edit: I still prefer to run multiple instances for xtool for different codecs because sometimes things will get broken if you use -d1 option and more than one or two methods, at least with current public xtool version and my testing (archive data corrupted and things like that). But honestly I don't know if this has anything to do with xtool or srep or DSG.
In this case I would use something like this for DSG
Code:
xtool:d1:mue5,k0x09000A000A000A000B000C000D000D000D000E000E000F001000120012001200:mmermaid:mkraken:core_2.9.10:lib_2+xtool:mzlib+xtool:dd3+...
Edit 2:
mermaid+kraken / ue5<key>+mermaid+kraken
Code:
Streams: 770978 / 770992
Time: 00:42:03 (CPU 03:21:13)
Size: 29.8 GB >> 51.2 GB
Done!!!
Streams: 865592 / 877159
Time: 00:45:44 (CPU 03:40:22)
Size: 29.8 GB >> 51.9 GB
Done!!!
Did not tested with zlib