Difference between revisions of "Motion (.MOT) File Format"
Jump to navigation
Jump to search
m |
m |
||
| Line 10: | Line 10: | ||
! Offset !! Type !! Size !! Description | ! Offset !! Type !! Size !! Description | ||
|- | |- | ||
| 0x00 || <code>uint32_t</code> || 4 || | | 0x00 || <code>uint32_t</code> || 4 || File identifier (Magic number). | ||
|- | |- | ||
| 0x04 || <code> | | 0x04 || <code>uint16_t[numEntries]</code> || 8 * numEntries || String offsets. | ||
|} | |} | ||
Revision as of 17:24, 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 | File identifier (Magic number). |
| 0x04 | uint16_t[numEntries] |
8 * numEntries | String offsets. |