models

Path	Type	FixedSize	ArrayValueSize	Interleaved	Name
/root/0/x/0/0	s_t2fsDataModelInfo	32			info
/root/0/x/0/1					model_0_1
/root/0/x/1/0/x	t2fsArray < s_t2fsDataVertex >		20	Yes	vertexBuffer
/root/0/x/1/1/x/0	t2fsArray		4		model_1_1_x_0
/root/0/x/1/1/x/1	s_t2fsDataBone	112			bone
/root/0/x/1/2/x/x/0	s_t2fsDataMaterial	24			material
/root/0/x/1/2/x/x/1					indices
/root/0/x/1/3/x	t2fsArray < s_t2fsDataHotpoint >		20		hotpointsArray
/root/0/x/1/4/x		8			model_1_4_x
/root/0/x/1/5					model_1_5
/root/0/x/2/x/0	t2fsArray		2		model_2_x_0
/root/0/x/2/x/1	t2fsArray < s_t2fsDataAnimationBoneIndices >		4		model_2_x_1
/root/0/x/2/x/2	t2fsArray < s_t2fsDataBoneOrientation >		20		boneOrientations
/root/0/x/2/x/3/0		16			model_2_x_3_0
/root/0/x/2/x/3/1	t2fsArray		12		model_2_x_3_1
/root/0/x/2/x/4	t2fsArray		28		model_2_x_4
/root/0/x/2/x/5/0	s_t2fsDataAnimationHeader	24			model_2_x_5_0
/root/0/x/2/x/5/1					model_2_x_5_1
/root/0/x/2/x/5/2					model_2_x_5_2
/root/0/x/3	t2fsArray		28		model_3

/root/0

• child-type: variable
• childeren: /root/0/x model

/root/0/x

• child-type: fixed
• childeren:
  • /root/0/x/0 model_0
  • /root/0/x/1 model_1
  • /root/0/x/2 poses
  • /root/0/x/3 model_3

/root/0/x/0

• child-type: fixed
• childeren:
  • /root/0/x/0/0 info
  • /root/0/x/0/1 model_0_1

/root/0/x/0/0

• child-type: data
• data-type: s_t2fsDataModelInfo
• data-size: 32

/root/0/x/0/1

• child-type: data

/root/0/x/1

• child-type: fixed
• childeren:
  • /root/0/x/1/0 meshes
  • /root/0/x/1/1 bones
  • /root/0/x/1/2 surfaces
  • /root/0/x/1/3 hotpoints
  • /root/0/x/1/4 model_1_4
  • /root/0/x/1/5 model_1_5

/root/0/x/1/0

• child-type: variable
• childeren: /root/0/x/1/0/x vertexBuffer

/root/0/x/1/0/x

• child-type: data
• data-type: array
• data-size: varies
• array-value-size: 20 bytes

/root/0/x/1/1

• child-type: variable

this is different then seeds, flipped with model_1_3 ?

• childeren: /root/0/x/1/1/x model_1_1_x

/root/0/x/1/1/x

• child-type: fixed
• childeren:
  • /root/0/x/1/1/x/0 model_1_1_x_0
  • /root/0/x/1/1/x/1 bone

/root/0/x/1/1/x/0

• child-type: data
• data-type: array
• data-size: varies
• array-value-size: 4 bytes

/root/0/x/1/1/x/1

• child-type: data
• data-type: s_t2fsDataBone
• data-size: 112

/root/0/x/1/2

• child-type: variable
• childeren: /root/0/x/1/2/x meshId

/root/0/x/1/2/x

• child-type: variable
• childeren: /root/0/x/1/2/x/x surface

/root/0/x/1/2/x/x

• child-type: fixed
• childeren:
  • /root/0/x/1/2/x/x/0 material
  • /root/0/x/1/2/x/x/1 indices

/root/0/x/1/2/x/x/0

• child-type: data
• data-type: s_t2fsDataMaterial
• data-size: 24

/root/0/x/1/2/x/x/1

• child-type: data

/root/0/x/1/3

• child-type: variable

this is different then seeds

• childeren: /root/0/x/1/3/x hotpointsArray

/root/0/x/1/3/x

• child-type: data
• data-type: array
• data-size: varies
• array-value-size: 20 bytes

only 3 entries have this set.., models 138, 174 and 268

/root/0/x/1/4

• child-type: variable
• childeren: /root/0/x/1/4/x model_1_4_x

/root/0/x/1/4/x

• child-type: data
• data-type: unknown
• data-size: 8

all set to 0000 0000 0800 0000, TODO does this need to go deeper?

/root/0/x/1/5

• child-type: data

this is different then seeds

• data-type: unknown
• data-size: varies

most set to 0000 0000 0800 0000, size may vary when otherwise (very few), TODO does this need to go deeper?

/root/0/x/2

• child-type: variable
• childeren: /root/0/x/2/x pose

/root/0/x/2/x

• child-type: fixed
• childeren:
  • /root/0/x/2/x/0 model_2_x_0
  • /root/0/x/2/x/1 model_2_x_1
  • /root/0/x/2/x/2 boneOrientations
  • /root/0/x/2/x/3 model_2_x_3
  • /root/0/x/2/x/4 model_2_x_4
  • /root/0/x/2/x/5 model_2_x_5

/root/0/x/2/x/0

• child-type: data
• data-type: array
• data-size: varies
• array-value-size: 2 bytes

almost always has count, but most times all values are just 0x0000, counts differ.

/root/0/x/2/x/1

• child-type: data
• data-type: array
• data-size: varies
• array-value-size: 4 bytes

count is the same as there are bones, these appear to be two 16bit values, possible signed. Maybe rotation count and position count? These are either set to 0xFFFF or seem to count up starting from 0.

/root/0/x/2/x/2

• child-type: data
• data-type: array
• data-size: varies
• array-value-size: 20 bytes

/root/0/x/2/x/3

• child-type: fixed
• childeren:
  • /root/0/x/2/x/3/0 model_2_x_3_0
  • /root/0/x/2/x/3/1 model_2_x_3_1

/root/0/x/2/x/3/0

• child-type: data
• data-type: unknown
• data-size: 16

are these timings?

/root/0/x/2/x/3/1

• child-type: data
• data-type: array
• data-size: varies
• array-value-size: 12 bytes

only 2 entries found, models 124 and 156

/root/0/x/2/x/4

• child-type: data
• data-type: array
• data-size: varies
• array-value-size: 28 bytes

/root/0/x/2/x/5

• child-type: fixed
• childeren:
  • /root/0/x/2/x/5/0 model_2_x_5_0
  • /root/0/x/2/x/5/1 model_2_x_5_1
  • /root/0/x/2/x/5/2 model_2_x_5_2

/root/0/x/2/x/5/0

• child-type: data
• data-type: s_t2fsDataAnimationHeader
• data-size: 24

on seeds this is 32 bytes in size, looks like same sort of data

/root/0/x/2/x/5/1

• child-type: data

based on data sizes and some repeating values this is likely bone rotation data, however I fail to make sense of the data, it looks compressed or maybe some sort of other bit stream.

/root/0/x/2/x/5/2

• child-type: data

based on data sizes and some repeating values this is likely bone position data, however I fail to make sense of the data, it looks compressed or maybe some sort of other bit stream.

/root/0/x/3

• child-type: data
• data-type: array
• data-size: varies
• array-value-size: 28 bytes

Only 11 models have this set: 227, 228, 444, 510, 804, 805, 806, 807, 808, 812 and 952