Leaderboard

There are at least two types of i3d file formats, used within the .i3d files used in ape escape 3 and Rule of Rose uses .i3d files in .mdl files. I3D_BIN: Mesh ✔️ Bones ✔️ Skin ❌ I3D_I3M: Animation ❌ Tools: https://github.com/Durik256/Noesis-Plugins/blob/master/fmt_i3dg.py - Supports meshes. fmt_RuleOfRose_PS2__i3d.zip - Supports bones (made by Bigchillghost from xentax, reuploaded into reshax for quicker accessibility)

But can't produce right width/height. It's 250 x 391 px.

WMA is an audio file format (Windows Media Audio) and can be played by VLC. SFD seems to be a font file but FontForge can't open it ARK files seems to be archive containers that contain inside them another ARK files and another files Edit: SFD is a video file format that can be played by VLC too Here is a python script with batch file to extract the contents of the ARK files, drag and drop one or more ARK files onto the batch (.bat) file Also an ARK.hexpat file you can use in ImHex ARK_File_Parser.rar ARK.rar

you should change the title to ASTRO BOT Rescue Mission, since it may confuse people as ASTRO BOT is also the name of the 2024 release!

You should upload some sample files instead of a video; a video isn't very helpful for reverse-engineering this game. NKP is a package file format used by KONAMI in PS2 games. Games I know of that use this format include Cool Girl, Gantz, and NANA, and there might be others. You can unpack NKP files using existing quickbms scripts： idstring "NKP\x1a" get NKP_SIZE long get ZERO long get FILES long for i = 0 < FILES get NAME_OFF long get OFFSET long savepos TMP goto NAME_OFF get NAME string goto TMP putarray 0 i OFFSET putarray 1 i NAME next i putarray 0 i NKP_SIZE math FILES = i for i = 0 < FILES getarray OFFSET 0 i getarray NAME 1 i math i + 1 getarray SIZE 0 i math SIZE - OFFSET log NAME OFFSET SIZE next After unpacking NKP, you'll find NKT files, which should be textures. I'm not skilled enough to fully parse them, but I'm certain that the palette starts at 0x1A0. Most textures are 8BPP, with a few 4BPP ones. Fonts might also be in some NKT files, but I haven't found them. I've attached a few NKT files, hoping that an graphic expert can analyze them. Additionally, you can find all the game's story scripts in allsc.nkp->unpack->(evt_***.nkp). They are in files with the .cg extension, which is actually a text format. You can directly view the script content; remember to use SHIFT-JIS encoding. NKT_TEXTURE_SAMPLE.zip

