https://okami.speedruns.wiki/api.php?action=feedcontributions&feedformat=atom&user=AkitoŌkami Speedrun Wiki - User contributions [en]2026-05-06T00:24:17ZUser contributionsMediaWiki 1.36.2https://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1847Motion (.MOT) File Format2025-09-07T22:42:02Z<p>Akito: /* (Example): */</p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
<br />
Every curve is computed using the '''Cubic Hermite interpolation formula.''' That means every curve is treated as a Hermite Curve. <br />
:[[File:Formula.png|Formula of the Cubic Hermite Interpolation, used in curves.]]<br />
<br />
<br />
'''Note:''' This formula's image was taken from the [https://en.wikipedia.org/wiki/Cubic_Hermite_spline ''Cubic Hermite spline Wiki''.] <br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the ''Property Family'' of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Quantized-Precision Curve || Position X<br />
|-<br />
| 51 || Quantized-Precision Curve || Position Y<br />
|-<br />
| 52 || Quantized-Precision Curve || Position Z<br />
|-<br />
| 53 || Quantized-Precision Curve || Rotation X<br />
|-<br />
| 54 || Quantized-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Quantized-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Quantized-Precision Curve || Scale X<br />
|-<br />
| 57 || Quantized-Precision Curve || Scale Y<br />
|-<br />
| 58 || Quantized-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, curves will be readen diferently.<br />
== Single Pose ==<br />
This ''Property Family'' is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose ''Property Family''.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose ''Property Family''.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
== Quantized Curve ==<br />
This ''Property Family'' Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the bone index 0''', being set on a '''Quantized Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes header are located'''.<br />
|}<br />
<br />
=== Quantized Curve Keyframe Header (12 bytes length)===<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (m1)<br />
|}<br />
This is the only ''Property Family'' that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After reading the keyframes header, what follows up are the keyframes in which the actual keyframes are stored in.<br />
<br />
=== Quantized Keyframes (4 bytes length)===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint8_t</code> || 1 || Keyframe time '''(Relative to the time of the last keyframe).'''<br />
|-<br />
| 0x01 || <code>uint8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>uint8_t</code> || 1 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x03 || <code>uint8_t</code> || 1 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the '''output value is blending from the minimum to the maximum value, based on the value of Delta.'''<br />
<br />
So, that would leave us with...<br />
* P_value = '''minimum_value + maximum_value * delta_value'''<br />
* M0_value = '''minimum_m0 + maximum_m0 * delta_m0'''<br />
* M1_value = '''minimum_m1 + maximum_m1 * delta_m1'''<br />
<br />
After computing the full values, The curve is to be computed using the Hermite Cubic Interpolation.<br />
<br />
<br />
<br />
== Quantized-Precision Curve ==<br />
For this ''Property Family'', the process is almost the exact same. However, there are some changes.<br />
First of, This is a more precise version of the Quantized curves. Therefore, the values are doubled up.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 50 || This field is telling that '''the curve animates the X Position of the bone index 0''', being set on a '''Quantized-Precision Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes header are located'''.<br />
|}<br />
<br />
===(Keyframes header):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float32_t</code> || 4 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float32_t</code> || 4 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float32_t</code> || 4 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float32_t</code> || 4 || Maximum value of the end tangent (m1)<br />
|}<br />
You can notice that, since the values were doubled up, The use of the custom float16_t were completely removed, since now the file can use float32's instead, which are more precise and stable in comparision. This results on the size of the keyframe header to be extended to '''24 bytes each.'''<br />
===(Keyframe):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint16_t</code> || 2 || Keyframe time '''(Absolute)'''.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Delta value of the Keyframe.<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x06 || <code>uint16_t</code> || 2 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
Aside from the keyframe time being '''Aboslute''', the rest of the process remains the exact same.<br />
<br />
<br />
<br />
== Full-Precision Curve ==<br />
This is the most straightforward ''Property Family''. However, the most expensive (in storaging terms).<br />
Different from the Quantized types, this one is not dependent of a ''Keyframe Header.''<br />
Instead, it tells the values right away, Rendering this ''Property Family'' the easiest to compute (considering this is not a single pose), the one with the most accurate movements, but the most expensive to store in storage terms.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 80 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Full-Precision Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes are located'''.<br />
|}<br />
===(Keyframes):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint16_t</code> || 2 || Keyframe time '''(Absolute)'''.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Padding, used to align the file, It has no use.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Keyframe Value<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Value of the keyframe's end tangent. (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
After that, the values can be used straight into the cubic interpolation formula.<br />
<br />
===Final Notes:===<br />
The space in which the movement of bones takes in also depends of the ''Property Family'' the curve is set in. For instance, if a bone's rest position's property (let's say it's 125.14 for X) is animated on a quantized curve, Since this is a big value, movement information will be lost due to the nature of the quantized ''Property Family'', especially when not used in a ''Quantized-Precision Curve''. Because of that, '''The bone's movements are relative to the bone's parent's pose on quantized types.''' For full precision however, since quantization is not needed, '''the property values are absolute.'''</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1846Motion (.MOT) File Format2025-09-07T22:41:24Z<p>Akito: /* (Example): */</p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
<br />
Every curve is computed using the '''Cubic Hermite interpolation formula.''' That means every curve is treated as a Hermite Curve. <br />
:[[File:Formula.png|Formula of the Cubic Hermite Interpolation, used in curves.]]<br />
<br />
<br />
'''Note:''' This formula's image was taken from the [https://en.wikipedia.org/wiki/Cubic_Hermite_spline ''Cubic Hermite spline Wiki''.] <br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the ''Property Family'' of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Quantized-Precision Curve || Position X<br />
|-<br />
| 51 || Quantized-Precision Curve || Position Y<br />
|-<br />
| 52 || Quantized-Precision Curve || Position Z<br />
|-<br />
| 53 || Quantized-Precision Curve || Rotation X<br />
|-<br />
| 54 || Quantized-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Quantized-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Quantized-Precision Curve || Scale X<br />
|-<br />
| 57 || Quantized-Precision Curve || Scale Y<br />
|-<br />
| 58 || Quantized-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, curves will be readen diferently.<br />
== Single Pose ==<br />
This ''Property Family'' is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose ''Property Family''.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose ''Property Family''.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
== Quantized Curve ==<br />
This ''Property Family'' Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the bone index 0''', being set on a '''Quantized Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes header are located'''.<br />
|}<br />
<br />
=== Quantized Curve Keyframe Header (12 bytes length)===<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (m1)<br />
|}<br />
This is the only ''Property Family'' that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After reading the keyframes header, what follows up are the keyframes in which the actual keyframes are stored in.<br />
<br />
=== Quantized Keyframes (4 bytes length)===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint8_t</code> || 1 || Keyframe time '''(Relative to the time of the last keyframe).'''<br />
|-<br />
| 0x01 || <code>uint8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>uint8_t</code> || 1 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x03 || <code>uint8_t</code> || 1 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the '''output value is blending from the minimum to the maximum value, based on the value of Delta.'''<br />
<br />
So, that would leave us with...<br />
* P_value = '''minimum_value + maximum_value * delta_value'''<br />
* M0_value = '''minimum_m0 + maximum_m0 * delta_m0'''<br />
* M1_value = '''minimum_m1 + maximum_m1 * delta_m1'''<br />
<br />
After computing the full values, The curve is to be computed using the Hermite Cubic Interpolation.<br />
<br />
<br />
<br />
== Quantized-Precision Curve ==<br />
For this ''Property Family'', the process is almost the exact same. However, there are some changes.<br />
First of, This is a more precise version of the Quantized curves. Therefore, the values are doubled up.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 50 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized-Precision Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes header are located'''.<br />
|}<br />
===(Keyframes header):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float32_t</code> || 4 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float32_t</code> || 4 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float32_t</code> || 4 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float32_t</code> || 4 || Maximum value of the end tangent (m1)<br />
|}<br />
You can notice that, since the values were doubled up, The use of the custom float16_t were completely removed, since now the file can use float32's instead, which are more precise and stable in comparision. This results on the size of the keyframe header to be extended to '''24 bytes each.'''<br />
===(Keyframe):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint16_t</code> || 2 || Keyframe time '''(Absolute)'''.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Delta value of the Keyframe.<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x06 || <code>uint16_t</code> || 2 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
Aside from the keyframe time being '''Aboslute''', the rest of the process remains the exact same.<br />
<br />
<br />
<br />
== Full-Precision Curve ==<br />
This is the most straightforward ''Property Family''. However, the most expensive (in storaging terms).<br />
Different from the Quantized types, this one is not dependent of a ''Keyframe Header.''<br />
Instead, it tells the values right away, Rendering this ''Property Family'' the easiest to compute (considering this is not a single pose), the one with the most accurate movements, but the most expensive to store in storage terms.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 80 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Full-Precision Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes are located'''.<br />
|}<br />
===(Keyframes):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint16_t</code> || 2 || Keyframe time '''(Absolute)'''.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Padding, used to align the file, It has no use.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Keyframe Value<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Value of the keyframe's end tangent. (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
After that, the values can be used straight into the cubic interpolation formula.<br />
<br />
===Final Notes:===<br />
The space in which the movement of bones takes in also depends of the ''Property Family'' the curve is set in. For instance, if a bone's rest position's property (let's say it's 125.14 for X) is animated on a quantized curve, Since this is a big value, movement information will be lost due to the nature of the quantized ''Property Family'', especially when not used in a ''Quantized-Precision Curve''. Because of that, '''The bone's movements are relative to the bone's parent's pose on quantized types.''' For full precision however, since quantization is not needed, '''the property values are absolute.'''</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1845Motion (.MOT) File Format2025-09-07T20:57:42Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
<br />
Every curve is computed using the '''Cubic Hermite interpolation formula.''' That means every curve is treated as a Hermite Curve. <br />
:[[File:Formula.png|Formula of the Cubic Hermite Interpolation, used in curves.]]<br />
<br />
<br />
'''Note:''' This formula's image was taken from the [https://en.wikipedia.org/wiki/Cubic_Hermite_spline ''Cubic Hermite spline Wiki''.] <br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the ''Property Family'' of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Quantized-Precision Curve || Position X<br />
|-<br />
| 51 || Quantized-Precision Curve || Position Y<br />
|-<br />
| 52 || Quantized-Precision Curve || Position Z<br />
|-<br />
| 53 || Quantized-Precision Curve || Rotation X<br />
|-<br />
| 54 || Quantized-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Quantized-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Quantized-Precision Curve || Scale X<br />
|-<br />
| 57 || Quantized-Precision Curve || Scale Y<br />
|-<br />
| 58 || Quantized-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, curves will be readen diferently.<br />
== Single Pose ==<br />
This ''Property Family'' is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose ''Property Family''.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose ''Property Family''.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
== Quantized Curve ==<br />
This ''Property Family'' Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes header are located'''.<br />
|}<br />
<br />
=== Quantized Curve Keyframe Header (12 bytes length)===<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (m1)<br />
|}<br />
This is the only ''Property Family'' that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After reading the keyframes header, what follows up are the keyframes in which the actual keyframes are stored in.<br />
<br />
=== Quantized Keyframes (4 bytes length)===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint8_t</code> || 1 || Keyframe time '''(Relative to the time of the last keyframe).'''<br />
|-<br />
| 0x01 || <code>uint8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>uint8_t</code> || 1 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x03 || <code>uint8_t</code> || 1 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the '''output value is blending from the minimum to the maximum value, based on the value of Delta.'''<br />
<br />
So, that would leave us with...<br />
* P_value = '''minimum_value + maximum_value * delta_value'''<br />
* M0_value = '''minimum_m0 + maximum_m0 * delta_m0'''<br />
* M1_value = '''minimum_m1 + maximum_m1 * delta_m1'''<br />
<br />
After computing the full values, The curve is to be computed using the Hermite Cubic Interpolation.<br />
<br />
<br />
<br />
== Quantized-Precision Curve ==<br />
For this ''Property Family'', the process is almost the exact same. However, there are some changes.<br />
First of, This is a more precise version of the Quantized curves. Therefore, the values are doubled up.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 50 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized-Precision Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes header are located'''.<br />
|}<br />
===(Keyframes header):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float32_t</code> || 4 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float32_t</code> || 4 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float32_t</code> || 4 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float32_t</code> || 4 || Maximum value of the end tangent (m1)<br />
|}<br />
You can notice that, since the values were doubled up, The use of the custom float16_t were completely removed, since now the file can use float32's instead, which are more precise and stable in comparision. This results on the size of the keyframe header to be extended to '''24 bytes each.'''<br />
===(Keyframe):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint16_t</code> || 2 || Keyframe time '''(Absolute)'''.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Delta value of the Keyframe.<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x06 || <code>uint16_t</code> || 2 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
Aside from the keyframe time being '''Aboslute''', the rest of the process remains the exact same.<br />
<br />
<br />
<br />
== Full-Precision Curve ==<br />
This is the most straightforward ''Property Family''. However, the most expensive (in storaging terms).<br />
Different from the Quantized types, this one is not dependent of a ''Keyframe Header.''<br />
Instead, it tells the values right away, Rendering this ''Property Family'' the easiest to compute (considering this is not a single pose), the one with the most accurate movements, but the most expensive to store in storage terms.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 80 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Full-Precision Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes are located'''.<br />
|}<br />
===(Keyframes):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint16_t</code> || 2 || Keyframe time '''(Absolute)'''.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Padding, used to align the file, It has no use.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Keyframe Value<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Value of the keyframe's end tangent. (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
After that, the values can be used straight into the cubic interpolation formula.<br />
<br />
===Final Notes:===<br />
The space in which the movement of bones takes in also depends of the ''Property Family'' the curve is set in. For instance, if a bone's rest position's property (let's say it's 125.14 for X) is animated on a quantized curve, Since this is a big value, movement information will be lost due to the nature of the quantized ''Property Family'', especially when not used in a ''Quantized-Precision Curve''. Because of that, '''The bone's movements are relative to the bone's parent's pose on quantized types.''' For full precision however, since quantization is not needed, '''the property values are absolute.'''</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1844Motion (.MOT) File Format2025-09-07T20:57:23Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
<br />
Every curve is computed using the '''Cubic Hermite interpolation formula.''' That means every curve is treated as a Hermite Curve. <br />
:[[File:Formula.png|Formula of the Cubic Hermite Interpolation, used in curves.]]<br />
<br />
<br />
'''Note:''' This formula's image was taken from the [https://en.wikipedia.org/wiki/Cubic_Hermite_spline ''Cubic Hermite spline Wiki''.] <br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the ''Property Family'' of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Quantized-Precision Curve || Position X<br />
|-<br />
| 51 || Quantized-Precision Curve || Position Y<br />
|-<br />
| 52 || Quantized-Precision Curve || Position Z<br />
|-<br />
| 53 || Quantized-Precision Curve || Rotation X<br />
|-<br />
| 54 || Quantized-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Quantized-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Quantized-Precision Curve || Scale X<br />
|-<br />
| 57 || Quantized-Precision Curve || Scale Y<br />
|-<br />
| 58 || Quantized-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, curves will be readen diferently.<br />
== Single Pose ==<br />
This ''Property Family'' is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose ''Property Family''.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose ''Property Family''.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
== Quantized Curve ==<br />
This ''Property Family'' Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes header are located'''.<br />
|}<br />
<br />
=== Quantized Curve Keyframe Header (12 bytes length)===<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (m1)<br />
|}<br />
This is the only ''Property Family'' that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After reading the keyframes header, what follows up are the keyframes in which the actual keyframes are stored in.<br />
<br />
=== Quantized Keyframes (4 bytes length)===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint8_t</code> || 1 || Keyframe time '''(Relative to the time of the last keyframe).'''<br />
|-<br />
| 0x01 || <code>uint8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>uint8_t</code> || 1 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x03 || <code>uint8_t</code> || 1 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the '''output value is blending from the minimum to the maximum value, based on the value of Delta.'''<br />
<br />
So, that would leave us with...<br />
* P_value = '''minimum_value + maximum_value * delta_value'''<br />
* M0_value = '''minimum_m0 + maximum_m0 * delta_m0'''<br />
* M1_value = '''minimum_m1 + maximum_m1 * delta_m1'''<br />
<br />
After computing the full values, The curve is to be computed using the Hermite Cubic Interpolation.<br />
<br />
<br />
<br />
== Quantized-Precision Curve ==<br />
For this ''Property Family'', the process is almost the exact same. However, there are some changes.<br />
First of, This is a more precise version of the Quantized curves. Therefore, the values are doubled up.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 50 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized-Precision Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes header are located'''.<br />
|}<br />
===(Keyframes header):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float32_t</code> || 4 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float32_t</code> || 4 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float32_t</code> || 4 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float32_t</code> || 4 || Maximum value of the end tangent (m1)<br />
|}<br />
You can notice that, since the values were doubled up, The use of the custom float16_t were completely removed, since now the file can use float32's instead, which are more precise and stable in comparision. This results on the size of the keyframe header to be extended to '''24 bytes each.'''<br />
===(Keyframe):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint16_t</code> || 2 || Keyframe time '''(Absolute)'''.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Delta value of the Keyframe.<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x06 || <code>uint16_t</code> || 2 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
Aside from the keyframe time being '''Aboslute''', the rest of the process remains the exact same.<br />
<br />
<br />
<br />
== Full-Precision Curve ==<br />
This is the most straightforward ''Property Family''. However, the most expensive (in storaging terms).<br />
Different from the Quantized types, this one is not dependent of a ''Keyframe Header.''<br />
Instead, it tells the values right away, Rendering this ''Property Family'' the easiest to compute (considering this is not a single pose), the one with the most accurate movements, but the most expensive to store in storage terms.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 80 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Full-Precision Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframes are located'''.<br />
|}<br />
===(Keyframes):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint16_t</code> || 2 || Keyframe time '''(Absolute)'''.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Padding, used to align the file, It has no use.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Keyframe Value<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Value of the keyframe's end tangent. (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
After that, the values can be used straight into the cubic interpolation formula.<br />
<br />
===Final nodes===<br />
The space in which the movement of bones takes in also depends of the ''Property Family'' the curve is set in. For instance, if a bone's rest position's property (let's say it's 125.14 for X) is animated on a quantized curve, Since this is a big value, movement information will be lost due to the nature of the quantized ''Property Family'', especially when not used in a ''Quantized-Precision Curve''. Because of that, '''The bone's movements are relative to the bone's parent's pose on quantized types.''' For full precision however, since quantization is not needed, '''the property values are absolute.'''</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1843Motion (.MOT) File Format2025-09-07T20:46:25Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
<br />
Every curve is computed using the '''Cubic Hermite interpolation formula.''' That means every curve is treated as a Hermite Curve. <br />
:[[File:Formula.png|Formula of the Cubic Hermite Interpolation, used in curves.]]<br />
<br />
<br />
'''Note:''' This formula's image was taken from the [https://en.wikipedia.org/wiki/Cubic_Hermite_spline ''Cubic Hermite spline Wiki''.] <br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the ''Property Family'' of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Quantized-Precision Curve || Position X<br />
|-<br />
| 51 || Quantized-Precision Curve || Position Y<br />
|-<br />
| 52 || Quantized-Precision Curve || Position Z<br />
|-<br />
| 53 || Quantized-Precision Curve || Rotation X<br />
|-<br />
| 54 || Quantized-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Quantized-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Quantized-Precision Curve || Scale X<br />
|-<br />
| 57 || Quantized-Precision Curve || Scale Y<br />
|-<br />
| 58 || Quantized-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, curves will be readen diferently.<br />
== Single Pose ==<br />
This ''Property Family'' is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose ''Property Family''.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose ''Property Family''.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
== Quantized Curve ==<br />
This ''Property Family'' Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
=== Quantized Curve Keyframe Header (12 bytes length)===<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (m1)<br />
|}<br />
This is the only ''Property Family'' that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After that, the keyframes are given.<br />
<br />
=== Quantized Keyframes (4 bytes length)===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint8_t</code> || 1 || Keyframe time '''(Relative to the time of the last keyframe).'''<br />
|-<br />
| 0x01 || <code>uint8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>uint8_t</code> || 1 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x03 || <code>uint8_t</code> || 1 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the '''output value is blending from the minimum to the maximum value, based on the value of Delta.'''<br />
<br />
So, that would leave us with...<br />
* P_value = '''minimum_value + maximum_value * delta_value'''<br />
* M0_value = '''minimum_m0 + maximum_m0 * delta_m0'''<br />
* M1_value = '''minimum_m1 + maximum_m1 * delta_m1'''<br />
<br />
After computing the full values, The curve is to be computed using the Hermite Cubic Interpolation.<br />
<br />
<br />
<br />
== Quantized-Precision Curve ==<br />
For this ''Property Family'', the process is almost the exact same. However, there are some changes.<br />
First of, This is a more precise version of the Quantized curves. Therefore, the values are doubled up.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 50 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized-Precision Curve ''Property Family''.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
===(Keyframes header):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float32_t</code> || 4 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float32_t</code> || 4 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float32_t</code> || 4 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float32_t</code> || 4 || Maximum value of the end tangent (m1)<br />
|}<br />
You can notice that, since the values were doubled up, The use of the custom float16_t were completely removed, since now the file can use float32's instead, which are more precise and stable in comparision. This results on the size of the keyframe header to be extended to '''24 bytes each.'''<br />
===(Keyframe):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint16_t</code> || 2 || Keyframe time '''(Absolute)'''.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Delta value of the Keyframe.<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x06 || <code>uint16_t</code> || 2 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
Aside from the keyframe time being '''Aboslute''', the rest of the process remains the exact same.<br />
<br />
<br />
<br />
=== Full-Precision Curve ===<br />
This is the most straightforward ''Property Family''. However, the most expensive (in storaging terms).<br />
Different from the Quantized types, this however is not dependent of a ''Keyframe Header.''<br />
Instead, it tells the values right away, Rendering this ''Property Family'' the easiest to compute (considering this is not a single pose), but the most expensive to store in storage terms.</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1842Motion (.MOT) File Format2025-09-07T20:36:01Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
<br />
Every curve is computed using the '''Cubic Hermite interpolation formula.''' That means every curve is treated as a Hermite Curve. <br />
:[[File:Formula.png|Formula of the Cubic Hermite Interpolation, used in curves.]]<br />
<br />
<br />
'''Note:''' This formula's image was taken from the [https://en.wikipedia.org/wiki/Cubic_Hermite_spline ''Cubic Hermite spline Wiki''.] <br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Quantized-Precision Curve || Position X<br />
|-<br />
| 51 || Quantized-Precision Curve || Position Y<br />
|-<br />
| 52 || Quantized-Precision Curve || Position Z<br />
|-<br />
| 53 || Quantized-Precision Curve || Rotation X<br />
|-<br />
| 54 || Quantized-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Quantized-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Quantized-Precision Curve || Scale X<br />
|-<br />
| 57 || Quantized-Precision Curve || Scale Y<br />
|-<br />
| 58 || Quantized-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
=== Quantized Curve Keyframe Header (12 bytes length)===<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (m1)<br />
|}<br />
This is the only Property Family that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After that, the keyframes are given.<br />
<br />
=== Quantized Keyframes (4 bytes length)===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint8_t</code> || 1 || Keyframe time '''(Relative to the time of the last keyframe).'''<br />
|-<br />
| 0x01 || <code>uint8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>uint8_t</code> || 1 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x03 || <code>uint8_t</code> || 1 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the '''output value is blending from the minimum to the maximum value, based on the value of Delta.'''<br />
<br />
So, that would leave us with...<br />
* P_value = '''minimum_value + maximum_value * delta_value'''<br />
* M0_value = '''minimum_m0 + maximum_m0 * delta_m0'''<br />
* M1_value = '''minimum_m1 + maximum_m1 * delta_m1'''<br />
<br />
After computing the full values, The curve is to be computed using the Hermite Cubic Interpolation.<br />
<br />
<br />
<br />
== Quantized-Precision Curve ==<br />
For this Property Family, the process is almost the exact same. However, there are some changes.<br />
First of, This is a more precise version of the Quantized curves. Therefore, the values are doubled up.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 50 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized-Precision Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
===(Keyframes header):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float32_t</code> || 4 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float32_t</code> || 4 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float32_t</code> || 4 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float32_t</code> || 4 || Maximum value of the end tangent (m1)<br />
|}<br />
You can notice that, since the values were doubled up, The use of the custom float16_t were completely removed, since now the file can use float32's instead, which are more precise and stable in comparision. This results on the size of the keyframe header to be extended to '''24 bytes each.'''<br />
===(Keyframe):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint16_t</code> || 2 || Keyframe time '''(Absolute)'''.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Delta value of the Keyframe.<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x06 || <code>uint16_t</code> || 2 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
Aside from the keyframe time being '''Aboslute''', the rest of the process remains the exact same.</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1841Motion (.MOT) File Format2025-09-07T20:31:40Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
<br />
Every curve is computed using the '''Cubic Hermite interpolation formula.''' That means every curve is treated as a Hermite Curve. <br />
:[[File:Formula.png|Formula of the Cubic Hermite Interpolation, used in curves.]]<br />
<br />
<br />
'''Note:''' This formula's image was taken from the [https://en.wikipedia.org/wiki/Cubic_Hermite_spline ''Cubic Hermite spline Wiki''.] <br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Quantized-Precision Curve || Position X<br />
|-<br />
| 51 || Quantized-Precision Curve || Position Y<br />
|-<br />
| 52 || Quantized-Precision Curve || Position Z<br />
|-<br />
| 53 || Quantized-Precision Curve || Rotation X<br />
|-<br />
| 54 || Quantized-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Quantized-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Quantized-Precision Curve || Scale X<br />
|-<br />
| 57 || Quantized-Precision Curve || Scale Y<br />
|-<br />
| 58 || Quantized-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
=== Quantized Curve Keyframe Header (12 bytes length)===<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (m1)<br />
|}<br />
This is the only Property Family that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After that, the keyframes are given.<br />
<br />
=== Quantized Keyframes (4 bytes length)===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Keyframe time (Relative to the time of the last keyframe).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>int8_t</code> || 1 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x03 || <code>int8_t</code> || 1 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the '''output value is blending from the minimum to the maximum value, based on the value of Delta.'''<br />
<br />
So, that would leave us with...<br />
* P_value = '''minimum_value + maximum_value * delta_value'''<br />
* M0_value = '''minimum_m0 + maximum_m0 * delta_m0'''<br />
* M1_value = '''minimum_m1 + maximum_m1 * delta_m1'''<br />
<br />
After computing the full values, The curve is to be computed using the Hermite Cubic Interpolation.<br />
<br />
<br />
<br />
== Quantized-Precision Curve ==<br />
For this Property Family, the process is almost the exact same. However, there are some changes.<br />
First of, This is a more precise version of the Quantized curves. Therefore, the values are doubled up.<br />
<br />
===(Example):===<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 50 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized-Precision Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
===(Keyframes header):===<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float32_t</code> || 4 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float32_t</code> || 4 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float32_t</code> || 4 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float32_t</code> || 4 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float32_t</code> || 4 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float32_t</code> || 4 || Maximum value of the end tangent (m1)<br />
|}<br />
You can notice that, since the values were doubled up, The use of the custom float16_t were completely removed.<br />
===(Keyframe):===</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1840Motion (.MOT) File Format2025-09-07T20:21:09Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
<br />
Every curve is computed using the '''Cubic Hermite interpolation formula.''' That means every curve is treated as a Hermite Curve. <br />
:[[File:Formula.png|Formula of the Cubic Hermite Interpolation, used in curves.]]<br />
<br />
<br />
'''Note:''' This formula's image was taken from the [https://en.wikipedia.org/wiki/Cubic_Hermite_spline ''Cubic Hermite spline Wiki''.] <br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
== Quantized Curve Keyframe Header (12 bytes length)==<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (m1)<br />
|}<br />
This is the only Property Family that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After that, the keyframes are given.<br />
<br />
== Quantized Keyframes (4 bytes length)==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Keyframe time (Relative to the time of the last keyframe).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>int8_t</code> || 1 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x03 || <code>int8_t</code> || 1 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the '''output value is blending from the minimum to the maximum value, based on the value of Delta.'''<br />
<br />
So, that would leave us with...<br />
* P_value = '''minimum_value + maximum_value * delta_value'''<br />
* M0_value = '''minimum_m0 + maximum_m0 * delta_m0'''<br />
* M1_value = '''minimum_m1 + maximum_m1 * delta_m1'''</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1839Motion (.MOT) File Format2025-09-07T20:19:29Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
<br />
Every curve is computed using the '''Cubic Hermite interpolation formula.''' That means every curve is treated as a Hermite Curve. <br />
[[File:Formula.png|thumb|Formula of the Cubic Hermite Interpolation, used in curves.]]<br />
<br />
<br />
'''Note:''' This formula's image was taken from the [https://en.wikipedia.org/wiki/Cubic_Hermite_spline ''Cubic Hermite spline Wiki''.] <br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
== Quantized Curve Keyframe Header (12 bytes length)==<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (m1)<br />
|}<br />
This is the only Property Family that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After that, the keyframes are given.<br />
<br />
== Quantized Keyframes (4 bytes length)==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Keyframe time (Relative to the time of the last keyframe).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>int8_t</code> || 1 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x03 || <code>int8_t</code> || 1 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the '''output value is blending from the minimum to the maximum value, based on the value of Delta.'''<br />
<br />
So, that would leave us with...<br />
* P_value = '''minimum_value + maximum_value * delta_value'''<br />
* M0_value = '''minimum_m0 + maximum_m0 * delta_m0'''<br />
* M1_value = '''minimum_m1 + maximum_m1 * delta_m1'''</div>Akitohttps://okami.speedruns.wiki/index.php?title=File:Formula.png&diff=1838File:Formula.png2025-09-07T20:17:36Z<p>Akito: </p>
<hr />
<div>Formula of the cubic Hermite interpolation</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1837Motion (.MOT) File Format2025-09-07T20:04:52Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
From now on, every single other curve are handled as hermite curves. See more bellow...<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
== Quantized Curve Keyframe Header (12 bytes length)==<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (m0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (m0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (m1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (m1)<br />
|}<br />
This is the only Property Family that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After that, the keyframes are given.<br />
<br />
== Quantized Keyframes (4 bytes length)==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Keyframe time (Relative to the time of the last keyframe).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>int8_t</code> || 1 || Delta value of the keyframe's start tangent. (m0)<br />
|-<br />
| 0x03 || <code>int8_t</code> || 1 || Delta value of the keyframe's end tangent. (m1)<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the '''output value is blending from the minimum to the maximum value, based on the value of Delta.'''<br />
<br />
So, that would leave us with...<br />
P_value = minimum_value + maximum_value * delta_value<br />
M0_value = minimum_m0 + maximum_m0 * delta_m0<br />
M1_value = minimum_m1 + maximum_m1 * delta_m1</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1836Motion (.MOT) File Format2025-09-07T20:00:56Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
From now on, every single other curve are handled as hermite curves. See more bellow...<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
== Quantized Curve Keyframe Header (12 bytes length)==<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent<br />
|}<br />
This is the only Property Family that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After that, the keyframes are given.<br />
<br />
== Quantized Keyframes (4 bytes length)==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Keyframe time (Relative to the time of the last keyframe).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>int8_t</code> || 1 || Delta value of the keyframe's start tangent.<br />
|-<br />
| 0x03 || <code>int8_t</code> || 1 || Delta value of the keyframe's end tangent.<br />
|}<br />
<br />
<br />
The keyframe deltas are calculated as following:<br />
X = Y + Z * W<br />
Where X is the output value, Y is the minimum value, Z is the maximum value, and W is the delta value.<br />
Essentially, the formula is telling that the output value is blending from the minimum to the maximum value, based on the value of Delta.</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1835Motion (.MOT) File Format2025-09-07T19:32:11Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
From now on, every single other curve are handled as hermite curves. See more bellow...<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
== Quantized Curve Keyframe Header (12 bytes length)==<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent<br />
|}<br />
This is the only Property Family that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After that, the keyframes are given.<br />
<br />
== Quantized Keyframes (4 bytes length)==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Keyframe time (Relative to the time of the last keyframe).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>int8_t</code> || 1 || Delta value of the keyframe's start tangent.<br />
|-<br />
| 0x03 || <code>int8_t</code> || 1 || Delta value of the keyframe's end tangent.<br />
|}<br />
<br />
For quantized keyframes, The logic is that, when the Delta Value of the keyframe equals 0, the keyframe is set to '''the Minimum value of the keyframe'''(Given in the Curve Keyframe Header). And when it's set to 255, it's set to '''the Maximum value of the keyframe'''(Given in the Curve Keyframe Header).</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1834Motion (.MOT) File Format2025-09-07T19:27:12Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
From now on, every single other curve are handled as hermite curves. See more bellow...<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
== Quantized Curve Keyframe Header (12 bytes length)==<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (p0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (p0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (p1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (p1)<br />
|}<br />
This is the only Property Family that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.<br />
<br />
After that, the keyframes are given.<br />
<br />
== Quantized Keyframes (4 bytes length)==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Keyframe time (Relative to the time of the last keyframe).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Delta value of the Keyframe.<br />
|-<br />
| 0x02 || <code>int8_t</code> || 1 || Delta value of the keyframe's P0 start tangent.<br />
|-<br />
| 0x03 || <code>int8_t</code> || 1 || Delta value of the keyframe's P1 end tangent.<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1833Motion (.MOT) File Format2025-09-07T19:19:38Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
From now on, every single other curve are handled as hermite curves. See more bellow...<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
== Quantized Curve Keyframe Header (12 bytes length)==<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (p0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (p0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (p1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (p1)<br />
|}<br />
This is the only Property Family that uses the '''float16_t''' type. That's a special type of float that can be represented as two bytes. Especifically, this type of float is built with a 1 bit sign, 6 bit exponent, a 9 bit significand and a bias of 47. The bias favours smaller numbers. That means, the highest the number, the less precise it is. That's to compensate the small amount of data two bytes can pack.</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1832Motion (.MOT) File Format2025-09-07T19:10:57Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
From now on, every single other curve are handled as hermite curves. See more bellow...<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
== Quantized Curve Keyframe Header (12 bytes length)==<br />
'''Only Quantized property families contain a keyframe Header'''. That's because Every keyframe is dependent on the values given on the Header.<br />
<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>float16_t</code> || 2 || Minimum value of a keyframe.<br />
|-<br />
| 0x02 || <code>float16_t</code> || 2 || Maximum value of a keyframe.<br />
|-<br />
| 0x04 || <code>float16_t</code> || 2 || Minimum value of the start tangent (p0)<br />
|-<br />
| 0x06 || <code>float16_t</code> || 2 || Maximum value of the start tangent (p0)<br />
|-<br />
| 0x08 || <code>float16_t</code> || 2 || Minimum value of the end tangent (p1)<br />
|-<br />
| 0x0A || <code>float16_t</code> || 2 || Maximum value of the end tangent (p1)<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1831Motion (.MOT) File Format2025-09-07T18:31:05Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
== Mot main header (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
On offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info (8 bytes length) ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
From now on, every single other curve are handled as hermite curves. See more bellow...<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}<br />
<br />
== Quantized Curve Keyframe Header (12 bytes length)==<br />
Only Quantized property families contain a keyframe Header. That's because Every keyframe is dependent on the values given on the Header.</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1830Motion (.MOT) File Format2025-09-07T18:14:57Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done. But since it animates bones most of the times, i will threat it as curves that animates bones.<br />
<br />
== Mot main header ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve info count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
on Offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. it's only set as a float if the property family of the curve is a Single Pose. Otherwise, it's a offset.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
From now on, every single other curve are hermite curves. See more bellow...<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || 0 || This field is telling that '''the curve is animating the bone index 0 of the model.'''<br />
|-<br />
| 0x01 || 16 || This field is telling that '''the curve animates the X Position of the root bone''', being set on a '''Quantized Curve Property Family.'''<br />
|-<br />
| 0x02 || 4 || This field is telling that '''there's 4 keyframes on this curve.'''<br />
|-<br />
| 0x04 || 512 || This field is '''telling in which offset of the file the keyframe infos are located'''.<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1829Motion (.MOT) File Format2025-09-07T18:08:26Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done.<br />
<br />
== Mot main header ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve info count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
on Offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. That's handled when the curve property is defined. It depends on the Property Family the curve is set in.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
From now on, every single other curve are hermite curves. See more bellow...<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's the most eficient type of curve, regarding storage size.<br />
<br />
(Example):</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1828Motion (.MOT) File Format2025-09-07T18:03:45Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done.<br />
<br />
== Mot main header ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve info count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
on Offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. That's handled when the curve property is defined. It depends on the Property Family the curve is set in.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}<br />
<br />
From now on, every single other curve are hermite curves. See more bellow...<br />
<br />
== Quantized Curve ==<br />
This Property Family Is known for having Quantized values. It's <br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Property Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computing needed.<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1827Motion (.MOT) File Format2025-09-07T17:57:38Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done.<br />
<br />
== Mot main header ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve info count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
on Offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. That's handled when the curve property is defined. It depends on the Property Family the curve is set in.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the cheapest to compute. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that '''the curve is animating the root bone of the model.'''<br />
|-<br />
| 0x01 || 5 || This field is telling that '''the curve animates the Z rotation of the root bone''', being set on a '''Single-Pose Property Family.'''<br />
|-<br />
| 0x02 || 1 || This field is telling that '''there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Family.'''<br />
|-<br />
| 0x04 || 0.52 || This field is '''telling the value or the Z rotation right away''', no more computation needed.<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1826Motion (.MOT) File Format2025-09-07T17:56:36Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done.<br />
<br />
== Mot main header ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's curve info count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
on Offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|-<br />
| 0x04 || <code>uint32_t / float32_t</code> || 4 || Keyframes offset / value<br />
|}<br />
<br />
the 4th offset of each curve info can be either a float, or uint32. That's handled when the curve property is defined. It depends on the Property Family the curve is set in.<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}<br />
<br />
The Property Family tells the game how the keyframes are handled ingame. Depending on the Family the property is set in, it can be readen diferently.<br />
== Single Pose ==<br />
This Property Family is the easiest one to Decode. Because since it's a single pose, The there's only one keyframe, in which is given on the Curve Info.<br />
<br />
(Example):<br />
{| class="wikitable"<br />
! Offset !! Value !! Description<br />
|-<br />
| 0x00 || -1 || This field is telling that the curve is animating the root bone of the model.<br />
|-<br />
| 0x01 || 5 || This field is telling that the curve animates the Z rotation of the root bone, being set on a Single-Pose Property Family.<br />
|-<br />
| 0x02 || 1 || This field is telling that there's only one keyframe on this curve, which makes sense, since this curve is set on a Single-Pose Family.<br />
|-<br />
| 0x04 || 0.52 || This field is telling the value or the Z rotation right away, no more computation needed.<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1825Motion (.MOT) File Format2025-09-07T17:46:52Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done.<br />
<br />
== Mot main header ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's property count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
on Offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|}<br />
<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
<br />
|-<br />
| 50 || Semi-Precision Curve || Position X<br />
|-<br />
| 51 || Semi-Precision Curve || Position Y<br />
|-<br />
| 52 || Semi-Precision Curve || Position Z<br />
|-<br />
| 53 || Semi-Precision Curve || Rotation X<br />
|-<br />
| 54 || Semi-Precision Curve || Rotation Y<br />
|-<br />
| 55 || Semi-Precision Curve || Rotation Z<br />
|-<br />
| 56 || Semi-Precision Curve || Scale X<br />
|-<br />
| 57 || Semi-Precision Curve || Scale Y<br />
|-<br />
| 58 || Semi-Precision Curve || Scale Z<br />
<br />
|-<br />
| 80 || Full-Precision Curve || Position X<br />
|-<br />
| 81 || Full-Precision Curve || Position Y<br />
|-<br />
| 82 || Full-Precision Curve || Position Z<br />
|-<br />
| 83 || Full-Precision Curve || Rotation X<br />
|-<br />
| 84 || Full-Precision Curve || Rotation Y<br />
|-<br />
| 85 || Full-Precision Curve || Rotation Z<br />
|-<br />
| 86 || Full-Precision Curve || Scale X<br />
|-<br />
| 87 || Full-Precision Curve || Scale Y<br />
|-<br />
| 88 || Full-Precision Curve || Scale Z<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1824Motion (.MOT) File Format2025-09-07T17:44:52Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done.<br />
<br />
== Mot main header ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's property count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
on Offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve properties (See below).<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|}<br />
<br />
The curve property will define what property of the bone/object it is animating. There's some properties who could not be determined yet. See some already identified values bellow.<br />
<br />
== Curve Properties (Already identified) ==<br />
{| class="wikitable"<br />
! Value !! Property Family !! Property<br />
|-<br />
| 0 || Single Pose || Position X<br />
|-<br />
| 1 || Single Pose || Position Y<br />
|-<br />
| 2 || Single Pose || Position Z<br />
|-<br />
| 3 || Single Pose || Rotation X<br />
|-<br />
| 4 || Single Pose || Rotation Y<br />
|-<br />
| 5 || Single Pose || Rotation Z<br />
|-<br />
| 6 || Single Pose || Scale X<br />
|-<br />
| 7 || Single Pose || Scale Y<br />
|-<br />
| 8 || Single Pose || Scale Z<br />
<br />
|-<br />
| 16 || Quantized Curve || Position X<br />
|-<br />
| 17 || Quantized Curve || Position Y<br />
|-<br />
| 18 || Quantized Curve || Position Z<br />
|-<br />
| 19 || Quantized Curve || Rotation X<br />
|-<br />
| 20 || Quantized Curve || Rotation Y<br />
|-<br />
| 21 || Quantized Curve || Rotation Z<br />
|-<br />
| 22 || Quantized Curve || Scale X<br />
|-<br />
| 23 || Quantized Curve || Scale Y<br />
|-<br />
| 24 || Quantized Curve || Scale Z<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1823Motion (.MOT) File Format2025-09-07T17:34:05Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done.<br />
<br />
== Mot main header ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's property count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}<br />
<br />
on Offset 8, The File gives informations about the curves, i.e: what bone it animates, etc.<br />
<br />
== Curve Info ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>int8_t</code> || 1 || Bone index (-1 means it animates the mode's root bone).<br />
|-<br />
| 0x01 || <code>int8_t</code> || 1 || Curve property.<br />
|-<br />
| 0x02 || <code>uint16_t</code> || 2 || Curve keyframe count.<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1822Motion (.MOT) File Format2025-09-07T17:27:23Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done.<br />
<br />
== Mot header ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t</code> || 2 || Animation's frame count.<br />
|-<br />
| 0x06 || <code>uint8_t</code> || 1 || Animation's property count.<br />
|-<br />
| 0x07 || <code>uint8_t</code> || 1 || Loop flag, sets if the animation either loops or not (1/0).<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1821Motion (.MOT) File Format2025-09-07T17:24:21Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done.<br />
<br />
== Format ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number).<br />
|-<br />
| 0x04 || <code>uint16_t[numEntries]</code> || 8 * numEntries || String offsets.<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1820Motion (.MOT) File Format2025-09-07T17:23:05Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates '''curves and/or properties''' for an given embbed model. Because of that, it's almost always certain that they are contained in a file container (dat).<br />
There's instances of mots that controlled properties instead of bones, so it's not always certain of what it animates. A further inspection have to be done.<br />
<br />
== Format ==<br />
{| class="wikitable"<br />
! Offset !! Type !! Size !! Description<br />
|-<br />
| 0x00 || <code>uint32_t</code> || 4 || Number of entries.<br />
|-<br />
| 0x04 || <code>int64_t[numEntries]</code> || 8 * numEntries || String offsets.<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1819Motion (.MOT) File Format2025-09-07T17:20:25Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
<br />
==Explanation==<br />
<br />
This file incorporates curves and/or properties for an given embbed model. Because of that, it's almost always certain that they are contained in a file container(dat).</div>Akitohttps://okami.speedruns.wiki/index.php?title=File_Formats&diff=1818File Formats2025-09-07T17:18:30Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
==Explanation==<br />
<br />
Here you will find an incomplete list of descriptions of file formats in Okami, discovered via [[Reverse Engineering]].<br />
<br />
'''Extension''' is a list of file extensions associated with this type.<br />
<br />
'''Short Description''' is an short explanation of the point of the file.<br />
<br />
== Archives == <br />
<br />
Archives are simply expanded into more files.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Extension !! Short Description<br />
|-<br />
| .bin || Generic Archive<br />
|-<br />
| .dat || Generic Archive with some exceptions. (See below.)<br />
|-<br />
| .DDP || Image Archive (DDS)<br />
|-<br />
| .EFF || Generic Archive<br />
|-<br />
| .SSD || Generic Archive<br />
|-<br />
| .TBL || Generic Archive <br />
|}<br />
<br />
'''.dat''' has a few exceptions: files in the event/ folder have their own format. Some (but not all) of the .dat files in the id/ folder as well as privilege/IllustPrivilege.dat are just DDS files one after the next. <br />
<br />
== Level Files (st#) ==<br />
<br />
Level files are found in data_pc/st#. See [[Map Table]] for a complete list.<br />
<br />
'''Archive''' is whether the files is stored in the .bin or .dat for the level in Okami HD for PC.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Extension !! Short Description !! Archive<br />
|-<br />
| .ACT || Something to do with NPCs. || .bin<br />
|-<br />
| .AKT || Archive of collision models (.AK) || .dat<br />
|-<br />
| [[Animal Group (.ANS) File Format|.ANS]] || Animals. || .bin<br />
|-<br />
| .BMH || Unknown. || .bin<br />
|-<br />
| .CAM || Unknown. || .bin<br />
|-<br />
| .CMP || Unknown. || .dat<br />
|-<br />
| .EAR || Unknown. || .dat<br />
|-<br />
| [[Encounter (.ECT) File Format|.ECT]] || Encounters. || .bin<br />
|-<br />
| .EFF || Unknown Archive. || .bin<br />
|-<br />
| .FI2 || Atmospheric Effects || .dat<br />
|-<br />
| [[Shop Contents (.ISL) File Format|.ISL]] || Shop contents and prices. || .bin<br />
|-<br />
| [[Loot (.ITS) File Format|.ITS]] || Guaranteed loot locations. || .bin<br />
|-<br />
| [[Exit Destination (.JMP) File Format|.JMP]] || Exit destinations. || .dat<br />
|-<br />
| .LI3 || Lighting. || .dat<br />
|-<br />
| [[Zones (.MEH/.SCA/.SCI) File Format|.MEH <br>.SCA <br>.SCI]] || Zone definitions, such as dialogue, exits, bit flags. || .bin <br>.bin <br>.dat<br />
|-<br />
| [[Motion (.MOT) File Format|.MOT]] || Animation file. || .dat<br />
|-<br />
| .MRT || Unknown. Has locations of map restoration areas. || .bin<br />
|-<br />
| .MSA || Unknown. || .bin<br />
|-<br />
| [[Message_Data_(.MSD)_File_Format|.MSD]] || Dialogue text. || .bin<br />
|-<br />
| [[Object_Placement_(.TAT/.TRE/.TSC)_File_Format|_objtbl.TSC <br>_objtbl2.TRE <br>_objtbl3.TAT]] || Objects placed around the map. || .dat<br />
|-<br />
| [[Drop Table (.RNI) File Format|_randtbl.RNI]] || Drop tables. || .dat<br />
|-<br />
| .RHT || Unknown. || .dat<br />
|-<br />
| .SCL || Unknown. || .dat<br />
|-<br />
| .SCP || Archive containing texture models (.SCR) and a texture archive (.DDP). || .dat<br />
|-<br />
| .SCR || Texture model definitions. || .dat/.SCP<br />
|-<br />
| .SCM || Unknown || .bin<br />
|-<br />
| .SSD || Unknown. || .bin<br />
|-<br />
| [[Dojo Contents (.SSL) File Format|.SSL]] || Dojo contents and prices. || .bin<br />
|-<br />
| .TS || Unknown. || .bin<br />
|-<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=Motion_(.MOT)_File_Format&diff=1817Motion (.MOT) File Format2025-09-07T17:17:12Z<p>Akito: Created page with "'''''Note''': This page pertains to Reverse Engineering of Okami File Formats.''"</p>
<hr />
<div>'''''Note''': This page pertains to Reverse Engineering of Okami File Formats.''</div>Akitohttps://okami.speedruns.wiki/index.php?title=File_Formats&diff=1816File Formats2025-09-07T17:14:11Z<p>Akito: /* Level Files (st#) */</p>
<hr />
<div>{{File Format}}<br />
==Explanation==<br />
<br />
Here you will find an incomplete list of descriptions of file formats in Okami, discovered via [[Reverse Engineering]].<br />
<br />
'''Extension''' is a list of file extensions associated with this type.<br />
<br />
'''Short Description''' is an short explanation of the point of the file.<br />
<br />
== Archives == <br />
<br />
Archives are simply expanded into more files.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Extension !! Short Description<br />
|-<br />
| .bin || Generic Archive<br />
|-<br />
| .dat || Generic Archive with some exceptions. (See below.)<br />
|-<br />
| .DDP || Image Archive (DDS)<br />
|-<br />
| .EFF || Generic Archive<br />
|-<br />
| .SSD || Generic Archive<br />
|-<br />
| .TBL || Generic Archive <br />
|}<br />
<br />
'''.dat''' has a few exceptions: files in the event/ folder have their own format. Some (but not all) of the .dat files in the id/ folder as well as privilege/IllustPrivilege.dat are just DDS files one after the next. <br />
<br />
== Level Files (st#) ==<br />
<br />
Level files are found in data_pc/st#. See [[Map Table]] for a complete list.<br />
<br />
'''Archive''' is whether the files is stored in the .bin or .dat for the level in Okami HD for PC.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Extension !! Short Description !! Archive<br />
|-<br />
| .ACT || Something to do with NPCs. || .bin<br />
|-<br />
| .AKT || Archive of collision models (.AK) || .dat<br />
|-<br />
| [[Animal Group (.ANS) File Format|.ANS]] || Animals. || .bin<br />
|-<br />
| .BMH || Unknown. || .bin<br />
|-<br />
| .CAM || Unknown. || .bin<br />
|-<br />
| .CMP || Unknown. || .dat<br />
|-<br />
| .EAR || Unknown. || .dat<br />
|-<br />
| [[Encounter (.ECT) File Format|.ECT]] || Encounters. || .bin<br />
|-<br />
| .EFF || Unknown Archive. || .bin<br />
|-<br />
| .FI2 || Atmospheric Effects || .dat<br />
|-<br />
| [[Shop Contents (.ISL) File Format|.ISL]] || Shop contents and prices. || .bin<br />
|-<br />
| [[Loot (.ITS) File Format|.ITS]] || Guaranteed loot locations. || .bin<br />
|-<br />
| [[Exit Destination (.JMP) File Format|.JMP]] || Exit destinations. || .dat<br />
|-<br />
| .LI3 || Lighting. || .dat<br />
|-<br />
| [[Zones (.MEH/.SCA/.SCI) File Format|.MEH <br>.SCA <br>.SCI]] || Zone definitions, such as dialogue, exits, bit flags. || .bin <br>.bin <br>.dat<br />
|-<br />
| [[Motion (.MOT) File Format|.MOT]] || Animation file. || .mot<br />
|-<br />
| .MRT || Unknown. Has locations of map restoration areas. || .bin<br />
|-<br />
| .MSA || Unknown. || .bin<br />
|-<br />
| [[Message_Data_(.MSD)_File_Format|.MSD]] || Dialogue text. || .bin<br />
|-<br />
| [[Object_Placement_(.TAT/.TRE/.TSC)_File_Format|_objtbl.TSC <br>_objtbl2.TRE <br>_objtbl3.TAT]] || Objects placed around the map. || .dat<br />
|-<br />
| [[Drop Table (.RNI) File Format|_randtbl.RNI]] || Drop tables. || .dat<br />
|-<br />
| .RHT || Unknown. || .dat<br />
|-<br />
| .SCL || Unknown. || .dat<br />
|-<br />
| .SCP || Archive containing texture models (.SCR) and a texture archive (.DDP). || .dat<br />
|-<br />
| .SCR || Texture model definitions. || .dat/.SCP<br />
|-<br />
| .SCM || Unknown || .bin<br />
|-<br />
| .SSD || Unknown. || .bin<br />
|-<br />
| [[Dojo Contents (.SSL) File Format|.SSL]] || Dojo contents and prices. || .bin<br />
|-<br />
| .TS || Unknown. || .bin<br />
|-<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=File_Formats&diff=1815File Formats2025-09-07T17:13:48Z<p>Akito: /* Level Files (st#) */</p>
<hr />
<div>{{File Format}}<br />
==Explanation==<br />
<br />
Here you will find an incomplete list of descriptions of file formats in Okami, discovered via [[Reverse Engineering]].<br />
<br />
'''Extension''' is a list of file extensions associated with this type.<br />
<br />
'''Short Description''' is an short explanation of the point of the file.<br />
<br />
== Archives == <br />
<br />
Archives are simply expanded into more files.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Extension !! Short Description<br />
|-<br />
| .bin || Generic Archive<br />
|-<br />
| .dat || Generic Archive with some exceptions. (See below.)<br />
|-<br />
| .DDP || Image Archive (DDS)<br />
|-<br />
| .EFF || Generic Archive<br />
|-<br />
| .SSD || Generic Archive<br />
|-<br />
| .TBL || Generic Archive <br />
|}<br />
<br />
'''.dat''' has a few exceptions: files in the event/ folder have their own format. Some (but not all) of the .dat files in the id/ folder as well as privilege/IllustPrivilege.dat are just DDS files one after the next. <br />
<br />
== Level Files (st#) ==<br />
<br />
Level files are found in data_pc/st#. See [[Map Table]] for a complete list.<br />
<br />
'''Archive''' is whether the files is stored in the .bin or .dat for the level in Okami HD for PC.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Extension !! Short Description !! Archive<br />
|-<br />
| .ACT || Something to do with NPCs. || .bin<br />
|-<br />
| .AKT || Archive of collision models (.AK) || .dat<br />
|-<br />
| [[Animal Group (.ANS) File Format|.ANS]] || Animals. || .bin<br />
|-<br />
| .BMH || Unknown. || .bin<br />
|-<br />
| .CAM || Unknown. || .bin<br />
|-<br />
| .CMP || Unknown. || .dat<br />
|-<br />
| .EAR || Unknown. || .dat<br />
|-<br />
| [[Encounter (.ECT) File Format|.ECT]] || Encounters. || .bin<br />
|-<br />
| .EFF || Unknown Archive. || .bin<br />
|-<br />
| .FI2 || Atmospheric Effects || .dat<br />
|-<br />
| [[Shop Contents (.ISL) File Format|.ISL]] || Shop contents and prices. || .bin<br />
|-<br />
| [[Loot (.ITS) File Format|.ITS]] || Guaranteed loot locations. || .bin<br />
|-<br />
| [[Exit Destination (.JMP) File Format|.JMP]] || Exit destinations. || .dat<br />
|-<br />
| .LI3 || Lighting. || .dat<br />
|-<br />
| [[Zones (.MEH/.SCA/.SCI) File Format|.MEH <br>.SCA <br>.SCI]] || Zone definitions, such as dialogue, exits, bit flags. || .bin <br>.bin <br>.dat<br />
|-<br />
| [[Motion (.MOT) File Format|.JMP]] || Animation file. || .mot<br />
|-<br />
| .MRT || Unknown. Has locations of map restoration areas. || .bin<br />
|-<br />
| .MSA || Unknown. || .bin<br />
|-<br />
| [[Message_Data_(.MSD)_File_Format|.MSD]] || Dialogue text. || .bin<br />
|-<br />
| [[Object_Placement_(.TAT/.TRE/.TSC)_File_Format|_objtbl.TSC <br>_objtbl2.TRE <br>_objtbl3.TAT]] || Objects placed around the map. || .dat<br />
|-<br />
| [[Drop Table (.RNI) File Format|_randtbl.RNI]] || Drop tables. || .dat<br />
|-<br />
| .RHT || Unknown. || .dat<br />
|-<br />
| .SCL || Unknown. || .dat<br />
|-<br />
| .SCP || Archive containing texture models (.SCR) and a texture archive (.DDP). || .dat<br />
|-<br />
| .SCR || Texture model definitions. || .dat/.SCP<br />
|-<br />
| .SCM || Unknown || .bin<br />
|-<br />
| .SSD || Unknown. || .bin<br />
|-<br />
| [[Dojo Contents (.SSL) File Format|.SSL]] || Dojo contents and prices. || .bin<br />
|-<br />
| .TS || Unknown. || .bin<br />
|-<br />
|}</div>Akitohttps://okami.speedruns.wiki/index.php?title=File_Formats&diff=1814File Formats2025-09-07T17:11:35Z<p>Akito: </p>
<hr />
<div>{{File Format}}<br />
==Explanation==<br />
<br />
Here you will find an incomplete list of descriptions of file formats in Okami, discovered via [[Reverse Engineering]].<br />
<br />
'''Extension''' is a list of file extensions associated with this type.<br />
<br />
'''Short Description''' is an short explanation of the point of the file.<br />
<br />
== Archives == <br />
<br />
Archives are simply expanded into more files.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Extension !! Short Description<br />
|-<br />
| .bin || Generic Archive<br />
|-<br />
| .dat || Generic Archive with some exceptions. (See below.)<br />
|-<br />
| .DDP || Image Archive (DDS)<br />
|-<br />
| .EFF || Generic Archive<br />
|-<br />
| .SSD || Generic Archive<br />
|-<br />
| .TBL || Generic Archive <br />
|}<br />
<br />
'''.dat''' has a few exceptions: files in the event/ folder have their own format. Some (but not all) of the .dat files in the id/ folder as well as privilege/IllustPrivilege.dat are just DDS files one after the next. <br />
<br />
== Level Files (st#) ==<br />
<br />
Level files are found in data_pc/st#. See [[Map Table]] for a complete list.<br />
<br />
'''Archive''' is whether the files is stored in the .bin or .dat for the level in Okami HD for PC.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Extension !! Short Description !! Archive<br />
|-<br />
| .ACT || Something to do with NPCs. || .bin<br />
|-<br />
| .AKT || Archive of collision models (.AK) || .dat<br />
|-<br />
| [[Animal Group (.ANS) File Format|.ANS]] || Animals. || .bin<br />
|-<br />
| .BMH || Unknown. || .bin<br />
|-<br />
| .CAM || Unknown. || .bin<br />
|-<br />
| .CMP || Unknown. || .dat<br />
|-<br />
| .EAR || Unknown. || .dat<br />
|-<br />
| [[Encounter (.ECT) File Format|.ECT]] || Encounters. || .bin<br />
|-<br />
| .EFF || Unknown Archive. || .bin<br />
|-<br />
| .FI2 || Atmospheric Effects || .dat<br />
|-<br />
| [[Shop Contents (.ISL) File Format|.ISL]] || Shop contents and prices. || .bin<br />
|-<br />
| [[Loot (.ITS) File Format|.ITS]] || Guaranteed loot locations. || .bin<br />
|-<br />
| [[Exit Destination (.JMP) File Format|.JMP]] || Exit destinations. || .dat<br />
|-<br />
| .LI3 || Lighting. || .dat<br />
|-<br />
| [[Zones (.MEH/.SCA/.SCI) File Format|.MEH <br>.SCA <br>.SCI]] || Zone definitions, such as dialogue, exits, bit flags. || .bin <br>.bin <br>.dat<br />
|-<br />
| .MOT || Animation (Motion). || .mot<br />
|-<br />
| .MRT || Unknown. Has locations of map restoration areas. || .bin<br />
|-<br />
| .MSA || Unknown. || .bin<br />
|-<br />
| [[Message_Data_(.MSD)_File_Format|.MSD]] || Dialogue text. || .bin<br />
|-<br />
| [[Object_Placement_(.TAT/.TRE/.TSC)_File_Format|_objtbl.TSC <br>_objtbl2.TRE <br>_objtbl3.TAT]] || Objects placed around the map. || .dat<br />
|-<br />
| [[Drop Table (.RNI) File Format|_randtbl.RNI]] || Drop tables. || .dat<br />
|-<br />
| .RHT || Unknown. || .dat<br />
|-<br />
| .SCL || Unknown. || .dat<br />
|-<br />
| .SCP || Archive containing texture models (.SCR) and a texture archive (.DDP). || .dat<br />
|-<br />
| .SCR || Texture model definitions. || .dat/.SCP<br />
|-<br />
| .SCM || Unknown || .bin<br />
|-<br />
| .SSD || Unknown. || .bin<br />
|-<br />
| [[Dojo Contents (.SSL) File Format|.SSL]] || Dojo contents and prices. || .bin<br />
|-<br />
| .TS || Unknown. || .bin<br />
|-<br />
|}</div>Akito