Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
It is all good and useful as well.
I will need it for my engine, but you go too fast.
I haven’t started programming this into my engine yet, because, to be honest, at times your notes are very confusing.
Anyhow what I was really asking is there more than one ambient light definition and if so is it based on the triangles in the walk mesh. I doubt they have any real light sources, though it is possible to do that on the PSX hardware (just slow).
Interesting stuff, the fact they used ambient lighting interests me. Perhaps they planed on using this to make the person look like they are in a light or dark place. In other words in shadow or outdoor light, or maybe that was there intention and they never got around to it as well. (Yet another than to add to the engine (Check ambient lighting for ambient lighting affects ;) ).
Emitted, Ambient, Diffuse, and Specular Light
Emitted light is the simplest - it originates from an object and is unaffected by any light sources.
The ambient component is the light from that source that's been scattered so much by the environment that its direction is impossible to determine - it seems to come from all directions. Backlighting in a room has a large ambient component, since most of the light that reaches your eye has bounced off many surfaces first. A spotlight outdoors has a tiny ambient component; most of the light travels in the same direction, and since you're outdoors, very little of the light reaches your eye after bouncing off other objects. When ambient light strikes a surface, it's scattered equally in all directions.
Diffuse light comes from one direction, so it's brighter if it comes squarely down on a surface than if it barely glances off the surface. Once it hits a surface, however, it's scattered equally in all directions, so it appears equally bright, no matter where the eye is located. Any light coming from a particular position or direction probably has a diffuse component.
Finally, specular light comes from a particular direction, and it tends to bounce off the surface in a preferred direction. A well-collimated laser beam bouncing off a high-quality mirror produces almost 100 percent specular reflection. Shiny metal or plastic has a high specular component, and chalk or carpet has almost none. You can think of specularity as shininess.
Although a light source delivers a single distribution of frequencies, the ambient, diffuse, and specular components might be different. For example, if you have a white light in a room with red walls, the scattered light tends to be red, although the light directly striking objects is white. OpenGL allows you to set the red, green, and blue values for each component of light independently.
The walk meshes seem a bit large for just one field location. Are they for a single or multiple field locations? There must be 'gateways' located within the mesh's bounds. What is the purpose of red versus green triangles. I don't recall that in the game.
I suppose my next task is finding the walk mesh in the PSX data. It appears that section 9 is located in the ????????.MIM files and the remaining sections are located in the ????????.DAT files. Do you know where the field models are kept in the game? Maybe section 6 is a redundant copy of the PSX field model information (????????.BSX files)? Just a possibility you might not have considered.
typedef struct {
S16 x;
S16 z;
S16 y;
} vector3S16;
typedef struct {
S16 left;
S16 bottom; // maybe top, I dont know/care Its nearly always centred
S16 right;
S16 top; // maybe bottom.
} range;
typedef {
char name_of-location[8];
U32 movement;
range picture;
U32 blank;
range range1;
U32 blank1[6];
} sec8header`
struct {
vector3S16 corner1;
vector3S16 corner1;
vector3S16 pos; // place where char will apear after transfer.
S16 destindex; // index in maplist
U32 unknownl; // 0x84848484 ot zero ?
}gateways;
struct {
vector3S16 corner1 ; // 6
vector3S16 corner2 ; // 6 12
U8 enterstate; // I have more or less faith into defaultstate, but not these two
U8 leavestate; // names are probably wrong
U8 defaultstate; //
U8 sound; // index zvuku, ale v jake databazi?
} triggers
struct {
S32 pos.x;
S32 pos.z;
S32 pos.y;
S32 visible; // is it visible? 01 true 00 false
} triangles;
typedef struct {
S16 blank; // always zero
S16 numchar; // number of characters
S16 size; // same as size
object charinfo[numchar];
} sec3;
typedef struct {
S16 charnamelen;
chars charname[charnamelen];
S16 blank; // 0 end of string?
char skeletname[12]; // AAAA.HRC1024 or AAA.HRC512\0 - just 12 chars, no ending zero
U16 numani; // number of animation or whatever it is. see ani[]
light_s light[3];
U8 ambientred;
U8 ambientgreen;
U8 ambientblue;
animation ani[numani];
} object;
typedef struct {
U8 red; // composition of light for spotlight
U8 green;
U8 blue;
vector3S16 pos; // position. I walkmesh [-x,-y,z]
} light_s;
pos.x = -x;
pos.y = -y;
pos.z = z;
typedef struct {
S16 lenght; // how long will be anme of next animation
char name[lenght]; // ACFE.aki | ADCC.tor | ????.yos // . == 2E
S16 unknown; // often 0x0001 - maybe end of string?
} animation
typedef struct {
S16 x;
S16 z;
S16 y;
}vector3S16
typedef struct {
S16 left;
S16 bottom; // maybe top, I dont know/care Its nearly always centred
S16 right;
S16 top; // maybe bottom.
} range;
S32 offs1;
S32 offs2;
S32 offs3;
S32 offsEOF; // offset to the end of file
now comes data from section one, it seems like slight fibonachi sequence with few irregularites.
typedef struct {
S16 blank; // is it always zero?
S16 numchar; // number of characters
S16 offs004;
object charinfo[numchar];
} sec3;
typedef struct {
S16 charnamelen;
chars charname[charnamelen];
S16 blank; // 0 end of string?
char skeletname[4]; // AAAA
U8 separator1; // 2E
char skelet_suffix[] // "HRC512\0" sometimes "HRC1024\0"
U16 numani; // number of animation or whatever it is. see ani[]
S16 unknown1[6]; // [1] some coeficient for diffusion of light
vector3S16 source; // vector for light position, size is 4096
S16 unknown[6]; // firs few are probably coefficients
// [x] --- unknown[x]
// [0] blue
// [1] ,[2],[3] dont know anything
//
//
// [4] red
// [5] green
animation ani[numani];
} object;
typedef struct {
S16 lenght; // how long will be anme of next animation
char name[lenght]; // ACFE.aki | ADCC.tor | ????.yos // . == 2E
S16 unknown; // often 0x0001 - maybe end of string?
} animation
typedef struct {
S16 x;
S16 z;
S16 y;
} vector3S16;
typedef struct {
vector3S16 vx;
vector3S16 vy;
vector3S16 vz;
S16 repeat;
S16 ox;
S16 oy;
S16 oz;
S32 blank;
S16 size;
} camera
vy.x = -vy.x;
vy.y = -vy.y;
vy.z = -vy.z;
oy = -oy;
vx.x /=4096.0; // of course, you have to change it (read values in S16 and vectors have to be floats)
// a littlse since here is vx.x S16 and it has to be float.
......
tx = -(ox*vx.x + oy*vy.x + oz*vz.x);
ty = -(ox*vx.y + oy*vy.y + oz*vz.y);
tz = -(ox*vx.z + oy*vy.z + oz*vz.z);
I think we've been trying to find that darned walkmesh for the last four years! I would *REALLY* like for that to be found, along with the camera location, camera range, and floor triggers. That's really the only thing stopping us from having a halfway decent field "player"
Check those out and see if I am right. The PC version of the game is SO much easier to hack (Sniff).
You owe Kero a PS1 ;)
I wish you well with your school by the way.
Cyb
Sector pool
--------------
typedef struct {
short x,z,y,res; // short is 2 bytes long integer
} vertex_3s; // 3 short
It seems that res and z are very often same, but not always.I dont know why.
WOW, I'm pleased as pickles.
I only ask you document this. It doesn't have to be pretty, I can do the text formatting. I would like to put it into Gears when I have the time.
When documenting please remeber to tell what version (PC/PSX) you are getting this from and what steps to take to extract the information. (The data is useless without context)
I've been watching the other threads and the progress on the animation front. Lots is getting tossed back and forth, but I'm getting lost with much of the math. (I'm innumerate)
I'm going to be super-busy when my current class ends and my next one starts.
I think we've been trying to find that darned walkmesh for the last four years! I would *REALLY* like for that to be found, along with the camera location, camera range, and floor triggers. That's really the only thing stopping us from having a halfway decent field "player"