Actually it uses PAL8 w/ GC/Wii swizzle (There's a palette data at the end) Palette format is N64_RGB5A3 Image data offset starts at 48 (0x30) end-01-color_panel1.texture.ps3 uses BGRA8888 w/ XBOX/PS3 swizzle while end-01-color_panel2.texture.ps3 and end-01-color_panel3.texture.ps3 uses BC3/DXT5

Just use this script to extract and import Unity bundles from/to PKG archive https://github.com/bartlomiejduda/Tools/blob/master/NEW Tools/UNITY_TOOLS/Multiple_UnityFS_files_in_one_archive_script.bms There should be 712 unity bundels after extraction. Use UABEA to edit them. Follow this tutorial in case of any troubles https://ikskoks.pl/tutorial-what-is-quickbms-how-to-export-and-import-with-quickbms/

By the way, you can also get the same result with ImageHeat https://github.com/bartlomiejduda/ImageHeat

Asset Studio can open the files you provide, but some files will crash when they are opened, so you can test several more versions and use the version with the least flashback to open the most files for subsequent processing. But before that, you need to split your pkg file Divide them into block files of multiple unityfs I wrote a python script and you just need to run it python split.py pkg file Output folder If you find it troublesome to run scripts, you can also try a more professional unityfs splitter Attached a few screenshots I ran If the problem is solved, you can mark this reply as a solution split.py

Using hex2obj. Checked the mdl manually which was not too hard:

Hi, you cant open m3g files from Dead Space or any IronMonkey or Firemonkeys that have <IMxM3G> header with any tools made to be for standard M3G engine as these games uses proprietary implementation of modified M3G and later M3G 2.0 standard (which standard officially was never finalized) which are compatible with official standard M3G. You might be able to open some IM-M3G file by changing the header to standard <JRS184> and some non ASCII bytes (for example copied from other m3g file) with whatever tool made for original .m3g. I recently forked PyM3G library allowing parsing M3G file and added some very very basic support for IMxM3G (mainly dection of IMxM3G header as valid) but I'm not interested in adding more support for that format myself although I don;t think it would be very hard having the PyM3G base already and given that for example DeadSpace binary for android has a lot of symbols preserved so decompiled code from it would be actually very useful for reversing the parts added to .m3g format. So if you are interested in developing support for Dead Space models then I can guide you some more. Also must say that this library makes it actually relatively easy to create .m3g files or convert them to different formats.

Updated, please remember to feedback if you have any questions resource.py

For extracting raw data from archives you can use the same script you linked (punisher_ps2_peg.bms) as archive file format is the same across all platforms https://rewiki.miraheze.org/wiki/The_Punisher_CEG_PEG_XEG The difference is in the image encoding, PC version uses standard DXT5 or RGBA8888, while encoding seems to be different on PS2 and XBOX. I was not able to find correct setting with ImageHeat. Here's how it looks for PC sample:

Well i figured what was that 5WNR file It's file with ".rwy" extension. But you'll get only track layout without uv's and without objects. Means it's useless.

Here's a link to hex2obj and some explanation. After inserting suiting parameters for a model into the app you'll get the obj file by File\SaveAs mesh.

Darn, thank you though! 👍

Tracks have different header, So the Python can't recognize them. Can you post please gt6 track extractor and Python too?

You're probably not after all this info, but I will provide it for anyone interested. Using this attached file as an example, 00595CEA.kmy, but all the models seem to follow a strict pattern in the header-like area (I guess? It's top of the file, I'm still learning), I'm not sure what 0x0-0x30 is, but once you get to 0x40 there's a pretty consistent pattern, (all of this is big endian, btw, vertices are short signed, UVs too I believe, I'm so far unsure about triangles, they might be strips) not sure what the first 2 bytes are for, maybe a submesh count? But the next 2-4 there's always the vertices count, which for this file is 64. The next two are some sort of count, not sure, next two are the UV count. Things seem to stop there and start back up at 0x4c, where there's an integer that I'm not certain of (it leads right to the end of the file mostly, probably points to the end of reading?), at 0x50 there's always the offset for the vertices (kind of, I'll get to that in a minute), next integer is the normal vertices offset (I guess, not certain), then the UV offset, and finally this strange "basis" offset, which is where the offsets start at, in this file it's at decimal 96, or 0x60, then the offsets from earlier are relative to that point, which now makes them line up. Using these I can consistently get the verts and UVs for a mesh. I'm just completely unsure of where the triangles start, what format they're in, etc., I can sometimes get the model to load a somewhat amount of faces that look kind of correct, but I can't say for sure that I'm even in the right area. I can't find an offset that points to them, the KMY2OBJ converter says something about them but I can't understand the code, it gets a bit too complicated in that area for my understanding. And clearly something goes wrong in the conversion, because some of the models I've tried to use it on only get a piece of the model, just like chunks. I really wish I could provide more about them like you've asked, but I honestly haven't a clue where the face indices start, I've taken some guesses on this model, but nothing really gives a good result. The attached file has an extracted OBJ from the singular tool that does exist, and actually seems to work on this model to a degree, so perhaps with some cross referencing it could be figured out, though honestly the code file probably makes more sense to someone who knows what they're doing, so I'll include it as well, it's how I managed to figure out most of this stuff. It's just a very bare bones converter and has issues with a lot of models, and is missing a lot of things I need. Here's what I did get though, a prop and a character. A character which I will also include for experimenting, and the OBJ that is missing 90% of their mesh. I did see that the material ID is in the hex numbers (it matches the hashed .texturefile, which I've given as well, and it seems both models use this texture file), and seems to be repeated a few times, probably pointing to different textures within the file. testfile.zip

Hmm ... Go to the Epics github site, clone the appropriate version of Unreal Engine, look for IPlatformFilePak (use VS or VSC to navigate), and you will find the solution. @iks: what's so funny?

Olá pessoal, estou trabalhando nesses formatos e progredindo com as malhas, alguns arquivos não funcionam corretamente, os uvs jxm têm submalhas e lods, postarei todo o progresso aqui

You could trick around with the .dat files produced by offzip, 001d7925.dat for example:

Thanks. Works on my side, using fmt_RuleOfRose(PS2)_i3d from Bigchillghost:

What do you mean by sample? If you mean the model I'm attempting to rip I have attached it below. Thank you for your willingness to help. jnfc.7z

In your c001x sample I found this, might be a track:

No, I mean samples of the actual files, not screenshots. Screenshots don't show much for anyone to check the files properly.

try this one, but it only works for cars

I managed to create a script that splits TRK files into RAW555 with conversion to RAW888. How to use: The attached package contains *.hexbm files in the folders. Based on these files, the script splits TRK files and then injects the modified files. TRK - game file with RGB555 graphics HEXBM - imhex bookmarks file. Contains offsets how to cut. TRK_to_RGB888_RAW.py -> Converting from TRK to RAW: - run the script and select the *.hexbm file, then the corresponding *.trk file. (for example: avlb0100.hexbm and avlb0100.trk) The script will create a folder with graphics. Editing graphics (after editing the file, overwrite it! The names and location of the graphics must remain in the same place!): These are RAW files, so you need to edit them with Photoshop, for example. The graphics files contain information about height and width. Set the rest as shown below. Save as Photoshop Raw. RGB888_RAW_to_TRK.py -> Converting from RAW to TRK: - select the trk file. Based on the trk file name, the script will automatically find the *.hexbm file and the folder with the graphics. TRK Cutter.zip

