ZenHAX

anyone have luck ripping destiny 2 yet ?? id love to get a hold of the In game Hud ui textures >.<

Would assume no tools were made yet for D2?

There is my script that I "suppose" works correctly when you copy&paste the keys provided by Sir Kane in the 3 variables at the beginning of the script:
http://aluigi.org/bms/destiny2.bms

Example:

set g_AESKey0   string "0xD6, 0x2A, 0xB2, 0xC1, 0x0C, 0xC0, 0x1B, 0xC5, 0x35, 0xDB, 0x7B, 0x86, 0x55, 0xC7, 0xDC, 0x3B"
set g_AESKey1   string "0x3A, 0x4A, 0x5D, 0x36, 0x73, 0xA6, 0x60, 0x58, 0x7E, 0x63, 0xE6, 0x76, 0xE4, 0x08, 0x92, 0xB5,"
set s_NonceInit string "0x84, 0xDF, 0x11, 0xC0, 0xAC, 0xAB, 0xFA, 0x20, 0x33, 0x11, 0x26, 0x99,"

Let us know if it works

Hello everybody,
I compiled and tested the cpp file by Sir Kane.
As a result you get binary files from the respective package. Currently only certain files can be identified (RIFF format).
At the moment I'm trying to convert these back to normal .wav files, so far I have not been successful.

Greetings...

I will release a tool in the next couple of days which will support audio/sound files, textures/images, videos, and all kind of text files (dialogs, names, lore, descriptions, etc). I didnt make a final decision what I will put into the first release but it will definitely include a "one-click-solution" where you just have to select a PKG and can view the assets of the given filetypes mentioned above.

Models is still too early in WIP progress and will not be supported in the first release, but me and others are working on this.

You can see a first preview of this tools right here: Destiny 2 Tool (Youtube Preview)
(Its likely that a lot of it will be changed in terms of functionality and interface)

Hey,
@Ginsor
The program looks very interesting, how did you actually manage to get the pictures from the UI packages?

Only as side information how you can get the audio files:
Simply use the ww2ogg program to convert the binary files with a special PCB package.

Best regards and
happy data mining

Good day everybody,
can you help me with one thing?

I have been trying to extract the package w64_ui_02af_12.pkg for a few days, but unfortunately I get the following error: "Block 0 uses non-loaded patch ID 1."

What I have found out so far:
- The patch ID of the header is 12
- The patch ID of the block is 1

The script assumes, however, that the patch ID of the block is exactly the same as that of the header.
I would be interested to know what these PatchID's say, does one of you know by chance?

Thanks and best regards.

you have to keep the other w64_ui_02af_*.pkg files in the same folder. in your example it looks for w64_ui_02af_1.pkg but cant find it

You ever finish it?

All features i want it to support in the first release are finished and working fine. Its only like i know have to do some quality of life things, re-arrange the UI, and clean up the code a bit. However, unfortunately Im quiet busy these days but I hope i can get back to that soon.

Hey! Any update on the tool?

Tool is working fine as it should but I wont release yet as I will wait for Forsaken to be released (Im already working on it)

Awsome! Glad to hear project is still going. Will the released version have model/texture export?

any updates on the tool yet?

• SirKane
• aluigi
• Ginsor
• Ehnoah
• Ernegian

Anybody heard from Detox/Xenon lately? I'm going to shoot the information from this thread over to him to see if he can just build me a couple of classes to add into an application and I'll build something everyone can use.

Ginsor if you wrote that in C#, send it my way and I'll make the additional touches (or if you could send me the decryption and extraction classes, that'd work.)

Lastly, per legality, what of this information are we able to upload? For example if I extracted all text from all packages, could I upload it all to a NoSQL database like Firebase? That'd be a great way to reduce load on the end-user when updates/patches/DLCs are released for Destiny. I imagine, on first launch, pulling a JSON response of the entire Firebase database and storing it locally to both reduce load times and bandwidth. Once an update comes out, I could literally just extract the information again, overwrite Firebase and push a notification (to anyone currently in the application) to rebuild the local database.

Let me know something.