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