Files
TeslaRel410/restoration
CydandClaude Fable 5 6b9a54089c BT410 5.3.104: turn-in-place -- the mech STEPS around at a standstill instead of pivoting like a statue
The dispatcher (master perf @0x4aa505-0x4aa588, from the raw disasm -- the
function Ghidra never decompiled), re-hosted at the gait seam in Simulate:

  From Standing, arm the trn clip when the mech is TURNING (the binary's
  operand is |angularVelocity| > 1e-4; at a standstill the turn rate is
  exactly walkingTurnRate, so the test is turnDemand * walkingTurnRate),
  the speed demand sits in the FULL sub-walk band [0, standSpeed], the
  model carries a trn clip (turnCapable, real since 5.3.103), and the
  wind-down debounce is clear.

  BOTH channels arm on the same frame -- the lockstep weld.  Arming only
  the leg lets the body enter its next cycle frames apart and the two walk
  cycles run permanently out of phase (the donor's rhythmic-gait-skip
  finding).  Each trn clip plays one figure and drops back to Standing via
  the case-4 group, so a held turn re-arms clip after clip.

  The debounce is the master perf's own shape: legResetLatch cleared at the
  top of every frame (@0x4a9bff), set by the advancer's wind-down, honoured
  here -- a walk that wound down THIS frame cannot re-enter as a turn until
  the next.

LIVE (new pod_render_trn.conf: throttle 0, turn 0.5, exterior clips):

    pos PINNED at (-641.043, 0, -243.722) across the whole run
    yaw sweeping the full circle
    spd oscillating +/-0.001347

That last number is the proof of authenticity: it is the trn clip's authored
root translation -- the foot shuffle.  The mech turns by STEPPING, not by
having its yaw slid underneath it, and the stride-driven speed model shows
the steps.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-03 14:55:36 -05:00
..

Scene Restorations

Modern re-renderings of the Division dVS scenes recovered from the Glaze developer drive (see HISTORY.md) and this repo's CONTENT tree. The originals ran on Division Ltd.'s pixel-pipeline hardware in 19941997; these tools parse the original data files and re-render them in WebGL, in the browser.

Viewers (open in any browser, fully self-contained)

  • vwe-archive.html — the Scene Archive: 26 curated scenes across all projects — Star Trek (Enterprise-D, Klingon flyby), Hull Pressure (sea demos, fish schools, sunken temple), BattleTech (polar map with mech lineup, Ravine and desert maps, stadium), Red Planet (Blade arena, the Mars canal milestone demo), and the Canyon/Maya-temple Division demos. Fly camera: drag to look, WASD to fly, R resets.
  • trek-scn.html — the original standalone Star Trek restoration (TREK.SCN and KLNGVID.SCN).

Toolkit

  • divformats.py — parsers for every Division format found on the drive: text VGF/VMF (DIV-VIZ2 geometry/materials, both the 1995 VERSION 2:07 and 1996 02:05 dialects, with header SCALE support), binary BGF/BMF (DIV-BIZ2) — the binary block-stream layout was recovered from Division's own reader source (DPL3/BIZREAD.C, 1994), including all 14 vertex layouts, pmesh/tristrip/polygon connectivity, LOD blocks (newer writers nest patches inside LODs; the largest LOD is taken), and embedded materials/textures/ramps — plus TGA and raw SVT textures, SPL splines, and SCN scene scripts.
  • audit.py — scans every .SCN on the drive and reports what fraction of its geometry survives, and in which format.
  • extract_all.py — extracts every scene with ≥60 % of its geometry recoverable (108 of 241 on the drive; the rest reference lost models) into allscenes.json, resolving models/materials/textures across the drive and this repo's CONTENT dirs.
  • gallery_build.py — curates scenes from allscenes.json into the self-contained vwe-archive.html (via gallery_template.html).
  • convert.py / viewer_template.html — the original single-scene Star Trek pipeline.

Rebuild

python extract_all.py     # requires the sda4/ drive dump beside this repo
python gallery_build.py

Fidelity notes

Faithful: vertices, triangles, material colors and shading ramps, textures, fog and light parameters, spline motion, camera start positions. Approximated: Division's rasterizer behavior, point sizes, timing (originals ran at 30 Hz). Not simulated: event-driven SPECIALFX particles. A few dev scenes had camera start positions inside geometry; those get overridden or auto-framed cameras (see START_OVERRIDE in gallery_build.py). Scenes missing one or more models from the drive say so in their header.