* spike: Reflex route D on the harness - the driver's two getters called from an unshipped probe, against a stand-in nvapi64.dll and against the installed driver; a decision table written before the runs, and what they showed (spike-notes §31; D132) No shipped code changes and no game was touched. - tools/fl-probe-reflex: fl_reflex_candidate.h, the call sequence that would move into the Overlay (find nvapi64.dll only if the process already holds it, resolve NvAPI_D3D_GetLatency and NvAPI_D3D_GetSleepStatus by interface id, call them SEH-guarded); --stub against tools/vendor-stubs/stub_nvapi64.cpp (ctest fl_reflex_probe_stub); --real against the installed driver with the probe playing the game's part - it sets latency markers on its own device, in its own process. - docs/spike-notes/31-reflex-route-d-harness.md: nine pre-committed measurements and their results. No fault before initialisation, without markers, or beside a marker-setting thread (38 million reads); a call costs half a microsecond; the Direct3D 12 device the Overlay holds is the object the driver takes; the report's unit is microseconds. The call belongs on the presenting thread once a second, not on the watchdog. The newest frames of a report are not final. Ends in the owner's go or no for one real title. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * docs(spike): §31 in the index, §M14 and §30 point at what the harness spike showed; the probe and its stub in the build document and CLAUDE.md's tools list Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * docs(spike): HANDOFF says the route D spike is done and what a plan must keep from it; the changelog names the probe as a developer's tool Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * fix(probe): the Reflex probe's Measure takes its callable by const reference - a forwarding reference it never forwarded (Qodana native, cppcoreguidelines-missing-std-forward) Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * fix(probe): what SonarCloud reported on the Reflex probe - the counter read through the union member it was initialised with, a guard for an empty measurement, NvU32 printed as what it is, a variable no longer named module; and the note says what a fourth run measured (1.5 us a call, 70 us at worst) Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
6.2 KiB
6.2 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 |
| §24 | The whole gate on .NET 11 RC3 — what the alpha line's SDK asks of the source (2026-10-31, beta.32, D73–D76) | spike-notes/24-dotnet11-probe.md |
| §25 | Xbox app / Microsoft Store (GDK) titles — the layout, the launch chain, the image paths (2026-11-03, beta.33, D77–D82) | spike-notes/25-xbox-gdk.md |
| §26 | DLSS 5 on Hogwarts Legacy, Dynamic frame generation on Phantom Blade Zero, and Streamline 2.12 → 2.14.16 (2026-11-06, beta.34, D83, D84) | spike-notes/26-dlss5-dynamic-streamline.md |
| §27 | Switching to Games, and a language change that lands elsewhere (2026-11-06, beta.34) | spike-notes/27-games-page-2026-11-06.md |
| §28 | The main line on .NET 11's release — the whole gate, and what the analyses read (2026-11-11, beta.37, D94–D96) | spike-notes/28-dotnet11-main.md |
| §29 | C# 15 against the checks — the canary, and where its constructs would go (2026-11-11, beta.37, D96) | spike-notes/29-csharp15-canary.md |
| §30 | Reflex latency per frame — the routes there are, and what each would cost; a reading, nothing run (2026-11-12, beside beta.45, D130; §M14) | spike-notes/30-reflex-latency.md |
| §31 | Reflex route D on the harness — the driver's two getters called from an unshipped probe, against a stand-in module and the installed driver; no game touched (2026-11-13, after beta.46, D132; §M14) | spike-notes/31-reflex-route-d-harness.md |