Files

T

CydandClaude Fable 5 41fca98f85 BT410 5.3.110: the gyroscope lives -- the cockpit's springs, the hit bounce, and the crunch, all wired

The feel wave's cornerstone, transcribed from the task-#56 byte-exact donor
per the GYRO.NOTES.md plan:

  THE SPRINGS.  IntegrateEyeJoint (@004b2ec0): the eye TRANSLATION spring
  whose equilibrium (posSpring+negSpring)/2 IS the authentic steady eye
  offset, with the byte-verified quirks intact -- the damping step
  OVERWRITES the force accumulator (it carries last frame's damping and
  the damage impulses by design) and the position step has NO dt.
  IntegrateBody (@004b30ec): the body ROTATION spring, X/Z-crossed on the
  spring force and crossed AGAIN on the orientation step.

  THE SIM (@004b275c): chain the power watch (5.3.109's mirrors), slew the
  sway angle between the powered and impaired percentages -- impaired reads
  the gyro's OWN mirrored alarms: watchdog != Ready or heat == Failure --
  band-clamp, run both integrators.  The Performance ends there.

  THE JOINT WRITES (@004b33e0/@004b34ec) live where the binary calls them:
  the MECH master-perf tail after the gait pass, death-gated -- the idle
  sway onto the EyeJoint, and TRANSLATION <- eyePosition + ROTATION <-
  bodyOrientation onto 'jointeye', the BallTranslation joint the cockpit
  eyepoint rides.  Every write QuantiseEps-gated.

  THE HIT BOUNCE (@004b2980): every non-collision hit shakes the cockpit.
  Direction from the damage force (random horizontal when ~zero), rotated
  into the yaw-only torso frame, per-type priced amount/multiplier*response
  (Explosive alone reads burstCount), clamped 1.3 UPPER only, then the four
  kicks -- impulse, torque (which zeroes .y and negates itself), the fixed
  up-axis vibration, and the vertical mirror.  Fed from the damage hub's
  step 1, BEFORE zone resolution -- an invalid-zone hit still shakes you.

  THE CRUNCH: driving through a crushable prop now kicks the gyro (torque
  0.4 along the contact normal, upward impulse 0.2) -- the 5.3.102 staged
  site, closed.

Resource: the five DamageResponse quads {trans,pitchRoll,yaw,vibration}
appended after the multipliers (record 0x21C, binary-verified layout) --
they were always in the stream; we simply never read them.  The ctor now
zeroes every accumulator (the donor's history records a NaN poison from
exactly that omission), copies the clamp pairs (body doubled), self-points
externalPitchPtr at spare0 until a torso binds it, and REGISTERS the
Performance on the master -- it ticks live, no fault.

Stub census: 19 across 13 files.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-03 16:42:56 -05:00

BT410 5.3.110: the gyroscope lives -- the cockpit's springs, the hit bounce, and the crunch, all wired

2026-08-03 16:42:56 -05:00

BT_L4

BT410 5.3.106: MISSION REVIEW LINKS -- the playback app, the winners circle, and the last Fail() in main

2026-08-03 15:54:31 -05:00

MUNGA

BT410 5.3.62: correction -- the fault address was never in our code

2026-07-29 08:22:15 -05:00

MUNGA_L4

BT410 5.3.106: MISSION REVIEW LINKS -- the playback app, the winners circle, and the last Fail() in main

2026-08-03 15:54:31 -05:00

override

source410: engine COMPLETE (165/165) - link reaches PE emission; deep ledger cut

2026-07-19 11:25:49 -05:00

shim/dpl/vpx

source410: link campaign - entire engine compiles (152/152), first true link,

2026-07-19 08:46:05 -05:00

backdate.py

4.10 reconstruction: BTL4OPT.EXE links clean and BOOTS to the first staged brick

2026-07-19 19:05:53 -05:00

build410.sh

BT410 Phase 5.3.7: weapon view-fire gating + build header-stamp hardening

2026-07-21 22:43:38 -05:00

compile410.sh

source410: THE WHOLE 4.10 TREE COMPILES - 11/11 under the fleet's BC++ 4.52

2026-07-19 07:58:26 -05:00

layout_probe.cpp

source410: THE WHOLE 4.10 TREE COMPILES - 11/11 under the fleet's BC++ 4.52

2026-07-19 07:58:26 -05:00

README.md

BT410 5.3.107: census checkpoint -- 98% covered, and nine "missing" TUs had survived all along

2026-08-03 15:57:27 -05:00

RENDER-ROADMAP.NOTES.md

BT410 5.3.82: the MFD bleed -- mechanism found (uninitialised translation table)

2026-07-29 21:06:22 -05:00

UNRESOLVED-LEDGER.txt

source410: engine COMPLETE (165/165) - link reaches PE emission; deep ledger cut

2026-07-19 11:25:49 -05:00

README.md

source410 — literal reconstruction of the missing BT 4.10 game source

Everything in this directory is RECONSTRUCTED, not recovered. The authentic surviving source lives in CODE/ and is never mixed with this tree. The goal here is an archival-grade recreation of the d:\tesla_bt\ translation units that exist only inside BTL4OPT.EXE (the shipped 4.10 binary), written in the 1995 VWE house style against the 1995 MUNGA/MUNGA_L4 engine headers that DID survive.

Ground rules

Never copy a reconstructed file into CODE/ — the assembled buildable tree (originals + reconstructions) is produced by a script into a build directory, so provenance stays unambiguous file-by-file.
Every .CPP here has a .NOTES.md sidecar carrying the evidence: the binary address map, decomp references, which sibling sources supplied each idiom, and every judgment call with its tier ([T1] decomp-proven … [T4] style guess). The .CPP itself stays clean 1995 style — no modern annotations inside.
Assert line numbers are constraints. The binary's Fail() sites record the original file+line (BTL4APP.CPP:400 etc.); reconstructed files are shaped so those calls land on their recorded lines. A file that can't meet its line constraints yet says so in the sidecar.
Layout mirrors the original tree: BT/ (bt.lib, 36 TUs) and BT_L4/ (btl4.lib, 13 TUs + BTL4.CPP), matching the surviving BT.MAK/BTL4.MAK.

What drives the work

The per-TU manifest: C:\VWE\BT411\reference\BT410_SOURCE_MANIFEST.md (tool tools/manifest410.py; method log phases/phase-03-bt410-source-manifest.md).
The decomp: C:\VWE\BT411\reference\decomp\all\part_*.c (+ section_dump.txt strings).
The port's semantic reconstructions: C:\VWE\BT411\game\reconstructed\ (WinTesla-hosted; each literal file here re-hosts one back onto the 1995 engine APIs).
Style/idiom exemplars: surviving CODE/BT/*.CPP, CODE/RP/RP_L4/*.CPP, CODE/RP/MUNGA*/** (the 1995 engine source itself).

Status (2026-08-03)

The census is 98% covered (897 of 917 binary-attributed functions): manifest410.py's 50-TU missing-source census now splits RECONSTRUCTED / SURVIVES / MISSING — an audit found NINE census TUs (btmssn, btcnsl, btreg, btteam, bttool, gauss, ppc, btl4arnd, btl4mode) had surviving source in CODE/ all along (attribution noise: the binary file-tags covered only part of each TU's functions). Remaining MISSING:

