oamio wrote: It is part of the file

A real mess. What's the point of this? The model attributes are described in FG01.json, and that would be pretty much enough for building the mesh.

Easy to extract:

Puterboy1 wrote:Sounds and sprites

Then I'm afraid I can't help you more.

Puterboy1 wrote:Now, about the .SPRI, .SOUN and .POSE files. Can they be converted?

Just make clear what you're actually looking for. Models? Textures? I won't waste any time on some aimless activities.

Here's a BMS script that will break the archives into smaller files named with a file ID. Supports with all the files in your samples pack except the .smk one.

Here a simple BMS script I wrote to unpack files from the samples you uploaded. No recognizable names to identify what these files are, so I just named them in the order they appear instead.
The data could be compressed or encrypted.

That's an invalid link.

Sorri , Link to sample files. https://mega.nz/#F!9ep10RDa!DJ-MxX41nLxlj_B7Pvcofg Archives are zstd compressed. Here is a BMS script for proper decompression. You'll need to update your QuickBMS to the lastest version. Still there're some files that cannot be decompressed correctly due to QuickBMS's...

Honestly I am really tired of asking you guys to upload sample files over and over again.

If you have a little spare time to write a tutorial that can be easy to understand for newbies that would be great and life saver for newbs like me. Unfortunately I don't think I'll have much free time in the following three weeks. Got a personal project to work with. But still I'll try to answer y...

OK, one after another: I have read the tutorial like multiple times but I'm still confuse Yeah, so was I at the first place. The only thing I even understood by that time was to look at the ascii part of a binary file in the hex editor. I want to learn it but the tools is kinda advance for new user ...

See? It's not that difficult at all.

But I believe it must be in the EXTRAS00.3DF. It's in there for sure. records.jpg It takes 372 bytes for each entry, with parent entry beginning at 0x4ECC. The first submesh start at 0xB980, while the face buffer comes right after the vertex chunk(FVFsize = 32). With an alignment of 0x10 bytes (ali...

Maybe i didn't understood what you were trying to explain to me ? i don't know... This is what I mean: To make it brief, I'll just skip those normals and UV stuffs. Say there's a file containing two submeshes where geo data are arranged like: submesh 1 some other data . . . submesh 2 then comes sub...

shakotay2 wrote:yeah, I see:

racing01.jpg

I tried tristrip on some meshes too but they look weird.

shakotay2 wrote:(uvs maybe at offset 24, but look a little bit weird)

I'm curious about what the rest two floats represent. Another UV?