BT412

Files

T

arcattackandClaude Opus 4.8 1ed8b05160 Radar view-wedge tracks the torso twist (Gitea issue #1 )

The SECTOR radar's view cone read viewHorizontalRotation, wired by the
MapDisplay ctor from the mech's Torso -- but FindSubObject and
GetHorizontalRotation were NULL stubs, so the connection was never created
and the wedge sat at heading 0 regardless of twist.

Reconstructed from the binary:
- FindSubObject (FUN_0041f98c): a subsystem-ROSTER walk (count @+0x124,
  array @+0x128) matching the streamed subsystem name (sub+0xd4) with a
  tolower-strcmp (FUN_004d4b58) -- the 'Torso' sub-object IS the roster
  Torso subsystem.
- GetHorizontalRotation: torso+0x1D8 == Torso::currentTwist (layout-locked),
  via the existing task-#56 bridge BTGetTorsoTwistAddr (Radian is layout-
  identical to Scalar).

Verified live (MadCat, Standard mode Q/E): the wedge tracks the twist in
lockstep (rot 0 -> -2.21 rad), and the semantic test passes -- body turned
away, torso twisted back onto the enemy: reticle green + wedge pointing at
the enemy's blip on the body-fixed scope.  NB the Blackhawk's torso is FIXED
(+/-0.01 deg limits) -- its wedge authentically never moves; test with a
twisting mech.  Diag env: BT_RADAR_LOG.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-17 15:24:52 -05:00

asset-formats.md

Gait: the AUTHENTIC walk lean -- interior/exterior clip sets, level cockpit + leaning mechs (task #59 )

2026-07-13 14:46:22 -05:00

bgf-format.md

KB: full staleness audit + sweep -- 35 verified corrections across 16 topics, 15 new glossary terms

2026-07-11 10:56:51 -05:00

build-and-run.md

Three-trigger keyboard weapon groups: 1=lasers 2=PPCs 3=missiles (task #43 )

2026-07-09 08:31:16 -05:00

cockpit-view.md

Gyro tail + audio (task #66 ): the INSTABILITY MODEL -- mech+0x3F0 reconstructed