TU	fns	note
`bt/mech3.cpp`	3	the resource STREAM BUILDERS (authoring-side)
`bt/mech4.cpp`	17	master perf / IntegrateMotion / ReplicantPerformance — large parts already re-hosted in `Mech::Simulate` at STAGED seams (see MECH4.NOTES.md)
`bt/gnrator.cpp`	0	GNRATOR.TCP is an 18-line test fragment; both its methods live in POWERSUB.CPP
`bt_l4/btl4galm.cpp`	0	zero attributed functions; header survives

The honest completion metric is the Fail() stub count: 22 stubs across 15 files (down from 26/18 at the start of the gait arc). SEQCTL.CPP and BTL4.CPP are stub-free.

Playable-systems status: the mech WALKS (two-channel clip gait, all 12 mech2 functions, interior+exterior clip sets), LIMPS from real leg damage (two-stage leg death), TURNS IN PLACE by stepping, walks REAL TERRAIN (the gravity-less ground snap), and collides authentically (frame rejection, knockdown stagger, the collision-damage economy, crushable props, rams). MISSION REVIEW links end to end (BTL4PB + L4SPLR + the review/camera launch in main) — runtime test pending a recorded spool. The engine tree gained L4SPLR.CPP (182 TUs).

Next work package — the mech-family, REVISED (round-3 finding, 2026-07-19): the plan to "reconstruct mech.hpp first" was the wrong order. A full read of the port's mech.hpp shows it is a hybrid (1995 skeleton + Recon proxies + port-only members + relocated fields), and substantial regions of the binary's 0x854-byte Mech object remain UNMAPPED — the port declares "the remaining members up to sizeof==0x854" in its mech2-4 slices. A literal MECH.HPP that precedes those TU reconstructions would be fiction. Corrected order:

