Compare commits
8
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
0c210d04c3 | ||
|
|
0ddc7e681a | ||
|
|
ddc7517492 | ||
|
|
63af4eb38c | ||
|
|
be10e68506 | ||
|
|
0058b7c167 | ||
|
|
a936466f5f | ||
|
|
a0690a4bc2 |
No files matched your search
+1
-1
@@ -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.47. In the app: Help ▸ Accessibility.*
|
||||
*Beta software: this page describes version 0.1.0-beta.48. In the app: Help ▸ Accessibility.*
|
||||
|
||||
## What FrameLedger aims for
|
||||
|
||||
|
||||
+1
-44
@@ -35,56 +35,13 @@ numeric core and does not move; the heading is the full version — corrected 20
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
|
||||
- **Two more lines from NVIDIA's latency report: how long the graphics card was really at work** (owner decision
|
||||
D142). In a real game the driver's *GPU render* stage turned out longer than the whole frame: it runs from the
|
||||
card's start to its end and includes the time the card waited. With Advanced metrics on, a session now also
|
||||
stores two figures the driver works out itself — **GPU active render**, the same stage without the waiting, and
|
||||
**GPU frame time**, from the end of one frame's work to the end of the next — as a second chart under *Latency*.
|
||||
They come from the report FrameLedger already asks the driver for; nothing more is asked. A driver may give
|
||||
neither, and the chart is then not there. Sessions recorded before this release do not have them.
|
||||
|
||||
- **For developers: the part inside a game reads two more figures of NVIDIA's latency report, and keeps every
|
||||
frame-generation multiplier a session saw** (owner decisions D142, D144; nothing a user sees until the Agent and
|
||||
the App read them). In a real game the driver's span between its two GPU marks was longer than the frame's whole
|
||||
— it includes the card's waiting. The driver's own *active* render time and its GPU frame time are members of
|
||||
the report FrameLedger already fetches; they are read from it, with **no further call into the driver**. Four
|
||||
reserved words of the shared memory carry them and the multipliers seen (layout 5 as it was). `fl_reflex_summary`
|
||||
and the injected `[latency]` cases hold it. Measured: +36 ns a read, once a second.
|
||||
|
||||
### Changed
|
||||
|
||||
- **The *GPU render* line says what it includes** (owner decision D143): *GPU render, start to end (idle time
|
||||
included)*, in the three languages. The numbers are the same.
|
||||
- **The driver's frame-generation multiplier is every value the session saw** (owner decision D144). The table of
|
||||
the driver's low-latency state kept only the last one: a session that generated frames at ×2 and ended in a menu
|
||||
showed 1. It now shows *1, 2*. Sessions already recorded keep what they stored.
|
||||
- **The texts say what was read** (owner decision D145). The accuracy statement, the README and the guide said no
|
||||
real game had been read; two have been, on one driver. They also say now that the stages overlap and do not add
|
||||
up to the total. **Privacy Policy 2.21** names the two new averages; **Disclaimer 2.17** changes only with the
|
||||
accuracy statement it carries. The terms window shows once.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Sensors were read less often than the setting says** (owner decision D146). With the sensor interval at
|
||||
1000 ms, nearly every session on the owner's PC got a sample every 1.3 seconds: the Agent waited the whole
|
||||
interval *after* each reading, and a reading there takes about a third of a second (what in it does is not
|
||||
established; on a PC where the Agent is not run as administrator it takes a millisecond, and the samples were
|
||||
already a second apart). It now keeps the period. No chart was wrong — every sample is stored with its own time — but a session
|
||||
has about a third more samples now, and about a quarter of the readings of NVIDIA's latency report no longer
|
||||
fall between two samples. For developers: `sensor_blobs.hz` was the constant 1 and is now the rate the
|
||||
session's samples had.
|
||||
- **A session could start with the last read of the session before it.** In a game that kept running between two
|
||||
sessions, a read of the driver's latency report that ended after the first session's last tick was taken as the
|
||||
second session's first point. A new session now drops it.
|
||||
|
||||
## Releases
|
||||
|
||||
Newest first. Each file holds that release's section exactly as it stood here.
|
||||
|
||||
| Version | Date | Notes |
|
||||
|---|---|---|
|
||||
| `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) |
|
||||
| `0.1.0-beta.46` | 2026-11-13 | [`docs/changelog/0.1.0-beta.46.md`](docs/changelog/0.1.0-beta.46.md) |
|
||||
| `0.1.0-beta.45` | 2026-11-12 | [`docs/changelog/0.1.0-beta.45.md`](docs/changelog/0.1.0-beta.45.md) |
|
||||
|
||||
@@ -139,6 +139,9 @@ src/
|
||||
# a frame's stages - NOT an argument of a hooked call: the Overlay calls two
|
||||
# read-only getters of the driver itself (reach GameDriver); seven adv.* series
|
||||
# and one table, and AdvancedDriverRead says what became of the read.
|
||||
# Since 0.1.0-beta.48 (D142-D144) also two figures the driver works out itself, of
|
||||
# the same report - no further call: an entry of their own, nvapi.reflex.gpu_times,
|
||||
# two adv.* series; and the table lists every frame-generation multiplier seen.
|
||||
FrameLedger.Infrastructure/ # SQLite, shm reader, vendor APIs, injector interop, parsers,
|
||||
# and Capture/ (PR-C): ShmRingAttacher/ShmCaptureSink over the
|
||||
# reader, HeldProcessLivenessSource, TargetResolver (path only,
|
||||
|
||||
+1
-1
@@ -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.47.*
|
||||
*Beta software: this page describes version 0.1.0-beta.48.*
|
||||
|
||||
## Games it will not measure
|
||||
|
||||
|
||||
@@ -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.47`** (2026-11-14), an unsigned installer built from that tag with its
|
||||
> **beta is `0.1.0-beta.48`** (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
|
||||
@@ -215,7 +215,7 @@ Elevation is **optional — for everything.** Hooked capture is the normal path
|
||||
|
||||
## Install
|
||||
|
||||
> **The latest beta is `v0.1.0-beta.47` (2026-11-14); before it `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.48` (2026-11-14); before it `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**.
|
||||
|
||||
@@ -1873,7 +1873,7 @@ Moved verbatim, in this order.
|
||||
| M12 ❓ | **Advanced metrics — which NVAPI rows answer on real hardware (D101, 2026-11-11).** `18_GPU_VENDOR_APIS` §The inventory lists sixty `nvapi.` rows whose reach is `Agent`. They are declared in the vendored headers; **none has been called on a GPU**, and CI has no driver, so it never takes that branch. Unknown per row: whether the RTX 5080 on the current driver answers or returns `NVAPI_NOT_SUPPORTED` (the memory-temperature target already does not exist on that card). | **The measurement is the bridge's probe on the owner's PC**, then the page itself (the release's owner-only item). Pre-committed: a call that does not answer → that row is N/A with NVAPI's own status as the reason, and nothing is put in its place; a call that hangs or faults twice → the row is off for the session (§Runtime policy); a value that contradicts the vendor's own tool → the row is withheld until it is explained. **Half answered the same day, by the bridge's own test on the dev box** (ctest `fl_nvapi_bridge`, AVAILABLE branch; RTX 5080): every fact answers (`present = 0xFFFFF`), eight of ten live groups answer (`0x33F` — no board and no power-supply temperature sensor on this card: N/A, by the first pre-committed outcome), the display answers its four groups, the global profile lists 24 settings; figures in `18_GPU_VENDOR_APIS` §L3. **Still open**: the same values on the page beside the vendor's own tool, and the session rows (`nvapi.session.*`), which need a game. **And one thing seen once and not explained**: in one test run of about a dozen that day, `FlNvReadLive` came back with no field at all although `FlNvReadFacts`, a moment earlier in the same process, had answered everything; nine further runs did not show it. A handle the driver invalidated is the usual cause of that shape, and nothing here re-enumerates after `FlNvInit`. Pre-committed for the reader that owns the thread: two readings in a row with no field → release and initialise the bridge again, once, and say so in the log; if that does not bring the fields back the layer is off for the session, as any layer that fails twice is. |
|
||||
| M13 ❓ | **Advanced metrics — LibreHardwareMonitor's CPU, memory, motherboard and storage groups, elevated, with PawnIO (D103, 2026-11-11).** Never opened by any build: §M10's elevated run has not been taken either, and this is a larger surface — a sensor chip on the LPC bus, the embedded controller, SPD over SMBus, SMART. Unknown: whether each group opens on the owner's board, what a refresh costs, whether opening the storage group touches removable drives (this PC once had a failing USB drive), and whether any group enables a privilege (`PrivilegeFootprintTests`). | **One elevated run with the probe verb, before the option exists.** Pre-committed: the storage group cannot be opened without touching removable drives → `lhm.storage.*` stays N/A in beta.39 and its reach reads `Deferred`; a node that throws twice → skipped for the session; the Agent above 1% of one core or 150 MB with the option on (NFR-2) → the slow groups are read less often or dropped before the release; a privilege enabled by a group → that group is not opened, and the owner is asked. **Two of the four answered 2026-11-11, before the option exists.** (1) **Storage: not opened, by the first outcome.** LibreHardwareMonitor 0.9.6's `StorageGroup` lists every drive through DiskInfoToolkit's `ReloadStorages` with no filter by bus and follows drives plugged in later — it cannot be opened without touching removable drives. `lhm.storage.*` reads `Deferred`, and `LhmGroups` has no member for it. (2) **Cost, unelevated, measured with `probe-advanced`** on the dev box: one refresh of the graphics-card group alone is 14 ms of processor time (62 ms elapsed) — 1.4% of one core at one a second, above NFR-2 — and one NVAPI read 0.4 ms. By the third outcome the sensor library is read every fifth tick (0.28%). **Still open, and the owner's**: the same probe as administrator with PawnIO — whether the processor, memory and motherboard groups open on this board, what they cost, and `PrivilegeFootprintTests`' new case on a token that holds the privileges (CI's does; the dev box's unelevated run passes by construction). **The first run was taken on 2026-11-12, by the owner, in ordinary use** (0.1.0-beta.40, the Agent as administrator with PawnIO, an i7-14700KF on a board with an IT8689E chip, an RTX 5080), and read here from a copy of the ledger and the Agent's log, not from a probe. **The groups open and read**: nine of ten sessions stored 119 processor series (a clock and a load per thread, temperatures, powers, voltages), 14 memory series and 21 motherboard series (six fans, six temperatures, nine voltages) beside the card's 41 — 195 from the sensor library in all. **No value was compared with another tool**; that is still the owner's. **Two faults, one cause** (`Infrastructure.Telemetry.LhmLibrary`): the Agent held up to three `Computer`s at once, and the library keeps the driver it reads the processor through and its bus mutexes per process — closing one `Computer` let go of them under the others. After seven sessions the Advanced reader's processor device threw `NullReferenceException` twice and was left alone (the page lost the processor until the reader reopened); once a session's start met another instance's close, the reader's `Open` threw `ObjectDisposedException`, and that session stored 17 series instead of 212. **Fixed 2026-11-12**: opens and closes are serialised and a `Computer` is parked, not closed, while another is in use. The cause is read from the log's timing and was not reproduced — it needs this elevation — so **whether the faults are gone is the owner's next sessions to show**: no `advanced: a device is left alone` and no `did not open` in the Agent's log. **First evidence, 2026-11-12, 0.1.0-beta.41, the same PC:** seven sessions between 06:38 and 07:01 with no `advanced:` line at all, each with the option on storing 212 or 213 series; on beta.40 that morning the processor device faulted out after each of six sessions (04:34–05:07) — thirteen of sixteen over the night. The reader failing to open was seen once in sixteen, so this is not yet enough to call that one gone. Still open: any value beside another tool. |
|
||||
| M16 ✅ | **The L2 telemetry layer's cost — the first number, and it is above NFR-2 (found 2026-11-11, measuring something else).** `LhmTelemetrySource` refreshes LibreHardwareMonitor's graphics-card group once a second in every recorded session. `probe-advanced` measured that refresh, through the same library and the same group, at **14 ms of processor time** on the dev box (RTX 5080, 41 mapped sensors, about twenty of them the Direct3D engine nodes the library enumerates per card) — 1.4% of one core, where NFR-2 allows the whole Agent 1% during capture and `14_TESTING` §Hook overhead's Agent figure has never been measured. This is a measurement of the call, not yet of a session: L2's own poller was not instrumented. | **Measure L2 in a session** (the Agent's processor time over a ten-minute capture, telemetry at 1000 ms and at 2000 ms). Pre-committed: at or under 1% → this row closes with the number; above → the owner chooses between a slower default for `telemetry.interval_ms`, reading the sensors the layer keeps from NVAPI on NVIDIA cards (L3 already has most, at 0.4 ms), or amending NFR-2 to what is measured. Not decided here, and nothing about L2 changes in the Advanced-metrics train. **Measured in a real Agent, 2026-11-11 (owner decision D110), and answered (D117).** `tools/agent-cost.ps1` runs the shipped `FrameLedger.Agent.exe --console capture` against a copy of hook-harness in a scratch data folder — a session that is not hooked, so the telemetry poller runs as in every session and nothing drains frames — and reads the Agent process's own processor time at exit; the cost per second is the slope between a 45 s and a 165 s session, two runs of each. Dev box (RTX 5080, not elevated, layers `l1+lhm+nvapi`): **19.3 ms of processor time per second of session = 1.93 % of one core with Advanced metrics off** (2,312 and 2,312 ms over 45 s; 4,594 and 4,656 ms over 165 s), **20.4 ms = 2.04 % with it on** (2,984 and 3,000; 5,547 and 5,344); peak working set 113 MiB and 119 MiB. A first pass with 30 s and 90 s sessions gave 1.56 % and 2.21 % — its two short runs differed by 670 ms, which is why the lengths were raised. So the probe's number holds in a session: the Agent's steady cost is about twice NFR-2's 1 %, nearly all of it the layer every session has always used, and the new option adds about a tenth of a percent. **The owner's answer: NFR-2 is amended to ≤ 2.5 % of one core** — the limit had never been measured, the sensors keep their one reading a second, and nothing in the code changes. Not measured: a hooked session (the drain's cost on top), a session with the Agent elevated and PawnIO's groups open, another PC. |
|
||||
| M14 ❓ | **Reflex latency per frame — is there a route within rules 4 and 5? (Train C, 2026-11-11.)** `17_HOOK_ENGINE` §Memory / latency names hooks on `NvAPI_D3D_SetSleepMode` / `SetLatencyMarker` and a call to `NvAPI_D3D_GetLatency`. NVAPI resolves all three through `nvapi_QueryInterface` by id — they are not exports, so a hook on them is a patch at an address learned at run time, the class refused on 2026-08-09. The route to try first needs no hook: the Overlay's own background thread **calls** `GetLatency` with the device of the swap chain it already hooks, once a second (the call returns the last 64 frames' reports). Unknown: whether calling into the driver from that thread is safe on every device kind, what it costs, what it returns when the game never enabled Reflex, and what it means for the Disclaimer's sentence about that thread. | **A spike on `hook-harness` and a stub first, then one real title.** Pre-committed: no route without a patch at a run-time address or a loader-lock call on the game's thread → Reflex stays N/A and the page says why; overhead above NFR-1 → the same. The owner says go or no on the spike's result. **2026-11-12 — the reading that comes before that spike is `spike-notes` §30** (owner decision D130: a document first, beside 0.1.0-beta.45; nothing was run). It finds: a hook on NVAPI's latency functions is the refused class, and a hook on Streamline's Reflex and PCL functions is train D's wrapper (§M15) — and would miss a game that fetched them before the attach, as `slInit` is missed (D129); the Overlay calling `slReflexGetState` itself breaks the thread contract the vendor's header states; **what remains is the route named in this row**, the Overlay calling two driver getters with the game's device, and a no-injection ETW route that gives the game-side markers only and makes the game post messages to its own window. Corrected there: `nvapi64.dll` exports **two** functions on the dev box (`nvapi_Direct_GetMethod` beside `nvapi_QueryInterface`), not one. The go or no is the owner's, and a go needs the owner's ruling that calling a driver getter with the game's device is inside rule 4. **2026-11-13 — the owner answered (D132, D133).** Route D goes to the spike this row names, on `hook-harness` and a stub `nvapi64.dll`, with the ruling: a driver's read-only getter called with the device of the swap chain the Overlay hooks is inside rule 4 (`CLAUDE.md`, the rule's note of that day). No real game before the owner has seen the result, and nothing shipped changes for the spike (`spike-notes` §31, written after 0.1.0-beta.46). Route C is **refused**; the ETW route **stays closed**, and §G is not reopened. **2026-11-13 — the harness spike is done (`spike-notes` §31), and none of its stop conditions fired.** With a stand-in module: nothing is called or loaded when `nvapi64.dll` is absent, a missing getter is refused whole, an error and a report of nothing read as what they are, and a call the driver holds for seconds stops only the thread that made it — so not the watchdog. With the installed driver (32.0.16.2114, RTX 5080), in the probe's own process and with the probe setting the markers a game would: no fault before `NvAPI_Initialize`, without markers, or across 38 million reads beside a marker-setting thread; a call costs half a microsecond to a microsecond and a half; the report is readable from markers alone, in microseconds; and the Direct3D 12 **device** — the object the Overlay already holds — is what the driver takes. What only a game can say is unanswered: a game's own device, a real report, another driver. **The owner's next word is go or no for one real title**; a go is a plan of its own first. **2026-11-13, the same evening — go (D136)**: a plan for one title, Cyberpunk 2077; no code before the plan is approved, and no release carrying it before a stop while a game runs has been exercised on 0.1.0-beta.46 (owner-only item 44 (d)). **2026-11-13, the plan and four more answers (D138–D141).** The read has **no switch of its own**: it is part of Advanced metrics, so after the release 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, not a limit in code (D138). The probe ran a leg with a sleep mode first (D139; `spike-notes` §31, *The leg with a sleep*): **the getters do not wait behind `NvAPI_D3D_Sleep`** — thirty-one million reads beside a thread that slept 97 % of the time, none of a millisecond; a read after a sleeping frame costs about 2.6 µs. An `nvapi64.dll` loaded from the game's own folder is refused with the reason (D140). One call of 2 ms or more switches the read off until the game exits (D141). The plan's design, as reviewed against the source, is in [`handoff/history/0.1.0-beta.46.md`](handoff/history/0.1.0-beta.46.md) §The train after 0.1.0-beta.46. **2026-11-13, night — written; released as 0.1.0Line truncated
|
||||
| M14 ❓ | **Reflex latency per frame — is there a route within rules 4 and 5? (Train C, 2026-11-11.)** `17_HOOK_ENGINE` §Memory / latency names hooks on `NvAPI_D3D_SetSleepMode` / `SetLatencyMarker` and a call to `NvAPI_D3D_GetLatency`. NVAPI resolves all three through `nvapi_QueryInterface` by id — they are not exports, so a hook on them is a patch at an address learned at run time, the class refused on 2026-08-09. The route to try first needs no hook: the Overlay's own background thread **calls** `GetLatency` with the device of the swap chain it already hooks, once a second (the call returns the last 64 frames' reports). Unknown: whether calling into the driver from that thread is safe on every device kind, what it costs, what it returns when the game never enabled Reflex, and what it means for the Disclaimer's sentence about that thread. | **A spike on `hook-harness` and a stub first, then one real title.** Pre-committed: no route without a patch at a run-time address or a loader-lock call on the game's thread → Reflex stays N/A and the page says why; overhead above NFR-1 → the same. The owner says go or no on the spike's result. **2026-11-12 — the reading that comes before that spike is `spike-notes` §30** (owner decision D130: a document first, beside 0.1.0-beta.45; nothing was run). It finds: a hook on NVAPI's latency functions is the refused class, and a hook on Streamline's Reflex and PCL functions is train D's wrapper (§M15) — and would miss a game that fetched them before the attach, as `slInit` is missed (D129); the Overlay calling `slReflexGetState` itself breaks the thread contract the vendor's header states; **what remains is the route named in this row**, the Overlay calling two driver getters with the game's device, and a no-injection ETW route that gives the game-side markers only and makes the game post messages to its own window. Corrected there: `nvapi64.dll` exports **two** functions on the dev box (`nvapi_Direct_GetMethod` beside `nvapi_QueryInterface`), not one. The go or no is the owner's, and a go needs the owner's ruling that calling a driver getter with the game's device is inside rule 4. **2026-11-13 — the owner answered (D132, D133).** Route D goes to the spike this row names, on `hook-harness` and a stub `nvapi64.dll`, with the ruling: a driver's read-only getter called with the device of the swap chain the Overlay hooks is inside rule 4 (`CLAUDE.md`, the rule's note of that day). No real game before the owner has seen the result, and nothing shipped changes for the spike (`spike-notes` §31, written after 0.1.0-beta.46). Route C is **refused**; the ETW route **stays closed**, and §G is not reopened. **2026-11-13 — the harness spike is done (`spike-notes` §31), and none of its stop conditions fired.** With a stand-in module: nothing is called or loaded when `nvapi64.dll` is absent, a missing getter is refused whole, an error and a report of nothing read as what they are, and a call the driver holds for seconds stops only the thread that made it — so not the watchdog. With the installed driver (32.0.16.2114, RTX 5080), in the probe's own process and with the probe setting the markers a game would: no fault before `NvAPI_Initialize`, without markers, or across 38 million reads beside a marker-setting thread; a call costs half a microsecond to a microsecond and a half; the report is readable from markers alone, in microseconds; and the Direct3D 12 **device** — the object the Overlay already holds — is what the driver takes. What only a game can say is unanswered: a game's own device, a real report, another driver. **The owner's next word is go or no for one real title**; a go is a plan of its own first. **2026-11-13, the same evening — go (D136)**: a plan for one title, Cyberpunk 2077; no code before the plan is approved, and no release carrying it before a stop while a game runs has been exercised on 0.1.0-beta.46 (owner-only item 44 (d)). **2026-11-13, the plan and four more answers (D138–D141).** The read has **no switch of its own**: it is part of Advanced metrics, so after the release 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, not a limit in code (D138). The probe ran a leg with a sleep mode first (D139; `spike-notes` §31, *The leg with a sleep*): **the getters do not wait behind `NvAPI_D3D_Sleep`** — thirty-one million reads beside a thread that slept 97 % of the time, none of a millisecond; a read after a sleeping frame costs about 2.6 µs. An `nvapi64.dll` loaded from the game's own folder is refused with the reason (D140). One call of 2 ms or more switches the read off until the game exits (D141). The plan's design, as reviewed against the source, is in [`handoff/history/0.1.0-beta.46.md`](handoff/history/0.1.0-beta.46.md) §The train after 0.1.0-beta.46. **2026-11-13, night — written; released as 0.1.0Line truncated
|
||||
| M15 ❓ | **The Streamline state behind `slGetFeatureFunction` — re-examined, not reopened (Train D, 2026-11-11).** The owner asked for the refusal in `handoff/history/p0-queue-1-6.md` to be looked at again. `18_GPU_VENDOR_APIS` §The trains states the route to try (hook the export, hand back a wrapper for a fixed list of names) and what it raises: the wrapper is a write to what the game receives, which rule 4 forbids as written; a wrapper must outlive the Overlay's unhook; a game that fetched its functions before the hook existed is never seen. | **A written design against each of the five grounds, then a spike.** Pre-committed: any ground unanswered → the route stays refused, and `sl.dlssg.*`, `sl.reflex.*` and the rest of that block read N/A with "refused" as the reason. Proceeding needs the owner's amendment of rule 4, asked with the rule quoted. |
|
||||
| M10 ✅ | ~~PDH `\GPU Engine(*)\Utilization Percentage` summed across engines does not reproduce the Task Manager figure the doc invokes. Decide what we actually report and label it accordingly~~ **Decided 2026-09-09 (PR-E1): L1 does not read the engine counters at all.** `LoadPct` is L2's vendor-reported `GPU Core` load (measured ✓ on NVIDIA, §M5 row R1) and is labelled *GPU load (vendor)* wherever it is shown; on a machine without L2 the field is N/A, never a sum that is not the number the user expects. What L1 does read from PDH is one counter, `\GPU Adapter Memory(luid_…_phys_0)\Dedicated Usage`, bound by LUID — the figure Task Manager labels "Dedicated GPU memory", measured 1301 MB at an idle desktop on the RTX 5080. Reopening this needs a measurement of `max(engine)` against Task Manager's own number, not a decision |
|
||||
|
||||
|
||||
+100
-111
@@ -86,6 +86,7 @@ owner-only items stay below; the history of every train, the passed owner-only i
|
||||
| `§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`](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`](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`](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) |
|
||||
| `§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) |
|
||||
@@ -93,134 +94,86 @@ owner-only items stay below; the history of every train, the passed owner-only i
|
||||
|
||||
---
|
||||
|
||||
## **START HERE** — 2026-11-14, 0.1.0-beta.47: the part inside a game asks NVIDIA's driver for its latency report; the batch log says how a batch ended
|
||||
## **START HERE** — 2026-11-14, 0.1.0-beta.48: two real games read; the driver's own GPU times beside a span that includes idle; every multiplier seen; samples a second apart
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.47.md`; this is what no other file carries.* The owner ran five sessions on
|
||||
beta.46 the evening it was released and said: check and go on. They were read (#439), the owner took six decisions
|
||||
(D136–D141) and approved the plan of the train the same evening, and the five pull requests of it were merged
|
||||
overnight: #440 (the decisions; the probe's leg with a sleep mode), #441 (D137), #442 (the latency words of region
|
||||
5), #443 (the Overlay makes the read; the gates; the fixtures), #444 (the Agent, the App, the legal texts,
|
||||
owner-only item 45). The release was held for item 44 (d), which the owner ran on 2026-11-14 (#445, and below).
|
||||
**What the five sessions showed, the design of the train as the plan's review left it, and the traps of beta.46
|
||||
are [`handoff/history/0.1.0-beta.46.md`](handoff/history/0.1.0-beta.46.md)**; what the read is and what bounds it
|
||||
is [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Calls the Overlay makes into a driver; what was measured is
|
||||
[`spike-notes/31-reflex-route-d-harness.md`](spike-notes/31-reflex-route-d-harness.md).
|
||||
*Status is `docs/changelog/0.1.0-beta.48.md`; this is what no other file carries.* The owner ran eight sessions on
|
||||
beta.47 the morning it was released and said, twice: check. They were read (#448, #449): Phantom Blade Zero three
|
||||
times, Cyberpunk 2077 twice, two Direct3D 11 games and a Direct3D 12 game with no NVIDIA library — **the read
|
||||
works in real games**, and four things came out of it that the owner ruled on the same morning (D142–D147) and
|
||||
approved as one train: #450 (the Overlay reads two more members of the report and keeps the multipliers seen),
|
||||
#451 (the Agent, the App, the texts — Privacy Policy 2.21, Disclaimer 2.17), #452 (the poller's period), and this
|
||||
release. **What the eight sessions showed is item 45's last paragraphs, below; beta.47's own section, its traps
|
||||
and its release facts are [`handoff/history/0.1.0-beta.47.md`](handoff/history/0.1.0-beta.47.md)**; what the
|
||||
read is and what bounds it is [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Calls the Overlay makes into a driver.
|
||||
|
||||
### What this release decided, beyond D136–D141
|
||||
### What this release decided, beyond D142–D147
|
||||
|
||||
- **It is the first thing the Overlay does in a game that is not reading a hooked call's arguments**, and it is
|
||||
listed as that — its own table in `17_HOOK_ENGINE`, its own reach in the catalog (`GameDriver`, not a stretched
|
||||
`Game`), its own paragraph in the Disclaimer. A second call of this kind needs a ruling of the same kind (D132).
|
||||
- **Resolve on the watchdog, once for the process; call on the presenting thread, after the record is published,
|
||||
behind one gate of four states** — idle, armed, reading, off. The plan's first draft had a busy flag beside
|
||||
accumulators: two presenting threads could have read back to back, and the watchdog could have published half a
|
||||
read. The whole design as reviewed is in the history file, §The train after 0.1.0-beta.46.
|
||||
- **`nvapi64.dll` is a shim.** The check that the two addresses lie inside the module it asked refused the real
|
||||
driver: the getters are in `nvapi64_impl.dll`, in the driver's store. An address is accepted when it is executable
|
||||
code of a loaded image, and a reference is kept on that image too. Only the run against the installed driver
|
||||
could find it — the stand-in answers with addresses of its own.
|
||||
- **The code that is called is a Control Flow Guard image**; the plan's review had reasoned from the shim, which is
|
||||
not. The probe enforces CFG and makes the calls from the header that ships, so this driver's getters are valid
|
||||
targets. A CFG-enforcing game on another driver is not covered, and a refusal there is a fast-fail.
|
||||
- **The layout stayed 5**: ten reserved words of region 5 took the read. `FL_HOOK_REFLEX`, `FL_MEASURED_LATENCY`
|
||||
and `reflexLatencyUs` stay unset — there is no hook, and the numbers are series beside the frames.
|
||||
- **D141 was asked twice.** A run on a busy PC showed the 2 ms latch can fire on a pause that was Windows'; the
|
||||
owner kept one call. Do not re-ask without a real game's numbers.
|
||||
- **What the game asked of Reflex, and Reflex through Streamline, are `RefusedRoute`** — a patch at a run-time
|
||||
address, and a call the vendor forbids from another thread (D133). `sl.pcl.markers` waits for train D's spike.
|
||||
|
||||
### What item 44's last part showed (2026-11-14)
|
||||
|
||||
- **A first try did not exercise it** (sessions 203–205, #445): *Disable all hooking* was on before the games were
|
||||
started, so two sessions were `RefusedKillSwitch` with nothing injected, and the hooked one ran to its exit.
|
||||
- **The second try did, twice, in Phantom Blade Zero** (sessions 206 and 207): the game started with the switch
|
||||
off, was recorded for a minute and a half, and the switch was turned on while it ran. Each log has `STOP` at the
|
||||
next safety scan, **an `UNHOOK_RESTORED` line for every one of the twenty-nine patches, all at one time**, one
|
||||
`PATCH_BATCH restore` — **83 309 µs and 85 578 µs for twenty-nine** — and `STOP_FLUSHED … a=1`. Nothing was
|
||||
declined. Both sessions ended `KillSwitchEngaged`, tier 1, no fault, no record dropped, writer status
|
||||
*unhooked*; the game ran on for three and four minutes and closed with nothing in Windows' application log.
|
||||
Restoring twenty-nine one by one would have cost about 2.4 s at this game's 84 ms a stop.
|
||||
- **Not said by the logs**: whether the owner felt a hitch at the stop. Not exercised: (e) a game with no
|
||||
Streamline and (g) off means off — both are parts of item 45 now.
|
||||
- **Two more members of a report already fetched are not a new call.** Rule 4's note stands as written: the same
|
||||
two getters, the Overlay's own buffer, the two names on `tools/overlay-allowed-fields.txt`. The owner ruled on
|
||||
them by name (D142); a third member is asked the same way.
|
||||
- **The driver's own times have a count each, and zero means not given.** An older driver leaves both zero, and
|
||||
so did the probe's frames. They are added after the frame is accepted, so which frames the seven spans are made
|
||||
of did not move — a session's old series mean what they meant.
|
||||
- **An entry of their own in the catalog** (`nvapi.reflex.gpu_times`), not an eighth and ninth line of the frame
|
||||
report: `AdvancedPresenter.MaxLines` is 8, and nine series of one entry are drawn as a band.
|
||||
- **The layout stayed 5 again**: line 0 of region 5 was full, so the four words came out of the seven reserved
|
||||
words that ended the `sl::DLSSOptions` line. Three remain there, two on the `sl::Constants` line, two on the
|
||||
FidelityFX line.
|
||||
- **The fact's key no longer holds the last multiplier.** It held it since beta.47, so every menu rewrote the
|
||||
session's context.
|
||||
- **`hz` is measured from the samples, not taken from the setting**: the finalizer cannot see the setting, and a
|
||||
session recovered from a `.partial` file never knew it.
|
||||
- **The plan named `tools/agent-cost` for the poller's change and it was not run**: it runs the Agent unelevated,
|
||||
where a poll takes a millisecond and the period was already a second. Said in #452 rather than run for show.
|
||||
|
||||
### Traps this train left
|
||||
|
||||
- **A bash here-document ate backslashes again** and wrote a NUL byte into a `.cpp`. Edit scripts are files.
|
||||
- **A file made by the Write tool is LF**; `dotnet format --verify-no-changes` fails a new `.cs` for it. Convert.
|
||||
- **`NvAPI_Status(__cdecl*)(…)` is a call by name to `nvapi-readonly-check`**: the status type has an alias in
|
||||
`fl_reflex.h`. And a member of the Overlay's own named like a vendor's (`fgMultiplier`) fails
|
||||
`overlay-fields-check` outside the header.
|
||||
- **A copy of the harness in `%TEMP%` leaves an overlay log the run's sweep does not own** (it matches this
|
||||
build's harness by path): the test that makes the copy sweeps it.
|
||||
- **Stacked pull requests, with a dirty tree**: once the lower one is squash-merged GitHub retargets the next to
|
||||
`main`; `gh pr update-branch` works while the upper branch only adds, and conflicts once it edited lines the
|
||||
lower one added — then `git rebase -S --onto origin/main <lower tip> <branch>` and a forced push with lease.
|
||||
- **Advisory checks found real things after the local gate was green**: SonarCloud a `wcslen`, Qodana's native
|
||||
report a `switch` that did not name two enumerators, its managed report two redundant qualifiers and a
|
||||
redundant `!`. Hold a merge until both have reported.
|
||||
- **The probe's numbers depend on what else the PC does**: a run beside a build read 3.4 µs where three alone read
|
||||
2.6, and saw reads of 2 ms. Say which kind a number is.
|
||||
- **A cause I wrote down before checking it.** "The third of a second is the processor's temperature" went into
|
||||
five files on two facts — unelevated a poll takes a millisecond; the sessions without a `cpu_temp` series are a
|
||||
second apart — and then four sessions *with* the series turned out to be a second apart too. The texts were
|
||||
taken back to what is established before the commit. **Count the exceptions before naming a cause.**
|
||||
- **A bash here-document ate a backslash again** (a Python one-liner with `'\\'`). Edit scripts are files — the
|
||||
rule already existed.
|
||||
- **`FETCH_HEAD` belongs to the worktree that fetched.** A merge in a second worktree needs the commit's id.
|
||||
- **A squash-merge of the lower pull request conflicts the upper one in `CHANGELOG.md` every time** both added to
|
||||
`[Unreleased]`. With Auto-fix on, the app asks for a merge of `main`, not a rebase: do it in a worktree of its
|
||||
own when a gate is running in the main one, keep the upper branch's file (it is the superset), and check that
|
||||
the merged tree equals the branch's tip — then the gate already run still stands.
|
||||
- **The gate script's last lines do not reach a background task's output**: read the log's last line and hash the
|
||||
`rules` folder by hand.
|
||||
- **An analyzer wants a `<summary>` once any `<param>` is written** (RCS1139).
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**The owner runs item 45**~~ **Run on 2026-11-14 in Phantom Blade Zero, three sessions: the read works in a
|
||||
real game** (item 45's last paragraphs) — the driver was found, read every second, and no call took more than
|
||||
45 µs. **Cyberpunk 2077 followed the same morning, twice, and three games the read must leave alone** (sessions
|
||||
211–215): read, 65 µs at the slowest, and *not read* where it should be. **Still to run of it**: Reflex off in
|
||||
a game's menu, off means off; and the owner's word on whether the games felt different.
|
||||
2. **The owner answered on the *GPU render* line (2026-11-14): read the driver's active time.** Two more members
|
||||
of the report FrameLedger already fetches — no further call into the driver. ~~**Plan first**~~ **Planned and
|
||||
approved the same day as the train of 0.1.0-beta.48 (D142–D147)**: the native half first, then the Agent, the
|
||||
App and the texts, then the sampling period, then the release and owner-only item 46 — one batch of tests for
|
||||
the owner, with what is left of item 45 in it. What the plan gathered: the multiplier row that keeps only the last value, the pages that still say no real game
|
||||
was read, the Agent's 1.32 s between samples beside `hz` 1.0. The owner tests what is left once, on that
|
||||
release. Still the owner's to say: more titles; the session summary's latency fields; D141 (the slowest call
|
||||
seen in a game is 65 µs, thirty times under it).
|
||||
1. **The owner runs item 46** — one batch on beta.48, with what is left of item 45 in it. Every outcome's meaning
|
||||
is written there.
|
||||
2. **Then the owner's to say**: more titles; D141 on a larger sample (the slowest call seen in a game is 65 µs);
|
||||
whether the processor update is worth timing on their PC and moving off the poll's thread (below).
|
||||
3. **`slAllocateResources`** keeps its patch (D135); looked at again when there are more sessions.
|
||||
4. **Train D** after train C, the same way: a spike first — `sl.pcl.markers` waits for it, and §30 found its hook
|
||||
4. **Train D** after it, the same way: a spike first — `sl.pcl.markers` waits for it, and §30 found its hook
|
||||
would miss a game that fetched its functions before the attach.
|
||||
|
||||
### 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.47 was released 2026-11-14T01:11:19Z** (08:11 in the owner's time zone) from the signed
|
||||
tag on `3d7c273` (#446), by run 43537436561 — 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; the four shipped natives carry
|
||||
`FL_BUILD_ID v0.1.0-beta.47`. The delta from beta.46 is 1 820 144 bytes beside a full package of 110 795 507 —
|
||||
"Delta processed 0452 files. 0024 patched, 0428 unchanged". The wiki was published by run 43539059710. The
|
||||
rehearsal on the release branch (run 43534606602, at `43426fe`, the released tree) had made a delta of 1 838 295
|
||||
bytes with the same file counts. **SonarCloud answered on `3d7c273`: 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 the advisory checks
|
||||
found three things after local gates were green (§Traps), and no required check failed.
|
||||
- **The release branch's local gate was red once, for a reason outside the code** (2026-11-14 07:20): the freshly
|
||||
linked `fl_guard_test.exe` was gone from the build tree seconds after the gate began — Windows Defender's log has
|
||||
three configuration changes at 07:20:53–56 and no detection; which security program removed the file is not
|
||||
known, and nothing of its settings was looked at further or touched. `fl_guard` ended after 0.72 s **and was
|
||||
counted as failed, not passed**: the rule of #438 (a native test names the line it ends on) did what it was
|
||||
written for. Run again, the gate was green.
|
||||
- ~~**No real game has run the read.**~~ Two have (Phantom Blade Zero and Cyberpunk 2077, 2026-11-14). **The accuracy
|
||||
statement, `LIMITATIONS.md` and the guide still say no real game had been read**: true when written, to be
|
||||
brought up to date with the next release, as beta.46's pages were.
|
||||
- **In Phantom Blade Zero the driver's *GPU render* span is longer than its total** (item 45): shown as reported,
|
||||
not explained. In Cyberpunk 2077 it is not. The owner's answer: read the driver's active time (NEXT 2).
|
||||
- ~~**The Agent's samples are 1.32 s apart while `sensor_blobs.hz` says 1.0**~~ (seen 2026-11-14 in the `t_ms`
|
||||
series). **Looked into the same day (D146)**: the poller waited its whole interval after a poll's work; only
|
||||
the App's series loader reads `hz`, and only where a row has no `t_ms`, so no chart was wrong. The poller now
|
||||
keeps a fixed period and `hz` is measured from the samples (`06_DATA_MODEL` §sensor_blobs) — in no release yet.
|
||||
- **Where the third of a second goes is not established.** Unelevated, a poll takes about a millisecond (the
|
||||
layers composed as the Agent composes them, each read under a stopwatch). In the owner's ledger 180 of 186
|
||||
- **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.
|
||||
- **No real game has given the two new figures yet.** In the probe `gpuActiveRenderTimeUs` read 0; whether
|
||||
Phantom Blade Zero's is the short number the reading of 2026-11-14 expects is item 46's to say.
|
||||
- **Where the third of a second of a poll goes is not established.** Unelevated, a poll takes about a millisecond
|
||||
(the layers composed as the Agent composes them, each read under a stopwatch). In the owner's ledger 180 of 186
|
||||
sessions are 1.32 s apart and six are 1.0 s: the two with no `cpu_temp` series (an Agent not elevated) are among
|
||||
the six — which points at the sensor library's processor update, run on the poll's thread as administrator
|
||||
with PawnIO — **but four sessions that have the series kept one second** (22, 72, 73, 136). **Not measured**:
|
||||
that call itself (it needs elevation), and whether it is processor time or waiting. Not changed; the period no
|
||||
longer depends on it. The owner's to say whether it is worth timing on their PC and moving off the poll's thread.
|
||||
that call itself (it needs elevation), and whether it is processor time or waiting. The period no longer
|
||||
depends on it; a poll that takes a third of every second is still a poll that takes a third of every second.
|
||||
- **With the sensor interval above one second, some readings of the driver's report are not stored**: the newest
|
||||
stands until a sample carries it (`SessionRecorder`). Said in the guide; not changed.
|
||||
- **No test runs the whole path through the real Agent**: the injected tests stop at the shared memory and the
|
||||
sampler's start from it; no end-to-end case loads the stand-in module under an Agent session.
|
||||
- **Two install batches of beta.46 took 0.61 s and 1.26 s and nothing explains them** (Hogwarts Legacy, Cyberpunk
|
||||
2077). Since this release the log says whether a batch went singly; the next long one can be read.
|
||||
- **Two install batches of beta.46 took 0.61 s and 1.26 s and nothing explains them.** Cyberpunk 2077's eight
|
||||
batches on beta.47 took 85–221 ms, each in one apply; Hogwarts Legacy has not been run since.
|
||||
- **The Japanese strings are new and unreviewed**, as every `ja` string is.
|
||||
- **Off means off has never been exercised on a real game** (item 43 (f), item 44 (g), now item 45 (g)); nor (c)
|
||||
- **Off means off has never been exercised on a real game** (item 43 (f), 44 (g), 45 (g), now 46 (e)); nor (c)
|
||||
and (h) of item 43, which only the owner sees.
|
||||
- **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.
|
||||
@@ -232,9 +185,8 @@ is [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Calls the Overlay makes into a dri
|
||||
- **`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:** what is left of item 45 (Reflex off in a game's menu; off means off; how it felt); one session
|
||||
each of Valor Mortis and Black Myth: Wukong with hooking off; what item 41 left unexercised;
|
||||
item 40 (d).
|
||||
**Owner-only:** item 46; 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
|
||||
|
||||
@@ -832,6 +784,43 @@ item 40 (d).
|
||||
**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.**
|
||||
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 `fgMultiplier` row 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, and `hz` says 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. *`fgMultiplier` shows 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's `LATENCY` lines 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 a `LATENCY` line*: 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.
|
||||
|
||||
**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
|
||||
|
||||
@@ -0,0 +1,90 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.48 was cut, 2026-11-14 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.48] - 2026-11-14
|
||||
|
||||
**The forty-eighth pre-release: NVIDIA's latency report has now been read in real games, and what they showed is
|
||||
in it.** On the day 0.1.0-beta.47 came out the owner recorded eight sessions with *Advanced metrics* on. The
|
||||
report was read in Phantom Blade Zero and in Cyberpunk 2077, with frame generation on and off: the driver answered
|
||||
every second, the slowest request took 65 millionths of a second, nothing was switched off, and no game was
|
||||
disturbed that the logs can show. Two games that are not Direct3D 12 and one that never loaded NVIDIA's library
|
||||
were left alone, each with its one line saying why. The same unsigned installer: verify its hash against
|
||||
`SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**What the first game showed, and what this release does about it.** In Phantom Blade Zero the line called *GPU
|
||||
render* was longer than the whole frame — 16 thousandths of a second where the total was 5. That line runs from
|
||||
the moment the graphics card starts on a frame to the moment it ends, **and includes the time the card waited in
|
||||
between**. NVIDIA's driver also works out the figure without the waiting, and the time from one frame's end to the
|
||||
next. Both are in the report FrameLedger already asks for, and a session now stores them as **a second chart under
|
||||
*Latency*, with two lines**: *GPU active render* and *GPU frame time*. Nothing more is asked of the driver. The
|
||||
old line stays, under a name that says what it includes. **The stages of a frame overlap; they were never parts
|
||||
that add up to the total**, and the texts now say so.
|
||||
|
||||
**Three more things the sessions showed.**
|
||||
- The table of the driver's low-latency state kept only the *last* frame-generation multiplier: a session that
|
||||
generated frames at ×2 and ended in a menu showed 1. It now lists every value the session saw — *1, 2*.
|
||||
- **Sensors were read every 1.3 seconds where the setting says every second** — on the owner's PC, in nearly every
|
||||
session since the series began. The capture agent waited the whole interval *after* each reading, and a reading
|
||||
there takes about a third of a second. It now keeps the period. No chart was wrong, because every sample is
|
||||
stored with its own time; but a session now has about a third more samples, and readings of the latency report
|
||||
no longer fall between two of them. What makes a reading take that long there is not established.
|
||||
- A session could begin with the last reading of the session before it, in a game that kept running between the
|
||||
two. It no longer does.
|
||||
|
||||
**What it is not.** Two games on one driver and one card (GeForce RTX 5080, driver 32.0.16.2114) are not every
|
||||
game. The two new figures have not been seen from a real game yet: a driver may give neither, and the chart is
|
||||
then simply not there. Reflex switched off in a game's menu, and a game started with Advanced metrics off, have
|
||||
still not been tried on a real game. They remain the driver's numbers, not a measurement by FrameLedger, and not
|
||||
the delay from a click to the screen; the session summary's latency fields still read N/A. Nothing here is read
|
||||
on Direct3D 11, Vulkan or OpenGL. The Japanese texts are new and unreviewed.
|
||||
|
||||
**Measured overhead this release.** A presented frame: unchanged. The request to the driver, once a second while
|
||||
Advanced metrics is on: summing the two further figures adds about 36 billionths of a second to work that follows
|
||||
the request itself. In the real games of 2026-11-14 the slowest request took 20 to 65 millionths of a second.
|
||||
|
||||
**Updating from `0.1.0-beta.47`:** Help ▸ Check for updates, then *Restart to update* with no game running. **The
|
||||
terms are shown once** — Privacy Policy 2.21 and Disclaimer 2.17. No change to the ledger (schema 23) or to the
|
||||
shared memory's layout (5); the detection rules stay at `2026.11.2`. **The code loaded into a game changed in this
|
||||
release**, so a game that was running during the update keeps the old part until it is started again.
|
||||
|
||||
### Added
|
||||
|
||||
- **Two more lines from NVIDIA's latency report: how long the graphics card was really at work** (owner decision
|
||||
D142). In a real game the driver's *GPU render* stage turned out longer than the whole frame: it runs from the
|
||||
card's start to its end and includes the time the card waited. With Advanced metrics on, a session now also
|
||||
stores two figures the driver works out itself — **GPU active render**, the same stage without the waiting, and
|
||||
**GPU frame time**, from the end of one frame's work to the end of the next — as a second chart under *Latency*.
|
||||
They come from the report FrameLedger already asks the driver for; nothing more is asked. A driver may give
|
||||
neither, and the chart is then not there. Sessions recorded before this release do not have them.
|
||||
|
||||
- **For developers: the part inside a game reads two more figures of NVIDIA's latency report, and keeps every
|
||||
frame-generation multiplier a session saw** (owner decisions D142, D144). In a real game the driver's span between its two GPU marks was longer than the frame's whole
|
||||
— it includes the card's waiting. The driver's own *active* render time and its GPU frame time are members of
|
||||
the report FrameLedger already fetches; they are read from it, with **no further call into the driver**. Four
|
||||
reserved words of the shared memory carry them and the multipliers seen (layout 5 as it was). `fl_reflex_summary`
|
||||
and the injected `[latency]` cases hold it. Measured: +36 ns a read, once a second.
|
||||
|
||||
### Changed
|
||||
|
||||
- **The *GPU render* line says what it includes** (owner decision D143): *GPU render, start to end (idle time
|
||||
included)*, in the three languages. The numbers are the same.
|
||||
- **The driver's frame-generation multiplier is every value the session saw** (owner decision D144). The table of
|
||||
the driver's low-latency state kept only the last one: a session that generated frames at ×2 and ended in a menu
|
||||
showed 1. It now shows *1, 2*. Sessions already recorded keep what they stored.
|
||||
- **The texts say what was read** (owner decision D145). The accuracy statement, the README and the guide said no
|
||||
real game had been read; two have been, on one driver. They also say now that the stages overlap and do not add
|
||||
up to the total. **Privacy Policy 2.21** names the two new averages; **Disclaimer 2.17** changes only with the
|
||||
accuracy statement it carries. The terms window shows once.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Sensors were read less often than the setting says** (owner decision D146). With the sensor interval at
|
||||
1000 ms, nearly every session on the owner's PC got a sample every 1.3 seconds: the Agent waited the whole
|
||||
interval *after* each reading, and a reading there takes about a third of a second (what in it does is not
|
||||
established; on a PC where the Agent is not run as administrator it takes a millisecond, and the samples were
|
||||
already a second apart). It now keeps the period. No chart was wrong — every sample is stored with its own time — but a session
|
||||
has about a third more samples now, and about a quarter of the readings of NVIDIA's latency report no longer
|
||||
fall between two samples. For developers: `sensor_blobs.hz` was the constant 1 and is now the rate the
|
||||
session's samples had.
|
||||
- **A session could start with the last read of the session before it.** In a game that kept running between two
|
||||
sessions, a read of the driver's latency report that ended after the first session's last tick was taken as the
|
||||
second session's first point. A new session now drops it.
|
||||
@@ -0,0 +1,146 @@
|
||||
# HANDOFF history — 0.1.0-beta.47
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.48 was cut, 2026-11-14 (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 it writes is relative to `docs/`. **Its NEXT and its "Left open" were written through the morning of 2026-11-14 as the owner's sessions were read**: what they led to is HANDOFF.md's section for 0.1.0-beta.48.*
|
||||
|
||||
## **START HERE** — 2026-11-14, 0.1.0-beta.47: the part inside a game asks NVIDIA's driver for its latency report; the batch log says how a batch ended
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.47.md`; this is what no other file carries.* The owner ran five sessions on
|
||||
beta.46 the evening it was released and said: check and go on. They were read (#439), the owner took six decisions
|
||||
(D136–D141) and approved the plan of the train the same evening, and the five pull requests of it were merged
|
||||
overnight: #440 (the decisions; the probe's leg with a sleep mode), #441 (D137), #442 (the latency words of region
|
||||
5), #443 (the Overlay makes the read; the gates; the fixtures), #444 (the Agent, the App, the legal texts,
|
||||
owner-only item 45). The release was held for item 44 (d), which the owner ran on 2026-11-14 (#445, and below).
|
||||
**What the five sessions showed, the design of the train as the plan's review left it, and the traps of beta.46
|
||||
are [`handoff/history/0.1.0-beta.46.md`](handoff/history/0.1.0-beta.46.md)**; what the read is and what bounds it
|
||||
is [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Calls the Overlay makes into a driver; what was measured is
|
||||
[`spike-notes/31-reflex-route-d-harness.md`](spike-notes/31-reflex-route-d-harness.md).
|
||||
|
||||
### What this release decided, beyond D136–D141
|
||||
|
||||
- **It is the first thing the Overlay does in a game that is not reading a hooked call's arguments**, and it is
|
||||
listed as that — its own table in `17_HOOK_ENGINE`, its own reach in the catalog (`GameDriver`, not a stretched
|
||||
`Game`), its own paragraph in the Disclaimer. A second call of this kind needs a ruling of the same kind (D132).
|
||||
- **Resolve on the watchdog, once for the process; call on the presenting thread, after the record is published,
|
||||
behind one gate of four states** — idle, armed, reading, off. The plan's first draft had a busy flag beside
|
||||
accumulators: two presenting threads could have read back to back, and the watchdog could have published half a
|
||||
read. The whole design as reviewed is in the history file, §The train after 0.1.0-beta.46.
|
||||
- **`nvapi64.dll` is a shim.** The check that the two addresses lie inside the module it asked refused the real
|
||||
driver: the getters are in `nvapi64_impl.dll`, in the driver's store. An address is accepted when it is executable
|
||||
code of a loaded image, and a reference is kept on that image too. Only the run against the installed driver
|
||||
could find it — the stand-in answers with addresses of its own.
|
||||
- **The code that is called is a Control Flow Guard image**; the plan's review had reasoned from the shim, which is
|
||||
not. The probe enforces CFG and makes the calls from the header that ships, so this driver's getters are valid
|
||||
targets. A CFG-enforcing game on another driver is not covered, and a refusal there is a fast-fail.
|
||||
- **The layout stayed 5**: ten reserved words of region 5 took the read. `FL_HOOK_REFLEX`, `FL_MEASURED_LATENCY`
|
||||
and `reflexLatencyUs` stay unset — there is no hook, and the numbers are series beside the frames.
|
||||
- **D141 was asked twice.** A run on a busy PC showed the 2 ms latch can fire on a pause that was Windows'; the
|
||||
owner kept one call. Do not re-ask without a real game's numbers.
|
||||
- **What the game asked of Reflex, and Reflex through Streamline, are `RefusedRoute`** — a patch at a run-time
|
||||
address, and a call the vendor forbids from another thread (D133). `sl.pcl.markers` waits for train D's spike.
|
||||
|
||||
### What item 44's last part showed (2026-11-14)
|
||||
|
||||
- **A first try did not exercise it** (sessions 203–205, #445): *Disable all hooking* was on before the games were
|
||||
started, so two sessions were `RefusedKillSwitch` with nothing injected, and the hooked one ran to its exit.
|
||||
- **The second try did, twice, in Phantom Blade Zero** (sessions 206 and 207): the game started with the switch
|
||||
off, was recorded for a minute and a half, and the switch was turned on while it ran. Each log has `STOP` at the
|
||||
next safety scan, **an `UNHOOK_RESTORED` line for every one of the twenty-nine patches, all at one time**, one
|
||||
`PATCH_BATCH restore` — **83 309 µs and 85 578 µs for twenty-nine** — and `STOP_FLUSHED … a=1`. Nothing was
|
||||
declined. Both sessions ended `KillSwitchEngaged`, tier 1, no fault, no record dropped, writer status
|
||||
*unhooked*; the game ran on for three and four minutes and closed with nothing in Windows' application log.
|
||||
Restoring twenty-nine one by one would have cost about 2.4 s at this game's 84 ms a stop.
|
||||
- **Not said by the logs**: whether the owner felt a hitch at the stop. Not exercised: (e) a game with no
|
||||
Streamline and (g) off means off — both are parts of item 45 now.
|
||||
|
||||
### Traps this train left
|
||||
|
||||
- **A bash here-document ate backslashes again** and wrote a NUL byte into a `.cpp`. Edit scripts are files.
|
||||
- **A file made by the Write tool is LF**; `dotnet format --verify-no-changes` fails a new `.cs` for it. Convert.
|
||||
- **`NvAPI_Status(__cdecl*)(…)` is a call by name to `nvapi-readonly-check`**: the status type has an alias in
|
||||
`fl_reflex.h`. And a member of the Overlay's own named like a vendor's (`fgMultiplier`) fails
|
||||
`overlay-fields-check` outside the header.
|
||||
- **A copy of the harness in `%TEMP%` leaves an overlay log the run's sweep does not own** (it matches this
|
||||
build's harness by path): the test that makes the copy sweeps it.
|
||||
- **Stacked pull requests, with a dirty tree**: once the lower one is squash-merged GitHub retargets the next to
|
||||
`main`; `gh pr update-branch` works while the upper branch only adds, and conflicts once it edited lines the
|
||||
lower one added — then `git rebase -S --onto origin/main <lower tip> <branch>` and a forced push with lease.
|
||||
- **Advisory checks found real things after the local gate was green**: SonarCloud a `wcslen`, Qodana's native
|
||||
report a `switch` that did not name two enumerators, its managed report two redundant qualifiers and a
|
||||
redundant `!`. Hold a merge until both have reported.
|
||||
- **The probe's numbers depend on what else the PC does**: a run beside a build read 3.4 µs where three alone read
|
||||
2.6, and saw reads of 2 ms. Say which kind a number is.
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**The owner runs item 45**~~ **Run on 2026-11-14 in Phantom Blade Zero, three sessions: the read works in a
|
||||
real game** (item 45's last paragraphs) — the driver was found, read every second, and no call took more than
|
||||
45 µs. **Cyberpunk 2077 followed the same morning, twice, and three games the read must leave alone** (sessions
|
||||
211–215): read, 65 µs at the slowest, and *not read* where it should be. **Still to run of it**: Reflex off in
|
||||
a game's menu, off means off; and the owner's word on whether the games felt different.
|
||||
2. **The owner answered on the *GPU render* line (2026-11-14): read the driver's active time.** Two more members
|
||||
of the report FrameLedger already fetches — no further call into the driver. ~~**Plan first**~~ **Planned and
|
||||
approved the same day as the train of 0.1.0-beta.48 (D142–D147)**: the native half first, then the Agent, the
|
||||
App and the texts, then the sampling period, then the release and owner-only item 46 — one batch of tests for
|
||||
the owner, with what is left of item 45 in it. What the plan gathered: the multiplier row that keeps only the last value, the pages that still say no real game
|
||||
was read, the Agent's 1.32 s between samples beside `hz` 1.0. The owner tests what is left once, on that
|
||||
release. Still the owner's to say: more titles; the session summary's latency fields; D141 (the slowest call
|
||||
seen in a game is 65 µs, thirty times under it).
|
||||
3. **`slAllocateResources`** keeps its patch (D135); looked at again when there are more sessions.
|
||||
4. **Train D** after train C, the same way: a spike first — `sl.pcl.markers` waits for it, and §30 found its hook
|
||||
would miss a game that fetched its functions before the attach.
|
||||
|
||||
### 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.47 was released 2026-11-14T01:11:19Z** (08:11 in the owner's time zone) from the signed
|
||||
tag on `3d7c273` (#446), by run 43537436561 — 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; the four shipped natives carry
|
||||
`FL_BUILD_ID v0.1.0-beta.47`. The delta from beta.46 is 1 820 144 bytes beside a full package of 110 795 507 —
|
||||
"Delta processed 0452 files. 0024 patched, 0428 unchanged". The wiki was published by run 43539059710. The
|
||||
rehearsal on the release branch (run 43534606602, at `43426fe`, the released tree) had made a delta of 1 838 295
|
||||
bytes with the same file counts. **SonarCloud answered on `3d7c273`: 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 the advisory checks
|
||||
found three things after local gates were green (§Traps), and no required check failed.
|
||||
- **The release branch's local gate was red once, for a reason outside the code** (2026-11-14 07:20): the freshly
|
||||
linked `fl_guard_test.exe` was gone from the build tree seconds after the gate began — Windows Defender's log has
|
||||
three configuration changes at 07:20:53–56 and no detection; which security program removed the file is not
|
||||
known, and nothing of its settings was looked at further or touched. `fl_guard` ended after 0.72 s **and was
|
||||
counted as failed, not passed**: the rule of #438 (a native test names the line it ends on) did what it was
|
||||
written for. Run again, the gate was green.
|
||||
- ~~**No real game has run the read.**~~ Two have (Phantom Blade Zero and Cyberpunk 2077, 2026-11-14). **The accuracy
|
||||
statement, `LIMITATIONS.md` and the guide still say no real game had been read**: true when written, to be
|
||||
brought up to date with the next release, as beta.46's pages were.
|
||||
- **In Phantom Blade Zero the driver's *GPU render* span is longer than its total** (item 45): shown as reported,
|
||||
not explained. In Cyberpunk 2077 it is not. The owner's answer: read the driver's active time (NEXT 2).
|
||||
- ~~**The Agent's samples are 1.32 s apart while `sensor_blobs.hz` says 1.0**~~ (seen 2026-11-14 in the `t_ms`
|
||||
series). **Looked into the same day (D146)**: the poller waited its whole interval after a poll's work; only
|
||||
the App's series loader reads `hz`, and only where a row has no `t_ms`, so no chart was wrong. The poller now
|
||||
keeps a fixed period and `hz` is measured from the samples (`06_DATA_MODEL` §sensor_blobs) — in no release yet.
|
||||
- **Where the third of a second goes is not established.** Unelevated, a poll takes about a millisecond (the
|
||||
layers composed as the Agent composes them, each read under a stopwatch). In the owner's ledger 180 of 186
|
||||
sessions are 1.32 s apart and six are 1.0 s: the two with no `cpu_temp` series (an Agent not elevated) are among
|
||||
the six — which points at the sensor library's processor update, run on the poll's thread as administrator
|
||||
with PawnIO — **but four sessions that have the series kept one second** (22, 72, 73, 136). **Not measured**:
|
||||
that call itself (it needs elevation), and whether it is processor time or waiting. Not changed; the period no
|
||||
longer depends on it. The owner's to say whether it is worth timing on their PC and moving off the poll's thread.
|
||||
- **No test runs the whole path through the real Agent**: the injected tests stop at the shared memory and the
|
||||
sampler's start from it; no end-to-end case loads the stand-in module under an Agent session.
|
||||
- **Two install batches of beta.46 took 0.61 s and 1.26 s and nothing explains them** (Hogwarts Legacy, Cyberpunk
|
||||
2077). Since this release the log says whether a batch went singly; the next long one can be read.
|
||||
- **The Japanese strings are new and unreviewed**, as every `ja` string is.
|
||||
- **Off means off has never been exercised on a real game** (item 43 (f), item 44 (g), now item 45 (g)); nor (c)
|
||||
and (h) of item 43, which only the owner sees.
|
||||
- **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:** what is left of item 45 (Reflex off in a game's menu; off means off; how it felt); one session
|
||||
each of Valor Mortis and Black Myth: Wukong with hooking off; what item 41 left unexercised;
|
||||
item 40 (d).
|
||||
+1
-1
@@ -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.47`** (2026-11-14), an unsigned installer built from that tag with its
|
||||
> **beta is `0.1.0-beta.48`** (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
@@ -125,7 +125,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.47`** (2026-11-14), an unsigned installer built from that tag with its
|
||||
> **beta is `0.1.0-beta.48`** (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
|
||||
|
||||
Reference in new issue
Block a user