Files
frameledger/docs/spike-notes.md
T
poli0981andClaude Opus 5.5 24a87159f4 fix: the owner's eight sessions of 2026-10-20 - a x2.52 state, the driver's DLSS word lost at exit, Start directly losing the game Steam starts, two summary windows, display sizes, a bare DLSS line; the Steam note; the two load-flaky tests (beta.27 PR-1) (#330)
The owner ran the installed 0.1.0-beta.26 (sessions 64-71) and asked for the results to be checked,
the two flaky tests fixed, bugs fixed, and a release if there were bugs. Read from a backup copy of
the ledger and the logs (docs/spike-notes/23-owner-runs-2026-10-20.md).

- FgWindow.IsNearWholeMultiplier: a window is a state's only within 10 % of a whole multiplier of two
  or more (FgSlices.Slice.IsActive); FgMixRecord.Parse reads stored rows by the same rule. Silent Hill
  2 under Dynamic MFG listed x2.52 for 12.8 s - windows where the multiplier stepped; it now reads
  x2.0, x3.0, none and 7.36 % not classified.
- NgxDriverState / CaptureSession: the driver is not asked after the game has gone, and CREATED |
  EVALUATE stand once a reading carried them. The last NGX reading, taken after the target exited,
  replaced every in-game one: none of the 14 answered sessions kept the two bits, so DLSS
  (driver-reported) and the NVIDIA App's mode (D63) never showed on an NGX-direct title.
- CaptureOrchestrator: a launch says it ended on its own (Recorded) with the pids it recorded
  (Targets), so a process turned away while it ran - the game Steam starts after Lies of P hands
  itself over - is recorded when it ends; the launch's own process never is.
- SessionSummaryOpener: one window per session; opening it again brings it forward.
- DisplayTally: the sizes are the mode's last sample that saw the window (a game leaving exclusive
  fullscreen closes it first; five sessions stored none).
- DlssText.Line: no line that says only "DLSS".
- Tests: the guard's scan set includes the test host above the harness, which under a full gate
  releases modules while it starts its other classes - ModuleScanFailed (reproduced 1 run in 12 of
  the assembly with coverage; 15 of 15 green after), ProcessUnreadable on 2026-10-19.
  ShmDrainIntegrationTests.InjectAsync asks again on those two reasons only (4 times at most, 250 ms
  apart); the pause case waits for READY; every injection suite waits for the harness's flushed
  "presenting" line instead of 800 ms (tests/Shared/HarnessReady.cs).
- Docs: 03_METRICS (the mix, the driver-reported rung, display sizes), 04_CAPTURE, 06_DATA_MODEL,
  08_UI, 14_TESTING, 18_GPU_VENDOR_APIS, 19_SAFETY (direct starts counted by the crash safety -
  measured, the policy unchanged), LIMITATIONS, guide (troubleshooting, results), spike-notes section
  23, HANDOFF items 20 and 21, CHANGELOG.

Then, on the owner's word about Steam games (Play > Start directly says a Steam game may hand itself to Steam - the notice, the tooltip and Settings (en/vi/ja); why a note rather than a fixed Steam rule (beta.27 PR-1)):

The owner, 2026-10-20: Steam games hand themselves to Steam; a note in the UI, or a fixed setting
that Steam's games always go through the Steam client - the choice left open. The note:

- GamePlayer: PlayResult.SteamGame - the game the agent starts (Start directly, or an App running as
  administrator, or a Steam record with no link) is one Steam's own records name; the notice then
  reads Play_Started_Steam_Format / Play_Elevated_Steam_Format. Store records are read once a press.
- Strings: Play_ToolTip_Direct and Settings_PlayMode_Body say a Steam game may hand itself to Steam
  and the game Steam then starts is recorded; Settings adds that a few will not start outside Steam
  at all. en/vi/ja, ja marked review; Strings.Designer regenerated.
