BT411

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

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

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

#111 FIXED: the peer-visible warp sphere is RETIRED -- observers see the un-wreck model swap, exactly what the pods showed. The blue bubble on another player's dying/respawning mech was never binary behavior: the authentic effect is the POV-ONLY translocation (POVTranslocateRenderable, the dying pilot's own eye-centred collapse/reveal -- btl4vid.cpp's own banner says 'the authentic effect is POV only', twice), and the world-anchored peer sphere was a deliberate July-10 port extension (160b78e) that the field read as a wrong effect ('should just be the big boom from other POV' -- Lynx, night 9, confirmed in follow-up). The death-side collapse was already local-gated (GetMissionPlayer, verified back through build 693), so retiring the extension removes the LAST peer-visible warp; the corpse-vs-dropzone replication-order question the field receipts could not settle becomes moot. Un-wreck edge keeps everything else: pfx cleanup (#129 ), model rebuild, the ungated [respawn] receipt (text updated: 'un-wrecked', no '+ warp'). BTStartWarpEffect kept caller-less as slot-guard documentation. Night-16 field receipts audited on the way in: all 24+ un-wreck edges are clean mode 9->1, no death-state jitter.

2026-08-14 00:01:39 -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

#21 closed at the true root + 'arcade shipped a brick' RETRACTED (era witnesses 6-0): _DAT_004ba830 is a DOUBLE 1.0, not float 0.0 -- the entire brick claim was a constant-width misread (dword read of a qword; the low half of 1.0's mantissa is zeros). Binary truth [T1 raw disasm @004ba738]: overcharge CLAMPS to exactly 1.0f, the ==1.0 Loaded test passes next tick, the weapon fires the stored charge at normal top-gear damage (divisor is the recommended gear). Fix: clamp corrected to 1.0f; the rescue scaffolding REMOVED (it patched our own misread -- 38 'rescues' were 38 events the machine silently clamped); gauge-side zeroing inherits the fix, which is almost certainly #21 's ORIGINAL field symptom (dark recharge arc + dark ready-dot = the dial reading our zeroed ratio while the rescue kept the weapon firing). seek21 bench PASS: 65 switches / 16 wraps / 9 overcharges -> fires through all, 13 post-overcharge gauge probes FULL, zero rescue prints. Docs: field guide section 2 rewritten as settled-by-testimony (credit to the group), decomp-reference block retracted with extracted constants, drift audit energy lane -> FAITHFUL, ZERO deviations. The witnesses' 'nah, that didn't happen' was worth eight bytes read at full width

2026-08-13 17:59:24 -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

