CydandClaude Opus 4.8 ca988db9ed radar: draw the MAP GEOMETRY -- staticEntities was empty on two stacked gates ...

Playtester DOS-binary comparison: our radar showed blips + wedge but NO map
outlines (the DOS reference draws the whole arena).  MapDisplay::DrawStatic
was always a faithful, working drawer of the rtype-18 GaugeImage outlines
(the same records docs/MAPS.html renders) -- it drew nothing because
staticEntityList was empty, from TWO stacked port regressions; fixing either
alone is insufficient:

1. GaugeRenderer::RebuildEntityGrid (per frame) Clear()ed BOTH grids and
   refilled from the DYNAMIC host iterators only -- the 528 static-flagged
   (0x20C) UnscalableTerrain map placements, which carry most arena outlines
   (arenall: 59 static vs 3 dynamic), were structurally excluded, and the
   wipe also destroyed anything the interest feed contributed.
2. The notify feed's static gate was transcribed as
   Terrain::GetClassDerivations() -- but the shipped content has ZERO Terrain
   records (census: 1008x UnscalableTerrain + 789x CulturalIcon, both
   deriving from Entity in our headers), so the predicate was dead code and
   rejected 100% of map geometry.  @0x4e6ef8 was almost certainly
   UnscalableTerrain's derivation (or the shipped machine's MUNGA derived
   UnscalableTerrain from Terrain).  [T3 on which; the corrected gate is
   what the content requires.]

FIX:
  - staticEntities is now PERSISTENT: filled ONCE per mission inside
    RebuildEntityGrid (AllEntityIterator; keep UnscalableTerrain-derived
    entities carrying a rtype-18 GaugeImage -- covers the static walls AND
    the dynamic CulturalIcon props the 2026-07-12 phantom-red-pip fix routed
    here).  Deterministic whether or not the interest feed delivers.
  - Per-frame RebuildEntityGrid now rebuilds only the MOVING grid (Mover
    filter + dead-mech skip unchanged).
  - Lifecycle: cleared + refill-armed at LinkToEntity (the pod process hosts
    many missions); the gate-corrected remove-notify prunes destroyed
    statics; the gate-corrected add-notify is guarded pre-fill so nothing
    double-adds.
  - BT_RADAR_LOG=1 prints '[radar] static grid filled: N'.

Verified live (glass, DEV.EGG): fill reports 326 map entities; structure
outlines now draw on the radar at the correct zoom; blips + sweep wedge
unregressed.  KB: GAUGE_COMPOSITE row 24 + the Phase-4 staticEntities
deferral resolved.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-08-13 07:26:15 -05:00

..

ammobin.cpp

#84: missiles ACCELERATE like the binary -- the pool flew at constant

2026-07-31 10:41:39 -05:00

ammobin.hpp

#84: missiles ACCELERATE like the binary -- the pool flew at constant

2026-07-31 10:41:39 -05:00

audiopresets.cpp

Audio Phase 2 (AUDIO_FIDELITY F1/F2/F13/F14): full-zone soundbank -- key-splits,

2026-07-16 11:04:34 -05:00

btcnsl.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

btdirect.cpp

Camera seat LIVE + Mech::PlayerLinkMessageHandler reconstructed (@0049f624)

2026-07-18 16:10:29 -05:00

btdirect.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

btinput.cpp

EJECT/PANIC wired: Mech::EjectPilot (id 0x19 @0049f854) + the crippled-mech gate

2026-08-02 16:45:54 -05:00

btinput.hpp

EJECT/PANIC wired: Mech::EjectPilot (id 0x19 @0049f854) + the crippled-mech gate

2026-08-02 16:45:54 -05:00

btl4app.cpp

