144 KiB
HANDOFF — read this first, then stop reading it
The one file a new session opens to pick up P0 work (corrected 2026-10-04). It carries sequencing, decisions
and traps. It deliberately carries no status.
The rule this file lives under
This file must never restate what another document already states. Four documents disagreeing about the gate's composition is what §S23-4 and §S23-5 were raised for, and
rules-validatenow fails a fifth copy in the shipped data. A handoff that summarises status becomes the next stale copy within a day — that has already happened three times here (#45's note, then #46–#52;15_ROADMAP's status block;spike-notes§8 correcting a stale claim and going stale in the same file).So: status lives where it lives. Read it there.
Question File What is unresolved and what does it block? docs/20_OPEN_QUESTIONS.md— §S24 is the index; the ✅/◐/❓/🔴/🅓 markers are load-bearingWhat was measured, on what machine? docs/spike-notes.mdWhich P0 item is where? docs/15_ROADMAP.mdWhat landed? CHANGELOG.mdWhat does the software promise users? README.md,legal/DISCLAIMER.md— both carry accuracy blocksAnd verify a status claim against the code before planning on it. Four times now those files have asserted in the present tense something that had been closed, or was never true. The 2026-08-05 session found the ledger stale across seven PRs and two documents contradicting themselves inside one section.
How this file is split (2026-10-19, beta.24, owner decision D66)
Everything this file held is still here or one link away, moved verbatim: what to do next and the open
owner-only items stay below; the history of every train, the passed owner-only items and the traps moved to
docs/handoff/. Code and documents cite the old sections by name — each name resolves here:
| Cited as | Now in |
|---|---|
§Where P0 actually stands, queue items 1–6 (§2b, "item 3" …) |
handoff/history/p0-queue-1-6.md |
queue item 7 (7a–7c), §Separable, §M5 |
handoff/history/p0-queue-7-m5.md |
§P2 (D1–D10) |
handoff/history/p2.md |
§P3 (D11–D17) |
handoff/history/p3.md |
§P4 |
handoff/history/p4.md |
§beta.3 |
handoff/history/0.1.0-beta.3.md |
§beta.4 |
handoff/history/0.1.0-beta.4.md |
§beta.5 |
handoff/history/0.1.0-beta.5.md |
§beta.6 |
handoff/history/0.1.0-beta.6.md |
§beta.7 |
handoff/history/0.1.0-beta.7.md |
§beta.8 |
handoff/history/0.1.0-beta.8.md |
§beta.9 |
handoff/history/0.1.0-beta.9.md |
§beta.10 |
handoff/history/0.1.0-beta.10.md |
§beta.11 |
handoff/history/0.1.0-beta.11.md |
§beta.12 |
handoff/history/0.1.0-beta.12.md |
§beta.13 |
handoff/history/0.1.0-beta.13.md |
§beta.14 |
handoff/history/0.1.0-beta.14.md |
§beta.15 |
handoff/history/0.1.0-beta.15.md |
§beta.16 |
handoff/history/0.1.0-beta.16.md |
§beta.17 |
handoff/history/0.1.0-beta.17.md |
§beta.18 |
handoff/history/0.1.0-beta.18.md |
§beta.19 |
handoff/history/0.1.0-beta.19.md |
§beta.20 |
handoff/history/0.1.0-beta.20.md |
§beta.21 |
handoff/history/0.1.0-beta.21.md |
§beta.22 |
handoff/history/0.1.0-beta.22.md |
§beta.23 |
handoff/history/0.1.0-beta.23.md |
§beta.24 |
handoff/history/0.1.0-beta.24.md |
§beta.25 |
handoff/history/0.1.0-beta.25.md |
§beta.26 |
handoff/history/0.1.0-beta.26.md |
§beta.27 |
handoff/history/0.1.0-beta.27.md |
§beta.28 |
handoff/history/0.1.0-beta.28.md |
§beta.29 |
handoff/history/0.1.0-beta.29.md |
§beta.30 |
handoff/history/0.1.0-beta.30.md |
§beta.31 |
handoff/history/0.1.0-beta.31.md |
§beta.32 |
handoff/history/0.1.0-beta.32.md |
§beta.33 |
handoff/history/0.1.0-beta.33.md |
§beta.34 |
handoff/history/0.1.0-beta.34.md |
§beta.35 |
handoff/history/0.1.0-beta.35.md |
§beta.36 |
handoff/history/0.1.0-beta.36.md |
§beta.37 |
handoff/history/0.1.0-beta.37.md |
§beta.38, §NEXT (the owner's request of 2026-11-11, the four trains) |
handoff/history/0.1.0-beta.38.md |
§beta.39, train B's plan as approved (its §NEXT) |
handoff/history/0.1.0-beta.39.md |
§beta.40, what the owner's first sessions with it showed, train B's traps |
handoff/history/0.1.0-beta.40.md |
§beta.41, what the owner's sessions on beta.40 and beta.41 showed, the plan of 2026-11-12 (D119–D122) |
handoff/history/0.1.0-beta.41.md |
§beta.42, what the owner's seven sessions on beta.42 showed (D121 answered, the guard's lost launches), beta.43's design as planned |
handoff/history/0.1.0-beta.42.md |
§beta.43, what the owner's nine sessions on beta.43 showed, session by session (item 41), the traps of that train |
handoff/history/0.1.0-beta.43.md |
§beta.44, what the owner's eight sessions on beta.44 showed, session by session (item 42), this release's facts, the traps of that train |
handoff/history/0.1.0-beta.44.md |
§beta.45, what the owner's seven sessions on beta.45 showed, session by session (item 43), that release's facts and SonarCloud's gate on its commit, the traps of that train |
handoff/history/0.1.0-beta.45.md |
§beta.46, what the owner's five sessions on beta.46 showed (item 44), the design of the train that followed as the plan's review left it (§The train after 0.1.0-beta.46), that release's facts, the traps of that train |
handoff/history/0.1.0-beta.46.md |
§beta.47, what that release decided beyond D136–D141, what item 44's last part showed, that release's facts, the traps of that train, its NEXT as the owner's sessions of 2026-11-14 changed it |
handoff/history/0.1.0-beta.47.md |
§beta.48, what that release decided beyond D142–D147, that release's facts, the traps of that train, its NEXT and its "Left open" as item 46 changed them |
handoff/history/0.1.0-beta.48.md |
§beta.49, what that release decided beyond D148–D151, that release's facts, the traps of that train, its NEXT and its "Left open" as item 47 and D152–D154 changed them |
handoff/history/0.1.0-beta.49.md |
§Owner-only, an open item |
§Owner-only below |
§Owner-only, a passed item (3, 12, 14–19, 38, 39) |
handoff/owner-only-passed.md |
§Traps, §Two corrections carried forward |
handoff/traps.md |
Dnn |
§Decisions index below |
START HERE — 2026-11-15, 0.1.0-beta.50: what a session was played with — controllers and input, read from outside the game, and built without a controller
Status is docs/changelog/0.1.0-beta.50.md; this is what no other file carries. On 2026-11-14 the owner asked
for nine things about controllers: whether a game supports them, on the game's page; which interfaces and
libraries; the share of a session played with a controller and with the keyboard; connections and drops; the
battery state that lasted longest; all of it stored and charted; changes between makers and each one's share; Xbox
controllers and the DualSense first; and whatever rounds it out. Nine answers given while planning made the
train (D155–D163, 21_INPUT_DEVICES §The owner's request and decisions): #464 (the arithmetic), #466 (schema
0024 and the .partial file's chunk 11), #467 (the reader), #468 (the Agent, the switch, Privacy Policy 2.22
and Disclaimer 2.18, Tier 2's definition), #469 (what a store lists, the input libraries, the game's page),
#470 (the session's summary, the charts, Trend, Compare, the export, the guide's page), and this release — which
also carries D152 and D154 from [Unreleased]. beta.49's own section, its traps, its release facts and its
"Left open" are handoff/history/0.1.0-beta.49.md.
The one thing to know: nothing here has met a controller
The developer has no controller, and the owner chose to build without a probe run first (D157). So:
- Checked against a real Windows, with no controller connected:
Win32InputBackendTests(the registration is accepted, the window drains, the reader reports "no controller"); the shipped Agent in a scratch data folder (tools/agent-cost.ps1 -Keep) storedinput_observed_ms29 826 of a 30.9 s session,input_sourcerawinput+xinput+lastinput, theinput.classseries and the reader's counters, and stored nothing with the option off or the terms not accepted; the Agent's cost per second of session was inside the run-to-run noise (2.06 % of a core without, 1.54 % with —20_OPEN_QUESTIONS§M17). - Checked against the owner's own file: the Steam app's
appinfo.vdfon the developer PC parsed to 3 581 records — 1 284 full, 440 partial, 1 857 with no entry. - Checked against bytes and sessions written by hand, and against nothing else: every DualSense report layout, XInput's states and battery words, a background program being given a controller's reports at all, Steam's virtual pad and the fold that makes one controller of two, the battery arithmetic, the marks, every share the App shows, and the reader's cost with a controller connected.
LIMITATIONS.md, the accuracy statement, the guide's page and the release's notes all say so. Item 48 is where
it meets the owner's Xbox controller and DualSense.
What this release decided, beyond D155–D163
- Only Xbox-compatible controllers (through XInput) and the DualSense (through its own reports) are read for
use. Any other controller is listed with its connections and is never "in use": the reader parses no other
report, and
LIMITATIONS.mdsays so. Adding one is a parser inDomain/Inputand bytes to test it with. - A DualSense's transport decides how its report is read, not the report's length: Windows pads the short
Bluetooth report to the device's longest, so
DualSenseReport.TryReadtakes the transport. - "Both at once" is a class of its own, in the table, the bar and the series. Trend's Controller share and Keyboard and mouse share are the two exclusive classes; neither includes "both".
- A mark is made from the series: a controller's
input.dev.N.activegoing from no value to a value is a connection; a battery "fell to low" where its level crossed XInput's low, or 10 %, downwards. The row'sconnectsdecides whether the first rise was the session's start. Sixty marks a chart at most. - Steam's
appinfo.vdfis read in format 41 only; another format is refused with the reason, and the game's page says N/A. InputTerms.MinimumPrivacyVersionis2.22and is compared as "at least": a later Privacy Policy does not stop the reading, and the next change to what is read raises the number in the same pull request.- No chart colour was added: the four classes use roles the palette has. Under a Windows contrast theme two
of them share a colour;
ACCESSIBILITY.md§Known limitations says what tells them apart. ShareBaris the base ofFgMixBarandInputShareBar.
Traps this train left
- A stack of pull requests that are squash-merged: when the lower one merges, GitHub deletes its branch and
retargets the upper one to
main, which then conflicts with itself. Checkgit diff origin/main <the lower branch's last tip>is empty, thengit merge -S -s ours origin/mainon the upper branch, and merge that up the stack. Look atgh pr viewbefore pushing to a lower branch: a push to a branch GitHub deleted re-creates it (it happened once here, and the branch was deleted again). - An edit script that is run twice must change nothing the second time. Two of this train's were not: the
guide's settings page listed Controllers and input twice (#468; fixed in #469) and
CLAUDE.md's layout said the input types twice (#468; fixed in this pull request). - A picture of a window from a test does not show its charts: ScottPlot's control does not draw through a
VisualBrush. Save each plot withPlot.SavePng. The picture is how two legends that covered their charts were found; the test is not in the tree. MarkdownRendererTestscounts the embedded documents: a new guide page is one more.plot.Add.Scatter([..], [..])does not compile — two overloads fit a collection expression; name the arrays.- A test cannot call
ChartPalette.For: it needs the App's resources. Parse the palette's XAML, asChartMathTestsdoes. - FluentAssertions'
OnlyContainfails on an empty collection — which is what the real backend returns on a PC with no controller. - A stored session of the test ledger with frames takes its own sensor blobs now (
SessionWithFramesAsync'ssensors), with their ownt_ms. GetLastInputInfo's time is not onEnvironment.TickCount's clock once the PC has slept: five hours apart on the developer PC after a sleep of five hours. The reader never compares the two; a test of #467 did, passed on every runner (they do not sleep) and failed the local gate before this release — fixed here (21_INPUT_DEVICES§What is read). The time actually played, next on the roadmap, must not make the same assumption.- Auto-merge does not wait for Qodana: it is advisory. #470 merged with one notice of Qodana's on
main(a parameter used only for its null check) — a notice counts against the gate of zero, and the script that read the local inspection's SARIF skipped notices. Fixed in this pull request, and the script counts them now. With auto-merge on, read Qodana's report before the required checks finish, or enable auto-merge after it. dotnet format --verify-no-changesthrough a pipe that counts lines says nothing when it fails — print its exit code. #470's first push carried a naming violation in a test fixture that way;checkand the first rehearsal (run 43646963371) caught it, and the second rehearsal is of the fixed tree.
NEXT
- The owner runs item 48 and says check; a copy of the ledger and the Agent's log are read. What it shows
comes first: a route that failed is said in
LIMITATIONS.md, a layout that is wrong is a parser fix with the owner's bytes as its test, and the accuracy statement's sentence about controllers is the owner's to reword once they have been read. - Then the order the owner set on 2026-11-14:
15_ROADMAP.md§After the controller train. It is not repeated here. Its first item uses what this train stores.
Left open by this session
This release's own facts — the tag's run, the digests, the delta, what SonarCloud and Qodana said of the released commit — are not in any file yet: the release is cut after this text. Record them in the next pull request.Recorded 2026-11-15: 0.1.0-beta.50 was released 2026-11-14T23:41:15Z (06:41 on 2026-11-15 in the owner's time zone) from the signed tag on5764d21(#471), by run 43652686348 — green at the first attempt, one run for the one tag push. Eight assets; the seven digests ofSHA256SUMS.txtequal the ones GitHub computed, and the portable package hashed here equals its line; the five native libraries in it carryFL_BUILD_ID v0.1.0-beta.50, none of them-dirty, and both entry points are there. The delta from beta.49 is 3 099 231 bytes beside a full package of 111 085 471 — "Delta processed 0452 files. 0026 patched, 0426 unchanged". The wiki was published by run 43654502311 (31 pages, the new Controllers and input among them). The tag's message reads0.1.0-beta.50, the bare version again. Three rehearsals on the release branch, and the third is of the released tree: run 43646963371 at9c69a32failed in the quality gate on a naming violation in a test fixture of #470; run 43648289839 and run 43649328136 were cancelled as the tree moved (the test of the last-input time; Qodana's notice); run 43650415247 atd6e4685passed, andmainat5764d21is that tree (a delta of 3 112 641 bytes, the same file counts)../build.ps1 checkran green on the developer PC at6dadd05; the two commits after it were inspected (ReSharper's InspectCode, no problem of any severity) and the App's suite run again. The owner's%LOCALAPPDATA%\FrameLedger\ruleshashed the same before and after. SonarCloud analysed5764d21: the quality gate passed. Qodana's two reports, CodeQL andcheckare green on that commit. On the way: Qodana's managed report on #470 was red with one notice when auto-merge merged it (fixed in #471, §Traps); SonarCloud passed #467 (81.4 % of new code covered) and #468 (83.6 %). One date is two dates: the changelog, the README and this file say 2026-11-15, the owner's day; GitHub shows the release on 2026-11-14 (UTC), and the legal texts in the installer are stamped 2026-11-14, the dayrelease.ymlreads from UTC. Nothing reads either; a train that ends before 07:00 in the owner's time zone will show it again.- The reader's cost with a controller connected is not measured (
20_OPEN_QUESTIONS§M17 f). With none it is inside the noise. - A game run as administrator under an Agent that is not has not been tried: Windows may not report input into it. Item 48 (j).
- Only Steam is read for what a store lists. GOG, Epic, the Xbox app and itch read N/A.
- The new block was looked at as pictures, in the dark and the light theme, not used by hand; its rendering under a contrast theme was reasoned from the palette, not looked at.
- The Japanese strings are unreviewed, as every
jastring is; this train added about a hundred. - A session that was read while its game was never in front shows its controllers and no share — by design; whether that reads well is the owner's to say.
- Carried from beta.49, unchanged (its history file has each in full): the two long install batches of
beta.46; Valor Mortis's crash at 51 s and Black Myth: Wukong's fault at exit; what item 41 left unexercised;
item 40 (d), items 36 (d) and 37; (c) and (h) of item 43;
docs/LIST_GAME_TESTED.mdis as of 2026-11-06;LIMITATIONS.mdand the accuracy statement on the processor's, memory's and motherboard's sensors are the owner's to reword; the alpha line rests (D98).
Owner-only: item 48; one session each of Valor Mortis and Black Myth: Wukong with hooking off; what item 41 left unexercised; item 40 (d).
Owner-only — no PR can close these
The items that passed — 3, 12, 14–19, and 38 and 39 on 2026-11-12 — moved verbatim to handoff/owner-only-passed.md (the first eight on 2026-10-19, D66); the numbers are kept, and a number is never reused.
-
§S23-2 — branch protection.
Rules / validateis not a required status check onmain, so the gate that makes the anti-cheat blocklist un-removable is advisory. Second-order problem:rules-publish.ymlfilters on four paths for bothpushandpull_request, so requiring the context as-is blocks every PR touching none of them, forever. Land the skip-shim (droppaths:, short-circuit inside the job) first; the setting is the owner's. -
Real-title verification runs for the upscaler/FG/RT work, against each game's own settings menu.
Live as of 2026-09-03: theRun twice, 2026-09-03 (P4) and 2026-09-04 (P1); done. What is still owed here is the quality preset on a title that chainsslGetNewFrameTokenproducer's table — Cyberpunk 2077 off / ×2 / ×4 and Hell Is Us DLSS + FG ×4, one launch each, readingpresents/tokensoff theFG counts:line against §S31's rows P1–P4.sl::DLSSOptions— Alan Wake 2 is the candidate — and the DLSS-G identity on a title wherekFeatureDLSS_Gis evaluated, if one exists. -
§H7's confirmation against the overlays actually resident on the dev machine. The compare-and-restore path is proven against a fixture (ctest
fl_unhook_inline); §H7 still says the six real overlays are "worth doing once the Overlay has real hooks", and it has them since P1. One capture with each overlay active; the result is aspike-notesrow. -
Re-ratify §S18 blocker 3 and §S27's basis once P2's PR-C/PR-F make the Agent the shipped injecting entry point (§P2, decision D4). The PRs restate both entries; whether the restatement stands is the owner's.
-
D33's first real use (beta.9).Done by 2026-09-27, read from a copy of the owner's ledger: three normal hooked sessions of GIRLS' FRONTLINE 2 under the exception (NetEase Yidun) on 2026-09-26 and 09-27, the longest 3 h 9 min; thejareview below is still owed. (The item as written:) Turn the option on; GIRLS' FRONTLINE 2 should be listed eligible (NetEase Yidun,NEP2.dll, three sessions); make the exception, turn hooking on and play one session: hooked, marked Hooked · exception, not stopped by the 30 s re-scan or by the Overlay whenNEP2.dllloads. Aniimo should read not eligible with itsNEPKernel.sys; the option off makes the next session Tier 2 with the exception kept. And thejatext ofSafety_Exception_*, which ships as English until a reviewer signs. -
beta.10 on real hardware. (a) The display mode: one DXGI game taken through exclusive full-screen → borderless → windowed in one session — the summary's shares, the Sessions column, the Trend's three share metrics — with a note of what the game's own menu called each mode. (b) The admin mode: turn it on → the disclosure → the UAC prompt → Settings says Running elevated; decline it → the administrator prompt was declined; sign out and in with the logon task → the prompt waits on the taskbar and one Agent results; start a game from FrameLedger while elevated → Task Manager's Elevated column says No; a game that runs as administrator → hooked; the CPU temperature with PawnIO (closes §M10 if it reads). (c) The Unreal Engine version on each Unreal game's page. (d) The Legal Gate shows Privacy 2.5 and Disclaimer 2.8 once. (e) The
jatext ofSafety_AdminMode_*, English until reviewed. (f)docs/LIST_GAME_TESTED.md— reviewed and approved by the owner before it was committed (D35, 2026-09-27); keep it current as games are run. -
beta.11 on real hardware. (a) GIRLS' FRONTLINE 2: the option on → Eligible → Make exception… (the disclosure
ac-exception-dialog/2, with its Trial paragraph) → hooking on → two sessions: the card says trial: 0 of 2, then 1 of 2, then Exception in force since … alone. (b) The library at your window's width, and the list; Refresh after installing a game, and with the USB drive unplugged (Not installed, the drive named). (c) Delete all sessions on a game's page and in Settings ▸ Data. (d) Sessions at a glance and the Trend with a second unit. (e) The Legal Gate shows the Disclaimer 2.9 and the EULA 1.4 once. (f) Thejatext ofSafety_Exception_Trial(English until reviewed) and the App strings markedreview. -
beta.12 on real hardware. (a) The game's memory: one hooked game and one that is not (hooking off, or a blocked game), each beside Task Manager's Details tab at the same moment — the summary's VRAM (this game) against Dedicated GPU memory, RAM (this game) against Memory (private working set); the Dashboard's live line; the Sessions columns, the Trend's memory metrics and the Sensors charts. (b) The Legal Gate shows the EULA 1.5, the Disclaimer 2.10 and the Privacy Policy 2.6 once, rendered, with the GPL as your licence, needing no acceptance. (c) Help ▸ User guide, Help ▸ About (its three tabs; Open the licences folder in the installed copy), and View on GitHub opening the
v0.1.0-beta.12tag. (d) Thejastrings markedreview(the memory labels, the About window, the first-start summary). (e)docs/LIST_GAME_TESTED.mdis as of beta.10: refresh it from a copy of the ledger, with the games' memory figures, and approve it before it is committed (D35). -
beta.13 on real hardware. (a) The first delta: update an installed
0.1.0-beta.12through Help ▸ Check for updates — the download is a fraction of the full ~107 MB, and the App comes back as beta.13; if it downloaded the full package instead, say so (Velopack falls back silently). (b) On this PC: with an Easy Anti-Cheat service running for any game, start a hook-enabled game — the notice says the anti-cheat is running on this PC, not in the game. (c) Two graphics cards, if a machine with them is at hand: the Sensors chart's GPU figures are the game's card. (d) Thejareview of the new safety strings, with the others still marked for it. -
beta.14 on real hardware. (a) The update from beta.13: choose Beta in Settings ▸ Updates, Help ▸ Check for updates, then Restart to update with no game running; Settings then reads Automatic (Beta). The
velopack:lines inui-*.logsay what was downloaded — a delta of about 2 MB; say so if it was the full package. (b) Explorer ▸ Properties ▸ Details ofFrameLedger.exeandFrameLedger.Agent.exename FrameLedger and the copyright; Task Manager lists FrameLedger Agent. (c) The wheel on every page, the dialogs and the summary window; over a chart the wheel scrolls the page and Ctrl+wheel zooms; the Logs page follows the newest line. (d) Hide scroll bars on and off, without a restart. (e) The import list in the dark theme, and Compare's tick boxes. (f) A crash: an Unreal game that crashes reads crashed (… CrashReportClient.exe); The Witcher 3 closed normally no longer reads crashed. (g) The new measurements on the RTX 5080: the VSync share against the game's own VSync setting, the render scale against the DLSS mode, the clocks, fan and limits. (h) Thejastrings markedreview. (i) The Privacy Policy 2.7 wording — before PR-5 and PR-7 merge. -
beta.17 on real hardware. (a) A theme switch: on Settings, Dark → Light → Dark, and again with a session's summary window open — every description and caption follows at once. (b) Hide scroll bars on: the Dashboard, Games, a game's page, Logs, About, Help ▸ User guide and a drop-down list draw no bar, and the wheel still scrolls; off, the bars come back without a restart. (c) Help ▸ User guide lists twelve pages and Limitations; a link to a section opens that section. (d) The wiki, once the release is out: the Wiki tab shows Home, the sidebar's two halves and a footer naming
v0.1.0-beta.17— then tick Restrict editing to collaborators only (Settings ▸ General ▸ Features ▸ Wikis), or anyone can change a page until the next release overwrites it. (e) Thejastrings markedreview. -
beta.24 on real hardware — decision tables written before the runs. (a) The mix (D62): a DLSS 4 title (Cyberpunk 2077 or Hell Is Us) with the NVIDIA App's Frame Generation Mode on Use 3D app setting, one session of about two minutes each at ×2, ×3 and ×4 chosen in the game's menu, plus its menus → the summary's Frame generation in this session lists ×2.0 / ×3.0 / ×4.0 with shares near the time spent, each with its own Native → Displayed, and the line Set in the game — no NVIDIA App frame-generation override. Then the MFG title with the App's Fixed ×6 → a ×6.0 row and Set in the NVIDIA App: Fixed ×6. Then Dynamic, Target FPS = Max refresh rate, Multiplier = Up to 6x → several rows or Not classified, and Set in the NVIDIA App: Dynamic, up to ×6, target: max refresh rate. Record the stored
driver_profilevalues for the Dynamic run:NGX_DLSSG_DYNAMIC_MULTI_FRAME_COUNT_MAX5 and the target0x01000000confirm the decode; anything else correctsNvidiaOverrides.FrameGenerationContext. (b) The quality mode (D63) on Expedition 33: the App's Super Resolution mode Quality, then DLAA, Ultra Performance, Performance, one short session each → the header reads DLSS (driver-reported) Quality · NVIDIA App and so on. StoredperformanceMode: Ultra Performance 3 (already measured on Silent Hill 2) and DLAA 5 confirm NGX's numbering; DLAA 4 would mean the report follows the profile's numbering above 3 — thenUpscalerNames.FromDriverReportchanges, and the row goes intospike-notes. (c) The libraries (D64): the same sessions' DLSS line names the super-resolution library and from the graphics driver when the override's copy is loaded; preset L → DLSS 4.5 (preset L). With Model Presets on Use 3D app setting, the game's own library and no generation beyond what was observed. Record the names the override loads under%ProgramData%\NVIDIA\NGX(the summary's Loaded: line) — they correct05_DETECTION§Shipped is not loaded. (d) DLSS 5 on the owner's DLSS 5 title: DLSS 5 runtime loaded. If it is not shown, record the module names it loads (Loaded: line);nvngx_dlssnr.dllis then corrected inCensusNamesand05_DETECTION. (2026-11-06,spike-notes§26: Hogwarts Legacy, Neural Rendering on, loadednvngx_dlssnr.dll310.9.16.0 from the game's folder — the name holds; whether it ran is what beta.34 measures, item 30(a).) (e) SonarCloud (D67): bulk-mark per13_CI_CD§SonarCloud; optionally its Ignore issues on multiple criteria rows; close PR #315. (f) The Legal Gate shows Disclaimer 2.11 and Privacy Policy 2.12 once. (g) Thejastrings markedreview. (2026-10-19, the owner's first runs —spike-notes§22: (a) the Dynamic context line reads the App's own words, and the mix found ×2.0 / ×3.0 / ×6.1 — plus a ×1336.0 row that was a defect, fixed in beta.26; (c) the override loads160_E658700.bin310.9.16.0 and1B0_E658703.dll2.14.16.0 from the NGX folder; (e) done — every issue marked; the last six, triaged in13_CI_CD§SonarCloud (beta.26), the same day, andmain's quality gate passes. The rest is not run yet.) (2026-10-20, the owner's runs of beta.26 —spike-notes§23: (a) done — ×2, ×3 and ×4 chosen in Cyberpunk 2077's menu read ×1.9 (ten seconds), ×3.0 and ×4.0, each with its own rates, under "Set in the game — no NVIDIA App frame-generation override"; Fixed ×6 on Expedition 33 read ×6.0 under "Set in the NVIDIA App: Fixed ×6"; Dynamic on Silent Hill 2 read ×2.0 and ×3.0, plus a ×2.52 row that was a defect, fixed in beta.27. The Witcher 3 under Fixed ×6 presented ×2.0 throughout: the rows are the frames, the line is the setting. (b) could not pass before beta.27: every stored driver word had lostCREATED | EVALUATE, read after the game had closed, so an NGX-direct title under the override never read its mode — run it on beta.27. (c) The Witcher 3 under the override loaded160_E658700.bin310.9.16.0 and1B0_E658700.dll2.14.16.0; Silent Hill 2 and Expedition 33 loaded1B0_E658703.dll.) -
beta.25 on real hardware — FSR's quality mode (D65), decision table written before the run. Lies of P (FSR through AMD's FidelityFX libraries) launched by FrameLedger, not attached, with the game's own FSR at Quality, then a second session at Performance → the summary's header reads FSR 3 Quality, then FSR 3 Performance (or FSR Quality where the SDK 2.x libraries name no version), and the CSV export's
# quality_mode:saysquality (game). Then: no mode on both → the title sizes its frames without asking, or asked before the hook was in: record the session's render → output resolution and the Loaded: line inspike-notes, and D65 stays built and silent for that title. A wrong mode (the Quality session reading Balanced) → the answers this title receives are not the vendor's documented ratios: record the storedupscaler_qualityand the render size inspike-notes, and the match is withdrawn until it is explained. With the game's dynamic resolution on (if it offers one) → no mode. (2026-10-19,spike-notes§22: the Quality session read no mode with the query hooked — the first branch; 1707×961 is the engine's own rounding of 66.67 %, not the size answer, so the title asked before the hook was in or never asked. D65 stays built and silent for Lies of P. The Performance session is not run.) (2026-10-20, §23: the Performance session, started through Steam, read "FSR 3 · 1280×720 → 2560×1440" and no mode — the first branch on both. 1280×720 is exactly the vendor's Performance size, so a query the hook met would have matched: the title did not ask while the hook was in. It cannot be launched by FrameLedger as this item asks — started directly it hands itself to Steam within seconds, and before beta.27 the game Steam started was not recorded at all.) -
beta.27 on real hardware. (a) The driver's report, and item 20(b): Expedition 33 under the NVIDIA App's DLSS override → the header reads DLSS (driver-reported) with the override's mode and · NVIDIA App (Balanced as set on 2026-10-20); then 20(b)'s four modes. Still Upscaler not identified → record the session's stored
ngx_driver_words: no reading while the game ran said the feature was created and evaluated. (b) Start directly on Lies of P: the notice says a Steam game may hand itself to Steam first, and the game Steam starts is recorded —agent-*.logsays started while the last session of its executable was ending; recording it now. The crash safety counts the hand-off: after two such starts hooking is off again (19_SAFETY). (c) One window per session: open a session from a Sessions tab, then again from the game page or its notification → the same window comes forward, restored if minimised. (d) A game in exclusive full-screen (Dark Souls III, Lies of P) → its summary's Display card shows the window size. -
beta.28 on real hardware. Two games at once — one hooked, one with hooking off (or refused) → the Dashboard shows two cards side by side, the hooked one first, and 2 games recording beside Live capture; each card's numbers are its own game's; closing one leaves the other's card where it is, and the count goes. A third game → a third card on the next row and 3 games recording. (The
jastringDashboard_Live_Count_Formatis markedreview.) -
beta.29 — SonarCloud from CI (D68), the owner's settings. None blocks anything. (a) Optional: add
SONAR_TOKENto the repository's Dependabot secrets (Settings ▸ Secrets and variables ▸ Dependabot) if Dependabot's pull requests should be analysed too; until thenci.yml'ssonarcloudjob is skipped for them, as it is for a fork's. (b) Optional: SonarCloud's branch list holdsbeta29/pr1-sonarcloud-ci, left by a dispatch of that branch the plan then refused (13_CI_CD§SonarCloud, The first analyses); delete it under Branches, or let SonarCloud remove it after 30 days without an analysis. (c) Optional:analyze (actions, none)(CodeQL over the workflows) andsonarcloudare not required checks; making either one required is the owner's setting. (d) Velopack 1.2.161 and Markdig 1.5.0 were not taken by #335 (docs/changelog/0.1.0-beta.29.md, The libraries Dependabot never updated): the first changes how updates install and wants a run of the update path on the owner's machine, the second its licence copy re-read. (2026-10-26, beta.30: Velopack 1.2.161 taken — the owner's decision D71, its update path is item 25(c); Markdig went to 1.4.2, its licence text re-read and unchanged; 1.5.0 waits for the cooldown.) -
beta.30 on real hardware. (a) Enter in the consent dialog (D69): on a game whose hooking is off, turn the switch on, type the phrase exactly and press Enter → hooking is on, and the switch and its text agree; Enter before the phrase is complete → nothing happens; Esc → the switch is back off beside off, and leaving the page and coming back shows the same. (b) The numbered markers (D70): the game whose GPU driver changed on 2026-10-24 — Sessions at a glance and the Trend show a badge 1 above the chart, whole, in both themes; the list under each chart names that day and Driver GPU: 32.0.16.1742 → 32.0.16.2101; pointing at the dashed line shows the same; a narrow window keeps every badge whole. (c) The updater (D71): Help ▸ Check for updates on beta.29 installs beta.30 (beta.29's updater, a delta); the update to beta.31, when it comes, is the first Velopack 1.2.161 installs — say whether it downloaded the delta or the full package, and whether it came back. (d) The
jastrings markedreview(Trend_Changes_Header,Trend_Change_Heading_Format). -
beta.32 on real hardware. (a) The update from beta.31: Help ▸ Check for updates, Restart to update — the terms window shows the EULA 1.6 and the Disclaimer 2.12 once, with no tick box, and nothing else of the alpha appears: no ALPHA badge, no banner, the title FrameLedger, Settings ▸ Updates ▸ Channel as before. (b) About ▸ Legal documents lists the Alpha notice, and its version line reads Runs on .NET 10.0.x; Help ▸ User guide has Alpha builds. (c) Whether the update downloaded the delta or the whole package. (d) The
jastrings markedreview:About_Runtime_*here;Alpha_*,FirstRun_Alpha_*,FirstRun_Doc_Alpha,App_Title_AlphaandSettings_UpdateChannel_AlphaBodyshow only in an alpha. -
0.1.0-alpha.1 on real hardware (D73, D74). (a) Installing it over beta.32:
FrameLedger.App-alpha-Setup.exefrom its release page — Velopack asks whether to replace the installed FrameLedger; the terms window shows the Alpha notice with its warning box, and Accept stays off until the box is ticked; Decline closes the App. (b) While it runs: the ALPHA badge (its tooltip names .NET 11.0.0-rc.3), the title FrameLedger Alpha, the banner at start (closable; its button opens the notice); About reads Alpha build — runs on .NET 11.0.0-rc.3…; Settings ▸ Updates ▸ Channel is locked with its line. (c)%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.1.dbexists and opens. (d) One hooked (Tier-1) session of a game measured before records as on the beta; the Agent's log names the release line and .NET 11. (e) Going back: the beta'sFrameLedger.App-win-Setup.exeover it — the beta shows the alpha's session. (f) Thejastrings markedreviewthat only an alpha shows (Alpha_*,FirstRun_Alpha_*,FirstRun_Doc_Alpha,App_Title_Alpha,About_Runtime_Alpha_Format,Settings_UpdateChannel_AlphaBody). -
beta.33 on real hardware: the Xbox titles (D77–D81). (a) The update from beta.32 (or alpha.2's, item 29): the terms window shows the Privacy Policy 2.13 once. (b) Import library offers the eleven Xbox titles as Xbox — the Unreal titles with their shipping executables (
…-WinGDK-Shipping.exe,ValorMortisMSG-Win64-Shipping.exe), the Unity titles with their players, nevergamelaunchhelper.exe— each with its package version (Xbox version 1.3.5124.0). (c) Each game's page shows its square logo whole in a square slot and its splash image as the banner, captioned Xbox. (d) Play starts Valor Mortis and FINAL FANTASY through Windows in both Play modes, and from an App run as administrator — the notice says Windows is starting it. (e) With consent given, one hooked session of each: Tier 1, frames, late attach, the engine and platform on the game page. (f) Thejastrings markedreview:Store_Xbox_Format,Art_Source_Xbox,Import_NothingFound,FirstRun_Import_Body,Settings_GameArt_Body,Play_Xbox_Format,Play_Xbox_NotStarted_Format,Play_PackagedGame_Format,Play_ToolTip_Store,Play_ToolTip_Direct,Settings_PlayMode_Body,Guard_TargetAppContainer,Guard_TargetMitigation. Thendocs/LIST_GAME_TESTED.mdgains the Xbox titles from a ledger copy (D35), approved before the commit. (2026-11-06, beta.34: done — inKONBINI and Valor Mortis, with the refresh the owner approved with the plan.) -
0.1.0-alpha.2 on real hardware (D73, D82). (a) The update from alpha.1: Help ▸ Check for updates offers alpha.2 — the first update an alpha's updater has found — and Restart to update installs it; say whether it downloaded the delta or the whole package. (b) The terms window shows the Privacy Policy 2.13 and the Alpha notice with its box again, and Accept waits for the tick. (c)
%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.2.dbexists beside alpha.1's, and opens. (d) Item 28's Xbox checks, on the alpha. -
beta.34 on real hardware (D83–D86). (a) The update from beta.33 (or alpha.3's, item 31): the terms window shows the Disclaimer 2.13 and the Privacy Policy 2.14 once. (b) Hogwarts Legacy with Neural Rendering on, one hooked session → DLSS 5 (neural rendering on N % of rendered frames); then off —
spike-notes§26's table, written before the run, decides (on and 0 %: neural rendering runs outsideslEvaluateFeature, the line stays runtime loaded, not seen running, and the session'ssl_tag_censusis recorded before anything is named). (c) Phantom Blade Zero under the NVIDIA App's Dynamic, up to ×3 → DLSS 4.5 (Dynamic multi frame generation, set in the NVIDIA App); the game's own ×3 with no override from the App → DLSS 4. (d) Games from any page: the cards at once, a second visit at once; the Debug lineui: page … shown … ms after its navigation. (e) Settings → change the language → the window comes back on Settings. (f) The filters on Games and Compare, the Compare columns and selection bar, the selected page's label in the pane, in both themes. (g) The 34jastrings this release adds, all markedreview:Dlss_Basis_Dynamic,Dlss_NeuralRendering_NotSeen,Dlss_Feature_NeuralRendering,Dlss_Basis_NeuralRendering_Format,Games_Filter_*,Games_Header_Filtered_Format,Filter_Clear,Compare_Filter_*,Compare_Count_Format,Compare_Count_Filtered_Format,Compare_ClearSelection,Compare_MidSession_Changed,A11y_Games_Filter_*,A11y_Compare_Filter_*. -
0.1.0-alpha.3 on real hardware (D73, D87). (a) The update from alpha.2: Help ▸ Check for updates offers alpha.3 and Restart to update installs it; say whether it downloaded the delta or the whole package. (b) The terms window shows the Disclaimer 2.13, the Privacy Policy 2.14 and the Alpha notice with its box again, and Accept waits for the tick. (c)
%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.3.dbexists beside alpha.2's, and opens; the ledger it left is at schema 22. (d) Item 30's checks, on the alpha. -
beta.35 on real hardware (D88–D91). (a) The update from beta.34 (or alpha.3's): no terms window, the ledger unchanged. (b) Narrator: a safety notice is read as it appears; the agent's banner going and coming; Tools ▸ Database maintenance ▸ Check reads its result; a short message at the bottom is read; H moves between each page's title and its sections; Settings ▸ Theme's options read their words; the Sessions table's cells read their values; Tab to a chart says its name and where its numbers are, and its arrows, Ctrl+arrows and A move it without scrolling the page; a double-click shows all of it. (c) Contrast themes: Aquatic and Desert, and one with an edited colour (Windows 10 if at hand) — every page, a dialog, the title bar's agent pill, a short message, a chart; turned on and off with FrameLedger open, it follows at once; Settings ▸ Theme shows its line. (d) Ctrl+1 … Ctrl+5 put the keyboard in the page and Narrator says its title. (e) Animation effects off (Settings ▸ Accessibility ▸ Visual effects): no page slides in. (f) Remove on a game's page: the box opens over the window, its Cancel puts the focus back on Remove; the light theme's agent pill and a done message read clearly. (g) Help ▸ Accessibility shows the statement. (h) The 35
jastrings this release adds, all markedreview:Menu_Help_Accessibility,Accessibility_Title,Settings_Theme_ContrastOnand 32A11y_*(the names, the chart names and keys, the announcements). -
Qodana, and beta.36 on real hardware (D93). (a) The update from beta.35: no terms window, the ledger unchanged. (b) The re-pointed bindings, by hand — the tests pin their text, not a click: on Games, a card opens its game and both Play buttons (card and list) start it, greyed in a viewer; on the Dashboard a recent session opens; on a game's page a session row's Open opens its summary; in a session's summary a Yes/No/N/A chip opens the override dialog; a safety notice's button dismisses it; Settings lists the hooked games with Revoke, the exception rows with Grant/Withdraw, and the system information lines. (c) Qodana Cloud: the trial's end changes nothing in CI (the Community linter needs no licence; the token names the project the report goes to). If an Ultimate licence is wanted — JetBrains has a programme for open-source projects —
13_CI_CD§Qodana says what moves. (d)qodanaas a required check, or not: advisory today, likesonarcloud. (e) The members nothing uses (13_CI_CD§Qodana, 34 and 49 getters): say which are dead, and a pull request removes them. -
beta.37 on real hardware — the first build on .NET 11's release (D94–D98). (a) The update from beta.36: Help ▸ Check for updates offers beta.37 and Restart to update installs it — a download of about 70 MB, not a few; the terms window shows the EULA 1.7 and the Disclaimer 2.14 once and nothing else; the ledger stays at schema 22. (b) A hooked session on .NET 11.0.0: one title you measure often, Tier 1 — frame times, the upscaler and frame generation as before; the Agent's log opens with
release line main, .NET 11.0.0, and Help ▸ About reads Runs on .NET 11.0.0. This is the run20_OPEN_QUESTIONS§G's table asked for before the move and did not get (D94). (c) The Agent in admin mode and the logon task still start it — the publish is self-contained on a new runtime. (d) Windows 10 22H2, if a PC or a VM with it is at hand: does it install and start? No version has ever been run there; D95 states it as untested, and one run would be the first evidence either way. (e) The Japanese of the three alpha strings that changed or are new (Alpha_Banner_Body_Format,Alpha_Banner_Body_Resting_Format,About_Runtime_Alpha_Format) and of the first-run summary's first line. (f) Going back — only if something is wrong: install beta.36 over it; the ledger opens. -
alpha.4 on real hardware — the last alpha for now (D98). (a) The update from alpha.3: Help ▸ Check for updates offers alpha.4 and Restart to update installs it — a large download, the runtime moving from the release candidate to 11.0.0. (b) The terms window shows the EULA 1.7, the Disclaimer 2.14 and the Alpha notice 1.1 and waits for the notice's box;
…\backups\ledger-before-0.1.0-alpha.4.dbexists beside the older copies, and opens; the ledger stays at schema 22. (c) The banner says the alpha line is paused and to install the beta — not the experimental-build warning — and Help ▸ About reads Alpha build — runs on .NET 11.0.0, with no "prerelease". (d) Then install beta.37 over it: the installer asks to replace it; the beta opens the ledger, shows no Alpha notice, and its update channel is no longer locked. -
beta.38, and the two Qodana reports (D99, D100). (a) The update from beta.37: Help ▸ Check for updates offers beta.38 — a small download — and Restart to update installs it; no terms window. (b) Links still open: the documentation from the Help menu, a document's page on GitHub from its window, a link inside the user guide and inside the update notes, and the source link in Help ▸ About each open in the browser, as before. (c) Qodana Cloud: the projects
frameledgerandframeledger-cppeach show a report frommainwith no problem. A job's log says Qodana license plan: Ultimate and the day the subscription is active until; when it lapses both jobs go red — advisory, never a blocked merge — andqodana.yamlsays the way back. (d)LogNoteW: the Overlay has one function nothing calls (src/native/FrameLedger.Overlay/src/dllmain.cpp). Say whether it is removed — a pull request of its own, eleven lines — or kept; either way the.editorconfigsection that names it is then removed or reworded. -
beta.39, Advanced metrics on real hardware (D101–D109). (a) The update from beta.38: the terms window shows the Privacy Policy 2.15 and the Disclaimer 2.15 once; the ledger moves to schema 23 and every earlier session opens as before. (b) The switch: Settings ▸ Recording ▸ Advanced metrics on — Advanced appears as the last item on the left at once, Ctrl+6 opens it; off — it goes, and Ctrl+6 does nothing. (c) This PC, on the RTX 5080: the facts (firmware, cores, memory sizes, the display's HDR and variable refresh), the Right now table beside the NVIDIA app or HWiNFO — the first comparison of any of these values with another tool — and the chart moving; a fan's Read at a few seconds behind the memory's. Leave the page: the Agent's log says the reader closes some fifteen seconds later, and opens again when the page does. (d) A session with a real game, the option on: it is on Session with its statistics and its chart; its summary has Advanced metrics… and the button opens it there; variable refresh was active and the colour space against what the game and the display really did; the driver's settings for the game against the NVIDIA app. A session recorded with the option off is not on the list. (e) As administrator, with PawnIO installed — the first run there has ever been (
20_OPEN_QUESTIONS§M10, §M13): the processor per core, the memory and the motherboard's sensors appear on This PC and Sources says Read; watch for a pause or a hang when the page first opens, and compare a few values with HWiNFO. Without it, Sources gives the reason in words. (f) What it costs: the Agent's processor time and memory during a session with the option on and with it off (NFR-2:1 %2.5 % of one core since D117, 150 MB) —and with that in hand, the answer to §M16§M16 was measured without a game and answered on 2026-11-11; what is left for a real game is the hooked session and the elevated one. (g) The words: thevistrings read as a Vietnamese speaker would write them; thejastrings markedreview. (h) A copy of the ledger (--data-dir) that holds such a session: the page is there, opens on Session, and This PC says it is a copy. -
beta.42 — the log that answers D121, the label, the plane at infinity (D119–D122). (a) The update from beta.41: Help ▸ Check for updates, Restart to update with no game running; no terms window. (b) Cyberpunk 2077 with FSR upscaling (FSR 3 or 4, with or without FSR frame generation — as it was when the upscaler read "unknown"): one session of a few minutes of play, then quit the game from its own menu. Nothing else is needed:
%LOCALAPPDATA%\FrameLedger\logs\overlay-<pid>-….logof that session is what is read. If the session now names FSR, say so — nothing in this release should have changed that. (c) A game that gave one depth plane — Lies of P, Clair Obscur or Dying Light: The Beast, FSR upscaling, Advanced metrics on: the session's Advanced page shows both planes, one of them "∞". If it still shows one, the missing plane is notFLT_MAXand the log of (b)'s kind says nothing about it — say so. (d) A session that changes upscaler — Dying Light: The Beast as it was (DLSS evaluated, then FSR), or any game switched between DLSS and FSR in its menu during one session: the summary names the one that ran longest, with that one's quality and render size, and says settings changed during session. (e) Any hooked game, ended by quitting it: its overlay log has lines after the first second —HOOK_INSTALLEDwith a module and a function,RUNTIME_CENSUS— and noPATCH_FAILED; if there is one, itsa=number is the reason. Four sessions were run on 2026-11-12 and read the same morning (START HERE §What the owner's first four sessions on beta.42 showed): (a) happened — the sessions carry the beta.42 build; (b) read, and D121 answered: the session upscaled with FSR 2.1, built into the game; (c) Lies of P and Dying Light showcameraNear = ∞; (e) all four logs are whole and none has aPATCH_FAILED. (d) was not exercised, and the owner has not said the item passed. -
beta.43 — the first real games with the two new hooks, and the guard's re-read (D123–D125). Not first on a game under the user-mode exception's trial (D38): a crash there ends the exception for good. (a) The update from beta.42: Help ▸ Check for updates, Restart to update with no game running; the terms window shows once, with Privacy Policy 2.17. (b) The guard: over the games played, the Agent's log (
logs\agent-<date>.log) has no session that ended at a game's launch withguard=ModuleScanFailed. If one does, its signal now says which kind — kept changing while it was read (four reads were not enough) or came back incomplete — say which. (c) A Streamline game with Advanced metrics on (Dying Light: The Beast, or Cyberpunk 2077 with DLSS): a session of a few minutes, quit from the game's menu. Its Advanced page shows the Streamline rows — jitter, motion vectors, depth, projection, resets — and the line under the session says read. Read them for sense: a field of view between about 0.3 and 2.5 rad, an aspect ratio near the screen's, a jitter under 1, planes that are not both zero. Values that make no sense mean the game's struct is not laid out as the one FrameLedger was built against: say so, with the numbers, and do not run further games. (d) FSR frame generation on (Cyberpunk 2077 or Lies of P), Advanced metrics on: the page shows the frame-generation rows — on, asynchronous or not, the flags, the rectangle — and the line says read. (e) The three answers of the line: a game with neither library says not hooked for both; a game where it says hooked — the game did not make the call for a library the game plainly uses is a finding, not a pass — say which game. (f) Off means off: with Advanced metrics off, start a game afresh and record a session; it has no Advanced button, and itslogs\overlay-<pid>-….loghas noHOOK_INSTALLEDline namingslSetConstantsorffxConfigure. (A game that was already running when a session with the option on was recorded keeps the two patches until it exits — that is by design, and its log will have the lines.) (g) Nothing else moved: no crash, noPATCH_FAILEDin any overlay log, frame rates and the frame-generation factor as on beta.42 for the same game and settings. What each outcome means, written before the run. (c) or (d) empty with not hooked: the log of that session says why — noHOOK_INSTALLEDfor the function (the library is a 1.x interposer or lacks the export) or aPATCH_FAILED(itsa=number is the reason). Empty with hooked — the game did not make the call: the game reaches Streamline or FSR by a way that does not pass the export — beta.44's plan needs to know. A crash, or a game that will not start: say so at once; Disable all hooking (Settings ▸ Capture) and switching Advanced metrics off are the two ways to run without the hooks, and which of them cured it says which hook it was. Nine sessions were run on 2026-11-12 and read the same afternoon (handoff/history/0.1.0-beta.43.md§What the owner's nine sessions on beta.43 showed): (a) happened — Privacy Policy 2.17 accepted once, at the update; (b) held — noguard=ModuleScanFailedsince the update; (c) read on Phantom Blade Zero, Cyberpunk 2077 and Hogwarts Legacy, every value sane but one: Cyberpunk 2077 gives its field of view in degrees (51–90), and the page labels it radians — the struct is laid out as expected, the label is wrong; (d) read on Lies of P, not exercised through the FidelityFX 2.3 loader; (e) the three answers were each seen and none is a finding, a game with neither library was not run; (f) held on Lies of P started afresh; (g) noPATCH_FAILED, no fault, frame rates as before — Lies of P's 35 s end with exit code 3 is, by the owner, the game's own crash after a shader failed to compile, and Hogwarts Legacy's fault at exit is in Windows' log six times since 2026-11-06, hooked or not. Judged passed 2026-11-12, on the owner's word to go on if it did; the two parts in bold stay open. -
beta.44 — the two questions about a feature in real games, and what the nine sessions found, fixed (D126–D128). Not first on a game under the user-mode exception's trial (D38): a crash there ends the exception for good. (a) The update from beta.43: Help ▸ Check for updates, Restart to update with no game running; the terms window shows once, with Privacy Policy 2.18. (b) Cyberpunk 2077 with Advanced metrics on, a session of a minute or two: its Advanced page shows the field of view as the game gives it —
51.0055 – 90, or whatever the game's setting makes it — with a line under it that says Not radians, and no "rad" beside the number. The two sessions of 2026-11-12 keep51.0055 – 90 rad (2922.4° – 5156.6°): they were stored that way. (c) Any Streamline game with Advanced metrics on (Phantom Blade Zero, Hogwarts Legacy, Cyberpunk 2077): the line under the session has one more sentence — Which version each Streamline feature is: …. What each requires: …. — and for each it says read, or hooked - the game asks this while it starts, and did not ask again after FrameLedger attached. The second is the expected answer for a game that was already past its start-up when FrameLedger attached; it is not a failure. If it says read: the page lists features by NVIDIA's names (kFeatureDLSS,kFeatureDLSS_G) with versions and requirements — check that the driver version it shows as detected is the installed driver's, and that Streamline's version is the game'ssl.*.dllfile version. (d) Which games, if any, say read: nothing to set up — FrameLedger attaches as soon as it sees the game — but say, for each Streamline game run, which of the two answers each call got. Hogwarts Legacy loaded its Streamline library some six seconds after FrameLedger attached on 2026-11-12, so it is the likeliest to say read; Phantom Blade Zero and Cyberpunk 2077 had it loaded already. (e) A game with no Streamline (Lies of P, Kingdom Come: Deliverance II): both say not hooked. (f) Off means off: with Advanced metrics off, start a game afresh and record a session; itslogs\overlay-<pid>-….loghas noHOOK_INSTALLEDline namingslGetFeatureVersion,slGetFeatureRequirements,slSetConstantsorffxConfigure. (g) Nothing else moved: no crash, noPATCH_FAILEDin any overlay log, frame rates and the frame-generation factor as on beta.43 for the same game and settings. With Advanced metrics on, a Streamline game's log hasslGetFeatureVersionandslGetFeatureRequirementsas its first two StreamlineHOOK_INSTALLEDlines. (h) The count of early ends (D126) is not something to provoke: if a game whose hooking you switched back on ends once within a minute of starting, hooking stays on; a second such end switches it off, as before. What each outcome means, written before the run. (c) not hooked on a Streamline game: the log says why — noHOOK_INSTALLEDfor the function (a 1.x interposer, or the export is missing) or aPATCH_FAILED. (c) and (d) both did not ask again on every game: the calls are made before any attach can be in — then these two hooks give nothing in attach mode, and whether they are worth their two patches is the owner's to say before train C. Read with numbers that make no sense (a driver version that is not the installed one, a feature namedfeature <number>): say so with the numbers — an id with no name only means NVIDIA added a feature this build does not know. A crash, or a game that will not start: say so at once; Disable all hooking (Settings ▸ Capture) and switching Advanced metrics off are the two ways to run without the hooks, and which of them cured it says which hook it was. Eight sessions were run on 2026-11-12 and read the same evening (handoff/history/0.1.0-beta.44.md§What the owner's eight sessions on beta.44 showed): (a) happened — Privacy Policy 2.18 accepted once; (b) held — Cyberpunk 2077 reads51.0055 – 90and not radians; (c), (d) both questions read on five games, six sessions of six — the expected answer was the other one — with the driver, Windows and NGX versions agreeing with the PC, and one reading no file could give: frame generation's Streamline plugin is 2.14.16 on three games that ship an older one; Cyberpunk's version question was not asked again; (e) held on Kingdom Come: Deliverance II; (g) noPATCH_FAILED, no fault, the two rows first; (h) seen for real — Valor Mortis's second early end switched hooking off, the owner switched it on, the count is 0. (f) was not exercised. Valor Mortis crashed 51 s into a hooked session exactly as on beta.40, and Black Myth: Wukong faults in Steam's crash handler at every exit: neither is explained, and neither began with this release. Taken as passed on the owner's "update and go on", 2026-11-12; (f) and the two comparisons stay open. -
beta.45 — six more Streamline calls in real games (D129–D131). Not first on a game under the user-mode exception's trial (D38): a crash there ends the exception for good. (a) The update from beta.44: Help ▸ Check for updates, Restart to update with no game running; the terms window shows once, with Privacy Policy 2.19. (b) Any Streamline game with Advanced metrics on (Phantom Blade Zero, Clair Obscur, Valor Mortis, Black Myth: Wukong, Cyberpunk 2077), a session of a few minutes that includes changing a graphics setting that touches frame generation or DLSS if the game lets you: its Advanced page has two more tables — Whether Streamline says each feature is supported, and loaded (
kFeatureDLSS_G · slIsFeatureSupported=eOk,· slIsFeatureLoaded= On or Off) and Each feature switched on or off, its resources allocated and freed, Streamline shut down — and the line under the session ends with one more sentence: Streamline's other calls - read: …; hooked, the game did not make the call: …; not hooked: …. Say, for each game, which calls are in which group. (c) Check one number you can know: a feature the game has switched off in its own menu and that reads On underslIsFeatureLoaded, or the reverse, is worth saying — "loaded" is Streamline's word for the plugin being in, not for the feature being in use, and what a real game does here is not known. (d) A game with no Streamline (Lies of P, Kingdom Come: Deliverance II): all six are in not hooked. (e) The way out: close each game the way you usually do. Black Myth: Wukong and Hogwarts Legacy already fault while closing (Steam'scrashhandler64.dll,_nvngx.dll); what matters is whether anything is different — a new fault in Windows' application log (Event Viewer ▸ Windows Logs ▸ Application, Application Error) naming another module, a game that hangs on exit, a game that used to close cleanly and does not. (f) Off means off: with Advanced metrics off, start a game afresh and record a session; itslogs\overlay-<pid>-….loghas noHOOK_INSTALLEDline naming any of the ten:slSetConstants,ffxConfigure,slGetFeatureVersion,slGetFeatureRequirements,slIsFeatureSupported,slIsFeatureLoaded,slSetFeatureLoaded,slAllocateResources,slFreeResources,slShutdown. (This is item 42 (f), which was not run.) (g) Nothing else moved: no crash, noPATCH_FAILEDin any overlay log, frame rates and the frame-generation factor as on beta.44 for the same game and settings; with Advanced metrics on the log ends with anUNHOOK_RESTOREDline for each patch and no "the stop was still writing". (h) The Advanced page's catalog: The preferences the game started Streamline with reads Not read: the game makes this call once, before FrameLedger is inside it. What each outcome means, written before the run. A call in hooked, the game did not make the call in every game: the game does that before FrameLedger is in, or never — then that hook gives nothing in attach mode, and whether it keeps its patch is the owner's to say.slIsFeatureSupportedwith a result that is noteOkfor a feature the game then uses: say which — the row is Streamline's answer to the game, and the game may have asked about another graphics card. A count of≥ 15: the game allocates or frees every few frames; the number stopped, nothing is wrong. Not hooked on a Streamline game: the log says why — noHOOK_INSTALLEDfor the function (a 1.x interposer, or the export is missing) or aPATCH_FAILED. A new fault on the way out, a hang on exit, or a crash in play: say so at once, with the game; switching Advanced metrics off and starting the game afresh runs it without any of the ten hooks, and if that cures it the hook is one of the six new ones or the four before — the overlay log's lastHOOK_INSTALLEDlines and Windows' fault entry say which is nearer. A game that will not start at all: Disable all hooking (Settings ▸ Capture). Seven sessions were run on 2026-11-13 and read the same day (handoff/history/0.1.0-beta.45.md§What the owner's seven sessions on beta.45 showed): (a) happened — Privacy Policy 2.19 accepted once; (b) five Streamline games, six sessions —slIsFeatureSupportedread in all,slIsFeatureLoadedin three games,slSetFeatureLoadedin two,slFreeResourcesandslShutdownonce in one game each,slAllocateResourcesin none; (d) held on Kingdom Come: Deliverance II; (e) nothing different: Hogwarts Legacy and Black Myth: Wukong fault while closing in the same module at the same offset as before, the other four games leave no fault; (g) noPATCH_FAILED, no fault counted, rates as before — and no session was stopped while its game ran, so the part aboutUNHOOK_RESTOREDlines was not exercised and was worded wrongly. (f) was not exercised; (c) and (h) are the owner's to say. Taken as passed on the owner's "check the logs and go on", 2026-11-13; (f) stays open.slAllocateResourceskeeps its patch (D135, the same day). -
beta.46 — hooks in and out under one stop of the threads, in real games (D134). Not first on a game under the user-mode exception's trial (D38): a crash there ends the exception for good. (a) The update from beta.45: Help ▸ Check for updates, Restart to update with no game running; the terms window does not show (nothing new is read). (b) Any Streamline game with Advanced metrics on (Hogwarts Legacy first — its thirteen patches took 2.8 s on beta.45 — then Phantom Blade Zero, Cyberpunk 2077, Dying Light: The Beast, Black Myth: Wukong): play as usual and close the game. Its
logs\overlay-<pid>-….loghasPATCH_BATCH installlines, and thesl.interposer.dllHOOK_INSTALLEDlines above each carry the same time to the thousandth of a second, not times 0.06–0.2 s apart. Say thea=of eachPATCH_BATCHline: it is the microseconds the game's threads were stopped for that batch. (c) How the game's start feels: no worse than on beta.45 — the hitching while a game with Streamline starts should, if anything, be shorter. (d) A stop while the game runs, which no session has exercised since beta.43: with a game running and being recorded, switch Disable all hooking on in Settings ▸ Capture; the part inside the game stops at its next safety scan, within 30 seconds. The game must go on running without a freeze of seconds; the log then hasSTOP, anUNHOOK_RESTOREDline for every patch, onePATCH_BATCH restoreline andSTOP_FLUSHED … a=1. Switch it back off afterwards. (e) A game with no Streamline (Kingdom Come: Deliverance II, Lies of P): its FSR rows are underPATCH_BATCHlines as well, and the session reads as before. (f) Nothing else moved: no crash, noPATCH_FAILED, noUNHOOK_DECLINEDunless another overlay is running, the same hooks inHOOK_INSTALLEDas on beta.45 for the same game, frame rates and the frame-generation factor as before, the Advanced rows as before. (g) Off means off (item 43 (f), never run): with Advanced metrics off, start a game afresh; noHOOK_INSTALLEDline names any of the ten Advanced-only calls. What each outcome means, written before the run. APATCH_BATCH installwhosea=is about what one patch cost on beta.45 (60 000–220 000) is the expected answer: one stop of the threads. Ana=of a second or more: one stop is long in that game — say which game and the number; it is still one where there were thirteen, but it is what would decide whether batches need a ceiling.HOOK_INSTALLEDlines of one batch with different times: the batch fell back to one patch at a time — the log then also has aPATCH_FAILED— say so with the log. A game that hitches at its start as it did not on beta.45, or freezes at (d): say so at once, with the game; 0.1.0-beta.45 is the build without this change. A hook that was in on beta.45 and is not on beta.46 (compare theHOOK_INSTALLEDlines), or a session that reads not hooked where it read read: the batch lost a patch — the log'sPATCH_FAILEDline names it and why. A crash in play or at exit that is new: say so at once; Disable all hooking runs the game with nothing patched after the start. Five sessions were run on 2026-11-13 and read the same day (handoff/history/0.1.0-beta.46.md§What the owner's five sessions on beta.46 showed): (a) held — the terms window did not show; (b) five Streamline games — every batch's lines carry one time;a=is 81 417–261 920 for sixteen of the eighteen batches, 1 260 835 for Hogwarts Legacy's thirteen and 608 700 for three of Cyberpunk 2077's, neither explained — and the sentence above about a fallback is wrong: a batch finished one patch at a time leaves no line unless a patch fails for good, so the log cannot say which of the two a longa=was; (f) held — no crash in play, noPATCH_FAILED, noUNHOOK_DECLINED, the same hooks as on beta.45, rates and factor as before, the two known faults on the way out at their old offsets. (d), (e) and (g) were not exercised; (c) is the owner's to say. Not passed: (d) is the half of this release that no real game has run. 2026-11-14, three more sessions (203–205), read the same morning — (d) is still not exercised. Disable all hooking was switched on before the games were started, not while one was being recorded: Cyberpunk 2077 (06:34) and Phantom Blade Zero (06:38) were each recorded asRefusedKillSwitch— tier 2, nothing injected, no overlay log for either process, which is FR-2.4 doing what it says and not what (d) asks. With the switch off again, Phantom Blade Zero (06:46, 518 s) was hooked from its start to its exit: twenty-two patches under one batch of 84 ms and ray tracing's two under one of 81 ms, ×3.0 at 89 → 268, no fault, a clean exit — and noSTOP, noUNHOOK_RESTORED, noPATCH_BATCH restoreline, because nothing stopped it while it ran. Windows' application log has no fault since 06:30. How (d) is run: start the game with the switch off and wait until FrameLedger shows it recording; then, with the game still running, switch Disable all hooking on; play on for half a minute; switch it off; close the game. 2026-11-14, the second try (sessions 206 and 207, Phantom Blade Zero): (d) held, twice. The game started with the switch off and was being recorded; the switch was turned on while it ran. Each log hasSTOPat the next safety scan, anUNHOOK_RESTOREDline for every one of the twenty-nine patches at one time, onePATCH_BATCH restore—a=83309anda=85578,b=0x1d— andSTOP_FLUSHED … a=1; noUNHOOK_DECLINED. Both sessions endedKillSwitchEngaged, tier 1, no fault, nothing dropped; the game ran on for three and four minutes and closed with nothing in Windows' application log. Whether a hitch was felt at the stop is the owner's to say. Taken as passed for what 0.1.0-beta.47 was held on — (a), (b), (d), (f). (e) and (g) were never run: they are (f) and (g) of item 45. -
beta.47 — NVIDIA's latency report, read inside a game (D132, D136, D138–D141). Cyberpunk 2077 first (D136), and not first on a game under the user-mode exception's trial (D38): a crash there ends the exception for good. This is the first release in which the part inside a game makes a call of its own — into the graphics driver, about once a second, on the game's presenting thread — so read (a) before (b). (a) The update: Help ▸ Check for updates, Restart to update with no game running; the terms window shows once, with Privacy Policy 2.20 and Disclaimer 2.16 — the Disclaimer's §2 has a new paragraph, One call it makes itself, into the graphics driver. Settings ▸ Advanced metrics says the same in its description. (b) Cyberpunk 2077, Advanced metrics on, frame generation OFF, Reflex on in the game's menu, five minutes of play, then close the game as usual. Its
logs\overlay-<pid>-….loghasLATENCYlines: reading the driver's latency report, and two more with the end of two paths —…\System32\nvapi64.dlland…\nvapi64_impl.dll. On the Advanced page, the session has a group Latency: the table What the driver's low-latency state is (five rows by NVIDIA's names, andfgMultiplier) and, in the chart's list, Latency per frame with seven lines. The line under the session ends with NVIDIA's latency report, which FrameLedger asks the graphics driver for inside the game: read. Say the total line's usual value, and whether the game felt any different with the option on — a hitch once a second is the thing to look for. (c) The same with frame generation ON (DLSS ×2 or more): the driver's pacer is another thread, and this is the arrangement the probe could not make. (d) Reflex switched off in the game's menu, if the game lets you: say what the line reads — read or asked, and the driver reported no frame; both are possible and neither is wrong. (e) Only after (b) and (c) are clean, a second game that uses Reflex through Streamline (Phantom Blade Zero, Clair Obscur, Black Myth: Wukong, Hogwarts Legacy). (f) A game that is not Direct3D 12 or has no NVIDIA library (Kingdom Come: Deliverance II, Lies of P): the line reads not read, with which of the two. (g) Off means off: with Advanced metrics off, start a game afresh; its log has noLATENCYline. (h) Nothing else moved: no fault counted, frame rates and the frame-generation factor as before, the game closes as it did. What each outcome means, written before the run. Read, with a total of a few to a few tens of milliseconds that moves with the frame rate: route D works in a real game; what comes next — more titles, the session summary — is the owner's to say. Asked, and the driver reported no frame in a game whose Reflex is on: the driver has a report for another object than the device FrameLedger holds; nothing is harmed, and the title is not readable this way. Not read — the game has not loaded nvapi64.dll in Cyberpunk 2077: what its files said did not happen at run time; another title is tried. Stopped — a call took N µs: one call of a few thousand microseconds, once, is most likely a pause of the game's thread on a busy PC (spike-notes§31, A run on a busy PC) — start the game again and see whether it repeats; if it repeats, or N is ten thousand or more, the driver holds the call in that game and route D stops for it — say so with the number. Stopped — a call into the driver faulted, or a fault counted in the session: route D stops (the commitment of §30) — say so at once, with the log. A game that freezes with aLATENCYline saying a call has not returned, or that freezes at all with the option on and not with it off: close it, say so at once; Advanced metrics off is the way to play it, and route D ends. A hitch once a second with the option on that is not there with it off: say so at once — the two-millisecond latch did not catch what a player can feel. The game closing by itself a second or two after it starts, only with the option on (Windows' Application log: exception0xc0000409): a Control Flow Guard refusal of the call — say so at once with the entry; that game enforces what the probe could only check for this driver. Spans that make no sense — a part larger than the total, a line that is always zero: say which; they are the driver's numbers and are shown as it reported them. Three sessions were run on 2026-11-14 and read the same morning — in Phantom Blade Zero, not Cyberpunk 2077 (sessions 208–210, Direct3D 12, Streamline 2.14.1). The read works in a real game. (a) held: the terms were accepted once, Disclaimer 2.16 and Privacy Policy 2.20. In all three the overlay log hasLATENCY … reading the driver's latency reportfour to five seconds after the attach, withC:\WINDOWS\SYSTEM32\nvapi64.dlland…\nvapi64_impl.dllon the two lines after it, and no laterLATENCYline: no error, no slow call, no fault, no stall. Each session's line reads read, and the slowest call into the driver was 24, 20 and 45 µs. Frame generation on: session 208, ×3.0 at 85 → 256 — and the driver's ownfgMultiplierread 3. Off: sessions 209 and 210, multiplier 1. Seven series in each, 227 / 24 / 823 points: 90 %, 62 % and 98 % of the Agent's own once-a-second samples (the short session spent its first seconds before the module was found). With frame generation ×3: total 23.4 ms, simulation 4.4, render submit 10.3, present 0.7, driver 10.9, OS queue 13.0, GPU render 11.5 (means). The driver's switches:bLowLatencyMode,bUseGameSleepandbFullscreenIFlipon at times, off at others;bFsVrrandbCplVsyncOnoff — so in a game the low-latency switch does read on, which it never did for the probe. No fault counted, nothing dropped, a normal exit each time, nothing about the game in Windows' application log; rates as on beta.46 for the same game. One outcome the list above names: a part larger than the total. GPU render reads 16.4 ms where the total reads 5.4 ms (session 209), and about equals it in session 210 (16.0 against 15.9 ms). The span is the driver'sgpuRenderStartTimetogpuRenderEndTime, and in this game that start lies before the frame's own simulation start: it reads like the time between two frames' GPU ends, idle time included — a reading, not a fact; the driver has a field of its own for the active time (gpuActiveRenderTimeUs), which FrameLedger does not read. It is shown as the driver reported it. The spans also overlap — render submit, driver and OS queue together are longer than the total — so they are not parts that add up, and the page does not say they are. Not run: Cyberpunk 2077, which (b) and (c) name; (d) Reflex off in the game's menu; (f) a game that is not Direct3D 12 or has no NVIDIA library; (g) off means off. Not said: whether the game felt any different with the option on. Not passed as written; what the three sessions were run for is answered. Five more sessions the same morning (211–215), read at 09:15: Cyberpunk 2077 twice, and three games the read must leave alone. (b), (c) Cyberpunk 2077 (Streamline 2.14.1, DLSS): session 211 with frame generation ×2.0 for 42 % of it (166 → 330) and menus for the rest, session 212 without, at 238 FPS. The module was found 4.8 s and 2.6 s after the attach, in the same two files; each session's line reads read; the slowest call took 34 and 65 µs; no laterLATENCYline. 190 of 195 and 429 of 438 samples carry a report. The total: 13.5 ms while frames were generated, 4.1 ms in the menus, 11.7 ms at 238 FPS without generation. GPU render is 2.7 ms there and never longer than the total (0 of 429 samples; 1 of 190) — so what the three sessions above showed is Phantom Blade Zero's, not the route's.bLowLatencyModeon throughout. The table'sfgMultiplierreads 1 in the session that held ×2 for 105 seconds: the row keeps the last value read, and that session ended in a menu — a row that lists what was seen would not mislead. D137's first Cyberpunk batches: eight of them, 85–221 ms, every oneinstallin one apply; beta.46's 0.61 s did not recur. (f) Not Direct3D 12: Crown & Coin (213) and Psycho-Sleuth (214), both Direct3D 11 — oneLATENCY no Direct3D 12 deviceline each, nothing after it, the session's line reads not read — not Direct3D 12. Direct3D 12 with no NVIDIA library: Dread Fields (215) —the game has not loaded nvapi64.dll, said once, not read. The three ran at the same time and were recorded apart. (h) held in all five: no fault counted, nothing dropped, normal exits, nothing in Windows' application log. A correction to the paragraph above: the Agent's samples are 1.32 s apart, not one second (thet_msseries; so in every session looked at back to beta.42, whilesensor_blobs.hzsays 1.0 — not looked into), so the shares are 227 of 258, 24 of 39 and 823 of 846 samples, and the gaps are the first seconds of a session. The owner's answer on the GPU render line (2026-11-14): read the driver's active time — planned as one train with what else is open. Left of this item: (d) Reflex off in the game's menu, (g) off means off, and the owner's word on how the games felt; the owner runs what is left once, with that train's release. They are (d), (e) and (g) of item 46. -
beta.48 — the driver's own GPU times, the multipliers seen, samples a second apart; and what item 45 left (D142–D146). One batch, as the owner asked: any Direct3D 12 games that use Reflex, as many as wanted, with Advanced metrics on — not first on a game under the user-mode exception's trial (D38). Then say check; the sessions are read from a copy of the ledger and the logs. (a) The update shows the terms window once, with Privacy Policy 2.21 and Disclaimer 2.17. (b) Phantom Blade Zero and Cyberpunk 2077 again, a few minutes of play each: on the Advanced page, under Latency, a second chart — the graphics card's time per frame, as the driver works it out — with two lines, GPU active render and GPU frame time; and the old line reads GPU render, start to end (idle time included). (c) A session with both a menu and frame generation: the table's
fgMultiplierrow lists both — 1, 2, or 1, 3 — not the last one. (d) Reflex switched off in a game's menu, if a game lets you (item 45 (d)): say what the session's line reads. (e) Off means off (item 45 (g)): switch Advanced metrics off, start a game afresh, play a minute, close it; switch it back on afterwards. (f) Any other games of the batch — Clair Obscur, Black Myth: Wukong, Hogwarts Legacy, Dread Fields, a Direct3D 11 game: nothing to do but play and close them. (g) How the games felt with the option on — a hitch once a second is the thing to look for; nobody but the player can say it. Read from the ledger, nothing for the owner to do: the samples of every session are one second apart, not 1.32 s, andhzsays what they were. What each outcome means, written before the run. The two lines are there, and active render is shorter than GPU render: D142 did what it was for; in Phantom Blade Zero the reading of 2026-11-14 expects GPU frame time near the 16 ms the old line showed, and active render well under it — if active render is as long as the old line there, that reading was wrong, and the span is long for another reason: say the numbers. The second chart is not there, and the seven lines are: the driver gave zero for both figures in every frame — nothing is wrong with the read, and the texts already say a driver may give neither; say which game. One line and not the other: the same, for one figure. Active render longer than GPU render, start to end: they are the driver's numbers and are shown as reported — say which game and by how much.fgMultipliershows one value in a session that had both: the driver's status did not change with the menu in that game, or the mask is wrong — say the game; the log'sLATENCYlines and the frame-generation mix of the session tell the two apart. Samples still 1.3 s apart: the period is not kept — the poll takes longer than the interval, or the change is not in the build: stop and say so. Samples a second apart and the Agent's processor use visibly higher: a poll that took a third of 1.32 s now takes a third of a second — say so; where that time goes is not established (§Left open). (d) reads "read": the driver reports frames with the game's Reflex off — both that and asked, and the driver reported no frame are possible and neither is wrong. (e) the log has aLATENCYline: off does not mean off — say so at once, with the log. A fault, a freeze, a game closing by itself, a hitch every second, or a session that says stopped: as item 45 says for each — say so at once. Run 2026-11-14, 12:49–14:12, and read the same afternoon from a copy of the ledger and the logs: ten sessions on beta.48 — Phantom Blade Zero seven times (217, 219, 220, 223–226), Cyberpunk 2077 three times (218, 221, 222). Every one tier 1, exit code 0, no fault counted, nothing dropped; nothing in Windows' application log. (Session 216, an hour of Phantom Blade Zero, was still beta.47 — it ran while the release was cut — and is 1.32 s apart like the ones before it.) The samples are a second apart: the median gap is 996–1002 ms in all ten (session 223: 2 294 of 2 394 gaps round to 1.00 s, the rest lie between 0.80 and 1.27 s), andhzreads 1.000–1.017. (a)legal_acceptanceholds Privacy Policy 2.21 and Disclaimer 2.17, accepted at 12:48:40. (b) Both figures were given by both games, in every frame report: in the nine sessions with the option on, every sample that has a GPU render span has both (3 834 of 3 834). Phantom Blade Zero is what the reading of 2026-11-14 expected: at 60 FPS (217) the span's median is 16.39 ms, GPU frame time 16.67 ms and GPU active render 9.59 ms; in the menu (224) 16.39 / 16.67 / 2.77; at 91 FPS (225) 11.49 / 11.79 / 10.05; with frame generation ×5 (223) 15.67 / 15.88 / 14.08. So in that game the span is the time from one frame to the next less a third of a millisecond, whatever the card did in it, and active render is never longer than it (0 of 3 406 samples). Cyberpunk 2077 is the outcome written above as "active render longer than GPU render, start to end": without frame generation it is longer at 157 of 158 samples (218: medians 3.17 against 2.79 ms, frame time 6.02) and at 48 of 48 (221: 2.03 against 1.82, frame time 2.37); with frame generation ×2 (222) it is shorter at all 222 (4.85 against 6.35, frame time 6.67). Shown as reported. Why is not established, and two things could do it: the two are averages over different frames — the span over every summed frame, one of no length included (the smallest mean span of a sample there is 0.5 µs, the smallest active time 0.29 ms), active render over the frames that gave one — or the driver counts work the two marks do not enclose. The ledger cannot tell them apart; a count of the frames whose span has no length would. (c)fgMultiplierreads 1, 2 in Cyberpunk 2077 (222: ×2.0 for 69 % of it), 1, 5 in Phantom Blade Zero (220: ×5.0 for 71 %, 30 → 151 FPS; 223: ×5.0 for 95 %, 63 → 316) and 1 in the seven sessions that generated nothing. (d) Session 221 (Cyberpunk 2077, 59 s of menus at 421 FPS) is the only Cyberpunk session whosebLowLatencyModereads on and off — 218 and 222 read on, as 211 and 212 did — and is taken to be the one where Reflex was switched off; the owner has not said which it was. Its line reads read, 48 of 57 samples carry a report, every one from the first on, and the slowest call took 19 µs: the driver goes on reporting frames. (e) Off means off, on a real game for the first time: session 226 (telemetry.advanced0) has nosession_advancedrow and 19 series where the others have 240; its log has ten hooks, none of the ones Advanced metrics adds, and noLATENCYline. The setting was still off when the ledger was copied. (f) No other game was in the batch. The read itself: onereading the driver's latency reportline a session, 1.4–6.7 s after the attach, in the same two files, and none after it; the slowest call of a session 18–123 µs; no latch. The install batches took 75–191 ms, every oneinstall. Samples with no report: after a session's first report, 0.4–7.3 % of its samples carry none (1 of 223 in 222; 134 of 2 377 in 223, minutes of four in five there). They are not the sensor library's ticks (25 of the 134 fall on one, 24 just after one). What the code says, not measured: the watchdog ticks once a second and arms a read when a second has passed since the last arm, so a tick that comes a moment early waits for the next one — the reads are a second apart or two, the samples exactly one. Nothing is lost by it; a sample shows a gap. (g) The owner's answer, asked whether a game hitched once a second with the option on (2026-11-14): no hitch. What the frames say, in the sessions without frame generation: a frame three times the median of the 120 before it and 8 ms longer comes 0.33 times a second with the option on (225) and 0.32 with it off (226), and such frames do not gather at a period of one second (vector strength 0.05–0.10 where chance gives 0.10–0.20; 217, 218 and 222 the same). Sessions with frame generation cannot be judged that way. Not seen in the ledger: what the page looked like, and the Agent's processor use now that a poll comes every second. Read, and (g) answered: (a)–(g) each have their answer;whether session 221 was (d) is inferred, and the owner's to say(d) is withdrawn in the next paragraph. The owner has not said the item is passed. Eight more sessions the same afternoon (227–234), read at once, and three things the owner said. Still beta.48: Cyberpunk 2077 three times (227 with the option off — noLATENCYline, no row; 232 mostly menus; 233 five minutes without frame generation), Phantom Blade Zero three times (228, 231, 234), Clair Obscur: Expedition 33 twice (229 with frame generation ×3 for 79 % of it, 230 without). All tier 1, exit code 0, no fault, nothing dropped; samples a second apart; slowest calls 10–29 µs;fgMultiplier1, 3 in 229. The owner's words: Reflex is checked together with frame generation — without frame generation the game does not switch Reflex on; a value that reads on and off is the NVIDIA App's override (the App's page for Phantom Blade Zero: Low Latency Mode — Ultra); and a session with Reflex off may be read. So (d) above is withdrawn as written: session 221 was not "the one where Reflex was switched off in a menu", and nothing here says what itsbLowLatencyModeon and off was. What the sessions do read: Clair Obscur without frame generation hasbUseGameSleepoff throughout (230) and with ×3 on and off (229) — the game's own Reflex goes with its frame generation, as the owner said; Phantom Blade Zero hasbLowLatencyModeoff throughout in 234; and in both the read is what it is with Reflex on — onereadingline, a report at every read, the two new figures in every one. Cyberpunk 2077 without frame generation again has active render longer than the span (233: 3.40 against 3.13 ms at 292 of 296 samples), and its menus do not (232: 0 of 126; active 0.39 ms inside a span of 1.18). The holes are larger in short sessions: 11.3 %, 16.2 % and 11.1 % of the samples after the first report in 228, 229 and 231; 6.0 % in 230; 0.8 % in 232. And "nothing is lost by it", above, was wrong: it was written on a reading of the Overlay alone. The Agent kept one set of readings until a sample carried it and overwrote it — a publication that landed just after a sample left that sample without, and the set that had waited was replaced at the next return to step (46 of session 223's 134 holes are exactly five samples apart). The Overlay's part is the other half: its ticks were a second and their own work apart, and a tick the loader woke published the read and armed none. Both are mended in 0.1.0-beta.49 (D150); neither is measured in a game yet. -
beta.49 — whose the difference is in Cyberpunk 2077's GPU times; and the holes (D148–D151). One batch, in pairs: the same game with frame generation off and with it on, Advanced metrics on. Reflex is not switched by hand — it goes with frame generation. Not first on a game under the user-mode exception's trial (D38). Then say check; the logs and a copy of the ledger are read. (a) The update shows no terms window: no legal text changed. (b) Cyberpunk 2077: six minutes or more of play without frame generation, in a scene like session 218's; six minutes or more with frame generation ×2; two minutes of menus only. (c) Phantom Blade Zero: six minutes or more without frame generation — the control — and six or more with. (d) About eight short sessions, three minutes each, any Direct3D 12 game that uses Reflex: the step between the game's side and the Agent's is different in every session, and one long session shows one of them. (e) One session with Advanced metrics off; switch it back on afterwards. (f) What Low Latency Mode is set to for Cyberpunk 2077 in the NVIDIA App — a word is enough. (g) How the games felt, as always. A game closed by itself loses its last batch of counts, under a minute: that is why six minutes and not two. What each outcome means, written before the run. The log's
LATENCY_FRAMESbatches each carry the state they belong to, so every one is read as this state, these counts. Cyberpunk without frame generation: nearly every frame that has both is in "active longer than span", and their mean span is near the 2.8 ms the chart shows — the difference is the driver's: it counts work the two marks do not enclose. The numbers are shown as reported and the label "idle time included" is what is wrong for that game: the owner decides its wording. "Active longer" is a minority whose spans are next to nothing, the rest have active within the span, and spans of no length or of a microsecond are about as many as that minority — the difference is ours: the span's mean is pulled down by frames that have none. The owner decides whether the mean is taken over the frames that have a span. Both heaps are large, with real spans — both; the heaps' sums give the like-for-like figure, and it is said with them. "GPU span absent" is not zero — those reads published no GPU point at all, and were never in the comparison. Phantom Blade Zero shows many frames in "active longer" — suspect the count before the driver: say so. The counts differ between a batch withbUseGameSleepon and one with it off, in the same game — that is the owner's point, measured: say the two side by side. The batches say a thousand milliseconds a read and as many periodic ticks as reads, and every session has next to no sample without a report — D150 did what it was for. The log says a thousand milliseconds a read and some sessions still lack a report at a steady share of their samples — the Agent's rule is not the whole of it: say the sessions and the share. The log says more than a thousand milliseconds a read — the Overlay is still uneven; the line's tick counts say whether the loader was waking it. (e) has aLATENCYorLATENCY_FRAMESline — off does not mean off: say so at once, with the log. A fault, a freeze, a game closing by itself, a hitch every second, or a session that says stopped: as item 45 says for each — say so at once. Run 2026-11-14 (sessions 236–245, ten on 0.1.0-beta.49), read the same day from a copy of the ledger and the Overlay's logs. All ten tier 1, exit code 0, no fault, nothing dropped. Phantom Blade Zero twice (236 without frame generation, 1 108 s; 237 with ×2, 811 s), Kingdom Come: Deliverance II (238), Clair Obscur (239), Black Myth: Wukong (240), Lies of P (241, and 245 with the option off), Hogwarts Legacy (242), Dying Light: The Beast (243), Cyberpunk 2077 (244). 239 and 240 ran at the same time, and so did 241, 242 and 243. (a) No new acceptance row after the update: the terms window did not appear. (b) Cyberpunk 2077 was one session of 125 s without frame generation (374 FPS); ×2 and the menus were not run. It is enough for the question. 88 reads in one state — low-latency mode on, the game sleeping, ×1 — summed 5 394 frames: 4 917 in "active longer than span", mean span 1 571 µs, mean active 1 849 µs; 96 within (3 866 / 3 431 µs); 381 with a span of no length and an active time; none absent, none refused. So the difference is the driver's: on frames that have a real span, its active time is 278 µs (18 %) longer than the two marks are apart. A small part is ours as well — 7 % of the frames have a span of no length and pull the span's mean down (the stored means are 1 892 and 2 138 µs). With frame generation on it is not measured on this build (0.1.0-beta.48's means: never longer). (c) The count is not what is wrong: in the six other sessions that reported (five games), not one frame of 129 900 is in "active longer", and no span is absent or of no length. Phantom Blade Zero: without frame generation 63 123 frames, span 16.4 ms, active 11.1 ms; with ×2 21 209 frames, span 33.2 ms, active 12.6 ms. (d) The holes: in batches of twenty reads or more a read took 1 000.94 ms (236), 997.18 (237), 999.99 (242, 244), and up to 1 013 ms in the sessions that shared the PC with another game. Samples without a report: 236 — 40 of 1 106, 39 of them in the first 46, while the game started; 237 — 36 of 809, in the first 42 and the last two; 244 — 9 of 123, in the first ten. Before, they were spread through a session (0.4–16 %). D150 did what it was for. Where two or three games ran at once the holes are blocks in which the game did not present (240: 103 of 477; 242: 80 of 402, 68 of them at its start; 243: 37 of 414; 239: 23 of 184): a read is taken on the presenting thread, so a game that presents nothing is not read — Lies of P's log has sixty reads in 189 s. (e) Off means off: session 245 has noLATENCYline and no Advanced row. The stop fired in a real game for the first time (D141): Kingdom Come: Deliverance II, 12 s after the attach, while the game was starting — the seventh read took 5 337 µs, and no further read was made; the session says so (Slow), the game ran 287 s and closed normally. No frame had been reported in those seven reads. The owner: that game has no Reflex in its settings — so there was no report to lose; the session's line says stopped where, without the slow call, it would have said the driver reported no frame. Elsewhere the slowest call was 22–235 µs. In Lies of P the driver reported no frame at all. What the states say of Reflex and frame generation (each batch carries its own): low-latency mode was on at a multiplier of 1 in Cyberpunk 2077 (88 reads), Black Myth: Wukong (253), Hogwarts Legacy (299) and Dying Light: The Beast (345); Phantom Blade Zero without frame generation sleeps through Reflex with low-latency mode off (1 062 reads) and switches it on with ×2; Clair Obscur without frame generation has both off and still reports its frames. The logs cannot say whether a game's menu or the NVIDIA App switched the mode on. NVIDIA's own guide makes frame generation need Reflex and not the reverse (spike-notes§30, Added 2026-11-14). Hogwarts Legacy gave a multiplier of 6 for seventeen reads. (f), (g) The owner, the same evening: "App reflex off, không khựng" — Low Latency Mode is off in the NVIDIA App, and no hitch. Read with (f) as it was asked, for Cyberpunk 2077: the low-latency mode its 88 reads show at a multiplier of 1 is then the game's own Reflex and not the App's override — Reflex on without frame generation, as NVIDIA's guide allows. Then shown, in two screenshots: the NVIDIA App's Program Settings for Cyberpunk 2077 have Low Latency Mode Off, set for that program (the rows that follow the global setting read "Global - …"; this one does not); and the game's own Video page has NVIDIA Reflex Low Latency: On, V-Sync off, borderless at 2560×1440, 378 FPS on the game's counter. So the driver'sbLowLatencyModeon, at a multiplier of 1, is the game's menu, seen from both sides. The owner's: the wording of the two GPU labels — idle time excluded / included does not describe a game whose active time is the longer. -
beta.50 — what a session was played with, read from real controllers (D155–D163). Everything this release shows of controllers was built and checked against data written by hand: the developer has no controller (D157). This batch is the first time any of it meets one. Not first on a game under the user-mode exception's trial (D38). Then say check; a copy of the ledger and the Agent's log are read. (a) The update shows the terms window once (Privacy Policy 2.22, Disclaimer 2.18): accept it. If a game was recorded after the update and before FrameLedger was opened, its summary says Not read in this session — that is the terms being waited for (D156), not a fault. (b) The Xbox controller: one session on its cable, one on Bluetooth, one on the wireless adapter if there is one. Five minutes each, played with the controller. (c) The DualSense: one session on its cable, one on Bluetooth. (d) Steam Input: the DualSense in a Steam game with Steam Input on for it, and the same game with Steam Input off. (e) One session, in this order, about two minutes each: only the controller; only the keyboard and mouse; hands off both; then Alt+Tab to another window and type there for a minute; then back to the game. (f) Unplug the controller and plug it back twice in one session (or switch it off and on), noting roughly when. (g) One session that starts on the Xbox controller, changes to the DualSense, and changes back. (h) A game played with the keyboard and mouse only, no controller connected. (i) A game that is not measured from inside (hooking off, or refused) played with a controller. (j) A game run as administrator while FrameLedger's Agent is not — if one is at hand. (k) One session with Settings ▸ Controllers and input off; switch it back on afterwards. (l) A Steam game's page and a page of a game from another store: the three rows at the end of Details. (m) How the games felt — the reader looks ten times a second; a hitch at that rhythm, or when a controller connects, is what to listen for. What each outcome means, written before the run. (e): the three stretches read near two minutes each in their own class, and the minute typed elsewhere is in no class — the time in front is a minute shorter than the time read — the definitions hold on real input. The minute typed elsewhere is counted as keyboard and mouse — the test for "the game is in front" is wrong for that game (a window owned by another process, a launcher): say the game;
LIMITATIONS.mdnames the case. The controller-only stretch reads as "both" — something makes keyboard or mouse input while the controller is used: Steam Input mapping it, the pad moving the pointer. Say which session; with Steam Input off (d) it should read "controller". A controller was played with and is never "in use" — look at the session's sources and the Agent's lineinput: run ended: no reports with the registration accepted means Windows did not deliver a background program that controller's reports on this PC; XInput silent means XInput answers only the program in front. Either is a route that failed, said with its counters — and the App said N/A or "not in use", never a made-up share. The Xbox controller reads "wired" on its cable, and four levels or nothing on Bluetooth; the DualSense reads steps of ten per cent on its cable, and on Bluetooth a level only if something else had switched its full reports on — asLIMITATIONS.mdsays. Anything else is recorded and that page reworded. Steam Input on: one controller is listed, marked "also shown to games as an Xbox pad" — the fold works. Two are listed, the DualSense and an Xbox pad — it missed: give both rows' times in use. (f): the connections and drops equal the times it was done, and the marks sit where it was done — the counts are right. More — the connection flaps, or a controller that sleeps is counted as dropped: say the counts. (g): "By maker" shows both with two changes — the owner's seventh point holds. (h): "No controller was connected during this session", and the keyboard and mouse have nearly all the time in front. (i): the block is there in a session that was not hooked. (j): every share is "no input" though the game was played — Windows does not tell a program that is not elevated about input into one that is: say so, and it goes intoLIMITATIONS.mdas measured. (k): the summary says "Not recorded for this session" and the row has no input figures — off means off. (l): the Steam game says full, partial or "lists none"; the other says N/A; "Input libraries loaded" names a library after a measured session. The Agent'sinput: run endedlines: the thread's processor time over the session's length. NFR-2 leaves 0.46 % of a core; a session with a controller is the first measurement of this (20_OPEN_QUESTIONS§M17 f). Above that, say the number. A hitch every tenth of a second, a stutter when a controller connects or drops, a game that loses the controller while FrameLedger records, or a fault: switch Controllers and input off, say so, and send the Agent's log. FrameLedger opens no controller and sends nothing to one (D159) — a controller that misbehaves only while it records would contradict that and is the most important thing this batch could find.
Answered 2026-08-05, do not re-ask: remove gameguard and keep guard (approved
over a red Rules gate, with the reasoning recorded in the merge commit); vendor NVAPI
headers and amd64/nvapi64.lib; Windows 11 is the measurement scope only —
SupportedOSPlatformVersion stays at Win 10 22H2 and the D3DKMT two-OS requirement is
deferred with a written rationale.
Decisions index
Where each owner decision is recorded — the file and its section, and a label to find it by. The decision itself is the text there, not this table.
| D | Recorded in | About |
|---|---|---|
| D1 | handoff/history/p2.md |
FrameLedger.Application gains a reference to FrameLedger.Shared (A); Domain still |
| D2 | handoff/history/p2.md |
never assigned — the numbering skips D2 and D3 (§P2 says so) |
| D3 | handoff/history/p2.md |
never assigned — see D2 |
| D4 | handoff/history/p2.md |
the Agent ships --console consent grant |
| D5 | handoff/history/p2.md |
FileGameConsentStore is retired in B; the CaptureHost writes a build-tree ledger.db |
| D6 | handoff/history/p2.md |
--data-dir exists only under --console (F; 12_BUILD §Debugging), so --serve can never |
| D7 | handoff/history/p2.md |
the FR-2.4 kill switch is the FOURTH input of HookedCaptureGate, not an upstream |
| D8 | handoff/history/p2.md |
FR-11 is NOT a consent precondition in P2 |
| D9 | handoff/history/p2.md |
P2 never clears hook_blocked_reason |
| D10 | handoff/history/p2.md |
the pipe (07_IPC) is P3, not P2; --serve is watcher-driven and logs |
| D11 | handoff/history/p3.md |
the pipe's transport |
| D12 | handoff/history/p3.md |
commands join as one more producer |
| D13 | handoff/history/p3.md |
SessionProgress is a third ICaptureObserver |
| D14 | handoff/history/p3.md |
Safety_ lives in FrameLedger.Shared, once |
| D15 | handoff/history/p3.md |
the App opens ledger.db directly, under 06_DATA_MODEL §Writer ownership: it writes games' |
| D16 | handoff/history/p3.md |
the settings registry (closes §G's row, written into 06_DATA_MODEL in PR-3): ui.language |
| D17 | handoff/history/p3.md |
FL_MOCK, if the owner wants it, is --serve --mock under --data-dir only (D6's shape), so a |
| D18 | handoff/history/0.1.0-beta.3.md |
the guard has one override, and its shape is fixed |
| D19 | handoff/history/0.1.0-beta.3.md |
the DLSS preset derived from the render scale is STILL not shown |
| D20 | handoff/history/0.1.0-beta.3.md |
the bug bundle does not get the machine's hardware |
| D21 | handoff/history/0.1.0-beta.4.md |
a process an anti-cheat driver protects is TargetUnreadable, and nothing offers a way past it |
| D22 | handoff/history/0.1.0-beta.5.md |
the per-game guard override (D18) is withdrawn; a finding about the game turns its hooking off |
| D23 | handoff/history/0.1.0-beta.5.md |
Tier 2 is a held session: duration, telemetry and the reason |
| D24 | handoff/history/0.1.0-beta.5.md |
a row follows its executable to another drive letter when exactly one other root holds it |
| D25 | handoff/history/0.1.0-beta.6.md |
a file name is not an identity |
| D26 | handoff/history/0.1.0-beta.6.md |
the Agent merges two entries for one executable under two drive letters |
| D27 | handoff/history/0.1.0-beta.6.md |
other bytes at the entry's path on another letter: the entry follows them with hooking off |
| D28 | handoff/history/0.1.0-beta.6.md |
HHW is measured through an entry pointed at swiftshader\Game.exe |
| D29 | handoff/history/0.1.0-beta.7.md |
a per-entry Recording switch (games.record_sessions) and the import's known-tools list |
| D30 | handoff/history/0.1.0-beta.8.md |
strict anti-cheat rules: any .sys in the install tree, and per-title lists |
| D31 | handoff/history/0.1.0-beta.8.md |
the store half's matrix |
| D32 | handoff/history/0.1.0-beta.8.md |
games blocked by anti-cheat: hide the hooking part, and scan the library ahead |
| D33 | handoff/history/0.1.0-beta.9.md |
the user-mode anti-cheat exception (CLAUDE.md rule 2, amended) |
| D34 | handoff/history/0.1.0-beta.10.md |
the admin mode asks Windows at EVERY Agent start |
| D35 | handoff/history/0.1.0-beta.10.md |
the tested-games list comes from a COPY of the owner's ledger (scratchpad, Python sqlit… |
| D36 | handoff/history/0.1.0-beta.10.md |
legal text changes where it would become false (Privacy 2.5, Disclaimer 2.8; EULA stays… |
| D37 | handoff/history/0.1.0-beta.10.md |
each PR merges when its CI is green, then the release PR and the GPG-signed tag |
| D38 | handoff/history/0.1.0-beta.11.md |
the user-mode exception's evidence moved under the grant, as a trial |
| D39 | handoff/history/0.1.0-beta.11.md |
charts across a game's sessions: both — Sessions at a glance on the Sessions tab, and A… |
| D40 | handoff/history/0.1.0-beta.11.md |
Delete all sessions: both places — the game's page and Settings ▸ Data |
| D41 | handoff/history/0.1.0-beta.11.md |
Refresh does all three: reload the library, offer the games the stores installed since,… |
| D42 | handoff/history/0.1.0-beta.11.md |
the library switches between a grid that fills the window and a list (ui.library_view) |
| D43 | handoff/history/0.1.0-beta.12.md |
the game's memory is measured from OUTSIDE the game, in both tiers |
| D44 | handoff/history/0.1.0-beta.12.md |
a user guide in English, guide/, rendered in the App (Help ▸ User guide), linked from t… |
| D45 | handoff/history/0.1.0-beta.12.md |
the legal split |
| D46 | handoff/history/0.1.0-beta.12.md |
documentation is corrected in place (struck, dated) with an index, docs/README.md; hist… |
| D47 | handoff/history/0.1.0-beta.14.md |
the update channel follows the running copy |
| D48 | handoff/history/0.1.0-beta.14.md |
the guard's narrow fix, both halves |
| D49 | handoff/history/0.1.0-beta.14.md |
all four metric groups |
| D50 | handoff/history/0.1.0-beta.14.md |
the managed binaries' identity |
| D51 | handoff/history/0.1.0-beta.15.md |
the scan set cuts a parent/child link only when it is proven wrong: both creation times… |
| D52 | handoff/history/0.1.0-beta.15.md |
the App's --data-dir is a viewer over a copy: no Agent is started or contacted (its com… |
| D53 | handoff/history/0.1.0-beta.17.md |
the wiki's source is the repository |
| D54 | handoff/history/0.1.0-beta.17.md |
the wiki's End-user half is the user guide, one source: it grows past D44's eight pages… |
| D55 | handoff/history/0.1.0-beta.19.md |
a game you uninstalled leaves the library by itself when it has no session (amends D41'… |
| D56 | handoff/history/0.1.0-beta.19.md |
an NW.js runtime is the import's game: an executable beside nw.dll + package.json ranks… |
| D57 | handoff/history/0.1.0-beta.21.md |
the four itch "launchers" are malware: the documentation is corrected, the import is no… |
| D58 | handoff/history/0.1.0-beta.21.md |
Wuthering Waves is on the title list (Steam 3513350, Anti-Cheat Expert), beside the fix… |
| D59 | handoff/history/0.1.0-beta.21.md |
Play, in two modes switched in Settings: "1: press Play → the platform opens → it runs;… |
| D60 | handoff/history/0.1.0-beta.23.md |
a game's artwork is what is already on the PC |
| D61 | handoff/history/0.1.0-beta.23.md |
the band takes the artwork's colour as far as every text on it reads: primary and secon… |
| D62 | handoff/history/0.1.0-beta.24.md |
the mix: every frame-generation state a session held, with its share, never averaged |
| D63 | handoff/history/0.1.0-beta.24.md |
the NVIDIA App's override is the quality mode where the driver reports it applied |
| D64 | handoff/history/0.1.0-beta.24.md |
DLSS labels are evidence-bound: versions and folder class, DLSS 4/4.5 only when shown, 5 only loaded |
| D65 | handoff/history/0.1.0-beta.25.md |
FSR's quality mode through ffxQuery — deferred from beta.24, built in beta.25; none at a dynamic resolution |
| D66 | handoff/history/0.1.0-beta.24.md |
the long documents are split; every original path stays as the index of its parts |
| D67 | handoff/history/0.1.0-beta.24.md |
SonarCloud stays on Automatic Analysis with .sonarcloud.properties; the owner marks in its UI |
| D68 | 13_CI_CD.md §SonarCloud |
SonarCloud is analysed from CI (ci.yml's sonarcloud job, SonarQube.Analysis.xml), with coverage; replaces D67 |
| D69 | 19_SAFETY_AND_ANTICHEAT.md §User-facing consent |
Enter enables once the consent phrase is typed exactly; before it Enter does nothing |
| D70 | 08_UI.md §Games › Trend |
the hardware-change markers are numbered badges, their changes listed under each chart, with a tooltip |
| D71 | 13_CI_CD.md §Dependabot and the NuGet audit |
Velopack and vpk 1.2.161 in beta.30 (item 24(d)'s Velopack half) |
| D72 | 13_CI_CD.md §Dependabot and the NuGet audit |
beta.31 takes the remaining updates inside the seven-day cooldown: .NET 10.0.14 packages, Markdig 1.5.0, CsWin32, Meziantou, coverlet 10.1.0, Catch2 3.16.1 |
| D73 | 12_BUILD.md §The alpha line |
the alpha line: a released beta's source on a prerelease .NET (.NET 11 RC3 first), on the alpha branch and Velopack's alpha channel; it replaces the beta, shares its data folder and copies the ledger before it first opens it |
| D74 | 08_UI.md §First-run flow |
the alpha's warning: the Alpha notice with its own tick box in the Legal Gate, the alpha's Agent waiting for it, an ALPHA badge and a banner, the update channel locked |
| D75 | ../legal/EULA.md §2B |
EULA 1.6 and Disclaimer 2.12 name alphas beside betas; the Alpha notice 1.0 approved with the plan |
| D76 | 12_BUILD.md §The alpha line |
alpha.1 is a retarget only: net11.0, C# 15 by LangVersion latest, three runtime-serviced packages; no preview feature, no C# 15 syntax |
| D77 | spike-notes/25-xbox-gdk.md |
the Xbox titles measured first, by package activation, read-only, each closed by its window; the decision table before the run |
| D78 | 19_SAFETY_AND_ANTICHEAT.md §The target must be able to take the Overlay |
GDK games only; an app-container (UWP) process is refused as TargetAppContainer, Tier 2 |
| D79 | 05_DETECTION.md §Platform signatures & metadata |
the platform is "Xbox" (xbox), in full: import, artwork, Play, capture, detection, docs and legal |
| D80 | 08_UI.md §Games |
Play on an Xbox game always activates its package, in both modes; the Agent answers PackagedGame and records it in attach mode |
| D81 | 20_OPEN_QUESTIONS.md §G |
title lists stay keyed by Steam id; an Xbox copy is matched by everything but that entry |
| D82 | handoff/history/0.1.0-beta.33.md |
alpha.2 right after beta.33; on RC3 unless the train reaches it after .NET 11 ships (then SDK 11.0.100, packages 11.0.0) |
| D83 | 05_DETECTION.md §DLSS generation |
the NVIDIA App's Dynamic frame generation, reported applied by the driver in a session where DLSS Frame Generation was identified, is DLSS 4.5 (amends D64) |
| D84 | 05_DETECTION.md §DLSS generation |
DLSS 5 heads the DLSS line where its neural rendering was measured running (kFeatureDLSS_NR, dlss_nr_pct); loaded only reads "runtime loaded" (amends D64) |
| D85 | 08_UI.md §Games, §Compare |
filters: Games — store, engine, state, installed, played; Compare — game, tier, frame generation (no period); Compare lists every session |
| D86 | 08_UI.md (the shell) |
the left pane's selected item keeps its label: our copy of WPF UI 4.3.0's LeftFluent item template |
| D87 | handoff/history/0.1.0-beta.34.md |
alpha.3 right after beta.34, on RC3 (before .NET 11's release, 2026-11-10) |
| D88 | ../ACCESSIBILITY.md |
the accessibility statement at the root, under Help ▸ Accessibility and on the wiki: WCAG 2.2 AA through WCAG2ICT is a goal, never a claim; reports by severity, no promised times |
| D89 | 08_UI.md §Screen readers |
what appears is said to a screen reader — notices, the agent's and the update's banners, the snackbars, a game page's notice, Database maintenance's results — while FrameLedger's window is active |
| D90 | 08_UI.md §Screen readers |
page titles heading 1, section titles heading 2; every chart named with where its numbers are; no series told apart by colour alone |
| D91 | 08_UI.md §Contrast |
Windows contrast themes are followed, whatever Settings ▸ Theme says |
| D92 | handoff/history/0.1.0-beta.35.md |
beta.35 in this train, no alpha; alpha.4 is the move to .NET 11's release (SDK 11.0.100, packages 11.0.0), a task of its own after 2026-11-10 |
| D93 | 13_CI_CD.md §Qodana |
Qodana Community for .NET from a workflow of its own (the organisation's licence is a 30-day trial, so not the Rider linter): a gate of zero problems, advisory; an inspection is switched off only in .editorconfig, with its reason |
| D94 | 12_BUILD.md §The main line's .NET |
the main line moves to .NET 11 with 0.1.0-beta.37, the day after it shipped; condition (a) of 20_OPEN_QUESTIONS §G's table — two alphas on the released runtime — set aside by the owner, not met |
| D95 | 02_SPEC.md NFR-8 |
Windows 10 22H2 is not blocked, and is stated as untested and unsupported (Microsoft supports .NET 11 on Windows 11); a processor needs SSE4.2 and POPCNT |
| D96 | 13_CI_CD.md §C# 15 and the analyses |
C# 15 on the main line from beta.37, a construct only where the build, CodeQL and Qodana read it — none of the four yet (Qodana's engine reads none, 2026-11-11), so beta.37 takes .NET 11's API and no syntax; no preview feature |
| D97 | ../legal/ALPHA_NOTICE.md |
an alpha is "a beta's source built to try a newer version of .NET, at times a prerelease one": EULA 1.7, Disclaimer 2.14 (with a paragraph on Windows and the processor), Alpha notice 1.1, approved with the plan; the App says "a prerelease .NET" only where the runtime is one |
| D98 | 12_BUILD.md §The alpha line |
alpha.4 is beta.37's source on .NET 11.0.0, and then the alpha line rests until a newer .NET has a preview; a resting alpha tells its user to install the beta |
| D99 | 13_CI_CD.md §Qodana |
Qodana for .NET on the Ultimate licence, in two reports from the start: the managed code to the Qodana Cloud project frameledger, the C++ to frameledger-cpp |
| D100 | 13_CI_CD.md §Qodana |
an inspection is switched off where the engine that raised it reads — ReSharper's in .editorconfig, the rest in qodana.yaml (amends D93); hints are off as a severity; in code loaded into a game only defects are fixed |
| D101 | 18_GPU_VENDOR_APIS.md §Advanced metrics |
"Thông số nâng cao" — Advanced metrics: the option telemetry.advanced, off by default, and off means nothing more is read or stored and the navigation item is hidden; everything reachable inside a game follows in stages, four trains A–D |
| D102 | 18_GPU_VENDOR_APIS.md §Advanced metrics |
stored in full with the session, in tables of their own (machine_profiles, session_advanced, schema 0023) and not in columns of sessions; series under adv. names with NaN, not −1, for a tick with no reading |
| D103 | 18_GPU_VENDOR_APIS.md §Advanced metrics |
LibreHardwareMonitor's CPU, memory, motherboard and storage groups only when the Agent already runs as administrator with PawnIO — the page links to that setting and never asks; power-supply and fan-controller groups refused, battery deferred |
| D104 | 18_GPU_VENDOR_APIS.md §Advanced metrics |
identifiers are never read: the card's serial number and unique id, a display's EDID, the list of programs that are encoding |
| D105 | 18_GPU_VENDOR_APIS.md §Advanced metrics |
the navigation item is the pane's last; Ctrl+1–5 keep their pages and Ctrl+6 opens it only while the option is on |
| D106 | 18_GPU_VENDOR_APIS.md §Advanced metrics |
a .partial chunk of an unknown type with a right checksum is skipped, where it ended the read |
| D107 | 18_GPU_VENDOR_APIS.md §Advanced metrics |
with no game running the Agent reads sensors only while the page is open |
| D108 | 18_GPU_VENDOR_APIS.md §Advanced metrics |
"never call a setter" is a build gate: every NvAPI_* call of the bridge is held to a committed list |
| D110 | 20_OPEN_QUESTIONS.md §M16 |
the L2 telemetry layer's cost is measured in a real Agent before anything is changed (tools/agent-cost.ps1); what to do about the number is asked after |
| D117 | 02_SPEC.md NFR-2 |
asked with the measurement in hand (1.93 % off, 2.04 % on): NFR-2 is amended to ≤ 2.5 % of one core during capture; the sensors keep one reading a second and no code changes |
| D111 | 18_GPU_VENDOR_APIS.md §Train B |
inside the game too, off means nothing more is read: the Overlay reads new fields and installs new hooks only while the Agent's control word says the session records Advanced metrics |
| D112 | 18_GPU_VENDOR_APIS.md §Train B |
slInit is not hooked in train B; if ever, never applicationId, projectId or the paths |
| D113 | 18_GPU_VENDOR_APIS.md §Train B |
train B is three releases: beta.40 fields of calls already hooked (no new patch site), beta.41 slSetConstants + ffxConfigure, beta.42 slGetFeatureVersion + slGetFeatureRequirements; each waits for the owner's run of the one before; C is beta.43, D beta.44 |
| D114 | 18_GPU_VENDOR_APIS.md §Train B |
the field of view is stored as a session's range, never as a series |
| D115 | 17_HOOK_ENGINE.md §Which struct version carries which field |
a tail member of a vendor struct is read only where the upstream tags prove it is there |
| D116 | 18_GPU_VENDOR_APIS.md §Train B |
"never the camera" is a build gate: tools/overlay-fields-check.ps1 |
| D118 | 18_GPU_VENDOR_APIS.md §Train B |
told that the sensor-library fix would take the number D113 gave train B's second release, the owner chose to release it at once as 0.1.0-beta.41: the train's second and third releases are beta.42 and beta.43, train C beta.44, train D beta.45 |
| D119 | 07_IPC.md §Region 5 |
FLT_MAX (or +infinity) in an FSR depth plane is stored and shown as "infinite" — three engines pass it for the plane at infinity; for FSR only: for Streamline FLT_MAX is the "not set" sentinel and stays absent |
| D120 | 03_METRICS.md §Upscaling |
a session's upscaler is the technology named on the most samples, and its quality and render size are read from that technology's samples — not the first one named, with the others' values beside it |
| D121 | HANDOFF.md §NEXT |
Cyberpunk 2077 was set to FSR upscaling and FrameLedger named none: a detection gap, to be investigated — which first needs a native log that survives the game's exit |
| D122 | 18_GPU_VENDOR_APIS.md §Train B |
train B's second step is split: beta.42 has no new patch site (D119–D121 and the patch registry's hardening); beta.43 is the two new hooks, begun only after the owner has run Cyberpunk on beta.42 and its log was read. The third release is beta.44, train C beta.45, train D beta.46 |
| D123 | 19_SAFETY_AND_ANTICHEAT.md §Pre-injection checks, check 1 |
a module list that changed while the guard read it is read again, at most three times, before it refuses — five real sessions on one PC in a week had ended as a safety unhook with no frame recorded; a list that never settles still refuses, and nothing else about what refuses changed |
| D124 | HANDOFF.md §NEXT |
the guard's re-read (D123) ships with 0.1.0-beta.43 and not as a release of its own — the train's numbers do not move a third time; until then a launch can still be lost that way on beta.42 |
| D125 | 17_HOOK_ENGINE.md §Hook inventory |
an FSR UPSCALE is counted at the first source that saw one and at no other — a precaution for a loader that hands a dispatch on to the leaf's export (Cyberpunk 2077's 2.3.0 does, for frame generation); no title run so far upscales through one |
| D126 | 19_SAFETY_AND_ANTICHEAT.md §Crash & stability safety |
the count of early abnormal ends starts again when the user switches hooking on (the consent grant sets it to 0) — it was never set back, so a game once switched off was switched off again by every single such end, under a reason that says "twice" (Lies of P, 2026-11-12) |
| D127 | 19_SAFETY_AND_ANTICHEAT.md §Crash & stability safety |
a fault while a game is closing, which a hooked session does not see (Hogwarts Legacy, the driver's _nvngx.dll, hooked or not), is written down and not changed in 0.1.0-beta.44 — seeing it would end a user-mode exception for a fault no hook caused; a decision of its own |
| D128 | 18_GPU_VENDOR_APIS.md §Train B |
a field of view over π is shown as the game gave it, with a row that says it is not radians, and is never converted — Cyberpunk 2077 gives Streamline degrees; converting would store a guess at the unit as the game's word |
| D129 | 18_GPU_VENDOR_APIS.md §Train B |
slInit is not hooked at all — asked to reopen D112 and shown that no shipped mode is in the game in time (launch mode waits for the presentation runtime, no patch is ever made on a game's thread, an Advanced-only hook waits for the Agent's request), the owner kept it out; a hook there would be a patch that reads nothing |
| D130 | 18_GPU_VENDOR_APIS.md §Train B |
six more Streamline core calls are hooked in one release, 0.1.0-beta.45 — slIsFeatureSupported, slIsFeatureLoaded, slSetFeatureLoaded, slAllocateResources, slFreeResources, slShutdown; trains C and D come after it, and train C's spike is written beside it as a document |
| D131 | 17_HOOK_ENGINE.md §Hook inventory |
the adapter a game asks slIsFeatureSupported about (sl::AdapterInfo: a LUID, or a Vulkan physical device) is never read — the feature's id and the result only; a build check refuses the struct's member names in code loaded into a game |
| D132 | 20_OPEN_QUESTIONS.md §M14, CLAUDE.md rule 4's note of 2026-11-13 |
Reflex route D goes to a spike on hook-harness and a stub first — and the ruling a go needed: calling a driver's read-only getter with the device of the swap chain the Overlay hooks is inside rule 4. No real game before the owner has seen the result |
| D133 | 20_OPEN_QUESTIONS.md §M14, spike-notes/30-reflex-latency.md |
Reflex route C (the Overlay calling slReflexGetState) is refused; the no-injection ETW route stays closed, and §G with it |
| D134 | 17_HOOK_ENGINE.md §Unhooking, Batches |
installs and restores are batched through MinHook's queue — one stop of the game's threads for a batch, not one a patch — in a pull request of its own, measured, released alone (0.1.0-beta.46) |
| D135 | 17_HOOK_ENGINE.md §Hook inventory |
slAllocateResources keeps its patch although no game called it in the first six sessions; looked at again when there are more |
| D136 | 20_OPEN_QUESTIONS.md §M14, spike-notes/31-reflex-route-d-harness.md §The question for the owner |
Reflex route D goes on to one real title, Cyberpunk 2077 — a plan of its own first, no code before it is approved, and no release carrying it before item 44 (d) has been run |
| D137 | 17_HOOK_ENGINE.md §Unhooking, Batches |
the PATCH_BATCH line says how a batch ended — one apply, or finished one patch at a time — after two batches in real games took 0.61 s and 1.26 s and the log could not say which; with the next release, not one of its own |
| D138 | 20_OPEN_QUESTIONS.md §M14, handoff/history/0.1.0-beta.46.md §The train after 0.1.0-beta.46 |
the Reflex read has no switch of its own: it is part of Advanced metrics — so it reaches every Direct3D 12 game that loaded the driver's nvapi64.dll, for everyone who switched Advanced metrics on; "one title" is the order of the owner's first runs (item 45), not a limit in code |
| D139 | spike-notes/31-reflex-route-d-harness.md §The leg with a sleep |
before any Overlay code the probe runs a leg with NvAPI_D3D_SetSleepMode and NvAPI_D3D_Sleep — writes, in the probe's own process, on its own device, in no shipped binary |
| D140 | 20_OPEN_QUESTIONS.md §M14 |
an nvapi64.dll loaded from the game's own folder — a replacement, not the driver's — is refused, and the session says why |
| D141 | 20_OPEN_QUESTIONS.md §M14 |
one call into the driver of 2 ms or more switches the Reflex read off until the game exits |
| D142 | 17_HOOK_ENGINE.md §Calls the Overlay makes into a driver |
asked on 2026-11-14 with Phantom Blade Zero's GPU render longer than its total: read the driver's gpuActiveRenderTimeUs, and with it gpuFrameTimeUs — two more members of the report already fetched, no further call |
| D143 | 18_GPU_VENDOR_APIS.md §The inventory |
the start-to-end GPU render line stays, stored and shown, under a label that says it includes the card's idle time |
| D144 | 07_IPC.md §Region 5 |
the driver's frame-generation multiplier is kept as every value a session saw, not the last one |
| D145 | ../legal/ACCURACY.md |
the accuracy statement, the README and the guide say two real games were read on one driver (they said none); Privacy Policy 2.21 and Disclaimer 2.17 with it |
| D146 | 06_DATA_MODEL.md §sensor_blobs |
the Agent's samples were 1.32 s apart under a 1 s setting (it waited the whole interval after its work): sample on a fixed period, and store the rate the samples had |
| D147 | 03_METRICS.md |
the session summary's latency fields stay N/A: the driver's total is simulation start to GPU end, not input to display |
| D148 | 17_HOOK_ENGINE.md §Native logging |
asked on 2026-11-14 with item 46's Cyberpunk 2077 numbers (active render longer than the span between the GPU marks): count the frames, and write the counts only to the Overlay's native log — no layout, schema, App or string change |
| D149 | 17_HOOK_ENGINE.md §Native logging |
told that a bug report carries the five newest Overlay logs and so these lines: no change to the legal texts — the Privacy Policy names the logs of the component loaded into games, and the lines are counts and sums of microseconds |
| D150 | 07_IPC.md §Region 5 |
the samples that carry no report are mended on both sides: the Overlay reads and publishes on a grid of one second, and the Agent no longer overwrites a reading that waits for a sample |
| D151 | 17_HOOK_ENGINE.md §Native logging |
the owner's word: Reflex is checked together with frame generation — without it the owner's games do not switch Reflex on, and a low-latency switch that reads on and off is the NVIDIA App's override. A batch of counts belongs to one state of the sleep status |
| D152 | 18_GPU_VENDOR_APIS.md §The inventory |
the two GPU labels say what each figure is — the driver's own figure, between the driver's start and end marks — not "idle time excluded / included": item 47 counted the active time as the longer in Cyberpunk 2077. Strings only; numbers and means unchanged |
| D153 | spike-notes/30-reflex-latency.md Added 2026-11-14 |
the owner's word: of Reflex it is enough to tell whether a game has it. Reflex and PCL leave train D (sl.pcl.markers stays refused), and D141's stop is not changed for a game's first seconds. My reading of one sentence; nothing shipped is removed by it |
| D154 | 18_GPU_VENDOR_APIS.md §The trains, 20_OPEN_QUESTIONS.md §M15 |
Advanced metrics is closed: train D is not built, the ten Streamline entries that waited for a spike are not read (RefusedRoute), rule 4 is not amended for them. Nothing shipped is removed |
| D155 | 21_INPUT_DEVICES.md §The owner's request and decisions |
controllers are read by the Agent, from outside the game: no hook is added, rule 4 is untouched, and a session that is not hooked has the numbers too |
| D156 | 21_INPUT_DEVICES.md §The owner's request and decisions |
the reading is on unless switched off (capture.input_devices), and reads nothing until the Privacy Policy that describes it (2.22 or later) has been accepted on the PC |
| D157 | 21_INPUT_DEVICES.md §The owner's request and decisions |
built without a probe run on real controllers first ("Xây thẳng"): every source reports what it did, and what was verified against hand-made data only is said in each pull request |
| D158 | 21_INPUT_DEVICES.md §The owner's request and decisions |
keyboard and mouse are one class known only by GetLastInputInfo's time: no Raw Input for them, no hook, no key in the process |
| D159 | 21_INPUT_DEVICES.md §DualSense |
nothing is ever sent to a controller; a DualSense on Bluetooth has a battery level only where Steam or the game switched it |
| D160 | 21_INPUT_DEVICES.md §The owner's request and decisions |
the numbers are columns of sessions, so they are in the CSV/JSON export and in a bug bundle, and the Privacy Policy's §3A says so |
| D161 | 21_INPUT_DEVICES.md §The owner's request and decisions |
a session that is not hooked is duration, hardware telemetry, the reason — and what the Agent reads from outside the game; CLAUDE.md's sentence is amended with the pull request that makes it true |
| D162 | 03_METRICS.md §Input |
also built: switches of method and the share with no input, marks on the frame-time chart, a battery's first and last level and its rate, the kind of connection, the Steam Input note, a trend metric, a Compare row, "usually played with" |
| D163 | 21_INPUT_DEVICES.md §The owner's request and decisions |
"supports controllers" is three pieces of evidence and never a verdict: Steam's own file on the disk (no network), the input libraries the game loaded, how the game was played |
| D109 | ../legal/DISCLAIMER.md §5, §5A |
asked on 2026-11-11 with both sentences quoted: the Disclaimer goes to 2.15 with the Privacy Policy — PawnIO and the admin mode are no longer "for the CPU temperature" alone; with Advanced metrics on they also read the processor's, the memory's and the motherboard's sensors. The admin mode's disclosure follows (agent-admin-dialog/2) |
Keeping this file honest
It goes stale the moment it starts describing state. If you find yourself writing "X is
done" here, that belongs in CHANGELOG.md or §S24 — put it there and write a pointer.
The only things that belong here are: what to do next and in what order, why that
order, decisions that live in no other file, and traps.
Since 2026-10-19 (beta.24, D66) this file is split, and the split is kept up by the release: at each release
the previous START HERE section moves, verbatim, to docs/handoff/history/<version>.md and gets its row in
§How this file is split; an owner-only item the owner reports passed moves to handoff/owner-only-passed.md
with its number; a new decision gets its row in §Decisions index. tools/docs-split-check.ps1 holds the
history index and its files to each other.