I've altered the conversion script and it's now filtering out faces with bad UVs without issue. "Bad" faces generally come in pairs but the first face of the pair doesn't always possess bad UVs, this results in the unintentional deletion of a face that was meant to exist along with the second face. This would make my approach to filtering a waste of time if not for the fact that the bad faces possessing good UVs seem to consistently share an edge with two other faces, something that can likewise be tested for and filtered out. After filtering faces both by their UVs and verts, most of the bad faces should be eliminated. New Armored Core Model Converter.7z

Oh, likewise. I think Imageheat is a pretty good tool. Even with my limited knowledge, I was able to make discoveries like this (2CV logo). Thanks to the tool you mentioned, I was able to achieve this other result. It definitely saves a lot of work! Thank you both so much!!!!!!!!

Ooooooh wow! Although I'm not very good with hexadecimal values, this tool was quite intuitive, even with my limited knowledge! Thank you so much, it's definitely the solution!😆

You can get some good results with ImageHeat https://github.com/bartlomiejduda/ImageHeat At offset 96 you can find fields like: 2 bytes (uint16) - image width 2 bytes (uint16) - image height 4 bytes (uint32) - palette offset

Done a few more optimisations to reduce the number of submeshes down to a reasonable level. Still work in progress:

The file format itself isn't too terribly complex it seems? There's seemingly no compression for those files either (at least in the demo). I've written a basic file extractor, it's probably far from perfect though.pac_extract.py

Holy crap thank you so much, for the longest I thought it was an archive file. I guess not 😄.

Hi, I'm nocturnalrhys (I lost my account) and I would like to share the documentation I'm doing about this game. I know some people don't like this game, but I do, and I'd like to take this .elf further. Currently, I've been documenting some features for 4 days in a row. Let's say I'm at 1.1% of the documentation, there are still more features to discover. But if anyone would like to contribute on GitHub, I've left a quick and easy documentation on how to use the source code I've left. PS: I don't really know if I've posted well https://github.com/NamelessDB/dbzsg_sc/tree/main

this https://sites.google.com/view/3d-model-archives/tools/akderebur-tools/valkyrie-profile-ak some tools part is missing.

I've just released a new version of ImageHeat 🙂 https://github.com/bartlomiejduda/ImageHeat/releases/tag/v0.25.2 Changelog: - Added support for new pixel formats: PVRTCI_2bpp_RGB, PVRTCI_2bpp_RGBA, PVRTCI_4bpp_RGB, PVRTCI_4bpp_RGBA, PVRTCII_2bpp, PVRTCII_4bpp, ETC1, BW1bpp, SharedExponentR9G9B9E5, RGBG8888, GRGB8888, ETC2_RGB, ETC2_RGBA, ETC2_RGB_A1, EAC_R11, EAC_RG11, ASTC_4x4, ASTC_5x4, ASTC_5x5, ASTC_6x5, ASTC_6x6, ASTC_8x5, ASTC_8x6, ASTC_8x8, ASTC_10x5, ASTC_10x6, ASTC_10x8, ASTC_10x10, ASTC_12x10, ASTC_12x12, ASTC_3x3x3, ASTC_4x3x3, ASTC_4x4x3, ASTC_4x4x4, ASTC_5x4x4, ASTC_5x5x4, ASTC_5x5x5, ASTC_6x5x5, ASTC_6x6x5, ASTC_6x6x6, BASISU_ETC1S, BASISU_UASTC, RGBM, RGBD - Added "Step-By-Page" shortcut - Added new Nintendo Switch unswizzle type - Added new PS4 unswizzle type - Added X360 and GameCube byteswap

Use the python script I've linked to before, or use someone else's splitter tool, if there is no problem, you can mark the previous reply as a solution, I think this reply has solved your problem Your file can be recognized

What command do i have to use to unpack all pkg files? Since the game has over 200 of them. Nevermind got it

I really don't understand this .mpk file. Is this file the same as the .pak pubg file that can be extracted and find a collection of other files inside?

okaayyyyy... turns out my previous copy of Wangan Midnight PS3 I downloaded from was a very bad copy which is why I got this error, so I downloaded another copy and now it finally works with TXRExtractor right now. At least I can finally open new topic for ripping Wangan Midnight PS3 model/textures.

accumulate rotations

After testing file parsing through regex expressions and finding it to be impractical, I've returned to my earlier approach and completed a finalized converter for Front Mission 4. The models are available here for those interested. FMO is next and will take far less time. FM4 Final Mass Converter.7z

OK, I set up a github repository to host the scripts, hopefully they'll help anyone who's curious about it! https://github.com/ScornMandark/G-SaviourExtract

The tool is now available. Download: https://github.com/Wildenhaus/IndexV2/releases How to use: