Tool for Dirge Of Cerberus (Final Fantasy VII).
It can currently extract textures & skeletal models with bones, weights, UVs, etc.
(before converting models you have to extract files from game archive
you can do this with Luigi's BMS script for FF13, or with noesis)
Drop model/texture file onto the tool and it will output models as OBJ & SMD, textures as TGA
OBJ will just have geometry. SMD will have everything.
If you use it on static model, it will output empty files.
Final Fantasy Dissidia NT tools.
Also work with Warriors Allstars, Dynasty Warriors 9, Nioh, Nioh 2, Fire Emblem Warriors, may work with other games.
Usage: drop something on the tool
1. G1M will produce ASCII model and SMD skeleton
2. G1T will extract all textures in "texture" folder
3. GMPK, PG1M will extract G1M & G1T
4. MDL (from Nioh) will extract G1M
5. bin.gz (from Fire Emblem Warriors) will extract G1M & G1T
Important NOTES
- ASCII format will have extended info for correct bone rotations. Noesis plugin that reads them is included.
- If model skeleton is in separate file, you need to drag both model and skeleton, dropping the skeleton onto the EXE. Alternatively, you can run the tool with 2 parameters:
ffsnt <model> <skeleton>
"Big endian" version. For console games.
Final Fantasy 7 remake tool.
Supports static & skeletal models, maps, textures. Usage instructions below.
Textures will be auto-assigned if you extract them before loading the map:
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 export material info in a text file, and 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.
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.
