vwemirror/BT411
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

#113 audit closed FAITHFUL + the turn-rate mechanism found: the missile flight envelope needed no change -- ttl = lifetime + 10.0 (_DAT_004bf5ac byte-read) and kill-plane -1.0 (_DAT_004bf5b0) are the binary's own laws, so the port's burn+10 shape was exact all along; the #84 label 'burn' vs the ctor's 'maxTimeOfFlight' is the same field genuinely double-serving (thrust duration AND the retirement base). The real find: model+0x40 IS the authored per-round turn rate (60/360 deg/s), scaled pi/180 (_DAT_004be8b8) into the thruster -- the binary flies authored agility while the port uses uniform tuned gains [T3]; open-questions' +0x4c candidate corrected to +0x40 and the Sunday item rescoped to wiring the authored rates (the NARC/STREAK 'angry bees'). Ledger nuances recorded: the silent displacement reaper beside the detonating world path; burn-phase lateral zero-stabilization. Ticket #113 comment 1842.

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016bw71WVsccjwW7uKRg4aWD
This commit is contained in:
Joe DiPrima
2026-08-14 12:12:52 -05:00
co-authored by Claude Fable 5
parent c3741d96df
commit 569b8d31b5
1 changed files with 14 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
context/open-questions.md
+14 -7
View File
@@ -1357,13 +1357,20 @@ EXPERT-only; the player+0x260 WRITER has never been read). Settled/confirmed [w
expert-only -> best read: a genuine 4.0->4.10 balance change (his hands-on spans the earlier
machine). Tester-notes line warranted (veteran heat is not a bug). The vet-vs-expert heat
MAGNITUDE coefficient stays open [T4].
- **NARC/STREAK per-type seeker maneuverability (Oracle: the "angry swarm of bees" at high
aspect angles near a maneuvering target)** [T3→T4]: the port's steering gains (4.0 turn /
8.0 loft) are PORT-TUNED constants applied uniformly to every missile family; Oracle's
memory says the maneuverable types behaved differently. Candidate: an authored per-model
turn-rate field in the missile model record (we consume +0x44 maxTimeOfFlight, +0x48
thrust, +0x50 detonationMode — +0x4c is UNREAD). Read +0x4c across the 8 cached missile
models; if it differentiates NARC/STREAK, wire it as the turn gain. Post-Friday.
- **NARC/STREAK per-type maneuverability -- MECHANISM FOUND (#113 audit, 2026-08-14) [T1]:
the authored turn rate is model field +0x40** (values 60/360 deg/s), scaled by
_DAT_004be8b8 = pi/180 into the thruster (@004bf5b4 stack-record build -> @004be7c4
thruster[0x3a], rad/s). The +0x4c candidate hypothesis was WRONG (superseded; +0x4c ->
thruster[0x3c], role unread). The binary flies the authored rates; the port's push
simulator uses uniform PORT-TUNED steering gains (4.0/8.0) [T3] and ignores +0x40.
SUNDAY ITEM: consume model+0x40 as the per-round turn gain (the table already caches the
record; add the field), bench LRM-vs-Streak turn-radius A/B, expect the 'angry bees'.
Same audit, envelope verdict: ttl = lifetime + 10.0 (_DAT_004bf5ac) and kill-plane -1.0
(_DAT_004bf5b0) are BYTE-FAITHFUL in the port -- #113 closed-faithful, no envelope change.
[T3 minor ledger]: the binary also silently retires rounds the constraint resolver
displaces >0.32u (embedded-in-terrain reaper, no boom) beside the detonating
world-collision path; and a thruster-state branch zero-stabilizes lateral terms during
burn (our seeker-loft shape approximates).
- **Gauss carrier confirmed vs content (Oracle: "the Mischief")**: Mischief = lok2 (the exe's
variant-name table: vul1="Mad Dog", lok2="Mischief", mad2="Zanin Neko"), and the Loki
family's L4GAUGE.CFG section authors GAUSS + AmmoBinGAUSS gauge rows — consistent. (A