Difference between revisions of "Motion (.MOT) File Format"
Jump to navigation
Jump to search
m |
m |
||
Line 3: | Line 3: | ||
==Explanation== | ==Explanation== | ||
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). | 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). | ||
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. | |||
== Format == | |||
{| class="wikitable" | |||
! Offset !! Type !! Size !! Description | |||
|- | |||
| 0x00 || <code>uint32_t</code> || 4 || Number of entries. | |||
|- | |||
| 0x04 || <code>int64_t[numEntries]</code> || 8 * numEntries || String offsets. | |||
|} |
Revision as of 17:23, 7 September 2025
Note: This page pertains to Reverse Engineering of Okami File Formats.
Explanation
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). 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.
Format
Offset | Type | Size | Description |
---|---|---|---|
0x00 | uint32_t |
4 | Number of entries. |
0x04 | int64_t[numEntries] |
8 * numEntries | String offsets. |