Compare commits
1
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
e1bb67eb0b |
No files matched your search
+1
-43
@@ -35,55 +35,13 @@ numeric core and does not move; the heading is the full version — corrected 20
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Changed
|
||||
|
||||
- **Play ▸ *Start directly* says what a Steam game may do.** Some Steam games hand themselves to Steam when
|
||||
FrameLedger starts them — Lies of P closes within seconds and Steam starts it again. Starting a game Steam installed,
|
||||
the notice now says it may hand itself to Steam first and that the game Steam then starts is recorded; the *Start
|
||||
directly* tooltip and Settings ▸ Games ▸ *Play button* say so too, adding that a few will not start outside Steam at
|
||||
all. Steam games keep *Start directly*: three of the five started directly on 2026-10-20 ran and were measured from
|
||||
their first frame, and a Vulkan game is measured only when FrameLedger starts it. In en/vi/ja (ja marked for review).
|
||||
|
||||
### Fixed
|
||||
|
||||
- **A frame-generation "state" of ×2.52.** The owner's Silent Hill 2 session under the NVIDIA App's *Dynamic* multi
|
||||
frame generation listed ×2.52 for 13 seconds beside ×2.0 and ×3.0: the five-second windows in which the multiplier
|
||||
stepped from ×2 to ×3 read in between, and three of them formed a state nobody held. Every frame generation that
|
||||
ships multiplies by a whole number, so a window now counts toward a state only within 10 % of one; the others are
|
||||
*Not classified*. Sessions already recorded are read by the same rule: that session lists ×2.0, ×3.0, no frame
|
||||
generation and 7.36 % not classified. The owner's runs of 2026-10-20 are recorded in
|
||||
`docs/spike-notes/23-owner-runs-2026-10-20.md`.
|
||||
- **The NVIDIA driver's DLSS report was lost from every stored session.** FrameLedger asked the driver one last time
|
||||
after the game had closed, and that answer — which no longer says DLSS ran — replaced the ones read while the game
|
||||
ran. So no session said *DLSS (driver-reported)* where no hook saw DLSS, and none named the NVIDIA App's quality mode
|
||||
on such a game: Clair Obscur: Expedition 33 under the App's override read *Upscaler not identified*. The driver is no
|
||||
longer asked once the game has closed, and once it reports that DLSS ran, the session keeps it. Sessions recorded
|
||||
before keep what they stored.
|
||||
- **Play ▸ *Start directly* recorded nothing of a game that hands itself to Steam.** Lies of P, started directly, closes
|
||||
within seconds and Steam starts it again; the game Steam started was turned away while the first session ended and
|
||||
never recorded. It is now recorded once that session ends, as a game started again already was. Each such start
|
||||
still counts toward the two early exits that turn hooking off for a game, so Limitations ▸ Play advises starting such
|
||||
a game through its store.
|
||||
- **Opening a session's summary twice opened two windows.** The open window comes forward instead, restored if
|
||||
minimised.
|
||||
- **No window or monitor size for a game in exclusive full-screen.** A game leaving exclusive full-screen closes its
|
||||
window a moment before its swap chain says so, and those last samples replaced the sizes: two Lies of P and three
|
||||
Dark Souls III sessions show none. The sizes are now the last ones the mode saw.
|
||||
- **A DLSS line that said only "DLSS"**, under a header that already did, is no longer shown: the NVIDIA App's override
|
||||
loads its libraries under names FrameLedger does not list (The Witcher 3), and the *Loaded:* line prints them.
|
||||
- **Two integration tests that failed under load** (developers only). The guard reads every process above the test
|
||||
harness too, the test host among them, and under a full `build.ps1 check` the test host is still starting its other
|
||||
test classes: a module it released while the guard read its list refused the injection (`ModuleScanFailed`, and
|
||||
`ProcessUnreadable` on 2026-10-19). The drain suite asks the guard again on those two reasons, four times at most;
|
||||
the pause case, which once read the writer still starting, waits for it to be ready; and every injection test waits
|
||||
for the harness's own "presenting" line instead of 800 ms (`tests/Shared/HarnessReady.cs`).
|
||||
|
||||
## Releases
|
||||
|
||||
Newest first. Each file holds that release's section exactly as it stood here.
|
||||
|
||||
| Version | Date | Notes |
|
||||
|---|---|---|
|
||||
| `0.1.0-beta.27` | 2026-10-20 | [`docs/changelog/0.1.0-beta.27.md`](docs/changelog/0.1.0-beta.27.md) |
|
||||
| `0.1.0-beta.26` | 2026-10-19 | [`docs/changelog/0.1.0-beta.26.md`](docs/changelog/0.1.0-beta.26.md) |
|
||||
| `0.1.0-beta.25` | 2026-10-19 | [`docs/changelog/0.1.0-beta.25.md`](docs/changelog/0.1.0-beta.25.md) |
|
||||
| `0.1.0-beta.24` | 2026-10-19 | [`docs/changelog/0.1.0-beta.24.md`](docs/changelog/0.1.0-beta.24.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.26.*
|
||||
*Beta software: this page describes version 0.1.0-beta.27.*
|
||||
|
||||
## Games it will not measure
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ pages.
|
||||
|
||||
<!-- accuracy-block:begin -->
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-10-19.** The software is a beta; its latest
|
||||
> **pre-release is `0.1.0-beta.26`** (2026-10-19), an unsigned installer built from that tag with its
|
||||
> **pre-release is `0.1.0-beta.27`** (2026-10-20), an unsigned installer built from that tag with its
|
||||
> checksums published beside it. 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
|
||||
@@ -174,7 +174,7 @@ Elevation is **optional — for everything.** Hooked capture is the normal path
|
||||
|
||||
## Install
|
||||
|
||||
> **The latest pre-release is `v0.1.0-beta.26` (2026-10-19); before it `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 pre-release is `v0.1.0-beta.27` (2026-10-20); before it `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**.
|
||||
|
||||
+48
-26
@@ -65,6 +65,7 @@ owner-only items stay below; the history of every train, the passed owner-only i
|
||||
| `§beta.23` | [`handoff/history/0.1.0-beta.23.md`](handoff/history/0.1.0-beta.23.md) |
|
||||
| `§beta.24` | [`handoff/history/0.1.0-beta.24.md`](handoff/history/0.1.0-beta.24.md) |
|
||||
| `§beta.25` | [`handoff/history/0.1.0-beta.25.md`](handoff/history/0.1.0-beta.25.md) |
|
||||
| `§beta.26` | [`handoff/history/0.1.0-beta.26.md`](handoff/history/0.1.0-beta.26.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) |
|
||||
@@ -72,39 +73,51 @@ owner-only items stay below; the history of every train, the passed owner-only i
|
||||
|
||||
---
|
||||
|
||||
## **START HERE** — 2026-10-19, 0.1.0-beta.26: a ×1336 frame-generation state, fixed
|
||||
## **START HERE** — 2026-10-20, 0.1.0-beta.27: the owner's eight sessions of 2026-10-20
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.26.md`; this is what no other file carries.* The owner ran the installed
|
||||
beta.25 the evening it shipped and sent screenshots: "Bạn có thể thử kiểm tra kết quả (fix nếu cần), cập nhật docs,
|
||||
làm chip và trigger lại sonarcloud thử nhé." Silent Hill 2's summary listed a ×1336.0 frame-generation state; the owner
|
||||
pointed at the cause ("có khoảng thời gian đầu game đang biên dịch shader") and then: "Bạn có thể cân nhắc (nếu thực sự
|
||||
cần) bản beta26 fix lỗi nhé." It was needed: every beta.25 session of a title that compiles its shaders under a loaded
|
||||
frame-generation runtime can store such a row, and the summary and the DLSS line print it. #327 (the fix and the
|
||||
owner's runs), #328 (the SonarCloud chip — the owner marked the last six issues the same day, and `main`'s quality
|
||||
gate passes) and this release.
|
||||
*Status is `docs/changelog/0.1.0-beta.27.md`; this is what no other file carries.* The owner ran the installed
|
||||
beta.26 the morning after it shipped: "Bạn có thể kiểm tra kết quả ở khoảng 8 kết quả gần nhất. Sửa luôn 2 test flake
|
||||
luôn trong phiên này và fix bug, publish bản mới nếu có bug." — and, mid-way: "1. cyberpunk 2077 là switch in-game.
|
||||
2. Fix bug mở xem 1 session nhiều lần ra nhiều cửa sổ." — then, on the Steam hand-off: "bạn có thể lựa chọn: note vào
|
||||
giao diện UI là các game trên Steam sẽ tự trigger Steam trước / Thêm Setting cố định trên game Steam là luôn chạy qua
|
||||
steam client". #330 (six fixes, the Steam note, the two flaky tests, `spike-notes` §23) and this release.
|
||||
|
||||
**No new owner decision.** The fix makes the window rule say what `03_METRICS` already promised ("windows with too few
|
||||
frames to read") about APPLICATION frames, not presents, and bounds the ratio at ×8 (`FgWindow.GenerationCeiling`) —
|
||||
no shipping frame generation passes ×6; the bound is raised only with a title measured above it. A stored mix is read
|
||||
by the same rule, so no session is rewritten and none keeps the row.
|
||||
**No new owner decision.** Each fix makes the code do what a document already said: a state is a frame generation's
|
||||
whole multiplier (`03_METRICS` §The mix), the driver's report is the session's and not the dead pid's (§The
|
||||
driver-reported rung), a game started again is recorded (`04_CAPTURE`, beta.15) — after a launch too —, a summary is
|
||||
one window, the display sizes are the ones seen.
|
||||
|
||||
**Measured on the owner's ledger** (a read-only backup copy, decoded with the App's own loader in a scratch test): the
|
||||
×1336.0 row was Silent Hill 2's first fifteen seconds — 1,369, 4,877 and 1,303 presents with 1, 0 and 1 application
|
||||
frames per five seconds, then a 13,348 ms frame: the game compiling its shaders at start (the owner). The only stored
|
||||
value above ×8 in 60 sessions. Lies of P read no FSR mode with `ffxQuery` hooked (bit 11 in `hooks_installed_mask`):
|
||||
item 21's first branch (`spike-notes` §22).
|
||||
**The owner's two ways for Steam games, and the one taken.** The owner offered a note in the UI or a fixed rule that
|
||||
Steam's games always go through the Steam client, and left the choice open. The note was taken (`08_UI` §Games, Play):
|
||||
the rule would have cost what *Start directly* exists for — three of the five Steam games started directly on
|
||||
2026-10-20 ran and were measured from their first frame, and a Vulkan game is measured only when FrameLedger starts it
|
||||
(Everhex Demo, a Steam game). Not every Steam game hands itself to Steam: Lies of P did, Expedition 33 closed instead.
|
||||
|
||||
**One question for the owner, not taken:** the crash safety counts a direct start's early exit — Lies of P handing
|
||||
itself to Steam, Expedition 33 closing within five seconds even unhooked — and two such starts turn hooking off for
|
||||
the game (`19_SAFETY` §Crash & stability safety, measured `spike-notes` §23). The policy cannot tell a hand-off from
|
||||
the hang it exists for, so it stands, and users are told to start such a game through its store. An exemption — an
|
||||
exit followed by the same executable within seconds — would loosen a safety rule and is the owner's to decide.
|
||||
|
||||
**Measured on the owner's ledger** (a read-only backup copy, the App's own loader in a scratch test): of 70 sessions,
|
||||
the ×2.52 row was the only stored state between two multipliers; none of the 14 sessions the driver answered kept
|
||||
`CREATED | EVALUATE` (Expedition 33: `0x8067F` while it ran on 2026-09-06, `0x8007F` stored); two Lies of P and three
|
||||
Dark Souls III sessions stored no window size.
|
||||
|
||||
**Traps met on the way:**
|
||||
|
||||
- **A row written by a released build is read by every later one.** Changing what makes a state changes nothing on a
|
||||
stored session unless its reader applies the rule too (`FgMixRecord.Parse`); the row would keep the old meaning.
|
||||
- **A session's timeline is one scratch test away**: `SessionSeriesLoader` over a ledger copy prints presents,
|
||||
generated and application frames per five seconds (a `PagesLoadTests` partial, never committed). Decoding the blobs
|
||||
by hand is not needed.
|
||||
- **SonarCloud's PR analysis lists only issues new in the PR**: whether a change clears a finding on `main` shows only
|
||||
in `main`'s next analysis.
|
||||
- **A probe taken after the target exits is not the session's.** NVIDIA's driver still answers for a dead pid, with
|
||||
the bits that say a feature ran cleared; any per-process question asked at a session's end must check that the game
|
||||
still lives (`CaptureSession`'s last snapshot), or the last answer erases the session's.
|
||||
- **A launch's own process reaches the watcher after the launch began**, so it lands among the processes turned away
|
||||
"one at a time"; whatever acts on those must leave out the launch's own pids (`Running.Targets`).
|
||||
- **The logs are the timeline of what the owner did**: `ui-*.log`'s `play:` lines say *through the agent* (Start
|
||||
directly) or *through steam*; `agent-*.log` has every session's end, a discarded one included — the ledger keeps no
|
||||
row for it. A hooking switch the user flips leaves no line: say what the logs show, not why hooking was off.
|
||||
- **Decode the windows before naming a cause**: the ×2.52 windows' runs — 251 application frames followed by one
|
||||
generated frame, 270 by two — showed the stepping at a glance.
|
||||
|
||||
**Owner-only:** items 20 and 21 annotated (`spike-notes` §22); nothing added.
|
||||
**Owner-only:** items 20 and 21 annotated (§23); item 22 added.
|
||||
|
||||
|
||||
## Owner-only — no PR can close these
|
||||
@@ -242,6 +255,15 @@ item 21's first branch (`spike-notes` §22).
|
||||
matched: the title did not ask while the hook was in. It cannot be launched by FrameLedger as this item asks — started
|
||||
directly it hands itself to Steam within seconds, and before beta.27 the game Steam started was not recorded at
|
||||
all.)*
|
||||
22. **beta.27 on real hardware.** (a) **The driver's report, and item 20(b):** Expedition 33 under the NVIDIA App's
|
||||
DLSS override → the header reads *DLSS (driver-reported)* with the override's mode and *· NVIDIA App* (*Balanced*
|
||||
as set on 2026-10-20); then 20(b)'s four modes. Still *Upscaler not identified* → record the session's stored
|
||||
`ngx_driver_words`: no reading while the game ran said the feature was created and evaluated. (b) **Start directly
|
||||
on Lies of P:** the notice says a Steam game may hand itself to Steam first, and the game Steam starts is recorded —
|
||||
`agent-*.log` says *started while the last session of its executable was ending; recording it now*. The crash safety
|
||||
counts the hand-off: after two such starts hooking is off again (`19_SAFETY`). (c) **One window per session:** open a session from a Sessions tab, then again from the game
|
||||
page or its notification → the same window comes forward, restored if minimised. (d) **A game in exclusive
|
||||
full-screen** (Dark Souls III, Lies of P) → its summary's Display card shows the window size.
|
||||
**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 —
|
||||
|
||||
@@ -0,0 +1,56 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.27 was cut, 2026-10-20 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.27] - 2026-10-20
|
||||
|
||||
**The twenty-seventh pre-release: the owner's eight sessions of 2026-10-20, checked — six faults fixed, and *Start
|
||||
directly* says what a Steam game may do.** The same unsigned installer: verify its hash against `SHA256SUMS.txt`, then
|
||||
*More info → Run anyway*.
|
||||
|
||||
**Updating from `0.1.0-beta.26`:** Help ▸ Check for updates, then *Restart to update* with no game running. Nothing is
|
||||
shown for you to accept again (the Disclaimer stays 2.11, the Privacy Policy 2.12), the ledger stays at schema 21, and
|
||||
no game is read again: the detection rules (`2026.10.4`) are beta.26's. Sessions you already recorded read the
|
||||
frame-generation fix at once; the driver's DLSS report, the display sizes and the game Steam starts are recorded from
|
||||
this version on — nothing already stored is rewritten.
|
||||
|
||||
### Changed
|
||||
|
||||
- **Play ▸ *Start directly* says what a Steam game may do.** Some Steam games hand themselves to Steam when
|
||||
FrameLedger starts them — Lies of P closes within seconds and Steam starts it again. Starting a game Steam installed,
|
||||
the notice now says it may hand itself to Steam first and that the game Steam then starts is recorded; the *Start
|
||||
directly* tooltip and Settings ▸ Games ▸ *Play button* say so too, adding that a few will not start outside Steam at
|
||||
all. Steam games keep *Start directly*: three of the five started directly on 2026-10-20 ran and were measured from
|
||||
their first frame, and a Vulkan game is measured only when FrameLedger starts it. In en/vi/ja (ja marked for review).
|
||||
|
||||
### Fixed
|
||||
|
||||
- **A frame-generation "state" of ×2.52.** The owner's Silent Hill 2 session under the NVIDIA App's *Dynamic* multi
|
||||
frame generation listed ×2.52 for 13 seconds beside ×2.0 and ×3.0: the five-second windows in which the multiplier
|
||||
stepped from ×2 to ×3 read in between, and three of them formed a state nobody held. Every frame generation that
|
||||
ships multiplies by a whole number, so a window now counts toward a state only within 10 % of one; the others are
|
||||
*Not classified*. Sessions already recorded are read by the same rule: that session lists ×2.0, ×3.0, no frame
|
||||
generation and 7.36 % not classified. The owner's runs of 2026-10-20 are recorded in
|
||||
`docs/spike-notes/23-owner-runs-2026-10-20.md`.
|
||||
- **The NVIDIA driver's DLSS report was lost from every stored session.** FrameLedger asked the driver one last time
|
||||
after the game had closed, and that answer — which no longer says DLSS ran — replaced the ones read while the game
|
||||
ran. So no session said *DLSS (driver-reported)* where no hook saw DLSS, and none named the NVIDIA App's quality mode
|
||||
on such a game: Clair Obscur: Expedition 33 under the App's override read *Upscaler not identified*. The driver is no
|
||||
longer asked once the game has closed, and once it reports that DLSS ran, the session keeps it. Sessions recorded
|
||||
before keep what they stored.
|
||||
- **Play ▸ *Start directly* recorded nothing of a game that hands itself to Steam.** Lies of P, started directly, closes
|
||||
within seconds and Steam starts it again; the game Steam started was turned away while the first session ended and
|
||||
never recorded. It is now recorded once that session ends, as a game started again already was. Each such start
|
||||
still counts toward the two early exits that turn hooking off for a game, so Limitations ▸ Play advises starting such
|
||||
a game through its store.
|
||||
- **Opening a session's summary twice opened two windows.** The open window comes forward instead, restored if
|
||||
minimised.
|
||||
- **No window or monitor size for a game in exclusive full-screen.** A game leaving exclusive full-screen closes its
|
||||
window a moment before its swap chain says so, and those last samples replaced the sizes: two Lies of P and three
|
||||
Dark Souls III sessions show none. The sizes are now the last ones the mode saw.
|
||||
- **A DLSS line that said only "DLSS"**, under a header that already did, is no longer shown: the NVIDIA App's override
|
||||
loads its libraries under names FrameLedger does not list (The Witcher 3), and the *Loaded:* line prints them.
|
||||
- **Two integration tests that failed under load** (developers only). The guard reads every process above the test
|
||||
harness too, the test host among them, and under a full `build.ps1 check` the test host is still starting its other
|
||||
test classes: a module it released while the guard read its list refused the injection (`ModuleScanFailed`, and
|
||||
`ProcessUnreadable` on 2026-10-19). The drain suite asks the guard again on those two reasons, four times at most;
|
||||
the pause case, which once read the writer still starting, waits for it to be ready; and every injection test waits
|
||||
for the harness's own "presenting" line instead of 800 ms (`tests/Shared/HarnessReady.cs`).
|
||||
@@ -0,0 +1,37 @@
|
||||
# HANDOFF history — 0.1.0-beta.26
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.27 was cut, 2026-10-20 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" point inside the original file.*
|
||||
|
||||
## **START HERE** — 2026-10-19, 0.1.0-beta.26: a ×1336 frame-generation state, fixed
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.26.md`; this is what no other file carries.* The owner ran the installed
|
||||
beta.25 the evening it shipped and sent screenshots: "Bạn có thể thử kiểm tra kết quả (fix nếu cần), cập nhật docs,
|
||||
làm chip và trigger lại sonarcloud thử nhé." Silent Hill 2's summary listed a ×1336.0 frame-generation state; the owner
|
||||
pointed at the cause ("có khoảng thời gian đầu game đang biên dịch shader") and then: "Bạn có thể cân nhắc (nếu thực sự
|
||||
cần) bản beta26 fix lỗi nhé." It was needed: every beta.25 session of a title that compiles its shaders under a loaded
|
||||
frame-generation runtime can store such a row, and the summary and the DLSS line print it. #327 (the fix and the
|
||||
owner's runs), #328 (the SonarCloud chip — the owner marked the last six issues the same day, and `main`'s quality
|
||||
gate passes) and this release.
|
||||
|
||||
**No new owner decision.** The fix makes the window rule say what `03_METRICS` already promised ("windows with too few
|
||||
frames to read") about APPLICATION frames, not presents, and bounds the ratio at ×8 (`FgWindow.GenerationCeiling`) —
|
||||
no shipping frame generation passes ×6; the bound is raised only with a title measured above it. A stored mix is read
|
||||
by the same rule, so no session is rewritten and none keeps the row.
|
||||
|
||||
**Measured on the owner's ledger** (a read-only backup copy, decoded with the App's own loader in a scratch test): the
|
||||
×1336.0 row was Silent Hill 2's first fifteen seconds — 1,369, 4,877 and 1,303 presents with 1, 0 and 1 application
|
||||
frames per five seconds, then a 13,348 ms frame: the game compiling its shaders at start (the owner). The only stored
|
||||
value above ×8 in 60 sessions. Lies of P read no FSR mode with `ffxQuery` hooked (bit 11 in `hooks_installed_mask`):
|
||||
item 21's first branch (`spike-notes` §22).
|
||||
|
||||
**Traps met on the way:**
|
||||
|
||||
- **A row written by a released build is read by every later one.** Changing what makes a state changes nothing on a
|
||||
stored session unless its reader applies the rule too (`FgMixRecord.Parse`); the row would keep the old meaning.
|
||||
- **A session's timeline is one scratch test away**: `SessionSeriesLoader` over a ledger copy prints presents,
|
||||
generated and application frames per five seconds (a `PagesLoadTests` partial, never committed). Decoding the blobs
|
||||
by hand is not needed.
|
||||
- **SonarCloud's PR analysis lists only issues new in the PR**: whether a change clears a finding on `main` shows only
|
||||
in `main`'s next analysis.
|
||||
|
||||
**Owner-only:** items 20 and 21 annotated (`spike-notes` §22); nothing added.
|
||||
+1
-1
@@ -12,7 +12,7 @@
|
||||
HTML comments are not part of the block.
|
||||
-->
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-10-19.** The software is a beta; its latest
|
||||
> **pre-release is `0.1.0-beta.26`** (2026-10-19), an unsigned installer built from that tag with its
|
||||
> **pre-release is `0.1.0-beta.27`** (2026-10-20), an unsigned installer built from that tag with its
|
||||
> checksums published beside it. 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
@@ -114,7 +114,7 @@ Frame timing is derived from high-resolution timestamps taken at the moment the
|
||||
|
||||
<!-- accuracy-block:begin -->
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-10-19.** The software is a beta; its latest
|
||||
> **pre-release is `0.1.0-beta.26`** (2026-10-19), an unsigned installer built from that tag with its
|
||||
> **pre-release is `0.1.0-beta.27`** (2026-10-20), an unsigned installer built from that tag with its
|
||||
> checksums published beside it. 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