haven't read your reply yet.

But here are the docs reuploaded:

Doax Xpr File:
http://www.scribd.com/doc/76850656/Doax ... k1d1ey8oii

DOAU Xpr Cat Format
http://www.scribd.com/doc/76850743/DOAU ... 5ytxoo50rm

ok, in b0ny's notes I hope you are talking about the DOAX html doc you posted a link to. The sourcecode of the DOA3 viewer shows that there are some differences in the struct data and struct lenghts which will make the DOAX and DOA3 XPR's incampatible. the last dword is not padding, its another cou...

The material struct from the doc: typedef struct _materialblock { // 144 bytes dword header; dword size; dword pad02; dword number; float mat_color0[4]; // diffuse color ? float mat_color1[4]; float mat_color2[4]; float mat_color3[4]; float mat_color5[4]; float power; // specular power ?? dword pad2...

I'm sorry if I sounded like a think highly of myself. I never wanted you to feel belittled, I just meant you know alot, but don't share your knowledge very well and if you did more people could help. I share my knowledge in game programming because I think it might help you to understand what some t...

no the positions in the image are multiplied by the 4th float. huh? I believe it is a vector of some sort, that is used to manipulate the 1st three floats you can see here the result of that; I think you'll agree that you didn't explain very well what you were doing here. You should try to explain ...

I might have missed somethings, but in your image if you really used the 3 float values from xpr to position the meshes, then: The head is at almost (0,0,0). Usually the feet are at (0,0,0) and more rarely the middle of the body. So it's possible that the positions are not absolute, but relative. Th...

In that image you posted, do you position the meshes according to the 3 float values from the file? If so, it seems clear to me that the positions are not absolute by looking at the position of the head.

OK. I don't get why we call it radius though. What radius?

I don't want to sound like I doubt your knowledge, but why are you so sure? Has the collision detection code been decompiled and someone could make sense of it? So do you know what "radius" is then? I've been into game programming for the past few years and I've never heard of a "radi...

I have another idea what the "radius" float in the xpr objects might be. Since this is a fighting game, it could also be a collision sphere. One way to find out would be to have really small radiuses or really big. If it's eally big, then either hitting an enemy won't do anything (because ...

FFFFFFFFUUU I can't believe I didn't notice that. Anyway, I wish I would know C++ sometimes. The 4th float value is named "Object radius". I'm not sure what radius its talking about. As far as I know radiuses are for spheres. And the only spheres a 3d model uses in games is the bounding s...

Well yeah, hacking and programming are different things and require different set of skills, even though they have some things in common which both should know. I for example, know how 3d data is stored internally in modern games and can generate static or animated models if I know how the data is s...

I posted what I know just to give others an idea of my own thoughts. I know, I just mean you could repost what you "think" you know. Right now some things are missing. Seems like you forgot to post some info which you forgot only you know, and there are places which are just confusing (th...

Well good luck to you. However, I think you are terrible at writing file specs :D jk, it's probably just me. However, this is not the first file specification I'm reading, so If you'll have time please consider rewriting the file specs like the BRRES file specs from the smash bros wiki. it's really ...

Sorry man, but your wording confuses me at some places, I'll try to reread it again. As for the 4th float value... if you are really sure it's really a float used for transforms, then I've only came across rotations stored in 3 floats, as radians or heading, pitch and roll (0:360) values. if it's a ...