[Warhammer Dark Omen Forum]

Warhammer Dark Omen Forum | Modifications | 3D Scenery Models
Portrait meshes

[aqrit]

the heads.db file is partially described in the wiki
I don't know if it helps with reversing key/seq files
but here is the rest of it... (guess work as always)

Code:

struct HEAD //  sizeof 39 bytes (0x27)
{
0x00    unsigned char ID[2]; // Presumably controls which texture is used. e.g. MB=Morgab Bernhardt
0x02    unsigned char Flags; // see table 1
0x03    unsigned char KeySeq; // animation to use?
0x04    ?? always zero

0x05    unsigned char MouthWidth;  // These may not be unsigned. Not Tested.
0x06    unsigned char MouthHeight;
0x07    unsigned char MouthX;      // This is where to draw the moving parts on the main graphic
0x08    unsigned char MouthY;      // (replacing what is there already) for facial animation

0x09    unsigned char EyesWidth;  // These may not be unsigned. Not Tested.
0x0A    unsigned char EyesHeight;
0x0B    unsigned char EyesX;      // This is where to draw the moving parts on the main graphic
0x0C    unsigned char EyesY;      // (replacing what is there already) for facial animation
//
0x0D    char body_mesh_id // meshes/%d.m3d file
0x0E    signed char head_body_x; // seperate from center...padding?  does not include the neck.
0x0F    signed char head_body_y; // ...
0x10    signed char head_body_z;
//
0x11    char head_mesh_id // meshes/%d.m3d file
0x12    signed char HeadX;
0x13    signed char HeadY;
0x14    signed char HeadZ;

0x15    char head movement multiplier
0x16    char KeyID // for cut-scenes?

0x17   char NeckID;
0x18   signed char NeckX;
0x19   signed char NeckY;
0x1A   signed char NeckZ;

0x1B    char WeaponID; // 0x27 = bow, 0x33 = sword, etc.
0x1C	signed char WeaponX;
0x1D	signed char WeaponY;
0x1E	signed char WeaponZ;  

0x1F    char BackpackID;
0x20    signed char BackpackX;
0x21    signed char BackpackY;
0x22    signed char BackpackZ;

0x23    char HelmentID
0x24    signed char HelmentX;
0x25    signed char HelmentY;
0x26    signed char HelmentZ;
};

[dougie]

Really good work, I'll run some tests today myself using this

to better understand seq files,

thankyou 

[dougie]

Do you know if morphing animation is used Olly?

actually changing vertices I mean,

in any of the heads

[olly]

I don't sorry

[dougie]

Alright, thanks.

[aqrit]

correction:

byte offset 0x16 of the "HEAD" struct seems to control which KEY file is used during the "talkie" first cut-scene...

[dougie]

good I'm trying this out now

[dougie]

haha, Morgan Burnheart's flying about 

[dougie]

To anyone who's interested, I have found out a bit more about .key files,
with help from aqrit's db code

.KEY files appear(Pretty sure) to contain a list of keyframes, which are just a rotation for the
head and a rotation for the body.
each keyframe is a struct that is 12 bytes,

the first byte of a .key file is the number of keyframes in the file(e.g. 64 frames in 0.KEY)

//the second bytes for each rotation has more effect,
//e.g. something like 0-275 degrees while the first
//has a lesser 0-85, not sure exactly


For example:

Code:

struct BODYHEAD{
    //12 bytes
    //Body rotation
    0x00    signed char body_rotation_x1; // a rotation value around x axis
    0x01    signed char body_rotation_x2; // a greater rotation value around x axis
    0x02    signed char body_rotation_y1; // a rotation value around y axis
    0x03    signed char body_rotation_y2; // a greater rotation value around y axis
    0x04    signed char body_rotation_z1; // a rotation value around z axis
    0x05    signed char body_rotation_z2; // a greater rotation value around z axis
    //Head rotation
    0x06    signed char head_rotation_x1; // a rotation value around x axis
    0x07    signed char head_rotation_x2; // a greater rotation value around x axis
    0x08    signed char head_rotation_y1; // a rotation value around y axis
    0x09    signed char head_rotation_y2; // a greater rotation value around y axis
    0x0A    signed char head_rotation_z1; // a rotation value around z axis
    0x0B    signed char head_rotation_z2; // a greater rotation value around z axis
}

