-
Notifications
You must be signed in to change notification settings - Fork 0
bone_child
{
"default type": "uint4",
"suffixes amount": 0,
"max suffix values": { },
"counting group": "per bone child",
"available since": "v2.3.0"
}
I didn't bother to implement this one since you can retrieve bone hierarchy with bone_parent
, apart from that: more often you will be using m_bone_child
since in most files skeletons are associated with meshes.
trying to compile with this field in .format
file will yield an error
JSON format structure since v2.2.0
-
bone_id
since v2.1.0 -
bone_weight
since v2.1.0 -
off_matr
,off_matrix
,offset_matr
,offset_matrix
since v2.0.0 -
bone_parent
since v2.3.0 -
bone_child
since v2.3.0 -
m_off_matr
,m_off_matrix
,m_offset_matr
,m_offset_matrix
since v2.2.0 -
m_bone_parent
since v2.3.0 -
m_bone_child
since v2.3.0 -
position_key
since v2.0.0 -
rotation_key
since v2.0.0 -
scale_key
since v2.0.0 -
position_time
,position_timestamp
,position_key_time
,position_key_timestamp
since v2.0.0 -
rotation_time
,rotation_timestamp
,rotation_key_time
,rotation_key_timestamp
since v2.0.0 -
scale_time
,scale_timestamp
,scale_key_time
,scale_key_timestamp
since v2.0.0 -
duration
since v2.0.0 -
ticks_per_second
since v2.0.0
key-words
: