CydandClaude Opus 4.8 b14b37b13d document BT_RIO_PROTRUDE in the generated environ.ini ...

The button-protrusion dial shipped with no player-facing documentation -- it
lived only in the source comment and the KB, so a tester who found the buttons
too long (or wanted them longer) had no way to discover the knob.

Adds a block to the self-documenting default environ.ini, at the end of the
cockpit section beside the other display-shaping options (BT_MFD_SCALE,
BT_RADAR_SCALE, BT_RADAR_POS, BT_COCKPIT_TINT): what it does, that it is a
LONGER bar rather than a wider button (press target and imagery unchanged),
that it touches only the red MFD and yellow map buttons, the 10 default, 0 for
the original look, the 1-200 range, and the gotcha that it takes a NUMBER --
'on' parses to 0 and turns it off.

Verified by generating a fresh environ.ini from this build and reading the
block back as a player would see it.  The loader has no allowlist and refuses
only BT_JOYCONFIG, so the key applies from the file; a real env var still wins
over it, per the file's own contract.

NB the default is only written when environ.ini is ABSENT (and only beside
BTL4.RES), so existing installs keep their file and will not gain this text --
the handout/KB remain the channel for testers who already have one.

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

2026-08-14 13:50:20 -05:00

..

fwd

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

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

glass

#170 root-caused + fixed: the #163 SteamAPI_Shutdown was the crash -- at round end every peer's close events are ALWAYS in flight, and Shutdown tears client state down while steamclient's own service thread dispatches them (the field stack: a steamclient worker calling literal NULL, zero btl4 frames, 7 hits / 3 machines / one module-relative stack). BTSteamNet_ShutdownAll is now a QUIESCE: steamActive gated FIRST, linger closes ('round over' not timeouts), one SNS drain, 60ms grace, NO SteamAPI_Shutdown -- and every exit path dies via TerminateProcess (menu-quit no longer returns through the CRT; it uses BTOrderlyDie like everything else, so the 883 detach deadlock stays dead too). Status callback guarded for the dying window. Crash filter now names foreign DLL frames (module+offset via VirtualQuery/GetModuleFileName) so the next foreign-thread crash arrives pre-symbolized. Exit contract: steam-networking.md

2026-08-12 23:23: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

#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

btl4main.cpp

document BT_RIO_PROTRUDE in the generated environ.ini

2026-08-14 13:50:20 -05:00