Difference between revisions of "Object Placement (.TAT/.TRE/.TSC) File Format"
Jump to navigation
Jump to search
Heinermann (talk | contribs) (map event req) |
Heinermann (talk | contribs) (→Object Entry: oops this isn't true) |
||
| Line 39: | Line 39: | ||
| 16 || 4 || <code>uint8_t[4]</code> || Unknown | | 16 || 4 || <code>uint8_t[4]</code> || Unknown | ||
|- | |- | ||
| 20 || 1 || <code>uint8_t</code> || | | 20 || 1 || <code>uint8_t</code> || Unknown | ||
|- | |- | ||
| 21 || 11 || <code>uint8_t[11]</code> || Unknown | | 21 || 11 || <code>uint8_t[11]</code> || Unknown | ||
Revision as of 08:48, 31 July 2025
Note: This page pertains to Reverse Engineering of Okami File Formats.
Object placement format.
TSC has objects from category 0x09 (gt), contains various general objects.
TRE has objects from category 0x0B (vt), contains mainly vegetation like grass and trees.
File Format
Header
| Start (Byte) | Width (Bytes) | Type | Description |
|---|---|---|---|
| 0 | 4 | uint32_t |
Number of Entries |
| 4 | 40 * numEntries | TObjEntry[numEntries] |
Entries |
| padding | Pad zeroes for 16 byte alignment |
Object Entry
| Start (Byte) | Width (Bytes) | Type | Description |
|---|---|---|---|
| 0 | 1 | uint8_t |
Object Table Index |
| 1 | 1 | uint8_t |
Object category. 0x09 = gt/, 0x0B = vt/
|
| 2 | 1 | uint8_t |
Unknown |
| 3 | 1 | uint8_t |
Unknown |
| 4 | 3 | PackedTuple<uint8_t> |
Size (width, height, depth). |
| 7 | 3 | PackedTuple<uint8_t> |
Rotation around axis (x, y, z). |
| 10 | 6 | PackedTuple<uint16_t> |
Location (x, y, z) |
| 16 | 4 | uint8_t[4] |
Unknown |
| 20 | 1 | uint8_t |
Unknown |
| 21 | 11 | uint8_t[11] |
Unknown |
| 32 | 8 | uint8_t[8] |
Unkown/padding |