- Why not the fixed rule: three of the five Steam games started directly on 2026-10-20 ran and were
  measured from their first frame, and a Vulkan game is measured only when FrameLedger starts it
  (Everhex Demo) - recorded in 08_UI.
- Docs: 08_UI, guide/08-settings, LIMITATIONS, CHANGELOG.
- Tests: GamePlayerTests (Steam started directly and elevated say it; a loose or GOG game does not).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 10:31:47 +07:00

4.5 KiB

P0 spike notes

P0's named deliverable (15_ROADMAP §P0). Where measured results go, not predictions. (It began empty by design and is now the longest record here.)

Rules:

  • Record what was observed, with the machine, driver version, game and SDK version it was observed on. A result without its context is not reusable.
  • Record failures and dead ends too. "We tried X, it deadlocked, here is why" is worth more than silence, and prevents the next person retrying it.
  • When an entry answers an item in 20_OPEN_QUESTIONS.md, fix the owning doc, delete the question, and note both here.
  • Nothing in P1 starts until the exit criteria at the bottom pass.

How this file is split (2026-10-19, beta.24, owner decision D66)

Each section below lives in its own file under docs/spike-notes/, moved verbatim; code and documents cite them as spike-notes §N, which this table resolves. A new measurement gets the next number, its own file and a row here, written before the run as the sections above it were (the decision table first).

Section What was measured File
§Environment Environment spike-notes/environment.md
§0 Licence checks (no hardware needed — do these first) spike-notes/00-licence-checks.md
§1 Guard (moved to first — 20_OPEN_QUESTIONS §R1) spike-notes/01-guard.md
§2 Vulkan layer passthrough (moved earlier — §R2) spike-notes/02-vulkan-layer.md
§3 Hook viability on hook-harness only spike-notes/03-hook-viability.md
§4 Vendor symbol reality check spike-notes/04-vendor-symbols.md
§5 Proxy swapchains (§H5) spike-notes/05-proxy-swapchains.md
§6 RT detection spike-notes/06-rt-detection.md
§7 First real injection (requires the guard, §1) spike-notes/07-first-real-injection.md
§8 The accuracy question — why this rewrite exists spike-notes/08-accuracy.md
§9 Frame generation spike-notes/09-frame-generation.md
§10 Telemetry layering spike-notes/10-telemetry-layering.md
§11 PresentMon / Tier 2 (§M2, §M6) spike-notes/11-presentmon-tier2.md
§12 The gate's own inputs — §S21 and §S20 (2026-08-04) spike-notes/12-gate-inputs.md
§13 Can the guard go RED against real anti-cheat? (2026-08-04) spike-notes/13-guard-red.md
§Exit criteria Exit criteria spike-notes/exit-criteria.md
§14 The P2 milestone and the FPS-impact run (slots — the owner's runs) spike-notes/14-p2-milestone-fps.md
§15 Unreal Engine versions in shipping executables (2026-09-27, beta.10) spike-notes/15-unreal-versions.md
§16 A game process's own memory, read from outside it (2026-10-03, beta.12, owner decision D43) spike-notes/16-game-memory.md
§17 Unity, Godot and RPG Maker versions in installed games (2026-10-12, beta.19) spike-notes/17-unity-godot-rpgmaker.md
§18 The Ren'Py version in an installed game (2026-10-12, beta.20) spike-notes/18-renpy-version.md
§19 Anti-cheat beside the executable — Wuthering Waves (2026-10-13, beta.21, owner decision D58) spike-notes/19-wuthering-waves.md
§20 The launcher in front of four itch installs is malware (2026-10-13, beta.21, owner decision D57) spike-notes/20-itch-malware.md
§21 Opening pages and switching tabs in the App (2026-10-14, beta.23) spike-notes/21-app-pages-and-tabs.md
§22 The owner's runs of beta.24 and beta.25 on real hardware (2026-10-19) spike-notes/22-owner-runs-2026-10-19.md
§23 The owner's runs of beta.26 on real hardware (2026-10-20) spike-notes/23-owner-runs-2026-10-20.md