Fix 2 (Gitea #12): gauge tree survives the in-session mech re-stream

2026-07-19 23:30:43 -05:00

btl4app.hpp

gauges: secondary/radar MFD composites live on a dev box (Milestone B)

2026-07-06 10:59:45 -05:00

btl4galm.cpp

#135 FIXED, two defects: (1) the generator lamp special was mis-reconstructed -- the binary @004cc27c is table_0051d070[generatorNumber] (bytes {0x29,0x1A..0x1D}, 1-based A..D, same shape as the condenser special), not an aux-screen placement probe generators never fill; a leaking generator now flashes its own lamp (benched: '[lamp] 0x1a <- 0x37 (FLASHING)' on a GeneratorA leak; was the field-logged 'NO LAMP RESOLVED'). (2) the eternal loop-button flash: Lamp::SetAlertState/SetState drop their panel notify when the edge lands off-page or in the one-frame mask race of a page transition, and the panel value latches the last-asserted flash forever -- Oracle's 'Loop 6 NEVER stopped' with Condenser6 SET/CLEARED balanced 3/3 in his log (the alarm manager was right; the lamp was stale). The skipped notify is now remembered and delivered at the lamp's next in-mode frame. KB: decomp-reference gains the 0x51d070 table + the stale-flash gotcha.

2026-08-11 17:08:48 -05:00

btl4galm.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

btl4gau2.cpp

#118: the eject slot graphic returns -- vtbl+0x58 is DrawBitMapOpaque [T0]

2026-08-03 23:56:53 -05:00

btl4gau2.hpp

Gauges: trigger-config joystick is LIVE -- @004c6ee0 is LinkToEntity, not SetColor

2026-07-21 08:49:58 -05:00

btl4gau3.cpp

#81 follow-ups: peer warp must not stomp the POV vortex; panel draw probe; mech3 ghost symbols

2026-07-30 10:10:29 -05:00

btl4gau3.hpp

gauge-complete P4g: MessageBoard reconstructed + registered -> LAST parse-skip cleared (0 unregistered gauges)

2026-07-07 21:39:47 -05:00

btl4gaug.cpp

#142 crouch: duckState is a THREE-state posture -- the strip is an animation

2026-08-07 23:35:37 -05:00

btl4gaug.hpp

#118: the eject slot graphic lands -- BitMapInverseWipeScalar reconstructed

2026-08-03 17:53:33 -05:00

btl4grnd.cpp

radar: draw the MAP GEOMETRY -- staticEntities was empty on two stacked gates

2026-08-13 07:26:15 -05:00

btl4grnd.hpp

Gitea #48 ROOT-CAUSED + FIXED: MFD "stray blocks / misplaced lamps" = uninitialized translation-table entries leaking pixels into other displays' bit-planes

2026-07-25 17:20:19 -05:00

btl4mppr.cpp

#118: the eject option comes alive -- per-frame arm chain closed (FUN_004a9b5c+0x10)

2026-08-03 13:53:09 -05:00

btl4mppr.hpp

#118: the PANIC BUTTON ejects -- keypad-bank routing + the 0x17/0x19 id bug

2026-08-03 17:31:16 -05:00

btl4mssn.cpp

Cockpit: authentic eyepoint + canopy lattice render (task #55)

2026-07-11 06:46:54 -05:00

btl4mssn.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

btl4pb.cpp

#118: the eject option comes alive -- per-frame arm chain closed (FUN_004a9b5c+0x10)

2026-08-03 13:53:09 -05:00

btl4pb.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

btl4rdr.cpp

Radar view-wedge tracks the torso twist (Gitea issue #1)

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

btl4rdr.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

btl4vid.cpp

#156 the mission start/end fade RECONSTRUCTED: POVStartEndRenderable was an inert stub (rounds hard-cut) -- the binary's 5-phase fog machine (ctor @00454394, Execute @0045447c; constants byte-read @0x454740-50: flash 0.1s, fades 1.0s, plane floors 0.01/0.05) now runs at the renderer frame head keyed on the local player's SimulationState (3 MissionStarting -> white flash + 1.0s fade-in from white; 4 MissionEnding -> 1.0s fade-to-black, planes closing to the floors, re-arm). Drives the live fog pipeline (currentFogNear/Far + FOGCOLOR, which the frame Clear also samples -- the fade owns sky/void too) and re-reads the STYLE members per frame exactly as the binary re-reads live view fog (mid-fade searchlight swaps track). Armed by the now-real ctor in btl4vid.cpp (house pattern: inert object, module machine). Bench fade_bench.sh: 40s relay-clocked round, both nodes PASS armed + phases 1/2/3/4 in order with the end edge on simState=4. Rider: the [rio] STALL detector now keys on REPLY drought instead of request age (which the 50ms poll refreshed forever -- the detector could never fire; #160 telemetry).

2026-08-11 18:54:12 -05:00

btl4vid.hpp

Searchlight reconstruction -- the pod's night kit, both halves

2026-08-05 19:44:23 -05:00

btplayer.cpp

#162 K/D chain fixed at the authority model, once and for all: death tail master-gated (the 1995 sender one-shot restored -- the binary has NO receiver dedup, +0x290 never set [T1 byte-scan]); the #81 latch-clear misattribution corrected (binary site = DropZoneReply tail); steam eggs stamp the host's advancedDamage mission-wide (penalty was silently off for every steam match); #38 badge/patch ride the lobby (bd/pt keys). Bench: kd_bench.sh, five hard invariants, 4/4 deaths+costs+credits, zero dupes

2026-08-11 00:21:46 -05:00

btplayer.hpp

scoring: the +1000 START grant -- BT's MissionStarting override was never ported

2026-08-07 11:43:54 -05:00

btscnrl.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

btstubs.cpp

#156 the mission start/end fade RECONSTRUCTED: POVStartEndRenderable was an inert stub (rounds hard-cut) -- the binary's 5-phase fog machine (ctor @00454394, Execute @0045447c; constants byte-read @0x454740-50: flash 0.1s, fades 1.0s, plane floors 0.01/0.05) now runs at the renderer frame head keyed on the local player's SimulationState (3 MissionStarting -> white flash + 1.0s fade-in from white; 4 MissionEnding -> 1.0s fade-to-black, planes closing to the floors, re-arm). Drives the live fog pipeline (currentFogNear/Far + FOGCOLOR, which the frame Clear also samples -- the fade owns sky/void too) and re-reads the STYLE members per frame exactly as the binary re-reads live view fog (mid-fade searchlight swaps track). Armed by the now-real ctor in btl4vid.cpp (house pattern: inert object, module machine). Bench fade_bench.sh: 40s relay-clocked round, both nodes PASS armed + phases 1/2/3/4 in order with the end edge on simState=4. Rider: the [rio] STALL detector now keys on REPLY drought instead of request age (which the 50ms poll refreshed forever -- the detector could never fire; #160 telemetry).

2026-08-11 18:54:12 -05:00

btvisgnd.cpp

Boresight parallax FIXED + the #4/#5 verdict instrumentation (Gitea #16, #4, #5)

2026-07-20 14:51:54 -05:00

CLASSMAP.md

#168 settled from the binary: projectiles are TIME-capped, never range-capped -- plain shell 5.0s (@4bddec), missile burnTime+10s + y<-1 kill-plane (@4bef78), WeaponRange is fire-control only (FireWeapon @4bcc60 has no range gate), so AFC50 hits at 2000+u are authentic. Two port defects killed: the invented len*1.3+60 flight cap (replaced by the authentic clocks) and the stale-point auto-hit (unguided contact tested the fire-time pick, so a locked AC could not miss a moving target -- the pool now tracks the live target). KB: decomp-reference gains the flight/expiry section, CLASSMAP's swapped authoritative/ghost Performance labels corrected (ReplicantInstance=4 [T0]), missile.cpp's misdecoded @4bf594 constant pool re-annotated, Missile proximity fuse 4.0u recorded. Bench: proj_ttl_bench.sh (probe fizzles 5.012/12.012 vs caps 5.0/12.0; 86 field launches, 0 early, 0 phantoms). Rides along: the #163 BTSteamNet_ShutdownAll header decl that missed d3f4b9a.

2026-08-11 04:39:37 -05:00

dmgtable.cpp

#124 twist-sign VERIFIED correct (live missile bench) + the rig to do it

2026-08-04 15:49:14 -05:00

dmgtable.hpp

#92: map the direct-fire hit->zone path; the FOOT is pickable over only 3% of a mech's height

2026-08-01 19:47:30 -05:00

dpl2d.cpp

K/D scoreboard ROOT-CAUSED (#45) + respawn latch fix (#57) + plate stage ops (#58)

2026-07-25 01:50:07 -05:00

dpl2d.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

emitter.cpp

#165 does not reproduce -- the destroyed-weapon fire gate HOLDS on the exact field path: bench (xfire_bench.sh) kills ERPPC_1+ERSLaser_1 via the cascade's own ForceCriticalFailure writer under held autofire -- ERSLaser_1 9 FIRED pre-kill, 0 post, 4213 refusals (destroyed=1), surviving ERMLaser fires on. Rajel's field read explained: the refusal tail recomputes output voltage every tick (binary-authentic), so a destroyed weapon's recharge dial keeps CYCLING under its X while the surviving torso lasers put the beams peers saw. Rider: the [emitter] FIRED receipt now NAMES its weapon under BT_DMG_LOG (the #110 nit) so the next field session can settle it by name.

2026-08-11 16:13:39 -05:00

emitter.hpp

#164 hardened to impossibility + the config theory tested NULL: the beam draw now requires the weapon to actually BE in Firing(0) -- the 1995 visual rode ContinueDischarge's per-frame re-messaging which stopped the instant the state left 0, so state-gated drawing is the faithful semantics and makes ANY beamFlag bookkeeping stick invisible by construction (Conn Man's screenshot: red laser, leg-level origin, dials green = a live weapon with a stuck flag). Receipts stand armed for the field: [beam] STUCK-ON (armed flag outside Firing) and DESTROYED-BUT-ON, each naming the weapon. The config-mid-discharge theory was tested deterministically (BT_CFGTEST waits for state 0 and dispatches ConfigureMappables to that weapon): the dispatch landed with beamFlag=1 and NO stick followed -- the handler does not disturb the discharge; theory retired with receipts. Upstream cause remains open; one field recurrence now names it.

2026-08-12 02:14:34 -05:00

gnrator.cpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

gnrator.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

gyro.cpp

#83: the COLLISION DIVERT -- type-0 damage prices as internal rattle, never armor

2026-07-30 17:04:24 -05:00

gyro.hpp

#55 steps 0/1/2/4: the 1995 DEATH pass restored, the arg gate made real, and 5 subsystems the respawn sweep never reached

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

heat.cpp

#128 terrain-ram instant coolant leak FIXED at the eligibility tag: GUID 0x50e590 is the AGGREGATE BANK's node (0xBBE), not the HeatSink base family -- the family-wide reading made every coolant-bearing subsystem (myomers, condensers, reservoirs...) rattle-eligible, so one over-floor ram sub-hit sprang an instant leak (field: Michael's 3 rams all 'Myomers condition 2 SET' -- a subsystem 1995 can never select). Authentic set {HeatSinkBank .30, Gyroscope .35, Torso .25}; scrapes remain free via the byte-anchored 0.5-pt floor (the 30k-lines/night [crashdmg] spam now sampled). Audit: docs/RAM_LEAK_AUDIT_20260811.md. Bench ram_bench.sh: 20 rattles, zero ineligible strikes

2026-08-11 02:33:14 -05:00

heat.hpp

#119: heatLoad filter restored to the POD's 28 Hz sample cadence

2026-08-02 20:05:06 -05:00

heatfamily_reslice.cpp

#119: heatLoad filter restored to the POD's 28 Hz sample cadence

2026-08-02 20:05:06 -05:00

heatfamily_reslice.hpp

Coolant Flush end-to-end (Gitea #7): InjectCoolant id-4 handler + drain + FLUSH.PFX cloud + 'H' key

2026-07-19 15:15:44 -05:00

hud.cpp

control mode: Basic re-centre used the STICKY held-button cell -- and the elevation-limit swap was never ported

2026-08-08 10:36:36 -05:00

hud.hpp

control mode: Basic re-centre used the STICKY held-button cell -- and the elevation-limit swap was never ported

2026-08-08 10:36:36 -05:00

matchlog.cpp

MP match forensics: per-peer matchlog + relay auto-upload + matchcheck

2026-07-22 13:22:10 -05:00

matchlog.hpp

MP match forensics: per-peer matchlog + relay auto-upload + matchcheck

2026-07-22 13:22:10 -05:00

mech2.cpp

#52 the peer STANDING-LOCK: case 0's fallthrough was intercepted

2026-08-07 00:50:54 -05:00

mech3.cpp

#82 ROOT FIX: reconstruct the crash SELF-DAMAGE -- wall-grinding now hurts,

2026-07-30 16:18:28 -05:00

mech4.cpp

#174 root-caused + fixed with a negative control: the binary's ONLY re-descend protection is the burst loop's zone-state guard wrapping the WHOLE per-burst application (@0x4a0446, part_012.c:14661 -- crit roll, TakeDamage, score tally, destroyed-flag; RecurseSegmentTable/SendSubsystemDamage have NO internal re-entry protection: no used-marking, no top gate). The port had narrowed the guard to the crit roll -- continued fire re-saturated dead zones (cascade re-fired: night-16 zone 18 x7, each pass re-pushing crit allotment = the ram 'crits worsened with each collision'), and hits on wreckage kept SCORING (binary awards zero -- a quiet farm-the-wreck exploit). Fix: guard restored to binary scope. Bench: BT_ZONE_HAMMER hook (4Hz explicit-zone self-damage) -- fixed build 1 cascade/10 hits/0 post-saturation applications; NEGATIVE CONTROL (fix stashed): 147 cascades. 147 -> 1. Gotcha 31: guard-scope narrowing -- diff the BRACE SCOPE when transcribing decomp ifs; and prove a bench detects the bug before trusting its pass

2026-08-13 02:42:07 -05:00

mech.cpp

#174 root-caused + fixed with a negative control: the binary's ONLY re-descend protection is the burst loop's zone-state guard wrapping the WHOLE per-burst application (@0x4a0446, part_012.c:14661 -- crit roll, TakeDamage, score tally, destroyed-flag; RecurseSegmentTable/SendSubsystemDamage have NO internal re-entry protection: no used-marking, no top gate). The port had narrowed the guard to the crit roll -- continued fire re-saturated dead zones (cascade re-fired: night-16 zone 18 x7, each pass re-pushing crit allotment = the ram 'crits worsened with each collision'), and hits on wreckage kept SCORING (binary awards zero -- a quiet farm-the-wreck exploit). Fix: guard restored to binary scope. Bench: BT_ZONE_HAMMER hook (4Hz explicit-zone self-damage) -- fixed build 1 cascade/10 hits/0 post-saturation applications; NEGATIVE CONTROL (fix stashed): 147 cascades. 147 -> 1. Gotcha 31: guard-scope narrowing -- diff the BRACE SCOPE when transcribing decomp ifs; and prove a bench detects the bug before trusting its pass

2026-08-13 02:42:07 -05:00

mech.hpp

#142 crouch: duckState is a THREE-state posture -- the strip is an animation

2026-08-07 23:35:37 -05:00

mechdmg.cpp

#108 peer-side WRECK receipt: make ghosts countable

2026-08-07 07:48:04 -05:00

mechdmg.hpp

#52 SKATE detector (ungated field forensic) -- negative-verified; local repro eludes

2026-08-05 12:41:55 -05:00

mechmppr.cpp

#152: the real hole -- glass/RIO rigs had NO torso-centre control; wire pod button 0x42

2026-08-09 17:26:27 -05:00

mechmppr.hpp

Gitea #6: secondary MFD Damage/Critical/Heat cycling -- reconstruct the

2026-07-19 16:28:38 -05:00

mechrecon.hpp

#67 part 2, ROOT-CAUSED AND FIXED: 1995 latent uninitialized fields, exposed by the port's allocator

2026-07-27 07:42:37 -05:00

mechsub.cpp

#165 ROOT-CAUSED after three failed fixes -- the binary keeps ONE destroyed cell per subsystem (+0x40: fire gate, dial X, wire header, every writer) and the port split it into FOUR stores; the everyday CRIT-LOTTERY kill (MechWeapon::TakeDamage) bypassed the reconstructed base and wrote only the X store, so X'd weapons kept firing while every prior fix aimed at a gate that was never broken (the 4,213-refusal bench drove BT_KILL_SUBSYS, which writes all cells -- it validated readers, not writers). FIX: MechWeapon::TakeDamage chains to MechSubsystem::TakeDamage (@0x4ac0bc semantics); the port-authored FSM-from-damage tail is DELETED (it parked partial-crit weapons at level 1 -- no FSM case, the silent freeze, and with beamFlag armed the 883 hanging beam: #164's upstream writer, caught red-handed by berserker's 20x STUCK-ON receipts); the phantom uninitialized simulationState int is ctor-initialized and kept in lockstep at every destroyed write; always-on [crit] DESTROYED receipt makes crit kills field-visible. BT_CRIT_SUBSYS bench hook drives the REAL writer path; weaponx_bench PASS: kill phase 0 FIRED post / 5,664 refusals / X+gate agree, partial phase keeps firing. Gotcha 30; #174 filed (cascade re-descend)

2026-08-13 00:35:33 -05:00

mechsub.hpp

EJECT/PANIC wired: Mech::EjectPilot (id 0x19 @0049f854) + the crippled-mech gate

2026-08-02 16:45:54 -05:00

mechtech.cpp

#119 leak-voice stutter SETTLED: authentic -- the wooHoo latch is authored OFF

2026-08-04 09:44:42 -05:00

mechtech.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

mechweap.cpp

#165 ROOT-CAUSED after three failed fixes -- the binary keeps ONE destroyed cell per subsystem (+0x40: fire gate, dial X, wire header, every writer) and the port split it into FOUR stores; the everyday CRIT-LOTTERY kill (MechWeapon::TakeDamage) bypassed the reconstructed base and wrote only the X store, so X'd weapons kept firing while every prior fix aimed at a gate that was never broken (the 4,213-refusal bench drove BT_KILL_SUBSYS, which writes all cells -- it validated readers, not writers). FIX: MechWeapon::TakeDamage chains to MechSubsystem::TakeDamage (@0x4ac0bc semantics); the port-authored FSM-from-damage tail is DELETED (it parked partial-crit weapons at level 1 -- no FSM case, the silent freeze, and with beamFlag armed the 883 hanging beam: #164's upstream writer, caught red-handed by berserker's 20x STUCK-ON receipts); the phantom uninitialized simulationState int is ctor-initialized and kept in lockstep at every destroyed write; always-on [crit] DESTROYED receipt makes crit kills field-visible. BT_CRIT_SUBSYS bench hook drives the REAL writer path; weaponx_bench PASS: kill phase 0 FIRED post / 5,664 refusals / X+gate agree, partial phase keeps firing. Gotcha 30; #174 filed (cascade re-descend)

2026-08-13 00:35:33 -05:00

mechweap.hpp

EJECT/PANIC wired: Mech::EjectPilot (id 0x19 @0049f854) + the crippled-mech gate

2026-08-02 16:45:54 -05:00

messmgr.cpp

#95: REVERT the salvo-damage hack; deliver the cluster the way the binary does

2026-08-01 04:42:15 -05:00

messmgr.hpp

#95: REVERT the salvo-damage hack; deliver the cluster the way the binary does

2026-08-01 04:42:15 -05:00

mislanch.cpp

weapon SPEC AUDIT: the fleet's authored numbers in one pass -- missile delivery fully reconciled

2026-08-02 13:31:36 -05:00

mislanch.hpp

#84: the replicant salvo now HOMES AT THE LIVE TARGET -- the stale-point double detonation is gone

2026-08-02 02:29:58 -05:00

missile.cpp

#168 settled from the binary: projectiles are TIME-capped, never range-capped -- plain shell 5.0s (@4bddec), missile burnTime+10s + y<-1 kill-plane (@4bef78), WeaponRange is fire-control only (FireWeapon @4bcc60 has no range gate), so AFC50 hits at 2000+u are authentic. Two port defects killed: the invented len*1.3+60 flight cap (replaced by the authentic clocks) and the stale-point auto-hit (unguided contact tested the fire-time pick, so a locked AC could not miss a moving target -- the pool now tracks the live target). KB: decomp-reference gains the flight/expiry section, CLASSMAP's swapped authoritative/ghost Performance labels corrected (ReplicantInstance=4 [T0]), missile.cpp's misdecoded @4bf594 constant pool re-annotated, Missile proximity fuse 4.0u recorded. Bench: proj_ttl_bench.sh (probe fizzles 5.012/12.012 vs caps 5.0/12.0; 86 field launches, 0 early, 0 phantoms). Rides along: the #163 BTSteamNet_ShutdownAll header decl that missed d3f4b9a.

2026-08-11 04:39:37 -05:00

missile.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

misthrst.cpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

misthrst.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

myomers.cpp

#137 FIXED: restore the binary Reset's +0x58c re-seed -- the respawn freeze was a

2026-08-09 16:19:36 -05:00

myomers.hpp

myomer system COMPLETE -- the 'WAVE 6 mover cutover' was a phantom built on

2026-07-31 09:17:31 -05:00

pilot.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

powersub.cpp

#135 FIXED, two defects: (1) the generator lamp special was mis-reconstructed -- the binary @004cc27c is table_0051d070[generatorNumber] (bytes {0x29,0x1A..0x1D}, 1-based A..D, same shape as the condenser special), not an aux-screen placement probe generators never fill; a leaking generator now flashes its own lamp (benched: '[lamp] 0x1a <- 0x37 (FLASHING)' on a GeneratorA leak; was the field-logged 'NO LAMP RESOLVED'). (2) the eternal loop-button flash: Lamp::SetAlertState/SetState drop their panel notify when the edge lands off-page or in the one-frame mask race of a page transition, and the panel value latches the last-asserted flash forever -- Oracle's 'Loop 6 NEVER stopped' with Condenser6 SET/CLEARED balanced 3/3 in his log (the alarm manager was right; the lamp was stale). The skipped notify is now remembered and delivered at the lamp's next in-mode frame. KB: decomp-reference gains the 0x51d070 table + the stale-flash gotcha.

2026-08-11 17:08:48 -05:00

powersub.hpp

#118 alarm dig complete: the TechStatus bit model -- MarkGeneratorOut bridge removed

2026-08-04 03:18:50 -05:00

projtile.cpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

projtile.hpp

Initial commit: bt411 -- standalone Windows BattleTech (Tesla 4.10 port)

2026-07-05 21:03:40 -05:00

projweap.cpp

#166 mechanism pinned + two input-layer fixes: Oracle's LRM jam = the ammo bin PARKED at Ejecting(3) with rounds aboard (his log: 'NoAmmo (gate2): rounds=18 binState=3', twice; eject tap cleared it exactly as the handler predicts). The MFD/HUD 'desync' is honest: the full green circle is the RECHARGE dial (untouched by the gate2 pin) and the btejam lamp keys only on weaponAlarm 5 (binary @004c9a38) -- state-7 pins show neither, authentically. The parking producer needs an unpaired eject PRESS, which pod hardware cannot make but our glass mouse layer could: (1) WM_CAPTURECHANGED now releases a held panel button when capture is stolen (Steam overlay/popups ate the WM_LBUTTONUP), (2) a new press releases any still-held previous button instead of orphaning it. Forensics: every EJECT message now logs data/bin/ejectState/binState/rounds always-on (ejects are rare) -- Friday names the producer if it recurs. Smoke: BT_EJECTTEST replays the full press/hold/dump receipt chain incl. the authentic mid-eject gate2 pin.

2026-08-11 16:45:12 -05:00

projweap.hpp

#118: the eject slot graphic lands -- BitMapInverseWipeScalar reconstructed

2026-08-03 17:53:33 -05:00

searchlight.cpp

Searchlight reconstruction -- the pod's night kit, both halves

2026-08-05 19:44:23 -05:00

searchlight.hpp

Searchlight reconstruction -- the pod's night kit, both halves

2026-08-05 19:44:23 -05:00

seeker.cpp

#55 steps 0/1/2/4: the 1995 DEATH pass restored, the arg gate made real, and 5 subsystems the respawn sweep never reached

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

seeker.hpp

#55 steps 0/1/2/4: the 1995 DEATH pass restored, the arg gate made real, and 5 subsystems the respawn sweep never reached

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

sensor.cpp

Input-audit cause #1: revive the Avionics power bank + add the unhandled-message trace

2026-07-25 10:05:57 -05:00

sensor.hpp

Input-audit cause #1: revive the Avionics power bank + add the unhandled-message trace

2026-07-25 10:05:57 -05:00

seqctl.cpp

Audio Phase 4d (AUDIO_FIDELITY F5): footStep is the authored CONTACT LEVEL

2026-07-16 14:16:14 -05:00

thermalsight.cpp

Searchlight + ThermalSight ToggleLamp WIRED (#61) -- and a swapped table attribution ROOT-CAUSED, retracting a false "1995 latent bug"

2026-07-25 10:46:59 -05:00

thermalsight.hpp

Searchlight + ThermalSight ToggleLamp WIRED (#61) -- and a swapped table attribution ROOT-CAUSED, retracting a false "1995 latent bug"

2026-07-25 10:46:59 -05:00

torso.cpp

control mode: REPRODUCE the "centering fought my control" fight, and prove the fix in Sauron's config

2026-08-08 13:59:39 -05:00

torso.hpp

control mode: Basic re-centre used the STICKY held-button cell -- and the elevation-limit swap was never ported

2026-08-08 10:36:36 -05:00