Joe DiPrimaandClaude Fable 5 1282063cc7 #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. ...

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

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

..

fwd

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

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

glass

#169 rider: shorten the roster build-gate tag to [WRONG BUILD] -- the '-- WILL NOT LAUNCH' tail clipped at the 536px row edge (caught in the layout preview render)

2026-08-11 15:55:23 -05:00

original

SeekVoltageGraph: full reconstruction -- the eng-page POWER graph + top-box eraser (Gitea #11)

2026-07-19 20:27:39 -05:00

reconstructed

#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

btl4main.cpp

#163 round-end freeze + hang-on-exit FIXED: bare ExitProcess ran DLL detach with live Steam threads (no SteamAPI_Shutdown existed anywhere) and intermittently deadlocked -- the dead process's fullscreen frame squatted on screen while its menu child hung in SteamAPI_Init against the wedged sibling (field-captured, ZEUS 22:12:38). Ordered exit everywhere: flush forensics, BTSteamNet_ShutdownAll BEFORE the child spawns, hide our windows, TerminateProcess (detach skipped, deadlock structurally unreachable). Audit ledger: docs/MISSION_END_AUDIT_20260811.md (also yields #156's fade root cause). Bench: relaunch_bench.sh -- old pids dead, menu children clean

2026-08-11 01:58:23 -05:00