From my ram dump we found out the engine itself uses DDS-DXT, the jpeg encoded textures weren't in the RAM, just the DDS streams.
Getting to the textures themselves is a little bit difficult, you really have to have a whole setup to parse the files.
Thusfar in development of my new tool, I can relatively easy get to the textures I want.
- BigFiles, contains concatenated files aligned to 0x800.
- Matching .idx files (encrypted to SDAT on disc versions, EDAT on PSN versions) define content groups, offsets, UIDs, sizes, and eventual extra sizes.
- Decompiling the Lua scripts we can get the linked script functions, characters and catalogs (everything is parsed as a Lua table, characters are empty, a catalog has to be
assigned to them).
- A catalog begins with a main entry, and after that come other archives which contain the mesh data and textures.
- The main entry of the catalogs consist of MESH_DATA, ENGINE_TEXTURE_FILE and other communicators.
- The texture file entries and such function as meta data. Before the actual communicator starts there's first a table with offsets into the other files after the main entry.
- For a texture file this table indexes the mipmaps.
The texture entries:
- Starts with a short header, then a table into what we think are jpeg chunks.
- The table provides offsets, compressed and decompressed sizes.
- The chunks are not compressed using:
- And probably nothing else as there's only references to Edge ZLIB in the executable, and that's not used here.
- Default decompressed sizes the textures are split up in seem to be mostly 0x6e00 and 0x20000
- The stored textures seem to be in some sort of jpeg format.
chrrox managed to get some part of this supposed jpeg format to show up:
If anyone wants samples I can provide all texture binaries from Jodie's Prologue/Navajo model and a DDS file ripped from the ram dump, just shoot a PM!