fix(app): the two GPU labels say what each figure is, not which holds the other (D152) (#462)
* docs: owner-only item 47 read (the Cyberpunk difference is the driver's; the holes are gone from steady play); Streamline's Reflex and DLSS-RR guides read against the code Item 47, run by the owner on 0.1.0-beta.49 (sessions 236-245), read from a copy of the ledger and the Overlay's logs: in Cyberpunk 2077 without frame generation the driver's active GPU time is longer than its two marks are apart on 4 917 of 5 394 frames, and on none of 129 900 frames in five other games; samples without a report are confined to a game's start; off means off; D141's stop fired in a real game for the first time. NVIDIA's Streamline guides for Reflex and DLSS Ray Reconstruction (2.14.16), read whole: the guide's page on Advanced metrics now says what bUseGameSleep and bLowLatencyMode mean; two design tables no longer promise PC latency (D147); spike-notes 30 has what the guides add. Two comments (fl_shm.h, dllmain.cpp) said super resolution and ray reconstruction run together - they do not; comments only, no object code changes. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * docs(handoff): item 47 (f) and (g) in the owner's words - the NVIDIA App's Low Latency Mode is off, no hitch Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * docs(handoff): item 47 (f) as the owner showed it - the NVIDIA App's Low Latency Mode is off for Cyberpunk 2077, the game's own Reflex is on Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * fix(app): the two GPU labels say what each figure is, not which holds the other (D152) "GPU active render (idle time excluded)" and "GPU render, start to end (idle time included)" followed NVIDIA's header, which defines the active time as the span between the driver's two GPU marks less its idle time. Item 47 counted it on 0.1.0-beta.49: in Cyberpunk 2077 without frame generation the active time is the longer of the two on 4 917 of 5 394 frames. The owner chose to reword the labels. They now read "GPU active render (the driver's own figure)" and "GPU render (between the driver's start and end marks)", in English, Vietnamese and Japanese; the guide says why. Strings only: the numbers and the means are unchanged. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * docs(handoff): D153 - of Reflex it is enough to tell whether a game has it: Reflex and PCL leave train D, D141's stop is unchanged Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
1 parent
dc329c09b4
commit
5440f8a34a
9 files changed
+46
-21
No files matched your search
@@ -37,6 +37,12 @@ numeric core and does not move; the heading is the full version — corrected 20
|
||||
|
||||
### Changed
|
||||
|
||||
- **The two lines of the graphics card's time say what each is, not which holds the other** (D152, the owner's
|
||||
decision). *GPU active render (idle time excluded)* and *GPU render, start to end (idle time included)* are now
|
||||
*GPU active render (the driver's own figure)* and *GPU render (between the driver's start and end marks)*, in
|
||||
English, Vietnamese and Japanese, and the guide says why: in Cyberpunk 2077 without frame generation the
|
||||
driver's active time is longer than its two marks are apart. The numbers are unchanged.
|
||||
|
||||
- **The guide's page on Advanced metrics says what two of the driver's switches mean** (`guide/12`): the latency
|
||||
report is there in a game that has Reflex built in, whether Reflex is on or off in its menu; `bUseGameSleep`
|
||||
says the game calls Reflex's sleep — NVIDIA asks for that even with Reflex off — and `bLowLatencyMode` is the
|
||||
|
||||
@@ -1099,7 +1099,11 @@ session that ended in a menu read 1). **Since 0.1.0-beta.48 (D142) two more seri
|
||||
`adv.nvapi.reflex.gpu_times.` and `active_render`, `frame_time` — the driver's `gpuActiveRenderTimeUs` and
|
||||
`gpuFrameTimeUs`, each the mean over the frames of that read that gave one. They are the driver's own figures, not
|
||||
spans between two of its marks: in Phantom Blade Zero `gpu_render` (the two GPU marks, idle time included) was
|
||||
longer than `total`, which is why its label now says what it includes (D143). An entry of their own keeps the
|
||||
longer than `total`, which is why its label now says what it includes (D143). **Reworded 2026-11-14 (D152)**:
|
||||
NVIDIA's header defines the active time as that span "excluding the idles in between", and in Cyberpunk 2077
|
||||
without frame generation the active time is the longer of the two on nine frames in ten (HANDOFF, item 47) — so
|
||||
the labels now say what each is (*the driver's own figure*; *between the driver's start and end marks*) and no
|
||||
longer that one is the other less its idle time. The numbers and the means are unchanged. An entry of their own keeps the
|
||||
seven spans within what one chart draws as lines. What the *game* asked of Reflex (`nvapi.reflex.mode`) is an argument of a function no module exports:
|
||||
reading it takes a patch at an address learned at run time, which is refused.
|
||||
|
||||
|
||||
+13
-6
@@ -153,15 +153,18 @@ and its release facts are [`handoff/history/0.1.0-beta.48.md`](handoff/history/0
|
||||
|
||||
1. ~~**The owner runs item 47**~~ **Run and read 2026-11-14** (item 47, *Run 2026-11-14*): the difference in
|
||||
Cyberpunk 2077 is the driver's, the holes are gone from steady play, off means off, and the stop fired once.
|
||||
2. **The owner's to say**: the wording of the two GPU labels (the mean stays — the counts say the driver's
|
||||
active time really is the longer there); whether D141's stop should spare a game's first seconds (Kingdom
|
||||
Come: Deliverance II lost its session's report to one call of 5.3 ms while it started). (f) and (g) are
|
||||
said: the App's *Low Latency Mode* is off, and no hitch.
|
||||
2. **The two GPU labels were reworded on the owner's word** (D152, 2026-11-14; strings in three languages, the
|
||||
guide — in `[Unreleased]`, not in a release yet). **D141's stop stays as it is, and nothing more of Reflex is read** (D153, the owner
|
||||
the same evening: "it only has to tell whether the game has it or not; Kingdom Come: Deliverance II has no
|
||||
Reflex in its settings" — so that session lost nothing to the stop). (f) and (g) are said: the App's *Low
|
||||
Latency Mode* is off, and no hitch.
|
||||
3. **`slAllocateResources`** keeps its patch (D135); looked at again when there are more sessions.
|
||||
4. **Train D** 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. **Read 2026-11-14 against Streamline's own
|
||||
guide (§30, *Added 2026-11-14*): the markers are the times the driver's report already gives**, so that entry
|
||||
would add a count and nothing else. Recommended to the owner: leave Reflex and PCL out of train D.
|
||||
would add a count and nothing else. ~~Recommended to the owner: leave Reflex and PCL out of train D.~~
|
||||
**Decided (D153): Reflex and PCL are not part of train D** — whether a game has Reflex is all that is wanted,
|
||||
and the driver's report already says it.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
@@ -987,7 +990,9 @@ left unexercised; item 40 (d).
|
||||
**The stop fired in a real game for the first time** (D141): Kingdom Come: Deliverance II, 12 s after the
|
||||
attach, while the game was starting — the seventh read took 5 337 µs, and no further read was made; the
|
||||
session says so (`Slow`), the game ran 287 s and closed normally. No frame had been reported in those seven
|
||||
reads. Elsewhere the slowest call was 22–235 µs. In Lies of P the driver reported no frame at all.
|
||||
reads. **The owner: that game has no Reflex in its settings** — so there was no report to lose; the
|
||||
session's line says *stopped* where, without the slow call, it would have said *the driver reported no
|
||||
frame*. Elsewhere the slowest call was 22–235 µs. In Lies of P the driver reported no frame at all.
|
||||
**What the states say of Reflex and frame generation** (each batch carries its own): low-latency mode was
|
||||
**on at a multiplier of 1** in Cyberpunk 2077 (88 reads), Black Myth: Wukong (253), Hogwarts Legacy (299) and
|
||||
Dying Light: The Beast (345); Phantom Blade Zero without frame generation sleeps through Reflex with
|
||||
@@ -1169,6 +1174,8 @@ Where each owner decision is recorded — the file and its section, and a label
|
||||
| D149 | [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Native logging | told that a bug report carries the five newest Overlay logs and so these lines: **no change to the legal texts** — the Privacy Policy names the logs of the component loaded into games, and the lines are counts and sums of microseconds |
|
||||
| D150 | [`07_IPC.md`](07_IPC.md) §Region 5 | the samples that carry no report are mended **on both sides**: the Overlay reads and publishes on a grid of one second, and the Agent no longer overwrites a reading that waits for a sample |
|
||||
| D151 | [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Native logging | the owner's word: Reflex is checked together with frame generation — without it the owner's games do not switch Reflex on, and a low-latency switch that reads on and off is the NVIDIA App's override. A batch of counts belongs to one state of the sleep status |
|
||||
| D152 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §The inventory | the two GPU labels say what each figure is — *the driver's own figure*, *between the driver's start and end marks* — not "idle time excluded / included": item 47 counted the active time as the longer in Cyberpunk 2077. Strings only; numbers and means unchanged |
|
||||
| D153 | [`spike-notes/30-reflex-latency.md`](spike-notes/30-reflex-latency.md) *Added 2026-11-14* | the owner's word: of Reflex it is enough to tell whether a game has it. Reflex and PCL leave train D (`sl.pcl.markers` stays refused), and D141's stop is not changed for a game's first seconds. My reading of one sentence; nothing shipped is removed by it |
|
||||
| D109 | [`../legal/DISCLAIMER.md`](../legal/DISCLAIMER.md) §5, §5A | asked on 2026-11-11 with both sentences quoted: the Disclaimer goes to 2.15 with the Privacy Policy — PawnIO and the admin mode are no longer "for the CPU temperature" alone; with Advanced metrics on they also read the processor's, the memory's and the motherboard's sensors. The admin mode's disclosure follows (`agent-admin-dialog/2`) |
|
||||
|
||||
---
|
||||
|
||||
@@ -199,7 +199,8 @@ above fired on the harness, and it ends in the question of one real title.
|
||||
- **The markers are the report.** `slPCLSetMarker` replaces `NvAPI_D3D_SetLatencyMarker`, and the times the
|
||||
markers carry (simulation, render submit, present) are the ones the driver hands back in the report this
|
||||
product already reads (route D). `sl.pcl.markers` would add a count of calls, the ping and the flash trigger —
|
||||
nothing a player reads. **Recommended to the owner: leave Reflex and PCL out of train D.**
|
||||
nothing a player reads. **Recommended to the owner: leave Reflex and PCL out of train D** — **decided the
|
||||
same evening (D153)**: whether a game has Reflex is all that is wanted.
|
||||
- **PC latency is not in the report, and NVIDIA takes it from outside the game**: its PCL statistics, read by
|
||||
tools started from an administrator's prompt (route E here). D147 stands on that; two design tables that still
|
||||
promised "PC latency as reported by Reflex" were corrected today (`03_METRICS`, `05_DETECTION`).
|
||||
|
||||
@@ -101,11 +101,15 @@ while Reflex is off, so *On* there does not say Reflex is on — `bLowLatencyMod
|
||||
while frame generation is on. Frame generation needs Reflex and not the other way round: the mode can be on
|
||||
with `fgMultiplier` at 1.
|
||||
|
||||
**The stages overlap; they are not parts that add up to the total.** And *GPU render, start to end* includes the
|
||||
time the card spent waiting between pieces of work — in one game it is longer than the whole frame. So a second
|
||||
chart, **the graphics card's time per frame, as the driver works it out**, has two lines of the driver's own
|
||||
figures: *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. A driver may give neither; the chart is then not there, and nothing is wrong.
|
||||
**The stages overlap; they are not parts that add up to the total.** And *GPU render* is the time between two
|
||||
marks the driver sets, at the start and at the end of the card's work on a frame: where the card waits between
|
||||
pieces of work, the waiting is in it — in one game it is longer than the whole frame. So a second chart, **the
|
||||
graphics card's time per frame, as the driver works it out**, has two lines of the driver's own figures: *GPU
|
||||
active render*, how long the driver says the card worked on the frame, and *GPU frame time*, from the end of one
|
||||
frame's work to the end of the next. **The active time is usually the shorter of the two, and not always**: in
|
||||
Cyberpunk 2077 without frame generation it is about a fifth longer than the two marks are apart, frame after
|
||||
frame — the driver counts work its marks do not enclose. Both are shown as the driver gives them. A driver may
|
||||
give neither; the chart is then not there, and nothing is wrong.
|
||||
|
||||
Three things to know about them:
|
||||
|
||||
|
||||
@@ -1054,7 +1054,7 @@
|
||||
<comment>review</comment>
|
||||
</data>
|
||||
<data name="AdvToken_active_render" xml:space="preserve">
|
||||
<value>GPU 実描画 (待機時間を除く)</value>
|
||||
<value>GPU 実描画 (ドライバーの算出値)</value>
|
||||
<comment>review</comment>
|
||||
</data>
|
||||
<data name="AdvToken_frame_time" xml:space="preserve">
|
||||
@@ -1062,7 +1062,7 @@
|
||||
<comment>review</comment>
|
||||
</data>
|
||||
<data name="AdvToken_gpu_render" xml:space="preserve">
|
||||
<value>GPU 描画、開始から終了まで (待機時間を含む)</value>
|
||||
<value>GPU 描画 (ドライバーの開始マークから終了マークまで)</value>
|
||||
<comment>review</comment>
|
||||
</data>
|
||||
<data name="AdvToken_gsync_module" xml:space="preserve">
|
||||
|
||||
@@ -796,13 +796,13 @@
|
||||
<value>Game Ready</value>
|
||||
</data>
|
||||
<data name="AdvToken_active_render" xml:space="preserve">
|
||||
<value>GPU active render (idle time excluded)</value>
|
||||
<value>GPU active render (the driver's own figure)</value>
|
||||
</data>
|
||||
<data name="AdvToken_frame_time" xml:space="preserve">
|
||||
<value>GPU frame time, one frame's end to the next</value>
|
||||
</data>
|
||||
<data name="AdvToken_gpu_render" xml:space="preserve">
|
||||
<value>GPU render, start to end (idle time included)</value>
|
||||
<value>GPU render (between the driver's start and end marks)</value>
|
||||
</data>
|
||||
<data name="AdvToken_gsync_module" xml:space="preserve">
|
||||
<value>G-SYNC module</value>
|
||||
|
||||
@@ -791,13 +791,13 @@
|
||||
<value>Game Ready</value>
|
||||
</data>
|
||||
<data name="AdvToken_active_render" xml:space="preserve">
|
||||
<value>GPU thực sự vẽ (không tính lúc nghỉ)</value>
|
||||
<value>GPU thực sự vẽ (số do driver tự tính)</value>
|
||||
</data>
|
||||
<data name="AdvToken_frame_time" xml:space="preserve">
|
||||
<value>nhịp khung của GPU, từ lúc xong khung này tới lúc xong khung kế</value>
|
||||
</data>
|
||||
<data name="AdvToken_gpu_render" xml:space="preserve">
|
||||
<value>GPU vẽ, từ lúc bắt đầu tới lúc xong (gồm cả lúc nghỉ)</value>
|
||||
<value>GPU vẽ (giữa mốc bắt đầu và mốc kết thúc của driver)</value>
|
||||
</data>
|
||||
<data name="AdvToken_gsync_module" xml:space="preserve">
|
||||
<value>Mô-đun G-SYNC</value>
|
||||
|
||||
@@ -455,13 +455,16 @@ public sealed class AdvancedPresenterTests
|
||||
];
|
||||
AdvancedPresenter.Metrics(series, []).Select(static m => m.Id).Should().BeEquivalentTo("nvapi.reflex.frame_report", "nvapi.reflex.gpu_times");
|
||||
|
||||
// The span between the driver's two GPU marks says what it includes, in every language (D143).
|
||||
// The span between the driver's two GPU marks says what it is, in every language (D143) - and neither label says
|
||||
// which of the two holds the other (D152): in Cyberpunk 2077 the driver's active time is the longer.
|
||||
foreach (string culture in new[] { "", "vi", "ja" })
|
||||
{
|
||||
string render = Strings.ResourceManager.GetString(nameof(Strings.AdvToken_gpu_render), CultureInfo.GetCultureInfo(culture))!;
|
||||
string active = Strings.ResourceManager.GetString(nameof(Strings.AdvToken_active_render), CultureInfo.GetCultureInfo(culture))!;
|
||||
render.Should().Contain("(", "the label carries what the span includes");
|
||||
render.Should().Contain("(", "the label carries what the span is");
|
||||
render.Should().NotBe(active);
|
||||
render.Should().NotContain("idle", "the span is not said to include the active time's idle time");
|
||||
active.Should().NotContain("idle", "the active time is not said to be the span less its idle time");
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in new issue
Block a user