.SEQ files then choose the order of these keyframes to create different animations for
each of the characters, I'm working on figuring them out

doug

[olly]

very good!

[dougie]

I've worked out SEQ files  , here's a quick look at
what they do:

0.seq is used by all characters(in talkie scenes) and 126.seq,
and 0.key

126.seq is for mouth movement, these are the only three files needed for most cutscenes, could
be all. in-game characters use other files(like orcs on level 2)

SEQ files contain lists of keyframes,
a keyframe is a state a character(like Burnheartd) can be in.

The second byte in a SEQ file is the number of keyframes in the first
animation set, 0F in 0.SEQ

Code:

0F==15 frames,
each frame is 4 bytes so: 15*4 bytes in the first animation set:

40 0F 05 01 00 00 03 04 14 07 03 00 24 17 05 00 00 00 05 00 00 00 05 01 00 00 03 04 14 09 03 04 14 07 03 04 28 04 05 00 00 00 05 00 00 00 05 01 00 00 03 04 0F 00 02 00 00 00 08 00 00 00 0F 0A 02 00 00

Each animation set is defined by a number(length in frames) such as
0F or 0B, and there are something like
28 sets in 0.SEQ, this number occurs after each previous set

types are:
"zero five" entries:
05 01 00 00 - eyes texture open(01 for open)
05 00 00 00 - eyes closed(00 for closed)

"zero three" entries:
these are for head and body rotation
03 04 14 07 - tell character to rotate to key 7 in 0.key
03 04 XX 02 - rotate to key 2 in 0.key
03 04 XX 07 - XX is an acceleration value, greater values cause rotation to be slower

the second byte is almost always 04, or 00, I haven't worked out what it does.
If the third byte XX is 0(0 acceleration), no rotation will occur for that key frame.

"zero A" entries:
0A 02 00 00 - causes mouth to start talking, audio+animation, using 126.SEQ

"zero 6" entries:
these are for mouth
*they only occur in 126.SEQ file like I said, that file is for mouth
06 11 00 00 - oow mouth
06 06 01 00 00 - mouth state
06 02 00 00 - mouth state
06 10 00 00 - mouth state

"zero 8" entries:
These are found at the end of each animation set:
08 00 00 00
they seem to cause that particular set to loop if that set was started.

"zero 2" entries:
02 00 00 00
These are also found at the end of an animation set like 08, I haven't worked out what they do.

That's most of the different keyframe types.

Each animation set is defined by a number of frames in
that set, e.g. 0F for the first, 07 for the second, 0B 3rd if you
look at "0.SEQ":

Code:

40 0F 05 01 00 00 03 04 14 07 03 04 14 04 05 00 00 00 05 00 00 00 05 01 00 00 03 04 14 09 03 04 14 07 03 04 28 04 05 00 00 00 05 00 00 00 05 01 00 00 03 04 0F 00 02 00 00 00 08 00 00 00 07 0A 02 00 00 03 04 0A 05 03 00 0F 04 03 04 0A 01 03 04 0A 02 02 00 00 00 08 00 00 00 0B 0A 02 00 00 03 04 14 03 03 04 0F 04 05 00 00 00 05 01 00 00 03 04 14 05 03 04 14 06 03 04 0A 01 03 04 0A 04 02 00 00 00 08 00 00 00

 

[olly]

Excellent!

[dougie]

I'm doing an implementation of these heads in Unreal Engine, using 3ds max 

[devast3d]

Wow, that's great news! Keep us updated 

[dougie]

I'm going to start looking into modifying texture memory for the mouth movements