OBD:TRAM: Difference between revisions

OBD:TRAM (view source)

No change in size , 8 September 2020

m

typo

5,389

edits

@@ Line 189: / Line 189: @@
 ;Eight-bit frame counts and limiting consequences thereof
-:Frame counts in Oni's TRAM are either absolute frame counts since the beginning of the animation, or intervals between events of keyframes. Mostly they are 16-bit integer fields (allowing for a range of either 65535 frames = 1092.25 seconds, or 32767 frames = 546.1333... seconds, depending on whether it's interpreted as signed or unsigned by the engine). In some contexts, though, 8-bit integers (bytes) are used instead, which reduce the range to 255 frames = 4.25 seconds (or 127 frames = 2.11666... seconds if the engine reads the byte as signed).
+:Frame counts in Oni's TRAM are either absolute frame counts since the beginning of the animation, or intervals between events or keyframes. Mostly they are 16-bit integer fields (allowing for a range of either 65535 frames = 1092.25 seconds, or 32767 frames = 546.1333... seconds, depending on whether it's interpreted as signed or unsigned by the engine). In some contexts, though, 8-bit integers (bytes) are used instead, which reduce the range to 255 frames = 4.25 seconds (or 127 frames = 2.11666... seconds if the engine reads the byte as signed).
 :The following contexts involve 8-bit frame counts:
 *[[OBD:TRAM/raw0x1C|Motion blur]]: