OK, gotcha :) But the offset which you say comes after seems to be too large. http://i39.tinypic.com/ztvgvp.png http://i40.tinypic.com/j63mnn.png Also, did you mean I should store the offset so I can return later to parse the MDL? Question,why not parse (read) it then, instead of storing the offset ...

So wait, "00000080" means next up is "user defined chunk (user binary)" where people can put what they want and Tecmo put the MDL block in it?

Sorry if I sound stupid. It's a bit confusing still.

d'oh. Nice start I guess. Well than I'll try the files inside it. they're already documented where? I created a virtual drive with daemon tools, but I can't read most of the files. "Invalid ms dos functions" when trying to copy most files. Maybe PSX ISO/BIN is not the same as your standard...

OK, this is as far as I could go for my first try: loop: byte {12} header uint {4} unknown uint {4} size of data following, usually power of two uint {4} size of data following, repeated byte {size} sometimes nulls, but not always byte {280} useful data which i don't get Need tips now.

Eh? I meant the doc is trolling me, lame joke, nvm. It is still confusing though. Why should I skip it? Its a MDL entry. Or maybe I don't get what you mean by this? just log the address of your cursor and the size, then jump past the binary using the size as the offset. then you continue your loop W...

Yeah that doc could use some work. Hes a troll now. Tristrips dont look incredibly difficult to generate. But altough each triangle has 3 edges, each one of them can have infinite amount of "neigbouring" edges. Should you just choose the one with the lowest angle? So it seems the MDL block...

EDIT: This thread has transformed from Tekken 3 to Tekken Hybrid, which has the Tekken 3 models, just hi-res, but still the same design. So skip all these pointless posts and start reading from the 4th post counting from the bottom of this page. --------------------------------------- ORIGINAL POST...

So some files are encrypted huh? And I was thinking AFSExplorer extracted corrupted files. Any ideas of the encryption? We know each file starts with an "XPR" so that could be a hint. Not an ordinary XOR though. The xprbreaker source uses mixed C/assembly code. It's too complicated for me....

@finale: so MDL chunk is always right after those? Cool, thanks.

I dont think any file is encrypted, are you sure the header is not just swapped with a hash?

I think only tristrips are used.

But it looks like you've gotten the vertex data out. All I did was: 1) get the 3rd integer from the file, which tells the offset of the 2nd part of the file, which contains vertex buffers and texture data. 2) moved the file cursor there 3) assuming that the map I was testing only used one type of v...

Yeah, wikitables are great for this, I just thought we could make it consistent with the other wiki pages.

Since I don't have files I can't verify whatever I'm writing is correct so I didn't write anything.

Check your pm inbox.

Anything's a start. I'm kind of stuck so I'm really lookign forward to any more info.

Sure thing. Here: http://wiki.xentax.com/index.php/Dead_Or_Alive_Ultimate You can use other pages, like DOA1 page as reference: http://wiki.xentax.com/index.php/Dead_Or_Alive Otherwise, you can always make a txt version and ask someone to port it for you (like me?). Maybe you can even post the simpl...

Uh, so 1) XPR files are basically split into two parts, 2) first part contains model and texture entries, second part contains vertex data and texture data, 3) second part's offset is the 3rd integer in the file, correct? Seems from browsing the sourcecodes that there are 10 types of vertex buffers....

If you guys will want me to add links to the first post, let me know in your posts.