Is there a list of which files correspond to which character? I.E. I know n_fz201 is Anna (pure luck figuring that out, it was the first character I tried the tool on), but don't want to have to extract every set to know the rest.
This is amazing, I'm far from being skilled enough to do something like this, but I was wondering if you folks were able to pull fonts from the game assets, I have been looking for KH fonts for years... Especially the cutscenes comics font and the KH3 system typo (more recently),
If you figure out how to extract the .pak files please let me know
"How" isn't the question. It's "when". They're encrypted, and people are hoarding the decrypted eboot.bin needed to obtain the key and decrypt the paks. If you want it, ask people in the PS4 scene. Nobody outside of it has been able to decrypt the paks.
If you figure out how to extract the .pak files please let me know
"How" isn't the question. It's "when". They're encrypted, and people are hoarding the decrypted eboot.bin needed to obtain the key and decrypt the paks. If you want it, ask people in the PS4 scene. Nobody outside of it has been able to decrypt the paks.
New version released. Now supports textures and auto-texture loading for maps. It will work for Kingdom Hearts 3 and for some other games.
You can use the tool to convert individual assets, or all assets in a folder.
1. To convert one asset, drop asset file onto the tool, or run the tool from command line with asset filename as parameter.
If asset file contains a texture, in will be exported to "textures" subfolder in Directx10 DDS format. After that you can convert them to the format you like.
If asset file contains static or skeletal mesh, in will be exported to ASCII. Raw data will also be saved in "staticmesh.raw" & "skeletalmesh.raw" folders for later use in map extraction.
If asset file contains a material, it will create "material.db" file with information for later use in map extraction. If "material.db" file already exists next to the tool, it will be updated with newly found materials.
If asset file contains a blueprint, it will create "blueprint.db" file with information for later use in map extraction. If "blueprint.db" file already exists next to the tool, it will be updated with newly found blueprints.
2. To convert all assets in a folder, place the tool in that folder and run it. Tool will search that folder and all subfolders for .uasset files and try converting them all. When prompted "are you sure?" you can press "enter" to confirm or Ctrl-C to cancel.
3. To convert maps, drop .umap file onto the tool, or run the tool from command line with umap filename as parameter. Current version will extract static meshes, skeletal meshes, blueprint-generated meshes, lights and landscapes from a map.
For map extraction to work, "staticmesh.raw" and "skeletalmesh.raw" folders with previously extracted data must be in the same folder with the tool. If some models will be missing, tool will give messages.
If "blueprint.db" file will be next to the tool, it will try and place all models mentioned in blueprints on the map. There's no proper blueprint support, so some models may be placed incorrectly.
If "material.db" file will be next to the tool, material information from that file will be used to place texture names in the output ASCII file, so when loaded, all textures will be applied automatically. By default, ASCII file will have texture names with ".PNG" format. If you converted textures to another format (for example .JPG), you need to replace ".png" to ".jpg" in ASCII file with any text editor before loading it.
If there will be no "material.db" file, or some materials will be missing in that file, tool will give messages and material names will be used for textures. In that case you can search and apply them manually. Some models do not use any textures (for example, solid color materials or lights). For such models ascii file will also have material name as texture name, so if you want, you can open that material in umodel and see whats the color and other properties.
Last edited by daemon1 on Mon May 11, 2020 9:03 am, edited 1 time in total.
- blueprints "workaround" support
- instanced static mesh support
- lights export
- materials with no textures dont make error messages anymore
note: blueprints are not properly supported, because i'm not going to read their code at all. This would be just too complicated. Since most blueprints just have 1 mesh inside and some logic, i'm assuming they are simply placing that mesh. In reality, the mesh position may be edited or calculated accoridng to game logic, or removed at all - this is all NOT supported.
For skeletal models to have textures auto-loaded on the map, you'll have to re-export them.
daemon1 wrote: ↑Fri Apr 24, 2020 5:43 pm
If "material.db" file will be next to the tool, material information from that file will be used to place texture names in the output ASCII file, so when loaded, all textures will be applied automatically. By default, ASCII file will have texture names with ".PNG" format. If you converted textures to another format (for example .JPG), you need to replace ".png" to ".jpg" in ASCII file with any text editor before loading it.
If there will be no "material.db" file, or some materials will be missing in that file, tool will give messages and material names will be used for textures. In that case you can search and apply them manually. Some models do not use any textures (for example, solid color materials or lights). For such models ascii file will also have material name as texture name, so if you want, you can open that material in umodel and see whats the color and other properties.
hello, I put the material.db, base materials, and basematerialinstance in the same folder with the umaps. I wasn't sure what I needed to all be together? still says missing materials on export so I'm confused on where the exported materials need to go? sorry
sorry, I'm asking how does it extract along with the umap? where does the location of the necessary files need to be? for example, I move the exe in the Material folder with the material.db and and drag the .umap to export in there, but it still says it can't find anything.