cadence census item 2: gyro spring-damper stepped on the pod's 28Hz clock (gotcha 32) -- the cockpit bounce runs the machine's timescale again. The binary steps IntegrateEyeJoint @004b2ec0 / IntegrateBody @004b30ec once per pod frame with PER-TICK math (no-dt position step, damping overwrite carrying last-tick state); at ~60fps the springs stepped 2.14x too often. Fix: 28Hz per-instance accumulator (heat.cpp #119 map pattern), 1/28 slices, remainder carried, catch-up capped 28; integrator BODIES byte-untouched; BT_GYRO_SPRING_HZ override (=0 restores render cadence, proven behaviorally identical to the old code: control run reproduces the BEFORE curve exactly, 0.0471 @ +0.240s / period 1.435s). Impulse bench (new BT_GYRO_KICK one-shot deterministic hit through the authentic GyroApplyDamage fan-out; [gtrace] gains wall-ms): BEFORE eye trough -0.0452 @ +0.24s, overshoot 23%, period ~1.43s, settle +3.44s; AFTER trough -0.0537 @ +0.29s, overshoot 7%, period ~2.4s, settle +3.49s; 97 integrator steps / 3.49s ~ 28Hz -- the clock provably ticks. Shape verdict: both single-overshoot damped responses; every delta is the per-tick semantics at dt=1/28 (per-SECOND damping ~e^c is cadence-invariant, hence equal settle). Nothing beyond the timescale.

2026-08-13 19:54:14 -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

#113 follow-on: missiles fly their AUTHORED agility -- the turn-rate cap is wired (model+0x40 deg/s, the field the #113 audit identified: pi/180-scaled into the binary thruster @004be7c4[0x3a], _DAT_004be8b8 byte-verified [T1]). The thrust table now reads tail[0] (it always fetched and dropped it); mislanch passes the rate via a salvo-scoped latch (BTPushSetTurnRate -- deliberately NOT a BTPushProjectile signature change: six call sites + three externs under /FORCE is the silent-AV churn class), master AND replicant mirror so peers see the same arcs; the steering keeps the field-verified exponential blend [T3] and CAPS this frame's heading change at turnDps*dt -- below the cap the old behavior is bit-identical, above it the round slews at the authored rate. BT_TURN_AUTH=0 restores uncapped; [projturn] CAP receipts under BT_PROJ_LOG. A/B bench (2-node standoff, scratchpad/night17/turn_bench.sh): AUTH runs 43/69 CAP receipts, ALL at 60dps (the blend wants <=~220 so 360 rounds are authentically unconstrained; LRMs slew ~3.6x slower during corrections -- the era 'sluggish 60 deg/sec' look); OFF runs ZERO CAP lines (negative control); impacts 25/9 vs 7/4 -- no accuracy collapse. Data bonus: mad2's 'LRM15'-labeled racks resolve 360dps (Narc-profile rounds, the guide's authored-mislabeling lore confirmed by receipts); madcat's are true 60dps LRMs.

2026-08-14 12:43:24 -05:00

mech.cpp

PPC hit scrambles the secondary displays (phase-14, all three work items)

2026-08-14 13:12:40 -05:00

mech.hpp

#83 FIXED: the incoming-missile alarm sounds again -- the July F7 driver was wired into DEAD CODE. Root cause: the alarm feed (cc2b109) lived in Missile::MoveAndCollide, but the world-entity Missile is a BLOCKED TRANSCRIPTION (2007 Entity-base mismatch) that never flies; live flight is the BTPushProjectile simulator in mech4.cpp -- so IncomingLock/DistanceToMissile stayed 0/FLT_MAX in every field build (solo AND MP) while the doc header said F7 fixed. Fix: the feed moves to the push simulator's per-frame update -- salvo LEAD only (the port's cluster = the binary's ONE Missile per trigger, @004bf5b4 ctor-registration into target+0x418 read by the target tick @004a9b5c: lock=1, dist=|missile-mech| entity positions); mirror leads on peer nodes report identically (mislanch resolves the live target by replicated ID), which is what puts the alarm in the VICTIM's cockpit -- inbound missiles are always mirrors there. Bridge hardened: BTIsRegisteredMech class check (the binary's 0x50bdb4 check) + the port's latched-death predicate 2||9 (@0049fb54). New: [incoming] receipt (BT_INCOMING_LOG, edges + 1Hz held) and BT_DESIGNATE=enemy (bench designator: production designation slots stamped with the nearest live mech on no-mech frames only -- standoff locks the boresight pick can't hold). Transcription block kept in missile.cpp with an INERT banner so the trap can't re-bite. Bench (2-node standoff LRM duel, 700-800u): 54/55 lock edges per node, dist closing 792->87 over ~2.2s, beeper STARTs with LIVE authored tempo (10 far -> 435 close, the 100..800->600..10 map) -- on replicant mirrors, i.e. the MP case. Era witness: Oracle identified [1:74] IncomingAlarm01 n58 on the soundboard same day ('sped up in the pods').

2026-08-13 22:25:38 -05:00

mechdmg.cpp

#111 FIXED: the peer-visible warp sphere is RETIRED -- observers see the un-wreck model swap, exactly what the pods showed. The blue bubble on another player's dying/respawning mech was never binary behavior: the authentic effect is the POV-ONLY translocation (POVTranslocateRenderable, the dying pilot's own eye-centred collapse/reveal -- btl4vid.cpp's own banner says 'the authentic effect is POV only', twice), and the world-anchored peer sphere was a deliberate July-10 port extension (160b78e) that the field read as a wrong effect ('should just be the big boom from other POV' -- Lynx, night 9, confirmed in follow-up). The death-side collapse was already local-gated (GetMissionPlayer, verified back through build 693), so retiring the extension removes the LAST peer-visible warp; the corpse-vs-dropzone replication-order question the field receipts could not settle becomes moot. Un-wreck edge keeps everything else: pfx cleanup (#129 ), model rebuild, the ungated [respawn] receipt (text updated: 'un-wrecked', no '+ warp'). BTStartWarpEffect kept caller-less as slot-guard documentation. Night-16 field receipts audited on the way in: all 24+ un-wreck edges are clean mode 9->1, no death-state jitter.

2026-08-14 00:01:39 -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

#179 FIXED: the look-state machine never committed the SPAWN state -- the Nova showed its rear laser's range pips in the forward view until the first look toggle (Oracle, night 17, same-evening report). The mapper commits eyepoint/enables/pip-group-mask on lookState EDGES only, and both state cells constructed equal (LookNone), so the first tick saw no edge; the reticle's group mask kept its construction bits. Fix: ctor seeds lookState = -1 (impossible), making the first tick an edge into LookNone that stamps the forward view at spawn. The firing half was never wrong -- the weapon ctor is binary-faithful (viewFireEnable = !rearFiring @004b99a8 [T1]); only the pips lied. Verified: pre-fix logs show ZERO [mppr] look-state commits without a look press (retroactive proof of the bug); the fixed build prints exactly one 'look state -> 0' at spawn with zero inputs (25s solo smoke). Rides Friday.

2026-08-13 23:32:30 -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

#113 follow-on: missiles fly their AUTHORED agility -- the turn-rate cap is wired (model+0x40 deg/s, the field the #113 audit identified: pi/180-scaled into the binary thruster @004be7c4[0x3a], _DAT_004be8b8 byte-verified [T1]). The thrust table now reads tail[0] (it always fetched and dropped it); mislanch passes the rate via a salvo-scoped latch (BTPushSetTurnRate -- deliberately NOT a BTPushProjectile signature change: six call sites + three externs under /FORCE is the silent-AV churn class), master AND replicant mirror so peers see the same arcs; the steering keeps the field-verified exponential blend [T3] and CAPS this frame's heading change at turnDps*dt -- below the cap the old behavior is bit-identical, above it the round slews at the authored rate. BT_TURN_AUTH=0 restores uncapped; [projturn] CAP receipts under BT_PROJ_LOG. A/B bench (2-node standoff, scratchpad/night17/turn_bench.sh): AUTH runs 43/69 CAP receipts, ALL at 60dps (the blend wants <=~220 so 360 rounds are authentically unconstrained; LRMs slew ~3.6x slower during corrections -- the era 'sluggish 60 deg/sec' look); OFF runs ZERO CAP lines (negative control); impacts 25/9 vs 7/4 -- no accuracy collapse. Data bonus: mad2's 'LRM15'-labeled racks resolve 360dps (Narc-profile rounds, the guide's authored-mislabeling lore confirmed by receipts); madcat's are true 60dps LRMs.

2026-08-14 12:43:24 -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

#83 FIXED: the incoming-missile alarm sounds again -- the July F7 driver was wired into DEAD CODE. Root cause: the alarm feed (cc2b109) lived in Missile::MoveAndCollide, but the world-entity Missile is a BLOCKED TRANSCRIPTION (2007 Entity-base mismatch) that never flies; live flight is the BTPushProjectile simulator in mech4.cpp -- so IncomingLock/DistanceToMissile stayed 0/FLT_MAX in every field build (solo AND MP) while the doc header said F7 fixed. Fix: the feed moves to the push simulator's per-frame update -- salvo LEAD only (the port's cluster = the binary's ONE Missile per trigger, @004bf5b4 ctor-registration into target+0x418 read by the target tick @004a9b5c: lock=1, dist=|missile-mech| entity positions); mirror leads on peer nodes report identically (mislanch resolves the live target by replicated ID), which is what puts the alarm in the VICTIM's cockpit -- inbound missiles are always mirrors there. Bridge hardened: BTIsRegisteredMech class check (the binary's 0x50bdb4 check) + the port's latched-death predicate 2||9 (@0049fb54). New: [incoming] receipt (BT_INCOMING_LOG, edges + 1Hz held) and BT_DESIGNATE=enemy (bench designator: production designation slots stamped with the nearest live mech on no-mech frames only -- standoff locks the boresight pick can't hold). Transcription block kept in missile.cpp with an INERT banner so the trap can't re-bite. Bench (2-node standoff LRM duel, 700-800u): 54/55 lock edges per node, dist closing 792->87 over ~2.2s, beeper STARTs with LIVE authored tempo (10 far -> 435 close, the 100..800->600..10 map) -- on replicant mirrors, i.e. the MP case. Era witness: Oracle identified [1:74] IncomingAlarm01 n58 on the soundboard same day ('sped up in the pods').

2026-08-13 22:25:38 -05:00

missile.hpp

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

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

misthrst.cpp

velocity/dt audit: DRAG WAS THE GOVERNOR -- the binary applies -0.001*v^2 every frame, burn AND coast (@004bef78 + thruster @004be474, ctor precomputes terminal sqrt(T/COD) into +0x348 as the seeker lead base; authored COD 0.001 byte-read from BTL4.RES type-15 srm/lrm/strk/nrk). The port omitted it: LRM hit 3030 u/s at burnout vs the machine's 547.7 terminal (5.5x), 3912u downrange at t=5s vs 2108u -- a major slice of the 'missiles reach anything' field feel. Pool now integrates speed += (accel - 0.001*v^2)*dt. The dt MODEL itself verified FAITHFUL (Mover zeroes accel per frame + integrates x dt in seconds, matched line-for-line to T0 MOVER.cpp -- the 28Hz myomer idiom does NOT apply; open-question closed). AC cosmetic tracer TOF constants landed (2.0f @0x4bc678, 1/9.8 x87 EXTENDED @0x4bc67c, muzzleHeight term via ResolveLaunchVelocity deferred-first-use). Stale banners swept (misthrst @004be474 recovered; projweap #168 flight-contact banner gone). KB: decomp-reference Mover-gravity fix + flight-model bullet, coast gravity = 6.5 not 9.8. Drift audit: SSVELOCITY/DT + SSRANGE AUTHENTICITY (manual cross-check: PPC/AFC100 MATCH, SRM 450-vs-800 authoring drift; rangefinder ladder NOT miscalibrated -- fixed 0-1200 + authored pips both sides; -100m range-bias state unimplemented, parked). Build clean

2026-08-13 14:58:04 -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

velocity/dt audit: DRAG WAS THE GOVERNOR -- the binary applies -0.001*v^2 every frame, burn AND coast (@004bef78 + thruster @004be474, ctor precomputes terminal sqrt(T/COD) into +0x348 as the seeker lead base; authored COD 0.001 byte-read from BTL4.RES type-15 srm/lrm/strk/nrk). The port omitted it: LRM hit 3030 u/s at burnout vs the machine's 547.7 terminal (5.5x), 3912u downrange at t=5s vs 2108u -- a major slice of the 'missiles reach anything' field feel. Pool now integrates speed += (accel - 0.001*v^2)*dt. The dt MODEL itself verified FAITHFUL (Mover zeroes accel per frame + integrates x dt in seconds, matched line-for-line to T0 MOVER.cpp -- the 28Hz myomer idiom does NOT apply; open-question closed). AC cosmetic tracer TOF constants landed (2.0f @0x4bc678, 1/9.8 x87 EXTENDED @0x4bc67c, muzzleHeight term via ResolveLaunchVelocity deferred-first-use). Stale banners swept (misthrst @004be474 recovered; projweap #168 flight-contact banner gone). KB: decomp-reference Mover-gravity fix + flight-model bullet, coast gravity = 6.5 not 9.8. Drift audit: SSVELOCITY/DT + SSRANGE AUTHENTICITY (manual cross-check: PPC/AFC100 MATCH, SRM 450-vs-800 authoring drift; rangefinder ladder NOT miscalibrated -- fixed 0-1200 + authored pips both sides; -100m range-bias state unimplemented, parked). Build clean

2026-08-13 14:58:04 -05:00

projweap.hpp

velocity/dt audit: DRAG WAS THE GOVERNOR -- the binary applies -0.001*v^2 every frame, burn AND coast (@004bef78 + thruster @004be474, ctor precomputes terminal sqrt(T/COD) into +0x348 as the seeker lead base; authored COD 0.001 byte-read from BTL4.RES type-15 srm/lrm/strk/nrk). The port omitted it: LRM hit 3030 u/s at burnout vs the machine's 547.7 terminal (5.5x), 3912u downrange at t=5s vs 2108u -- a major slice of the 'missiles reach anything' field feel. Pool now integrates speed += (accel - 0.001*v^2)*dt. The dt MODEL itself verified FAITHFUL (Mover zeroes accel per frame + integrates x dt in seconds, matched line-for-line to T0 MOVER.cpp -- the 28Hz myomer idiom does NOT apply; open-question closed). AC cosmetic tracer TOF constants landed (2.0f @0x4bc678, 1/9.8 x87 EXTENDED @0x4bc67c, muzzleHeight term via ResolveLaunchVelocity deferred-first-use). Stale banners swept (misthrst @004be474 recovered; projweap #168 flight-contact banner gone). KB: decomp-reference Mover-gravity fix + flight-model bullet, coast gravity = 6.5 not 9.8. Drift audit: SSVELOCITY/DT + SSRANGE AUTHENTICITY (manual cross-check: PPC/AFC100 MATCH, SRM 450-vs-800 authoring drift; rangefinder ladder NOT miscalibrated -- fixed 0-1200 + authored pips both sides; -100m range-bias state unimplemented, parked). Build clean

2026-08-13 14:58:04 -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