XeNTaX

Battle of the Immortals its the 1st game i see of the New Mmorpg dont have the textures encrypted, i think the skel, animation and mesh are stored in the *.M4F files also each model have a cfg file, good luck to everyone.



File Formats:

Textures: *.DDS
Mesh, Skel and Ani: *M4F (maybe packed on this file)

Download to Test
http://www.megaupload.com/?d=FSYKO15P

Rimbros wrote:Battle of the Immortals its the 1st game i see of the New Mmorpg dont have the textures encrypted, i think the skel, animation and mesh are stored in the *.M4F files also each model have a cfg file, good luck to everyone.



File Formats:

Textures: *.DDS
Mesh, Skel and Ani: *M4F (maybe packed on this file)

Download to Test
http://www.megaupload.com/?d=FSYKO15P

a friend working in it, him have 85% program done, very soon are up

Will he release the source? Or file format?

finale00 wrote:Will he release the source? Or file format?

not source, only packer and unpacker tool.

Oh I see. That will be useful also.

CriticalError wrote:a friend working in it, him have 85% program done, very soon are up

No news?

Oh yeah, those M4F files look very parsable. Vertices and indices are clearly visible. Models look nice too. If they don't finish it I'll probably work one too as I finish up alibat.

The contents of this post was deleted because of possible forum rules violation.

Good job finale, i never see this format before *..m4f

nobody found a way to import m4f files into max,blender? I get unpacker and anyway is the same, sqp unpacker/packerget same files like En Client :S.

Guess I'll look at it now lol I've been busy trying to improve my program to support modding plugins as well as conversion plugins.

The header has an offset table with what appears to be counts of whatever section it is.

There are 14 dwords, which is basically 7 sections (a count and an offset for each).

The first pair of dwords are the numTex and the texOffset. Each texture name is 292 bytes long, and contains unicode characters (most likely chinese, GB2312 or something like that)

The third pair of dwords are the numMesh and meshOffset. Each mesh is defined sequentially, starting with the name, followed by a lot of dwords. The name is 80 bytes long, followed by FF FF FF FF, followed by 17 dwords, followed by 72 bytes of 00's. We can probably just say that's 18 dwords.

A quick search for vertex offsets leads me to believe that those 17 dwords are also counts and offsets, amongst other things.

finale00 wrote:Guess I'll look at it now lol I've been busy trying to improve my program to support modding plugins as well as conversion plugins.

The header has an offset table with what appears to be counts of whatever section it is.

There are 14 dwords, which is basically 7 sections (a count and an offset for each).

The first pair of dwords are the numTex and the texOffset. Each texture name is 292 bytes long, and contains unicode characters (most likely chinese, GB2312 or something like that)

The third pair of dwords are the numMesh and meshOffset. Each mesh is defined sequentially, starting with the name, followed by a lot of dwords. The name is 80 bytes long, followed by FF FF FF FF, followed by 17 dwords, followed by 72 bytes of 00's. We can probably just say that's 18 dwords.

A quick search for vertex offsets leads me to believe that those 17 dwords are also counts and offsets, amongst other things.

good interesting view, the truth is appreciated and sorry, there is not an easy job but you are one of the more experience here in the forum and ask why good simply because the game has very good models, good will wait for new news take care.

mesh stores vertCount, faceCount, normCount, uvCount, along with their offsets. Some other counts I am not sure of.

Looks like

finale00 wrote:mesh stores vertCount, faceCount, normCount, uvCount, along with their offsets. Some other counts I am not sure of.

Looks like

Code: Select all

struct Mesh {
   char_80 name
   dword_6 unk
   dword_2 vertCount, vertOffset
   dword_2 faceCount, faceOffset
   dword_2 normCount, normOffset
   dword_2 unk
   dword_2 unk
   dword_2 unk
   byte_72 padding
}

Didn't figure out the material section so I don't know which is the UV. There are then two additional counts/offsets that I am not sure of.

wow you rock man, gratz for new job still waiting i'm not pro for make it alone so thats the problem anyway thanks again for your support.

The boneCount and offset is the fourth pair of dwords in the header.
num3 is sometimes 0. Don't know.
Multiple meshes may have the same name. These need to be dealt with appropriately. They might be assigning materials per mesh rather than per face.