MECH.HPP is the CAPSTONE, grown incrementally with each mech-family TU reconstruction (mech.cpp → mech2-4 → subsystem TUs), starting as an interface + known-ordered members with explicit reserved[] filler for unmapped regions (sidecar-tracked), tightened as each TU pins its slice.
The dependent headers (mechsub, mechmppr, btl4mppr, emitter+mechweap, btplayer, projtile, missile) ship WITH their TUs against the staged MECH.HPP.
The blocked originals (BTTOOL, GAUSS, PPC, BTREG) and the BTL4APP pilot compile green as those land — BTREG last (it includes the whole game-header world). Offset oracles for every stage: BT411 CLASSMAP.md, decomp-reference.md §3, and the port headers' static_assert-locked members.

Toolchain — IN HAND (2026-07-19)

Borland C++ 4.52, archived at ../../BORLAND/BC45/, chosen by byte-match: the fleet's own CODE/RP/CW32.LIB is identical to 4.52's (and not 4.5's). BCC32/TLINK32/TLIB/MAKE run natively on Win11. The shipped BTL4OPT.EXE recipe is CODE/BT/OPT.MAK (plain bcc32, -DLBE4;DEBUG_LEVEL=0;DEBUG_STREAM=cout, -5 -a4 -ff -k- -V -Jg -x- -RT- + the full -O set, PCH btopt.csm; link -Tpe -ax with c0x32.obj + dpmi32.lib + cw32.lib = Borland PowerPack DPMI32, not Phar Lap TNT). Compile verification of reconstructed TUs is therefore possible file-by-file; the current blocker for full closure is the 1995 engine header gap (vdata.hpp first — only the drifted WinTesla VDATA.h survives, in BT412/engine). Include order for builds: CODE/BT/* over CODE/RP/*, -DNO_PRECOMPILED_HEADERS until the mech-family headers are reconstructed. Remaining gap: TASM32 (JOYSTICK.ASM only).

Link campaign (build410, 2026-07-19)

source410/build410.sh assembles BTL4OPT.EXE: merged-engine mass compile (152/152 green — the ENTIRE surviving engine compiles), BT TUs (11/11), tlib libs (munga 1.25MB / mungal4 with the prebuilt-1995 objs / bt / btl4), then the authentic tlink32 link rooted by a probe main (build scaffold). First true link run: 52 unresolved externals (UNRESOLVED-LEDGER.txt) = the measured remaining gap. Kill-lists: l4gauge.cpp back-date (14 widget statics), the missing-engine-body back-date wave (~24: rotation, player, team, l4app, explode, dropzone, terrain, cultural, subsystm-statics, netclient...), the prebuilt RANDOM.obj fold, and the staged game-TU statics blocks (MECH.CPP et al. — each TU file opens with its binary-evidenced Derivation/SharedData statics and grows into the full body). Link-lib arbitration: SOS = SOSDBXC+SOSMBXC (the 32-bit Borland-flat variants; SOSMW*=16-bit), WATTCP excluded (it belongs to the 16-bit NetNub TSR — the game talks to it via shared memory), filestrm = the RP-era pair (BT-tree pair is post-4.10 drift; override layer).