OBD:TRAM: Difference between revisions

[[image:tram_all.gif]]

{{OBDtr| 0x030 | offset  |FFFFC8| 60 B9 80 00 | 0x0080B960  | .raw-address of the [[OBD:TRAM/raw0x30|position data]] (for basic prediction) )}}

:0x'''01''' 00 00 00 - private1 (used at runtime only; marks that the animation was loaded)

:0x'''40''' 00 00 00 - inAir

:0x00 00 '''80''' 00 - noAIPickup

{{OBDtr| 0x044 | link    |C8FFFF| 00 00 00 00 | unused      | direct animation 1 (link to another TRAM file) }}

Aiming screen TRAMs "use" several bones here. Other overlay TRAMs use only "chest". Non-overlay TRAMs use none.

{{OBDtr| 0x04C | bitset32 |FFC8FF| 00 00 00 00 | 0          | replaced parts; same bitset layout as above; only overlay TRAMs other than aiming-screen ones "replace" parts. }}

{{OBDtr| 0x054 | int16    |C800C8| 01 00      | 1          | main attack direction; the following directions are possible:

{{OBDtr| 0x056 | uint16  |C87C64| 06 00    | 6 <nowiki>=</nowiki> superpunch | vocalization type (-1 if unused); references one of the 10 vocalization slots in [[OBD:ONCC|ONCC]]

{{OBDtrBK|Extent info}}

{{OBDtr| 0x158 | int32    |FF80C0| 00 00 00 00 | 0          | runtime only; pointer to the sound for this animation (initialised from [[OBD:BINA/SABD|SABD]])}}

{{OBDtr| 0x15C | int16    |D0C0AF| 00 00      | 0          | runtime only; sound start frame (initialised from SABD) }}

{{OBDtr| 0x15E | int16    |D0C0AF| 3C 00      | 60          | animation frame rate (typically 60 frames per second) }}

{{OBDtr| 0x162 | int16    |EEDDFF| 16 00      | 22          | animation type (from anim_types.[[OBD:StNA|StNA]]) }}

{{OBDtr| 0x164 | int16    |C5FF8A| 16 00      | 6          | aiming type }}

{{OBDtr| 0x166 | int16    |C5FF8A| 00 00      | 0          | from state }}

{{OBDtr| 0x16A | int16    |C0C0C0| 13 00      | 19          | number of bodyparts }}

{{OBDtr| 0x16C | int16    |FF0080| 50 00      | 80          | number of frames (at possibly custom frame rate) }}

:0x'''04'''00 - "shoulder" (not used by the engine; possibly for rocket launchers)

{{OBDtr| 0x17A | uint16  |0000BF| FF FF      | 65535      | maximal interpolation }}

{{OBDtr| 0x17C | uint16  |804040| FF FF      | 65535      | action frame }}

{{OBDtr| 0x182 | uint8    |808080| 02          | 2          | number of elements in the attack part }}

{{OBDtr| 0x183 | uint8    |808080| 00          | 0          | number of elements in the take damage part }}

{{OBDtr| 0x184 | uint8    |FFAA82| 01          | 1          | number of elements in the motion blur part }}

{{OBDtr| 0x185 | uint8    |FFAA82| 01          | 1          | number of elements in the shortcut part }}

{{OBDtr| 0x186 | uint8    |00D900| 02          | 2          | number of elements in the footstep part }}

{{OBDtr| 0x187 | uint8    |00D900| 04          | 4          | number of elements in the particle part }}

{{OBDtr| 0x188 | char[24] |CACAFF| AD DE      | dead        | unused }}

:(The following analysis assumes 60fps as an animation's frame rate. If the framerate can be reduced, the limiting time amounts will increase accordingly.)

Most typically a frame count is an unsigned 16-bit integer, which allows for a comfortable range of 65535 frames = 1092.25 seconds = 18 m 12.25 s. Even if the integer is accidentally parsed as 16-bit ''signed'', the wraparound to negative values only happens after 32767 frames = 546.1<span style="text-decoration:overline;">3</span> seconds = 9 m 6.1<span style="text-decoration:overline;">3</span> s. Oni has other contexts where frame counts are stored as 16-bit integers, e.g., [[OBD:SNDD|SNDD]] and [[OBD:OBAN|OBAN]].

Some of the frame counts inside a TRAM are stored as 8-bit integers (unsigned), which reduces the range to 255 frames = 4.25 seconds (or, in the event of signed interpretation, 127 frames = 2.11<span style="text-decoration:overline;">6</span> seconds).<br />The contexts where 8-bit frame counts occur are as follows.

For an animation that has a keyframe for every bone at each game tick, a 518-frame duration corresponds to 8.6<span style="text-decoration:overline;">3</span> seconds, whereas 213 frames = 3.55 seconds. Typically, however, rotation tracks will have significant keyframe reduction, e.g., Konoko's "Rising Fury!" lasts 80 frames but the pelvis rotation has only 23 keyframe intervals. Assuming 4:1 keyframe reduction for typical animations, this means that the 16-bit offset won't be an issue (for size-6 animations) unless the animation is longer than about 30 seconds.