Live preview (JavaScript)
The loop is played live in your browser from the validated loop table (the same data the reference render below was made from); the badge on the player is its self-test (seam + motion probes). A pre-rendered GIF fallback is embedded for no-JS viewers.
Super Heavy Battle Tank — from the unit’s FBI.
COB-exact: timeline 1:1 from vc109.cob (aim/fire (COB VM), disassembled with _cob_dis.py). Fire/hit/death/smoke scripts are engine-driven or firing-only and not part of this loop.
COB timeline (VC109.COB)
- 0.00–0.40 s — Rest pose (3DO zero point)
- 0.40–1.30 s — AimPrimary(8192, 3641): +45° yaw / +20° pitch at the COB aim speeds (concurrent)
- 1.30–10.90 s — 4 shots at the M20_SABOT reloadtime (2400 ms) — barrels/flares per the compiled script (barrel1/barrel2)
- 10.90–14.50 s — AimSecondary(8192, 3641) + 2 shots at the ARMMECH_ROCKET reloadtime (1800 ms) — barrels/flares per the compiled script (flashes only)
- 14.50–17.30 s — AimTertiary(8192, 3641) + 2 shots at the CORKROG_ROCKET reloadtime (1400 ms) — barrels/flares per the compiled script (flashes only)
- 24.20–24.20 s — AimPrimary(0, 0) and the other weapons’ close calls: back to the rest aim (the aim calls the engine sends next; RestoreAfterDelay pacing is engine-driven)
- 24.20–24.80 s — rest again — loop restarts seam-clean (frame N = frame 0, pixel-verified)
Every stage duration equals its COB sleep exactly; values are raw COB units (turns: BAM 65536 = 360°, moves: elmo × 163840). Renderer conversions follow the proven family conventions (_cob_anim.py).
Engine-side hooks & source notes
- Three weapon systems, three pacing grids — the loop fires them in the engine's order, each on its own weapon-TDF reloadtime: M20_SABOT (2400 ms, 4 shots), ARMMECH_ROCKET (1800 ms, 2 shots), CORKROG_ROCKET (1400 ms, 2 shots). The pacing is read from the weapon definitions, never invented.
- Per-weapon restore chains — the script carries RestoreAfterDelay AND RestorePrimary; both are per-weapon restores, and both run exactly once at the close (their engine pacing stays out of the loop).
- The close calls (AimPrimary/AimSecondary/AimTertiary at (0, 0)) stand in for the engine-paced restores and close every channel seam-clean (pixel-verified frame 0 = frame N).