Parse the file and then write out the contents in MQO format. Here's a Sanae plugin that I use. that is something that really interests me, I been trying to add a cubemap to the files so they can have a shiny effect. If you notice the taxi is glossy but the MS are matte. I was trying to see if I cou...

I noticed the phrase "I am trying to ..." come up fairly often in many request threads, and was wondering just how much "trying" actually occurred before you decided to create a request. For me, if it's a model or an archive I probably spend 5 minutes and then conclude I have no ...

Spent about 20 mins comparing files and writing down some patterns. mst files specify stuff to load and other properties. From this we can conclude that cmi files contain models cai files contain animations. For the cmi file, the header and bone structs are parsed fine. The material section and the ...

Viewing UNK files is different from extracting files from an SPK.

Here is the outline of the KCP index file. Each entry defines the number of subfolders and files, and then specifies them in that order. There are still unknowns, but fortunately not too many. Data is most likely compressed. The problem with this script right now is that it just prints out all of th...

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

Some of the files start with 02. The majority start with 04. There is some slight differences there.
Other than that, the format is pretty much the same.

A bunch of script data, then a bunch of references to some shader files, and then some materials, and then what appears to be bones.

Everything after makes no sense to me. I can't find any pattern without brute forcing it (ie: keep reading bytes until you see a huge number that marks the end of the chunk).

This applies to "script data" chunks, "shader" chunks, and whatever else after.

Yes, you can store each mesh separately and then choose to output them as separate files. Just group the corresponding vertex chunks with the face chunks and you're all set. Some of the images I included the mesh list so you can see object[0], object[1], ... Those are all separate meshes. Once the f...

Ya, I think noesis has that as one of the options. Scroll through the list.
I don't know if that's the problem though.

Well, I implemented the hack-ish method I described and processed the Magellan model...maybe correctly I don't know. http://i.imgur.com/K4EuG.jpg But it didn't work for the gundam you sent. The keys don't match up as I had previously claimed, so perhaps that's not what it should be based on. EDIT: j...

Probably can't do much about it without modifying the GMO parser code.
Someone else had the same problem with GMO files from another game. I think he said the bones were not being done correctly.

Found another pattern, and I can use it to parse the model correctly, but it's sort of hack-ish. Basically, I mentioned there was some seemingly random number at the end of each chunk. Instead of interpreting it as a long, I interpreted as two shorts, and this was the result: 13 vert chunks, 9 face ...

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

oh lol I thought they were referring to some model viewer you wrote for the det files.

That's really detailed. Can you animate it as well?

Anyways I'm looking at the client and there are some DET files for "map" objects. Any clue on the compress there?