M2/.skel: Difference between revisions
Jump to navigation
Jump to search
m (→SKPD) |
m (→SKPD) |
||
| Line 13: | Line 13: | ||
} skl1; | } skl1; | ||
=SKPD= | =SKPD= | ||
uint8_t _0x00[8]; | 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). | 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). | ||
Revision as of 21:54, 21 September 2017
chunks are probably seq, bone, attach
SKA1
SKB1
SKL1
struct skl1chunk {
int a;
int lenname;
int c;
int d;
char name[lenname];
char e[size-16-b];
} skl1;
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).
SKS1
AFID
anim file ids, somehow duplicated from .m2
BFID
bone file ids, somehow duplicated from .m2