We've gotten pretty far ignoring them so far, but eventually we'll need to add in .zaf_ readers so animations can animate with respect to a basepose. The zaf_ structure isn't cryptic like zaa_ and as far as I can tell the meaning of each sub chunk can be inferred from the name.
The head of this bdroid is sunken because it is being animated with the head transform of a human skeleton, instead of being offset by the head transform of the bdroid skel.
(Picture is from Blender import but the same problem applies to LibSWBF2/Phoenix...)
We've gotten pretty far ignoring them so far, but eventually we'll need to add in
.zaf_readers so animations can animate with respect to a basepose. Thezaf_structure isn't cryptic likezaa_and as far as I can tell the meaning of each sub chunk can be inferred from the name.The head of this bdroid is sunken because it is being animated with the head transform of a human skeleton, instead of being offset by the head transform of the
bdroidskel.(Picture is from Blender import but the same problem applies to LibSWBF2/Phoenix...)