CINF (File Format): Difference between revisions

Revision as of 23:23, 13 April 2016

The CINF format is for character layouts (i.e. skeletons/armatures). Character layouts are associated with models and skins through ANCS files.

To do:
MP2/3/DKCR differences

Type	Count	Name	Notes
u32	1	Bone Count
Bone	Bone Count	Bone Table
u32	1	Build Order ID Count
u32	Build Order ID Count	Build Order ID Table	The first element of the ID table is the root bone, followed by the rest of the bone IDs in reverse numerical order. This table is enumerated in-order to construct a singly-linked hierarchy of bones using child/sibling convention.
u32	1	Bone Name Count
Bone Name	Bone Name Count	Bone Name Table
End of file

Offset	Type	Count	Name	Notes
0x0	u32	1	Bone ID
0x4	u32	1	Parent Bone ID
0x8	float	3	Position	The position is in the armature's local space, not in the parent's bone space.
0x14	u32	1	Linked Bone Count
0x18	u32	Linked Bone Count	Linked Bone ID Array	This array includes both the parent bone ID as well as all children.
End of bone

Type	Count	Name
string	1	Bone Name
u32	1	Bone ID
End of bone name

@@ Line 1: / Line 1: @@
-The '''CINF format''' is for skeletons. Skeletons are associated with models and skins through [[ANCS (File Format)|ANCS]] files.
+The '''CINF format''' is for character layouts (i.e. skeletons/armatures).
+Character layouts are associated with models and skins through [[ANCS (File Format)|ANCS]] files.
 {{todo|MP2/3/DKCR differences}}
@@ Line 69: / Line 70: @@
 | 3
 | '''Position'''
-| The position is in the skeleton's local space, not in the parent's bone space.
+| The position is in the armature's local space, not in the parent's bone space.
 |-
 | 0x14