Compare commits

..
29 Commits
Author SHA1 Message Date
poli0981andClaude Fable 5.2 465c1c2c63 refactor(app): the notes of a session's input need its controllers' record, not its row
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-15 05:52:25 +07:00
poli0981andClaude Fable 5.2 52939c3456 test(app): the fixture's constant is named as the format check wants
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-15 05:28:15 +07:00
poli0981 d414bb6747 Merge main (#469 squashed) into feat/input-ui: the trees are the same below this branch's own commits 2026-11-15 05:26:40 +07:00
poli0981andClaude Fable 5.2 83cdceef8f test(app): the bar's gap is named by the class that has it; one sentence for the frames session's own sensors
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-15 05:12:43 +07:00
poli0981 8e9dc000b0 Merge feat/input-facts (main with #468; the guide's repeated row) into feat/input-ui 2026-11-15 05:06:35 +07:00
poli0981andClaude Fable 5.2 e91f99279c feat(input): a session's summary says what it was played with - the shares, the controllers and their batteries, two charts, marks on the frame-time chart; Trend, Compare and the CSV export (D155-D163)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-15 05:06:28 +07:00
poli0981andClaude Fable 5.2 1c261e950a docs(guide): the settings page listed Controllers and input twice
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-15 04:57:05 +07:00
poli0981 784fbb5399 Merge main (#468 squashed) into feat/input-facts: the trees are the same below this branch's own commits 2026-11-15 04:57:00 +07:00
poli0981 e364f95166 Merge feat/input-agent (main with #467) into feat/input-facts 2026-11-15 04:35:45 +07:00
poli0981 a7ee7fd8ed Merge main (#467 squashed) into feat/input-agent: the trees are the same below this branch's own commits 2026-11-15 04:35:33 +07:00
poli0981andClaude Fable 5.2 30f064874e wip(input): the game page's details tests expect the three controller rows; the library names test without ToLowerInvariant
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-15 04:30:13 +07:00
poli0981 cd7ed8bf00 Merge feat/input-agent (main with #466) into feat/input-facts 2026-11-14 23:04:59 +07:00
poli0981 9afbeb6801 Merge feat/input-reader (main with #466) into feat/input-agent 2026-11-14 23:04:48 +07:00
poli0981 0378b7dfa2 Merge main (#466 squashed) into feat/input-reader: the trees are the same below this branch's own commits 2026-11-14 23:04:44 +07:00
poli0981 26b4b3ccb6 wip(input): what a store lists of controller support, the input libraries, the game page's three rows 2026-11-14 23:03:43 +07:00
poli0981 7dbb3c573a Merge feat/input-reader (main at 1d1d4ff) into feat/input-agent 2026-11-14 22:53:00 +07:00
poli0981 102dcdd3f1 Merge feat/input-storage (main at 1d1d4ff) into feat/input-reader 2026-11-14 22:52:58 +07:00
poli0981andClaude Fable 5.2 ac360eae01 style(input): import order in the Agent's composition; no redundant qualifier in a test (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-14 22:52:56 +07:00
poli0981 43e0c2b347 Merge branch 'main' into feat/input-storage 2026-11-14 22:48:46 +07:00
poli0981andClaude Fable 5.2 b579133128 wip(input): the Agent records what a session was played with - the switch, the terms, the legal texts
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-14 22:48:03 +07:00
poli0981andClaude Fable 5.2 f7129807e6 test(input): what InspectCode reported in the reader's tests - redundant casts, a hub disposed twice, a suppression not needed
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-14 22:20:52 +07:00
poli0981 be96564a8f Merge feat/input-storage (the inspection fix) into feat/input-reader 2026-11-14 22:19:55 +07:00
poli0981andClaude Fable 5.2 e24f09ae8a test(input): no using that makes the file's own qualified names redundant (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-14 22:19:52 +07:00
poli0981 80155d7638 Merge feat/input-storage (main at 8f24854, the Qodana fix) into feat/input-reader 2026-11-14 22:14:22 +07:00
poli0981andClaude Fable 5.2 8b4cccbb25 fix(input): an arm of XInputPad.Battery's switch said what the default says (Qodana, on #464 after it merged)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-14 22:14:11 +07:00
poli0981 2dd0e4f271 Merge main (8f24854, #464 squashed) into feat/input-storage: the trees are the same below this branch's own commit 2026-11-14 22:13:56 +07:00
poli0981andClaude Fable 5.2 e2675cd91c feat(input): the input reader, which the Agent does not start yet - raw input for controllers, XInput, the time of the last input (D155, D158, D159)
Application.Input.InputReader takes a slice about ten times a second from Infrastructure.Input.Win32InputBackend, on
the thread of InputDeviceHub, which exists only while a session has a view of it. It opens no device, sends nothing
to one and registers for no keyboard or mouse. tools/input-readonly-check.ps1 holds its Windows calls to a list.

With no controller at hand, what the reader does with one connected is not established.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-14 22:12:33 +07:00
poli0981andClaude Fable 5.2 dca740e94b feat(input): a session can store what it was played with - schema 0024, the .partial file's chunk 11, both tiers (D160)
Nine columns on sessions (the time in front and its four classes, the switches of method, the sources that answered,
the controllers as JSON) and three on games (what a store lists of controller support), ADD COLUMN only. The .partial
file gains chunk 11, so a session recovered after the Agent died keeps its readings. SessionFinalizer.Build stores
them before the tier branch: hooked, unhooked and recovered sessions alike. The input series are sensor_blobs rows
named input.*, which the sensors' read now leaves out and FindInputSensorsAsync returns.

Nothing produces a reading yet. A ledger this build has opened cannot be opened by 0.1.0-beta.49 or earlier.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-14 21:54:13 +07:00
poli0981andClaude Fable 5.2 b29993ba82 feat(input): the arithmetic of controller statistics - classes, batteries, makers, one pad seen twice (D155-D163)
Nothing reads a device yet. Domain.Input says whether an XInput state or a DualSense report is a pad in use and what
its battery is, adds a battery's readings up, counts switches and decides when two entries are one pad;
Application.Input holds one session's slices and turns them into a reading a second; InputSessionBuilder turns a
session's readings into its totals, its controllers as JSON and its timeline. TelemetrySample can carry a reading.

Every byte and reading under test was written by hand: no report from a real controller has passed through this code.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-14 21:44:42 +07:00
13 changed files with 218 additions and 484 deletions

No files matched your search

+1 -1
View File
@@ -9,7 +9,7 @@ barrier. It is written for the person who has just met one; the details for deve
FrameLedger is a desktop program: its own window, its dialogs, its document windows, the icon by the clock and the
notices Windows shows for it. It draws nothing inside a game, so it cannot make a game itself any easier to use.
*Beta software: this page describes version 0.1.0-beta.50. In the app: Help ▸ Accessibility.*
*Beta software: this page describes version 0.1.0-beta.49. In the app: Help ▸ Accessibility.*
## What FrameLedger aims for
+91 -5
View File
@@ -35,12 +35,99 @@ numeric core and does not move; the heading is the full version — corrected 20
## [Unreleased]
### Added
- **A session's summary says what it was played with** (owner decisions D155-D163): **Played with** — a bar and a table
of the time the game was in front that was played with a controller, with the keyboard and mouse, with both at once
and with no input; how often you changed between them; each controller of the session with its connection, the time
in use and connected, how often it connected and dropped, and its battery — the state it was in longest and for how
long, the first and last level, how fast it ran down; and each maker's share when two were used. Two charts follow:
**Input over the session** and **Controller battery**. On a measured session's Frametime chart, **Controller marks**
draws a controller's connections, drops and low batteries across the frames. For every session, measured from inside
or not. **Trend** has *Controller share* and *Keyboard and mouse share*, **Compare** has *Played with* and
*Controllers*, and a CSV export has an `# input:` line. The user guide has a page for it, *Controllers and input*.
Checked against synthetic sessions only: no controller had been read when this was written.
- **A session records what it was played with — a controller, the keyboard and mouse, both, or neither** (D155–D163,
the owner's decisions of 2026-11-14; *Settings ▸ Controllers and input*, on unless you switch it off). While a game
is recorded, FrameLedger's agent notes — from Windows, never from the game — which game controllers are connected
and in use, their battery level, and whether the keyboard or mouse is in use, and the session stores how the time
the game was in front divides between them, how often each controller connected and dropped, and its battery. It
works for a game FrameLedger does not measure too. **No button, stick, key or text is kept; nothing is sent to a
controller; and nothing is read until you have accepted the Privacy Policy that describes it** — after this
update, sessions recorded before FrameLedger has been opened once have no such figures. The screens that show the
figures come with the same release. Xbox-compatible controllers and the DualSense are read for use; another
controller is listed and never counted as in use. **None of this had been read from a real controller when it was
written** — it was checked against data written by hand (`LIMITATIONS.md` §Controllers and input).
- **A game's page says what is known about controller support — three things, and no verdict** (D163). *Controller
support (store)*: what Steam lists for the game — full, partial, or none — read from the Steam app's own file on
your PC when you open the page; nothing is asked of the store, and a game that is not Steam's reads N/A. *Input
libraries loaded*: which of XInput, DirectInput, Windows.Gaming.Input, GameInput and SDL the game had loaded the
last time it was measured from inside. *Usually played with*: the share of the time in front with a controller,
the keyboard and mouse, both and neither, over the sessions that recorded it. English, Vietnamese, Japanese.
- **The terms are shown once: Privacy Policy 2.22 and Disclaimer 2.18.** Both said FrameLedger never reads input.
They now say what is read — that a controller, or the keyboard or mouse, is in use — what is kept, and what never
is (`docs/legal-drift-history.md`).
- **For developers: the arithmetic of controller statistics, with nothing reading a device yet** (D155–D163, the
owner's decisions of 2026-11-14; `docs/21_INPUT_DEVICES.md`, `docs/03_METRICS.md` §Input). `FrameLedger.Domain.Input`
says whether an XInput state or a DualSense report is a pad in use and what its battery is, adds a battery's readings
up, counts switches, and decides when two entries are one pad seen twice; `Application.Input` holds one session's
slices and turns them into a reading a second; `InputSessionBuilder` turns a session's readings into its totals, its
controllers as JSON and its timeline. A telemetry sample can carry a reading; none does. **Every byte and reading
under test was written by hand — no report from a real controller has passed through this code.**
- **For developers: a session can store what it was played with — schema 0024** (D160; `docs/06_DATA_MODEL.md`). Nine
columns on `sessions` (the time in front and its four classes, the switches of method, the sources that answered,
the controllers as JSON) and three on `games` (what a store lists of controller support), ADD COLUMN only; the
`.partial` file gains chunk 11, so a session recovered after the Agent died keeps its readings; the finalizer
stores them for hooked and unhooked sessions alike; the input series are `sensor_blobs` rows named `input.*`, which
the sensors' read leaves out. Nothing produces a reading yet. **A ledger this build has opened cannot be opened by
0.1.0-beta.49 or earlier.**
- **For developers: the input reader, which the Agent does not start yet** (D155, D158, D159; `docs/21_INPUT_DEVICES.md`
§The reader). `Application.Input.InputReader` takes a slice about ten times a second from
`Infrastructure.Input.Win32InputBackend` — raw input for joysticks and gamepads delivered to a window that is never
shown, three of XInput's getters, the time of the last keyboard or mouse input, the window in front — on the thread
of `InputDeviceHub`, which exists only while a session has a view of it. It opens no device, sends nothing to one,
and registers for no keyboard or mouse. A new gate, `tools/input-readonly-check.ps1`, holds the reader's Windows
calls to a committed list and refuses, on the list or off it, a call that sends to a device, injects input or reads
a key; no other managed source and no native source may name an input function. **With no controller at hand, what
the reader does with one connected is not established**: its tests use a Windows whose answers they write, and one
suite runs it on the real Windows of the machine and asserts only that it opens, answers and closes.
### Changed
- **Advanced metrics is closed: the ten readings that were "being studied" are now "not read", with the reason**
(D154, the owner's decision). What a game sets and asks through Streamline's own functions for a feature — DLSS
frame generation's options and state, the video memory DLSS estimates for itself, the options of ray
reconstruction, Image Scaling and Dynamic Vibrance, the PC-latency markers — is reached only by handing the game
a function of FrameLedger's in place of Streamline's, which is refused. The *Sources* list says so, in English,
Vietnamese and Japanese, and the guide no longer says a later release reads more. Nothing that was read stops
being read.
- **The two lines of the graphics card's time say what each is, not which holds the other** (D152, the owner's
decision). *GPU active render (idle time excluded)* and *GPU render, start to end (idle time included)* are now
*GPU active render (the driver's own figure)* and *GPU render (between the driver's start and end marks)*, in
English, Vietnamese and Japanese, and the guide says why: in Cyberpunk 2077 without frame generation the
driver's active time is longer than its two marks are apart. The numbers are unchanged.
- **The guide's page on Advanced metrics says what two of the driver's switches mean** (`guide/12`): the latency
report is there in a game that has Reflex built in, whether Reflex is on or off in its menu; `bUseGameSleep`
says the game calls Reflex's sleep — NVIDIA asks for that even with Reflex off — and `bLowLatencyMode` is the
one that says the mode is on; frame generation needs Reflex, not the reverse. From NVIDIA's Streamline guide
for Reflex, and from the owner's ten sessions on 0.1.0-beta.49.
### Documentation
- **0.1.0-beta.50's release facts are recorded** (`docs/HANDOFF.md` §Left open by this session): the run, the eight
assets and their digests, the build id in the five native libraries, the delta, the wiki, the rehearsals, what
SonarCloud and Qodana said of the released commit — and that the release shows two dates, the owner's day in
the documents and UTC's on GitHub and in the legal texts.
- **Owner-only item 47 was run and read** (`docs/HANDOFF.md`): in Cyberpunk 2077 without frame generation the
driver's active GPU time is longer than its own two marks are apart on 4 917 of 5 394 frames (1 849 µs beside
1 571 µs) and on none of 129 900 frames in five other games — the difference is the driver's; samples without a
report are now confined to a game's start; a session with the option off has no latency line; and the stop of
D141 fired in a real game for the first time (Kingdom Come: Deliverance II, one call of 5.3 ms while it
started).
- **Streamline's programming guides for Reflex and for DLSS Ray Reconstruction (2.14.16) read against the code**
(`docs/spike-notes/30-reflex-latency.md`, *Added 2026-11-14*). Ray reconstruction was already measured the way
the guide describes; two comments in the Overlay's source and one line of `17_HOOK_ENGINE` said super
resolution and ray reconstruction run together, and they do not. `03_METRICS` and `05_DETECTION` no longer
promise "PC latency as reported by Reflex" (D147). No code changed: comments only.
## Releases
@@ -48,7 +135,6 @@ Newest first. Each file holds that release's section exactly as it stood here.
| Version | Date | Notes |
|---|---|---|
| `0.1.0-beta.50` | 2026-11-15 | [`docs/changelog/0.1.0-beta.50.md`](docs/changelog/0.1.0-beta.50.md) |
| `0.1.0-beta.49` | 2026-11-14 | [`docs/changelog/0.1.0-beta.49.md`](docs/changelog/0.1.0-beta.49.md) |
| `0.1.0-beta.48` | 2026-11-14 | [`docs/changelog/0.1.0-beta.48.md`](docs/changelog/0.1.0-beta.48.md) |
| `0.1.0-beta.47` | 2026-11-14 | [`docs/changelog/0.1.0-beta.47.md`](docs/changelog/0.1.0-beta.47.md) |
+11 -5
View File
@@ -158,10 +158,17 @@ src/
# GetLastInputInfo - it opens no device and sends nothing to one) and InputDeviceHub
# (one thread for the Agent, only while a session has a view). Read from OUTSIDE the
# game, both tiers; `capture.input_devices`, on by default.
# The App shows it since the same release: Services/InputPresentation (a session's
# "Played with", from the stored row), Controls/ShareBar with InputShareBar and FgMixBar,
# Charts/InputSeries with two charts and the controller marks on FrametimeChart,
# Services/ControllerEvidence (a game's page: three pieces of evidence, no verdict, D163).
# Controllers and input (0.1.0-beta.50, owner decisions D155-D163, docs/21_INPUT_DEVICES):
# Input/ - InputReader (a slice ten times a second over the port IInputBackend),
# InputTickAccumulator (one session's slices into a reading a tick), InputTerms (the
# reading waits for Privacy Policy 2.22, D156), the ports IInputDevices /
# IInputActivitySource; Recording/InputSessionBuilder (totals, the controllers as JSON,
# the input.* series; schema 0024). Domain/Input holds the arithmetic and the two
# parsers (an XInput state, a DualSense report). Infrastructure/Input is the Windows
# side: Win32InputBackend (raw input for joysticks and gamepads, three XInput getters,
# GetLastInputInfo - it opens no device and sends nothing to one) and InputDeviceHub
# (one thread for the Agent, only while a session has a view). Read from OUTSIDE the
# game, both tiers; `capture.input_devices`, on by default.
FrameLedger.Infrastructure/ # SQLite, shm reader, vendor APIs, injector interop, parsers,
# and Capture/ (PR-C): ShmRingAttacher/ShmCaptureSink over the
# reader, HeldProcessLivenessSource, TargetResolver (path only,
@@ -247,7 +254,6 @@ guide/ # the user guide (beta.12, D44): ~~eight~~ short
# App (Help > User guide); README.md is its contents. docs/ is for developers.
# (twelve since beta.17, D54: the screens, every setting, troubleshooting, a glossary;
# and the guide is the wiki's End-user part)
# (since 0.1.0-beta.50 also 13-controllers.md, Controllers and input)
wiki/ # the wiki's own pages (beta.17, D53): Home, _Sidebar, the developer pages. wiki.yml
# publishes them with guide/, LIMITATIONS.md and ACCESSIBILITY.md to the Wiki tab at a release;
# tools/wiki-build.ps1 assembles and checks them (build.ps1 wiki-check)
+1 -1
View File
@@ -5,7 +5,7 @@ hooking on for — and reading the graphics calls the game makes. That is why it
resolution, the upscaler, frame generation and ray tracing apart. It is also where its limits come from. This
page lists them in plain words; each item links to the document that has the details.
*Beta software: this page describes version 0.1.0-beta.50.*
*Beta software: this page describes version 0.1.0-beta.49.*
## Games it will not measure
+2 -2
View File
@@ -13,7 +13,7 @@ app too (Help ▸ User guide, Help ▸ Limitations, Help ▸ Accessibility), and
<!-- accuracy-block:begin -->
> ⚠ **What FrameLedger actually measures today — 2026-11-11.** The software is a beta; its latest
> **beta is `0.1.0-beta.50`** (2026-11-15), an unsigned installer built from that tag with its
> **beta is `0.1.0-beta.49`** (2026-11-14), an unsigned installer built from that tag with its
> checksums published beside it (alphas — experimental builds that try a newer .NET — are published apart). The source holds the desktop app
> (library, store import, charts, settings) and the background Agent, which records a session when a
> game in the library runs (unless you switched its recording off), injects only into games you enabled
@@ -225,7 +225,7 @@ Elevation is **optional — for everything.** Hooked capture is the normal path
## Install
> **The latest beta is `v0.1.0-beta.50` (2026-11-15); before it `v0.1.0-beta.49` (2026-11-14), `v0.1.0-beta.48` (2026-11-14), `v0.1.0-beta.47` (2026-11-14), `v0.1.0-beta.46` (2026-11-13), `v0.1.0-beta.45` (2026-11-12), `v0.1.0-beta.44` (2026-11-12), `v0.1.0-beta.43` (2026-11-12), `v0.1.0-beta.42` (2026-11-12), `v0.1.0-beta.41` (2026-11-12), `v0.1.0-beta.40` (2026-11-12), `v0.1.0-beta.39` (2026-11-11), `v0.1.0-beta.38` (2026-11-11), `v0.1.0-beta.37` (2026-11-11), `v0.1.0-beta.36` (2026-11-10), `v0.1.0-beta.35` (2026-11-09), `v0.1.0-beta.34` (2026-11-06), `v0.1.0-beta.33` (2026-11-03), `v0.1.0-beta.32` (2026-10-31), `v0.1.0-beta.31` (2026-10-26), `v0.1.0-beta.30` (2026-10-26), `v0.1.0-beta.29` (2026-10-25), `v0.1.0-beta.28` (2026-10-20), `v0.1.0-beta.27` (2026-10-20), `v0.1.0-beta.26` (2026-10-19), `v0.1.0-beta.25` (2026-10-19), `v0.1.0-beta.24` (2026-10-19), `v0.1.0-beta.23` (2026-10-14), `v0.1.0-beta.22` (2026-10-13), `v0.1.0-beta.21` (2026-10-13), `v0.1.0-beta.20` (2026-10-12), `v0.1.0-beta.19` (2026-10-12), `v0.1.0-beta.18` (2026-10-07), `v0.1.0-beta.17` (2026-10-07), `v0.1.0-beta.16` (2026-10-06), `v0.1.0-beta.15` (2026-10-06), `v0.1.0-beta.14` (2026-10-06), `v0.1.0-beta.13` (2026-10-04), `v0.1.0-beta.12` (2026-10-04), `v0.1.0-beta.11` (2026-10-03), `v0.1.0-beta.10` (2026-09-28), `v0.1.0-beta.9` (2026-09-26), `v0.1.0-beta.8` (2026-09-25), `v0.1.0-beta.7` (2026-09-23), `v0.1.0-beta.6` (2026-09-23), `v0.1.0-beta.5` (2026-09-22), `v0.1.0-beta.4` (2026-09-21), `v0.1.0-beta.3` (2026-09-21), `v0.1.0-beta.2` (2026-09-17) and `v0.1.0-beta.1` (2026-09-16).** They are pre-releases: read the notes of the one you install — `CHANGELOG.md` links each release's own file under `docs/changelog/` — for what it measures, what it does not yet, and how to update, before installing. A source build is `docs/12_BUILD.md`.
> **The latest beta is `v0.1.0-beta.49` (2026-11-14); before it `v0.1.0-beta.48` (2026-11-14), `v0.1.0-beta.47` (2026-11-14), `v0.1.0-beta.46` (2026-11-13), `v0.1.0-beta.45` (2026-11-12), `v0.1.0-beta.44` (2026-11-12), `v0.1.0-beta.43` (2026-11-12), `v0.1.0-beta.42` (2026-11-12), `v0.1.0-beta.41` (2026-11-12), `v0.1.0-beta.40` (2026-11-12), `v0.1.0-beta.39` (2026-11-11), `v0.1.0-beta.38` (2026-11-11), `v0.1.0-beta.37` (2026-11-11), `v0.1.0-beta.36` (2026-11-10), `v0.1.0-beta.35` (2026-11-09), `v0.1.0-beta.34` (2026-11-06), `v0.1.0-beta.33` (2026-11-03), `v0.1.0-beta.32` (2026-10-31), `v0.1.0-beta.31` (2026-10-26), `v0.1.0-beta.30` (2026-10-26), `v0.1.0-beta.29` (2026-10-25), `v0.1.0-beta.28` (2026-10-20), `v0.1.0-beta.27` (2026-10-20), `v0.1.0-beta.26` (2026-10-19), `v0.1.0-beta.25` (2026-10-19), `v0.1.0-beta.24` (2026-10-19), `v0.1.0-beta.23` (2026-10-14), `v0.1.0-beta.22` (2026-10-13), `v0.1.0-beta.21` (2026-10-13), `v0.1.0-beta.20` (2026-10-12), `v0.1.0-beta.19` (2026-10-12), `v0.1.0-beta.18` (2026-10-07), `v0.1.0-beta.17` (2026-10-07), `v0.1.0-beta.16` (2026-10-06), `v0.1.0-beta.15` (2026-10-06), `v0.1.0-beta.14` (2026-10-06), `v0.1.0-beta.13` (2026-10-04), `v0.1.0-beta.12` (2026-10-04), `v0.1.0-beta.11` (2026-10-03), `v0.1.0-beta.10` (2026-09-28), `v0.1.0-beta.9` (2026-09-26), `v0.1.0-beta.8` (2026-09-25), `v0.1.0-beta.7` (2026-09-23), `v0.1.0-beta.6` (2026-09-23), `v0.1.0-beta.5` (2026-09-22), `v0.1.0-beta.4` (2026-09-21), `v0.1.0-beta.3` (2026-09-21), `v0.1.0-beta.2` (2026-09-17) and `v0.1.0-beta.1` (2026-09-16).** They are pre-releases: read the notes of the one you install — `CHANGELOG.md` links each release's own file under `docs/changelog/` — for what it measures, what it does not yet, and how to update, before installing. A source build is `docs/12_BUILD.md`.
1. Download the latest `FrameLedger.App-win-Setup.exe` from [Releases](https://github.com/poli0981/frameledger/releases). It installs into `%LOCALAPPDATA%\FrameLedger.App`; your data stays in `%LOCALAPPDATA%\FrameLedger`, and uninstalling asks before touching it.
2. SmartScreen may warn — releases are not code-signed (free, open-source project). Verify the SHA-256 checksum published with each release, then **More info → Run anyway**.
+1 -2
View File
@@ -334,8 +334,7 @@ CI/CD with the native build (`release.yml` exists since P4 PR-5, 2026-09-14 —
## After the controller train — the owner's order (2026-11-14)
Advanced metrics is closed (D154) and the controller feature ~~is being built as 0.1.0-beta.50's train~~ **was
released as 0.1.0-beta.50 (2026-11-15), unproven on a real controller until owner-only item 48**. Asked what
Advanced metrics is closed (D154) and the controller feature is being built as 0.1.0-beta.50's train. Asked what
comes after, the owner was shown six directions and chose four of them, and added distribution. **This is the
order of work after the controller train; each begins with a plan of its own and the owner's approval.** Nothing
here is designed yet, and what is marked *to verify* is a lead, not a finding.
-7
View File
@@ -56,13 +56,6 @@ Everything is a Windows API in a library Windows ships. **No third-party library
| `GetForegroundWindow`, `GetWindowThreadProcessId` | whose window is in front | already used for the focus sample (`04_CAPTURE`) |
| Steam's `appcache\appinfo.vdf`, on the disk | whether the store lists controller support for a library game | a local file: no request is made (rule 8) |
**The time `GetLastInputInfo` gives is compared only with the time it gave before** — "did it change since the last
slice". It is never set against a clock of .NET's. *Measured 2026-11-15, by accident*: on the developer PC, which
had slept for five hours since it started, that time and `Environment.TickCount` stood five hours apart — Windows'
tick counts the time asleep and .NET's does not — and a test that assumed one clock failed (it now asks only that
the time does not go back). Anything built on these times later — the time actually played, `15_ROADMAP` §After the
controller train — must work in differences of this one source, or it breaks on every PC that sleeps.
**Rejected, with the reason** (the checklist of `18_GPU_VENDOR_APIS` §Checklist applies to any library):
- **Windows.Gaming.Input** — its readings stop when the program is not in front, which the Agent never is.
+107 -187
View File
@@ -88,7 +88,6 @@ owner-only items stay below; the history of every train, the passed owner-only i
| `§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`](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`](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`](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`](handoff/history/0.1.0-beta.49.md) |
| `§Owner-only`, an open item | [§Owner-only](#owner-only--no-pr-can-close-these) below |
| `§Owner-only`, a passed item (3, 12, 14–19, 38, 39) | [`handoff/owner-only-passed.md`](handoff/owner-only-passed.md) |
| `§Traps`, `§Two corrections carried forward` | [`handoff/traps.md`](handoff/traps.md) |
@@ -96,146 +95,126 @@ owner-only items stay below; the history of every train, the passed owner-only i
---
## **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
## **START HERE** — 2026-11-14, 0.1.0-beta.49: item 46 read; the frames counted for the log, Reflex and frame generation together; a read a second on a grid; the Agent keeps the reading that waits
*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`](handoff/history/0.1.0-beta.49.md).**
*Status is `docs/changelog/0.1.0-beta.49.md`; this is what no other file carries.* The owner ran item 46 on
beta.48 the afternoon it was released — ten sessions, then eight more — and said: check (#455, and item 46's last
paragraphs, below). The read works, the samples are a second apart, both games give both of the driver's own
times, the multipliers are listed, off means off, **and the owner's word: no hitch**. Two things were left, the
owner said *do both*, and four answers given while planning made the train (D148–D151): #456 (the Overlay counts
each summed frame for its log), #457 (the watchdog's periodic tick on a grid), #458 (the Agent keeps the reading
that waits; the guide on whose switches the table shows), and this release. **beta.48's own section, its traps
and its release facts are [`handoff/history/0.1.0-beta.48.md`](handoff/history/0.1.0-beta.48.md).**
### The one thing to know: nothing here has met a controller
### What this release decided, beyond D148–D151
**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`) stored `input_observed_ms` 29 826 of a 30.9 s session, `input_source`
`rawinput+xinput+lastinput`, the `input.class` series 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.vdf` on 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.md` says so. Adding one is a parser in `Domain/Input` and 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.TryRead` takes 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.active` going 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's
`connects` decides whether the first rise was the session's start. Sixty marks a chart at most.
- **Steam's `appinfo.vdf` is read in format 41 only**; another format is refused with the reason, and the game's
page says N/A.
- **`InputTerms.MinimumPrivacyVersion` is `2.22` and 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.
- **`ShareBar`** is the base of `FgMixBar` and `InputShareBar`.
- **The counts are of each frame's own two numbers, with sums, and no threshold.** The draft counted spans of no
length; a sample whose mean span is half a microsecond says spans of one or two microseconds exist, and a count
of exact zeros would have read "the driver's" where it was "ours". So the frames that have both a span and an
active time are kept in two heaps — active longer than the span, or not — each with its count and both sums.
- **A batch's state is three things**: the driver's low-latency switch, its "the game sleeps" switch
(`bUseGameSleep`: NVAPI's "is `NvAPI_D3D_Sleep()` being called") and its frame-generation multiplier. The second
was added on the owner's word — Reflex goes with frame generation in the owner's games, and the low-latency
switch can be the NVIDIA App's override — and Clair Obscur's two sessions read exactly that: `bUseGameSleep`
off throughout without frame generation, on with ×3.
- **Only the driver read and the publication are the periodic tick's.** The request is still followed on every
tick, so the hooks a session asks for go in on the tick the loader woke — a game that has just loaded
Streamline calls it at once. A draft that moved the whole block would have missed those calls.
- **One read is armed at every periodic tick, and the grid is what keeps two apart**: half a second at the least,
after a tick that ran that late. "At most once a second" is no longer said anywhere.
- **A session's first publication may hold a moment's worth.** A request seen on a woken tick is published by the
periodic tick that follows, however soon. One test read a single publication as complete and had to stop.
- **The Agent keeps two sets, and an empty one does not wait.** A reading can stand at the sample after the one it
would have ridden — a second later. With the sensor interval above a second the oldest is still pushed out.
- **No legal text changed (D149)**, although a bug report carries the Overlay's logs and so these lines: the
owner was told and chose it. The Privacy Policy names the logs of the component loaded into games.
- **The plan was reviewed against the source by a second reader before the owner saw it, and sixteen things in
the draft were wrong** — among them the three above, and the whole of the Agent's half, which the draft did not
have.
### 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. Check `git diff origin/main <the lower
branch's last tip>` is empty, then `git merge -S -s ours origin/main` on the upper branch, and merge that up
the stack. **Look at `gh pr view` before 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 with `Plot.SavePng`. The picture is how two legends that covered their charts
were found; the test is not in the tree.
- **`MarkdownRendererTests` counts 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, as
`ChartMathTests` does.
- **FluentAssertions' `OnlyContain` fails 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`'s
`sensors`), with their own `t_ms`.
- **`GetLastInputInfo`'s time is not on `Environment.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-changes` through 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; `check` and the first
rehearsal (run 43646963371) caught it, and the second rehearsal is of the fixed tree.
- **A cause I offered and then counted away**: "the holes are the sensor library's fifth tick" — 25 of 134 fell on
one. The pattern that was there (46 of 134 exactly five samples apart) was the Agent's own attach rule, found
by reading `SessionRecorder`, not by looking harder at the Overlay.
- **A fixture that proved nothing**: the case for a woken watchdog first churned `sl.common.dll`, which wakes
nobody — it is in neither the inventory nor the census — and passed. It was caught only because the case
asserts, from the log, that the watchdog *was* woken (0 early ticks). **A test of a mechanism asserts that the
mechanism ran.** `opengl32.dll` is the wake that unloads nothing under a hook.
- **Qodana's native report reads the tests**: `static_cast<unsigned long long>(a * b)` is
`bugprone-implicit-widening-of-multiplication-result`. Widen an operand, not the product.
- **A here-document with an apostrophe in it failed again.** Edit scripts are files.
- **No edit while a gate runs still holds when CI asks for one**: the Qodana fix went into a second worktree of
the lower branch, and reached the upper one by a merge.
- **The item's own text said "nothing is lost by it" of the holes**, on a reading of the Overlay alone. A reading
was lost at every return to step. Say what was looked at.
### NEXT
1. **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.
2. **Then the order the owner set on 2026-11-14: [`15_ROADMAP.md`](15_ROADMAP.md) §After the controller train.**
It is not repeated here. Its first item uses what this train stores.
1. ~~**The owner runs item 47**~~ **Run and read 2026-11-14** (item 47, *Run 2026-11-14*): the difference in
Cyberpunk 2077 is the driver's, the holes are gone from steady play, off means off, and the stop fired once.
2. **The two GPU labels were reworded on the owner's word** (D152, 2026-11-14; strings in three languages, the
guide — in `[Unreleased]`, not in a release yet). **D141's stop stays as it is, and nothing more of Reflex is read** (D153, the owner
the same evening: "it only has to tell whether the game has it or not; Kingdom Come: Deliverance II has no
Reflex in its settings" — so that session lost nothing to the stop). (f) and (g) are said: the App's *Low
Latency Mode* is off, and no hitch.
3. **`slAllocateResources`** keeps its patch (D135); looked at again when there are more sessions.
4. ~~**Train D**~~ **Advanced metrics is closed (D154, 2026-11-14): train D is not built.** The owner was shown
the catalog — 140 entries, 110 read — and what the ten entries of reach `Spike` hold (Streamline's own headers,
2.14.16: DLSS frame generation's options and state, the video-memory estimates, ray reconstruction's, Image
Scaling's and Dynamic Vibrance's options, the PCL markers), with what reading them takes: a function of ours
handed to the game in place of Streamline's (rule 4), which a game that fetched its functions before the
attach never calls. The owner: "Đóng luôn". The ten are `RefusedRoute` now, the guide no longer says a later
release reads more, and §M15 is decided. **What is next is the controller feature**, planned in a session of
its own.
### 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 on `5764d21` (#471), by run 43652686348 — green at the first attempt, one
run for the one tag push. Eight assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed,
and the portable package hashed here equals its line; the five native libraries in it carry `FL_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 reads `0.1.0-beta.50`**, the bare version again.
**Three rehearsals on the release branch, and the third is of the released tree**: run 43646963371 at `9c69a32`
failed 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 at
`d6e4685` passed, and `main` at `5764d21` is that tree (a delta of 3 112 641 bytes, the same file counts).
**`./build.ps1 check` ran green on the developer PC at `6dadd05`**; 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\rules` hashed the same before and after.
**SonarCloud analysed `5764d21`: the quality gate passed. Qodana's two reports, CodeQL and `check` are 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 day
`release.yml` reads 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 `ja` string 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.md` is as of 2026-11-06;
`LIMITATIONS.md` and the accuracy statement on the processor's, memory's and motherboard's sensors are the
owner's to reword; the alpha line rests (D98).
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
after this text. Record them in the next pull request, with what SonarCloud and Qodana said.~~ **Recorded
2026-11-14: 0.1.0-beta.49 was released 2026-11-14T11:12:44Z** (18:12 in the owner's time zone) from the signed
tag on `afe4984` (#459), by run 43587336452 — green at the first attempt, one run for the one tag push. Eight
assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed, and the portable package hashed
here equals its line; the five native libraries in it carry `FL_BUILD_ID v0.1.0-beta.49`, none of them
`-dirty`. The delta from beta.48 is 1 100 211 bytes beside a full package of 110 803 443 — "Delta processed
0452 files. 0023 patched, 0429 unchanged". The wiki was published by run 43588972123. **Two rehearsals on the
release branch**: run 43580081466 at `1ab2809`, and — after a test-only fix reached the branch — run
43581734484 at `9f94356`, whose tree is the released one (a delta of 1 134 949 bytes, the same file counts).
**SonarCloud analysed `afe4984`: the quality gate passed and no issue is open on `main`. Qodana's two reports,
CodeQL and `check` are green on that commit.** On the way two advisory checks did find something, each in a
test of this train and each fixed before its pull request merged: Qodana's native report on #456 (two
products widened after the multiplication), SonarCloud on #457 (a line of the log handed to `printf`). **The
train stopped once for the owner**: two signed merges timed out at the passphrase prompt after #457; it went on
when the owner had unlocked the key. The tag's message reads `FrameLedger 0.1.0-beta.49` where the tags before
it read the bare version — nothing reads it, and a pushed tag is not moved.
- **Why Cyberpunk 2077's active render is longer than its span without frame generation** — item 47's to say. A
third session that afternoon repeated it (233: 3.40 against 3.13 ms at 292 of 296 samples) and a session of
menus did not (232: 0 of 126).
- **The Agent's half of the holes is read from the code and fits the ledger; it is not measured.** And with both
sides on a second a slip of phase can still leave a sample without a report: item 47 counts them.
- **A game that exits by itself loses the batch of counts in hand** — under a minute. Not changed: nothing runs
at a process's exit.
- **Where the third of a second of a poll goes is not established** (the history file of beta.48 has what is
known). Not looked at in this train.
- **With the sensor interval above one second, some readings of the driver's report are not stored** — the oldest
of the two that wait is pushed out. Said in the guide; not changed.
- **No test runs the whole path through the real Agent**: the injected tests stop at the shared memory, the
sampler's and the pending queue's start from it.
- **Two install batches of beta.46 took 0.61 s and 1.26 s and nothing explains them.** Item 46's ten sessions had none
above 191 ms.
- **The Japanese strings are unreviewed**, as every `ja` string is; this release added none.
- **(c) and (h) of item 43**, which only the owner sees, are still not exercised.
- **Valor Mortis's crash at 51 s** (twice, beta.40 and beta.44) **and Black Myth: Wukong's fault in Steam's crash
handler at every exit** are not explained. One session of each with hooking off is the comparison that is missing.
- **What item 41 left unexercised**: a configure through the FidelityFX 2.3 loader (Cyberpunk 2077 with FSR frame
generation), a game with neither library.
- **A fault while a game is closing is not seen by a hooked session** (D127: written down, not changed).
- **`docs/LIST_GAME_TESTED.md` is as of 2026-11-06**: refreshing it is a new copy of the ledger and the owner's review.
- **Item 40 (d)** was not exercised and the owner has not said item 40 passed. **Items 36 (d) and 37 are still open.**
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
sensors "have never been read on real hardware"** — the owner's to reword. The alpha line still rests (D98).
**Owner-only:** item 48; one session each of Valor Mortis and Black Myth: Wukong with hooking off; what item 41
**Owner-only:** item 47; 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
@@ -1032,65 +1011,6 @@ left unexercised; item 40 (d).
Latency: On**, V-Sync off, borderless at 2560×1440, 378 FPS on the game's counter. So the driver's
`bLowLatencyMode` on, 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.
48. **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.md` names 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 line
`input: 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* — as `LIMITATIONS.md` says. 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 into `LIMITATIONS.md` as 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's `input: run ended` lines*: 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
-141
View File
@@ -1,141 +0,0 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.50 was cut, 2026-11-15 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.50] - 2026-11-15
**The fiftieth pre-release: what a session was played with.** FrameLedger now notes, with every session, whether
the game was played with a controller, with the keyboard and mouse, with both at once or with nothing — and which
controllers were connected, for how long, how often they connected and dropped, and how their batteries did. It
reads this from Windows, **outside the game**, so it is there for every game you record, measured from inside or
not. The same unsigned installer: verify its hash against `SHA256SUMS.txt`, then *More info → Run anyway*.
**The terms window appears once: Privacy Policy 2.22 and Disclaimer 2.18.** Both used to say FrameLedger never
reads input. It now reads that a controller, or the keyboard or mouse, **was in use** — never which button, stick
or key, never text, never where the mouse is, never a serial number or a Bluetooth address — and it sends nothing
to a controller. **Nothing of this is read until you have accepted the new terms**, and Settings ▸ Recording ▸
*Controllers and input* switches it off altogether.
**Read this before you rely on it: none of it had been read from a real controller when this was released.** The
developer has none. Every figure was checked against sessions written by hand, and each part of the reader says
in the session what it could and could not do. The owner's Xbox controller and DualSense are the first real ones
it meets, after this release; what they show goes into the next one. Until then, treat the controller figures as
new and unproven — a share that looks wrong may be wrong.
**What you will see.**
- **A session's summary has a section, *Played with***: a bar and a table of the time the game was in front by
what it was played with; how often you changed between a controller and the keyboard and mouse; each controller
with its connection, its time in use and connected, how often it connected and dropped, and its battery — the
state it was in longest and for how long; each maker's share when you used two; a chart of the whole session
second by second, and a chart of each battery. On a measured session's Frametime chart, *Controller marks* draws
a controller's connections, drops and low batteries across the frames.
- **A game's page ends its *Details* with three rows about controllers** — what Steam lists for the game (read
from the Steam app's own file on your PC; nothing is looked up online), which of Windows' controller libraries
the game had loaded, and how you have actually played it. Three pieces of evidence: FrameLedger does not decide
whether a game "supports controllers".
- **Trend** has *Controller share* and *Keyboard and mouse share*; **Compare** shows what each session was played
with; a CSV or JSON export, and a bug report, carry the same figures and each controller's model name — say so
before you share one.
- **The user guide has a page for it**, *Controllers and input*, and `LIMITATIONS.md` lists what it cannot tell:
it knows a controller was in use while the game was in front, not what the game did with it; the keyboard and
the mouse are one class; Xbox-compatible controllers and the DualSense are read for use, others are only listed;
a battery level is there only when the controller reports one to Windows.
**Also in this release**, from before the controller work: the two lines of the graphics card's time under
*Latency* say what each figure is (D152), and Advanced metrics is closed — the ten Streamline readings that were
"being studied" are "not read", with the reason (D154).
**A session that was not measured from inside** now has more than its length, its sensors and the reason: it has
the game's memory and what it was played with — everything FrameLedger reads from outside the game (D161).
### Added
- **A session's summary says what it was played with** (owner decisions D155-D163): **Played with** — a bar and a table
of the time the game was in front that was played with a controller, with the keyboard and mouse, with both at once
and with no input; how often you changed between them; each controller of the session with its connection, the time
in use and connected, how often it connected and dropped, and its battery — the state it was in longest and for how
long, the first and last level, how fast it ran down; and each maker's share when two were used. Two charts follow:
**Input over the session** and **Controller battery**. On a measured session's Frametime chart, **Controller marks**
draws a controller's connections, drops and low batteries across the frames. For every session, measured from inside
or not. **Trend** has *Controller share* and *Keyboard and mouse share*, **Compare** has *Played with* and
*Controllers*, and a CSV export has an `# input:` line. The user guide has a page for it, *Controllers and input*.
Checked against synthetic sessions only: no controller had been read when this was written.
- **A session records what it was played with — a controller, the keyboard and mouse, both, or neither** (D155–D163,
the owner's decisions of 2026-11-14; *Settings ▸ Controllers and input*, on unless you switch it off). While a game
is recorded, FrameLedger's agent notes — from Windows, never from the game — which game controllers are connected
and in use, their battery level, and whether the keyboard or mouse is in use, and the session stores how the time
the game was in front divides between them, how often each controller connected and dropped, and its battery. It
works for a game FrameLedger does not measure too. **No button, stick, key or text is kept; nothing is sent to a
controller; and nothing is read until you have accepted the Privacy Policy that describes it** — after this
update, sessions recorded before FrameLedger has been opened once have no such figures. The screens that show the
figures come with the same release. Xbox-compatible controllers and the DualSense are read for use; another
controller is listed and never counted as in use. **None of this had been read from a real controller when it was
written** — it was checked against data written by hand (`LIMITATIONS.md` §Controllers and input).
- **A game's page says what is known about controller support — three things, and no verdict** (D163). *Controller
support (store)*: what Steam lists for the game — full, partial, or none — read from the Steam app's own file on
your PC when you open the page; nothing is asked of the store, and a game that is not Steam's reads N/A. *Input
libraries loaded*: which of XInput, DirectInput, Windows.Gaming.Input, GameInput and SDL the game had loaded the
last time it was measured from inside. *Usually played with*: the share of the time in front with a controller,
the keyboard and mouse, both and neither, over the sessions that recorded it. English, Vietnamese, Japanese.
- **The terms are shown once: Privacy Policy 2.22 and Disclaimer 2.18.** Both said FrameLedger never reads input.
They now say what is read — that a controller, or the keyboard or mouse, is in use — what is kept, and what never
is (`docs/legal-drift-history.md`).
- **For developers: the arithmetic of controller statistics, with nothing reading a device yet** (D155–D163, the
owner's decisions of 2026-11-14; `docs/21_INPUT_DEVICES.md`, `docs/03_METRICS.md` §Input). `FrameLedger.Domain.Input`
says whether an XInput state or a DualSense report is a pad in use and what its battery is, adds a battery's readings
up, counts switches, and decides when two entries are one pad seen twice; `Application.Input` holds one session's
slices and turns them into a reading a second; `InputSessionBuilder` turns a session's readings into its totals, its
controllers as JSON and its timeline. A telemetry sample can carry a reading; none does. **Every byte and reading
under test was written by hand — no report from a real controller has passed through this code.**
- **For developers: a session can store what it was played with — schema 0024** (D160; `docs/06_DATA_MODEL.md`). Nine
columns on `sessions` (the time in front and its four classes, the switches of method, the sources that answered,
the controllers as JSON) and three on `games` (what a store lists of controller support), ADD COLUMN only; the
`.partial` file gains chunk 11, so a session recovered after the Agent died keeps its readings; the finalizer
stores them for hooked and unhooked sessions alike; the input series are `sensor_blobs` rows named `input.*`, which
the sensors' read leaves out. Nothing produces a reading yet. **A ledger this build has opened cannot be opened by
0.1.0-beta.49 or earlier.**
- **For developers: the input reader, which the Agent does not start yet** (D155, D158, D159; `docs/21_INPUT_DEVICES.md`
§The reader). `Application.Input.InputReader` takes a slice about ten times a second from
`Infrastructure.Input.Win32InputBackend` — raw input for joysticks and gamepads delivered to a window that is never
shown, three of XInput's getters, the time of the last keyboard or mouse input, the window in front — on the thread
of `InputDeviceHub`, which exists only while a session has a view of it. It opens no device, sends nothing to one,
and registers for no keyboard or mouse. A new gate, `tools/input-readonly-check.ps1`, holds the reader's Windows
calls to a committed list and refuses, on the list or off it, a call that sends to a device, injects input or reads
a key; no other managed source and no native source may name an input function. **With no controller at hand, what
the reader does with one connected is not established**: its tests use a Windows whose answers they write, and one
suite runs it on the real Windows of the machine and asserts only that it opens, answers and closes.
### Changed
- **Advanced metrics is closed: the ten readings that were "being studied" are now "not read", with the reason**
(D154, the owner's decision). What a game sets and asks through Streamline's own functions for a feature — DLSS
frame generation's options and state, the video memory DLSS estimates for itself, the options of ray
reconstruction, Image Scaling and Dynamic Vibrance, the PC-latency markers — is reached only by handing the game
a function of FrameLedger's in place of Streamline's, which is refused. The *Sources* list says so, in English,
Vietnamese and Japanese, and the guide no longer says a later release reads more. Nothing that was read stops
being read.
- **The two lines of the graphics card's time say what each is, not which holds the other** (D152, the owner's
decision). *GPU active render (idle time excluded)* and *GPU render, start to end (idle time included)* are now
*GPU active render (the driver's own figure)* and *GPU render (between the driver's start and end marks)*, in
English, Vietnamese and Japanese, and the guide says why: in Cyberpunk 2077 without frame generation the
driver's active time is longer than its two marks are apart. The numbers are unchanged.
- **The guide's page on Advanced metrics says what two of the driver's switches mean** (`guide/12`): the latency
report is there in a game that has Reflex built in, whether Reflex is on or off in its menu; `bUseGameSleep`
says the game calls Reflex's sleep — NVIDIA asks for that even with Reflex off — and `bLowLatencyMode` is the
one that says the mode is on; frame generation needs Reflex, not the reverse. From NVIDIA's Streamline guide
for Reflex, and from the owner's ten sessions on 0.1.0-beta.49.
### Documentation
- **Owner-only item 47 was run and read** (`docs/HANDOFF.md`): in Cyberpunk 2077 without frame generation the
driver's active GPU time is longer than its own two marks are apart on 4 917 of 5 394 frames (1 849 µs beside
1 571 µs) and on none of 129 900 frames in five other games — the difference is the driver's; samples without a
report are now confined to a game's start; a session with the option off has no latency line; and the stop of
D141 fired in a real game for the first time (Kingdom Come: Deliverance II, one call of 5.3 ms while it
started).
- **Streamline's programming guides for Reflex and for DLSS Ray Reconstruction (2.14.16) read against the code**
(`docs/spike-notes/30-reflex-latency.md`, *Added 2026-11-14*). Ray reconstruction was already measured the way
the guide describes; two comments in the Overlay's source and one line of `17_HOOK_ENGINE` said super
resolution and ray reconstruction run together, and they do not. `03_METRICS` and `05_DETECTION` no longer
promise "PC latency as reported by Reflex" (D147). No code changed: comments only.
-125
View File
@@ -1,125 +0,0 @@
# HANDOFF history — 0.1.0-beta.49
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.50 was cut, 2026-11-15 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path is relative to `docs/`.*
## **START HERE** — 2026-11-14, 0.1.0-beta.49: item 46 read; the frames counted for the log, Reflex and frame generation together; a read a second on a grid; the Agent keeps the reading that waits
*Status is `docs/changelog/0.1.0-beta.49.md`; this is what no other file carries.* The owner ran item 46 on
beta.48 the afternoon it was released — ten sessions, then eight more — and said: check (#455, and item 46's last
paragraphs, below). The read works, the samples are a second apart, both games give both of the driver's own
times, the multipliers are listed, off means off, **and the owner's word: no hitch**. Two things were left, the
owner said *do both*, and four answers given while planning made the train (D148–D151): #456 (the Overlay counts
each summed frame for its log), #457 (the watchdog's periodic tick on a grid), #458 (the Agent keeps the reading
that waits; the guide on whose switches the table shows), and this release. **beta.48's own section, its traps
and its release facts are [`handoff/history/0.1.0-beta.48.md`](handoff/history/0.1.0-beta.48.md).**
### What this release decided, beyond D148–D151
- **The counts are of each frame's own two numbers, with sums, and no threshold.** The draft counted spans of no
length; a sample whose mean span is half a microsecond says spans of one or two microseconds exist, and a count
of exact zeros would have read "the driver's" where it was "ours". So the frames that have both a span and an
active time are kept in two heaps — active longer than the span, or not — each with its count and both sums.
- **A batch's state is three things**: the driver's low-latency switch, its "the game sleeps" switch
(`bUseGameSleep`: NVAPI's "is `NvAPI_D3D_Sleep()` being called") and its frame-generation multiplier. The second
was added on the owner's word — Reflex goes with frame generation in the owner's games, and the low-latency
switch can be the NVIDIA App's override — and Clair Obscur's two sessions read exactly that: `bUseGameSleep`
off throughout without frame generation, on with ×3.
- **Only the driver read and the publication are the periodic tick's.** The request is still followed on every
tick, so the hooks a session asks for go in on the tick the loader woke — a game that has just loaded
Streamline calls it at once. A draft that moved the whole block would have missed those calls.
- **One read is armed at every periodic tick, and the grid is what keeps two apart**: half a second at the least,
after a tick that ran that late. "At most once a second" is no longer said anywhere.
- **A session's first publication may hold a moment's worth.** A request seen on a woken tick is published by the
periodic tick that follows, however soon. One test read a single publication as complete and had to stop.
- **The Agent keeps two sets, and an empty one does not wait.** A reading can stand at the sample after the one it
would have ridden — a second later. With the sensor interval above a second the oldest is still pushed out.
- **No legal text changed (D149)**, although a bug report carries the Overlay's logs and so these lines: the
owner was told and chose it. The Privacy Policy names the logs of the component loaded into games.
- **The plan was reviewed against the source by a second reader before the owner saw it, and sixteen things in
the draft were wrong** — among them the three above, and the whole of the Agent's half, which the draft did not
have.
### Traps this train left
- **A cause I offered and then counted away**: "the holes are the sensor library's fifth tick" — 25 of 134 fell on
one. The pattern that was there (46 of 134 exactly five samples apart) was the Agent's own attach rule, found
by reading `SessionRecorder`, not by looking harder at the Overlay.
- **A fixture that proved nothing**: the case for a woken watchdog first churned `sl.common.dll`, which wakes
nobody — it is in neither the inventory nor the census — and passed. It was caught only because the case
asserts, from the log, that the watchdog *was* woken (0 early ticks). **A test of a mechanism asserts that the
mechanism ran.** `opengl32.dll` is the wake that unloads nothing under a hook.
- **Qodana's native report reads the tests**: `static_cast<unsigned long long>(a * b)` is
`bugprone-implicit-widening-of-multiplication-result`. Widen an operand, not the product.
- **A here-document with an apostrophe in it failed again.** Edit scripts are files.
- **No edit while a gate runs still holds when CI asks for one**: the Qodana fix went into a second worktree of
the lower branch, and reached the upper one by a merge.
- **The item's own text said "nothing is lost by it" of the holes**, on a reading of the Overlay alone. A reading
was lost at every return to step. Say what was looked at.
### NEXT
1. ~~**The owner runs item 47**~~ **Run and read 2026-11-14** (item 47, *Run 2026-11-14*): the difference in
Cyberpunk 2077 is the driver's, the holes are gone from steady play, off means off, and the stop fired once.
2. **The two GPU labels were reworded on the owner's word** (D152, 2026-11-14; strings in three languages, the
guide — in `[Unreleased]`, not in a release yet). **D141's stop stays as it is, and nothing more of Reflex is read** (D153, the owner
the same evening: "it only has to tell whether the game has it or not; Kingdom Come: Deliverance II has no
Reflex in its settings" — so that session lost nothing to the stop). (f) and (g) are said: the App's *Low
Latency Mode* is off, and no hitch.
3. **`slAllocateResources`** keeps its patch (D135); looked at again when there are more sessions.
4. ~~**Train D**~~ **Advanced metrics is closed (D154, 2026-11-14): train D is not built.** The owner was shown
the catalog — 140 entries, 110 read — and what the ten entries of reach `Spike` hold (Streamline's own headers,
2.14.16: DLSS frame generation's options and state, the video-memory estimates, ray reconstruction's, Image
Scaling's and Dynamic Vibrance's options, the PCL markers), with what reading them takes: a function of ours
handed to the game in place of Streamline's (rule 4), which a game that fetched its functions before the
attach never calls. The owner: "Đóng luôn". The ten are `RefusedRoute` now, the guide no longer says a later
release reads more, and §M15 is decided. **What is next is the controller feature**, planned in a session of
its own.
### Left open by this session
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
after this text. Record them in the next pull request, with what SonarCloud and Qodana said.~~ **Recorded
2026-11-14: 0.1.0-beta.49 was released 2026-11-14T11:12:44Z** (18:12 in the owner's time zone) from the signed
tag on `afe4984` (#459), by run 43587336452 — green at the first attempt, one run for the one tag push. Eight
assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed, and the portable package hashed
here equals its line; the five native libraries in it carry `FL_BUILD_ID v0.1.0-beta.49`, none of them
`-dirty`. The delta from beta.48 is 1 100 211 bytes beside a full package of 110 803 443 — "Delta processed
0452 files. 0023 patched, 0429 unchanged". The wiki was published by run 43588972123. **Two rehearsals on the
release branch**: run 43580081466 at `1ab2809`, and — after a test-only fix reached the branch — run
43581734484 at `9f94356`, whose tree is the released one (a delta of 1 134 949 bytes, the same file counts).
**SonarCloud analysed `afe4984`: the quality gate passed and no issue is open on `main`. Qodana's two reports,
CodeQL and `check` are green on that commit.** On the way two advisory checks did find something, each in a
test of this train and each fixed before its pull request merged: Qodana's native report on #456 (two
products widened after the multiplication), SonarCloud on #457 (a line of the log handed to `printf`). **The
train stopped once for the owner**: two signed merges timed out at the passphrase prompt after #457; it went on
when the owner had unlocked the key. The tag's message reads `FrameLedger 0.1.0-beta.49` where the tags before
it read the bare version — nothing reads it, and a pushed tag is not moved.
- **Why Cyberpunk 2077's active render is longer than its span without frame generation** — item 47's to say. A
third session that afternoon repeated it (233: 3.40 against 3.13 ms at 292 of 296 samples) and a session of
menus did not (232: 0 of 126).
- **The Agent's half of the holes is read from the code and fits the ledger; it is not measured.** And with both
sides on a second a slip of phase can still leave a sample without a report: item 47 counts them.
- **A game that exits by itself loses the batch of counts in hand** — under a minute. Not changed: nothing runs
at a process's exit.
- **Where the third of a second of a poll goes is not established** (the history file of beta.48 has what is
known). Not looked at in this train.
- **With the sensor interval above one second, some readings of the driver's report are not stored** — the oldest
of the two that wait is pushed out. Said in the guide; not changed.
- **No test runs the whole path through the real Agent**: the injected tests stop at the shared memory, the
sampler's and the pending queue's start from it.
- **Two install batches of beta.46 took 0.61 s and 1.26 s and nothing explains them.** Item 46's ten sessions had none
above 191 ms.
- **The Japanese strings are unreviewed**, as every `ja` string is; this release added none.
- **(c) and (h) of item 43**, which only the owner sees, are still not exercised.
- **Valor Mortis's crash at 51 s** (twice, beta.40 and beta.44) **and Black Myth: Wukong's fault in Steam's crash
handler at every exit** are not explained. One session of each with hooking off is the comparison that is missing.
- **What item 41 left unexercised**: a configure through the FidelityFX 2.3 loader (Cyberpunk 2077 with FSR frame
generation), a game with neither library.
- **A fault while a game is closing is not seen by a hooked session** (D127: written down, not changed).
- **`docs/LIST_GAME_TESTED.md` is as of 2026-11-06**: refreshing it is a new copy of the ledger and the owner's review.
- **Item 40 (d)** was not exercised and the owner has not said item 40 passed. **Items 36 (d) and 37 are still open.**
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
sensors "have never been read on real hardware"** — the owner's to reword. The alpha line still rests (D98).
**Owner-only:** item 47; one session each of Valor Mortis and Black Myth: Wukong with hooking off; what item 41
left unexercised; item 40 (d).
+1 -1
View File
@@ -12,7 +12,7 @@
HTML comments are not part of the block.
-->
> ⚠ **What FrameLedger actually measures today — 2026-11-11.** The software is a beta; its latest
> **beta is `0.1.0-beta.50`** (2026-11-15), an unsigned installer built from that tag with its
> **beta is `0.1.0-beta.49`** (2026-11-14), an unsigned installer built from that tag with its
> checksums published beside it (alphas — experimental builds that try a newer .NET — are published apart). The source holds the desktop app
> (library, store import, charts, settings) and the background Agent, which records a session when a
> game in the library runs (unless you switched its recording off), injects only into games you enabled
+1 -1
View File
@@ -127,7 +127,7 @@ Frame timing is derived from high-resolution timestamps taken at the moment the
<!-- accuracy-block:begin -->
> ⚠ **What FrameLedger actually measures today — 2026-11-11.** The software is a beta; its latest
> **beta is `0.1.0-beta.50`** (2026-11-15), an unsigned installer built from that tag with its
> **beta is `0.1.0-beta.49`** (2026-11-14), an unsigned installer built from that tag with its
> checksums published beside it (alphas — experimental builds that try a newer .NET — are published apart). The source holds the desktop app
> (library, store import, charts, settings) and the background Agent, which records a session when a
> game in the library runs (unless you switched its recording off), injects only into games you enabled
@@ -40,12 +40,8 @@ public sealed class Win32InputBackendTests
if (backend.TryReadLastInputTick(out uint tick))
{
// What the reader relies on: asked again, the time has not gone back. It is NOT compared with
// Environment.TickCount, and nothing may be: measured 2026-11-15 on a PC that had slept for five hours,
// the two were five hours apart - Windows' tick counts the sleep and .NET's does not. The reader only ever
// asks whether the time changed since its last slice (InputReader), which no sleep can spoil.
backend.TryReadLastInputTick(out uint again).Should().BeTrue();
unchecked((int)(again - tick)).Should().BeGreaterThanOrEqualTo(0);
// The same clock as Environment.TickCount, and never ahead of it by more than a moment.
unchecked((int)((uint)Environment.TickCount - tick)).Should().BeGreaterThan(-60_000);
}
uint front = backend.ForegroundProcessId();