Compare commits
1
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
ca05d33641 |
No files matched your search
+1
-68
@@ -35,80 +35,13 @@ numeric core and does not move; the heading is the full version — corrected 20
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
|
||||
- **Filters on Games and Compare** (owner request 2026-11-06, decision D85). Games: store, engine, state, installed and
|
||||
played, beside the search and sort, with *Clear filters*; the title counts what is shown of all. Compare: game, tier
|
||||
and frame generation over every session (it listed the newest 200), with a count; a ticked session stays listed.
|
||||
|
||||
### Changed
|
||||
|
||||
- **The list of games FrameLedger has been run with is current again** (`docs/LIST_GAME_TESTED.md`, decision D35's
|
||||
method): refreshed from a copy of the owner's database taken 2026-11-06 and reviewed by the owner — fifteen more
|
||||
games measured hooked, among them Phantom Blade Zero under the NVIDIA App's *Dynamic* mode, Hogwarts Legacy loading
|
||||
DLSS 5's runtime and the first two Xbox app games — and the sessions recorded without measurement or refused by the
|
||||
guard since 2026-09-27. The guide's Settings page says a language change stays on Settings; the closed §S30 notes the
|
||||
fifth Streamline id decoded (`docs/open-questions/closed-s.md`).
|
||||
- **The Compare page's layout** (the owner's screenshot): the selection bar beside the list instead of a window's width
|
||||
away, with *Clear selection*; columns sized to what they hold — *Tier* and *FPS* touched, and wide gaps split the rest —;
|
||||
the date sorts by when; the settings-changed column says so in words or shows a dash (it was blank); the result
|
||||
table's session labels sit over their columns.
|
||||
- **The selected page keeps its name in the left pane** (D86): WPF UI's pane animates the selected item's label away
|
||||
(Compare's, in the screenshot — every page's while selected); FrameLedger uses a copy of its template without that.
|
||||
- **Games opens at once from any page** (owner request 2026-11-06: switching to Games stalled 0.5–1.5 s). The window
|
||||
keeps the library page it built and shows it again on every later visit, reading the library again behind it; the
|
||||
library is read off the UI thread; the cards appear before the executables are checked — a USB drive that sleeps
|
||||
took a second or more to answer, and no card was shown until every one had — and each card gets its *Not installed*
|
||||
pill when its check answers; a read keeps every card that would look the same instead of rebuilding them all; the
|
||||
list view builds only the rows on screen (`spike-notes` §27).
|
||||
- **Changing the language keeps the page you are on** — Settings, after a change made there. The App remembered only
|
||||
the pages it opened from code, so the language changed on Settings came back on the last game page opened
|
||||
(`src/FrameLedger.App/Services/ShellHost.cs`).
|
||||
- **DLSS 5 is named where the game ran it** (owner decision D84, amending D64). The owner's Hogwarts Legacy, Neural
|
||||
Rendering on, loaded DLSS 5's runtime (`nvngx_dlssnr.dll` 310.9.16.0, from the game's folder) and the session could say
|
||||
only *DLSS 5 runtime loaded* — nothing measured whether it ran. The Overlay's Streamline hook now decodes DLSS 5's
|
||||
feature (`kFeatureDLSS_NR`, Streamline 2.14) into its own per-frame fact, and the Agent keeps the share of the frames
|
||||
the game rendered through Streamline that carried it (`sessions.dlss_nr_pct`, **schema 0022** — a ledger this build
|
||||
migrated no longer opens in an earlier one). Seen running, the DLSS line reads *DLSS 5 (neural rendering on 97.3% of
|
||||
rendered frames)*, above every other generation; loaded and seen not running, *DLSS 5 runtime loaded, not seen
|
||||
running*; where nothing could tell (an earlier Overlay, a title outside Streamline), *DLSS 5 runtime loaded*, as
|
||||
before. Its library is listed with its version and source like the others, its Streamline plugin `sl.dlss_nr.dll`
|
||||
is recorded when loaded, and a game shipping either file shows *Supports DLSS 5 Neural Rendering* (rules
|
||||
`2026.11.2`, capability `dlss_nr`). The **Privacy Policy 2.14** names neural-rendering libraries among those whose
|
||||
versions are read; the **Disclaimer 2.13**'s accuracy block says when DLSS 5 is named. One hook-path change: one more
|
||||
compare in the `slEvaluateFeature` detour and one more test where a present is recorded (`spike-notes` §26).
|
||||
- **Streamline's headers are `v2.14.16`'s** (developers): the vendored copy was `v2.12.0`, byte for byte; three of its
|
||||
eleven files change — `kFeatureDLSS_NR`, the uplift buffer types 70–72, `kStructVersion7`, the version — and
|
||||
nothing FrameLedger consumed otherwise (`src/native/third_party/streamline/README.md`).
|
||||
- **A session under the NVIDIA App's *Dynamic* frame generation reads DLSS 4.5** (owner decision D83, amending D64).
|
||||
Dynamic and its ×6 mode exist only in DLSS 4.5, and the DLSS line named a generation from the measured multiplier
|
||||
alone: the owner's Phantom Blade Zero under *Dynamic, up to ×3* held ×2.0 and ×3.0 and read *DLSS 4 (a ×3.0
|
||||
frame-generation state)*. It reads *DLSS 4.5 (Dynamic multi frame generation, set in the NVIDIA App)* where the game's
|
||||
driver profile sets Dynamic, the driver reports its frame-generation override applied in the game's process, and DLSS
|
||||
Frame Generation was counted; a state measured at ×5 or more still ranks first, and a *Fixed* multiplier names nothing
|
||||
by itself (The Witcher 3 under Fixed ×6 still presented ×2.0). The game page's chip and the CSV's `# dlss:` line
|
||||
(`basis=dynamic_frame_generation`) follow; the **Disclaimer 2.13** says so in its accuracy block
|
||||
(`src/FrameLedger.Domain/Detection/DlssGeneration.cs`, `src/FrameLedger.App/Services/DlssText.cs`; `spike-notes` §26).
|
||||
- **The guard's source reads in order again** (developers only; no behaviour changes): the note that says what runs only
|
||||
for a target the anti-cheat evaluation allowed sits above the function it describes again — beta.33's two isolation
|
||||
checks had come between them — and names that isolation check among what runs
|
||||
(`src/native/FrameLedger.Injector/src/fl_guard.cpp`).
|
||||
|
||||
### Fixed
|
||||
|
||||
- **An Xbox game's page no longer fails on a strange picture name** in the game's own `MicrosoftGame.config` (beta.33's):
|
||||
a name that points at a stream of a file (`a:b.png`) made the search for its scaled variants throw — the page then
|
||||
showed no picture and logged an error, and an action on the page that reloads it could end in the crash report. Such a
|
||||
name is no picture a package ships, so it is passed over like a name outside the package
|
||||
(`src/FrameLedger.Infrastructure/Art/XboxArtCache.cs`). Found by a self-review of #351 and #352 after their gates
|
||||
passed; no install of the owner's eleven titles has such a name.
|
||||
|
||||
## Releases
|
||||
|
||||
Newest first. Each file holds that release's section exactly as it stood here.
|
||||
|
||||
| Version | Date | Notes |
|
||||
|---|---|---|
|
||||
| `0.1.0-beta.34` | 2026-11-06 | [`docs/changelog/0.1.0-beta.34.md`](docs/changelog/0.1.0-beta.34.md) |
|
||||
| `0.1.0-alpha.2` | 2026-11-03 | [`docs/changelog/0.1.0-alpha.2.md`](docs/changelog/0.1.0-alpha.2.md) |
|
||||
| `0.1.0-beta.33` | 2026-11-03 | [`docs/changelog/0.1.0-beta.33.md`](docs/changelog/0.1.0-beta.33.md) |
|
||||
| `0.1.0-alpha.1` | 2026-10-31 | [`docs/changelog/0.1.0-alpha.1.md`](docs/changelog/0.1.0-alpha.1.md) |
|
||||
|
||||
+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.33.*
|
||||
*Beta software: this page describes version 0.1.0-beta.34.*
|
||||
|
||||
## Games it will not measure
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ pages.
|
||||
|
||||
<!-- accuracy-block:begin -->
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-11-06.** The software is a beta; its latest
|
||||
> **beta is `0.1.0-beta.33`** (2026-11-03), an unsigned installer built from that tag with its
|
||||
> **beta is `0.1.0-beta.34`** (2026-11-06), an unsigned installer built from that tag with its
|
||||
> checksums published beside it (alphas — experimental builds on a prerelease .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
|
||||
@@ -176,7 +176,7 @@ Elevation is **optional — for everything.** Hooked capture is the normal path
|
||||
|
||||
## Install
|
||||
|
||||
> **The latest beta is `v0.1.0-beta.33` (2026-11-03); before it `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.34` (2026-11-06); before it `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**.
|
||||
|
||||
@@ -482,7 +482,7 @@ never the path), and the super-resolution preset the driver reports applied:
|
||||
|---|---|---|
|
||||
| Super-resolution render preset **L or M** that the NVIDIA driver reports applied, in a session where super resolution ran | DLSS 4.5 (2nd-gen transformer) | `ngx_driver_words` — the SR word's `PRESET` bit and `renderPreset`; presets L/M arrived with DLL 310.5.0 (NVIDIA's DLSS 4.5 release, driver 591.74) |
|
||||
| A DLSS Frame Generation state measured at **×5 or more** | DLSS 4.5 (Dynamic / 6× multi-frame generation) | `fg_mix` / `fg_factor` with `fg_mode = dlssg` |
|
||||
| The NVIDIA App's **Dynamic** frame generation — set in the game's profile and reported applied by the driver — in a session where DLSS Frame Generation was counted *(beta.34, owner decision D83)* | DLSS 4.5 (Dynamic multi frame generation, set in the NVIDIA App) | `driver_profile`'s `NGX_DLSSG_MODE` = 4 (dynamic), `ngx_driver_words`' FG word with `FG_MODE` (bit 13), `fg_mode = dlssg` |
|
||||
| The NVIDIA App's **Dynamic** frame generation — set in the game's profile and reported applied by the driver — in a session where DLSS Frame Generation was identified *(beta.34, owner decision D83)* | DLSS 4.5 (Dynamic multi frame generation, set in the NVIDIA App) | `driver_profile`'s `NGX_DLSSG_MODE` = 4 (dynamic), `ngx_driver_words`' FG word with `FG_MODE` (bit 13), `fg_mode = dlssg` |
|
||||
| Preset **J or K** reported applied | DLSS 4 (transformer) | as above |
|
||||
| A DLSS Frame Generation state at **×3 or ×4** | DLSS 4 (multi-frame generation) | as above |
|
||||
| `nvngx_dlss.dll` **2.x** | DLSS 2 | `runtime_modules` |
|
||||
@@ -497,7 +497,8 @@ generation and its ×6 mode exist only in DLSS 4.5, so a session the driver repo
|
||||
multiplier the mode chose: the owner's Phantom Blade Zero under *Dynamic, up to ×3* held ×2.0 and ×3.0 — nine hooked sessions
|
||||
from 2026-11-03 to 11-05 — and read *DLSS 4 (a ×3.0 frame-generation state)* until then. The row needs all three: the
|
||||
profile's Dynamic (`NGX_DLSSG_MODE` = 4, NVIDIA's own name for the value), the driver's report that its frame-generation
|
||||
override applied in the game's process (the FG word's `FG_MODE` bit), and DLSS Frame Generation counted in the session —
|
||||
override applied in the game's process (the FG word's `FG_MODE` bit), and DLSS Frame Generation identified in the session
|
||||
(`fg_mode = dlssg`; its factor need not have been counted) —
|
||||
a profile set to Dynamic that the driver never applied is a setting, not evidence. The driver's own mode number is not
|
||||
read: it answers 3 under Dynamic and 1 under *Fixed* on every stored session (`spike-notes` §26), and NVIDIA's header
|
||||
names neither. A *Fixed* ×5 or ×6 is not this row — Witcher 3 under the App's Fixed ×6 still presented ×2.0 — and
|
||||
|
||||
+71
-69
@@ -72,6 +72,7 @@ owner-only items stay below; the history of every train, the passed owner-only i
|
||||
| `§beta.30` | [`handoff/history/0.1.0-beta.30.md`](handoff/history/0.1.0-beta.30.md) |
|
||||
| `§beta.31` | [`handoff/history/0.1.0-beta.31.md`](handoff/history/0.1.0-beta.31.md) |
|
||||
| `§beta.32` | [`handoff/history/0.1.0-beta.32.md`](handoff/history/0.1.0-beta.32.md) |
|
||||
| `§beta.33` | [`handoff/history/0.1.0-beta.33.md`](handoff/history/0.1.0-beta.33.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) | [`handoff/owner-only-passed.md`](handoff/owner-only-passed.md) |
|
||||
| `§Traps`, `§Two corrections carried forward` | [`handoff/traps.md`](handoff/traps.md) |
|
||||
@@ -79,87 +80,73 @@ owner-only items stay below; the history of every train, the passed owner-only i
|
||||
|
||||
---
|
||||
|
||||
## **START HERE** — 2026-11-03, 0.1.0-beta.33: games from the Xbox app and the Microsoft Store
|
||||
## **START HERE** — 2026-11-06, 0.1.0-beta.34: DLSS 5 and DLSS 4.5 from what the game and the driver did; filters; Games at once
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.33.md`; this is what no other file carries.* The owner: "Trong phiên này, ta sẽ tập
|
||||
trung xử lý, đánh giá, phân tích cho các game thuộc MS Store/ Xbox App/Game Pass cho (các) phiên bản tiếp theo nhé. Quy
|
||||
trình vẫn như mọi lần." — handle, evaluate and analyse the games of the Microsoft Store, the Xbox app and Game Pass for the
|
||||
next versions, the usual train; the owner's games are in `C:\XboxGames` and `D:\xbox`. #351 (the library, the install
|
||||
root, detection, the art, Privacy 2.13), #352 (Play, the guard's two refusals, one exe-path reader) and this release;
|
||||
`0.1.0-alpha.2` follows (D82).
|
||||
*Status is `docs/changelog/0.1.0-beta.34.md`; this is what no other file carries.* The owner asked for seven things, the
|
||||
usual train: (1) how DLSS 5 Neural Rendering is detected on Hogwarts Legacy (Neural Rendering on in the game), and its
|
||||
version; (2) under the NVIDIA App's *Dynamic* multi frame generation the label read DLSS 4, though Dynamic and ×6 exist
|
||||
only in DLSS 4.5 (Phantom Blade Zero); (3) filters on Games and Compare; (4) the Compare page's layout, from a
|
||||
screenshot; (5) the documents and the tested-games list, from the database; (6) switching to Games stalled 0.5–1.5 s;
|
||||
(7) a language change landed on the last content page instead of Settings. And while planning: "Bạn check Streamline các
|
||||
bản gần đây có gì thay đổi và sửa luôn nếu thật sự cần nhé." — check what changed in recent Streamline versions and fix it
|
||||
if really needed. #356 (two fixes from a self-review of #351 and #352), #357 (D83), #358 (D84, Streamline `v2.14.16`),
|
||||
#359 (items 6 and 7), #360 (items 3 and 4, D85, D86), #361 (item 5) and this release; `0.1.0-alpha.3` follows (D87) —
|
||||
the owner's screenshot is of an alpha, so the alpha is how these reach the owner's PC.
|
||||
|
||||
**Decisions (asked while planning, do not re-ask):**
|
||||
|
||||
- **D77 — measure first, on the owner's titles**: the launch chain was measured by activating six of the eleven packages
|
||||
with no FrameLedger hook, read-only, each game closed by its window and never killed, with the decision table committed
|
||||
before the run (`spike-notes` §25, its two commits in #351).
|
||||
- **D78 — GDK only**: an app-container (UWP) process is refused with a reason of its own, `TargetAppContainer`, Tier 2
|
||||
(`19_SAFETY` §The target must be able to take the Overlay); `LIMITATIONS.md` says so.
|
||||
- **D79 — the platform is "Xbox"** (id `xbox`), full scope: import, art, Play, Tier-1 capture, detection, docs and legal.
|
||||
- **D80 — Play on an Xbox game always activates its package**, in both D59 modes (`08_UI` §Games): started by its path a
|
||||
GDK game is never the game in its package — the run corrected the plan's premise that `CreateProcess` fails with error 5
|
||||
(it hands the launch executable back to the package, so the game is not the launcher's descendant; an Unreal shipping
|
||||
executable runs outside it). The Agent records such a game in attach mode.
|
||||
- **D81 — title lists stay keyed by Steam id**: an Xbox copy is matched by everything but that entry; the gap is
|
||||
`20_OPEN_QUESTIONS` §G *Xbox app / Microsoft Store titles*.
|
||||
- **D82 — alpha.2 right after beta.33** (the owner runs `0.1.0-alpha.1`, and the alpha's channel is locked): on RC3; if
|
||||
the train reaches the alpha after .NET 11's release on 2026-11-10, the standing rule applies (SDK 11.0.100, packages
|
||||
11.0.0) — no new decision.
|
||||
- **D83 — Dynamic frame generation is DLSS 4.5's**: the owner's rule, "Dynamic and ×6 exist only in DLSS 4.5". The
|
||||
evidence is the game's driver profile setting Dynamic (`NGX_DLSSG_MODE` = 4) **and** the driver reporting its
|
||||
frame-generation override applied in the game's process (`FG_MODE` in its FG word), in a session where DLSS
|
||||
Frame Generation was identified (`fg_mode = dlssg`; its factor need not have been counted); a state measured at ×5 or more still ranks first, and a *Fixed* multiplier names nothing by itself
|
||||
(amends D64). The driver's `frameGenerationMode` — 3 under Dynamic and 1 under Fixed in every session read, and unnamed
|
||||
by NVIDIA — is recorded in `spike-notes` §26, not keyed on.
|
||||
- **D84 — DLSS 5 is the session's generation where its neural rendering was measured running**: the Overlay decodes
|
||||
`kFeatureDLSS_NR` in its `slEvaluateFeature` detour and the Agent keeps its share of the Streamline batches
|
||||
(`sessions.dlss_nr_pct`, schema 0022) — *DLSS 5 (neural rendering on N % of rendered frames)*; loaded and seen not
|
||||
running, *runtime loaded, not seen running*; where nothing could tell, *runtime loaded*, as before (amends D64).
|
||||
- **D85 — the filters**: Games — store, engine, state, installed, played; Compare — game, tier, frame generation, no
|
||||
period; Compare lists every session (it listed the newest 200).
|
||||
- **D86 — the left pane's selected item keeps its label**: our copy of WPF UI 4.3.0's LeftFluent item template, whose
|
||||
`IsActive` trigger animated it away.
|
||||
- **D87 — alpha.3 right after beta.34**, on RC3: the train reaches it before .NET 11's release on 2026-11-10.
|
||||
|
||||
The Privacy Policy 2.13's wording was approved with the plan (D36).
|
||||
Streamline was re-vendored at `v2.14.16` on the owner's instruction above, not as a decision of its own. The wording of
|
||||
the Disclaimer 2.13 and the Privacy Policy 2.14, and the tested-games list (D35), were approved with the plan (D36).
|
||||
|
||||
**Choices made here:**
|
||||
|
||||
- **A GDK package root is an install-root boundary**, for the guard's check 4 and for detection alike, and only where no
|
||||
store boundary matched — so it can only widen what is walked (`19_SAFETY` §Pre-injection checks, amended 2026-11-03).
|
||||
The guard gained `GamesInstalled\<X>` with it, and one case list read by both test suites
|
||||
(`tests/fixtures/install-roots/cases.txt`) holds the two resolvers together.
|
||||
- **`root_file`, a new detection signal**, answered from the install root's own listing, so the `xbox` platform rule —
|
||||
first, because a GDK FINAL FANTASY ships Steam's DLL — is decidable even where a very large install's walk ran short.
|
||||
- **The two refusals read the target once, before the primitive**, never at the 30 s re-scan; "could not tell" refuses as
|
||||
`ProcessUnreadable`, and only enforcing flags count (`SetContextIpValidation` without strict mode is on every
|
||||
CET-compatible process: `pwsh.exe` reads `0x105`).
|
||||
- **`TargetResolver` reads the watcher's spelling** (`ProcessImagePath`) but keeps the guard's rights, so D21's
|
||||
`TargetUnreadable` is unchanged.
|
||||
- **Neural rendering's share is over the Streamline batches**, not every present: a generated frame evaluates nothing,
|
||||
and a title that never drains a batch reads *nothing could tell* (null), never 0 %.
|
||||
- **A writer older than beta.34 is told apart by its family bit**, `FL_HOOK_SL_NEURAL_RENDERING` (bit 12), published with
|
||||
the detour — an old Overlay's silence leaves `dlss_nr_pct` null instead of a measured 0 %; no layout change.
|
||||
- **The Games page is the window's**, kept by our own page provider (`WindowPageCache`), not `NavigationCacheMode`: WPF UI
|
||||
4.3.0 reads that only when neither a service provider nor a page provider is set, and `SetNavigationControl` sets one
|
||||
(`16_WPFUI_SYNTAX` §Navigation). One per window, so a language change's window builds its own.
|
||||
- **The cards come before the executable checks** — 39 of the owner's 41 Steam games are on a USB drive that sleeps — and
|
||||
each card gets its *Not installed* pill when its check answers.
|
||||
- **The pane's item template is a copy changed in one place**, reading WPF UI's own `NavigationViewConstants.xaml`: before
|
||||
the WPF UI pin moves, the upstream template is read again.
|
||||
|
||||
**Measured on the way** (`spike-notes` §25): eleven GDK packages, full trust, the user's token, medium integrity, none of
|
||||
the four mitigations; the image path and the loader's main module both in the `Content` spelling; every game `.exe`
|
||||
refuses `FILE_READ_DATA`/`FILE_EXECUTE` outside its package, so no Unreal version and no *Runs as* for these titles;
|
||||
`GetProcessMitigationPolicy` answers through `PROCESS_QUERY_LIMITED_INFORMATION`, and an unknown policy answers
|
||||
`ERROR_INVALID_PARAMETER`.
|
||||
**Measured on the way:** the owner's DLSS sessions of 2026-11-01 → 11-06, the driver's frame-generation numbering and
|
||||
Streamline's `v2.12.0` → `v2.14.16` changes are `spike-notes` §26 (the ledger read read-only; the vendored copy was
|
||||
`v2.12.0` byte for byte); the Games page before and after is §27 (first cards 822–830 ms → 10–15 ms with the first
|
||||
executable check held 800 ms; a revisit 181–215 ms → 15–16 ms). The neural-rendering decode costs nothing measurable in
|
||||
the detour and 0.14–0.19 ns on the present's feature byte (#358's body; NFR-1's budget is 1 µs per present).
|
||||
|
||||
**Traps met on the way:**
|
||||
|
||||
- **Malwarebytes quarantines `fl_guard_test.exe`** (`Malware.Heuristic.108256`, records in
|
||||
`C:\ProgramData\Malwarebytes\MBAMService\RtpDetections`) on some builds and not others: ctest then reports `fl_guard` as
|
||||
passed in 0.5 s with no output and `fl_prescan` with an empty command. Read `LastTest.log` for the assertion count before
|
||||
believing a native pass; an exclusion for `E:\frameledger\build\` is the owner's to add (a security setting), and CI runs
|
||||
both suites.
|
||||
- **`build.ps1` finds the x64 clang-format; `Get-ChildItem … clang-format.exe` finds the ARM64 one first**, which will not
|
||||
start on this PC.
|
||||
- **SonarCloud's quality gate on #351 was 77.7 % new-code coverage** (≥ 80 % wanted) and one `cpp:S5813` (`wcslen`): both
|
||||
closed in #352 — its own gate 95.4 %, main's after the merge 86.5 % on the code since beta.32 with no open issue. The
|
||||
job is advisory, so a merge on green does not wait for it — read its verdict after each merge.
|
||||
- **FluentAssertions' `OnlyContain` fails an empty collection**: a test of what this PC holds (`GamingRoots.OnThisPc()`)
|
||||
passed here and failed on the hosted runner, which has no `.GamingRoot` (#352's first CI run) — assert that nothing
|
||||
is wrong rather than that everything is right.
|
||||
- **`notice-check` reads the tracked tree**: a file deleted from the working tree but not from the index fails it with
|
||||
*Could not find file* — after every build and test had passed (#360's first local gate). Stage the change
|
||||
(`git add -A`) before the gate.
|
||||
- **A new hook family bit belongs in the native token test's exact mask** (`guard_test.cpp`), and a new Streamline fact
|
||||
in the 0xF00D case's list of facts it must not light — #358's first gate (`0x100f` against `15`).
|
||||
- **WPF UI 4.3.0**: `NavigationCacheMode` is ignored once a page provider is set; `INavigationService.SetNavigationControl`
|
||||
hands the NavigationView the container's provider, so ours is set after it; LeftFluent's item template collapses the
|
||||
selected item's label.
|
||||
- **Microsoft.Data.Sqlite's async methods run synchronously**: a read awaited on the UI thread blocks it — `Task.Run` it.
|
||||
|
||||
**Owner-only:** item 28 — the Xbox titles on real hardware.
|
||||
|
||||
### 0.1.0-alpha.2 — the second alpha, the same day (D82)
|
||||
|
||||
`alpha` took main at this pull request — `v0.1.0-beta.33` and these notes, no other change — by a merge commit, as
|
||||
`13_CI_CD` §The alpha line says: no file the switch holds had moved on main, so nothing conflicted and the switch is the
|
||||
first alpha's (SDK `11.0.100-rc.3.26522.148`, the three packages at `11.0.0-rc.3.26522.148`, the same NuGet licence
|
||||
texts). Its gate on the 11 SDK must pass before the pull request into `alpha` is merged by hand (the branch has no
|
||||
auto-merge); the release runs from the signed tag `v0.1.0-alpha.2` on `alpha`, and its delta from alpha.1 is the first
|
||||
an alpha's release has to find — #350's lookup, by the name the pack lists. Its notes are
|
||||
`docs/changelog/0.1.0-alpha.2.md`, which open with the experimental-build warning.
|
||||
|
||||
- **The next alpha moves to .NET 11's release**: from 2026-11-10 the switch is SDK `11.0.100` and the packages `11.0.0`,
|
||||
and RC3 is out of support — move the alpha even if no beta comes.
|
||||
|
||||
**Owner-only:** item 29 — the second alpha on real hardware.
|
||||
**Owner-only:** item 30 — beta.34 on real hardware.
|
||||
|
||||
|
||||
## Owner-only — no PR can close these
|
||||
@@ -371,6 +358,20 @@ an alpha's release has to find — #350's lookup, by the name the pack lists. It
|
||||
with its box again, and Accept waits for the tick. (c)
|
||||
`%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.2.db` exists beside alpha.1's, and opens. (d) Item 28's
|
||||
Xbox checks, on the alpha.
|
||||
30. **beta.34 on real hardware** (D83–D86). (a) **The update from beta.33** (or alpha.3's, item 31): the terms window
|
||||
shows the Disclaimer 2.13 and the Privacy Policy 2.14 once. (b) **Hogwarts Legacy with Neural Rendering on**, one
|
||||
hooked session → *DLSS 5 (neural rendering on N % of rendered frames)*; then **off** — `spike-notes` §26's table,
|
||||
written before the run, decides (on and 0 %: neural rendering runs outside `slEvaluateFeature`, the line stays
|
||||
*runtime loaded, not seen running*, and the session's `sl_tag_census` is recorded before anything is named).
|
||||
(c) **Phantom Blade Zero** under the NVIDIA App's *Dynamic, up to ×3* → *DLSS 4.5 (Dynamic multi frame generation, set
|
||||
in the NVIDIA App)*; the game's own ×3 with no override from the App → *DLSS 4*. (d) **Games** from any page: the
|
||||
cards at once, a second visit at once; the Debug line `ui: page … shown … ms after its navigation`. (e) **Settings →
|
||||
change the language** → the window comes back on Settings. (f) The filters on Games and Compare, the Compare columns
|
||||
and selection bar, the selected page's label in the pane, in both themes. (g) The 34 `ja` strings this release adds,
|
||||
all marked `review`: `Dlss_Basis_Dynamic`, `Dlss_NeuralRendering_NotSeen`, `Dlss_Feature_NeuralRendering`,
|
||||
`Dlss_Basis_NeuralRendering_Format`, `Games_Filter_*`, `Games_Header_Filtered_Format`, `Filter_Clear`,
|
||||
`Compare_Filter_*`, `Compare_Count_Format`, `Compare_Count_Filtered_Format`, `Compare_ClearSelection`,
|
||||
`Compare_MidSession_Changed`, `A11y_Games_Filter_*`, `A11y_Compare_Filter_*`.
|
||||
**Answered 2026-08-05, do not re-ask:** remove `gameguard` and keep `guard` (approved
|
||||
over a red `Rules` gate, with the reasoning recorded in the merge commit); vendor NVAPI
|
||||
headers **and** `amd64/nvapi64.lib`; Windows 11 is the **measurement scope** only —
|
||||
@@ -467,10 +468,11 @@ Where each owner decision is recorded — the file and its section, and a label
|
||||
| D80 | [`08_UI.md`](08_UI.md) §Games | Play on an Xbox game always activates its package, in both modes; the Agent answers `PackagedGame` and records it in attach mode |
|
||||
| D81 | [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) §G | title lists stay keyed by Steam id; an Xbox copy is matched by everything but that entry |
|
||||
| D82 | [`HANDOFF.md`](HANDOFF.md) §START HERE | alpha.2 right after beta.33; on RC3 unless the train reaches it after .NET 11 ships (then SDK 11.0.100, packages 11.0.0) |
|
||||
| D83 | [`05_DETECTION.md`](05_DETECTION.md) §DLSS generation | the NVIDIA App's Dynamic frame generation, reported applied by the driver in a session that counted DLSS Frame Generation, is DLSS 4.5 (amends D64) |
|
||||
| D83 | [`05_DETECTION.md`](05_DETECTION.md) §DLSS generation | the NVIDIA App's Dynamic frame generation, reported applied by the driver in a session where DLSS Frame Generation was identified, is DLSS 4.5 (amends D64) |
|
||||
| D84 | [`05_DETECTION.md`](05_DETECTION.md) §DLSS generation | DLSS 5 heads the DLSS line where its neural rendering was measured running (`kFeatureDLSS_NR`, `dlss_nr_pct`); loaded only reads "runtime loaded" (amends D64) |
|
||||
| D85 | [`08_UI.md`](08_UI.md) §Games, §Compare | filters: Games — store, engine, state, installed, played; Compare — game, tier, frame generation (no period); Compare lists every session |
|
||||
| D86 | [`08_UI.md`](08_UI.md) (the shell) | the left pane's selected item keeps its label: our copy of WPF UI 4.3.0's LeftFluent item template |
|
||||
| D87 | [`HANDOFF.md`](HANDOFF.md) §START HERE | alpha.3 right after beta.34, on RC3 (before .NET 11's release, 2026-11-10) |
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1,81 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.34 was cut, 2026-11-06 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.34] - 2026-11-06
|
||||
|
||||
**The thirty-fourth pre-release: DLSS 5 and DLSS 4.5 named from what the game and the driver did, filters on Games
|
||||
and Compare, and a Games page that opens at once.** The same unsigned installer: verify its hash against
|
||||
`SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**Updating from `0.1.0-beta.33`:** Help ▸ Check for updates, then *Restart to update* with no game running. The
|
||||
Disclaimer (2.13) and the Privacy Policy (2.14) are shown once for you to accept; the EULA does not change. The ledger
|
||||
moves to schema 22, which a beta.33 cannot open. The detection rules move to `2026.11.2`, so every game in the
|
||||
library is read again once. DLSS 4.5 under the NVIDIA App's *Dynamic* frame generation reads on sessions you already
|
||||
have; whether DLSS 5's neural rendering ran is kept for sessions recorded from now on.
|
||||
|
||||
### Added
|
||||
|
||||
- **Filters on Games and Compare** (owner request 2026-11-06, decision D85). Games: store, engine, state, installed and
|
||||
played, beside the search and sort, with *Clear filters*; the title counts what is shown of all. Compare: game, tier
|
||||
and frame generation over every session (it listed the newest 200), with a count; a ticked session stays listed.
|
||||
|
||||
### Changed
|
||||
|
||||
- **The list of games FrameLedger has been run with is current again** (`docs/LIST_GAME_TESTED.md`, decision D35's
|
||||
method): refreshed from a copy of the owner's database taken 2026-11-06 and reviewed by the owner — fifteen more
|
||||
games measured hooked, among them Phantom Blade Zero under the NVIDIA App's *Dynamic* mode, Hogwarts Legacy loading
|
||||
DLSS 5's runtime and the first two Xbox app games — and the sessions recorded without measurement or refused by the
|
||||
guard since 2026-09-27. The guide's Settings page says a language change stays on Settings; the closed §S30 notes the
|
||||
fifth Streamline id decoded (`docs/open-questions/closed-s.md`).
|
||||
- **The Compare page's layout** (the owner's screenshot): the selection bar beside the list instead of a window's width
|
||||
away, with *Clear selection*; columns sized to what they hold — *Tier* and *FPS* touched, and wide gaps split the rest —;
|
||||
the date sorts by when; the settings-changed column says so in words or shows a dash (it was blank); the result
|
||||
table's session labels sit over their columns.
|
||||
- **The selected page keeps its name in the left pane** (D86): WPF UI's pane animates the selected item's label away
|
||||
(Compare's, in the screenshot — every page's while selected); FrameLedger uses a copy of its template without that.
|
||||
- **Games opens at once from any page** (owner request 2026-11-06: switching to Games stalled 0.5–1.5 s). The window
|
||||
keeps the library page it built and shows it again on every later visit, reading the library again behind it; the
|
||||
library is read off the UI thread; the cards appear before the executables are checked — a USB drive that sleeps
|
||||
took a second or more to answer, and no card was shown until every one had — and each card gets its *Not installed*
|
||||
pill when its check answers; a read keeps every card that would look the same instead of rebuilding them all; the
|
||||
list view builds only the rows on screen (`spike-notes` §27).
|
||||
- **Changing the language keeps the page you are on** — Settings, after a change made there. The App remembered only
|
||||
the pages it opened from code, so the language changed on Settings came back on the last game page opened
|
||||
(`src/FrameLedger.App/Services/ShellHost.cs`).
|
||||
- **DLSS 5 is named where the game ran it** (owner decision D84, amending D64). The owner's Hogwarts Legacy, Neural
|
||||
Rendering on, loaded DLSS 5's runtime (`nvngx_dlssnr.dll` 310.9.16.0, from the game's folder) and the session could say
|
||||
only *DLSS 5 runtime loaded* — nothing measured whether it ran. The Overlay's Streamline hook now decodes DLSS 5's
|
||||
feature (`kFeatureDLSS_NR`, Streamline 2.14) into its own per-frame fact, and the Agent keeps the share of the frames
|
||||
the game rendered through Streamline that carried it (`sessions.dlss_nr_pct`, **schema 0022** — a ledger this build
|
||||
migrated no longer opens in an earlier one). Seen running, the DLSS line reads *DLSS 5 (neural rendering on 97.3% of
|
||||
rendered frames)*, above every other generation; loaded and seen not running, *DLSS 5 runtime loaded, not seen
|
||||
running*; where nothing could tell (an earlier Overlay, a title outside Streamline), *DLSS 5 runtime loaded*, as
|
||||
before. Its library is listed with its version and source like the others, its Streamline plugin `sl.dlss_nr.dll`
|
||||
is recorded when loaded, and a game shipping either file shows *Supports DLSS 5 Neural Rendering* (rules
|
||||
`2026.11.2`, capability `dlss_nr`). The **Privacy Policy 2.14** names neural-rendering libraries among those whose
|
||||
versions are read; the **Disclaimer 2.13**'s accuracy block says when DLSS 5 is named. One hook-path change: one more
|
||||
compare in the `slEvaluateFeature` detour and one more test where a present is recorded (`spike-notes` §26).
|
||||
- **Streamline's headers are `v2.14.16`'s** (developers): the vendored copy was `v2.12.0`, byte for byte; three of its
|
||||
eleven files change — `kFeatureDLSS_NR`, the uplift buffer types 70–72, `kStructVersion7`, the version — and
|
||||
nothing FrameLedger consumed otherwise (`src/native/third_party/streamline/README.md`).
|
||||
- **A session under the NVIDIA App's *Dynamic* frame generation reads DLSS 4.5** (owner decision D83, amending D64).
|
||||
Dynamic and its ×6 mode exist only in DLSS 4.5, and the DLSS line named a generation from the measured multiplier
|
||||
alone: the owner's Phantom Blade Zero under *Dynamic, up to ×3* held ×2.0 and ×3.0 and read *DLSS 4 (a ×3.0
|
||||
frame-generation state)*. It reads *DLSS 4.5 (Dynamic multi frame generation, set in the NVIDIA App)* where the game's
|
||||
driver profile sets Dynamic, the driver reports its frame-generation override applied in the game's process, and DLSS
|
||||
Frame Generation was identified (whether or not its factor was counted); a state measured at ×5 or more still ranks first, and a *Fixed* multiplier names nothing
|
||||
by itself (The Witcher 3 under Fixed ×6 still presented ×2.0). The game page's chip and the CSV's `# dlss:` line
|
||||
(`basis=dynamic_frame_generation`) follow; the **Disclaimer 2.13** says so in its accuracy block
|
||||
(`src/FrameLedger.Domain/Detection/DlssGeneration.cs`, `src/FrameLedger.App/Services/DlssText.cs`; `spike-notes` §26).
|
||||
- **The guard's source reads in order again** (developers only; no behaviour changes): the note that says what runs only
|
||||
for a target the anti-cheat evaluation allowed sits above the function it describes again — beta.33's two isolation
|
||||
checks had come between them — and names that isolation check among what runs
|
||||
(`src/native/FrameLedger.Injector/src/fl_guard.cpp`).
|
||||
|
||||
### Fixed
|
||||
|
||||
- **An Xbox game's page no longer fails on a strange picture name** in the game's own `MicrosoftGame.config` (beta.33's):
|
||||
a name that points at a stream of a file (`a:b.png`) made the search for its scaled variants throw — the page then
|
||||
showed no picture and logged an error, and an action on the page that reloads it could end in the crash report. Such a
|
||||
name is no picture a package ships, so it is passed over like a name outside the package
|
||||
(`src/FrameLedger.Infrastructure/Art/XboxArtCache.cs`). Found by a self-review of #351 and #352 after their gates
|
||||
passed; no install of the owner's eleven titles has such a name.
|
||||
@@ -0,0 +1,85 @@
|
||||
# HANDOFF history — 0.1.0-beta.33
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.34 was cut, 2026-11-06 (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.*
|
||||
|
||||
## **START HERE** — 2026-11-03, 0.1.0-beta.33: games from the Xbox app and the Microsoft Store
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.33.md`; this is what no other file carries.* The owner: "Trong phiên này, ta sẽ tập
|
||||
trung xử lý, đánh giá, phân tích cho các game thuộc MS Store/ Xbox App/Game Pass cho (các) phiên bản tiếp theo nhé. Quy
|
||||
trình vẫn như mọi lần." — handle, evaluate and analyse the games of the Microsoft Store, the Xbox app and Game Pass for the
|
||||
next versions, the usual train; the owner's games are in `C:\XboxGames` and `D:\xbox`. #351 (the library, the install
|
||||
root, detection, the art, Privacy 2.13), #352 (Play, the guard's two refusals, one exe-path reader) and this release;
|
||||
`0.1.0-alpha.2` follows (D82).
|
||||
|
||||
**Decisions (asked while planning, do not re-ask):**
|
||||
|
||||
- **D77 — measure first, on the owner's titles**: the launch chain was measured by activating six of the eleven packages
|
||||
with no FrameLedger hook, read-only, each game closed by its window and never killed, with the decision table committed
|
||||
before the run (`spike-notes` §25, its two commits in #351).
|
||||
- **D78 — GDK only**: an app-container (UWP) process is refused with a reason of its own, `TargetAppContainer`, Tier 2
|
||||
(`19_SAFETY` §The target must be able to take the Overlay); `LIMITATIONS.md` says so.
|
||||
- **D79 — the platform is "Xbox"** (id `xbox`), full scope: import, art, Play, Tier-1 capture, detection, docs and legal.
|
||||
- **D80 — Play on an Xbox game always activates its package**, in both D59 modes (`08_UI` §Games): started by its path a
|
||||
GDK game is never the game in its package — the run corrected the plan's premise that `CreateProcess` fails with error 5
|
||||
(it hands the launch executable back to the package, so the game is not the launcher's descendant; an Unreal shipping
|
||||
executable runs outside it). The Agent records such a game in attach mode.
|
||||
- **D81 — title lists stay keyed by Steam id**: an Xbox copy is matched by everything but that entry; the gap is
|
||||
`20_OPEN_QUESTIONS` §G *Xbox app / Microsoft Store titles*.
|
||||
- **D82 — alpha.2 right after beta.33** (the owner runs `0.1.0-alpha.1`, and the alpha's channel is locked): on RC3; if
|
||||
the train reaches the alpha after .NET 11's release on 2026-11-10, the standing rule applies (SDK 11.0.100, packages
|
||||
11.0.0) — no new decision.
|
||||
|
||||
The Privacy Policy 2.13's wording was approved with the plan (D36).
|
||||
|
||||
**Choices made here:**
|
||||
|
||||
- **A GDK package root is an install-root boundary**, for the guard's check 4 and for detection alike, and only where no
|
||||
store boundary matched — so it can only widen what is walked (`19_SAFETY` §Pre-injection checks, amended 2026-11-03).
|
||||
The guard gained `GamesInstalled\<X>` with it, and one case list read by both test suites
|
||||
(`tests/fixtures/install-roots/cases.txt`) holds the two resolvers together.
|
||||
- **`root_file`, a new detection signal**, answered from the install root's own listing, so the `xbox` platform rule —
|
||||
first, because a GDK FINAL FANTASY ships Steam's DLL — is decidable even where a very large install's walk ran short.
|
||||
- **The two refusals read the target once, before the primitive**, never at the 30 s re-scan; "could not tell" refuses as
|
||||
`ProcessUnreadable`, and only enforcing flags count (`SetContextIpValidation` without strict mode is on every
|
||||
CET-compatible process: `pwsh.exe` reads `0x105`).
|
||||
- **`TargetResolver` reads the watcher's spelling** (`ProcessImagePath`) but keeps the guard's rights, so D21's
|
||||
`TargetUnreadable` is unchanged.
|
||||
|
||||
**Measured on the way** (`spike-notes` §25): eleven GDK packages, full trust, the user's token, medium integrity, none of
|
||||
the four mitigations; the image path and the loader's main module both in the `Content` spelling; every game `.exe`
|
||||
refuses `FILE_READ_DATA`/`FILE_EXECUTE` outside its package, so no Unreal version and no *Runs as* for these titles;
|
||||
`GetProcessMitigationPolicy` answers through `PROCESS_QUERY_LIMITED_INFORMATION`, and an unknown policy answers
|
||||
`ERROR_INVALID_PARAMETER`.
|
||||
|
||||
**Traps met on the way:**
|
||||
|
||||
- **Malwarebytes quarantines `fl_guard_test.exe`** (`Malware.Heuristic.108256`, records in
|
||||
`C:\ProgramData\Malwarebytes\MBAMService\RtpDetections`) on some builds and not others: ctest then reports `fl_guard` as
|
||||
passed in 0.5 s with no output and `fl_prescan` with an empty command. Read `LastTest.log` for the assertion count before
|
||||
believing a native pass; an exclusion for `E:\frameledger\build\` is the owner's to add (a security setting), and CI runs
|
||||
both suites.
|
||||
- **`build.ps1` finds the x64 clang-format; `Get-ChildItem … clang-format.exe` finds the ARM64 one first**, which will not
|
||||
start on this PC.
|
||||
- **SonarCloud's quality gate on #351 was 77.7 % new-code coverage** (≥ 80 % wanted) and one `cpp:S5813` (`wcslen`): both
|
||||
closed in #352 — its own gate 95.4 %, main's after the merge 86.5 % on the code since beta.32 with no open issue. The
|
||||
job is advisory, so a merge on green does not wait for it — read its verdict after each merge.
|
||||
- **FluentAssertions' `OnlyContain` fails an empty collection**: a test of what this PC holds (`GamingRoots.OnThisPc()`)
|
||||
passed here and failed on the hosted runner, which has no `.GamingRoot` (#352's first CI run) — assert that nothing
|
||||
is wrong rather than that everything is right.
|
||||
|
||||
**Owner-only:** item 28 — the Xbox titles on real hardware.
|
||||
|
||||
### 0.1.0-alpha.2 — the second alpha, the same day (D82)
|
||||
|
||||
`alpha` took main at this pull request — `v0.1.0-beta.33` and these notes, no other change — by a merge commit, as
|
||||
`13_CI_CD` §The alpha line says: no file the switch holds had moved on main, so nothing conflicted and the switch is the
|
||||
first alpha's (SDK `11.0.100-rc.3.26522.148`, the three packages at `11.0.0-rc.3.26522.148`, the same NuGet licence
|
||||
texts). Its gate on the 11 SDK must pass before the pull request into `alpha` is merged by hand (the branch has no
|
||||
auto-merge); the release runs from the signed tag `v0.1.0-alpha.2` on `alpha`, and its delta from alpha.1 is the first
|
||||
an alpha's release has to find — #350's lookup, by the name the pack lists. Its notes are
|
||||
`docs/changelog/0.1.0-alpha.2.md`, which open with the experimental-build warning.
|
||||
|
||||
- **The next alpha moves to .NET 11's release**: from 2026-11-10 the switch is SDK `11.0.100` and the packages `11.0.0`,
|
||||
and RC3 is out of support — move the alpha even if no beta comes.
|
||||
|
||||
**Owner-only:** item 29 — the second alpha on real hardware.
|
||||
@@ -27,7 +27,8 @@ are `NvAPI_NGX_GetNGXOverrideState`'s, from `ngx_driver_words`. Bits: `0x1F` ini
|
||||
So the driver reports `FG_MODE` applied under both of the App's modes and its own mode number tells them apart — 3 under
|
||||
Dynamic, 1 under Fixed, on all sixteen sessions — but NVIDIA's header names neither number. **What D83 reads is the
|
||||
profile's value, which the header does name (4, `NGX_DLSSG_MODE_DYNAMIC`), with the report's `FG_MODE` bit as proof the
|
||||
driver applied it**, and DLSS Frame Generation counted in the session. The ceiling's decode (frames generated per
|
||||
driver applied it**, and DLSS Frame Generation identified in the session (`fg_mode = dlssg`, whether or not its factor
|
||||
was counted). The ceiling's decode (frames generated per
|
||||
rendered frame, `03_METRICS` §The mix) held: a ceiling of 5 reached ×6.0, a ceiling of 2 never passed ×3.0.
|
||||
|
||||
**Decided (D83):** a session the driver reports running the App's Dynamic mode is **DLSS 4.5**, below a measured ×5 and
|
||||
@@ -41,7 +42,7 @@ Session 132 (2026-11-06 13:56, hooked, attached, 141 s, Neural Rendering on in t
|
||||
`nvngx_dlssg.dll` 310.9.16.0 and Streamline 2.14.16 (`sl.interposer.dll`, `sl.common.dll`, `sl.dlss_g.dll`,
|
||||
`sl.reflex.dll`). The install ships the matching Streamline plugin, `Engine\Plugins\Runtime\Nvidia\StreamlineCore\
|
||||
Binaries\ThirdParty\Win64\sl.dlss_nr.dll` (402,048 bytes; `nvngx_dlssnr.dll` is 266,424,944), which no list asked about.
|
||||
The driver's super-resolution word read `0x80605` (created and evaluated, no override); the session counted DLSS Frame
|
||||
The driver's super-resolution word read `0x80605` (created and evaluated, no override); the session identified DLSS Frame
|
||||
Generation but refused a factor (non-uniform, ×1.97 overall); 140.2 FPS presented.
|
||||
|
||||
What the App made of it: *DLSS · Super Resolution 310.9.16, from the game · … · DLSS 5 runtime loaded* — loaded, never
|
||||
|
||||
+1
-1
@@ -12,7 +12,7 @@
|
||||
HTML comments are not part of the block.
|
||||
-->
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-11-06.** The software is a beta; its latest
|
||||
> **beta is `0.1.0-beta.33`** (2026-11-03), an unsigned installer built from that tag with its
|
||||
> **beta is `0.1.0-beta.34`** (2026-11-06), an unsigned installer built from that tag with its
|
||||
> checksums published beside it (alphas — experimental builds on a prerelease .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
@@ -116,7 +116,7 @@ Frame timing is derived from high-resolution timestamps taken at the moment the
|
||||
|
||||
<!-- accuracy-block:begin -->
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-11-06.** The software is a beta; its latest
|
||||
> **beta is `0.1.0-beta.33`** (2026-11-03), an unsigned installer built from that tag with its
|
||||
> **beta is `0.1.0-beta.34`** (2026-11-06), an unsigned installer built from that tag with its
|
||||
> checksums published beside it (alphas — experimental builds on a prerelease .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
|
||||
|
||||
@@ -201,12 +201,13 @@ public static class DlssText
|
||||
}
|
||||
|
||||
/// <summary>
|
||||
/// The NVIDIA App's Dynamic frame generation ran in the session (beta.34, D83): DLSS Frame Generation was counted, the
|
||||
/// The NVIDIA App's Dynamic frame generation ran in the session (beta.34, D83): DLSS Frame Generation was identified, the
|
||||
/// game's driver profile sets <c>NGX_DLSSG_MODE</c> to Dynamic, and the driver's frame-generation word reports the mode
|
||||
/// override applied in the game's process (<see cref="NgxOverrideFlags.FgMode"/>). The driver's own mode number —
|
||||
/// 3 under Dynamic and 1 under Fixed on every stored session (<c>spike-notes</c> §26) — is not what is read: NVIDIA's
|
||||
/// header names the profile's values and not the report's. A profile that sets Dynamic the driver never applied, or a
|
||||
/// session where no DLSS Frame Generation was counted, is not evidence.
|
||||
/// session where no DLSS Frame Generation was identified, is not evidence; a factor the count refused takes nothing
|
||||
/// from it.
|
||||
/// </summary>
|
||||
private static bool DynamicFrameGeneration(SessionRow row) =>
|
||||
Is(row.FgMode, "dlssg")
|
||||
|
||||
@@ -112,7 +112,8 @@ public sealed class DlssTextTests
|
||||
/// <summary>
|
||||
/// beta.34, owner decision D83: Phantom Blade Zero under the NVIDIA App's Dynamic frame generation, up to ×3, held ×2.0
|
||||
/// and ×3.0 and read "DLSS 4 (a ×3.0 frame-generation state)" — Dynamic exists only in DLSS 4.5. Evidence is the
|
||||
/// profile's Dynamic AND the driver's report that the override applied AND DLSS Frame Generation counted.
|
||||
/// profile's Dynamic AND the driver's report that the override applied AND DLSS Frame Generation identified — its
|
||||
/// factor need not have been counted.
|
||||
/// </summary>
|
||||
[Fact]
|
||||
public void TheNvidiaAppsDynamicFrameGenerationTheDriverAppliedIsDlss45() => InEnglish(() =>
|
||||
@@ -130,7 +131,10 @@ public sealed class DlssTextTests
|
||||
DlssText.Label(phantomBlade with { DriverProfileJson = _dynamicUpToThree.Replace("\"Value\":4,", "\"Value\":2,", StringComparison.Ordinal) })
|
||||
.Should().Be("DLSS 4 (a ×3.0 frame-generation state)", "Fixed is not Dynamic: Witcher 3 under Fixed ×6 still presented ×2.0");
|
||||
DlssText.Label(phantomBlade with { FgMode = "na", FgFactor = null, FgMixJson = null })
|
||||
.Should().BeNull("no DLSS Frame Generation was counted");
|
||||
.Should().BeNull("no DLSS Frame Generation was identified");
|
||||
DlssText.Label(phantomBlade with { FgFactor = null, FgMixJson = null, FgRefusal = "non_uniform" })
|
||||
.Should().Be("DLSS 4.5 (Dynamic multi frame generation, set in the NVIDIA App)",
|
||||
"DLSS Frame Generation identified is the evidence; a factor the count refused takes nothing from it");
|
||||
DlssText.Label(phantomBlade with { NgxDriverWordsJson = null }).Should().Be("DLSS 4 (a ×3.0 frame-generation state)", "no driver report, no evidence");
|
||||
return 0;
|
||||
});
|
||||
|
||||
Reference in new issue
Block a user