mirror of
https://github.com/jkdansereau/goldeneye-pc-port.git
synced 2026-10-23 15:52:42 +02:00
James Dansereau
08865bedeb
Ran the M-152 next-step probe (GE_D288=1 GE_PCDUMP=560-745:5, backgrounded, 25s bare -level_20 boot). Two problems surfaced with the probe itself, not the underlying bug: it fires 116k times in ~1500-2000 frames (the bbox_frac>0.15 threshold catches ordinary near-camera geometry throughout the whole run, not just the reported ~562-741 window), and the target color signature (83,62,44) never appears in the log. No GE_PCDUMP PPM output was produced either, so no visual cross-check was available. Confidence unchanged from M-152; this is a probe-refinement finding, not a root-cause finding. Recorded the concrete next step (frame-gate GE_D288 on num_dls the way GE_D236RM already does) in the D288 entry. Also caught and documented a real tooling gotcha: a backgrounded ge007.x86_64.exe launch from this Bash tool doesn't reliably die to `pkill -f` (process shows as bare `ge007.x86_64` in ps, no .exe suffix) -- a stray instance ran ~90s past its intended capture window before being caught via `taskkill //F //IM ge007.x86_64.exe`. Added to porting-notes.md so the next session uses taskkill from the start. findings-index.csv regen was a no-op (no new Dxx label).