M2/.skel: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (→SKL1) |
||
| Line 3: | Line 3: | ||
=SKL1= | =SKL1= | ||
struct skl1chunk { | struct skl1chunk { | ||
uint32_t a; | |||
uint32_t lenname; | |||
uint32_t c; | |||
uint32_t d; | |||
char name[lenname]; | char name[lenname]; | ||
uint8_t e[header.size-16-lenname]; | |||
} skl1; | } skl1; | ||
=SKA1= | =SKA1= | ||
=SKB1= | =SKB1= | ||
Revision as of 23:08, 21 September 2017
chunks are probably seq, bone, attach
SKL1
struct skl1chunk {
uint32_t a;
uint32_t lenname;
uint32_t c;
uint32_t d;
char name[lenname];
uint8_t e[header.size-16-lenname];
} skl1;
SKA1
SKB1
SKS1
SKPD
struct {
uint8_t _0x00[8];
uint32_t parent_skel_file_id;
uint8_t _0x0c[4];
} skeleton_parent_data;
The parent skeleton file data id is used for de-duplication. E.g. lightforgeddraeneimale references draeneimale_hd. lightforgeddraeneimale does not have any M2/.anim files, but uses those of draeneimale_hd via parent-link (does not even have an AFID chunk).
AFID
anim file ids, somehow duplicated from .m2
BFID
bone file ids, somehow duplicated from .m2