Compare commits
5
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
134115bfd5 | ||
|
|
da2cb93fa9 | ||
|
|
eb1c375b87 | ||
|
|
4a0d5b482d | ||
|
|
a13206f220 |
No files matched your search
+4
-157
@@ -59,12 +59,10 @@ dotnet_diagnostic.MA0011.severity = warning
|
||||
# and GenerateDocumentationFile is on for the shipping ones.
|
||||
dotnet_diagnostic.CS1591.severity = suggestion
|
||||
|
||||
# --- ReSharper inspections: what Qodana reads (docs/13_CI_CD.md §Qodana, D93 and D100) ---
|
||||
# Qodana's linters run ReSharper's engine - Qodana for .NET since 2026-11-11, the Community linter before it - and the
|
||||
# engine reads these keys; so does Rider or ReSharper in the editor, which is why they are here and not in
|
||||
# qodana.yaml: the same list everywhere. An inspection is off only where it argues with a choice this project made;
|
||||
# each line says which. Everything else it reports is fixed. (What is NOT ReSharper's - a whole severity, the
|
||||
# IntelliJ platform's Markdown and XML inspections, JetBrains' security rules - has no key here and is in qodana.yaml.)
|
||||
# --- ReSharper inspections: what Qodana reads (docs/13_CI_CD.md §Qodana, D93) ---
|
||||
# Qodana Community for .NET is ReSharper's InspectCode, and InspectCode reads these keys - so does Rider or ReSharper
|
||||
# in the editor, which is why they are here and not in qodana.yaml: the same list everywhere. An inspection is off
|
||||
# only where it argues with a choice this project made; each line says which. Everything else it reports is fixed.
|
||||
[*.{cs,xaml}]
|
||||
# The compiler's missing-XML-comment warning, already a suggestion above (CS1591): InspectCode reports suggestions.
|
||||
resharper_c_sharp_warnings_cs1591_highlighting = none
|
||||
@@ -149,12 +147,6 @@ resharper_redundant_empty_switch_section_highlighting = none
|
||||
# A binding path through a null yields no value, and the template shows nothing: that is the design.
|
||||
resharper_xaml_possible_null_reference_exception_highlighting = none
|
||||
|
||||
[*.resx]
|
||||
# A vi or ja value that equals the English one is deliberate: product and technology names, units and format strings
|
||||
# are not translated, and a ja safety string is the English verbatim until a reviewer signs it (docs/09_I18N.md;
|
||||
# tools/resx-audit.ps1 holds that rule). 271 results on Qodana for .NET's first run.
|
||||
resharper_overridden_with_same_value_highlighting = none
|
||||
|
||||
[src/FrameLedger.App/**.cs]
|
||||
# WPF codegen constraints, not style choices. The generated App.g.cs and
|
||||
# *.g.cs partials declare these types public, so making them internal is a
|
||||
@@ -184,148 +176,3 @@ resharper_collection_never_updated_local_highlighting = none
|
||||
resharper_unused_method_return_value_local_highlighting = none
|
||||
resharper_redundant_assignment_highlighting = none
|
||||
resharper_return_type_can_be_not_nullable_highlighting = none
|
||||
|
||||
# --- ReSharper C++ inspections: what Qodana's native report reads (docs/13_CI_CD.md §Qodana, D99 and D100) ---
|
||||
# The native report runs ReSharper's C++ engine, and with it the clang-tidy checks and clang diagnostics that engine
|
||||
# bundles (the keys that say clang_tidy). The native code is built by MSVC alone, with /W4 /WX; what clang says about
|
||||
# code it never compiles is read here as advice. An inspection is off only where it argues with a choice this project
|
||||
# made, and each line says which; everything else the report found was fixed.
|
||||
[src/native/**.{cpp,h,inl}]
|
||||
# Where the compiler pads a struct. Information, not a fault: the layouts that matter are asserted (static_assert on
|
||||
# sizes and offsets in fl_shm.h, and the mirror test against fl-layout-dump).
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_padded_highlighting = none
|
||||
# MSVC's own keywords - __try/__except (rule 5's guard around every hook body), __declspec, __stdcall. This code is
|
||||
# built by MSVC and by nothing else.
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_language_extension_token_highlighting = none
|
||||
# A function looked up by name - GetProcAddress, vkGetInstanceProcAddr, a vtable slot - comes back as a pointer to
|
||||
# another function type and is cast to its real one: that is the API. Through void* is how the cast says it is meant.
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_cast_function_type_strict_highlighting = none
|
||||
resharper_cpp_clang_tidy_bugprone_casting_through_void_highlighting = none
|
||||
# Memory read as something else - a COM object as its vtable, a relay's bytes as an address - says reinterpret_cast,
|
||||
# also where static_cast from void* would compile.
|
||||
resharper_cpp_reinterpret_cast_from_void_ptr_highlighting = none
|
||||
# It proposes std::cmp_less for a comparison whose sides differ in sign. The comparisons it found cast one side
|
||||
# explicitly, and the compiler's own sign warnings (C4018, C4388, C4389) are errors in this build.
|
||||
resharper_cpp_clang_tidy_modernize_use_integer_sign_comparison_highlighting = none
|
||||
# A `default:` under a switch that names every enumerator is deliberate: a value outside the enumeration - a corrupt
|
||||
# one, a future one - takes the refusing arm instead of falling out of the switch.
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_covered_switch_default_highlighting = none
|
||||
# "Not eliding copy on return": a verdict returned from a const local is copied. It is a few words wide.
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_nrvo_highlighting = none
|
||||
# A type that owns a handle deletes its copies or declares none; the moves are then not generated either, which is
|
||||
# what is wanted. Four more `= delete` lines would say nothing the destructor did not.
|
||||
resharper_cpp_clang_tidy_cppcoreguidelines_special_member_functions_highlighting = none
|
||||
# An enumeration zero-initialised (`D3D_FEATURE_LEVEL got{}`) is an out parameter cleared before the call that fills it.
|
||||
resharper_cpp_clang_tidy_bugprone_invalid_enum_default_initialization_highlighting = none
|
||||
# An enumeration's width is part of a layout or of the atomic word it is stored in, not a size to be minimised.
|
||||
resharper_cpp_clang_tidy_performance_enum_size_highlighting = none
|
||||
# "Possibly unused #include": a file that calls std::memset includes <cstring>, also when <windows.h> already brought
|
||||
# it in. What it reported was of that kind, or a header named again inside a conditional block, but for two that
|
||||
# nothing used; those were removed.
|
||||
resharper_cpp_unused_include_directive_highlighting = none
|
||||
# A function another file calls by a declaration of its own (the harness's Hold* functions), an entry point the
|
||||
# loader calls by name (DllMain), a placeholder a target links: "can be made static" reads one file.
|
||||
resharper_cpp_use_internal_linkage_highlighting = none
|
||||
# "Can be made const": a parameter or a method through which the code acts on a device, a ring or a handle is not
|
||||
# const because the type system would allow it; and a local that is already const gains nothing from constexpr - for a
|
||||
# std::string it would hold only while the text fits the small-string buffer.
|
||||
resharper_cpp_parameter_may_be_const_ptr_or_ref_highlighting = none
|
||||
resharper_cpp_member_function_may_be_const_highlighting = none
|
||||
resharper_cpp_variable_can_be_made_constexpr_highlighting = none
|
||||
# THE ENGINE MISREADS THESE. (1) `std::atomic_ref<T>{x}.fetch_or(bit)` is reported as an expression without side
|
||||
# effects; the side effect is the call. (2) A Win32, D3D12 or ffx-api structure is zero-initialised and then filled
|
||||
# field by field - the reserved fields must stay zero - and is handed to the API by its address or its header's: the
|
||||
# engine reports the initialiser as always rewritten and the fields as assigned and never used. (3) A test of a
|
||||
# constexpr function (`Check(F(a) == b && G(a) == c, ...)`) has the engine evaluate it and call one side redundant.
|
||||
resharper_cpp_expression_without_side_effects_highlighting = none
|
||||
resharper_cpp_initialized_value_is_always_rewritten_highlighting = none
|
||||
resharper_cpp_assigned_value_is_never_used_highlighting = none
|
||||
resharper_cpp_redundant_boolean_expression_argument_highlighting = none
|
||||
# Proposals to restate working code in a newer idiom - a range-for, std::ranges, any_of, starts_with, std::min, a raw
|
||||
# string, an if with an initialiser, emplace_back. The native code is written to be read beside the hook path: an
|
||||
# index and a plain loop, the same in the guard, its tests and the probes.
|
||||
resharper_cpp_clang_tidy_modernize_loop_convert_highlighting = none
|
||||
resharper_cpp_clang_tidy_modernize_use_ranges_highlighting = none
|
||||
resharper_cpp_use_range_algorithm_highlighting = none
|
||||
resharper_cpp_clang_tidy_readability_use_anyofallof_highlighting = none
|
||||
resharper_cpp_clang_tidy_modernize_use_starts_ends_with_highlighting = none
|
||||
resharper_cpp_clang_tidy_readability_use_std_min_max_highlighting = none
|
||||
resharper_cpp_clang_tidy_modernize_raw_string_literal_highlighting = none
|
||||
resharper_cpp_clang_tidy_modernize_use_emplace_highlighting = none
|
||||
resharper_cpp_clang_tidy_modernize_return_braced_init_list_highlighting = none
|
||||
resharper_cpp_use_associative_contains_highlighting = none
|
||||
resharper_cpp_too_wide_scope_highlighting = none
|
||||
resharper_cpp_if_can_be_replaced_by_constexpr_if_highlighting = none
|
||||
|
||||
# A structure Windows defines and this SDK's headers do not give (RTL_PROCESS_MODULE_INFORMATION,
|
||||
# PROCESS_MEMORY_COUNTERS_EX2), and a test's stand-in for a Vulkan dispatchable object, are declared field for field:
|
||||
# the fields nothing names are what puts the others at their offsets.
|
||||
[src/native/{FrameLedger.Injector/src/fl_guard_sources.cpp,FrameLedger.ProcessStats/src/fl_process_stats.cpp,tools/fl-probe-guard/main.cpp,tests/vklayer_test.cpp}]
|
||||
resharper_cpp_declarator_never_used_highlighting = none
|
||||
|
||||
# fl::patch::Install takes its hook engine as a template parameter and calls Create / Enable / Disable on it. The
|
||||
# test's two stand-in engines are used that way and no other, which ReSharper's "never used" does not follow through a
|
||||
# dependent call: six reports, one per member (Qodana, 2026-11-12). The members are the test.
|
||||
[src/native/tests/unhook_inline_test.cpp]
|
||||
resharper_cpp_declarator_never_used_highlighting = none
|
||||
|
||||
# The linter's compiler, not the build's: NVAPI's header makes NvU32 `unsigned int` under clang and `unsigned long`
|
||||
# under MSVC, which is the compiler that builds this probe - and `%lu` is right for it.
|
||||
[src/native/tools/fl-probe-nvapi/main.cpp]
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_format_highlighting = none
|
||||
|
||||
# --- the probes, the harness and the tests ---
|
||||
[src/native/{tools,tests}/**.{cpp,h}]
|
||||
# printf, fprintf, fputs, fclose: a probe prints what it found and a test prints why it failed; neither has anything
|
||||
# to do about a failed write to its own console.
|
||||
resharper_cpp_clang_tidy_cert_err33_c_highlighting = none
|
||||
# atoi on the harness's own arguments, which its tests write: a number that does not parse is 0, and the run that
|
||||
# asked for it fails on its own assertion.
|
||||
resharper_cpp_clang_tidy_bugprone_unchecked_string_to_number_conversion_highlighting = none
|
||||
# A printf-shaped helper (`Note(fmt, ...)`): the attribute clang proposes is not MSVC's, and a parameter pack would
|
||||
# be a second implementation of printf.
|
||||
resharper_cpp_clang_tidy_modernize_avoid_variadic_functions_highlighting = none
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_missing_format_attribute_highlighting = none
|
||||
# `&pointer` handed to an API that takes `void*` (ReadProcessMemory, a memcpy of a vtable slot, a Streamline array of
|
||||
# constants): the conversion is the call's own.
|
||||
resharper_cpp_clang_tidy_bugprone_multi_level_implicit_pointer_conversion_highlighting = none
|
||||
# A test builds a handle or an address from a number, on purpose: a fake one, or one read from another process.
|
||||
resharper_cpp_clang_tidy_performance_no_int_to_ptr_highlighting = none
|
||||
# A macro that pastes its argument into a name (FL_DEV(vkGetDeviceQueue)) cannot put it in parentheses.
|
||||
resharper_cpp_clang_tidy_bugprone_macro_parentheses_highlighting = none
|
||||
# A test's fixture: a global with a std::string in it, a memcpy into a byte buffer that is not a string, two strings
|
||||
# added in an assertion's message.
|
||||
resharper_cpp_clang_tidy_bugprone_throwing_static_initialization_highlighting = none
|
||||
resharper_cpp_clang_tidy_bugprone_not_null_terminated_result_highlighting = none
|
||||
resharper_cpp_clang_tidy_performance_inefficient_string_concatenation_highlighting = none
|
||||
# layout_test checks facts the compiler already knows - a constant's length, a bit-field's range - at run time, so
|
||||
# that a failure prints which one: the branch that cannot be taken is the test passing.
|
||||
resharper_cpp_unreachable_code_highlighting = none
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_unreachable_code_highlighting = none
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_tautological_value_range_compare_highlighting = none
|
||||
|
||||
# --- CODE LOADED INTO A GAME: the Overlay, the Vulkan layer, the shared-memory headers ---
|
||||
# D100: here only a defect is fixed, in a pull request of its own with the hook's overhead measured (rule 5,
|
||||
# 14_TESTING §Hook overhead). The report found none. What it did say about these files, each kept as it is:
|
||||
[src/native/{FrameLedger.Overlay,FrameLedger.VkLayer,FrameLedger.Shm}/**.{cpp,h,inl}]
|
||||
# Arms with the same body are different cases, each with its own comment saying why it reads as it does.
|
||||
resharper_cpp_clang_tidy_bugprone_branch_clone_highlighting = none
|
||||
# MinHook's MH_ALL_HOOKS is NULL, by its header.
|
||||
resharper_cpp_zero_constant_can_be_replaced_with_nullptr_highlighting = none
|
||||
# Kept on purpose, each with its reason beside it in dllmain.cpp: a retired enumerator whose bit must not be reused;
|
||||
# slSetTag, deprecated by a header whose replacement no measured module exports.
|
||||
resharper_cpp_enumerator_never_used_highlighting = none
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_deprecated_declarations_highlighting = none
|
||||
|
||||
# DEAD CODE, FOUND AND NOT REMOVED: nothing calls dllmain.cpp's LogNoteW. D100 changes code loaded into a game for
|
||||
# a defect only, so taking it out is the owner's to order (HANDOFF, the native report's section) and not this
|
||||
# report's to do. Until then this one file is not read for an unused function. Remove this section with it.
|
||||
[src/native/FrameLedger.Overlay/src/dllmain.cpp]
|
||||
resharper_cpp_declarator_never_used_highlighting = none
|
||||
resharper_cpp_clang_tidy_clang_diagnostic_unused_function_highlighting = none
|
||||
|
||||
# The guard's rule matcher, which the Overlay compiles too. ResolveTolerance clears its out parameter with memset, as
|
||||
# ResetRules does: a Tolerance is flags with default member initialisers, which is all "non-trivially default
|
||||
# constructible" means here, and zero is what those initialisers say.
|
||||
[src/native/FrameLedger.Injector/{src/fl_ac_rules.cpp,include/fl_ac_rules.h}]
|
||||
resharper_cpp_clang_tidy_bugprone_raw_memory_call_on_non_trivial_type_highlighting = none
|
||||
+21
-117
@@ -1,31 +1,28 @@
|
||||
# Qodana (owner decisions D93, 2026-11-10, and D99, 2026-11-11; docs/13_CI_CD.md §Qodana).
|
||||
# Qodana (owner decision D93, 2026-11-10; docs/13_CI_CD.md §Qodana).
|
||||
#
|
||||
# JetBrains' template for the Qodana Scan action, changed where FrameLedger differs
|
||||
# and each change said here:
|
||||
#
|
||||
# - The linter is Qodana for .NET (Rider's engine) in NATIVE mode, on a Windows
|
||||
# runner: the projects target Windows, and the linter then builds and loads them
|
||||
# with the SDK this job installs from global.json - no container, and no
|
||||
# EnableWindowsTargeting. qodana.yaml names the linter and the mode; nothing is
|
||||
# passed as an action argument. (Until beta.37 this was the Community linter in a
|
||||
# Linux container, the one Linux job this repository had.)
|
||||
# - The action is pinned to a commit, as every action that is not GitHub's own is
|
||||
# here.
|
||||
# - The linter is Qodana Community for .NET (qodana.yaml names it and says why): a
|
||||
# Linux container, which is why this job alone runs on ubuntu-latest in a
|
||||
# Windows-only project. EnableWindowsTargeting lets the .NET SDK there build and
|
||||
# load projects whose target is Windows; it is passed to the container rather than
|
||||
# written into Directory.Build.props, because no build of the product is meant to
|
||||
# run anywhere but Windows.
|
||||
# - The action is pinned to a commit (v2026.2.2, the newest; the template names
|
||||
# v2026.1), as every action that is not GitHub's own is here.
|
||||
# - Permissions are the ones the job uses: it reads the repository, writes a check
|
||||
# run with the annotations and one comment on the pull request. The template's
|
||||
# `contents: write` is for pushing quick-fixes, which this job never does.
|
||||
# - A workflow of its own, as JetBrains advises, and ADVISORY: `main`'s required
|
||||
# contexts stay `check` and the two `analyze` jobs. A problem Qodana finds, a
|
||||
# Qodana Cloud outage or a lapsed licence is a red job beside a green `check`,
|
||||
# never a blocked merge.
|
||||
# - Two jobs, two reports (D99): `managed` reads the solution - the C#, the XAML and
|
||||
# what Rider's plugins read around it - and reports to the Qodana Cloud project
|
||||
# `frameledger`; `native` reads the C++ of src/native through a Visual Studio
|
||||
# solution CMake generates for it, with settings of its own (qodana-native.yaml),
|
||||
# and reports to `frameledger-cpp`. Neither reads what the other does. The pull
|
||||
# request's comment and annotations are the managed job's alone.
|
||||
# contexts stay `check` and the two `analyze` jobs. A problem Qodana finds, or a
|
||||
# Qodana Cloud outage, is a red job beside a green `check`, never a blocked merge.
|
||||
# - `main` only: the `alpha` branch is main's source under another release line
|
||||
# (docs/13_CI_CD.md §The alpha line), and main's is what is analysed.
|
||||
# - INTERIM since beta.37 (D94, 2026-11-11): main builds on .NET 11, which the
|
||||
# linter's image does not carry (SDKs 8 to 10), so qodana.yaml's `bootstrap`
|
||||
# installs the SDK global.json names into the container first. The Ultimate
|
||||
# linter's pull request replaces this job with one on Windows.
|
||||
|
||||
name: Qodana
|
||||
|
||||
@@ -43,8 +40,7 @@ concurrency:
|
||||
cancel-in-progress: true
|
||||
|
||||
jobs:
|
||||
managed:
|
||||
name: Qodana (managed)
|
||||
qodana:
|
||||
# A pull request from this repository, or a push or a dispatch. QODANA_TOKEN
|
||||
# reaches neither a fork's pull request nor Dependabot's, and their token cannot
|
||||
# write the check run or the comment.
|
||||
@@ -52,7 +48,7 @@ jobs:
|
||||
github.event_name != 'pull_request' ||
|
||||
(github.event.pull_request.head.repo.full_name == github.repository &&
|
||||
github.event.pull_request.user.login != 'dependabot[bot]')
|
||||
runs-on: windows-latest
|
||||
runs-on: ubuntu-latest
|
||||
timeout-minutes: 60
|
||||
permissions:
|
||||
contents: read
|
||||
@@ -68,111 +64,19 @@ jobs:
|
||||
# A full history is required for pull request analysis.
|
||||
fetch-depth: 0
|
||||
|
||||
# Native mode runs the linter in this job's environment, so the SDK it loads
|
||||
# the projects with is this one. No MSVC step here on purpose: it exports
|
||||
# Platform=x64, which MSBuild reads as a solution platform (build.ps1's
|
||||
# Clear-VcxprojPlatform).
|
||||
- name: Set up .NET
|
||||
uses: actions/setup-dotnet@v6
|
||||
with:
|
||||
global-json-file: global.json
|
||||
|
||||
# Restored only: `check` saves this cache, under the same key.
|
||||
- name: Restore the NuGet cache
|
||||
uses: actions/cache/restore@v6
|
||||
with:
|
||||
path: ~/.nuget/packages
|
||||
key: nuget-${{ runner.os }}-${{ hashFiles('**/Directory.Packages.props', 'global.json') }}
|
||||
restore-keys: nuget-${{ runner.os }}-
|
||||
|
||||
# Built before it is inspected: a build that fails is then one red step with
|
||||
# the compiler's own message, not a report of thousands of unresolved symbols.
|
||||
# The native DLLs are absent here, so the .targets that copy them warn and the
|
||||
# build goes on, as on a fresh clone.
|
||||
- name: Build what the linter loads
|
||||
shell: pwsh
|
||||
run: |
|
||||
dotnet build FrameLedger.slnx -c Release
|
||||
if ($LASTEXITCODE -ne 0) { throw 'the build failed' }
|
||||
|
||||
# pr-mode false: the whole solution every time, so a pull request and `main`
|
||||
# are judged by the same list. upload-result: the SARIF and the linter's log
|
||||
# as an artifact of the run, for a reader with no Qodana Cloud account.
|
||||
# Caches are saved from `main` only (a pull request reads them), under keys of
|
||||
# this job's own: one per branch would crowd the repository's cache quota,
|
||||
# which NuGet's share.
|
||||
# Caches are saved from `main` only (a pull request reads them): one per
|
||||
# branch would crowd the repository's cache quota, which NuGet's share.
|
||||
- name: Qodana Scan
|
||||
uses: JetBrains/qodana-action@3e8d76ff0e0241618abd808682f426afe84bab3f # v2026.2.2
|
||||
with:
|
||||
pr-mode: false
|
||||
upload-result: true
|
||||
artifact-name: qodana-report
|
||||
cache-default-branch-only: true
|
||||
primary-cache-key: qodana-managed-${{ github.ref_name }}-${{ github.sha }}
|
||||
additional-cache-key: qodana-managed-main
|
||||
env-vars-to-linter: EnableWindowsTargeting
|
||||
env:
|
||||
QODANA_TOKEN: ${{ secrets.QODANA_TOKEN }}
|
||||
QODANA_ENDPOINT: 'https://qodana.cloud'
|
||||
|
||||
native:
|
||||
name: Qodana (native)
|
||||
# The same condition as `managed`, for the same reason: QODANA_TOKEN_NATIVE
|
||||
# reaches neither a fork's pull request nor Dependabot's.
|
||||
if: >-
|
||||
github.event_name != 'pull_request' ||
|
||||
(github.event.pull_request.head.repo.full_name == github.repository &&
|
||||
github.event.pull_request.user.login != 'dependabot[bot]')
|
||||
runs-on: windows-latest
|
||||
timeout-minutes: 60
|
||||
# No annotations and no comment from this job (below), so it writes nothing.
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
steps:
|
||||
- uses: actions/checkout@v7
|
||||
with:
|
||||
ref: ${{ github.event.pull_request.head.sha }}
|
||||
fetch-depth: 0
|
||||
|
||||
# global.json sits above the solution, and the linter resolves it.
|
||||
- name: Set up .NET
|
||||
uses: actions/setup-dotnet@v6
|
||||
with:
|
||||
global-json-file: global.json
|
||||
|
||||
# The Visual Studio generator finds the toolset itself: no MSVC step. Configure
|
||||
# fetches MinHook, Catch2 and jsmn into the build tree, as the gate's does.
|
||||
- name: Generate the solution and the one generated header
|
||||
shell: pwsh
|
||||
working-directory: src/native
|
||||
run: |
|
||||
cmake --version
|
||||
cmake --preset x64-vs-analysis
|
||||
if ($LASTEXITCODE -ne 0) { throw 'cmake configure failed' }
|
||||
cmake --build --preset x64-vs-analysis --target fl_ac_floor_gen
|
||||
if ($LASTEXITCODE -ne 0) { throw 'generating the blocklist floor failed' }
|
||||
if (-not (Test-Path ../../build/native/x64-vs-analysis/FrameLedgerNative.slnx)) {
|
||||
Get-ChildItem ../../build/native/x64-vs-analysis -Filter 'FrameLedgerNative.*' | ForEach-Object { Write-Host $_.Name }
|
||||
throw 'CMake did not write FrameLedgerNative.slnx (qodana-native.yaml names it)'
|
||||
}
|
||||
|
||||
# A report of its own: its own settings file, results folder, artifact, cache
|
||||
# keys and Qodana Cloud project. The pull request's comment and annotations are
|
||||
# the managed job's; a second job of the same linter would overwrite them.
|
||||
- name: Qodana Scan
|
||||
uses: JetBrains/qodana-action@3e8d76ff0e0241618abd808682f426afe84bab3f # v2026.2.2
|
||||
with:
|
||||
args: --config qodana-native.yaml
|
||||
results-dir: ${{ runner.temp }}/qodana-native/results
|
||||
cache-dir: ${{ runner.temp }}/qodana-native/caches
|
||||
pr-mode: false
|
||||
upload-result: true
|
||||
artifact-name: qodana-report-native
|
||||
cache-default-branch-only: true
|
||||
primary-cache-key: qodana-native-${{ github.ref_name }}-${{ github.sha }}
|
||||
additional-cache-key: qodana-native-main
|
||||
post-pr-comment: false
|
||||
use-annotations: false
|
||||
env:
|
||||
QODANA_TOKEN: ${{ secrets.QODANA_TOKEN_NATIVE }}
|
||||
QODANA_ENDPOINT: 'https://qodana.cloud'
|
||||
EnableWindowsTargeting: 'true'
|
||||
+3
-6
@@ -9,7 +9,7 @@ barrier. It is written for the person who has just met one; the details for deve
|
||||
FrameLedger is a desktop program: its own window, its dialogs, its document windows, the icon by the clock and the
|
||||
notices Windows shows for it. It draws nothing inside a game, so it cannot make a game itself any easier to use.
|
||||
|
||||
*Beta software: this page describes version 0.1.0-beta.49. In the app: Help ▸ Accessibility.*
|
||||
*Beta software: this page describes version 0.1.0-beta.37. In the app: Help ▸ Accessibility.*
|
||||
|
||||
## What FrameLedger aims for
|
||||
|
||||
@@ -29,7 +29,7 @@ notices Windows shows for it. It draws nothing inside a game, so it cannot make
|
||||
|
||||
| Keys | What they do |
|
||||
|---|---|
|
||||
| **Ctrl+1** … **Ctrl+5** (also with the numeric keypad) | Open Dashboard, Games, Compare, Logs and Settings, and move the keyboard into that page; a screen reader hears its title. **Ctrl+6** opens Advanced the same way while Advanced metrics is switched on, and does nothing while it is off. |
|
||||
| **Ctrl+1** … **Ctrl+5** (also with the numeric keypad) | Open Dashboard, Games, Compare, Logs and Settings, and move the keyboard into that page; a screen reader hears its title. |
|
||||
| **Alt** or **F10**, then the arrow keys and **Enter** | Move to the menus. **Alt** with a menu's underlined letter opens it (*File*, *Tools*, *Help* in English). |
|
||||
| **Tab** and **Shift+Tab** | Move through a page or a dialog in reading order. |
|
||||
| The **arrow keys**, **Home**, **End**, **Page Up**, **Page Down** | Move inside a list or a table — a game's sessions, the games list, the Compare list, the import checklist. |
|
||||
@@ -96,7 +96,7 @@ from the same translations. The documents — the user guide, this page, the leg
|
||||
into a screen; every text reads against its background in both themes and after a theme switch, and under Windows'
|
||||
four contrast themes and two edited ones is drawn in the theme's own colours at 4.5:1 or better; **Esc** closes the
|
||||
open dialog without an answer, and a dialog gives the focus back; **Ctrl+1** … **Ctrl+5** open the pages in their
|
||||
order and move the keyboard into them, and **Ctrl+6** the Advanced page only while its option is on; a page slides in only while Windows' animation effects are on; the program
|
||||
order and move the keyboard into them; a page slides in only while Windows' animation effects are on; the program
|
||||
declares it follows each screen's scaling.
|
||||
- **By hand**: the owner's pass of 2026-11-09 above, repeated for each release that changes a screen.
|
||||
- **Not tested yet**: NVDA, JAWS, Voice Access, touch, Windows 10, and other people's PCs. They should work through the
|
||||
@@ -107,9 +107,6 @@ from the same translations. The documents — the user guide, this page, the leg
|
||||
|
||||
Each one with what to do instead. A barrier that is not on this list is worth reporting.
|
||||
|
||||
- **The Advanced page's "This PC" does not announce its readings as they change.** They change every second; a
|
||||
screen reader reads the table when you move through it, and each row says its reading, its value and the time it
|
||||
was read at.
|
||||
- **A chart's points cannot be read one by one.** A screen reader hears the chart's name and where its numbers are:
|
||||
a session's figures and *Statistics per series* in its summary, the table under the Compare chart, the Sessions table
|
||||
and the list of changes under a trend chart, and **File ▸ Export ▸ Session CSV** or **Session JSON**.
|
||||
|
||||
@@ -35,70 +35,12 @@ numeric core and does not move; the heading is the full version — corrected 20
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
|
||||
- **For developers: the arithmetic of controller statistics, with nothing reading a device yet** (D155–D163, the
|
||||
owner's decisions of 2026-11-14; `docs/21_INPUT_DEVICES.md`, `docs/03_METRICS.md` §Input). `FrameLedger.Domain.Input`
|
||||
says whether an XInput state or a DualSense report is a pad in use and what its battery is, adds a battery's readings
|
||||
up, counts switches, and decides when two entries are one pad seen twice; `Application.Input` holds one session's
|
||||
slices and turns them into a reading a second; `InputSessionBuilder` turns a session's readings into its totals, its
|
||||
controllers as JSON and its timeline. A telemetry sample can carry a reading; none does. **Every byte and reading
|
||||
under test was written by hand — no report from a real controller has passed through this code.**
|
||||
|
||||
### Changed
|
||||
|
||||
- **Advanced metrics is closed: the ten readings that were "being studied" are now "not read", with the reason**
|
||||
(D154, the owner's decision). What a game sets and asks through Streamline's own functions for a feature — DLSS
|
||||
frame generation's options and state, the video memory DLSS estimates for itself, the options of ray
|
||||
reconstruction, Image Scaling and Dynamic Vibrance, the PC-latency markers — is reached only by handing the game
|
||||
a function of FrameLedger's in place of Streamline's, which is refused. The *Sources* list says so, in English,
|
||||
Vietnamese and Japanese, and the guide no longer says a later release reads more. Nothing that was read stops
|
||||
being read.
|
||||
|
||||
- **The two lines of the graphics card's time say what each is, not which holds the other** (D152, the owner's
|
||||
decision). *GPU active render (idle time excluded)* and *GPU render, start to end (idle time included)* are now
|
||||
*GPU active render (the driver's own figure)* and *GPU render (between the driver's start and end marks)*, in
|
||||
English, Vietnamese and Japanese, and the guide says why: in Cyberpunk 2077 without frame generation the
|
||||
driver's active time is longer than its two marks are apart. The numbers are unchanged.
|
||||
|
||||
- **The guide's page on Advanced metrics says what two of the driver's switches mean** (`guide/12`): the latency
|
||||
report is there in a game that has Reflex built in, whether Reflex is on or off in its menu; `bUseGameSleep`
|
||||
says the game calls Reflex's sleep — NVIDIA asks for that even with Reflex off — and `bLowLatencyMode` is the
|
||||
one that says the mode is on; frame generation needs Reflex, not the reverse. From NVIDIA's Streamline guide
|
||||
for Reflex, and from the owner's ten sessions on 0.1.0-beta.49.
|
||||
|
||||
### Documentation
|
||||
|
||||
- **Owner-only item 47 was run and read** (`docs/HANDOFF.md`): in Cyberpunk 2077 without frame generation the
|
||||
driver's active GPU time is longer than its own two marks are apart on 4 917 of 5 394 frames (1 849 µs beside
|
||||
1 571 µs) and on none of 129 900 frames in five other games — the difference is the driver's; samples without a
|
||||
report are now confined to a game's start; a session with the option off has no latency line; and the stop of
|
||||
D141 fired in a real game for the first time (Kingdom Come: Deliverance II, one call of 5.3 ms while it
|
||||
started).
|
||||
- **Streamline's programming guides for Reflex and for DLSS Ray Reconstruction (2.14.16) read against the code**
|
||||
(`docs/spike-notes/30-reflex-latency.md`, *Added 2026-11-14*). Ray reconstruction was already measured the way
|
||||
the guide describes; two comments in the Overlay's source and one line of `17_HOOK_ENGINE` said super
|
||||
resolution and ray reconstruction run together, and they do not. `03_METRICS` and `05_DETECTION` no longer
|
||||
promise "PC latency as reported by Reflex" (D147). No code changed: comments only.
|
||||
|
||||
## Releases
|
||||
|
||||
Newest first. Each file holds that release's section exactly as it stood here.
|
||||
|
||||
| Version | Date | Notes |
|
||||
|---|---|---|
|
||||
| `0.1.0-beta.49` | 2026-11-14 | [`docs/changelog/0.1.0-beta.49.md`](docs/changelog/0.1.0-beta.49.md) |
|
||||
| `0.1.0-beta.48` | 2026-11-14 | [`docs/changelog/0.1.0-beta.48.md`](docs/changelog/0.1.0-beta.48.md) |
|
||||
| `0.1.0-beta.47` | 2026-11-14 | [`docs/changelog/0.1.0-beta.47.md`](docs/changelog/0.1.0-beta.47.md) |
|
||||
| `0.1.0-beta.46` | 2026-11-13 | [`docs/changelog/0.1.0-beta.46.md`](docs/changelog/0.1.0-beta.46.md) |
|
||||
| `0.1.0-beta.45` | 2026-11-12 | [`docs/changelog/0.1.0-beta.45.md`](docs/changelog/0.1.0-beta.45.md) |
|
||||
| `0.1.0-beta.44` | 2026-11-12 | [`docs/changelog/0.1.0-beta.44.md`](docs/changelog/0.1.0-beta.44.md) |
|
||||
| `0.1.0-beta.43` | 2026-11-12 | [`docs/changelog/0.1.0-beta.43.md`](docs/changelog/0.1.0-beta.43.md) |
|
||||
| `0.1.0-beta.42` | 2026-11-12 | [`docs/changelog/0.1.0-beta.42.md`](docs/changelog/0.1.0-beta.42.md) |
|
||||
| `0.1.0-beta.41` | 2026-11-12 | [`docs/changelog/0.1.0-beta.41.md`](docs/changelog/0.1.0-beta.41.md) |
|
||||
| `0.1.0-beta.40` | 2026-11-12 | [`docs/changelog/0.1.0-beta.40.md`](docs/changelog/0.1.0-beta.40.md) |
|
||||
| `0.1.0-beta.39` | 2026-11-11 | [`docs/changelog/0.1.0-beta.39.md`](docs/changelog/0.1.0-beta.39.md) |
|
||||
| `0.1.0-beta.38` | 2026-11-11 | [`docs/changelog/0.1.0-beta.38.md`](docs/changelog/0.1.0-beta.38.md) |
|
||||
| `0.1.0-alpha.4` | 2026-11-11 | [`docs/changelog/0.1.0-alpha.4.md`](docs/changelog/0.1.0-alpha.4.md) |
|
||||
| `0.1.0-beta.37` | 2026-11-11 | [`docs/changelog/0.1.0-beta.37.md`](docs/changelog/0.1.0-beta.37.md) |
|
||||
| `0.1.0-beta.36` | 2026-11-10 | [`docs/changelog/0.1.0-beta.36.md`](docs/changelog/0.1.0-beta.36.md) |
|
||||
|
||||
@@ -20,8 +20,6 @@ A C++ DLL (`FrameLedger.Overlay.dll`) is injected into games the user explicitly
|
||||
> **Amended 2026-10-03 (owner decision D38): the evidence moved from before the grant to its trial.** "≥ 2 successful Tier-1 sessions" above could never be met by a game blocked at add time — since beta.8 that is every blocked game — nor after a ledger reset. Asked with that, the owner chose: a grant needs no session; the first two hooked sessions under it are a trial, and any end during the trial (a crash, a safety unhook, a floor stop, a new finding, or a stored hooked session with no frames or an abnormal exit) ends the exception **for good** (`games.ac_exception_trial_failed_at`, schema 0017, never cleared). Every other condition above is unchanged, and so is the last sentence.
|
||||
3. **Never implement evasion.** No manual mapping, no PE header erasure, no thread hiding, no signature obfuscation, no unlinking from the PEB module list. Injection uses documented `LoadLibraryW`. The DLL keeps its real name, real exports, and version info. A performance tool must be *visible* to anti-cheat, not hidden from it. Any PR that makes FrameLedger harder to detect is rejected on principle.
|
||||
4. **Never read or write game memory outside our own hooks.** We read arguments passed to APIs we hooked and COM/handle objects we legitimately own. No pattern scanning for game internals, no reading player/entity state, no writing to game memory. Ever.
|
||||
|
||||
> **Amended 2026-11-13 (owner decision D132): a driver's read-only getter, with the device of the swap chain we hook.** Asked with this rule quoted, the owner ruled that calling NVIDIA's two latency getters (`NvAPI_D3D_GetLatency`, `NvAPI_D3D_GetSleepStatus`) with the device behind a swap chain the Overlay hooks is inside this rule: it reads the driver's report, not game memory, and writes nothing. ~~Nothing shipped does it yet~~ **Shipped since 0.1.0-beta.47 (owner decisions D136, D138–D141)**, after the spike on `hook-harness`, a stub and the installed driver (`spike-notes` §31): only while a session records Advanced metrics (no switch of its own), about once a second on the presenting thread, through an `nvapi64.dll` the game had loaded — one in the game's own folder is refused, and a fault or a call of 2 ms or more ends it until the game exits (`17_HOOK_ENGINE` §Calls the Overlay makes into a driver). **It is the only call of its kind; another needs a ruling of the same kind.** Getters only, never a setter, a marker or a sleep, and never a call that loads `nvapi64.dll` into a game.
|
||||
5. **The hook must never crash the game.** Every hook body: SEH-guarded, allocation-free, lock-free, no logging, no exceptions crossing the boundary. On repeated faults, self-disable (`17_HOOK_ENGINE` §Fault policy).
|
||||
6. **FPS display rule (product requirement):** wherever FPS is shown and Frame Generation is active, show *Native FPS*, *Displayed FPS*, and the FG factor together (`62 → 118 FPS (×1.9 FG)`). Never a single inflated number. See `docs/03_METRICS.md`.
|
||||
|
||||
@@ -75,12 +73,9 @@ RELEASE_LINE # `main`, or `alpha` on the alpha branch (D73, 20
|
||||
build.ps1 # the quality gate; CI runs this identical script
|
||||
SonarQube.Analysis.xml # SonarCloud's settings for ci.yml's sonarcloud job (D68, 2026-10-25; it replaced
|
||||
.config/dotnet-tools.json # .sonarcloud.properties) and the scanner it runs — 13_CI_CD §SonarCloud
|
||||
qodana-native.yaml # the same for the native job: the C++ of src/native, through the Visual Studio solution
|
||||
# CMake writes for it (preset x64-vs-analysis), a report of its own (D99)
|
||||
qodana.yaml # Qodana's settings for the managed job of .github/workflows/qodana.yml (D93; Qodana for
|
||||
# .NET on the Ultimate licence since 2026-11-11, D99): the linter, the solution, a gate
|
||||
# of zero problems, and what is switched off that .editorconfig has no key for —
|
||||
# ReSharper's inspections are .editorconfig's resharper_* keys (D100) — 13_CI_CD §Qodana
|
||||
qodana.yaml # Qodana's settings for .github/workflows/qodana.yml (D93, 2026-11-10): the linter, the
|
||||
# solution, a gate of zero problems; the inspections' severities are .editorconfig's
|
||||
# resharper_* keys — 13_CI_CD §Qodana
|
||||
src/
|
||||
native/
|
||||
FrameLedger.Overlay/ # C++20 DLL injected into the game (hooks + ring writer + optional overlay)
|
||||
@@ -105,48 +100,7 @@ src/
|
||||
# composes it from, SessionEndReason, the census/NGX/marker facts;
|
||||
# and Recording/ since 2026-09-10 (PR-D): SessionRecorder,
|
||||
# SessionAggregator + FgLadder, SessionFinalizer, the .partial
|
||||
# writer and PartialRecovery, ExitStatusMapper, the crash policy;
|
||||
# and Advanced/ since 2026-11-11 (D101): AdvancedMetricCatalog, the one
|
||||
# list "Advanced metrics" reads - what is read, and what is not with the
|
||||
# reason (18_GPU_VENDOR_APIS §Advanced metrics) - and the value model
|
||||
# (AdvancedValue / AdvancedFact / AdvancedReading / AdvancedSnapshot) and
|
||||
# the port IAdvancedHardware. Infrastructure implements it: AdvancedHardwareHub
|
||||
# (one reader for the Agent, on its own thread, only while held - D107) over
|
||||
# NvapiAdvancedReader (the bridge's ABI 3) and LhmAdvancedReader (LhmGroups:
|
||||
# the card; as administrator with PawnIO the processor, memory and board -
|
||||
# never storage, D103). The Agent composes it since the switch, `telemetry.advanced`
|
||||
# (PR-5, 2026-11-11: off by default; on, a session holds the hub), and
|
||||
# Ipc/AdvancedMachineResponder answers GetAdvancedMachine from the hub's last
|
||||
# snapshot - each request is the page's hold on it (PR-6, D107). Recording/
|
||||
# AdvancedSessionBuilder stores what a session's samples carried (schema 0023:
|
||||
# machine_profiles + session_advanced, adv.* series with NaN for a gap, D102).
|
||||
# Train B (0.1.0-beta.40, D111): Capture/InGameAdvancedSampler turns the shared
|
||||
# memory's region 5 - what a hooked game told DLSS and FSR, read by the Overlay
|
||||
# only while the session asks (ICaptureObserver.WantsInGameAdvanced) - into session
|
||||
# facts and two adv.* series; reach `Game` in the catalog; no schema change.
|
||||
# Since 0.1.0-beta.43 also what the game tells Streamline each frame and how it
|
||||
# configures FSR frame generation, from two calls hooked only once Advanced has been
|
||||
# asked for; AdvancedInGameCall says of each: read, never called, or not hooked.
|
||||
# Since 0.1.0-beta.44 also what Streamline answers when the game asks about a
|
||||
# feature (its version, what it requires), from two more calls hooked the same
|
||||
# way; ~~a game asks while it starts, so "never called" is the usual answer there~~
|
||||
# (the games run since ask again later, and are read).
|
||||
# Since 0.1.0-beta.45 also whether Streamline says a feature is supported and
|
||||
# loaded, the game switching it, its resources allocated and freed and Streamline
|
||||
# shut down, from six more calls hooked the same way (D130); slInit is not hooked
|
||||
# and its entry says why (AdvancedReach.BeforeAttach, D129).
|
||||
# Since 0.1.0-beta.47 (train C, D136-D141) also what NVIDIA's driver reports about
|
||||
# a frame's stages - NOT an argument of a hooked call: the Overlay calls two
|
||||
# read-only getters of the driver itself (reach GameDriver); seven adv.* series
|
||||
# and one table, and AdvancedDriverRead says what became of the read.
|
||||
# Since 0.1.0-beta.48 (D142-D144) also two figures the driver works out itself, of
|
||||
# the same report - no further call: an entry of their own, nvapi.reflex.gpu_times,
|
||||
# two adv.* series; and the table lists every frame-generation multiplier seen.
|
||||
# Since 0.1.0-beta.49 (D148-D151) the Overlay also counts each frame of that report
|
||||
# by its GPU span and the driver's active time - for its native log ONLY
|
||||
# (LATENCY_FRAMES, a batch per state of the sleep status; nothing published or
|
||||
# stored); its watchdog's periodic tick is on a grid (fl_watchdog_tick.h), and
|
||||
# Recording/PendingInGameReadings keeps the reading that waits for a sample.
|
||||
# writer and PartialRecovery, ExitStatusMapper, the crash policy
|
||||
FrameLedger.Infrastructure/ # SQLite, shm reader, vendor APIs, injector interop, parsers,
|
||||
# and Capture/ (PR-C): ShmRingAttacher/ShmCaptureSink over the
|
||||
# reader, HeldProcessLivenessSource, TargetResolver (path only,
|
||||
@@ -169,9 +123,7 @@ src/
|
||||
# is built as of 2026-09-14 (PR-5 Games/Dashboard, PR-6 summary +
|
||||
# charts, PR-7 trend/compare, PR-8a Settings/safety notices/Logs/
|
||||
# --diag, PR-8b tray + the Agent's maintenance flags, PR-9 first run
|
||||
# + Legal Gate FR-11); Strings.resx en/vi/ja. The Advanced page
|
||||
# (2026-11-11, D101/D105: Pages/AdvancedPage, there and on Ctrl+6 only
|
||||
# while `telemetry.advanced` is on - 08_UI §Advanced). `--data-dir <copy>`
|
||||
# + Legal Gate FR-11); Strings.resx en/vi/ja. `--data-dir <copy>`
|
||||
# (beta.15, D52) = a VIEWER: no Agent started or contacted,
|
||||
# nothing on the PC changed, the profile's own folder refused
|
||||
FrameLedger.CaptureHost/ # UNSHIPPED, and since P2 PR-C (2026-09-09) a THIN SHELL: verbs,
|
||||
@@ -199,16 +151,7 @@ tools/ # accuracy-check, changelog-check, chokepoint-che
|
||||
# versioninfo-check, vklayer-blastradius, fps-impact-runbook,
|
||||
# wiki-build (beta.17: builds and checks the wiki; the wiki-check gate),
|
||||
# buildid-check (beta.18: the release's build id in the shipped natives),
|
||||
# docs-split-check (beta.24, D66: CHANGELOG/HANDOFF and their parts agree),
|
||||
# agent-cost (D110, 2026-11-11: a developer tool, not a gate - what the shipped
|
||||
# Agent costs per second of session, Advanced metrics off and on),
|
||||
# nvapi-readonly-check (D108, 2026-11-11: every NVAPI call of the bridge is on
|
||||
# nvapi-allowed-calls.txt, and none there writes or identifies; since beta.47 also
|
||||
# the Overlay - no NvAPI call by name, and the only interface ids it may name are
|
||||
# the two on overlay-nvapi-allowed.txt),
|
||||
# overlay-fields-check (D116, 2026-11-12: every member of a vendor's struct the
|
||||
# Overlay reads for Advanced metrics is in fl_adv_fields.h and on
|
||||
# overlay-allowed-fields.txt; a camera's position, axes and matrices nowhere)
|
||||
# docs-split-check (beta.24, D66: CHANGELOG/HANDOFF and their parts agree)
|
||||
# (six names added 2026-10-04)
|
||||
# (PowerShell). This line used to name three, one of which
|
||||
# — resx-audit — ~~does not exist~~ exists since 2026-09-13 with
|
||||
@@ -219,9 +162,6 @@ tools/ # accuracy-check, changelog-check, chokepoint-che
|
||||
# (--vulkan since #140, --opengl since #141)
|
||||
# fl-probe-* -> guard, hook profile, interposer, NVAPI, process
|
||||
# stats, signer, Vulkan layer; fl-baseline-probe;
|
||||
# and fl-probe-reflex (2026-11-13, D132: the spike of Reflex route D,
|
||||
# spike-notes §31 - unshipped, with a stand-in nvapi64.dll among the stubs;
|
||||
# built from the Overlay's own fl_reflex.h since beta.47);
|
||||
# vendor-stubs/ -> fixture DLLs with the vendors' export names
|
||||
rules/detection-rules.json # engine/platform/capability + anticheat blocklist
|
||||
guide/ # the user guide (beta.12, D44): ~~eight~~ short English pages for players, embedded in the
|
||||
@@ -238,13 +178,13 @@ Dependency direction: `App/Agent → Application → Domain`; **`Application →
|
||||
|
||||
## Coding conventions
|
||||
|
||||
**C# —** `Nullable enable`, `TreatWarningsAsErrors`, `AnalysisLevel latest-all`, file-scoped namespaces, Roslynator + Meziantou + VS Threading analyzers, `dotnet format` clean. Qodana reads the C# and the XAML in an advisory workflow of its own, with a gate of zero problems *(since 2026-11-10, D93; Qodana for .NET on the Ultimate licence since 2026-11-11, D99 — `13_CI_CD` §Qodana)*: fix what it reports, or switch the inspection off with the reason on the line above, **in the place the engine that raised it reads** *(D100)* — one of ReSharper's (C#, XAML, `.resx`, the C++) in `.editorconfig`; what has no key there (the hints as a severity, the Markdown and XML inspections, the files JetBrains' security rules were read in) in `qodana.yaml` — never anywhere else, never without a reason. A new file that starts a process fails `ProcessStartSitesTests`, and Qodana's security rule reports it: read what it starts and where the path and the arguments come from, then list it in the test, in `qodana.yaml` and in `13_CI_CD` §Qodana. Async suffixed `Async`, `ConfigureAwait(false)` off the UI. All user-visible strings from `.resx`. Timestamps UTC (unix-ms in SQLite); QPC ticks only inside the capture pipeline.
|
||||
**C# —** `Nullable enable`, `TreatWarningsAsErrors`, `AnalysisLevel latest-all`, file-scoped namespaces, Roslynator + Meziantou + VS Threading analyzers, `dotnet format` clean. Qodana Community for .NET (ReSharper's inspections) reads the C# and the XAML in an advisory workflow of its own, with a gate of zero problems *(since 2026-11-10, D93 — `13_CI_CD` §Qodana)*: fix what it reports, or switch the inspection off in `.editorconfig` with the reason beside it — never in `qodana.yaml`, never without one. Async suffixed `Async`, `ConfigureAwait(false)` off the UI. All user-visible strings from `.resx`. Timestamps UTC (unix-ms in SQLite); QPC ticks only inside the capture pipeline.
|
||||
|
||||
**C++ —** `clang-format` (LLVM base, 4-space, 120 col) enforced in CI. No STL containers that allocate in hook paths. No `std::mutex` in hook paths. `-D_HAS_EXCEPTIONS=0` in the Overlay target. Every hook entry point wrapped per the `FL_HOOK_GUARD` macro (`17_HOOK_ENGINE`). Static analysis: ~~`/analyze` + clang-tidy (`bugprone-*`, `cert-*`, `concurrency-*`)~~ CodeQL (`codeql.yml`, a required check); `/analyze` and clang-tidy are not configured *(corrected 2026-10-04)*. SonarCloud analyses the C++ too, from CMake's compilation database, in `ci.yml`'s advisory `sonarcloud` job *(since 2026-10-25, D68 — `13_CI_CD` §SonarCloud)*. Qodana reads it as well, in a report of its own *(since 2026-11-11, D99: ReSharper's C++ inspections and the clang-tidy checks they run, advisory, a gate of zero — `13_CI_CD` §Qodana)*: fix what it reports, or switch the inspection off in `.editorconfig` with the reason above it; **in code loaded into a game only a defect is fixed**, in a pull request of its own with the overhead measured *(D100)*.
|
||||
**C++ —** `clang-format` (LLVM base, 4-space, 120 col) enforced in CI. No STL containers that allocate in hook paths. No `std::mutex` in hook paths. `-D_HAS_EXCEPTIONS=0` in the Overlay target. Every hook entry point wrapped per the `FL_HOOK_GUARD` macro (`17_HOOK_ENGINE`). Static analysis: ~~`/analyze` + clang-tidy (`bugprone-*`, `cert-*`, `concurrency-*`)~~ CodeQL (`codeql.yml`, a required check); `/analyze` and clang-tidy are not configured *(corrected 2026-10-04)*. SonarCloud analyses the C++ too, from CMake's compilation database, in `ci.yml`'s advisory `sonarcloud` job *(since 2026-10-25, D68 — `13_CI_CD` §SonarCloud)*.
|
||||
|
||||
**Licence header —** every first-party source file (`.cs .cpp .h .inl .ps1 .xaml`) opens with two comment lines, `SPDX-License-Identifier: GPL-3.0-only` and `Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE` (beta.12, owner decision D45). GPLv3 §7 requires additional terms to be named in the source files, and `NOTICE` holds them — (b) preserve the notices, (c) mark modified versions, (e) no trademark rights in the name. `tools/notice-check.ps1` is a `build.ps1` gate; `-Fix` writes a missing header. `src/native/third_party/` is excluded.
|
||||
|
||||
**Struct mirroring —** ~~`FlFrameRecord`, `FlShmHandshake`, `FlWriterState` and `FlControlBlock`~~ `FlShmHandshake`, `FlWriterState`, `FlControlBlock`, `FlDisplayState` (layout 4, beta.10), `FlAdvancedState` (layout 5, 2026-11-11, Advanced metrics train B), `FlFrameRecord` and `FlTolerance` (D33, beta.9) each exist twice *(corrected 2026-10-04)*: `src/native/FrameLedger.Shm/include/fl_shm.h` / `fl_tolerance.h` (**normative**) and `src/FrameLedger.Shared/ShmLayout.cs` as `[StructLayout(LayoutKind.Sequential)]`. `ShmLayoutMirrorTests` asserts size and every field offset on both sides **against JSON emitted by ~~`tools/fl-layout-dump`~~ `src/native/tools/fl-layout-dump`**, never a transcribed table, and walks the field list in both directions so a field added on either side alone fails.
|
||||
**Struct mirroring —** ~~`FlFrameRecord`, `FlShmHandshake`, `FlWriterState` and `FlControlBlock`~~ `FlShmHandshake`, `FlWriterState`, `FlControlBlock`, `FlDisplayState` (layout 4, beta.10), `FlFrameRecord` and `FlTolerance` (D33, beta.9) each exist twice *(corrected 2026-10-04)*: `src/native/FrameLedger.Shm/include/fl_shm.h` / `fl_tolerance.h` (**normative**) and `src/FrameLedger.Shared/ShmLayout.cs` as `[StructLayout(LayoutKind.Sequential)]`. `ShmLayoutMirrorTests` asserts size and every field offset on both sides **against JSON emitted by ~~`tools/fl-layout-dump`~~ `src/native/tools/fl-layout-dump`**, never a transcribed table, and walks the field list in both directions so a field added on either side alone fails.
|
||||
|
||||
It also asserts **blittability** (`RuntimeHelpers.IsReferenceOrContainsReferences`), because offsets cannot see it: measured 2026-08-05, swapping the `fixed byte BuildId[32]` for this repo's own `[MarshalAs(ByValTStr)] string` idiom keeps `Marshal.SizeOf` at 64 and every offset correct while `Unsafe.SizeOf` collapses to **40** — a mirror that passes the obvious checks and cannot be read out of a memory-mapped view.
|
||||
|
||||
|
||||
+6
-103
@@ -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.49.*
|
||||
*Beta software: this page describes version 0.1.0-beta.37.*
|
||||
|
||||
## Games it will not measure
|
||||
|
||||
@@ -51,11 +51,6 @@ shown is recorded too, from outside the game. ([Capture](docs/04_CAPTURE.md))
|
||||
game). Unity's crash handler and Chromium's `crashpad_handler` start with every game that has them, so their presence
|
||||
says nothing. Sessions recorded before 0.1.0-beta.14 keep how they were stored — a few of them may read *crashed*
|
||||
because Windows logged a memory report about the game. ([details](docs/04_CAPTURE.md))
|
||||
- **A game that faults while it is closing can read *ended normally* in a session measured from inside the game.**
|
||||
FrameLedger looks for Windows' crash report when it saves the session, and for such a session that is before
|
||||
Windows has written it; the same fault in a session that was not measured from inside reads *crashed*. Seen on one
|
||||
game whose graphics-driver library faults at every exit, measured or not (2026-11-12), and on a second whose
|
||||
Steam crash handler faults at every measured exit. Not changed yet.
|
||||
|
||||
## Frame rate and frame generation
|
||||
|
||||
@@ -95,9 +90,7 @@ shown is recorded too, from outside the game. ([Capture](docs/04_CAPTURE.md))
|
||||
same games as *Render → output resolution* in the accuracy statement; elsewhere it says it was not measured.
|
||||
- The upscaler is read from the game's calls: DLSS and NIS through NVIDIA Streamline, and FSR through AMD's
|
||||
FidelityFX libraries. **Intel XeSS is not read** (its licence forbids it), FSR 2 and upscalers built into the
|
||||
game are not identified — Cyberpunk 2077's FSR 2.1 is one: its sessions say "unknown" beside a measured render
|
||||
size — and Vulkan and OpenGL games read N/A. A game that sends FSR upscaling through two unrelated libraries in
|
||||
one run is counted from the first alone (none is known). Where no hook saw DLSS but the NVIDIA driver
|
||||
game are not identified, and Vulkan and OpenGL games read N/A. Where no hook saw DLSS but the NVIDIA driver
|
||||
reports it, the page says it is the driver's report.
|
||||
- **The quality mode** (Quality, Balanced, DLAA, …) is shown only when it is known: the NVIDIA App's override
|
||||
where the NVIDIA driver reports it applied (marked *· NVIDIA App*, since 0.1.0-beta.24), or the mode the game
|
||||
@@ -124,17 +117,8 @@ shown is recorded too, from outside the game. ([Capture](docs/04_CAPTURE.md))
|
||||
- **Ray tracing** is *Yes*, *No* or *N/A* — measured from the game's ray-tracing calls on Direct3D 12, and
|
||||
N/A where FrameLedger could not look. **Path tracing is never stated as a fact**: there is no API signal
|
||||
for it. You can correct any of these by hand, and your correction is labelled as yours.
|
||||
- HDR output, end-to-end latency (click to screen), the video-memory budget Windows gives a game, and
|
||||
shader-compilation stutter are **not measured yet** — they read N/A. ([Accuracy](legal/ACCURACY.md))
|
||||
- **NVIDIA's own latency report** is read only with *Advanced metrics* on, only on an NVIDIA card, only in a
|
||||
Direct3D 12 game that uses NVIDIA Reflex: how long the driver says each stage of a frame took, about once a
|
||||
second. They are the driver's numbers, not FrameLedger's measurement. **The stages overlap and do not add up to
|
||||
the total**, and the graphics card's stage includes the time the card waited — in one game it is longer than the
|
||||
whole frame; the driver's own figure for the card's active time is shown beside it where the driver gives one.
|
||||
One point is one reading, drawn at the sample that carried it — up to a second after it was taken; with the
|
||||
sensor interval set above one second, some readings are not stored.
|
||||
FrameLedger asks the driver for them from inside the game; a read that is slow or faults is switched off until the game is closed, and the session says so.
|
||||
([Advanced metrics](guide/12-advanced-metrics.md))
|
||||
- HDR output, NVIDIA Reflex latency, the video-memory budget Windows gives a game, and shader-compilation
|
||||
stutter are **not measured yet** — they read N/A. ([Accuracy](legal/ACCURACY.md))
|
||||
|
||||
## The game's memory
|
||||
|
||||
@@ -189,84 +173,6 @@ shown is recorded too, from outside the game. ([Capture](docs/04_CAPTURE.md))
|
||||
- **CPU temperature** needs *Run the agent as administrator* and the separately installed PawnIO driver, and
|
||||
has not been verified on real hardware yet. CPU load is the time the processor was busy — not Task
|
||||
Manager's "utility" figure, which can exceed 100%. ([Telemetry](docs/18_GPU_VENDOR_APIS.md))
|
||||
- **Advanced metrics** (since 0.1.0-beta.39; Settings ▸ Recording, off by default) stores more of what the graphics
|
||||
driver and the sensors report with each session. Its limits:
|
||||
- **A session recorded while it was off is not filled in later**, and switching it on applies from the next session.
|
||||
- **What a game tells DLSS and FSR** (since 0.1.0-beta.40) is kept only for a game FrameLedger measures from
|
||||
inside, and only where the game hands it over in a call FrameLedger intercepts. **Most games set their DLSS
|
||||
options through a call it cannot see and show nothing**; the FSR rows need FSR 3.1 or later through AMD's own
|
||||
library. The session says which it was — nothing seen, or not measured inside the game — and neither means the
|
||||
game uses no upscaler. They are the game's words, not a check of what the upscaler did; the field of view is a
|
||||
lowest and highest value, never a line over time; FSR's memory is a point where the game asked, so most sessions
|
||||
have none. FSR's upscaling values have been read from real games; **the DLSS options have not been confirmed on
|
||||
one yet.**
|
||||
- **What a game tells Streamline each frame, and how it configures FSR frame generation** (since 0.1.0-beta.43)
|
||||
are read from two calls FrameLedger hooks **only once a session with Advanced metrics on has started in that
|
||||
game** — a session recorded with the option off puts neither hook in. Streamline's values are those of **the
|
||||
first viewport that called**: a game with several (split screen, a picture-in-picture view) shows one, and the
|
||||
count of calls covers all. The frame-generation rows are **what the game asked for** — a game that asks for
|
||||
generation and gets none still reads "on", and the session's summary is where what was generated is measured. A
|
||||
setting the game changed during the session reads "on and off". The session's line says, for each of the two,
|
||||
whether it was read, hooked and never called by the game, or not hooked (the game did not load the library).
|
||||
Streamline 1.x is not read. Streamline's values have been read from three real games and the frame-generation
|
||||
configuration from one (2026-11-12); **a configuration that reaches FSR through AMD's 2.3 loader has not been
|
||||
read from a real game yet.** **A game may give a value in a unit of its own**: Cyberpunk 2077 gives Streamline
|
||||
its field of view in degrees where NVIDIA's header says radians. A field of view too large to be radians is
|
||||
shown as the game gave it, with a line saying so, and is never converted (since 0.1.0-beta.44; a session
|
||||
recorded before keeps the line it was stored with, which labels the degrees as radians). The count of resets is
|
||||
the number of calls in which the game said so — menus and loading screens raise it.
|
||||
- **Which version each Streamline feature is, and what it requires** (since 0.1.0-beta.44) are Streamline's
|
||||
answers to two questions a game asks while it starts — and, in the games run so far, again later. FrameLedger
|
||||
hooks the two calls only once a session with Advanced metrics on has started in that game. **A game that asks
|
||||
only at its start shows nothing here**, and the session's line then says the call was hooked and the game did
|
||||
not ask again; the four Unreal Engine games run on 2026-11-12 asked again and were read, and Cyberpunk 2077
|
||||
asked again for the requirements and not for the versions. A second session of a game that kept running keeps
|
||||
what the first one read. The rows are Streamline's answer as the game received it — the versions
|
||||
of Windows and of the driver are the ones Streamline found — not FrameLedger's own check of the PC. Twelve
|
||||
features are kept; a thirteenth is not. The lists the answer points to (the buffers, the Vulkan extensions) are
|
||||
never read, so the rows give how many buffers a feature needs and not which. **The version Streamline gives for
|
||||
a feature can differ from the file in the game's folder** — three games answered 2.14.16 for DLSS frame
|
||||
generation while shipping an older plugin; which file that newer one is was not looked into. The games run so
|
||||
far do not ask Streamline about DLSS upscaling unless they upscale through it, so a game can list frame
|
||||
generation here and no upscaler.
|
||||
- **Whether each Streamline feature is supported and loaded, and what the game did with it** (since
|
||||
0.1.0-beta.45) come from six more calls, hooked the same way — only once a session with Advanced metrics on has
|
||||
started in that game. **What the game did before that is not seen**: a feature it switched on while it started
|
||||
has no "switched" row, and resources it allocated then are not counted. The counts are **calls the game made**,
|
||||
not resources, and each stops at fifteen (shown as `≥ 15`); they and the switching start again with each
|
||||
session, while the two answers are kept from an earlier session of a game that kept running. "Supported" is
|
||||
Streamline's answer for the graphics card the game asked about; which card that was is never read, so on a PC
|
||||
with two cards the row does not say. A refusal is shown by NVIDIA's own name for it
|
||||
(`eErrorFeatureNotSupported`), and it is the game that was refused, not FrameLedger. None of this says a
|
||||
feature ran or drew anything. **Read on five games on 2026-11-13**: each asked whether its features are
|
||||
supported, three asked whether they are loaded, two switched features off and on, one freed a feature's
|
||||
resources once and one shut Streamline down once. **None allocated a feature's resources after FrameLedger was
|
||||
in it**, so that row has not been seen in a real game.
|
||||
- **What a game started Streamline with is not read, and will not be**: the game makes that call once, before
|
||||
FrameLedger can be inside it — also when FrameLedger starts the game itself. The Advanced page lists the entry
|
||||
with that reason.
|
||||
- **The driver's own figures** — the card's firmware and architecture, its memory in detail, what a display can do
|
||||
with HDR and variable refresh, the driver's settings for the game — exist on **NVIDIA** cards only. On other cards
|
||||
they read N/A; the card's sensors (fans, voltages, loads) are read on every brand, and none has been tested on an
|
||||
AMD or Intel card.
|
||||
- **The sensors are read every five seconds**, NVIDIA's figures every second; between two readings a sensor has no
|
||||
value, and its last one is not repeated.
|
||||
- **The processor's, the memory's and the motherboard's sensors** need *Run the agent as administrator* and the
|
||||
separately installed PawnIO driver, and **have never been read on real hardware**. Without them they read N/A
|
||||
with the reason.
|
||||
- **A drive's temperature is not read at all**: the sensor library cannot list drives without touching removable
|
||||
ones. Power supplies, fan controllers and batteries are not read either.
|
||||
- **No serial number and no display identification data (EDID) is read**, so two PCs with the same parts look the
|
||||
same.
|
||||
- **None of these readings has been checked against another tool**, and they are **not in an export or a bug
|
||||
report**.
|
||||
- **The Advanced page's "This PC" is read only while that page is open** (or a game is being recorded), is not
|
||||
stored, and keeps five minutes of each reading in memory. A reading with more than eight parts — every
|
||||
processor core — is drawn as its lowest, average and highest; the table lists each part.
|
||||
- **A session's chart needs its per-second series**, which are kept for the newest sessions of each game only
|
||||
(Settings ▸ Recording); an older session keeps its statistics.
|
||||
|
||||
([Telemetry](docs/18_GPU_VENDOR_APIS.md#advanced-metrics-owner-decisions-d101d108-2026-11-11))
|
||||
- **Whether the graphics card was held back by its power limit or by heat** (since 0.1.0-beta.14) is known only on
|
||||
NVIDIA cards, and only as it was at each once-a-second reading. On other cards it reads N/A.
|
||||
- **Frames per watt** (since 0.1.0-beta.14) counts the game's own frames — never generated ones — against the graphics
|
||||
@@ -277,8 +183,7 @@ shown is recorded too, from outside the game. ([Capture](docs/04_CAPTURE.md))
|
||||
|
||||
Off by default. When on, **Windows asks every time the agent starts** and names an unknown publisher, because
|
||||
FrameLedger is not signed. It lets FrameLedger open games that run as administrator and read the CPU
|
||||
temperature — with Advanced metrics on, also the processor's, the memory's and the motherboard's sensors — where
|
||||
PawnIO is installed; it does not bypass anti-cheat, does not open protected processes, and does not make games you
|
||||
temperature; it does not bypass anti-cheat, does not open protected processes, and does not make games you
|
||||
start from FrameLedger run as administrator. **The risk:** FrameLedger is installed in your user folder, so a
|
||||
program running under your account could replace its files and would then run as administrator the next time
|
||||
you accept the prompt. Turn it on only if you trust everything that runs under your account.
|
||||
@@ -323,9 +228,7 @@ a barrier is on its own page: [Accessibility](ACCESSIBILITY.md) (in the app: Hel
|
||||
- **Some games will not start directly** (seen on two Steam games, 2026-10-19 and 20). Lies of P, started by *Start
|
||||
directly*, hands itself to Steam within seconds — since 0.1.0-beta.27 the game Steam then starts is recorded —, and
|
||||
Clair Obscur: Expedition 33 closes within seconds, with or without FrameLedger's hook. Each such start ends a
|
||||
measured session early, which the crash safety counts: two turn hooking off for the game — and since
|
||||
0.1.0-beta.44 the count starts again each time you switch hooking back on (before, one more such end was enough
|
||||
once a game had been switched off). Start such a game through
|
||||
measured session early, which the crash safety counts: two turn hooking off for the game. Start such a game through
|
||||
its store (Settings ▸ Games ▸ *Play button*); the notice after Play says when a Steam game may hand itself to Steam.
|
||||
([details](docs/spike-notes/23-owner-runs-2026-10-20.md))
|
||||
|
||||
|
||||
@@ -12,8 +12,8 @@ app too (Help ▸ User guide, Help ▸ Limitations, Help ▸ Accessibility), and
|
||||
[wiki](https://github.com/poli0981/frameledger/wiki) with the developer pages.
|
||||
|
||||
<!-- accuracy-block:begin -->
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-11-11.** The software is a beta; its latest
|
||||
> **beta is `0.1.0-beta.49`** (2026-11-14), an unsigned installer built from that tag with its
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-11-06.** The software is a beta; its latest
|
||||
> **beta is `0.1.0-beta.37`** (2026-11-11), an unsigned installer built from that tag with its
|
||||
> checksums published beside it (alphas — experimental builds that try a newer .NET — are published apart). The source holds the desktop app
|
||||
> (library, store import, charts, settings) and the background Agent, which records a session when a
|
||||
> game in the library runs (unless you switched its recording off), injects only into games you enabled
|
||||
@@ -87,18 +87,8 @@ app too (Help ▸ User guide, Help ▸ Limitations, Help ▸ Accessibility), and
|
||||
> mean, median and peak. The game's other processes (launchers, helpers) are not counted.
|
||||
> - **Video memory:** in use on the whole graphics card, recorded from Windows and GPU-driver telemetry
|
||||
> and charted. **Not measured at all:** the video-memory budget Windows gives a game, which frame
|
||||
> spikes were shader compilation, end-to-end PC latency, and HDR. Stutter count and stutter time are
|
||||
> spikes were shader compilation, PC latency (Reflex), and HDR. Stutter count and stutter time are
|
||||
> measured from frame times.
|
||||
> - **NVIDIA's latency report (only with Advanced metrics on; Direct3D 12; a game that uses NVIDIA Reflex):** how
|
||||
> long the driver says each stage of a frame took — simulation, render submit, present, driver, the operating
|
||||
> system's queue, the graphics card — read from the graphics driver about once a second and shown as the driver
|
||||
> reported it: **the driver's numbers, not a measurement by FrameLedger**, an average of the frames of one read,
|
||||
> never checked against another tool, and not the delay from a click to the screen. **The stages overlap and do
|
||||
> not add up to the total.** The graphics card's stage runs from its start to its end and includes the time the
|
||||
> card waited — in one game it was longer than the whole frame — so since beta.48 two figures the driver works
|
||||
> out itself are shown beside it: the card's active time, and the time from one frame's end to the next. A
|
||||
> driver may give neither, and then there is no line. Read in two real games, on one driver and one card
|
||||
> (2026-11-14). A game that does not use Reflex has none. The session summary's latency fields stay N/A.
|
||||
> - **Pacing, VSync and the graphics card (since beta.14):** the share of the time below 30 FPS, below 60 FPS and below
|
||||
> the monitor's refresh rate, measured from frame times with small margins so that a game held at its limit is not
|
||||
> counted as below it (a rate less than 2 % under the line reads partly as at it), and how much one frame's time
|
||||
@@ -112,33 +102,6 @@ app too (Help ▸ User guide, Help ▸ Limitations, Help ▸ Accessibility), and
|
||||
> Windows once a second and charted. Processor temperature is read only when the Agent runs as
|
||||
> administrator — an option, off by default, for which Windows asks at every start of the Agent — with
|
||||
> PawnIO installed, and that reading has not yet been checked on real hardware; everywhere else it is `N/A`.
|
||||
> - **Advanced metrics (since beta.39; off unless you switch it on in Settings):** with it on, a session also stores
|
||||
> what the graphics driver and the sensor library report about the hardware — the graphics card's memory, load,
|
||||
> clocks, fans, voltages and power in detail, what a display can do, the driver's settings for the game — as they
|
||||
> report it: NVIDIA's figures once a second, the sensor library's every five seconds. None of these readings has
|
||||
> been checked against another tool. The processor's, the memory's and the motherboard's need the Agent as
|
||||
> administrator with PawnIO and have never been read on real hardware; a drive's temperature is not read. The
|
||||
> Advanced page shows them as they were stored, and what the PC reads at the moment only while that page is open.
|
||||
> - **What a game tells its upscaler (since beta.40; only with Advanced metrics on, only for a game measured from
|
||||
> inside):** the output size, presets and exposure a game hands DLSS, and the sharpening, jitter, exposure, depth
|
||||
> range, field-of-view range, flags and frame time it hands FSR, are read from the arguments of the calls
|
||||
> FrameLedger intercepts and shown as the game stated them — not checked against what the upscaler did. Most games
|
||||
> set their DLSS options through a call that cannot be intercepted and show none; the FSR values need FSR 3.1 or
|
||||
> later through AMD's own library. Since beta.43 also what a game tells NVIDIA Streamline about each frame (jitter,
|
||||
> motion-vector scale, depth range, field-of-view range, how often it reset the upscaler's history — for the first
|
||||
> viewport that called, where a game has several) and how it configures FSR frame generation (the settings it asked
|
||||
> for, not whether frames were generated). Since beta.44 also what Streamline answers when a game asks about a
|
||||
> feature — its version, and what it requires (graphics APIs, V-Sync, GPU scheduling, Windows and driver versions):
|
||||
> Streamline's answer as the game received it, not a check of the PC. A game that asks only while it starts has
|
||||
> none and the session says so; the Unreal Engine games run so far ask again later, and were read. Since beta.45
|
||||
> also whether Streamline says each feature is supported and whether it is loaded, and what the game did with it
|
||||
> after FrameLedger attached — switched it on or off, allocated and freed its resources (counted to fifteen), shut
|
||||
> Streamline down: calls the game made, not a statement that a feature ran or produced anything. FSR's upscaling
|
||||
> values, Streamline's constants (seven games), its answers about a feature (seven games), the
|
||||
> frame-generation configuration (one game) and five of beta.45's six calls (five games) have been read from
|
||||
> real games; no game run so far allocated a feature's resources after FrameLedger attached, and the DLSS
|
||||
> options have not been confirmed on one yet. A game may give a value in a unit of its own: one gives
|
||||
> Streamline its field of view in degrees, and it is shown as given.
|
||||
> - **Safety:** every pre-injection check runs before injection, including the signed-by-a-known-vendor
|
||||
> half of the suspicious-module rule. During every capture the Agent re-runs the checks every 30 s and
|
||||
> stops capturing on a refusal: a Direct3D or OpenGL game's hooks are removed, and the Vulkan layer
|
||||
@@ -215,7 +178,7 @@ Elevation is **optional — for everything.** Hooked capture is the normal path
|
||||
|
||||
## Install
|
||||
|
||||
> **The latest beta is `v0.1.0-beta.49` (2026-11-14); before it `v0.1.0-beta.48` (2026-11-14), `v0.1.0-beta.47` (2026-11-14), `v0.1.0-beta.46` (2026-11-13), `v0.1.0-beta.45` (2026-11-12), `v0.1.0-beta.44` (2026-11-12), `v0.1.0-beta.43` (2026-11-12), `v0.1.0-beta.42` (2026-11-12), `v0.1.0-beta.41` (2026-11-12), `v0.1.0-beta.40` (2026-11-12), `v0.1.0-beta.39` (2026-11-11), `v0.1.0-beta.38` (2026-11-11), `v0.1.0-beta.37` (2026-11-11), `v0.1.0-beta.36` (2026-11-10), `v0.1.0-beta.35` (2026-11-09), `v0.1.0-beta.34` (2026-11-06), `v0.1.0-beta.33` (2026-11-03), `v0.1.0-beta.32` (2026-10-31), `v0.1.0-beta.31` (2026-10-26), `v0.1.0-beta.30` (2026-10-26), `v0.1.0-beta.29` (2026-10-25), `v0.1.0-beta.28` (2026-10-20), `v0.1.0-beta.27` (2026-10-20), `v0.1.0-beta.26` (2026-10-19), `v0.1.0-beta.25` (2026-10-19), `v0.1.0-beta.24` (2026-10-19), `v0.1.0-beta.23` (2026-10-14), `v0.1.0-beta.22` (2026-10-13), `v0.1.0-beta.21` (2026-10-13), `v0.1.0-beta.20` (2026-10-12), `v0.1.0-beta.19` (2026-10-12), `v0.1.0-beta.18` (2026-10-07), `v0.1.0-beta.17` (2026-10-07), `v0.1.0-beta.16` (2026-10-06), `v0.1.0-beta.15` (2026-10-06), `v0.1.0-beta.14` (2026-10-06), `v0.1.0-beta.13` (2026-10-04), `v0.1.0-beta.12` (2026-10-04), `v0.1.0-beta.11` (2026-10-03), `v0.1.0-beta.10` (2026-09-28), `v0.1.0-beta.9` (2026-09-26), `v0.1.0-beta.8` (2026-09-25), `v0.1.0-beta.7` (2026-09-23), `v0.1.0-beta.6` (2026-09-23), `v0.1.0-beta.5` (2026-09-22), `v0.1.0-beta.4` (2026-09-21), `v0.1.0-beta.3` (2026-09-21), `v0.1.0-beta.2` (2026-09-17) and `v0.1.0-beta.1` (2026-09-16).** They are pre-releases: read the notes of the one you install — `CHANGELOG.md` links each release's own file under `docs/changelog/` — for what it measures, what it does not yet, and how to update, before installing. A source build is `docs/12_BUILD.md`.
|
||||
> **The latest beta is `v0.1.0-beta.37` (2026-11-11); before it `v0.1.0-beta.36` (2026-11-10), `v0.1.0-beta.35` (2026-11-09), `v0.1.0-beta.34` (2026-11-06), `v0.1.0-beta.33` (2026-11-03), `v0.1.0-beta.32` (2026-10-31), `v0.1.0-beta.31` (2026-10-26), `v0.1.0-beta.30` (2026-10-26), `v0.1.0-beta.29` (2026-10-25), `v0.1.0-beta.28` (2026-10-20), `v0.1.0-beta.27` (2026-10-20), `v0.1.0-beta.26` (2026-10-19), `v0.1.0-beta.25` (2026-10-19), `v0.1.0-beta.24` (2026-10-19), `v0.1.0-beta.23` (2026-10-14), `v0.1.0-beta.22` (2026-10-13), `v0.1.0-beta.21` (2026-10-13), `v0.1.0-beta.20` (2026-10-12), `v0.1.0-beta.19` (2026-10-12), `v0.1.0-beta.18` (2026-10-07), `v0.1.0-beta.17` (2026-10-07), `v0.1.0-beta.16` (2026-10-06), `v0.1.0-beta.15` (2026-10-06), `v0.1.0-beta.14` (2026-10-06), `v0.1.0-beta.13` (2026-10-04), `v0.1.0-beta.12` (2026-10-04), `v0.1.0-beta.11` (2026-10-03), `v0.1.0-beta.10` (2026-09-28), `v0.1.0-beta.9` (2026-09-26), `v0.1.0-beta.8` (2026-09-25), `v0.1.0-beta.7` (2026-09-23), `v0.1.0-beta.6` (2026-09-23), `v0.1.0-beta.5` (2026-09-22), `v0.1.0-beta.4` (2026-09-21), `v0.1.0-beta.3` (2026-09-21), `v0.1.0-beta.2` (2026-09-17) and `v0.1.0-beta.1` (2026-09-16).** They are pre-releases: read the notes of the one you install — `CHANGELOG.md` links each release's own file under `docs/changelog/` — for what it measures, what it does not yet, and how to update, before installing. A source build is `docs/12_BUILD.md`.
|
||||
|
||||
1. Download the latest `FrameLedger.App-win-Setup.exe` from [Releases](https://github.com/poli0981/frameledger/releases). It installs into `%LOCALAPPDATA%\FrameLedger.App`; your data stays in `%LOCALAPPDATA%\FrameLedger`, and uninstalling asks before touching it.
|
||||
2. SmartScreen may warn — releases are not code-signed (free, open-source project). Verify the SHA-256 checksum published with each release, then **More info → Run anyway**.
|
||||
@@ -261,7 +224,7 @@ FrameLedger is GPL-3.0-only free software, and you are welcome to build it, chan
|
||||
| `FrameLedger.Overlay.dll` | Inside the game | C++20 hooks + lock-free shared-memory writer. Records only; never analyzes, allocates, or blocks |
|
||||
| `FrameLedger.VkLayer.dll` | Inside the game | Vulkan implicit layer (Vulkan titles use this instead of injection) |
|
||||
|
||||
GPU telemetry is layered so the project never depends on a proprietary vendor licence: a vendor-neutral DXGI/performance-counter baseline, LibreHardwareMonitor (MPL-2.0) for sensors on all vendors, and NVIDIA's NVAPI SDK (MIT) for NVIDIA-only extras (telemetry and the driver's DLSS record; and, with Advanced metrics on, the driver's own latency report, read inside a Direct3D 12 game that uses NVIDIA Reflex). No Intel or AMD GPU *telemetry* SDK is bundled — see `docs/18_GPU_VENDOR_APIS.md` for why. The one AMD component in the tree is five MIT headers from the FidelityFX SDK, used for types only so the upscaler hook can read an FSR title's own dispatch descriptor; nothing AMD-built is linked or redistributed.
|
||||
GPU telemetry is layered so the project never depends on a proprietary vendor licence: a vendor-neutral DXGI/performance-counter baseline, LibreHardwareMonitor (MPL-2.0) for sensors on all vendors, and NVIDIA's NVAPI SDK (MIT) for NVIDIA-only extras (telemetry and the driver's DLSS record today; Reflex latency is not read yet). No Intel or AMD GPU *telemetry* SDK is bundled — see `docs/18_GPU_VENDOR_APIS.md` for why. The one AMD component in the tree is five MIT headers from the FidelityFX SDK, used for types only so the upscaler hook can read an FSR title's own dispatch descriptor; nothing AMD-built is linked or redistributed.
|
||||
|
||||
---
|
||||
|
||||
|
||||
+1
-1
@@ -1 +1 @@
|
||||
main
|
||||
alpha
|
||||
@@ -25,14 +25,8 @@
|
||||
-->
|
||||
<Property Name="sonar.exclusions">src/native/third_party/**,**/Strings.Designer.cs,src/native/tools/hook-harness/dxr_raygen_dxil.h,src/native/tools/vendor-stubs/**,tests/fixtures/**,legal/licenses/**,docs/vendor-exports.json,src/FrameLedger.Infrastructure/Persistence/Migrations/**,build/**,out/**,**/bin/**,**/obj/**,**/TestResults/**</Property>
|
||||
|
||||
<!--
|
||||
Tests repeat their arrange steps on purpose; duplication there is not a defect.
|
||||
HookFamilies.cs is the Domain's mirror of FlHookFamily (ShmLayout.cs): Domain references nothing, so the enum is
|
||||
written twice by design and MetricEnumMirrorTests fails when the two differ. Six members added at once
|
||||
(0.1.0-beta.45) were 39 duplicated lines of 1,063 new ones, 3.7 % against the gate's 3 %, and failed it on the
|
||||
release's commit with no issue open. The mirror is left out of the detection; FlHookFamily itself is not.
|
||||
-->
|
||||
<Property Name="sonar.cpd.exclusions">tests/**,src/native/tests/**,src/FrameLedger.Domain/Metrics/HookFamilies.cs</Property>
|
||||
<!-- Tests repeat their arrange steps on purpose; duplication there is not a defect. -->
|
||||
<Property Name="sonar.cpd.exclusions">tests/**,src/native/tests/**</Property>
|
||||
|
||||
<Property Name="sonar.sourceEncoding">UTF-8</Property>
|
||||
|
||||
|
||||
@@ -479,26 +479,6 @@ function Invoke-ProjectGates {
|
||||
# beta.24 (D66): CHANGELOG.md and docs/HANDOFF.md keep their paths as the index of their parts under docs/changelog/
|
||||
# and docs/handoff/. A released section left in CHANGELOG.md, a release file whose heading is not its name or that
|
||||
# links relatively, or an index and its files that do not name each other both ways is red here.
|
||||
# 2026-11-11 (D108): "the bridge never calls a setter" was a sentence in docs/18 a reviewer checked by reading one
|
||||
# file. With Advanced metrics the bridge calls forty-four NVAPI entry points, and the header declares a setter beside
|
||||
# almost every getter: each call is held to tools/nvapi-allowed-calls.txt, in both directions, and a writer or a
|
||||
# reader of an identifier (D104) is red even when the list names it. Text only - it runs with or without the native
|
||||
# build.
|
||||
Write-Step 'nvapi-readonly-check'
|
||||
$nvapiTool = Join-Path $repo 'tools/nvapi-readonly-check.ps1'
|
||||
Invoke-Checked 'nvapi-readonly-check (self-test)' { & $nvapiTool -SelfTest }
|
||||
Invoke-Checked 'nvapi-readonly-check' { & $nvapiTool -RepoRoot $repo }
|
||||
|
||||
# 2026-11-12 (D116): the same for the code loaded into a game. Advanced metrics, train B, reads more members of
|
||||
# the vendors' structs than the frame record ever needed, and the same structs hold where the player's camera is.
|
||||
# Every such read is in one header, each member on tools/overlay-allowed-fields.txt in both directions; a camera's
|
||||
# position, axes and matrices are named nowhere in the Overlay or the Vulkan layer, whatever the list says. Text
|
||||
# only.
|
||||
Write-Step 'overlay-fields-check'
|
||||
$fieldsTool = Join-Path $repo 'tools/overlay-fields-check.ps1'
|
||||
Invoke-Checked 'overlay-fields-check (self-test)' { & $fieldsTool -SelfTest }
|
||||
Invoke-Checked 'overlay-fields-check' { & $fieldsTool -RepoRoot $repo }
|
||||
|
||||
Write-Step 'docs-split-check'
|
||||
$splitTool = Join-Path $repo 'tools/docs-split-check.ps1'
|
||||
Invoke-Checked 'docs-split-check (self-test)' { & $splitTool -SelfTest }
|
||||
|
||||
@@ -162,7 +162,7 @@ The profile's own folder is refused there.)*
|
||||
- **ADR-8:** **No evasion, ever** (`19_SAFETY` §What we will never build). This is an architectural constraint, not a preference — it defines what "correct" means for this codebase.
|
||||
- **ADR-9:** Elevation demoted from required to optional; the Agent runs as a standard user by default.
|
||||
**Chosen, not inherited, since beta.10 (owner decision D34, 2026-09-27):** Settings ▸ Capture agent ▸ *Run the agent as
|
||||
administrator* (`capture.run_elevated`, off by default, a versioned disclosure — `agent-admin-dialog/2` *(`/1` until 2026-11-11, when Advanced metrics widened what the option adds — D101)* — before it turns
|
||||
administrator* (`capture.run_elevated`, off by default, a versioned disclosure — `agent-admin-dialog/1` — before it turns
|
||||
on). With it on, **Windows is asked every time the Agent starts** — a UAC prompt owned by the App's window when the App
|
||||
starts it, flashing on the taskbar when the logon task does — and there is no silent path: no "highest privileges" task,
|
||||
no service. The elevated Agent is started for one user (`--serve --for-user <SID>`) and refuses to run as another
|
||||
|
||||
+1
-2
@@ -53,7 +53,6 @@ Requirement IDs (`FR-x`, `NFR-x`) are referenced by other docs, commits, and tes
|
||||
- FR-5.3 Charts handle ≥ 500k points via min/max decimation; zoom/pan; PNG export.
|
||||
- FR-5.4 Native/Displayed toggle wherever FG data exists.
|
||||
- FR-5.5 Stutter markers annotated with cause when known (`PSO compile`, `VRAM budget exceeded`).
|
||||
- FR-5.6 *(owner decision D101, 2026-11-11)* **Advanced metrics**: an option, off by default, and a page of its own that shows what the vendor interfaces make available — NVAPI, LibreHardwareMonitor through PawnIO, and in later releases Streamline and FidelityFX inside the game — each value under what it belongs to, the PC or one session, and each value that is not read listed with the reason. Off means nothing more is read or stored. `18_GPU_VENDOR_APIS` §Advanced metrics is the design and the inventory. *(Not built: the catalog exists, nothing reads it yet.)*
|
||||
|
||||
### FR-6 History & comparison
|
||||
- FR-6.1 Sessions table per game: date, duration, tier badge, Native, Displayed, FG×, lows, resolution + upscaler, RT/PT/RR chips, crash badge, tags.
|
||||
@@ -105,7 +104,7 @@ Draw live FPS/frametime/upscaler info inside the game. Only for games already ho
|
||||
## Non-functional requirements
|
||||
|
||||
- **NFR-1 Game-side overhead:** ≤ 1 µs per present, ≤ 8 MB resident, measured game FPS impact ≤ 0.5% vs uninstrumented.
|
||||
- **NFR-2 Agent overhead:** ~~≤ 1% of one core during capture~~ **≤ 2.5 % of one core during capture** *(owner decision D117, 2026-11-11: the 1 % had never been measured; measured in a real Agent it is 1.93 % with Advanced metrics off and 2.04 % with it on — `20_OPEN_QUESTIONS` §M16, `tools/agent-cost.ps1` — nearly all of it the once-a-second read of the graphics card's sensors, which stays)*, ≤ 150 MB working set *(measured: 113 MiB off, 119 MiB on)*, ~0% idle. *(D101, 2026-11-11: the limits hold with Advanced metrics on — FR-5.6. Its reads run on a thread of their own, the slow ones seldom, and with no game running only while its page is open (D107), so "~0% idle" is not spent on it. Measured on the development PC in a session that is not hooked; a hooked session, an elevated Agent with PawnIO's groups and a real game are the owner's run, `HANDOFF` §Owner-only.)*
|
||||
- **NFR-2 Agent overhead:** ≤ 1% of one core during capture, ≤ 150 MB working set, ~0% idle.
|
||||
- **NFR-3 Stability:** faults **originating in our own hook bodies** are contained by `FL_HOOK_GUARD`, counted, and self-disable the Overlay after 3 occurrences; the safety-unhook path completes within one frame. The Overlay adds no allocation, lock, syscall or logging to the present path.
|
||||
|
||||
> This deliberately does **not** say "must never crash a game" (`20_OPEN_QUESTIONS` §H8). SEH containment cannot reliably catch stack overflow, cannot intercept `__fastfail` — and `-D_HAS_EXCEPTIONS=0` converts a would-be STL throw into exactly that (`spike-notes.md` §H3) — and does not help when the game installs a vectored exception handler that runs first. An absolute promise the mechanism cannot support does not belong in a requirement, and must stay out of user-facing text: the Disclaimer already says injection carries risk, and that wording is the honest one.
|
||||
|
||||
+2
-68
@@ -36,7 +36,7 @@ Let `D` = session duration (first → last present), `F_app` = frames the *game*
|
||||
| **Frametime σ** | population stddev of `ft_app` (ms) | 1 |
|
||||
| **Stutter count** | `ft_app[i] > 2 × rollingMedian(ft_app, 19)` (centered, window in **frames**) | 1 |
|
||||
| **Stutter time %** | `Σ ft_app[stutter] / Σ ft_app × 100` | 1 |
|
||||
| **PC latency** | mean/p95 of `reflexLatencyUs` when Reflex reports it *(nothing fills `reflexLatencyUs`: a report arrives after its frame's record is written. Since train C, 2026-11-13, the driver's stage report is read as seven Advanced series beside the frames — `18_GPU_VENDOR_APIS` §The inventory — and these session fields stay N/A; asked again on 2026-11-14 with two real games read, the owner kept them N/A (D147): the driver's total runs from simulation start to the graphics card's end, not from an input to the display)* | **1 only** |
|
||||
| **PC latency** | mean/p95 of `reflexLatencyUs` when Reflex reports it | **1 only** |
|
||||
| **PSO stutter %** | share of stutter frames with `psoCreatedThisFrame > 0` | **1 only** |
|
||||
| **Time below 30 / 60 FPS** (beta.14) | share of `Σ ft_app` in frames that count as below X — `ft > 1.10 × 1000/X`, or the nine-frame rolling median `> 1.02 × 1000/X` (§Pacing) | 1 |
|
||||
| **Time below refresh** (beta.14) | the same over **presents**, X = `display_monitor_hz` — the display's rate, so over what the display received | 1 |
|
||||
@@ -687,18 +687,6 @@ From the upscaler hooks we get, per frame:
|
||||
> Measured on the hook harness with the vendor stub answering as the SDK documents (`fl_guard` "FSR's quality
|
||||
> mode", by size through the SDK 2.x loader and by ratio through the 1.1.x monolith); a real title is owner-only
|
||||
> item 21 (Lies of P at Quality, then Performance).
|
||||
- **One technology's name, quality and size** *(2026-11-12, owner decision D120)*. A session's — and a segment's —
|
||||
upscaler is **the technology named on the most samples of the dominant stream** (a tie goes to the lower value, as
|
||||
the quality byte's does), not the first one any record names. While a session names one technology, its quality
|
||||
and render size are read from the whole stream as before: under frame generation the name sits on one present in
|
||||
N. When it names **more than one**, the quality and the size are read **only from the samples that name the
|
||||
chosen one**, a quality byte of the other family is withheld (`UpscalerChoice.QualityFor`), and the session is
|
||||
marked "settings changed during session". The session this was found on (Dying Light: The Beast, 81 seconds:
|
||||
DLSS evaluated for most of it, an FSR dispatch for a few seconds) had been stored as "DLSS" with FSR's Balanced
|
||||
byte and FSR's render size — three true readings of two technologies under one name. What the chosen technology
|
||||
did not say stays N/A (rule 7). `Domain.Metrics.UpscalerChoice`; the live card still names the first technology
|
||||
the session saw (`FgLadder.UpscalerIdentity`), which for a session in progress is a different question and was
|
||||
not changed.
|
||||
- Resolution changes mid-session (user changed settings, or dynamic resolution scaling) produce **segments**: the session stores a segment list `(startFrame, renderW/H, outputW/H, upscaler, quality)`. Aggregates report the dominant segment plus a "settings changed during session" flag — averaging across a settings change is the classic way benchmark numbers become meaningless.
|
||||
|
||||
> **Two segmentation axes exist, they compose in ONE order, and neither document said so until
|
||||
@@ -976,60 +964,6 @@ min / max in `sensor_stats_json` (§Sensor aggregates). MiB stored; shown in GB
|
||||
|
||||
~~`vramUsedMb` from `IDXGIAdapter3::QueryVideoMemoryInfo(LOCAL)` inside the game = **this game's** usage and budget. **MiB, truncating, and it must use the same divisor as `vramBudgetMb`** — the two are compared, and mismatched rounding would put a systematic bias into `budget_exceeded_pct`. Residual: a flip within 1 MiB of the budget, 0.004% of a 24 GiB card. Stored as its own series and clearly labelled apart from the adapter-wide figure from `18_GPU_VENDOR_APIS`. Aggregates: avg, max, and `budget_exceeded_pct` (share of samples where `CurrentUsage > Budget`, i.e. the driver was likely evicting — a genuinely useful stutter explanation).~~
|
||||
|
||||
## Input — what a session was played with, both tiers (owner decisions D155–D163)
|
||||
|
||||
**Owner request, 2026-11-14:** the share of a session played with a controller and with the keyboard, how often a
|
||||
controller connected and dropped, the battery state that lasted longest, the switches between makers' controllers.
|
||||
What is read and what never is: [`21_INPUT_DEVICES.md`](21_INPUT_DEVICES.md). The arithmetic is
|
||||
`Domain.Input` and `Application.Recording.InputSessionBuilder`. **Not built end to end yet** — nothing reads a device
|
||||
until the pull requests after the one that wrote this section; until then these are definitions under test.
|
||||
|
||||
**What it can say, and what it cannot.** Everything is read from outside the game. So a number here says that a
|
||||
controller, or the keyboard or mouse, was *in use while the game's window was in front* — never what the game did with
|
||||
it, and never which button or key.
|
||||
|
||||
**The unit is a slice** of about a tenth of a second, and a slice counts for a session only when a window of the
|
||||
session's game was in front and the session was not paused (a pause is a gap, as for frames). A slice with another
|
||||
program in front is not classified: typing in a browser beside the game is not the game played with the keyboard.
|
||||
|
||||
| Class | A slice in front in which |
|
||||
|---|---|
|
||||
| Controller | a controller was in use and the time of the last keyboard-or-mouse input did not move |
|
||||
| Keyboard & mouse | that time moved and no controller was in use. One class: only a time is read (D158) |
|
||||
| Both | both |
|
||||
| No input | neither |
|
||||
|
||||
- **A controller is in use** when a button is down, a trigger is past its threshold, or a stick is outside its dead
|
||||
zone. A stick held counts. One that drifts inside the dead zone does not — a pad lying on a desk is not played with.
|
||||
- **A share** is a class's time over the time the game was in front (`input_foreground_ms`). The four add up to it.
|
||||
- **A switch of method** is a change between *controller* and *keyboard & mouse* from one tick (a second) to a later
|
||||
one. A tick played with both, or with neither, is no one thing and does not end the run before it: putting the
|
||||
controller down and picking it up again is not a switch.
|
||||
- **Connections** are counted from the session's second slice: a controller that is there when the session starts has
|
||||
not connected. A Bluetooth pad that goes to sleep has disconnected.
|
||||
- **A battery** is timed by the clock, in front or not: the time at each level, the level that lasted longest, the
|
||||
first and the last. Each source keeps its own steps — XInput's four words, a DualSense's per cent in tens — and none
|
||||
is converted into another's. **A rate**, in per cent an hour, is the fall from the first to the last reading on
|
||||
battery over the time read on battery; it is given only for a level in per cent that fell, was not put on power in
|
||||
between, and was read on battery for ten minutes or more.
|
||||
- **A maker's share** is the time its controllers were in use over that time for every maker. **A switch of maker**
|
||||
is counted like a switch of method, between ticks in which one maker's controllers alone were in use.
|
||||
- **One pad seen twice is one controller.** With Steam Input in front of a controller Windows shows the controller the
|
||||
player holds and an Xbox pad Steam presents for it. One of XInput's pads that was in use at the same moments as
|
||||
another controller — nine tenths of the busier one's time, over ten seconds or more — is folded into it: into a
|
||||
controller that is not XInput's at any time, into another of XInput's pads only in a session in which Steam's
|
||||
virtual gamepad was seen. Two players pressing in step are two players.
|
||||
|
||||
**The timeline** is one series, `input.class`: what each tick was mostly played with, as the class's number (0 no
|
||||
input, 1 controller, 2 keyboard & mouse, 3 both), and no value for a tick with the game not in front. Each of the
|
||||
first eight controllers has `input.dev.N.active` (the part of the tick's time in front it was in use; no value where
|
||||
it was not connected) and, with a battery that has a level, `input.dev.N.battery`.
|
||||
|
||||
**Known limits.** Keyboard and mouse cannot be told apart. Input a program injects counts as keyboard and mouse — Steam
|
||||
Input mapping a pad to keys, a macro tool — so a pad mapped that way reads as *both*. A game whose window belongs to
|
||||
another process reads as never in front (the focus sample's limit). Whether a controller's own input moves Windows'
|
||||
last-input time has not been checked on a real PC.
|
||||
|
||||
## Sensor aggregates
|
||||
|
||||
Per session over 1 Hz samples: `avg` (mean of non-null), `max` — and since beta.12 the `median` (the linear-interpolation
|
||||
@@ -1073,7 +1007,7 @@ processor's, not the whole PC's — averaged over the session's sensor ticks. `D
|
||||
| RT active | measured per frame | not available |
|
||||
| Path tracing | heuristic, confidence-scored, never asserted | not available |
|
||||
| ~~Per-process VRAM~~ Game process memory (beta.12) | ~~exact~~ dedicated / shared GPU memory as Task Manager counts it — a known 512 MiB allocation read +512.0 MiB (`spike-notes` §16); private working set equal to Windows' own counter; read from outside the game | ~~not available~~ the same, from outside; an unpinned hold sums the executable's processes |
|
||||
| PC latency | ~~as reported by Reflex~~ **not available** (D147, *corrected 2026-11-14*): the driver's report ends at the end of the GPU's work, not at the display. The stages it does give are Advanced metrics — the driver's numbers, unchecked | not available |
|
||||
| PC latency | as reported by Reflex | not available |
|
||||
| Display mode (beta.10) | per 100 ms sample: exclusive fullscreen as the swap chain answers it (DXGI; OpenGL and Vulkan cannot say), borderless, windowed, minimised; the window's size from user32 | per 1 s sample, from the window alone: windowed, minimised, or *fullscreen or borderless* — never split |
|
||||
| GPU temp / load / power | vendor API accuracy, ±1 s sampling | same |
|
||||
| GPU clocks / fan / memory temperature (beta.14) | vendor API accuracy, ±1 s sampling | same |
|
||||
|
||||
+1
-4
@@ -26,9 +26,6 @@ public interface IFrameSource : IAsyncDisposable
|
||||
> DrainResult Drain(Span<FlFrameRecord> into, IList<ulong> gapIndices);
|
||||
> void PublishGuardResult(uint completedEvaluations, bool unhookRequested);
|
||||
> void SetPaused(bool paused); void RequestLogFlush();
|
||||
> FlAdvancedState? AdvancedState { get; } void SetAdvancedRequested(bool requested); // region 5, train B (2026-11-12): the
|
||||
> // word is written either way as the ring is attached, before the first guard result; the region is read only by
|
||||
> // a session whose observer WantsInGameAdvanced, and carried on CaptureProgress.InGameAdvanced
|
||||
> }
|
||||
> public sealed class CaptureSession(...) // the loop: gate → inject → attach → drain, until something ends it
|
||||
> {
|
||||
@@ -540,7 +537,7 @@ Crash-within-60s-of-injection happening twice for the same game ⇒ **hooking au
|
||||
|---|---|
|
||||
| Game process, per present | ≤ 1 µs; no syscall, no allocation, no lock, no logging (`17_HOOK_ENGINE`) |
|
||||
| Game process, resident | ≤ 8 MB (DLL + ring) |
|
||||
| Agent, during capture | ~~≤ 1%~~ ≤ 2.5 % of one core average *(NFR-2 as D117 amended it, 2026-11-11: measured 1.93 %, `20_OPEN_QUESTIONS` §M16)*, ≤ 150 MB working set |
|
||||
| Agent, during capture | ≤ 1% of one core average, ≤ 150 MB working set |
|
||||
| Agent, idle | ~0% (1 Hz process poll only) |
|
||||
| Measured game FPS impact | ≤ 0.5% vs uninstrumented, verified per release (`14_TESTING` §Hook overhead) |
|
||||
|
||||
|
||||
@@ -22,8 +22,8 @@ Derived in the Agent from the record stream; the mapping is in `03_METRICS`. Sum
|
||||
| Render resolution vs output resolution (incl. mid-session changes) | upscaler parameter reads + `ResizeBuffers` |
|
||||
| Frame Generation mode + factor | NGX/SL/FFX FG feature evaluation, then cadence — **Tier 1 only**. ~~then (Tier 2 only) PresentMon `FrameType`~~ retired (§S31 row P2), and Tier 2 no longer produces frames to run cadence over either |
|
||||
| Ray Tracing active | AS builds + `DispatchRays` (both, to catch inline RayQuery) |
|
||||
| Ray Reconstruction | ~~NGX `RayReconstruction` feature evaluated~~ Streamline's `slEvaluateFeature(kFeatureDLSS_RR)` — it runs **instead of** super resolution, in DLSS's own quality mode (Streamline's guide; measured 2026-08-15), so the upscaler is DLSS and this is a yes/no beside it. A game that calls NGX directly reads N/A (`03_METRICS` §RT/PT/RR) *(corrected 2026-11-14)* |
|
||||
| ~~Reflex on + PC latency~~ The driver's latency report and sleep status (0.1.0-beta.47, Advanced metrics only) | ~~NVAPI Reflex hooks~~ two read-only getters of the driver, called by the Overlay (`17_HOOK_ENGINE` §Calls the Overlay makes into a driver). **PC latency — input to display — is not read** (D147): the report ends where the GPU's work ends, and NVIDIA's own figure is taken from outside the game (`spike-notes` §30, route E) *(corrected 2026-11-14)* |
|
||||
| Ray Reconstruction | NGX `RayReconstruction` feature evaluated |
|
||||
| Reflex on + PC latency | NVAPI Reflex hooks |
|
||||
| Per-process VRAM | `QueryVideoMemoryInfo` |
|
||||
| PSO compilation events | pipeline-creation hooks |
|
||||
| Display mode — exclusive fullscreen / borderless / windowed / minimised, with the window, back buffer and monitor (beta.10) | `GetFullscreenState` + `GetDesc` polled on the presenting chain (≤ 2 Hz, shared-memory region 4), and the window's geometry read by the Agent **out of process** — so this row is **both tiers**: a Tier-2 session has the window alone, and never splits exclusive from borderless (`03_METRICS` §Display mode) |
|
||||
|
||||
+1
-85
@@ -2,7 +2,7 @@
|
||||
|
||||
`%LOCALAPPDATA%\FrameLedger\ledger.db`. Pragmas: `journal_mode=WAL`, `synchronous=NORMAL`, `foreign_keys=ON`, `busy_timeout=5000`. `Microsoft.Data.Sqlite` + Dapper; all writes in explicit transactions.
|
||||
|
||||
**Writer ownership:** Agent writes `sessions`, `session_segments`, `frame_blobs`, `sensor_blobs`, `hardware_snapshots`, *(since schema 0023, 2026-11-11)* `machine_profiles` and `session_advanced`, the hook-state columns on `games`, **and since P4 PR-1 (2026-09-14) the *detected* columns on `games`** — `engine`, `engine_version`, `platform` under the per-field provenance rule (`05_DETECTION` §Caching: a `user` field is never touched), `capability_flags` whole, and the cache key `detection_rules_version` / `detection_exe_size_bytes` / `detection_exe_mtime_ms`, and since schema 0011 (2026-09-25) the executable's own facts `exe_machine` / `exe_file_version` / `exe_product_version` / `library_versions`, written whole like the flags — through `IGameRepository.ApplyDetectionAsync` only. The UI and the Agent were both already writers of `games`; this adds columns to the Agent's half, not a third writer (HANDOFF §P4). **And since P4 PR-4 the UI's library import writes `platform`, `store_id` and `game_version` through `ApplyStoreMetadataAsync`** — the same per-field provenance rule, badged `detected` (a store's record is not the user's typing), on columns the UI already owned. **And since 2026-09-23 the Agent's relocator merges two entries for one executable under two drive letters** (`IGameMerge`, HANDOFF D26, `19_SAFETY` §A moved drive is the same executable): in one transaction it re-parents the dropped entry's `sessions` to the survivor (before the delete — `sessions.game_id` cascades), carries a block or a crash auto-disable still in force to the survivor (`hook_enabled` only ever to 0; `hook_blocked_reason` is copied, never originated or cleared), adds the crash counts, deletes the dropped `games` row, and then moves the survivor to the file's path (after the delete — `exe_path` is UNIQUE). It was the one Agent write that deletes a `games` row until beta.19; it never touches a consent column. **And since beta.19 (2026-10-12, D55) the Agent removes an entry whose game is no longer installed** (`IGamePrune`, `SqliteGamePrune`, asked by the detection sweep through `UninstalledEntryPrune`): one `DELETE` that holds every stored condition in the same statement — the same row at the same path, `removed_at` NULL, no session stored (`NOT EXISTS` on `sessions` — nothing cascades), no `hook_blocked_reason`, `hook_prescan_state` not `blocked`, no `ac_exception_at` and no `ac_exception_trial_failed_at` — behind `retention.remove_uninstalled_games`; a block, a grant and D38's mark are never removed with their entry (`19_SAFETY` §What a finding does to the game, *What clears it*). **And since 2026-09-23 the UI writes `record_sessions`** (schema 0009, FR-1.6): the entry's recording switch, which the Agent only reads — off, the watcher does not watch for the program. The script's one data change switches it off for entries an old import made for Steam's own tools (`SteamLibrarySource.KnownTools`, the ids as of the script); a twin merge keeps it off when either twin had it off. **And since 2026-09-25 the Agent's pre-scan of the library (`19_SAFETY` §What a finding does to the game) writes the hook-state columns of every entry, not only of those the user asked to hook** — `hook_prescan_state`, and on a finding `hook_enabled = 0` and `hook_blocked_reason` — and its own key, `hook_prescan_rules_version` / `hook_prescan_exe_size_bytes` / `hook_prescan_exe_mtime_ms` (schema 0010), through `IGameConsentStore.RecordPreScanAsync` only: columns that were already the Agent's, never over a block, never a new row. **And since 2026-09-26 (schema 0014, D33) the Agent writes the user-mode exception's columns** — `ac_exception_*` on `games` through `IGameConsentStore` only (eligibility from the sweep, a grant from the `SetAntiCheatException` command, every end), and `sessions.ac_exception_family` with the session — the grant only after the user accepted its disclosure in the UI, which asks and never writes. **And since 2026-10-03 (beta.11, D40) the Agent deletes sessions on request** — every session of one game or of every game, `DeleteSessions` over the pipe, through `ISessionRepository.DeleteSessionsAsync` in one transaction (segments, blobs and annotations cascade), never while one is being recorded; the UI asks and never deletes a session row itself *(for Delete all sessions; FR-1.4's removal is the App's own cascade, above — corrected 2026-10-04)*. **Maintenance (P4 PR-7) adds no writer:** the retention sweep on demand is the Agent's, asked over the pipe; the UI's `VACUUM` rewrites pages with the same contents and changes no row (§Retention built note). UI writes `games` (user-editable fields — since P3 PR-3 that is the FR-1.3 metadata, the `*_default` tri-states, and `removed_at`; ~~never a `hook_*` column~~ **and two downgrades** *(corrected 2026-10-04)*: *Change executable* (2026-09-21, `GameLibrary.ChangeExecutableAsync`) turns hooking off, clears the consent and pre-scan columns and ends an excepLine truncated
|
||||
**Writer ownership:** Agent writes `sessions`, `session_segments`, `frame_blobs`, `sensor_blobs`, `hardware_snapshots`, the hook-state columns on `games`, **and since P4 PR-1 (2026-09-14) the *detected* columns on `games`** — `engine`, `engine_version`, `platform` under the per-field provenance rule (`05_DETECTION` §Caching: a `user` field is never touched), `capability_flags` whole, and the cache key `detection_rules_version` / `detection_exe_size_bytes` / `detection_exe_mtime_ms`, and since schema 0011 (2026-09-25) the executable's own facts `exe_machine` / `exe_file_version` / `exe_product_version` / `library_versions`, written whole like the flags — through `IGameRepository.ApplyDetectionAsync` only. The UI and the Agent were both already writers of `games`; this adds columns to the Agent's half, not a third writer (HANDOFF §P4). **And since P4 PR-4 the UI's library import writes `platform`, `store_id` and `game_version` through `ApplyStoreMetadataAsync`** — the same per-field provenance rule, badged `detected` (a store's record is not the user's typing), on columns the UI already owned. **And since 2026-09-23 the Agent's relocator merges two entries for one executable under two drive letters** (`IGameMerge`, HANDOFF D26, `19_SAFETY` §A moved drive is the same executable): in one transaction it re-parents the dropped entry's `sessions` to the survivor (before the delete — `sessions.game_id` cascades), carries a block or a crash auto-disable still in force to the survivor (`hook_enabled` only ever to 0; `hook_blocked_reason` is copied, never originated or cleared), adds the crash counts, deletes the dropped `games` row, and then moves the survivor to the file's path (after the delete — `exe_path` is UNIQUE). It was the one Agent write that deletes a `games` row until beta.19; it never touches a consent column. **And since beta.19 (2026-10-12, D55) the Agent removes an entry whose game is no longer installed** (`IGamePrune`, `SqliteGamePrune`, asked by the detection sweep through `UninstalledEntryPrune`): one `DELETE` that holds every stored condition in the same statement — the same row at the same path, `removed_at` NULL, no session stored (`NOT EXISTS` on `sessions` — nothing cascades), no `hook_blocked_reason`, `hook_prescan_state` not `blocked`, no `ac_exception_at` and no `ac_exception_trial_failed_at` — behind `retention.remove_uninstalled_games`; a block, a grant and D38's mark are never removed with their entry (`19_SAFETY` §What a finding does to the game, *What clears it*). **And since 2026-09-23 the UI writes `record_sessions`** (schema 0009, FR-1.6): the entry's recording switch, which the Agent only reads — off, the watcher does not watch for the program. The script's one data change switches it off for entries an old import made for Steam's own tools (`SteamLibrarySource.KnownTools`, the ids as of the script); a twin merge keeps it off when either twin had it off. **And since 2026-09-25 the Agent's pre-scan of the library (`19_SAFETY` §What a finding does to the game) writes the hook-state columns of every entry, not only of those the user asked to hook** — `hook_prescan_state`, and on a finding `hook_enabled = 0` and `hook_blocked_reason` — and its own key, `hook_prescan_rules_version` / `hook_prescan_exe_size_bytes` / `hook_prescan_exe_mtime_ms` (schema 0010), through `IGameConsentStore.RecordPreScanAsync` only: columns that were already the Agent's, never over a block, never a new row. **And since 2026-09-26 (schema 0014, D33) the Agent writes the user-mode exception's columns** — `ac_exception_*` on `games` through `IGameConsentStore` only (eligibility from the sweep, a grant from the `SetAntiCheatException` command, every end), and `sessions.ac_exception_family` with the session — the grant only after the user accepted its disclosure in the UI, which asks and never writes. **And since 2026-10-03 (beta.11, D40) the Agent deletes sessions on request** — every session of one game or of every game, `DeleteSessions` over the pipe, through `ISessionRepository.DeleteSessionsAsync` in one transaction (segments, blobs and annotations cascade), never while one is being recorded; the UI asks and never deletes a session row itself *(for Delete all sessions; FR-1.4's removal is the App's own cascade, above — corrected 2026-10-04)*. **Maintenance (P4 PR-7) adds no writer:** the retention sweep on demand is the Agent's, asked over the pipe; the UI's `VACUUM` rewrites pages with the same contents and changes no row (§Retention built note). UI writes `games` (user-editable fields — since P3 PR-3 that is the FR-1.3 metadata, the `*_default` tri-states, and `removed_at`; ~~never a `hook_*` column~~ **and two downgrades** *(corrected 2026-10-04)*: *Change executable* (2026-09-21, `GameLibrary.ChangeExecutableAsync`) turns hooking off, clears the consent and pre-scan columns and ends an exception grant — it never writes a block or a grant — and *Remove game ▸ DeLine truncated
|
||||
|
||||
## Schema (v2 — hook architecture)
|
||||
|
||||
@@ -399,9 +399,6 @@ CREATE TABLE sensor_blobs (
|
||||
-- beta.14 (D49) also gpu_core_clock|gpu_mem_clock (MHz), gpu_fan (RPM), gpu_mem_temp (°C)
|
||||
-- and gpu_power_limit|gpu_thermal_limit (100 or 0 per tick, NVIDIA only) — a series name
|
||||
-- needs no migration
|
||||
-- since schema 0023 (2026-11-11, D102) also the ADVANCED series, every one under a name
|
||||
-- that starts with `adv.` (Application.Advanced.AdvancedMetricCatalog): NaN, not -1,
|
||||
-- for a tick with no reading, and read by FindAdvancedSensorsAsync only
|
||||
-- cpu_load / ram_mb / cpu_temp and sessions.avg_cpu_load, avg_cpu_temp, max_cpu_temp,
|
||||
-- avg_ram_mb were in schema 0001 with NO producer until 2026-09-21 (Telemetry.SystemTelemetrySource
|
||||
-- on the poller's tick). Rows before that date hold NULL, which is what they measured; no migration.
|
||||
@@ -467,7 +464,6 @@ switch's rule); integers are invariant-culture within an inclusive range; choice
|
||||
| `capture.run_elevated` | bool | `0` | | The App when it starts the Agent, and an Agent the logon task started — both BEFORE the Agent exists, through `Infrastructure.Startup.RunElevatedSetting` (one row, `PRAGMA query_only`, no version gate, anything but `1` is off) (D34, beta.10): on, Windows is asked for administrator rights at every Agent start (`01_ARCHITECTURE` ADR-9) |
|
||||
| `capture.min_session_s` | int | `30` | 5–600 | Agent, per session (FR-3.6) |
|
||||
| `telemetry.interval_ms` | int | `1000` | 500–2000 | Agent, per session (FR-3.5) |
|
||||
| `telemetry.advanced` | bool | `0` | | Agent, per session (FR-5.6, owner decision D101, 2026-11-11): **Advanced metrics**. On, a session holds the Agent's shared reader and stores its `adv.*` series and its `session_advanced` row (schema 0023); off — and any row that is not exactly `1` — nothing more is read or stored, and a session recorded while off has no row. Settings ▸ Recording (`18_GPU_VENDOR_APIS` §The switch) |
|
||||
| `retention.raw_sessions_per_game` | int | `20` | 0–10000; **0 = unlimited** | Agent, per session (§Retention) |
|
||||
| `retention.remove_uninstalled_games` | bool | `1` | | Agent, at every detection sweep (beta.19, D55, FR-1.8): on, an entry whose executable has been gone for ten minutes — its drive connected, the folder it was installed in still there — and that has no session and no anti-cheat block or exception is removed; off, it stays and reads *Not installed* (D41's behaviour) |
|
||||
| `update.channel` | choice | ~~`stable`~~ `auto` (beta.14, D47) | `auto` · `stable` · `beta` | UI (P4 PR-5 reads it: `beta` = GitHub pre-releases too; `auto` follows the running copy, a pre-release asking for pre-releases — `11_UPDATER` §The update audit) |
|
||||
@@ -495,39 +491,6 @@ Because Tier-1 and Tier-2 sessions carry different fields, every query that comp
|
||||
> axis (a gap's interval is stored as 0), so a series still drifts ahead of its sensors past each gap.
|
||||
> Sensor series are aligned to `t_ms` (milliseconds from `qpc_epoch`) and a tick with no reading is stored as
|
||||
> **−1** — never 0, which would be a reading — because temperatures, loads, power and memory are never negative.
|
||||
>
|
||||
> **A reading taken inside a game stands at the sample that carried it** (0.1.0-beta.49, owner decision D150): the
|
||||
> Overlay publishes about once a second and the Agent samples exactly once a second, so a publication waits for
|
||||
> the next sample — two may wait, the older is carried first (`PendingInGameReadings`). An `adv.*` point that
|
||||
> came from a game can therefore stand up to a second after its read; a tick with nothing waiting is NaN.
|
||||
>
|
||||
> **`t_ms` is the time axis; `hz` is the fallback** (written here 2026-11-14, owner decision D146 — the code cited
|
||||
> this rule before the page had it). Every series of a session is stored beside `t_ms`, which carries each
|
||||
> sample's own time, and the App draws against it; `hz` is read only for a row that has no `t_ms`
|
||||
> (`SessionSeriesLoader`). **Until 0.1.0-beta.48 `hz` was the constant 1**, whatever the samples did — and they
|
||||
> were not one second apart: the poller waited its whole interval *after* a poll's work. In the owner's ledger of
|
||||
> 2026-11-14, under a setting of 1000 ms, 180 of the 186 sessions long enough to tell have a median of 1.32 s
|
||||
> between samples; six have 1.0 s. **What takes the third of a second is not established.** Unelevated — the layers
|
||||
> composed as the Agent composes them, each read under a stopwatch — a poll takes about a millisecond. The two
|
||||
> sessions with no `cpu_temp` series (an Agent that was not elevated) are among the six, which points at the
|
||||
> sensor library's processor update, run on the poll's thread as administrator with PawnIO; but four sessions
|
||||
> that have the series kept one second, and the call itself was not timed (it needs elevation). Since 0.1.0-beta.48 the poller keeps a fixed period
|
||||
> (`TelemetryPoller.UntilNextTick`) and `hz` is the rate the session's samples had, measured from the samples
|
||||
> (`SessionFinalizer.SampleRate`: the gaps between the first and the last over the time between them, to a
|
||||
> thousandth; 1 for fewer than two) — so it is right for a session recovered from a `.partial` file as well.
|
||||
> Rows written before keep their 1.
|
||||
>
|
||||
> **The advanced series are the exception, and say so by their name (schema 0023, owner decision D102).** A series
|
||||
> whose name starts with `adv.` stores **NaN** for a tick with no reading: a motherboard's −12 V rail is negative, so
|
||||
> −1 cannot mark a gap, and most of its ticks are gaps — the sensor library is read every fifth. They go through a
|
||||
> second encoder, `ISeriesCodec.EncodeSparseFloat32`, which allows NaN and still refuses an infinity; **the rule
|
||||
> above is not relaxed**: `EncodeFloat32` throws on a NaN as before, because a frame time has no gaps. Both decode
|
||||
> with `DecodeFloat32`. `ISessionRepository.FindSensorsAsync` — what every summary, chart and export reads — leaves
|
||||
> the `adv.` rows out (`series NOT LIKE 'adv.%'`), since those readers drop every negative value as "no reading";
|
||||
> `FindAdvancedSensorsAsync` returns them with `t_ms` first. One session stores at most 256 of them
|
||||
> (`AdvancedSessionBuilder.MaxSeries`); what is beyond is counted in its directory, not stored.
|
||||
> **Size, measured 2026-11-11** on values shaped like the dev box's reader (17 series with a reading every tick, 41
|
||||
> with one every fifth): one hour is 816 KiB raw and **189 KiB stored** — well inside NFR-5's 3 MB an hour.
|
||||
|
||||
## The `.partial` file
|
||||
|
||||
@@ -550,16 +513,6 @@ Because Tier-1 and Tier-2 sessions carry different fields, every query that comp
|
||||
> | 6 `Note` | wall clock + UTF-8 text: a state transition | each transition |
|
||||
> | 7 `Touches` | N × `i64` QPC at which the host touched the target | each flush |
|
||||
> | 8 `SensorsWide` | the same samples under a 32-bit presence mask that carries the game process's memory (D43) | each flush, since beta.12 *(row added 2026-10-04)* |
|
||||
> | 9 `SensorsAdvanced` | the advanced readings of the samples of the type-8 chunk before it (D101): `u16` names, then per name `u16` bytes and UTF-8; `u32` samples, then per sample `i64` QPC, `u16` readings and per reading `u16` name, `f64` value. Each chunk carries its own names, so it reads without any earlier chunk | each flush **in which a sample carries any** — with Advanced metrics off, never; the file is then byte for byte what it was (2026-11-11) |
|
||||
> | 10 `AdvancedContext` | UTF-8 JSON (`AdvancedJson.OfContext`): the PC's facts, the session's, its series' directory, each source's state; the last one wins | the first flush after the recorder set it, and again only when it changed (2026-11-11) |
|
||||
>
|
||||
> **A chunk of a type the reader does not know is skipped, not the end of the file (owner decision D106,
|
||||
> 2026-11-11).** Its length and checksum have been verified by then, so it is a whole chunk a newer build wrote.
|
||||
> Until that day `_ => false` ended the read there, and a build one release older lost everything after the first
|
||||
> new chunk — the price types 9 and 10 would have charged a beta.38 reading a beta.39 file. A chunk of a KNOWN type
|
||||
> that does not parse still ends the read: that is a torn or a wrong file, not a newer one.
|
||||
> (`PartialSessionFileAdvancedTests`: an unknown type between two known ones; the same with its checksum broken;
|
||||
> a kill at every byte offset of a file that holds both new types.)
|
||||
>
|
||||
> Recovery (`PartialRecovery`): a file whose guid is already a row is deleted (the finalize had landed);
|
||||
> one under the minimum session length is discarded; one with no readable header is dropped; the rest
|
||||
@@ -765,43 +718,6 @@ Sequential embedded SQL (`Migrations/0001_init.sql`, `0002_*.sql`, …), applied
|
||||
> from its crash file (which carries no module list). `LatestVersion` is 21;
|
||||
> `LedgerDatabaseTests.ScriptTwentyOneAddsTheModuleSourcesColumnAndAnEarlierSessionHasNone`, the repository round trip.
|
||||
|
||||
> **`0023_advanced_metrics.sql` (2026-11-11, owner decisions D101 and D102) — what Advanced metrics stores.** Two
|
||||
> tables and **no column on `sessions`** — the first `CREATE TABLE` since 0001. Every read of a `sessions` row, the
|
||||
> JSON export and the bug bundle carry the whole row, and a driver profile does not belong in a bug bundle.
|
||||
> `machine_profiles(id, hash UNIQUE, facts_json, captured_at)` holds the facts of the PC, one row per distinct set
|
||||
> (`hash` = SHA-256 of `facts_json`); it stands beside `hardware_snapshots`, not in it, because that table's hash
|
||||
> feeds the trend's hardware-change markers and a set of facts that exists only while an option is on would raise a
|
||||
> marker each time the option is switched. `session_advanced(session_id PRIMARY KEY → sessions ON DELETE CASCADE,
|
||||
> machine_profile_id → machine_profiles, facts_json, stats_json, series_json)` holds one row per session **recorded
|
||||
> with the option on**: its facts and each source's state, the statistics of its advanced series (the form of
|
||||
> `sensor_stats_json`), and the directory of the series that are members of a family. **A session recorded with the
|
||||
> option off has no row** — that absence is how the App says "the option was off when this was recorded" rather than
|
||||
> "nothing answered" — and is never given one. The JSON is `Application.Advanced.AdvancedJson`'s (camel case, nulls
|
||||
> left out, a status by its name); writing is strict, reading is tolerant, and **only a fact whose catalog entry is
|
||||
> read may be written** (`AdvancedJson.Storable`), so no identifier reaches either table (D104). **Since
|
||||
> 0.1.0-beta.40 (train B) the same row holds what the game told its upscaler** — the session facts of the entries
|
||||
> whose reach is `Game`, after the driver's, and `sources.inGame` (`Reading`, `NothingSeen`, `NotHooked`; absent in
|
||||
> a row beta.39 wrote, which reads as "not said") — and its two series are `adv.ffx.upscale.frame_time_delta` and
|
||||
> `adv.ffx.memory_usage` in `sensor_blobs`. **Since 0.1.0-beta.43** `sources` may also hold `streamlineConstants`
|
||||
> and `fsrFrameGeneration` (`Read`, `NeverCalled`, `NotHooked`; `Application.Advanced.AdvancedInGameCall`) — what
|
||||
> became, in that session, of the two calls hooked only for Advanced metrics; both absent in a row written before,
|
||||
> and in a session not measured inside the game. **Since 0.1.0-beta.44** also `streamlineFeatureVersion` and
|
||||
> `streamlineFeatureRequirements`, the same three values for the two questions a game asks Streamline about a
|
||||
> feature — where `NeverCalled` is the usual one, a game asking while it starts — and the facts
|
||||
> `sl.feature.versions` and `sl.feature.requirements`, rows named `<feature> · <member>` in the vendor's words.
|
||||
> **Since 0.1.0-beta.45** six more keys, the same three values each — `streamlineFeatureSupported`,
|
||||
> `streamlineFeatureLoaded`, `streamlineSetFeatureLoaded`, `streamlineAllocateResources`, `streamlineFreeResources`,
|
||||
> `streamlineShutdown`, absent in every row written before — and the facts `sl.feature.support` and
|
||||
> `sl.feature.lifecycle`, rows named `<feature> · <call>` (`slShutdown` alone for the shutdowns); a count that
|
||||
> reached its ceiling is the text `≥ 15`. No column and no script: schema 23 as it was. A session deleted
|
||||
> takes its row with it; a profile no session points to is left, as a hardware snapshot is; the retention sweep
|
||||
> removes a session's `adv.` series with its other raw series and keeps its row. Written by the Agent only, in the
|
||||
> session's own transaction (`SqliteSessionRepository.InsertAdvancedAsync`). `LatestVersion` is 23;
|
||||
> `LedgerDatabaseTests.ScriptTwentyThreeCreatesTheTwoAdvancedTablesAndAnEarlierSessionHasNoRow` (whose helper now
|
||||
> undoes a script's `CREATE TABLE` and `CREATE INDEX` as well as its `ADD COLUMN`), the repository's four cases.
|
||||
> **Nothing produces a row yet**: the option that switches the reader on is the next pull request's.
|
||||
> **A beta.38 cannot open a ledger a later build migrated.**
|
||||
|
||||
> **`0022_dlss_nr.sql` (beta.34, 2026-11-06, owner decision D84) — DLSS 5's neural rendering, measured.** One REAL column,
|
||||
> ADD COLUMN only: `dlss_nr_pct`, the share (0–100) of the presents that drained a Streamline evaluation on which the game
|
||||
> evaluated `kFeatureDLSS_NR` (`Domain.Metrics.NeuralRendering`). Written by the recorder's aggregation
|
||||
|
||||
+5
-122
@@ -14,17 +14,15 @@ in beta.9 without a row here)*:
|
||||
|
||||
Created by the Overlay on init, opened by the Agent. Name is deliberately plain and identifiable (`19_SAFETY` — no obfuscated object names).
|
||||
|
||||
Layout — **~~four~~ ~~five~~ six regions** (layout 4 since 2026-09-27, beta.10: region 4 is new and the ring moved
|
||||
from `0xC0` to `0x100`; **layout 5 since 2026-11-11**, Advanced metrics train B: region 5 is new — twenty-three cache
|
||||
lines, where the four before it are one each — and the ring moved from `0x100` to `0x6C0`):
|
||||
Layout — **~~four~~ five regions, each exactly one 64-byte cache line before the ring** (layout 4 since
|
||||
2026-09-27, beta.10: region 4 is new and the ring moved from `0xC0` to `0x100`):
|
||||
|
||||
```
|
||||
[0x0000] FlShmHandshake 64 B write-once by the Overlay at init
|
||||
[0x0040] FlWriterState 64 B Overlay-written (writeIndex touched every present)
|
||||
[0x0080] FlControlBlock 64 B Agent-written
|
||||
[0x00C0] FlDisplayState 64 B Overlay-written, at most every 500 ms per chain (layout 4)
|
||||
[0x0100] FlAdvancedState 1472 B Overlay-written by its watchdog, once a second, only while the Agent asks (layout 5)
|
||||
[0x06C0] FlFrameRecord[capacity] (64 B each, power-of-two capacity)
|
||||
[0x0100] FlFrameRecord[capacity] (64 B each, power-of-two capacity)
|
||||
```
|
||||
|
||||
The header is split in two on purpose. The immutable handshake and the
|
||||
@@ -74,8 +72,7 @@ struct alignas(64) FlControlBlock { // Agent-written
|
||||
uint32_t overlayEnabled; // @8 in-game overlay draw toggle (v1.1)
|
||||
uint32_t guardTicks; // @12 completed guard evaluations, NOT a timer
|
||||
uint32_t logFlushRequested; // @16 a COUNTER: bumped by the Agent at session end; the watchdog flushes the native log on a change (17_HOOK_ENGINE §Native logging, 2026-09-06)
|
||||
uint32_t advancedRequested; // @20 0, or this session's request for Advanced metrics (D111): non-zero, new to this ring; written at attach, either way
|
||||
uint32_t reserved[10]; // @24..63 must be zero
|
||||
uint32_t reserved[11]; // @20..63 must be zero
|
||||
};
|
||||
|
||||
struct alignas(64) FlDisplayState { // Overlay-written (layout 4, 2026-09-27, beta.10)
|
||||
@@ -96,122 +93,9 @@ static_assert(sizeof(FlShmHandshake) == 64);
|
||||
static_assert(sizeof(FlWriterState) == 64);
|
||||
static_assert(sizeof(FlControlBlock) == 64);
|
||||
static_assert(sizeof(FlDisplayState) == 64);
|
||||
static_assert(sizeof(FlAdvancedState) == 1472); // region 5: fl_shm.h is its declaration, member by member
|
||||
static_assert(FL_SHM_DISPLAY_OFFSET == 0xC0 && FL_SHM_ADVANCED_OFFSET == 0x100 && FL_SHM_RING_OFFSET == 0x6C0 && FL_SHM_RING_OFFSET % 64 == 0);
|
||||
static_assert(FL_SHM_DISPLAY_OFFSET == 0xC0 && FL_SHM_RING_OFFSET == 0x100 && FL_SHM_RING_OFFSET % 64 == 0);
|
||||
```
|
||||
|
||||
**Region 5 — what a hooked game told its upscaler (layout 5, 2026-11-11; Advanced metrics train B, owner decisions
|
||||
D111 and D113; written by the Overlay's watchdog since 0.1.0-beta.40).** `18_GPU_VENDOR_APIS` §Train B is the design.
|
||||
What the region is, as a contract between the two sides:
|
||||
|
||||
- **Off means nothing is read and nothing is written.** `FlControlBlock.advancedRequested` is the Agent's word that
|
||||
this session records Advanced metrics — written at attach, either way, because the control block outlives a session
|
||||
(`ShmRingReader.SetAdvancedRequested`). While it is 0 the Overlay reads no field and installs no hook beyond what
|
||||
it did before, and writes nothing here: a ring nobody ever asked is zero from end to end (`fl_guard` checks every
|
||||
byte, with a target that sends everything), and `validMask == 0` means "nothing was read", never "the game used
|
||||
none of it".
|
||||
- **"On" is a request, not a 1** *(2026-11-12)*. A game outlives a session, and so do the summaries the Overlay keeps
|
||||
inside it — a range, a count, a mask of what was ever seen. So the word is a value no session of this ring used
|
||||
before (above the word as it stands and above the request the region last answered; never 0), the watchdog starts
|
||||
its summaries afresh at a value it has not seen, and every publication names the request it answers
|
||||
(`FlAdvancedState.request`, the word that was `reserved0`). The reader returns only a publication that names the
|
||||
value it wrote: what a second session of the same game finds in the region before the first tick is the first
|
||||
session's, and is not read. After an "off" the region keeps its last publication, untouched.
|
||||
- **One writer, once a second — on a grid since 0.1.0-beta.49 (owner decision D150).** The detours keep
|
||||
process-local accumulators; the watchdog copies them here at its **periodic** tick, one a second by the
|
||||
performance counter (`fl_watchdog_tick.h`). Until then it published at *every* tick, and a tick was a second
|
||||
and its own work after the one before — or at once, whenever the LoadLibrary detour woke the thread. So a
|
||||
session's publications fell behind the Agent's samples a little with every tick, and a woken tick's publication
|
||||
took the driver read with it and armed none: the publication after it was empty (0.4 to 16 % of a session's
|
||||
samples carried no report, HANDOFF item 46; under a loader that never stops, 35 720 publications in eight
|
||||
seconds and nine reads). A tick woken early still follows the request, installs and takes the census; it writes
|
||||
nothing here. **A request first seen on a woken tick is published by the periodic tick that follows, however
|
||||
soon that is**: a session's first publication may hold a moment's worth — one dispatch of a range that has two
|
||||
ends — and every one after it a second's. A reader takes ranges and "seen" words as *since the request*, which
|
||||
they are, and never reads a single publication as complete. No game thread writes the region, so the seqlock has a single writer: `seq` odd, the fields,
|
||||
`seq` even.
|
||||
- **A publication waits for a sample, and is not replaced while it waits** (0.1.0-beta.49, owner decision D150;
|
||||
the Agent's half). `SessionRecorder` looks at the region and at the telemetry poller about ten times a second
|
||||
and attaches a publication's readings to the newest sample it drains. It used to keep one set and overwrite it:
|
||||
a publication that landed just after a sample left that sample without a report, and at the next change of
|
||||
step the set that had waited was overwritten — one sample in five for minutes in the owner's session 223. Two
|
||||
sets now wait, the older is carried first (`PendingInGameReadings`): a session lacks a report at one sample at
|
||||
most when the two fall out of step, and loses no reading after it. With the sensor interval above a second
|
||||
more publications arrive than samples and the oldest is pushed out, as before.
|
||||
- **The reader keeps its last consistent copy** (`ShmRingReader.AdvancedState`): null until something was published
|
||||
for its request;
|
||||
the same copy while `seq` has not moved, without copying 1472 bytes again; and that copy still when the writer is
|
||||
inside on every attempt — a watchdog killed with its process leaves `seq` odd for good, and what it published
|
||||
before is still what the game said.
|
||||
- **Zero is "not read", never a value.** A Streamline `Boolean` and a DLSS preset are stored as the vendor's value
|
||||
plus one; a float as its bits, with `FL_ADV_FLOAT_NONE` for "none seen" — and, in `ffxNearBits` / `ffxFarBits` alone, `FL_ADV_FLOAT_INFINITE` (`0x7F800000`, +infinity's own bits) for a plane at infinity *(0.1.0-beta.42, owner decision D119: an engine with an infinite depth hands FSR `FLT_MAX` or +infinity for one plane; for Streamline `FLT_MAX` is "not set" and stays refused)* — the vendors' own sentinels are refused in
|
||||
the detour and never reach the region; a size of 0 is "not given".
|
||||
- **A per-frame value is summarised where it is seen**: a flag is an "ever seen" mask, a jitter the largest magnitude,
|
||||
a field of view its lowest and highest (D114), the reported frame time a count and a sum the watchdog drains.
|
||||
- **Sized once for the train's three releases.** The members ~~0.1.0-beta.41 and beta.42~~ ~~0.1.0-beta.42 and
|
||||
beta.43~~ 0.1.0-beta.43 and beta.44 fill *(renumbered twice on 2026-11-12 — D118: a fix release took beta.41;
|
||||
D122: the second step became two releases, and beta.42 fills none of them. The comments in `fl_shm.h` and
|
||||
`ShmLayout.cs` carry the new numbers since beta.42)* (`ffxFg*`,
|
||||
`sl*`, `features`) are declared now and stay zero until then, so those releases bump no layout. **The `sl*` group
|
||||
is filled since 0.1.0-beta.43** by the `slSetConstants` hook (`17_HOOK_ENGINE` §Hook inventory), under
|
||||
`FL_ADV_VALID_SL_CONSTANTS`: the call count of every viewport, and for the first viewport seen the resets, the
|
||||
jitter's largest magnitude, the motion-vector scale, the two depth planes, the field of view's range, the aspect
|
||||
ratio, and one bit per `Boolean` in each of two words — seen true, seen false. `FlHookFamily` gains
|
||||
`FL_HOOK_SL_CONSTANTS` (bit 13): the hook is in, which it is only in a process that was asked at least once.
|
||||
**The `ffxFg*` group is filled since the same release** by the `ffxConfigure` hook, under
|
||||
`FL_ADV_VALID_FFX_FG_CONFIG`: the frame-generation configures of the one module counted, three switches as "seen
|
||||
off / seen on" bit pairs (enabled, asynchronous, generated frames only), every flag any configure carried, and
|
||||
the last generation rectangle as left, top, width, height — **four `-1` for a rectangle with a negative side or
|
||||
one past 32,767**, never a clipped one. `FL_HOOK_FFX_CONFIGURE` (bit 14) is published when every ffx-api module
|
||||
the process loaded has its `ffxConfigure` patched.
|
||||
- **The feature slots are written since 0.1.0-beta.44**: `features` is twelve slots of twenty-four words — word 0
|
||||
the `sl::Feature` id plus one (0 is an empty slot), word 1 which of the two questions has an answer (bit 0 the
|
||||
version, bit 1 the requirements), then the two versions, the flags, three counts and four more versions, as
|
||||
`fl_shm.h` lays them out. Slots fill from 0 in the order the game first asked about each feature; **a new request
|
||||
does not empty them** — the one group that is a fact about the process and not about a session — and
|
||||
`FL_ADV_VALID_SL_FEATURES` stays set with them. `FL_HOOK_SL_FEATURE_VERSION` (bit 15) and
|
||||
`FL_HOOK_SL_FEATURE_REQUIREMENTS` (bit 16) are published with their patches, in a process that was asked.
|
||||
- **Word 1 of a slot carries more since 0.1.0-beta.45** (no layout change): bit 2 `slIsFeatureSupported` answered,
|
||||
with the `sl::Result` it gave in bits 8..15 (0 is `eOk`; a refusal is kept, it is the answer; `0xFF` a code a byte
|
||||
cannot carry); bit 3 `slIsFeatureLoaded` answered and bit 4 what it said; bit 5 the game switched the feature off
|
||||
through `slSetFeatureLoaded`, bit 6 on. **Bits 5 and 6 are a session's and a new request clears them**; every
|
||||
other bit of the word is a fact about the process and stays, as the slot does. A feature Streamline refused has
|
||||
a slot with only that word in it. `FL_HOOK_SL_FEATURE_SUPPORTED` (bit 17), `FL_HOOK_SL_FEATURE_LOADED` (18) and
|
||||
`FL_HOOK_SL_SET_FEATURE_LOADED` (19) are published with their patches.
|
||||
- **And two counts** (the same release): bits 16..19 of word 1 are how many times the game allocated the feature's
|
||||
resources (`slAllocateResources`), bits 20..23 how many times it freed them (`slFreeResources`) — each stops at
|
||||
15 — and `slShutdowns` (@308, taken from the three reserved words that ended the `sl::Constants` line; two remain)
|
||||
counts `slShutdown` calls, with `FL_ADV_VALID_SL_SHUTDOWN` (bit 6 of the mask) set once one was seen. All three
|
||||
are a session's and a new request clears them. `FL_HOOK_SL_ALLOCATE_RESOURCES` (bit 20),
|
||||
`FL_HOOK_SL_FREE_RESOURCES` (21) and `FL_HOOK_SL_SHUTDOWN` (22) are published with their patches.
|
||||
- **Reflex latency words (train C; written by the Overlay since 0.1.0-beta.47; owner decisions D136, D138).** The
|
||||
ten reserved words that ended the first line (@24..63) are `latState`, `latReads`, `latFrames` and seven sums:
|
||||
simulation, render submit, present, driver, OS render queue, GPU render, and the total from simulation start to
|
||||
GPU render end. **The layout is still 5**: no offset and no size moved, and the handshake's build id refuses a
|
||||
mismatched pair before either side reads the other. Unlike every other group here they are **not what the game
|
||||
passed to a call the Overlay hooks**: the Overlay makes a call of its own, about once a second, on the presenting
|
||||
thread, to the driver's two read-only getters, through an `nvapi64.dll` the game had already loaded
|
||||
(`17_HOOK_ENGINE` §Memory / latency). `latState`'s low byte is a `FlLatencyState` — no device, no module, refused
|
||||
(a module in the executable's own folder, D140), no getter, reading, error, slow (D141), faulted, stalled — and
|
||||
above it the driver's sleep status as switches *seen on* and *seen off* and the last frame-generation multiplier.
|
||||
`latFrames` and the sums are **of the newest read not yet published** — zero when no read was made since the
|
||||
publication before — so a reader divides one publication's sum by its frames and never adds publications up. A
|
||||
sum of all ones is a span some summed frame did not report. `FL_ADV_VALID_LATENCY` (bit 7 of the mask) is set once
|
||||
a read returned OK for the request; it is not one of "the game's calls were read", and `latState` is published
|
||||
whether or not it is set.
|
||||
- **Four more latency words (0.1.0-beta.48; owner decisions D142, D144).** The first line was full, so they are
|
||||
four of the seven reserved words that ended the `sl::DLSSOptions` line (@100..115; three remain, @116..127) —
|
||||
nothing of DLSS's, and **the layout is still 5** for the same reasons. `latGpuActiveSumUs` and `latGpuFrameSumUs`
|
||||
are the two times the driver works out itself — the graphics card's render time *excluding the idles in
|
||||
between* (`gpuActiveRenderTimeUs`) and one frame's GPU end to the next's (`gpuFrameTimeUs`) — summed over the
|
||||
frames of the newest read that gave one; `latGpuCounts` holds how many did, the first in its low half and the
|
||||
second in its high half, because a frame can give one and not the other. A frame that gives zero (an older
|
||||
driver leaves both zero) or more than a second is in neither the sum nor the count, and is still summed for the
|
||||
seven spans. `latMultipliersSeen` is the session's: bit n is set once the sleep status gave frame-generation
|
||||
multiplier n since the request, bit 31 standing for 31 and more; `latState` still carries the last one.
|
||||
- The Vulkan layer never writes it. `ShmLayoutMirrorTests.TheAdvancedStateMirrorMatches` checks every member's
|
||||
offset against `fl-layout-dump`; `ShmRingReaderTests` the three reads and that the request is stored either way.
|
||||
|
||||
**Region 4 — the presenting swap chain's display facts (layout 4, 2026-09-27, beta.10).** The owner asked for the game's
|
||||
window size and display mode (exclusive fullscreen / borderless / windowed) and the share of a session each took. The two
|
||||
facts only the process knows — whether the chain is in exclusive fullscreen, and which window it presents to — are
|
||||
@@ -518,7 +402,6 @@ Unchanged in spirit from v1, bumped to `v2` for the new message set.
|
||||
| `Shutdown` | UI→A | graceful stop → `ShutdownAck`, then the host stops (sessions finalize inside its grace window). *(Built 2026-09-13, PR-1b: `IAgentLifetime`, the host's under `--serve`, a logged no-op under `--console`.)* |
|
||||
| `DeleteSessions` | UI→A | **Added 2026-10-03 (beta.11, D40).** `{ gameId? }` — every session of that game, or of every game when it is null, with their segments, frame and sensor series and annotations (they cascade) → `DeleteSessionsAck { gameId?, games, sessions }`. `Error SessionRunning` and nothing deleted while a session of that game — of any game, for all — is being recorded (`CaptureOrchestrator.IsRecording` / `IsRecordingAny`). The client names no rows beyond the game: they are the Agent's (§Writer ownership). Additive: an older Agent answers `Error UnknownType`, which the App says as "restart the agent". Carries no safety fact. |
|
||||
| `SweepRetention` | UI→A | **no payload** — a trigger, like `UpdateRules`: the Agent applies `06_DATA_MODEL` §Retention to every game with the `retention.raw_sessions_per_game` it reads itself → `SweepRetentionAck { keep, games, sessions }` (`keep` 0 = unlimited, and then nothing was swept). *(Built 2026-09-15, P4 PR-7, for Tools ▸ Database maintenance: `Application.Recording.RetentionSweep` over `ISessionRepository.SweepRetentionAllAsync`, composed into `AgentCommandHandler` under `--serve`. The client names no number because the rows are the Agent's (§Writer ownership). Additive: an older Agent answers `Error UnknownType`, which the dialog reads as "restart the Agent". Carries no safety fact.)* |
|
||||
| `GetAdvancedMachine` | UI→A | **Added 2026-11-11 (Advanced PR-6, owner decisions D101/D107).** `{ factsHash? }` → `AdvancedMachineAck { ready, takenAtUnixMs, factsHash?, factsJson?, readings[{ series, value }], series[{ series, metricId, label }], nvapi, nvapiCode?, sensors, elevatedSensors }` — what the Agent's shared advanced reader last read about this PC (`18_GPU_VENDOR_APIS` §The page's feed). **The handler reads no sensor**: the answer is the reader's last snapshot, one reference, because the pipe's read loop awaits its handler and a driver call there would hold up `Ping` and `StopSession`; the one thing it awaits is the option, a `settings` row asked for at most every two seconds. **A request is the page's hold on the reader**: the first acquires it and each renews a five-second lease, so the App asks once a second while the page is open and nothing has to say that it closed (`Application.Ipc.AdvancedMachineResponder`). `ready: false` — held, not yet read — carries nothing else. `readings` are that tick's only: a slow source is read every few ticks and the client keeps the last value it saw; a value that is not a number is left out. `factsJson` is the PC's facts as the ledger stores them (`AdvancedJson.OfFacts`), left out when the request's `factsHash` is the Agent's own. The three states are `AdvancedSourceStatus` names; a name a client does not know reads as unknown. `Error AdvancedOff` while `telemetry.advanced` is off — nothing is read, and a hold a previous request took is let go at once. Additive, protocol 2: an older Agent answers `Error UnknownType`, which the page shows as such. Carries no safety fact and changes nothing. |
|
||||
| `SessionStarted` | A→UI | `{ sessionGuid, gameId, gameName, pid, tier, startedAt, hold? }` — **published once per session**: at the attach (tier 1, `startedAt` the attach), or — **since 2026-09-23** — at the first tick of a session held unhooked (tier 2, `startedAt` the session's start, `pid` 0 when the loop never opened the process, as a hooking-off hold never does). ~~a session that never attaches has no `SessionStarted`, only its `SessionCompleted` (tier 2)~~ — that was the beta.5 wire, and every hooking-off, refused or unreadable game read "Nothing is being captured." for as long as it ran. **`hold` (optional, tier 2 only)** is why nothing is measured: `{ reason, guardReason?, family?, signal?, hookingTurnedOff }` — the loop's `SessionEndReason` and, when the guard said anything but allow, its reason, family and signal: the same words the row's `capture_notes` will carry, so the live card and the summary read one sentence (`Formats.Tier2HoldReason` / `Tier2Reason`). The refusal's own event (`CaptureRefused` and the rest, below) goes out with this start rather than when the game exits, and is not repeated at the end |
|
||||
| `SessionHeld` | A→UI | **Added 2026-09-23.** 1 Hz while a client listens, for a session held unhooked only: `{ sessionGuid, elapsedS, gpuTempC?, cpuTempC?, gpuLoadPct?, cpuLoadPct?, gameVramDedicatedMb?, gameRamPrivateMb? }` — how long it has run and the machine's sensors (and since beta.12 the game process's own memory, read from outside it — optional, an older client ignores them). **Never `SessionProgress`**: its `presents5s`, `presentedQualifier` and `fgMode` are required, and zeros there would put measured-looking numbers on the wire for a session that measures nothing (rule 6 has nothing to show and shows nothing) |
|
||||
| `SessionProgress` | A→UI | 1 Hz: `{ sessionGuid, elapsedS, presents5s, presentedFps5s?, presentedQualifier, nativeFps5s?, displayedFps5s?, fgFactor?, fgMode, upscaler?, upscalerQuality?, upscalerDriverReported?, renderW/H?, outputW/H?, rtActive?, gpuTempC?, cpuTempC?, cpuLoadPct?, vramProcMb?, latencyUs?, fgRefusal?, fgRuntimeCensus?, gameVramDedicatedMb?, gameRamPrivateMb? }` (the last two added 2026-10-03, beta.12, optional: the game process's dedicated GPU memory and private working set, MiB, from the newest telemetry tick; `vramProcMb` stays reserved for the in-process figure and has no producer) — a 5 s rolling window over the ring through the SAME Domain calculators the row uses (`SessionProgressCalculator`, D13). **`upscalerQualityOverride` added 2026-10-19 (beta.24, D63), optional:** the mode an NVIDIA App override set when the driver reports it applied in the target and DLSS super resolution ran there — `performance`, `balanced`, `quality`, `ultra_performance`, `ultra_quality`, `dlaa`, or `override` when the driver's report alone does not settle the mode (the profile is the stored session's); absent otherwise. **`upscalerDriverReported` added 2026-09-21, optional:** `dlss` when the NVIDIA driver reports an NGX super-resolution feature created and evaluated in the target (`03_METRICS` §The driver-reported rung), so the live card says `DLSS (driver-reported)` where no hook can name the upscaler; identity only. **`cpuLoadPct` added 2026-09-21, optional** (CPU time busy over the last telemetry tick, 0–100; `cpuTempC` has a producer from the same date, present only when the Agent is elevated with PawnIO). **Two fields added 2026-09-14, both optional (an older client ignores them, §C):** `fgRefusal` is the row's `fg_refusal` (schema 0003) — present when `fgMode` names a technology and `fgFactor` is absent, so the live card can say "DLSS-G active — factor not counted" rather than N/A; `fgRuntimeCensus` is the raw census so the `fg_runtime_loaded` chip can name the module. **Rule 6 at the wire (2026-09-13):** `nativeFps5s` / `displayedFps5s` / `fgFactor` are present only when frame generation was measured in the window; otherwise `presentedFps5s` stands alone with `presentedQualifier` (`census_not_run` · `no_fg_runtime` · `fg_runtime_loaded` · `none_withheld`, the row's `presented_qualifier` from the same function). Every unmeasured field is absent, never 0. Suppressed when no client is connected |
|
||||
|
||||
+3
-73
@@ -38,7 +38,7 @@ Compare showed the icon alone)*. Light/Dark/System themes via `ApplicationThemeM
|
||||
> a refusal is a message box and exit 2. The viewer's folder is its own single-instance key, so it runs beside the
|
||||
> profile's App. D6 is unchanged: the Agent's `--data-dir` stays under `--console`.
|
||||
|
||||
**NavigationView items:** Dashboard · Games · Compare · Logs · *Advanced* (since 2026-11-11, D105: last in `MenuItems`, `Visibility` bound to `Services.AdvancedOption.IsOn` — there only while `telemetry.advanced` is on, §Advanced) — `Settings` lives in `FooterMenuItems`. Icons from `SymbolIcon` (Fluent System Icons; pick from the `SymbolRegular` enum — see 16 §Icons).
|
||||
**NavigationView items:** Dashboard · Games · Compare · Logs — `Settings` lives in `FooterMenuItems`. Icons from `SymbolIcon` (Fluent System Icons; pick from the `SymbolRegular` enum — see 16 §Icons).
|
||||
|
||||
**Menu bar**
|
||||
- **File:** Add game… · Import library (Steam / GOG / Epic / itch.io / Xbox *— since beta.33*) · Export ▸ (Session CSV / Session JSON / Chart PNG) · Exit
|
||||
@@ -850,77 +850,7 @@ Tail view of `ui-*.log` / `agent-*.log` (toggle), level filter, search (`ui:Auto
|
||||
> The status line says shown / total / file. Tests: `LogTailTests`, `LogsViewModelTests`, and the page renders in
|
||||
> `PagesLoadTests`.
|
||||
|
||||
### Advanced
|
||||
> **Built 2026-11-11 (Advanced PR-7; owner decisions D101, D105, D107).** `Pages/AdvancedPage` over
|
||||
> `ViewModels/AdvancedViewModel`, a `TabControl` of three tabs by what a value belongs to:
|
||||
>
|
||||
> - **This PC** — `Services.AdvancedMachineFeed`, watched between `Loaded` and `Unloaded` and while the page is visible
|
||||
> (a window hidden to the tray lets go too), which is what makes the Agent read with no game running and stop when the
|
||||
> page closes (D107). A status line says what the last request came to (`Advanced_State_*`: read at a time, waiting,
|
||||
> off, no agent, an older agent, a viewer); *About this PC* is the facts under the catalog's groups; *Right now* is a
|
||||
> `DataGrid` of every series with **the time it was read at** — a sensor read every fifth tick is never shown as new;
|
||||
> *Over time* is one catalog entry's last five minutes (`Charts/AdvancedSeriesChart`, a date axis).
|
||||
> - **Session** — a selector of the newest fifty sessions that have a `session_advanced` row
|
||||
> (`ISessionRepository.ListAdvancedAsync`), then the PC's facts as they were and the session's own, the stored
|
||||
> statistics, and the entry's series over the session (`SessionSeriesLoader.LoadAdvancedAsync`: `t_ms` is the clock,
|
||||
> NaN is left out, a negative reading is kept). A session whose raw series retention removed keeps its statistics
|
||||
> and says the series are gone. A session's summary has **Advanced metrics…** where the session has a row
|
||||
> (`SessionSummaryViewModel.HasAdvanced`); it asks for that session through `Services.AdvancedSelection` and
|
||||
> navigates, and a page already on screen takes the request at once.
|
||||
> - **Sources** — every entry of `AdvancedMetricCatalog`: its label, what it belongs to, its source, and *Read*, or
|
||||
> the reason it is not (`AdvReach_*`), or — live — why its source is silent (`AdvSource_*`). An entry read inside
|
||||
> the game (reach `Game`, 0.1.0-beta.40) says *Read inside a game FrameLedger measures, when the game makes the
|
||||
> call* (`Advanced_Status_InGame`): it is not a state of the PC. What became of those entries in one session is in
|
||||
> that session's sources line on the Session tab (`Advanced_InGameLine` with `AdvInGame_*`): read, the game made none
|
||||
> of the calls, or the session was not measured inside the game; a session stored before beta.40 has no such
|
||||
> sentence. **Since 0.1.0-beta.43** a session measured inside the game has one more
|
||||
> (`Advanced_InGameCallsLine` with `AdvInGameCall_*`): for what the game tells Streamline each frame and for how it
|
||||
> configures FSR frame generation, each *read*, *hooked - the game did not make the call*, or *not hooked - the
|
||||
> game did not load the library that has the call*. "Nothing here" then says which of the two it is.
|
||||
> **Since 0.1.0-beta.44** one more (`Advanced_InGameFeatureCallsLine`): for which version each Streamline feature
|
||||
> is and for what each requires, the same three — except that hooked and not seen reads *hooked - the game asks
|
||||
> this while it starts, and did not ask again after FrameLedger attached* (`AdvInGameCall_NotAskedAgain`,
|
||||
> `AdvancedLabels.InGameStartupCall`): the usual case, and not a finding about the game.
|
||||
> **Since 0.1.0-beta.45** one more, and one only for six calls (`Advanced_InGameMoreCallsLine`,
|
||||
> `AdvancedPresenter.MoreCalls`): *Streamline's other calls - read: …; hooked, the game did not make the call: …;
|
||||
> not hooked: …*, each call under its own name (`slIsFeatureSupported`, a function's name and so not translated)
|
||||
> in the group that is true of it, and the word for "none" where a group is empty. A session stored before has
|
||||
> none of the six and no such sentence. The catalog's `sl.init.preferences` carries a reason of its own
|
||||
> (`AdvReach_BeforeAttach`): *Not read: the game makes this call once, before FrameLedger is inside it*.
|
||||
>
|
||||
> **Words.** Every catalog entry, group, reason, source state and driver token is a `Strings.resx` key made from its own
|
||||
> name (`Adv_<id>`, `AdvGroup_*`, `AdvReach_*`, `AdvSource_*`, `AdvToken_*`) in `en`, `vi`, `ja`; the English label of
|
||||
> an entry **is** its summary in the catalog, and a test holds the two equal. A key that is not there — a token a
|
||||
> newer build stored — reads as the stored text, never as nothing (`ViewModels/AdvancedLabels`).
|
||||
> `ViewModels/AdvancedPresenter` is the pure mapping, each rule with a test.
|
||||
>
|
||||
> **Charts.** A family with more than eight members is drawn as its lowest, average and highest
|
||||
> (`AdvancedPresenter.MaxLines`), and the page says so; the table beside it lists every member. Lines differ by
|
||||
> pattern as well as colour (`ChartPatterns`).
|
||||
>
|
||||
> **A viewer** (`--data-dir`) has no Agent: *This PC* says so, the page opens on *Session*, and nothing is asked. The
|
||||
> navigation item is there when the copy's option is on **or the copy holds an advanced session** (`App.RunAsync`).
|
||||
>
|
||||
> **Accessibility** (`ACCESSIBILITY.md` §For contributors): one first-level heading, a level on every section; the two
|
||||
> templates are implicit by type, so no page-local resource key is named; every row type overrides `ToString` so an
|
||||
> item is read by its text; no `LiveSetting` — the readings change every second and are not announced; each chart has
|
||||
> its name and says its numbers are in the table beside it. Tests: `AdvancedPresenterTests`, `AdvancedViewModelTests`,
|
||||
> `PagesLoadTests` (the page among every surface, both themes, the contrast themes), `AccessibilityTests`
|
||||
> (`CtrlOneToFive…`), `GuideDocumentsTests`.
|
||||
|
||||
### Settings
|
||||
> **Advanced metrics (2026-11-11, owner decision D101; Advanced PR-5).** The Recording section has **Advanced metrics**
|
||||
> (`telemetry.advanced`, off by default, off in a viewer like every setting the Agent reads): one `ui:CardControl` with a
|
||||
> `ToggleSwitch`, under *Raw series kept per game*. Its text says what is read, that off reads and stores nothing more,
|
||||
> that it applies from the next session and that an earlier session is not filled in. The Agent reads it at each
|
||||
> session's start, so the row gets the usual "Applied. The capture agent reads it at the next session" strip. The
|
||||
> switch also sets `AdvancedOption.IsOn` at once, so the navigation item and Ctrl+6 follow it without a restart
|
||||
> (§Advanced, PR-7). With it, three texts that said what
|
||||
> an Agent running as administrator adds with PawnIO now name the processor's, the memory's and the motherboard's
|
||||
> sensors beside the CPU temperature: the Agent section's elevation line, the first run's Agent step, and the admin
|
||||
> mode's disclosure (`agent-admin-dialog/2`). Tests: `SettingsViewModelTests.AdvancedMetricsIsOffByDefaultAndItsToggleIsPersisted`,
|
||||
> `ViewerModeTests.EverySettingTheAgentReadsIsOffInAViewer`, `GuideDocumentsTests.TheSettingsPageOfTheGuideNamesEverySetting`.
|
||||
>
|
||||
> **beta.23 (owner decisions D60/D61).** The Games section has, under the Play button, **Show game artwork**
|
||||
> (`ui.game_art`, on) and **Colour the game page from its artwork** (`ui.game_art_tint`, on; disabled while the first is
|
||||
> off) — the game page's artwork and its band's colour (§Games › Game detail, *The header's cover*). Neither downloads
|
||||
@@ -961,7 +891,7 @@ Agent section: elevation state with a plain explanation of what elevation *optio
|
||||
|
||||
> **The admin mode, beta.10 (owner decision D34; `01_ARCHITECTURE` ADR-9).** The Agent section has a switch, *Run the agent
|
||||
> as administrator* (`capture.run_elevated`, off by default). Turning it on opens a `ContentDialog`
|
||||
> (`Services.AgentAdminPrompt`, text `FrameLedger.Shared`'s `Safety_AdminMode_*`, version `agent-admin-dialog/2` *(`/1` until 2026-11-11, when Advanced metrics widened what the option adds — D101)* in its
|
||||
> (`Services.AgentAdminPrompt`, text `FrameLedger.Shared`'s `Safety_AdminMode_*`, version `agent-admin-dialog/1` in its
|
||||
> corner) whose primary button is enabled only by ticking "I understand…" and whose default button keeps standard rights;
|
||||
> declined, nothing is written. Either way the row is written and the Agent restarts — asked to stop over the pipe, its
|
||||
> instance lock waited out, the connection's next round starting it the new way — **except under a running session**,
|
||||
@@ -1100,7 +1030,7 @@ the requirement was one bullet under §UX rules, and nothing checked it.
|
||||
|
||||
| Keys | Does | Where |
|
||||
|---|---|---|
|
||||
| **Ctrl+1 … Ctrl+5** (and the numeric keypad's 1–5); **Ctrl+6** since 2026-11-11 (D105) — the Advanced page, only while `AdvancedOption.IsOn`: `ShellShortcuts` refuses it otherwise, so the number stays free | Dashboard · Games · Compare · Logs · Settings — and since beta.35 the page's first control takes the focus once it is shown, its title (the page's first-level heading) said to a screen reader; before, the focus stayed where it was, often on the page that had just gone | `MainWindow` `InputBindings` → `MainWindowViewModel.NavigateToCommand` → `ShellShortcuts`, then `Services/PageFocus` (the shell tells it each page shown, from `NavigationView.Navigated`) |
|
||||
| **Ctrl+1 … Ctrl+5** (and the numeric keypad's 1–5) | Dashboard · Games · Compare · Logs · Settings — and since beta.35 the page's first control takes the focus once it is shown, its title (the page's first-level heading) said to a screen reader; before, the focus stayed where it was, often on the page that had just gone | `MainWindow` `InputBindings` → `MainWindowViewModel.NavigateToCommand` → `ShellShortcuts`, then `Services/PageFocus` (the shell tells it each page shown, from `NavigationView.Navigated`) |
|
||||
| **Alt**, **F10** | Focuses the menu bar; arrows and Enter walk File / Tools / Help | WPF `Menu`, nothing custom |
|
||||
| **Alt** + a menu's access key | Opens that menu — `_File` `_Tools` `_Help`; `_Tệp` `_Công cụ` `Trợ _giúp`; `ファイル(_F)` `ツール(_T)` `ヘルプ(_H)` *(row added 2026-11-09: the keys existed since P3 and this table did not name them)* | the `Menu_*` strings' `_` |
|
||||
| **Tab / Shift+Tab** | Moves through a page in reading order | layout order; no `TabIndex` overrides |
|
||||
|
||||
@@ -93,7 +93,7 @@ Tails the active files (shared read), level filter, text search, pause autoscrol
|
||||
2. **Bundle builder** creates `FrameLedger-bugreport-YYYYMMDD-HHmm.zip` in a user-chosen location:
|
||||
- `logs/` (last 7 days, redacted copies)
|
||||
- `sysinfo.json` (app + agent + **overlay build id**, OS build, CPU/GPU name, driver version, telemetry source, Vulkan layer state, PawnIO present?, elevation state, locale)
|
||||
- `overlay-<pid>-*.log` for the last hooked sessions, plus hook fault details and the ring's dropped/fault counters — these are what make injection bugs diagnosable at all. *(The file exists since 2026-09-06 — `17_HOOK_ENGINE` §Native logging: written at init, on the Agent's request at session end, and on the stop — and since 0.1.0-beta.42 by the Overlay's watchdog whenever something new was logged, so it is whole after a game that simply exits, with each install named by module and symbol and each descriptor type an ffx module was handed; `FAULT` lines carry the exception code and the hook's name, `UNHOOK_*` lines say per patch whether it was restored or left to a later hooker.)*
|
||||
- `overlay-<pid>-*.log` for the last hooked sessions, plus hook fault details and the ring's dropped/fault counters — these are what make injection bugs diagnosable at all. *(The file exists since 2026-09-06 — `17_HOOK_ENGINE` §Native logging: written at init, on the Agent's request at session end, and on the stop; `FAULT` lines carry the exception code and the hook's name, `UNHOOK_*` lines say per patch whether it was restored or left to a later hooker.)*
|
||||
- `settings.json` (sanitized — no paths)
|
||||
- optional checkbox: last session metadata + aggregates JSON (never raw blobs by default)
|
||||
- crash dumps included only when the user ticks the checkbox (size warning shown)
|
||||
|
||||
@@ -20,11 +20,6 @@ cmake --preset x64-release
|
||||
cmake --build --preset x64-release
|
||||
```
|
||||
|
||||
A third preset, **`x64-vs-analysis`** *(2026-11-11)*, builds nothing that ships: it has CMake write a Visual Studio
|
||||
solution (`build/native/x64-vs-analysis/FrameLedgerNative.slnx`, generator "Visual Studio 18 2026", tests and tools
|
||||
on) for Qodana's native report, which reads C++ through a solution (`13_CI_CD` §Qodana). It needs Visual Studio 18;
|
||||
the gate and the release never use it.
|
||||
|
||||
Targets:
|
||||
- `FrameLedger.Overlay` → `FrameLedger.Overlay.dll`
|
||||
- `FrameLedger.VkLayer` → `FrameLedger.VkLayer.dll` + `VkLayer_FRAMELEDGER_overlay.json`
|
||||
@@ -35,7 +30,6 @@ Targets:
|
||||
- `hook-harness` → the dummy **D3D11 + D3D12** app, WARP + composition swapchain so it runs headless on CI (`17_HOOK_ENGINE` §Test harness). D3D12 is device → command queue → swapchain, which is the acquisition asymmetry a D3D11-only fixture cannot exercise. ~~Vulkan and OpenGL modes to follow as those hooks land.~~ **`--vulkan --hold-presenting N` since 2026-09-06 (P1 item 3):** a real swapchain on a hidden window through the real loader, reached by `LoadLibraryW("vulkan-1.dll")` so only the vendored headers are needed and CI (no loader) still builds it; exit 77 = cannot run here, which the ctest reads as SKIP. **`--opengl --hold-presenting N` since the same day (P1 item 4):** a real context on a hidden window, `SwapBuffers`'d through gdi32 as a title does, on Microsoft's generic renderer — so it runs on CI.
|
||||
- `fl-probe-hookprofile` → build-profile probes for `/guard:cf` and `-D_HAS_EXCEPTIONS=0` (`20_OPEN_QUESTIONS` §H1/§H3)
|
||||
- `fl-probe-guard` → measures the Windows APIs the guard is built on, unelevated (`spike-notes.md` §1). Not the guard, and takes no injection rights.
|
||||
- `fl-probe-reflex` → the instrument of `spike-notes` §31 (2026-11-13, owner decision D132) — **since the owner said go (D136) it is built from the Overlay's own header, `FrameLedger.Overlay/include/fl_reflex.h`**, so its ctest runs the shipped call sequence with Control Flow Guard enforced; its `--real` also prints which image the two getter addresses lie in (`nvapi64_impl.dll`, not the `nvapi64.dll` that is asked). What it was written as: the call sequence Reflex route D would put into the Overlay — find `nvapi64.dll` only if the process already holds it, resolve the driver's two getters by interface id, call them — in an unshipped probe built with the Overlay's flags. `--stub` runs it against `fl_stub_nvapi64` → `nvapi64.dll` (a stand-in with knobs for a missing getter, an empty report, an error and a call that does not return; its outputs in a directory of their own, so that its `nvapi64.lib` is never beside the vendored one's name) and is ctest `fl_reflex_probe_stub`; `--real` runs it against the installed driver on an NVIDIA adapter, with the probe setting the latency markers a game would, in its own process — a measurement, never a test. It takes the vendored NVAPI headers' include directory and **does not link `nvapi64.lib`**. Nothing shipped includes its header.
|
||||
- `fl_stub_sl_interposer` → `sl.interposer.dll`, and `fl_stub_sl_common` → `sl.common.dll` (`src/native/tools/vendor-stubs/`). **Fixtures, never shipped**, built under `FL_BUILD_TOOLS`; nothing `12_BUILD` publishes references them. They export the **measured** vendor names from `docs/vendor-exports.json` so the Overlay's symbol resolution is observable, and the second is a **decoy** exporting the same name from a different module — without it, "we resolve module-scoped" is a property no test can falsify. Their **output filenames are the vendor's and their version blocks are ours**: `fl_add_version_resource` takes the real filename so a file called `sl.interposer.dll` in our build tree still says plainly that it is FrameLedger's, which `19_SAFETY` requires of everything we build.
|
||||
- `fl_stub_ffx_dx12` → `amd_fidelityfx_dx12.dll`, `fl_stub_ffx_upscaler` → `amd_fidelityfx_upscaler_dx12.dll`, `fl_stub_ffx_fg` → `amd_fidelityfx_framegeneration_dx12.dll` — the three AMD **leaves** — and `fl_stub_ffx_loader` → `amd_fidelityfx_loader_dx12.dll`, a **forwarding stand-in** bound to the two 2.x leaves through their FrameLedger-named *direct* entry — the way the real loader was measured to bypass the leaves' exports — so `--hold-presenting-ffx` can push every dispatch through a loader that is hooked along with the leaves and prove the count reads 1× (2026-09-04). Same rules as the Streamline stubs: fixtures, never shipped, vendor filenames with our version blocks. `fl_stub_ffx_fsr3_host` → `ffx_fsr3_x64.dll` (2026-09-05): the FSR 3.0 **host** facade, exporting the four names `SpeaksFsr3Host` probes for through the vendored `fsr3-v3.0.4` header's own `FFX_API`; `--ffx-topology fsr3host|fsr3host+mono` drives it, and `hookinventory-check` Pass C reads it as the export parser's second positive control.
|
||||
- **`fl_fidelityfx_headers`** → an INTERFACE target over the five vendored FidelityFX ffx-api headers (`src/native/third_party/fidelityfx/`, tag v2.3.0, MIT by exception). Three include directories because upstream's headers include each other by relative path; include directories only and nothing to link — no `.lib` is vendored — and `hookinventory-check` Pass C reads the Overlay's export table because `ffx_api.h` declares its entry points `__declspec(dllexport)` unconditionally.
|
||||
@@ -410,8 +404,6 @@ Seven self-test cases, both directions; `./tools/notice-check.ps1 -Fix` writes a
|
||||
13d. **`tools/wiki-build.ps1 -SelfTest`, then `-Check`** (beta.17, owner decisions D53/D54, 2026-10-07) — assembles the GitHub Wiki from `wiki/`, `guide/`, `LIMITATIONS.md` and (beta.35) `ACCESSIBILITY.md` into a temporary folder, as `wiki.yml` does at a release (`13_CI_CD` §wiki.yml), and fails on a link to a file, folder or section that does not exist, two sources for one page, a page that neither Home nor the sidebar leads to, a sidebar that lists the guide in another order than `guide/README.md`, a backticked repository path in a `wiki/` page that names nothing, and a version number written into a `wiki/` page (the footer says which release the wiki shows). ~~Nine~~ Ten self-test cases since beta.35 (the statement's page, D88), both directions
|
||||
14. `tools/changelog-check.ps1 -SelfTest` — nine cases, five expected RED. The live half needs a pull request's changed-file list and is supplied by `ci.yml`
|
||||
14b. `tools/release-notes.ps1 -SelfTest` — five cases over a fixture changelog (a dated and an undated section, a missing one, a prefix that must not match, an empty one), and since beta.24 three over a temporary tree: a version with its own `docs/changelog/<version>.md` is read from it, one without from `CHANGELOG.md`, a prefix of a file name is not that file. The live half needs a tag's version and runs in `release.yml`, where a missing or empty section is a red release (P4 PR-5)
|
||||
14e. **`tools/nvapi-readonly-check.ps1 -SelfTest`, then live** (owner decision D108, 2026-11-11) — every `NvAPI_*` call in `src/native/FrameLedger.NvapiBridge/src/fl_nvapi_bridge.cpp`, the one translation unit that links `nvapi64.lib` into a shipped binary, is on `tools/nvapi-allowed-calls.txt` and every name there is called; a name that sets, saves, restores, deletes, registers, resets, enables, disables or controls something is red **even when the list names it**, and so is one that returns an identifier (D104) — three reads the verb rule would refuse are exempt by name, each with its reason. Comments and string literals are taken out first, so a setter named in the comment that says it is never called is not a call. Seventeen self-test cases, both directions. Text only: it runs with or without the native build. `18_GPU_VENDOR_APIS` §Runtime policy's "never call a setter", which was a sentence until the bridge went from fourteen calls to forty-four
|
||||
14f. **`tools/overlay-fields-check.ps1 -SelfTest`, then live** (owner decision D116, 2026-11-12) — the same for the code loaded into a game: every member of a vendor's struct the Overlay reads for Advanced metrics is read in ONE header, `src/native/FrameLedger.Overlay/include/fl_adv_fields.h`, through parameters with fixed names, and is on `tools/overlay-allowed-fields.txt`; every name there is read; the parameters are not aliased and `->` reaches nothing but `desc` and the Overlay's own `region`; no other Overlay or Vulkan-layer source reads a listed member; **a camera's position, axes and matrices** (`cameraPos`, `cameraUp`, `cameraRight`, `cameraFwd`, the five matrices, `cameraPinholeOffset`, `cameraPosition`, `cameraForward`) **are named nowhere in those sources and not on the list, whatever the list says**; and neither `sl::Constants` nor `ffxDispatchDescFrameGenerationPrepareV2` is copied by value or measured with `sizeof`. Comments and string literals are taken out first. Nineteen self-test cases, both directions. Text only. It reads names, not types — which struct version carries a member is `17_HOOK_ENGINE` §Which struct version carries which field and ctest `fl_adv_fields`
|
||||
14d. **`tools/docs-split-check.ps1 -SelfTest`, then live** (beta.24, owner decision D66) — `CHANGELOG.md` holds no released section beside `[Unreleased]`; each `docs/changelog/<version>.md` holds one `## ` heading, its own `## [<version>] - date`, and no relative link (the App renders release notes as `CHANGELOG.md`); `CHANGELOG.md` and the files under `docs/changelog/`, and `docs/HANDOFF.md` and the files under `docs/handoff/` — and since PR-5 `docs/20_OPEN_QUESTIONS.md` and `docs/open-questions/`, `docs/spike-notes.md` and `docs/spike-notes/` — name each other in both directions. Eleven self-test cases, both directions
|
||||
14c. **`tools/buildid-check.ps1 -SelfTest`** (beta.18) — eight cases, both directions: a binary built from a dirty tree (`-dirty`, or the short form's `+`), one with no id, a missing one, and an expected id that is dirty or not an id are red. The live half needs the release's clean-checkout id and runs in `release.yml` over the published tree (§Release-time token substitution)
|
||||
15. `tools/resx-audit.ps1` — ~~**skipped loudly; it does not exist, and no `.resx` file does either**~~ **built 2026-09-13 (P3 PR-2)**: `-SelfTest` first (11 fixture cases, both directions), then the live pass over every `Strings.resx` family under `src/` — key sets equal across en/vi/ja, `Safety_*` in `ja` marked for review or signed, `Strings.Designer.cs` current with `tools/resx-gen.ps1`. A tree with no family is red (`09_I18N` §Translation workflow)
|
||||
|
||||
+8
-191
@@ -124,14 +124,11 @@ FrameLedger uses the **`poli0981/.github` ops repo** where its templates fit, an
|
||||
read `net10.0`; and for a construct it has not met, a pull request's run is not the evidence — a
|
||||
`workflow_dispatch` on the branch is, §C# 15 and the analyses.)*
|
||||
|
||||
### `qodana.yml` — push to `main`, pull requests into `main`, `workflow_dispatch` · **repo-local, built 2026-11-10 (D93); Qodana for .NET since 2026-11-11 (D99)**
|
||||
- ~~One job, `qodana`, on `ubuntu-latest` — the only Linux job in this repository, because the linter is a Linux
|
||||
container~~ Two jobs, on `windows-latest`, each a report of its own: **`native`** (*Qodana (native)*) has CMake
|
||||
write a Visual Studio solution and reads the C++ of `src/native` with `qodana-native.yaml`'s settings; and
|
||||
`managed` (*Qodana (managed)*): `JetBrains/qodana-action` (pinned to
|
||||
`v2026.2.2`'s commit; Dependabot moves the pin) runs **Qodana for .NET** in native mode over `FrameLedger.slnx`
|
||||
with `qodana.yaml`'s settings, after a `dotnet build`. No job here runs on Linux any more. §Qodana below says what
|
||||
it reads, what was changed from JetBrains' template and where an inspection is switched off.
|
||||
### `qodana.yml` — push to `main`, pull requests into `main`, `workflow_dispatch` · **repo-local, built 2026-11-10 (D93)**
|
||||
- One job, `qodana`, on `ubuntu-latest` — the only Linux job in this repository, because the linter is a Linux
|
||||
container: `JetBrains/qodana-action` (pinned to `v2026.2.2`'s commit; Dependabot moves the pin) runs Qodana Community
|
||||
for .NET over `FrameLedger.slnx` with `qodana.yaml`'s settings. §Qodana below says what it reads, what was changed
|
||||
from JetBrains' template and where an inspection is switched off.
|
||||
- **Advisory, with a gate of zero problems:** one problem turns the job red; it is not a required context.
|
||||
- `permissions: contents: read, checks: write, pull-requests: write` — the annotations and the one comment; granted to
|
||||
the job, the workflow grants none.
|
||||
@@ -357,10 +354,7 @@ from CI.
|
||||
writes into the checkout, since the scanner walks all of it (`build/`, with the sources CMake fetches there, `out/`,
|
||||
every `bin/` and `obj/`, `TestResults/`) — SonarCloud also drops what `.gitignore` names (the first run: "63 files
|
||||
ignored because of scm ignore settings"), and the patterns say it in the file rather than rely on that; the same
|
||||
duplication exclusions *(and, since 2026-11-12, `src/FrameLedger.Domain/Metrics/HookFamilies.cs`: the Domain's
|
||||
mirror of `FlHookFamily`, the same enum twice by design and held together by `MetricEnumMirrorTests`. The six
|
||||
members 0.1.0-beta.45 added to both were 3.7 % duplication on new code against the gate's 3 %, and failed the gate
|
||||
on the release's commit with no issue open)*; C++20; UTF-8; the OpenCover paths; the compilation database;
|
||||
duplication exclusions; C++20; UTF-8; the OpenCover paths; the compilation database;
|
||||
**`sonar.cs.roslyn.ignoreIssues`** — Roslynator, Meziantou, the VS threading and the .NET
|
||||
analyzers already gate the build, warnings as errors, and what they report at a lower severity is this project's
|
||||
choice, so only SonarCloud's own rules are imported; and **two rules ignored where they apply by design** — `S8417`
|
||||
@@ -450,7 +444,7 @@ the comment below; the rest are fixed in the same train (beta.24 PR-2).
|
||||
| `cpp:S935` `FlGetBuildId` returns no value | 1 | **False positive** | `FL_BUILD_ID` is defined by the build (`12_BUILD` §Version); the analysis compiles without it. |
|
||||
| `cpp:S3519` out-of-bounds `memcpy` | 1 | **False positive** | `fl_patch_check.h` reads the prologue of a function this DLL hooked, under SEH, by design (`17_HOOK_ENGINE` §Unhooking). |
|
||||
| `cpp:S836` garbage value returned | 1 | **False positive** | `hook-harness`'s `VtableOf` reads the vtable of a COM object it created itself. |
|
||||
| `csharpsquid:S3869` `DangerousGetHandle` | 1 | **Accept** | `ParentDump` passes the dump file's handle to `MiniDumpWriteDump` inside the `using` that owns the stream, on the same thread, so it cannot be released during the call; CsWin32 generates no `SafeHandle` overload here (`NativeMethods.json`: `useSafeHandles: false`). **Raised again 2026-11-12:** #398 moved that call into `TryWriteOnce` (the dump is now tried three times), and SonarCloud tracks an issue by where it is — the accepted one closed and a new one opened on the same expression, as a blocker on new code. Nothing about the call changed; it is to be accepted again (HANDOFF owner-only item 38 (j)). |
|
||||
| `csharpsquid:S3869` `DangerousGetHandle` | 1 | **Accept** | `ParentDump` passes the dump file's handle to `MiniDumpWriteDump` inside the `using` that owns the stream, on the same thread, so it cannot be released during the call; CsWin32 generates no `SafeHandle` overload here (`NativeMethods.json`: `useSafeHandles: false`). |
|
||||
| `cpp:S1669`, `cpp:S6191`, `csharpsquid:S4036`, `githubactions:S7637`, `csharpsquid:S2190`, `S3427`, `S8949` | 35 | **Fixed** in beta.24 PR-2 — 5 of the 23 `S1669` were in the vendored Vulkan headers and leave with the exclusions | — |
|
||||
|
||||
**`cpp:S5813`, the 17 accepted, and why each string is terminated** (lines as of beta.24):
|
||||
@@ -493,184 +487,7 @@ on `src/FrameLedger.Infrastructure/**/*` and `src/FrameLedger.Shared/**/*`, so n
|
||||
stop reappearing on pull requests. *(Since D68 the `S8417` and `S6640` rows are `SonarQube.Analysis.xml`'s, in the
|
||||
repository; `S6232`'s are not — a union read outside `LARGE_INTEGER` would be a finding — and its 24 stay marked.)*
|
||||
|
||||
## Qodana — `qodana.yml`, a workflow of its own (owner decisions D93, 2026-11-10; D99 and D100, 2026-11-11)
|
||||
|
||||
**Since 2026-11-11 the linter is Qodana for .NET, on the Ultimate licence (D99).** The owner took an Ultimate licence for
|
||||
the Qodana Cloud organisation and asked for Qodana over every language. So the linter is **Qodana for .NET**
|
||||
(`qodana-dotnet`: Rider's engine) where it was the Community one, in **native mode** on a Windows runner: no container,
|
||||
the projects built and loaded with the SDK the job installs from `global.json`, and no `EnableWindowsTargeting`.
|
||||
`qodana.yaml` names the linter and the mode (`withinDocker: false`); nothing is an action argument, so `qodana scan` on
|
||||
a developer's PC reads the same file. The job is `managed` — *Qodana (managed)* in a pull request's checks: checkout,
|
||||
`setup-dotnet`, the NuGet cache restored, `dotnet build -c Release` first — so that a build that fails is one red step
|
||||
with the compiler's own message, not a report of unresolved symbols — then the action, pinned by commit. No MSVC step,
|
||||
on purpose: it exports `Platform=x64`, which MSBuild reads as a solution platform. The linter's log says what the token
|
||||
bought: "Qodana license plan: Ultimate", and the Qodana Cloud project it is linked to (`frameledger`). Still advisory,
|
||||
still a gate of zero, still `main` and its pull requests alone. From here down to *As it was built* is the job as it
|
||||
is; below that is D93's own account, which is now history.
|
||||
|
||||
**Two reports (D99).** Asked how to gather the C# and the C++, the owner chose two reports from the start, and made a
|
||||
second Qodana Cloud project (`frameledger-cpp`, the `QODANA_TOKEN_NATIVE` secret). The managed report leaves
|
||||
`src/native` out; the native one (*The native report*, below) reads nothing else, so every file is in exactly one.
|
||||
|
||||
**What is read, and by what.**
|
||||
|
||||
| What | Read by | |
|
||||
|---|---|---|
|
||||
| The C#, XAML and `.resx` of the thirteen projects | `managed` | ReSharper's engine, as under D93 |
|
||||
| Markdown and XML around the solution | `managed` | the IntelliJ platform's own inspections — 23 and 10 results on the first run |
|
||||
| JetBrains' security rules over the C# — pattern rules for a process start, an SQL text and the like | `managed` | new with this linter (its OpenGrep plugin) — 36 results on the first run, every one read; the files they were read in are listed in `qodana.yaml`, so a new one is reported |
|
||||
| The C++ of `src/native` | `native` | ReSharper's C++ engine and the clang-tidy checks it bundles, over a Visual Studio solution CMake writes for it |
|
||||
| JSON and YAML, the workflows among them | nothing reported | whether the profile inspects them and found nothing, or does not inspect them, was not established; CodeQL's `actions` language reads the workflows |
|
||||
| PowerShell (`build.ps1`, `tools/`), CMake files, the HLSL shader | no linter of JetBrains' reads them here | SonarCloud reads the PowerShell |
|
||||
|
||||
**The first runs on this linter, and what was done (2026-11-11).** Run 42923079119 — the job with no settings beyond the
|
||||
solution: **3,953 problems** in 92 inspections, and 3,607 of them **hints**: the lowest level an IDE has, which the
|
||||
editor offers without underlining anything (this linter files them as `TYPO`, Qodana as *Low*). Meziantou's "name the
|
||||
parameter" 1,084 times, a trailing comma 979, a XAML binding whose `DataContext` the engine cannot know 414, the MVVM
|
||||
Toolkit's partial-property proposal 224, "invert `if`" 114 — and every other Roslyn analyzer message below the level
|
||||
this build makes an error. **Hints are off as a severity**, one group in `qodana.yaml` (`severity:TYPO`): the Community
|
||||
linter never reported them, and D93's rule is about warnings and suggestions. With that, run 42928814104: **347**.
|
||||
|
||||
| What | n | Done |
|
||||
|---|---|---|
|
||||
| `OverriddenWithSameValue` — a vi or ja value equal to the English one | 271 | off in `.editorconfig` (`[*.resx]`): product and technology names, units and format strings are not translated, and a ja safety string is the English verbatim until a reviewer signs it |
|
||||
| `csharp_injection_rule-CommandInjection` — a process started with something that is not a literal | 35 | **read, one by one** (below): 11 places in `src`, 24 in tests; one place was hardened. The rule stays on, and the files read are left out of the plugin's inspection by path in `qodana.yaml` (*How the security rules are scoped*, below), so a new file that starts a process is reported |
|
||||
| `MarkdownIncorrectTableFormatting` | 20 | off in `qodana.yaml`: Rider wants columns padded to one width; these tables are written to be diffed |
|
||||
| `XmlHighlighting` in `src/FrameLedger.App/app.manifest` | 10 | that file ignored for that inspection: the linter has no schema for a Windows application manifest |
|
||||
| `UnusedVariable.Compiler` and `RedundantUsingDirective` in `PrimaryDisplay.cs` | 6 | **the linter's own fault**, and the file is left as it is: resolving `PInvoke.EnumDisplaySettings(null, …)` — the `null`-to-`PCWSTR` conversion — the engine of this linter's build (QDNET-262.12299) fails an internal assertion (`IsStandardImplicitConversionFromExpression(conversion.Kind)`, in its `backend.log`), loses the method, and reports its three locals and the file's three usings as unused. The compiler builds the file with warnings as errors, and InspectCode 2026.2.3.1 and 2026.3.0 report nothing in it. Those two inspections are excluded for that one file in `qodana.yaml`, to be removed when a linter build reads it |
|
||||
| `MarkdownUnresolvedHeaderReference` | 3 | off in `qodana.yaml`: all three resolve on GitHub, whose anchor rule the linter does not follow (`#display-mode--both-tiers-beta10`) |
|
||||
| `csharp_injection_rule-SQLInjection` | 1 | the same: the one place assigns a constant command text and binds every value as a parameter, as every statement in this repository does; its file is listed with the others |
|
||||
| `RedundantBoolCompare`, in a test | 1 | fixed — the expression also carried a clause its first half implied |
|
||||
|
||||
With those settled, run 42940926340 (2026-11-11, this pull request's branch, the whole solution): **no problem
|
||||
reported** — the gate's zero, on this linter.
|
||||
|
||||
**How the security rules are scoped — by the plugin's one inspection, not by a rule.** Every result of the
|
||||
OpenGrep plugin's several hundred rules is produced by one inspection, `OpenGrepInspection`; a rule's own id
|
||||
(`csharp_injection_rule-CommandInjection`) is in the report and is honoured nowhere. Three runs measured it — a
|
||||
profile entry's `ignore` (42932842462), an `exclude` path under the rule's id (42935752891), `enabled: false`
|
||||
on the rule (42938295264): all 36 results stood each time, and the linter's log shows why — the plugin hands its
|
||||
server every rule file whatever the profile says. What the plugin's inspection does honour is a path: an
|
||||
`exclude` entry named `OpenGrepInspection` (its scopes are in the report's `log/effective.profile.xml`). So the
|
||||
eleven files of `src` the results were read in, and `tests`, are listed there — and in the run above the
|
||||
inspection was performed on 943 files, where it had been 1,308, and reported nothing: it is on, and it reads
|
||||
what is not listed. The price is stated in `qodana.yaml`: a listed file is left out of **all** of the plugin's
|
||||
rules, not only the one that fired. The plugin is also most of the job's time — about six of its fifteen
|
||||
minutes.
|
||||
|
||||
**A second tripwire, in the gate: `ProcessStartSitesTests`.** Qodana is advisory, and its rule is a pattern for
|
||||
`Process.Start`. The test sweeps `src` for every way a process is started here — `Process.Start`, a
|
||||
`ProcessStartInfo`, `CreateProcessWithTokenW` through CsWin32, and the registration of the logon task — and fails
|
||||
on a file that is not in its list, until that file has been read and listed. `Startup/UnelevatedProcess`, which
|
||||
the rule never saw, is in it.
|
||||
|
||||
**Every place that starts a process, as read on 2026-11-11.** The rule is a pattern, not a data flow: it reports any
|
||||
`Process.Start` whose argument is not a literal. What matters at each is what is started and where its path and
|
||||
arguments come from.
|
||||
|
||||
| Place | What it starts | Where the path and the arguments come from |
|
||||
|---|---|---|
|
||||
| `App/Services/AgentLauncher` | `FrameLedger.Agent.exe` | the file beside the App (`AppContext.BaseDirectory`); arguments the App builds (`--serve`, the data folder) |
|
||||
| `App/Services/AgentTool` | the same Agent, with one maintenance flag | a constant at each of its two callers (`--install-task`, the Settings page's flags) |
|
||||
| `Infrastructure/Startup/AgentElevation` | the Agent, elevated (`runas`) | the Agent's own path; `--serve --for-user <this user's SID>` |
|
||||
| `Infrastructure/Startup/LogonTask` | nothing itself — it registers the logon task, whose action Windows starts at sign-in | the Agent's path and constant arguments (`--serve`), into a Task Scheduler definition for this user, at the lowest privileges |
|
||||
| `Infrastructure/Diagnostics/CrashDumpWriter` | this process's own executable, as the dumper | `Environment.ProcessPath`; an `ArgumentList`, no shell |
|
||||
| `Infrastructure/Capture/ProcessLauncher` | the game | the executable the user added and enabled hooking for, and the launch arguments the user wrote for it; no shell |
|
||||
| `App/Services/ShellStarter` | a game, directly or through its store (`steam://…`, `explorer.exe shell:AppsFolder\<AUMID>`) | the launch `GamePlayer` resolves from the record of a game the user added (D59, D80) |
|
||||
| `App/Services/Explorer` | `explorer.exe` on a folder or a file | a quoted path of FrameLedger's own: the data folder, the logs, a bug report's zip, the licences folder |
|
||||
| `App/Services/ShellUrlOpener` | the browser or the mail client | the project's own pages, or a Markdown link `MarkdownLinks` has already held to `http`, `https` and `mailto`. **Hardened here**: the opener now refuses any other scheme itself (`ShellUrlOpenerTests`) — the shell runs whatever it is handed, and a `file:` address is a program |
|
||||
| `App/ViewModels/SettingsViewModel` | the browser | one constant address |
|
||||
| `Infrastructure/Startup/UnelevatedProcess` | the Agent or a game with the shell's token, from an elevated process (`CreateProcessWithTokenW`) | its two callers above, `AgentLauncher` and `ProcessLauncher` — not a `Process.Start`, so the rule did not see it; the sweep does |
|
||||
|
||||
None takes a value from outside the PC or from a file FrameLedger did not write, except the game's own path and
|
||||
arguments — which starting the game the user chose is.
|
||||
|
||||
**The native report — `qodana-native.yaml`, the job `native` (D99, 2026-11-11).** The C++ of `src/native`, read by
|
||||
the same linter — Qodana for .NET, whose C++ is ReSharper C++ — in native mode on a Windows runner. It is the only
|
||||
linter of JetBrains' that can: the native layer is MSVC-only, and the two C/C++ linters (`qodana-cpp`,
|
||||
`qodana-clang`) are Linux images. It reads C++ through a Visual Studio solution, and `src/native` is a CMake tree, so
|
||||
the job has CMake write one first: the preset **`x64-vs-analysis`** (generator "Visual Studio 18 2026", tests and
|
||||
tools on) puts `FrameLedgerNative.slnx` under `build/native/x64-vs-analysis`, and the job builds from it the one
|
||||
target whose output is a header (`fl_ac_floor_gen`, the blocklist floor). Nothing else is compiled, and nothing from
|
||||
that tree ships. Then the action, with `--config qodana-native.yaml`: the solution, `RelWithDebInfo` and `x64` — the
|
||||
flags the shipped binaries are built with — and, left out by path, what is not FrameLedger's code (the build tree,
|
||||
`third_party`, the vendor stubs, a compiled shader as a byte array). Its own results folder, cache keys and artifact
|
||||
(`qodana-report-native`), and the Qodana Cloud project `frameledger-cpp` through `QODANA_TOKEN_NATIVE`. It posts no
|
||||
comment and no annotations — a second job of the same linter would overwrite the managed job's — so its result is the
|
||||
job's own status and its report. Advisory, and a gate of zero, like the other.
|
||||
|
||||
**What it runs** is ReSharper's C++ inspections and, through them, the clang-tidy checks and clang diagnostics that
|
||||
engine bundles. clang never builds this code — MSVC does, with `/W4 /WX` — so what clang says is read as advice. Every
|
||||
one of them has a key in `.editorconfig` (`resharper_cpp_…_highlighting`; a clang-tidy check's is
|
||||
`resharper_cpp_clang_tidy_<check>_highlighting`), so D100's rule holds without a second file: no `.clang-tidy`.
|
||||
|
||||
**Its first runs, and what was done.** Run 42923079119: **4,695 problems**, 4,040 of them hints, which are off as on
|
||||
the managed side. Run 42928814104: **655** — **494 distinct**, because a source file compiled into three targets is
|
||||
reported three times.
|
||||
|
||||
| What | distinct | Done |
|
||||
|---|---|---|
|
||||
| A choice this code made, off for the native tree: where the compiler pads a struct (46); MSVC's own keywords, `__try` among them (54); a function pointer got by name cast to its real type, through `void*` (55); `reinterpret_cast` where memory is read as something else (5); `std::cmp_less` proposed for comparisons that already cast (20); a `default:` under a full enum switch (3); a copied verdict (4); the moves of a type that owns a handle (11); a zeroed out-parameter enum (8); an enum's width (5); "can be made const / constexpr / static" (52); "possibly unused `#include`" (15) | 278 | off in `.editorconfig`, each with its reason. Of the fifteen includes two were unused and were removed; the others are a file including what it uses although another header already brings it |
|
||||
| A newer idiom proposed for working code — a range-for, `std::ranges`, `any_of`, `starts_with`, a raw string, an `if` with an initialiser | 53 | off: the native code is written to be read beside the hook path, an index and a plain loop |
|
||||
| **The engine misreading**: `std::atomic_ref<T>::fetch_or` as an expression without side effects (7); a Win32, D3D12 or ffx-api structure zero-initialised and then filled field by field as "always rewritten" and "assigned, never used" (15); a test of a `constexpr` function as a redundant argument (3) | 25 | off, with what the engine gets wrong written beside the keys |
|
||||
| Fields nothing names, in a structure Windows defines and the SDK's headers do not give (`RTL_PROCESS_MODULE_INFORMATION`, `PROCESS_MEMORY_COUNTERS_EX2`) and in a test's stand-in for a Vulkan object | 25 | off for those four files: the fields are what puts the others at their offsets |
|
||||
| `%lu` with an `NvU32`, in `fl-probe-nvapi` | 19 | off for that file: NVAPI's header makes `NvU32` an `unsigned int` under clang and an `unsigned long` under MSVC — the linter's compiler, not the build's |
|
||||
| The probes, the harness and the tests: an unchecked `printf` (35), `atoi` on the harness's own arguments (20), a `&pointer` handed to a `void*` parameter (7), a printf-shaped helper (4), a fake handle built from a number (4), a test's fixtures (4), `layout_test`'s run-time checks of compile-time facts (3), a macro that pastes a name (1) | 78 | off for `tools` and `tests` |
|
||||
| Code loaded into a game (below) | 7 | kept as it is, off for those files; one of them is dead code, recorded for the owner |
|
||||
| **Fixed**: `sizeof(a) / sizeof(a[0])` → `std::size(a)` (4); a multiplication done in a narrower type than the one it is stored in or compared with (2: a constant in the guard's sources, a test); a member function, and a type alias, nothing used (3) | 9 | in the code; none changes what a shipped binary does |
|
||||
|
||||
With those settled, run 42942068024 — the first with these settings — reported **one** problem: `LogNoteW`, now by
|
||||
ReSharper's own inspection where clang's had said it before (below). And run 42943094415 (2026-11-11, this pull
|
||||
request's branch): **no problem reported** — the gate's zero, in the native report too.
|
||||
|
||||
**Code loaded into a game — the Overlay, the Vulkan layer, the shared-memory headers, the guard's rule matcher.**
|
||||
D100: there only a defect is fixed, in a pull request of its own with the hook's overhead measured (rule 5,
|
||||
`14_TESTING` §Hook overhead), and a proposal about style is not acted on. About a quarter of the 655 results were in
|
||||
those files; nearly all of them are the tree-wide kinds above. **The report found no defect there.** What is
|
||||
particular to them, read and kept: two `if` chains whose arms have the same body and are different cases, each with
|
||||
its comment (`dllmain.cpp`); MinHook's `MH_ALL_HOOKS`, which is `NULL` by its header; a retired enumerator kept so
|
||||
that its bit is not reused; `slSetTag`, deprecated by a header whose replacement no measured module exports;
|
||||
`ResolveTolerance` clearing its out-parameter with `memset`, as `ResetRules` does — a `Tolerance` is flags whose
|
||||
default initialisers are zero. And one thing that is not as it should be: **`LogNoteW` in `dllmain.cpp`, which nothing
|
||||
calls** — dead code. It is not a defect, so D100 leaves its removal to the owner (HANDOFF); until then that one file
|
||||
is not read for an unused function (`.editorconfig` says so, in a section to be removed with it).
|
||||
|
||||
**"Zero" has to mean "analysed".** A report with no problem cannot tell a clean tree from one the linter did not
|
||||
read. So the settings were proved on a branch that puts back three of the things fixed here — the unused alias, the
|
||||
unused member function, the narrow multiplication. Run 42942390715 reported exactly those three, each by the
|
||||
inspection that had found it the first time (`CppTypeAliasNeverUsed` in `tools/fl-probe-interposer/main.cpp`;
|
||||
`clang-diagnostic-unused-member-function` and `bugprone-implicit-widening-of-multiplication-result` in
|
||||
`tests/ring_test.cpp`), and `LogNoteW`, and nothing else. The branch was deleted. Do the same before trusting a
|
||||
zero after a change to the preset, the settings or the linter's version.
|
||||
|
||||
**What it does not read.** CMake files and PowerShell have no inspection in this linter (SonarCloud reads the
|
||||
PowerShell); the HLSL shader and the `.def` file are not C++. CodeQL (`analyze (cpp, manual)`, a required check) and
|
||||
SonarCloud go on reading the C++ as before: this is a third reader, and the only one of the three that is ReSharper's.
|
||||
|
||||
**Where an inspection is switched off: by the engine that raised it (D100, amending D93's "never in `qodana.yaml`").**
|
||||
What Qodana reports is fixed, unless the inspection argues with a choice this project made; then it is off, with the
|
||||
reason on the line above — in the place the engine that raised it reads:
|
||||
|
||||
- **ReSharper's** — the C#, the XAML, the `.resx`, and the C++ of the native report with the clang-tidy checks it
|
||||
runs — in **`.editorconfig`** (`resharper_*_highlighting`), where Rider and ReSharper in the editor read it too:
|
||||
sixty-four keys for the managed code, fifty-four lines for the C++, some of them for a folder or a file alone.
|
||||
- **What has no key there** — in **`qodana.yaml`**: a whole severity (the hints) and the IntelliJ platform's Markdown
|
||||
and XML inspections under `profile.inspections`; under `exclude`, by inspection and path, the files JetBrains'
|
||||
security rules were read in and a file the linter itself fails on.
|
||||
- **What is not FrameLedger's code** is left out by path (`exclude`): `SonarQube.Analysis.xml`'s list, for its reasons.
|
||||
|
||||
**What it does not use, and what happens if the licence lapses.** Quick-fixes (the linter would push commits — the job
|
||||
has no `contents: write`, and a change nobody read is not wanted), code coverage in Qodana (the gate's coverage and
|
||||
SonarCloud's already read the same reports) and FlexInspect are Ultimate features this job leaves alone. Without a
|
||||
valid licence the linter does not start, so the job is red — advisory, never a blocked merge; the way back is
|
||||
`linter: qodana-cdnet` with the job on `ubuntu-latest`, as it ran until beta.37.
|
||||
|
||||
**Running it on a developer's PC.** `qodana scan` in the repository root reads `qodana.yaml`, downloads the linter and
|
||||
needs the project's token in `QODANA_TOKEN` — the Ultimate linter checks the licence. Without a token, InspectCode
|
||||
still gives ReSharper's part (*As it was built*, below), with `--toolset-path` at the 11.0 SDK's `MSBuild.dll`; the
|
||||
Markdown, XML and security results are the Rider linter's alone.
|
||||
|
||||
**As it was built — the Community linter, 2026-11-10 to beta.37 (D93).** Kept as written; where it says *is*, read *was*.
|
||||
## Qodana — `qodana.yml`, a workflow of its own (owner decision D93, 2026-11-10)
|
||||
|
||||
**D93 — Qodana reads the C# and the XAML from CI.** The owner made the project on Qodana Cloud, set the `QODANA_TOKEN`
|
||||
secret (2026-11-10) and asked for Qodana in CI from the workflow JetBrains gives, changed where it had to be, with what
|
||||
|
||||
+2
-40
@@ -28,10 +28,9 @@ The anti-cheat guard is the one component where a bug can cost someone an accoun
|
||||
- **Ring buffer:** SPSC correctness under a hammering writer thread; seqlock torn-read detection; wrap and overwrite-oldest semantics; power-of-two capacity assumptions. Include the **one-full-lap case**: a reader stalled exactly `capacity` records must not validate a different frame as unchanged (this is what the never-reset `seq` counter defends, `07_IPC` §Protocol rules).
|
||||
- **Drop accounting:** the reader-side computation (`writeIndex - readIndex > capacity`) reports the right count and resumes at the right index. The writer has no drop counter to test — by design.
|
||||
- **Torn records produce gap markers,** not silently shortened streams; a golden test asserts the gap does not appear as a stutter.
|
||||
- **Record and header layout:** `static_assert(sizeof(...) == 64)` and `offsetof` assertions for `FlFrameRecord` **and all ~~three~~ ~~four~~ five header structs** *(five since layout 5, 2026-11-11: `FlAdvancedState`, 1472 bytes; what reads and writes it is tested at four levels since 0.1.0-beta.40 — `fl_adv_fields` the Overlay's header alone, `fl_guard` `[advanced]` the injected Overlay with the word off and on, `InGameAdvancedSamplerTests` / `CaptureSessionTests` / `SessionRecorderTests` what the Agent makes of a publication, and `AgentEndToEndTests.WhatTheGameTellsFsrIsStoredOnlyByASessionThatRecordsAdvancedMetrics` the shipped Agent, the real Overlay and the harness: two sessions of one target, the first storing nothing of it)* (`FlShmHandshake`, `FlWriterState`, `FlControlBlock`, and `FlDisplayState` since layout 4, beta.10) — plus D33's `FlTolerance`, mirrored the same way *(corrected 2026-10-04)* — the Agent reads across the process boundary in every one of them. Both halves exist as of 2026-08-05: the native side is `layout_test.cpp` plus the `static_assert`s (ctest `fl_shm_layout`), and the runtime offset dump from `tools/fl-layout-dump` is consumed by `ShmLayoutMirrorTests`, which walks the field list in **both directions** and additionally asserts blittability — `Marshal.SizeOf` and every offset stay correct for a mirror that uses `[MarshalAs(ByValTStr)] string`, while `Unsafe.SizeOf` drops from 64 to 40 and the struct can no longer be read from a mapped view.
|
||||
- **Record and header layout:** `static_assert(sizeof(...) == 64)` and `offsetof` assertions for `FlFrameRecord` **and all ~~three~~ four header structs** (`FlShmHandshake`, `FlWriterState`, `FlControlBlock`, and `FlDisplayState` since layout 4, beta.10) — plus D33's `FlTolerance`, mirrored the same way *(corrected 2026-10-04)* — the Agent reads across the process boundary in every one of them. Both halves exist as of 2026-08-05: the native side is `layout_test.cpp` plus the `static_assert`s (ctest `fl_shm_layout`), and the runtime offset dump from `tools/fl-layout-dump` is consumed by `ShmLayoutMirrorTests`, which walks the field list in **both directions** and additionally asserts blittability — `Marshal.SizeOf` and every offset stay correct for a mirror that uses `[MarshalAs(ByValTStr)] string`, while `Unsafe.SizeOf` drops from 64 to 40 and the struct can no longer be read from a mapped view.
|
||||
- **Fault policy:** injected SEH faults in a fake hook body → counter increments, original still called, self-disable at 3.
|
||||
- **Hook index verification, by behaviour.** A vtable slot carries no identity, so "check that slot 8 *is* `Present`" is not a question the runtime can answer — the earlier wording here required something unimplementable. What is answerable: patch the slot, call the method, see whether the detour ran (`17_HOOK_ENGINE` §Getting vtable addresses; proved for slots 8, 13 and 22 in `spike-notes.md` §H4). Runs headless on CI via WARP and `CreateSwapChainForComposition`. A deliberate mismatch aborts installation instead of patching.
|
||||
- **A run that was cut short is not a pass** (2026-11-13). ctest calls a test passed when its process exits with 0, and on that day the development PC's security software removed a freshly linked `fl_guard_test.exe` while the gate ran: ctest printed `fl_guard ... Passed 0.66 sec` for a suite that takes three minutes, and the gate went red only because the next test runs the same executable and could not find it. So **every native test now names the line it ends on** — `fl_test_completes(<test> <regex>…)`, or `fl_catch2_test_completes(<test>…)` for a Catch2 executable (its `All tests passed (` line, or its summary row when a case was skipped, and never a row that names a failure) — and ctest requires that line (`PASS_REGULAR_EXPRESSION`; the helpers and the reasons are in `src/native/CMakeLists.txt`, above `enable_testing()`). Three things hold it: **the configure fails** when a test in `tests/` or `tools/` was registered without one (tried: a test added bare stops CMake with its name); **four canary tests** print what a Catch2 run would — nothing, its last line, a row with a skipped case, a row with a failure beside "passed" — through the same helper, and the two that must be red are `WILL_FAIL`; and the tests that were passing on a line printed in the *middle* of their run (`fl_nvapi_bridge`, `fl_process_stats`, `fl_nvapi_probe`, `fl_signer_probe`) now need that line and, after it, their last one. For `fl_nvapi_probe` this also closes what `fl_nvapi_bridge` was fixed for on 2026-09-25: a pass expression makes ctest ignore the exit code, so a run that printed its branch and then `FAILED` passed. `fl_signer_probe` accepts either ending — its criterion was always that the answers are printed. A `SKIP_RETURN_CODE` still wins over a missing line. **Not covered**: the managed tests (`dotnet test` reports a host that died) and a process that is stopped *after* printing its last line.
|
||||
- **Every probe must be shown to fail.** A probe that ends in an unconditional assertion is green by construction and its ctest is decorative — `fl_proxy_swapchain` shipped in exactly that state. Before a probe counts as a regression net, break the thing it watches and watch it go red.
|
||||
|
||||
## Managed unit tests
|
||||
@@ -146,7 +145,7 @@ own work item on the STA thread and puts back — and with the keys a parameter,
|
||||
## Hook overhead measurement (NFR-1, per release)
|
||||
|
||||
1. `hook-harness` in a fixed workload, present-rate uncapped: 3 runs hooked vs 3 unhooked → mean present-call cost delta must be ≤ 1 µs (measured with QPC around the call site in an instrumented harness build).
|
||||
2. Real game, fixed 10-minute scene, capture ON vs OFF, 3 runs each: **game's own Avg FPS delta ≤ 0.5%**, Agent CPU ~~≤ 1%~~ ≤ 2.5 % of a core *(NFR-2 as D117 amended it, 2026-11-11; `tools/agent-cost.ps1` measures the unhooked half without a game)*, Agent RSS ≤ 150 MB, Overlay resident ≤ 8 MB.
|
||||
2. Real game, fixed 10-minute scene, capture ON vs OFF, 3 runs each: **game's own Avg FPS delta ≤ 0.5%**, Agent CPU ≤ 1% of a core, Agent RSS ≤ 150 MB, Overlay resident ≤ 8 MB.
|
||||
|
||||
> **NOT MEASURED. The runbook exists as of 2026-09-10 (P2 PR-G); the run is the owner's.**
|
||||
> `tools/fps-impact-runbook.ps1` sequences the six launches, holds consent granted for the ON leg and
|
||||
@@ -159,43 +158,6 @@ own work item on the STA thread and puts back — and with the keys a parameter,
|
||||
> Until the run happens, the honest state of this line is *unmeasured*, not *passing*.
|
||||
3. Results recorded in the release notes ("measured overhead this release: …").
|
||||
|
||||
**What a patch costs when it goes in and comes out (since 0.1.0-beta.46) is not the per-present number above**, and
|
||||
is measured where it happens: `fl_guard`'s Streamline `[advanced]` case prints the microseconds of each install
|
||||
batch and of the stop's one restore (the Overlay's `PATCH_BATCH` lines), and the time from the unhook request to
|
||||
`UNHOOKED`; it asserts that every lazily installed patch is under a batch line, that the stop is one, and that the
|
||||
restore stays under a second — the bound the one-patch-at-a-time stop did not meet on the development PC. In a real
|
||||
game the same lines are in `logs\overlay-<pid>-….log` — read there on 2026-11-13 for five games: eighteen install
|
||||
batches, 81–262 ms for sixteen of them and 0.61 s and 1.26 s for two (`17_HOOK_ENGINE` §Unhooking, *Batches*); and
|
||||
on 2026-11-14 two restores of twenty-nine patches each, 83 ms and 86 ms, when the owner stopped the part inside a
|
||||
running game.
|
||||
|
||||
**The call into the driver (train C, 0.1.0-beta.47) is tested in three places, each for what the
|
||||
others cannot say.** `fl_reflex_summary` (Catch2) drives `fl_adv_fields.h`'s reader on reports written by hand: the
|
||||
two newest frames held back, a frame summed once, a span the driver did not report, a span no frame can have, frame
|
||||
ids that start again, and the ten words of a publication — and since 0.1.0-beta.48 the driver's two own times
|
||||
(summed over the frames that gave one, each with its own count; zero and more than a second are not counted and
|
||||
refuse nothing) and the bit a multiplier has — and since 0.1.0-beta.49 the counts for the native log: every place
|
||||
a summed frame can be in, a span of a microsecond, an active time as long as the span, a refused frame, when a
|
||||
batch is due, a batch closed by a change of state and the thirty-two such closings a request has, the six lines
|
||||
and what each carries; a hidden `[.bench]` case is the measurement of one report's cost. `fl_watchdog_tick`
|
||||
(Catch2, no thread and no clock) drives the grid the watchdog's periodic tick is on: sixty ticks each late and
|
||||
each followed by work keep whole seconds, a wait is never rounded down, a tick woken early is not periodic and
|
||||
moves nothing, a late tick is not followed by another within half a period. `fl_guard`'s nine `[latency]` cases
|
||||
(the eighth reads the log: the first batch after ten reads, by number, and what is left when a flush is asked for
|
||||
— against the stand-in's `kModeGpuShapes`; the ninth keeps the loader waking the watchdog without pause — a
|
||||
thread that asks for `opengl32.dll` for as long as the target lives — and holds one publication a second, each
|
||||
with a read, none within half a second of another: 35 720 publications in eight seconds on the code before it; a
|
||||
hidden `[.measure]` case prints ninety reads' own lines) inject the Overlay
|
||||
into a Direct3D 12 target that has loaded a stand-in `nvapi64.dll`, and read that module's call counts from outside
|
||||
through its named section (`fl_stub_nvapi_shared.h`) — so "the driver was not called" is a count: not asked → not
|
||||
even asked for the addresses; asked → about one read a second, sums equal to the stand-in's, every counted read a
|
||||
received call; an error; a span not reported; the request off; a second session; the stop; a call of 50 ms (the
|
||||
last one); a fault (counted once, the hooks stay); a module without the getters; no module (none is loaded); a
|
||||
module beside the executable (refused, never asked); Direct3D 11 (not read). `fl_reflex_probe_stub` runs the same
|
||||
header, `fl_reflex.h`, in a process that **enforces Control Flow Guard** — the injected cases do not: `hook-harness`
|
||||
is not a CFG image. **None of them is a driver.** `fl-probe-reflex --real` is the measurement against the installed
|
||||
one, run by hand (`spike-notes` §31), and a real game is owner-only item 45.
|
||||
|
||||
## Tier cross-validation (accuracy regression net) — **GONE, 2026-08-28, and this is the entry to read before planning P5**
|
||||
|
||||
~~Run the same game session with Tier 1 and Tier 2 simultaneously where possible (ETW does not conflict with hooking) and compare frametime distributions: Avg/1% Low must agree within **1%**. Divergence beyond that means one of the two paths is wrong and blocks the release. This is also the check that would have caught the original detection-accuracy problem.~~
|
||||
|
||||
+16
-331
@@ -172,81 +172,6 @@ Every hook must be listed here with a purpose. Anything not on this list is not
|
||||
| ✅ `opengl32.dll!wglSwapBuffers` (2026-09-06, P1 item 4) | The OpenGL present hook (§Presentation). A system module, not a vendor one, so — like the row below — it is deliberately **not** in `FL_HOOK_INVENTORY` and `hookinventory-check` does not cover it; listed here so the table above and these two rows together are the whole inventory |
|
||||
| ✅ `kernelbase.dll!LoadLibraryExW` (2026-09-06, P1 item 1) | The wake for lazily loaded runtimes and the in-process anti-cheat stop — §DLL entry step 3 above carries the mechanism. **Rule 4:** it reads one argument the API was given (`flags`) and one property of a handle the loader just returned to *its own caller* (the module file name); nothing of the game's. **~~It is the only hook on a system module, and~~ Like `wglSwapBuffers` above it, it is deliberately not in `FL_HOOK_INVENTORY` (corrected 2026-10-04):** that table is *vendor* symbols resolved by name and gated by `hookinventory-check` against `vendor-exports.json`, and `LoadLibraryExW` is neither vendor nor uncertain. It is listed here instead so the table above and this row together are the whole inventory. It **never** installs, uninstalls or patches anything itself (§H2) |
|
||||
|
||||
### Calls the Overlay makes into a driver — not hooks, and the only ones
|
||||
|
||||
Everything else on this page learns what it learns from the arguments of a call the game made. This is the one
|
||||
place the Overlay **makes a call of its own** into code that is neither the game's nor FrameLedger's, and it is
|
||||
listed here so that nobody takes it for a hook or adds a second one without the same ruling
|
||||
(`CLAUDE.md` rule 4's note of 2026-11-13, owner decisions D132, D136, D138–D141).
|
||||
|
||||
| Call | When, where | Rule 4 | What bounds it |
|
||||
|---|---|---|---|
|
||||
| **NVIDIA's `NvAPI_D3D_GetLatency` and `NvAPI_D3D_GetSleepStatus`** — the driver's two read-only latency getters (Advanced metrics train C; `fl_reflex.h`; **since 0.1.0-beta.47**) | **Only while a session asks for Advanced metrics** (D138: no switch of its own), only for a Direct3D 12 swap chain whose device is the one the Overlay holds, **about once a second, on the presenting thread, after that present's record is published**. The watchdog finds the addresses once for the process and arms one read at a time; a present pays one relaxed load. The addresses come from an `nvapi64.dll` **the game had already loaded** — asked for by name, never loaded — through its `nvapi_QueryInterface` and the two interface ids of the vendored `nvapi_interface.h`. The Overlay links no NVAPI | The owner's ruling (D132): a driver's read-only getter called with the device behind the swap chain the Overlay hooks reads the driver's report, not game memory, and writes nothing. Getters only — never a setter, a marker or a sleep (`tools/nvapi-readonly-check.ps1` holds which ids code loaded into a game may name: these two). What is read of the two structs is on `tools/overlay-allowed-fields.txt` like every other vendor member | **An `nvapi64.dll` in the executable's own folder is refused** (D140): the driver's is in Windows' directories. **A fault** in a getter is caught by a guard of its own, counted once in `faultCount`, and ends the reads for the process. **One call of 2 ms or more** ends them too (D141). **A call that has not returned after two seconds** is logged, flushed and published as stalled — nothing can stop it, and the presenting thread it holds is the game's. Each is until the game exits |
|
||||
|
||||
**Where the addresses are, measured** (`fl-probe-reflex --real`, driver 32.0.16.2114): System32's `nvapi64.dll` is a
|
||||
shim and answers the two ids with addresses inside **`nvapi64_impl.dll`**, in the driver's own store. So an address
|
||||
is accepted when it is executable code of an image the process has loaded, and **the Overlay keeps a reference on
|
||||
that image as well as on `nvapi64.dll`** — two modules the game loaded, never released, for the reason
|
||||
`ResolveScoped` gives: a presenting thread may be about to call. `nvapi64_impl.dll` is a Control Flow Guard image;
|
||||
the probe, which enforces CFG, has made the calls from the header that ships, so on this driver the getters are
|
||||
valid targets. **Not excluded**: a game that enforces CFG on a driver the probe has not been run against — a target
|
||||
that were not valid is a fast-fail no guard catches.
|
||||
|
||||
**In a real game** (the owner, 2026-11-14, Phantom Blade Zero on 0.1.0-beta.47, three sessions, frame generation
|
||||
×3 and off): the module was found four to five seconds after the attach — `nvapi64.dll` in System32, the getters in
|
||||
`nvapi64_impl.dll`, as on the probe — a read was made about every second for 344 s, 52 s and 1 119 s, **the slowest
|
||||
call took 24, 20 and 45 µs**, and no latch fired: no error, no slow call, no fault, no stall. **Cyberpunk 2077 the
|
||||
same morning**, two sessions (frame generation ×2 and off, 260 s and 581 s): found 4.8 s and 2.6 s after the attach,
|
||||
the slowest call 34 and 65 µs, no latch. Two Direct3D 11 games and one Direct3D 12 game with no `nvapi64.dll` were
|
||||
left alone, each with its one line. Two games read, one driver.
|
||||
|
||||
**Two more members of the same report, and the multipliers seen (0.1.0-beta.48; owner decisions D142, D144).** In
|
||||
Phantom Blade Zero the span between the driver's two GPU marks was longer than the frame's whole: it includes the
|
||||
card's waiting. NVIDIA's header has the figure that does not — `gpuActiveRenderTimeUs`, "excluding the idles in
|
||||
between" — and beside it `gpuFrameTimeUs`, one frame's GPU end to the next's. Both are read from the report the
|
||||
getter already filled: **no call is added, and no interface id** (`tools/nvapi-readonly-check.ps1` is unchanged;
|
||||
the two names are on `tools/overlay-allowed-fields.txt`). The buffer is the Overlay's own, so there is no question
|
||||
of a member lying past what a game allocated; an older driver leaves both zero, and zero is read as *not given* —
|
||||
each time has its own count, and neither decides which frames the seven spans are made of. The sleep status'
|
||||
frame-generation multiplier is now also kept as the set of values a session saw (a session that generated ×2 and
|
||||
ended in a menu read 1). **One defect fixed with it**: a read that ended after a session's last tick was taken by
|
||||
the next session as its first point; a new request now drops it. **Measured** (the header's own function, the
|
||||
Overlay's flags, a report of 62 summed frames, 2 million reports × 3, twice): 393–396 ns before, 429–434 ns after
|
||||
— **+36 ns a read**, once a second, and after the call's time has been taken, so it cannot reach the 2 ms latch.
|
||||
The present path is unchanged: one relaxed load.
|
||||
|
||||
**Since 0.1.0-beta.49 each summed frame is also counted for the native log** (owner decisions D148, D151;
|
||||
§Native logging, `LATENCY_FRAMES`). The owner's ten sessions on beta.48 (HANDOFF, item 46) gave both of the
|
||||
driver's own times in every frame report of both games — and in Cyberpunk 2077 without frame generation the mean
|
||||
active time was **longer** than the mean span between the two GPU marks (3.17 against 2.79 ms), which the two
|
||||
means cannot explain: the span's is over every summed frame, one of no length included, the active time's over
|
||||
the frames that gave one. So the reader places each summed frame by its own two numbers (`CountGpuTimes`), after
|
||||
the frame is accepted: which frames are summed does not change, and the seven spans, the two times and their
|
||||
counts are what they were. **No new call, no further member of the report** — the two GPU marks and
|
||||
`gpuActiveRenderTimeUs` were read already — and nothing of it leaves the process: the watchdog adds each read's
|
||||
counts to a batch and writes the batch to the log. **Measured** (the same instrument: 2 million reports × 3,
|
||||
twice): 424–435 ns before, 490–499 ns after — **+65 ns a read**, once a second, after the call's time has been
|
||||
taken. `fl_reflex_summary_test "[.bench]"` is that measurement in the tree. The present path is unchanged.
|
||||
|
||||
**Since 0.1.0-beta.49 the read is on a grid of one second** (owner decision D150; `fl_watchdog_tick.h`). The
|
||||
watchdog used to wait a second *after* each tick's work, and a tick the LoadLibrary detour woke was a tick like
|
||||
any other: it took what the last read left, published it and — less than a second having passed since the last
|
||||
arm — armed nothing, so the next publication carried no read. The Agent samples on a period of exactly one second
|
||||
since 0.1.0-beta.48, and its sessions showed the holes: 0.4 to 16 % of a session's samples without a report
|
||||
(HANDOFF, item 46). Now the watchdog's **periodic** tick is due at a deadline by the performance counter, and the
|
||||
next deadline is one period after the one that was due, not after the moment the tick ran; a tick woken early
|
||||
does everything it did — the request is followed and the hooks a session asks for go in at once — **except take
|
||||
the driver read and publish region 5**, which are the periodic tick's. One read is armed at every periodic tick
|
||||
(`g_latArmedQpc` and its "a second since the last arm" are gone). A periodic tick that ran more than half a
|
||||
second late is not followed by another on the grid's next mark: the grid starts again from it, so **two reads are
|
||||
never less than half a second apart** — "about once a second" still, and no longer "at most". Nothing on a game
|
||||
thread changed: the presenting thread makes the read when it finds the gate armed, as before. **Measured** on `hook-harness` with the stand-in module, by the batches' own lines (`fl_guard_test "[.measure]"`): ten reads in 9 996 ms, the next twenty in 20 002, the next sixty in 59 997, each batch with as many periodic ticks as reads; and with a thread asking the loader for a module without pause — 18 240, 36 427 and 143 424 early wakes in the three batches — 9 997, 20 000 and 59 999 ms for the same reads. On the code before it the second case published 35 720 times in eight seconds, with nine reads. **Not measured in a game**, and not the whole of the holes: the Agent overwrote a reading that waited for a sample, which is its own change (`07_IPC` §Region 5).
|
||||
|
||||
**The gate.** One word, four states — idle, armed, reading, off (`dllmain.cpp`, above `ReadLatencyOnce`). Only the
|
||||
watchdog arms; a presenting thread takes *armed* to *reading* by compare-exchange and owns the 15.4 KB report
|
||||
buffer (static storage, never a game thread's stack) and the read's result until it stores *idle* or *off*; the
|
||||
watchdog takes the result only when nobody is reading. No lock, and no second read while one is under way.
|
||||
|
||||
### Watchdog observations — not hooks, and listed here so nobody mistakes them for one
|
||||
|
||||
| Observation | Mechanism | Rule 4 | Why |
|
||||
@@ -269,17 +194,12 @@ watchdog takes the result only when nobody is reading. No lock, and no second re
|
||||
|---|---|
|
||||
| NGX: `NVSDK_NGX_D3D11/D3D12/VULKAN_CreateFeature`, `EvaluateFeature`, `ReleaseFeature` | Which NGX feature is *actually created and evaluated per frame*: SuperSampling (DLSS), RayReconstruction (DLSS-D), FrameGeneration (DLSS-G) |
|
||||
| NGX parameter accessors (`NVSDK_NGX_Parameter_SetI/GetI/SetUI`) — **exported by `sl.common.dll` only; see below** | `Width`/`Height` (render) vs `OutWidth`/`OutHeight` (output), `PerfQualityValue` (quality preset), sharpness |
|
||||
| ✅ Streamline: `slEvaluateFeature` · ~~⏳ `slInit`~~ *(not hooked, and not to be: owner decision D129, 2026-11-12 — its row below says why)*, ~~`slSetFeatureLoaded`~~ *(its own row below since beta.45)*, ~~`slSetConstants`~~ *(its own row below since beta.43)*, ~~`slGetFeatureRequirements`~~ *(its own row below since beta.44, with `slGetFeatureVersion`)* | Feature set actually active when the game goes through SL rather than NGX directly (`kFeatureDLSS`, `DLSS_G`, `DLSS_RR`, `Reflex`, `NIS`; since beta.34 `kFeatureDLSS_NR` — DLSS 5's neural rendering, its own fact bit and family `FL_HOOK_SL_NEURAL_RENDERING`, D84; rule 4: the `feature` argument of the API hooked, nothing else). **Built 2026-08-09**, identity only: one MinHook detour on `sl.interposer.dll!slEvaluateFeature`, resolved **module-scoped** and installed lazily by the watchdog. Sets `FL_MEASURED_UPSCALER` + `FL_HOOK_UPSCALER_IDENTITY`; decodes `kFeatureDLSS`/`kFeatureNIS` and reports `FL_UPSCALER_UNKNOWN` for anything else. **Never `FL_UPSCALER_NONE`** — a Streamline-only writer cannot see FFX, XeSS or NGX-direct, and `NONE` is the only one of the three states that may be aggregated as a negative. **Since 0.1.0-beta.40 (Advanced metrics train B, D111), and only while the Agent asks** (`FlControlBlock.advancedRequested`): the `sl::DLSSOptions` a title chains into `inputs` — the struct the quality mode is read from — is read further: `outputWidth`/`outputHeight`, `preExposure`, `exposureScale`, `colorBuffersHDR`, the five presets of version 1, and where the struct's own `structVersion` proves them present `ultraQualityPreset` and `useAutoExposure` (≥ 2) and `alphaUpscalingEnabled` (≥ 3) — §Which struct version carries which field. Rule 4: more members of the same argument of the same call; `fl_adv_fields.h` is the one place, `tools/overlay-fields-check.ps1` holds it. No new patch site. **Measured** (the header's own functions, `/O2 /guard:cf /Qspectre /MT`, 20 M calls × 3): +9.5–11.7 ns per evaluation that chains the options while asked; with the word at 0, one relaxed load and a branch not taken — below what the bench resolves. Most titles set these through `slDLSSSetOptions`, which is not an export, and read N/A (train D) |
|
||||
| ✅ Streamline: `slSetConstants` (0.1.0-beta.43, Advanced metrics train B; owner decisions D111–D116, D122) | **What the game tells Streamline about a frame**, once per frame and viewport, read from the `sl::Constants` it passes — rule 4: an argument of the call hooked, and of it only the members named here. **Read:** `jitterOffset`, `mvecScale`, `cameraNear`, `cameraFar`, `cameraFOV`, `cameraAspectRatio` and the seven `Boolean`s (`depthInverted`, `cameraMotionIncluded`, `motionVectors3D`, `reset`, `orthographicProjection`, `motionVectorsDilated`, `motionVectorsJittered`). **Never read:** the five matrices (bytes 32..351 of the struct), `cameraPinholeOffset`, and the camera's position and three axes (bytes 368..423) — `tools/overlay-fields-check.ps1` refuses their names anywhere in code loaded into a game, and ctest `fl_adv_fields` publishes two structs that differ in every one of those bytes and gets the same bytes out. **The one row that is not installed unless asked for** (D111): `InstallByFamily` returns before it resolves the symbol in a process the Agent has never asked for Advanced metrics — resolving takes a reference on the module — so with the option off the export's first bytes are the file's (`fl_guard` `[advanced]` reads them from the target). Once asked, the patch goes in on that watchdog tick and stays for the life of the process; the detour forwards without looking while the request is off, and after a stop (`MayObserve`). **Every call** checks the struct's GUID and a `structVersion` of at least 1 before any member is read, and the viewport handle's the same way; every member read is one version 1 carries, so a version-1 struct laid against unreadable memory is read whole without a fault (the same ctest). **Summaries are the first viewport's**: a title with two viewports sets constants for each every frame, and "the last value" across them would flip twice a frame; the call count is of every viewport. `FLT_MAX` is Streamline's "not set" here and is kept nowhere (D119's plane at infinity is FidelityFX's). Family `FL_HOOK_SL_CONSTANTS` (bit 13), published with the patch: it entitles no field of a frame record, and tells "hooked, never called" from "not hooked". **Measured overhead** (the detour's body on the headers, the Overlay's flags, 20 million calls a run, three runs): not asked **+0.57 / +0.60 / +0.58 ns**; asked, the summarised viewport **+19.61 / +19.54 / +19.79 ns**; asked, another viewport +5.83 / +6.01 / +5.62 ns. |
|
||||
| ✅ Streamline: `slGetFeatureVersion` and `slGetFeatureRequirements` (0.1.0-beta.44, Advanced metrics train B's third step; owner decisions D111–D116, D122) | **What Streamline answers when the game asks about a feature** — which version it is, and what it requires. Two rows, two patches, two detours of one shape: **the original runs first, exactly once, on every path, with both arguments forwarded untouched**, and the struct the game passed is read only when the original said `eOk` — a refusal leaves the struct as the game made it, which is not an answer. Rule 4: an argument of the call hooked, read after the call, and of it only the members named here. **Read from `sl::FeatureVersion`:** `versionSL`, `versionNGX`. **Read from `sl::FeatureRequirements`:** `flags`, `maxNumCPUThreads`, `maxNumViewports`, `numRequiredTags`, `osVersionDetected`, `osVersionRequired`, `driverVersionDetected`, `driverVersionRequired`. **Never read:** `requiredTags` — the pointer the count belongs to — and everything after `driverVersionRequired`: the Vulkan queue counts and the pointers to the names of extensions and features. **No pointer of the game's is followed** (`tools/overlay-fields-check.ps1`, parameters `fv` and `fr`; ctest `fl_adv_fields`: two answers that differ only in those bytes publish the same region, and an answer cut off where the Vulkan members begin, laid against unreadable memory, is read without a fault; the injected `fl_guard` case's stub hands back wild pointers and no fault is counted). **Installed only where asked for** (D111), as `slSetConstants` is: `InstallByFamily` returns before it resolves either symbol in a process the Agent has never asked for Advanced metrics; once in, a patch stays for the life of the process and its detour forwards without looking while the request is off. **They are the first two rows of the table**: a game asks these while it starts, the watchdog patches rows in the table's order, and each patch stops the game's threads for a moment (0.1–0.25 s apart in the owner's logs of 2026-11-12, where `slSetConstants` was the fifth Streamline patch in, 1.9–7.8 s after the attach). *(Since 0.1.0-beta.46 the rows a tick finds go in together, under one stop of the threads — §Unhooking, Batches — so the order no longer decides which row waits behind which; it is still the order of their log lines.)* In a process never asked they are passed over and the order changes nothing. ~~**Most sessions will still have missed the calls** — an attach after the game's start-up is the usual case — and the session then says the call was hooked and the game did not ask again.~~ *(Measured 2026-11-12, the owner's eight sessions on beta.44: both calls were read in six of six Streamline sessions on five games — Unreal's Streamline plugin asks again after the attach, Cyberpunk 2077 asks again for requirements and not for versions. A game that asks only while starting still reads "hooked, not asked again".)* Three conditions before a read, as for `slSetConstants`: the Agent is asking, observing has not stopped, and the struct carries its own GUID and a version of at least 1 on this call (a struct with another GUID is not kept: the injected case sends one). Every member read is version 1's (§Which struct version carries which field). **Twelve slots** in region 5 (`FlAdvancedState.features`, layout 5 as it was), one per feature in the order first asked about; the last answer about a feature is the one kept; a thirteenth feature is not kept. **A new request does not empty them**: what version a feature is and what it requires are facts about the process, and a second session of a game that kept running would otherwise have nothing where the first had the answer — the one group `Reset` leaves, with its bit of the mask. Streamline 1.x is refused before anything is resolved (`SpeaksStreamline2`). Families `FL_HOOK_SL_FEATURE_VERSION` (bit 15) and `FL_HOOK_SL_FEATURE_REQUIREMENTS` (bit 16), each published with its patch; neither entitles a field of a frame record. **Measured overhead** (the detours' bodies on the headers, the Overlay's flags, 20 million calls a run, three runs, eight features asked about in turn): the version — not asked **+0.58 / +0.61 / +0.58 ns**, asked **+14.82 / +14.54 / +14.47 ns**; the requirements — not asked **+0.58 / +0.63 / +0.61 ns**, asked **+20.88 / +21.01 / +20.96 ns**. A game makes these calls a handful of times. |
|
||||
| ✅ Streamline: `slIsFeatureSupported`, `slIsFeatureLoaded`, `slSetFeatureLoaded` (0.1.0-beta.45; owner decisions D129–D131) | **Whether a feature is supported, whether it is loaded, and the game switching it on and off.** Three rows, three patches. Rule 4: bare arguments and results of the calls hooked, and no vendor struct at all — the feature's id; the `sl::Result` `slIsFeatureSupported` returned, **every result**, since a refusal is the answer to that question (the original runs first, both arguments forwarded untouched); the `bool` `slIsFeatureLoaded` wrote, read only when it returned `eOk`; the `bool` the game passed to `slSetFeatureLoaded`, noted before the call. **The adapter `slIsFeatureSupported` is asked about is never read** (D131): `sl::AdapterInfo` holds the adapter's LUID or a Vulkan physical device; the detour forwards the reference and `tools/overlay-fields-check.ps1` refuses the names of its members (`deviceLUID`, `deviceLUIDSizeInBytes`, `vkPhysicalDevice`) anywhere in the Overlay and the Vulkan layer — the fixture's adapter carries a wild pointer. **Installed only where asked for** (D111), as the four rows before them. `slIsFeatureSupported` and `slIsFeatureLoaded` follow the two rows of beta.44 at the head of the table; `slSetFeatureLoaded` follows `slSetConstants`. **Kept in word 1 of the feature's slot** (region 5, layout 5 as it was): bit 2 and the result in bits 8..15, bits 3 and 4, bits 5 and 6 — the last two a session's, cleared by a new request; the rest the process's, kept (`fl_adv_fields.h` `kFeatureSessionBits`). A refused feature therefore has a slot now, with nothing in it but that word. The declarations of the three functions are the same from Streamline v2.0.0 to v2.14.16, and `sl::Result` is the same forty codes in the same order at all sixteen tags (`include/sl_result.h`, `05a3c7e3889c` … `8a844b68ff55`), so a code means the same whatever interposer answered. Families `FL_HOOK_SL_FEATURE_SUPPORTED` (bit 17), `FL_HOOK_SL_FEATURE_LOADED` (18), `FL_HOOK_SL_SET_FEATURE_LOADED` (19), each published with its patch. **Measured overhead** (the detours' bodies on the headers, the Overlay's flags, 20 million calls a run, three runs, eight features in turn): `slIsFeatureSupported` — not asked **+1.50 / +1.48 / +1.50 ns**, asked **+11.97 / +11.98 / +12.08 ns**; `slIsFeatureLoaded` — **+1.79 / +1.77 / +1.89 ns**, **+12.35 / +12.31 / +12.33 ns**; `slSetFeatureLoaded` — **+1.44 / +1.47 / +1.80 ns**, **+11.28 / +11.54 / +11.45 ns**. **`slInit` is not a row and will not be** (D129): a game calls it once, before the Overlay is in the process or before a patch can land — launch mode waits for the presentation runtime before it injects, nothing is ever patched on a game's thread (§H2), and a row that exists only for Advanced metrics waits for the Agent's request. **A stop takes about 160 ms for every patch it restores** (measured on the fixture, 0.1.0-beta.45: each `MH_DisableHook` snapshots the system's threads): twelve patches took 1.9 s, fifteen 2.4 s, and the watchdog's wait for the stop's log lines, 2 s until then, is now a quarter of a second for every patch the registry can hold. **Since 0.1.0-beta.46 (D134) a stop restores its patches under one stop of the threads**: eighteen in 76–90 ms on the fixture, where one by one they took 1.37–1.56 s (§Unhooking, Batches). |
|
||||
| ✅ Streamline: `slAllocateResources`, `slFreeResources`, `slShutdown` (0.1.0-beta.45; owner decision D130) | **The game allocating and freeing a feature's resources, and shutting Streamline down — counted, and nothing else.** Three rows, three patches. Rule 4: the feature's id is the only argument looked at; the command buffer and the viewport of the two resource calls are forwarded and never read (the fixture's command buffer is a wild pointer), and `slShutdown` has no argument. **`slFreeResources` and `slShutdown` are on a game's way out**: each detour notes the call first and then calls the original, exactly once, and runs nothing of ours after it returns; the fixture goes on calling the stub after `slShutdown`, through every detour. **Installed only where asked for** (D111); the last three Streamline rows of the table. **Kept** in word 1 of the feature's slot as two four-bit counts — allocations in bits 16..19, frees in 20..23, each stopping at 15 and never carrying into its neighbour — and, for `slShutdown`, in `FlAdvancedState.slShutdowns` (@308, the first of three reserved words; layout 5 as it was) with `FL_ADV_VALID_SL_SHUTDOWN` (bit 6 of the mask). All three are a session's: a new request clears them. Families `FL_HOOK_SL_ALLOCATE_RESOURCES` (bit 20), `FL_HOOK_SL_FREE_RESOURCES` (21), `FL_HOOK_SL_SHUTDOWN` (22). The three declarations are the same from Streamline v2.0.0 to v2.14.16. **Measured overhead** (the detours' bodies on the headers, the Overlay's flags, 20 million calls a run, three runs): `slAllocateResources` — not asked **+0.70 / +0.72 / +0.80 ns**, asked **+10.43 / +10.53 / +10.74 ns**; `slFreeResources` — **+0.61 / +0.84 / +0.58 ns**, **+10.33 / +10.57 / +10.44 ns**; `slShutdown` — not asked within the bench's noise (+0.06 / −0.12 / +0.04 ns), asked **+3.39 / +3.37 / +3.52 ns**. Inventory 23 → 26 rows; a Streamline title with Advanced metrics asked for now carries thirteen patches on the interposer, and a stop restores each in about 160 ms (the row above). **In real games (2026-11-13: six sessions, five games)** `slAllocateResources` was not called once after the attach, `slFreeResources` once in one game (Phantom Blade Zero, frame generation's) and `slShutdown` once in one (Dying Light: The Beast); no session counted a fault, and the two games that fault while closing did so at the offsets they had before these hooks. Installing the thirteen interposer patches took 0.7 s to 2.8 s of a game's start, 57 to 215 ms a patch. The owner's word on both (2026-11-13): `slAllocateResources` keeps its patch and is looked at again with more sessions (D135); installs and restores are to be batched, one stop of the threads for a batch (D134, 0.1.0-beta.46). |
|
||||
| ✅ Streamline: `slEvaluateFeature` · ⏳ `slInit`, `slSetFeatureLoaded`, `slSetConstants`, `slGetFeatureRequirements` | Feature set actually active when the game goes through SL rather than NGX directly (`kFeatureDLSS`, `DLSS_G`, `DLSS_RR`, `Reflex`, `NIS`; since beta.34 `kFeatureDLSS_NR` — DLSS 5's neural rendering, its own fact bit and family `FL_HOOK_SL_NEURAL_RENDERING`, D84; rule 4: the `feature` argument of the API hooked, nothing else). **Built 2026-08-09**, identity only: one MinHook detour on `sl.interposer.dll!slEvaluateFeature`, resolved **module-scoped** and installed lazily by the watchdog. Sets `FL_MEASURED_UPSCALER` + `FL_HOOK_UPSCALER_IDENTITY`; decodes `kFeatureDLSS`/`kFeatureNIS` and reports `FL_UPSCALER_UNKNOWN` for anything else. **Never `FL_UPSCALER_NONE`** — a Streamline-only writer cannot see FFX, XeSS or NGX-direct, and `NONE` is the only one of the three states that may be aggregated as a negative |
|
||||
| ✅ Streamline: `slSetTag` — **and, since 2026-09-05, every tag's TYPE** (`slTagCensus`; a HUD-less / UI tag marks the present `FL_FG_DLSS_G`, rule 4: the same argument) | The **global** resource tags, where a title states the size of the buffer it is upscaling *from*: `kBufferTypeScalingInputColor`'s extent → `renderW/H` — **or, since 2026-09-05, the size the tagged `sl::Resource` declares when the extent is zero** (`TagSize` in `fl_sl_inputs.h`, shared by all three tag routes; GUID-checked; a Resource declaring no size is still the honest unknown). **Built 2026-08-15** (`FL_HOOK_UPSCALER_PARAMS`), and it is an ALTERNATIVE to the local tags in `slEvaluateFeature`'s `inputs`, not a layer over them — `sl_core_api.h:258` says global and local tags "do NOT interact", so a title using one yields nothing from the other and both are read. Published only on a frame where an evaluation was also seen, because a tag is viewport state that outlives any one frame. This row was MISSING from this table while the hook shipped, which is the gap the banner above now names |
|
||||
| ✅ Streamline: `slSetTagForFrame` — **and every tag's TYPE, as above** | The same global tags through **Streamline 2.8's frame-based entry point**, which deprecates `slSetTag`: `(const FrameToken&, const ViewportHandle&, const ResourceTag*, uint32_t, CommandBuffer*)` — the token first, then exactly `slSetTag`'s list, handed to the same tag walk. **Built 2026-09-04** (`FL_HOOK_UPSCALER_PARAMS`, its own trampoline; the family is now **published when whole** — once every tag export the loaded interposer has is patched — because publishing on the first row entitled records the second was not yet producing, 38 of 41 on the fixture: the ffx leaves' #110 defect again, fixed the same way). Measured need: Dying Light: The Beast (SL 2.8.0) published `Dlss` identity on every batch and the params bit on none across three captures, because a 2.8 title that tags per frame never calls the deprecated export. The token is not read; the frame count stays with `slGetNewFrameToken`. The installer picks this detour by SYMBOL (`kSymbolSlSetTagForFrame`, bound to the row by `static_assert`), not by family, since the two rows share a family bit and differ in signature |
|
||||
| ✅ **FidelityFX ffx-api: `ffxDispatch` on the FOUR modules a game calls** — `amd_fidelityfx_dx12.dll` (SDK 1.1.x monolith), `amd_fidelityfx_upscaler_dx12.dll`, `amd_fidelityfx_framegeneration_dx12.dll`, **and `amd_fidelityfx_loader_dx12.dll`** (added the evening of 2026-09-04: three loader-shipping titles at FSR produced zero dispatches at any leaf export, so the loader is where their calls arrive) · ⏳ FSR 3.0 host route `ffx_fsr3_x64.dll!ffxFsr3ContextDispatchUpscale` / `ffxFsr3DispatchFrameGeneration` · ~~`ffxFsr2ContextCreate`~~ · ~~`ffxCreateContext`~~ | **Built 2026-09-04** (`HANDOFF` item 7c). One observer behind three trampolines reads the DESCRIPTOR the title passed — head type first, body only after the type matched a constant from the vendored MIT headers (`third_party/fidelityfx/`, tag v2.3.0): **UPSCALE** → identity (`FSR3` from the monolith, `FSR_UNVERSIONED` from the 2.x upscaler DLL, which hosts FSR 3.1 and FSR 4 behind one type) + `renderSize` → `renderW/H` (quality and sharpness `0xFF`: the dispatch carries neither — *since beta.25 the quality byte is the mode the `ffxQuery` row below names for the dispatched size, `0xFF` when none does*) + one COUNT *(since 0.1.0-beta.43, owner decision D125: **counted at the first source that saw an UPSCALE and at no other** — `g_ffxUpscaleOwner`, `fl::adv::Owns`. Cyberpunk 2077's loader 2.3.0 hands a dispatch on to the leaf's export — its frame-generation dispatch types are logged on the loader and on the leaf — so an UPSCALE through such a loader reaches two hooked modules, and one count per module read K = 1 as 2.0 on the fixture bound that way (`--ffx-topology 2x-export`: 60 presents, 120 counted). No title run so far upscales through one; it is a precaution. Measured on the header with the Overlay's flags: +0.02 to +0.03 ns on the module that is counted, about 4 ns less on the forwarded copy)*; **PREPARE / PREPARE_V2** → `frameID` counted on a *new* index only — this vendor's `slGetNewFrameToken`, the `fgEvaluations` producer once a title has ever prepared, with the UPSCALE count as the fallback for a title that never does; **FRAMEGENERATION** → `fgMode = FSR_FG` on that present. Rule 4: the argument of the API we hooked, never `context`, `pNext`, a command list or a resource. **Why all four:** a UE5 title ships the two leaves with no loader and calls their exports; a loader-shipping title calls the loader's export and the signed loader reaches its providers through an object, not the leaves' exports (measured: Dying Light: The Beast, KCD2, Wukong). The morning's "never the loader" rested on the export tables alone and was reversed by the run. What guards against a loader that DID re-enter a leaf's export is the K = 1 control with all four hooked and the consumer's `frames/upscale-drained`, both of which read 2× in that case. `ffxCreateContext` is deliberately NOT a row — nothing it carries fills a field the dispatch does not, and its honest family would collide with `slEvaluateFeature`'s under the installer's equality binding. The family is compound (`IDENTITY \| PARAMS \| FG_EVALUATIONS`), pinned by `static_assert`s that also bind the leaf table to the rows both ways and refuse the loader as a row. Streamline keeps precedence for the count once it has ever issued a token, so every §S31-validated title is byte-identical. Second count: the consumer prints `frames/upscale-drained`, the AMD `tokens/batch`. **FSR 3.0 — BUILT 2026-09-05 as a fifth AMD target:** `ffx_fsr3_x64.dll!ffxFsr3ContextDispatchUpscale` (Cyberpunk's copy; named export, its own descriptor, vendored from tag **`fsr3-v3.0.4`** — the tag whose twelve `ffxFsr3*` declarations match the shipped module, not the `v1.1.4` first named). Rule 4: the detour reads `renderSize` of the descriptor the title passed and nothing else — never the context, a resource or the command list; the offset is pinned to a literal (1256) so a re-vendoring that moved it fails to compile. Same family and publish point as the four rows (`PublishFfxFamilyIfWhole` waits for a loaded host too), keyed by module in the installer; identity `FSR3` as a fact. `ffxFsr3DispatchFrameGeneration` is deliberately not a row (§H11 carries the reversal condition); the `ffx_fsr3upscaler_x64.dll` leaf is the pre-committed alternative if the facade reads silent (row B2) — never both, or `frames/upscale-drained` reads 2.00. **Since 0.1.0-beta.40 (Advanced metrics train B, D111), and only while the Agent asks:** the UPSCALE arm reads the rest of `ffxDispatchDescUpscale` — `enableSharpening`, `sharpness`, `jitterOffset`, `preExposure`, `cameraNear`, `cameraFar`, `cameraFovAngleVertical`, `flags`, `reset`, `frameTimeDelta` — into process-local summaries (an "ever seen" mask, a largest magnitude, a lowest and highest, a count and a sum; one module's dispatches are counted, so a dispatch that reaches the loader and a leaf is one). Never on the FSR 3.0 host's legacy descriptor, which is vouched Line truncated
|
||||
| ✅ **FidelityFX ffx-api: `ffxQuery` on the same four modules** (beta.25, owner decision D65) — `amd_fidelityfx_dx12.dll`, `amd_fidelityfx_upscaler_dx12.dll`, `amd_fidelityfx_framegeneration_dx12.dll`, `amd_fidelityfx_loader_dx12.dll` | **Built 2026-10-19.** The mode an FSR title runs at reaches the vendor only as an argument of `ffxQuery` — "what render size (`…GETRENDERRESOLUTIONFROMQUALITYMODE`, `0x00010003`) or ratio (`…GETUPSCALERATIOFROMQUALITYMODE`, `0x00010002`) does this mode give at this display size?" — asked before the title sizes its targets; the per-frame dispatch carries the size alone. The detour calls the original FIRST, exactly once, and only when it returned `FFX_API_RETURN_OK` reads the descriptor's type, display size and mode and the values the vendor wrote through the title's own out pointers, into a five-slot table (one per `FfxApiUpscaleQualityMode`); the `ffxDispatch` UPSCALE arm names the ONE mode whose kept answer fits the dispatched `renderSize` (and `upscaleSize`, where stated) as `0x10 + mode` in `upscalerQuality`, else `0xFF` (`03_METRICS` §Upscaling). **Rule 4:** the arguments of the API we hooked — the descriptor the title passed and the out values of that same call — never `context`, a resource or anything the title did not hand the hooked export; nothing of the title's is written, and every read is under the hook's SEH guard. Both query layouts and type ids are pinned to literals by `static_assert`s, identical at SDK v1.1.4 and v2.3.0. **Its own family**, `FL_HOOK_UPSCALER_QUALITY` (bit 11 of `hooksInstalledMask`, mirrored in `FlHookFamily` and `HookFamilies`): `InstallByFamily` binds a row by equality, and the query entitles no measured field by itself — the byte rides under `FL_MEASURED_UPSCALER_PARAMS` from the dispatch arm — so the bit says only that the query was hooked, which tells "never asked" from "could not have seen it ask". Published like the dispatch family, once every loaded leaf is patched (`PublishFfxQueryFamilyIfWhole`); the FSR 3.0 host has no `ffxQuery` and no row (`static_assert`). A loader that passes a query on to a leaf's export refreshes one kept answer twice; nothing is counted, so nothing is counted twice. **Measured overhead** (a copy of the two bodies, `/O2 /guard:cf /Qspectre /MT`, 20 M calls × 3 runs, every slot holding both a size and a ratio — the worst case): 7.6–8.2 ns added per UPSCALE dispatch, i.e. per application frame, and 1.6 ns per query beside the trampoline; the per-present path gains one load. Harness: `--ffx-query sizes|ratios`; `fl_guard` "FSR's quality mode". **Since 0.1.0-beta.40 (Advanced metrics train B, D111), and only while the Agent asks:** when the query the vendor answered OK is the upscaler's memory — `FFX_API_QUERY_DESC_TYPE_UPSCALE_GPU_MEMORY_USAGE` (`0x00010008`, ffx-api 1.1.2) or `…_V2` (`0x00010009`, 2.0) — the `FfxApiEffectMemoryUsage` it wrote through the title's own out-pointer is kept (total and aliasable bytes), one module's queries counted. Only a title that asks is answered: FrameLedger never calls `ffxQuery` itself. The frame-generation memory queries (`0x00020007`, `0x0002000b`) are not read. +4.3–6.1 ns per such query while asked. Harness: `--ffx-memory-query v1|v2`; `fl_guard` "region 5 stays empty until the Agent asks". |
|
||||
| ✅ **FidelityFX ffx-api: `ffxDispatch` on the FOUR modules a game calls** — `amd_fidelityfx_dx12.dll` (SDK 1.1.x monolith), `amd_fidelityfx_upscaler_dx12.dll`, `amd_fidelityfx_framegeneration_dx12.dll`, **and `amd_fidelityfx_loader_dx12.dll`** (added the evening of 2026-09-04: three loader-shipping titles at FSR produced zero dispatches at any leaf export, so the loader is where their calls arrive) · ⏳ FSR 3.0 host route `ffx_fsr3_x64.dll!ffxFsr3ContextDispatchUpscale` / `ffxFsr3DispatchFrameGeneration` · ~~`ffxFsr2ContextCreate`~~ · ~~`ffxCreateContext`~~ | **Built 2026-09-04** (`HANDOFF` item 7c). One observer behind three trampolines reads the DESCRIPTOR the title passed — head type first, body only after the type matched a constant from the vendored MIT headers (`third_party/fidelityfx/`, tag v2.3.0): **UPSCALE** → identity (`FSR3` from the monolith, `FSR_UNVERSIONED` from the 2.x upscaler DLL, which hosts FSR 3.1 and FSR 4 behind one type) + `renderSize` → `renderW/H` (quality and sharpness `0xFF`: the dispatch carries neither — *since beta.25 the quality byte is the mode the `ffxQuery` row below names for the dispatched size, `0xFF` when none does*) + one COUNT; **PREPARE / PREPARE_V2** → `frameID` counted on a *new* index only — this vendor's `slGetNewFrameToken`, the `fgEvaluations` producer once a title has ever prepared, with the UPSCALE count as the fallback for a title that never does; **FRAMEGENERATION** → `fgMode = FSR_FG` on that present. Rule 4: the argument of the API we hooked, never `context`, `pNext`, a command list or a resource. **Why all four:** a UE5 title ships the two leaves with no loader and calls their exports; a loader-shipping title calls the loader's export and the signed loader reaches its providers through an object, not the leaves' exports (measured: Dying Light: The Beast, KCD2, Wukong). The morning's "never the loader" rested on the export tables alone and was reversed by the run. What guards against a loader that DID re-enter a leaf's export is the K = 1 control with all four hooked and the consumer's `frames/upscale-drained`, both of which read 2× in that case. `ffxCreateContext` is deliberately NOT a row — nothing it carries fills a field the dispatch does not, and its honest family would collide with `slEvaluateFeature`'s under the installer's equality binding. The family is compound (`IDENTITY \| PARAMS \| FG_EVALUATIONS`), pinned by `static_assert`s that also bind the leaf table to the rows both ways and refuse the loader as a row. Streamline keeps precedence for the count once it has ever issued a token, so every §S31-validated title is byte-identical. Second count: the consumer prints `frames/upscale-drained`, the AMD `tokens/batch`. **FSR 3.0 — BUILT 2026-09-05 as a fifth AMD target:** `ffx_fsr3_x64.dll!ffxFsr3ContextDispatchUpscale` (Cyberpunk's copy; named export, its own descriptor, vendored from tag **`fsr3-v3.0.4`** — the tag whose twelve `ffxFsr3*` declarations match the shipped module, not the `v1.1.4` first named). Rule 4: the detour reads `renderSize` of the descriptor the title passed and nothing else — never the context, a resource or the command list; the offset is pinned to a literal (1256) so a re-vendoring that moved it fails to compile. Same family and publish point as the four rows (`PublishFfxFamilyIfWhole` waits for a loaded host too), keyed by module in the installer; identity `FSR3` as a fact. `ffxFsr3DispatchFrameGeneration` is deliberately not a row (§H11 carries the reversal condition); the `ffx_fsr3upscaler_x64.dll` leaf is the pre-committed alternative if the facade reads silent (row B2) — never both, or `frames/upscale-drained` reads 2.00 |
|
||||
| ✅ **FidelityFX ffx-api: `ffxQuery` on the same four modules** (beta.25, owner decision D65) — `amd_fidelityfx_dx12.dll`, `amd_fidelityfx_upscaler_dx12.dll`, `amd_fidelityfx_framegeneration_dx12.dll`, `amd_fidelityfx_loader_dx12.dll` | **Built 2026-10-19.** The mode an FSR title runs at reaches the vendor only as an argument of `ffxQuery` — "what render size (`…GETRENDERRESOLUTIONFROMQUALITYMODE`, `0x00010003`) or ratio (`…GETUPSCALERATIOFROMQUALITYMODE`, `0x00010002`) does this mode give at this display size?" — asked before the title sizes its targets; the per-frame dispatch carries the size alone. The detour calls the original FIRST, exactly once, and only when it returned `FFX_API_RETURN_OK` reads the descriptor's type, display size and mode and the values the vendor wrote through the title's own out pointers, into a five-slot table (one per `FfxApiUpscaleQualityMode`); the `ffxDispatch` UPSCALE arm names the ONE mode whose kept answer fits the dispatched `renderSize` (and `upscaleSize`, where stated) as `0x10 + mode` in `upscalerQuality`, else `0xFF` (`03_METRICS` §Upscaling). **Rule 4:** the arguments of the API we hooked — the descriptor the title passed and the out values of that same call — never `context`, a resource or anything the title did not hand the hooked export; nothing of the title's is written, and every read is under the hook's SEH guard. Both query layouts and type ids are pinned to literals by `static_assert`s, identical at SDK v1.1.4 and v2.3.0. **Its own family**, `FL_HOOK_UPSCALER_QUALITY` (bit 11 of `hooksInstalledMask`, mirrored in `FlHookFamily` and `HookFamilies`): `InstallByFamily` binds a row by equality, and the query entitles no measured field by itself — the byte rides under `FL_MEASURED_UPSCALER_PARAMS` from the dispatch arm — so the bit says only that the query was hooked, which tells "never asked" from "could not have seen it ask". Published like the dispatch family, once every loaded leaf is patched (`PublishFfxQueryFamilyIfWhole`); the FSR 3.0 host has no `ffxQuery` and no row (`static_assert`). A loader that passes a query on to a leaf's export refreshes one kept answer twice; nothing is counted, so nothing is counted twice. **Measured overhead** (a copy of the two bodies, `/O2 /guard:cf /Qspectre /MT`, 20 M calls × 3 runs, every slot holding both a size and a ratio — the worst case): 7.6–8.2 ns added per UPSCALE dispatch, i.e. per application frame, and 1.6 ns per query beside the trampoline; the per-present path gains one load. Harness: `--ffx-query sizes|ratios`; `fl_guard` "FSR's quality mode". |
|
||||
| ~~XeSS: `xessD3D12CreateContext`, `xessD3D12Init`, `xessD3D12Execute`~~ **Closed at the census by licence, 2026-09-04** (`20_OPEN_QUESTIONS` §Scope decisions, `18_GPU_VENDOR_APIS` §Intel XeSS SDK): no hook on any `libxess*.dll` export *(corrected 2026-10-04)* | ~~`outputResolution`, `qualitySetting`, XeSS version; `xess_fg` variants for XeFG~~ |
|
||||
| ✅ **FidelityFX ffx-api: `ffxConfigure` on the same four modules** (0.1.0-beta.43, Advanced metrics train B; owner decisions D111–D116, D122) | **How the game configures FSR frame generation** — a title calls `ffxConfigure` with a frame-generation descriptor, usually every frame. Rule 4: an argument of the call hooked, and of it only what is named here. **Read**, and only when the header's type is `FFX_API_CONFIGURE_DESC_TYPE_FRAMEGENERATION` (`0x20002`): `frameGenerationEnabled`, `allowAsyncWorkloads`, `flags`, `onlyPresentGenerated`, `generationRect`. **Never read:** `swapChain`, the two callbacks and their contexts, `HUDLessColor`, `frameID`; and of every other configure type — key-value pairs, the distortion field, the camera info — nothing but the header's type. ctest `fl_adv_fields` publishes two descriptors that differ in all of those and gets the same bytes out, and hands the detour a key-value descriptor, which is shorter, without a read past it. **Installed only where asked for** (D111), as `slSetConstants` is: `InstallByFamily` returns before it resolves anything in a process never asked for Advanced metrics, so with the option off the export's first bytes in the target are the file's (`fl_guard` `[advanced]`). Published when every ffx-api module the process loaded is patched (`FL_HOOK_FFX_CONFIGURE`, bit 14), as the dispatch and query families are. **Counted at the first module that saw a frame-generation configure** — an owner slot of its own: the fixture's loader has always handed `ffxConfigure` on to the leaf's export, and Cyberpunk 2077's loader does the same with dispatches, so one call reaches two hooked modules (the injected case reads one configure a frame through the loader, not two). The rectangle is stored in one word, sixteen bits a side, so a publication never carries half of one rectangle beside half of the next; a side that is negative or past fifteen bits makes it four `-1`. The descriptor's type is kept for the log whatever it is (`FFX_CONFIGURE`, §Native logging). The detour consults `MayObserve()` first. **Measured overhead** (the detour's body on the headers, the Overlay's flags, 20 million calls a run, three runs): not asked **+1.72 / +1.68 / +1.78 ns** (the type kept for the log); asked, the counted module **+15.02 / +15.55 / +15.11 ns**; asked, the forwarded copy +2.70 / +2.81 / +2.65 ns; asked, another configure type +2.43 / +2.55 / +2.47 ns. |
|
||||
| ✅ **Application frames per present** (`fgEvaluations`) — **`sl.interposer.dll!slGetNewFrameToken` since 2026-09-03** | Native vs Displayed frame counts at Tier 1 — see `03_METRICS` §Frame Generation. **The producer is the frame-token export**: Streamline hands a title one token per application frame and the title must ask; the detour counts distinct tokens between two presents (pointer changes, nothing dereferenced), `FL_HOOK_FG_EVALUATIONS` is its family, and it installs on every Streamline 2 title including the ones that evaluate nothing through `slEvaluateFeature`. Rule 4: the out-parameter of an API we hooked. Premise and its gate in `03_METRICS`; pre-committed table in `20_OPEN_QUESTIONS` §S31. *The row as it stood before:* ~~NGX/SL/FFX/XeSS FG feature evaluations per present. **Built 2026-08-15 for Streamline, and MEASURED TO YIELD NOTHING ON THAT ROUTE**~~ — `slEvaluateFeature(kFeatureDLSS_G)` is never called by Cyberpunk 2077 (0 across ~14,000 batches, four FG settings), so this row installs, is honest, and counts zero; see `docs/HANDOFF.md` item 3. Built on the detour that was already there: `kFeatureDLSS_G` contributes to a saturating COUNT in the same word the feature bits live in (`fl_sl_seen.h`) rather than to a bit, because a bit collapses several evaluations between two presents into one — and under multi-frame generation that is the common case, not the edge. The row's family is therefore compound (`FL_HOOK_UPSCALER_IDENTITY \| FL_HOOK_FG_EVALUATIONS`), pinned by a `static_assert` because `hookinventory-check` reads that column as an opaque identifier. **Counts EVALUATIONS, not generated frames** — the 2026-08-14 owner ruling; the multiplier lives in `sl::DLSSGOptions`, which is only reachable by the route §2b refused. ~~Non-NVIDIA FG vendors are **deferred with a written rationale**: `amd_fidelityfx_framegeneration_dx12.dll` 3.1.5 exports only the five generic `ffx*` entry points, identical to five sibling modules, so identity is in the arguments and we have no headers~~ — **AMD has a producer since 2026-09-04** (the FidelityFX row above: the PREPARE dispatch's `frameID`, or the UPSCALE count on a title that never prepares, feeds `fgEvaluations` when Streamline has never issued a token); Intel stays at the census (`20_OPEN_QUESTIONS` §Scope decisions, by licence); the FSR 3.0 host DLL's UPSCALE (`ffxFsr3ContextDispatchUpscale`, since 2026-09-05) counts like an ffx-api UPSCALE when neither Streamline nor a PREPARE has spoken |
|
||||
|
||||
> `GetFrameStatistics().PresentCount` is **not** in this inventory and must not be
|
||||
@@ -380,72 +300,6 @@ So:
|
||||
> **`third_party/streamline/README.md` asserted this pass existed for five days
|
||||
> before it did**, which is why it is described here rather than only there.
|
||||
|
||||
### Which struct version carries which field (owner decision D115, 2026-11-11)
|
||||
|
||||
**A field of a vendor struct is read only where it is proven to be there.** A game hands a hook a struct of the
|
||||
version it was built against; a member a later version added lies past the end of what an older game allocated, and
|
||||
reading it is reading game memory outside the argument (rule 4) — not merely a wrong value. So every read of a tail
|
||||
member is gated on the struct's own version, and the gate comes from this table, not from the one header in the tree
|
||||
— which declares only the newest shape, and for `sl::DLSSOptions` says nothing about which version added what.
|
||||
|
||||
Established 2026-11-11 from the upstream tags, through GitHub's API: each tag's header was fetched by blob and the
|
||||
struct's declarations — type, name and order — compared across tags. The members' own types were checked at the
|
||||
oldest and the newest tag (`enum Boolean : char`, `enum class DLSSMode : uint32_t`, `enum class DLSSPreset :
|
||||
uint32_t`, `float2`/`float3`/`float4x4`; no `#pragma pack` in either).
|
||||
|
||||
**Streamline** (`NVIDIA-RTX/Streamline`; tags v2.0.0, v2.1.0, v2.2.0, v2.4.0, v2.4.15, v2.7.2, v2.7.30, v2.7.32,
|
||||
v2.8.0, v2.9.0, v2.10.0, v2.10.3, v2.11.1, v2.12.0, v2.14.1, v2.14.16):
|
||||
|
||||
| Struct | `structVersion` | First tag (blob of the header) | Members that version adds, in order |
|
||||
|---|---|---|---|
|
||||
| `sl::DLSSOptions` (`include/sl_dlss.h`) | 1 | v2.0.0 (`7de7411e507d`) | `mode`, `outputWidth`, `outputHeight`, `sharpness`, `preExposure`, `exposureScale`, `colorBuffersHDR`, `indicatorInvertAxisX`, `indicatorInvertAxisY`, `dlaaPreset`, `qualityPreset`, `balancedPreset`, `performancePreset`, `ultraPerformancePreset` |
|
||||
| | 2 | v2.1.0 (`60882f60e6f4`) | `ultraQualityPreset`, `useAutoExposure` |
|
||||
| | 3 | v2.4.0 (`27d352db364f`) | `alphaUpscalingEnabled` |
|
||||
| `sl::Constants` (`include/sl_consts.h`) | 1 | v2.0.0 (`db6f37adcf66`) | every member through `motionVectorsJittered` — the matrices, `jitterOffset`, `mvecScale`, `cameraPinholeOffset`, the camera's position and axes, `cameraNear`, `cameraFar`, `cameraFOV`, `cameraAspectRatio`, `motionVectorsInvalidValue`, the seven `Boolean`s |
|
||||
| | 2 | v2.4.0 (`bba15338a623`) | `minRelativeLinearDepthObjectSeparation` |
|
||||
| `sl::FeatureVersion` (`include/sl.h`; `include/sl_core_types.h` from v2.7.2) | 1 | v2.0.0 (`fc2d6ee39fea`) | `versionSL`, `versionNGX` |
|
||||
| `sl::FeatureRequirements` (the same headers) | 1 | v2.0.0 (`fc2d6ee39fea`) | `flags`, `maxNumCPUThreads`, `maxNumViewports`, `numRequiredTags`, `requiredTags`, `osVersionDetected`, `osVersionRequired`, `driverVersionDetected`, `driverVersionRequired`, then ten Vulkan members from `vkNumComputeQueuesRequired` to `vkFeatures13` |
|
||||
| | 2 | v2.1.0 (`79037e0974d2`) | `vkNumOpticalFlowQueuesRequired` |
|
||||
|
||||
`sl::DLSSOptions` keeps those seventeen declarations, same types and order, through v2.14.16 (`9a875bd4f843`); v2.8.0
|
||||
only re-spelled the deprecated `sharpness`. `sl::Constants` is unchanged from v2.4.0 through v2.14.16
|
||||
(`15589e577df9`). Streamline 1.x is refused before any read (`SpeaksStreamline2`). **Since 0.1.0-beta.43 the
|
||||
Overlay reads `sl::Constants`, and only members of version 1** — nothing of version 2 — so no version test beyond
|
||||
"at least 1" is needed, and the read ends before `minRelativeLinearDepthObjectSeparation`, the member version 2
|
||||
added.
|
||||
|
||||
**The two answers about a feature** (established 2026-11-12, the same way, over the same sixteen tags):
|
||||
`sl::FeatureVersion` is two members at every tag, and `sl::FeatureRequirements` is the nineteen of v2.0.0 plus the
|
||||
one v2.1.0 added, unchanged through v2.14.16 (`a255f5c5e99a`). `sl::Version` is three `uint32_t` — `major`, `minor`,
|
||||
`build` — in `include/sl_version.h` from v2.0.0 (`deec7cd04363`) to v2.14.16 (`dc3041ae8b44`), and the two functions'
|
||||
declarations are the same at both ends: `sl::Result slGetFeatureVersion(sl::Feature, sl::FeatureVersion&)` and
|
||||
`sl::Result slGetFeatureRequirements(sl::Feature, sl::FeatureRequirements&)`. **Since 0.1.0-beta.44 the Overlay reads
|
||||
both, and only members of version 1**: the read of the requirements ends at `driverVersionRequired`, before the first
|
||||
Vulkan member, so no version test beyond "at least 1" is needed.
|
||||
|
||||
**FidelityFX** (`GPUOpen-LibrariesAndSDKs/FidelityFX-SDK`; tags v1.1.0 — FSR 3.1.0, the first ffx-api — v1.1.1,
|
||||
v1.1.2, v1.1.3, v1.1.4, v2.0.0, v2.1.0, v2.2.0, v2.3.0, v2.4.0). The descriptor header carries a `type` and no size
|
||||
or version, so the question is whether the declaration ever changed:
|
||||
|
||||
| Struct | Tags | Result |
|
||||
|---|---|---|
|
||||
| `ffxDispatchDescUpscale` | v1.1.0 (`68860479bb94`) … v2.4.0 (`9d4a3e5f6c60`) | **one declaration in all ten**: twenty-three members, `flags` the last |
|
||||
| `ffxConfigureDescFrameGeneration` | v1.1.0 (`0ecdd4b4e59b`) … v2.4.0 (`823a3b4720f1`) | **one declaration in all ten**: thirteen members |
|
||||
| `FfxApiResource`, `FfxApiResourceDescription`, `FfxApiFloatCoords2D`, `FfxApiDimensions2D`, `FfxApiRect2D` | v1.1.0 … v2.4.0 | one declaration each in all ten |
|
||||
| `ffxQueryDescUpscaleGetGPUMemoryUsage` (`0x00010008`), `FfxApiEffectMemoryUsage` | from v1.1.2 | one declaration since; a game that sends the type knows the struct |
|
||||
| `ffxQueryDescUpscaleGetGPUMemoryUsageV2` (`0x00010009`) | from v2.0.0 | one declaration since |
|
||||
|
||||
**What follows for a hook** (Advanced metrics, train B):
|
||||
|
||||
- `sl::DLSSOptions`: a member is read at `structVersion >=` the row that adds it — never "at least 1" for the tail.
|
||||
- `sl::Constants`: everything this project may read is version 1's. The camera's position, axes and matrices are
|
||||
never read at any version (rule 4; the catalog's `PlayerState`).
|
||||
- `ffxDispatchDescUpscale`, `ffxConfigureDescFrameGeneration`: every member may be read on the ffx-api route, since
|
||||
no ffx-api release has a shorter one. `ffxDispatchDescFrameGenerationPrepareV2`'s camera arrays are never read.
|
||||
- **Not established, so nothing more is read there**: the FSR 3.0 host's legacy descriptors (`fsr3-v3.0.x`) beyond
|
||||
the `renderSize` the existing hook pins; any struct of a Streamline or FidelityFX release newer than the last tag
|
||||
above — a re-vendoring re-runs this comparison (`third_party/*/README.md` §Checklist).
|
||||
|
||||
### Ray tracing
|
||||
| Hook | Yields |
|
||||
|---|---|
|
||||
@@ -480,7 +334,7 @@ or version, so the question is whether the declaration ever changed:
|
||||
| Hook / call | Yields |
|
||||
|---|---|
|
||||
| ~~`IDXGIAdapter3::QueryVideoMemoryInfo` (we **call** it, not hook it, once per second from our own thread)~~ | ~~**Per-process VRAM** `CurrentUsage` + `Budget` — previously impossible; now exact~~ **Never built; superseded 2026-10-03 (D43):** the game's memory is read from OUTSIDE the game by the Agent (`18_GPU_VENDOR_APIS` §The game process's memory), so nothing in the Overlay calls it. Only the budget would need it, and that stays open (`20_OPEN_QUESTIONS` §M11) |
|
||||
| NVAPI Reflex: ~~hook `NvAPI_D3D_SetSleepMode`, `NvAPI_D3D_SetLatencyMarker`~~; call `NvAPI_D3D_GetLatency` and `NvAPI_D3D_GetSleepStatus` *(the two hooks cannot be: neither function is an export — `20_OPEN_QUESTIONS` §M14. **The calls are made since 0.1.0-beta.47** — §Calls the Overlay makes into a driver, above; owner decisions D132, D136)* | Reflex on/off + PC latency breakdown. Declarations come from the vendored MIT NVAPI headers (`18_GPU_VENDOR_APIS` §L3); the Overlay links them like any other header. NVIDIA-only — the whole block compiles out to a no-op capability flag elsewhere |
|
||||
| NVAPI Reflex: hook `NvAPI_D3D_SetSleepMode`, `NvAPI_D3D_SetLatencyMarker`; call `NvAPI_D3D_GetLatency` | Reflex on/off + PC latency breakdown. Declarations come from the vendored MIT NVAPI headers (`18_GPU_VENDOR_APIS` §L3); the Overlay links them like any other header. NVIDIA-only — the whole block compiles out to a no-op capability flag elsewhere |
|
||||
|
||||
### Explicitly not hooked
|
||||
Input APIs, file I/O, network, memory allocators, window messages beyond what the overlay needs, anything game-specific. Rule 4 in CLAUDE.md.
|
||||
@@ -657,11 +511,9 @@ static_assert(sizeof(FlFrameRecord) == 64);
|
||||
> v3 makes it safe by CONSTRUCTION. Every enum's 0 is now `NOT_REPORTED`, and
|
||||
> `rtFlags`' polarity is flipped so its bits mean *observed*.
|
||||
>
|
||||
> Four answers items 4/6/7 owe had no home and now do: DLSS **with** Ray
|
||||
> Reconstruction (`featureFlags`, since RR was a mutually exclusive
|
||||
> `upscaler` value — *corrected 2026-11-14: this said "DLSS-SR and Ray
|
||||
> Reconstruction concurrently"; RR runs instead of super resolution, it is still
|
||||
> DLSS*), `upscalerSharpness`, and — in `FlWriterState`, because they
|
||||
> Four answers items 4/6/7 owe had no home and now do: DLSS-SR **and** Ray
|
||||
> Reconstruction concurrently (`featureFlags`, since RR was a mutually exclusive
|
||||
> `upscaler` value), `upscalerSharpness`, and — in `FlWriterState`, because they
|
||||
> are session facts and not per-frame — the device **RT tier** without which
|
||||
> `03_METRICS`' definite RT `No` had no producer at all, plus `rtStateObjectsCreated`
|
||||
> and `rasterPsoCreated`.
|
||||
@@ -719,7 +571,7 @@ Field notes — each of these was a defect in an earlier revision:
|
||||
- **SPSC lock-free ring**, capacity a power of two (default 8192 records = 512 KB), overwrite-oldest.
|
||||
- Writer/reader seqlock protocol, including the rule that the payload write must
|
||||
**exclude** the `seq` field and that `seq` is never reset: `07_IPC` §Protocol rules.
|
||||
- Header: ~~three~~ **four** separate 64-byte lines before the ring — and, since layout 5 (2026-11-11), region 5's twenty-three, which the watchdog alone writes and only while the Agent asks (`07_IPC` §Region 5) — *(corrected 2026-10-04: since layout 4, 2026-09-27,
|
||||
- Header: ~~three~~ **four** separate 64-byte lines before the ring *(corrected 2026-10-04: since layout 4, 2026-09-27,
|
||||
beta.10, `FlDisplayState` at 0xC0 — Overlay-written at most every 500 ms; the ring starts at 0x100)* — `FlShmHandshake` (write-once),
|
||||
`FlWriterState` (Overlay-written: `writeIndex`, `status`, `apiMask`, `faultCount`),
|
||||
and `FlControlBlock` (**Agent**-written: `pauseRequested`, `unhookRequested`,
|
||||
@@ -727,7 +579,7 @@ Field notes — each of these was a defect in an earlier revision:
|
||||
header — they are written by the other process, and mixing them into an
|
||||
Overlay-written line reintroduces exactly the false sharing the split exists to
|
||||
prevent. Layout is normative in `07_IPC` §A + B.
|
||||
- **The hot path performs: one QPC read, a few field reads from cached state, one 60-byte store, two relaxed atomic stores and two compiler fences.** No syscall, no allocation, no lock, no logging. Target ≤ 1 µs per present. *(Added 2026-10-04: the summary leaves out the per-present `IDXGISwapChain::GetLastPresentCount` call (§H5, the `dxgiUnseen` count) and the display sample every 500 ms at most (region 4).)* *(Added 2026-11-13, train C, 0.1.0-beta.47: after the store, one relaxed load of the latency gate; and, while a session asks for Advanced metrics and the watchdog armed one, a call into the driver about once a second — §Calls the Overlay makes into a driver. That call is the one thing on this path that is not bounded by FrameLedger's own code: 0.5–2.6 µs measured against the installed driver, and a call of 2 ms or more is the last.)*
|
||||
- **The hot path performs: one QPC read, a few field reads from cached state, one 60-byte store, two relaxed atomic stores and two compiler fences.** No syscall, no allocation, no lock, no logging. Target ≤ 1 µs per present. *(Added 2026-10-04: the summary leaves out the per-present `IDXGISwapChain::GetLastPresentCount` call (§H5, the `dxgiUnseen` count) and the display sample every 500 ms at most (region 4).)*
|
||||
- Per-frame mutable state (current upscaler, render res, dispatch counts) lives in a small struct updated by the feature hooks and *read* by the present hook; counters reset at present.
|
||||
|
||||
## The watchdog thread — the only thread we add to the game
|
||||
@@ -791,9 +643,8 @@ Every hook body is wrapped:
|
||||
```
|
||||
|
||||
- Any SEH exception inside our code ⇒ increment `faultCount`, record which hook, **return control to the original function** so the game continues.
|
||||
- 3 faults total ⇒ set `status = self_disabled`, ~~uninstall all hooks (`MH_DisableHook(MH_ALL_HOOKS)`)~~ restore each patch's prologue only while its bytes are still our jump (compare-and-restore per patch through `StopObserving`, §Unhooking, §H7 — `MH_ALL_HOOKS` would have removed an overlay chained after us; corrected 2026-09-27; since 0.1.0-beta.46 the patches that are still ours come out together, under one stop of the threads — §Unhooking, Batches), stop writing, stay dormant. The Agent sees the flag and finalizes the session as `degraded`.
|
||||
- 3 faults total ⇒ set `status = self_disabled`, ~~uninstall all hooks (`MH_DisableHook(MH_ALL_HOOKS)`)~~ restore each patch's prologue only while its bytes are still our jump (compare-and-restore per patch through `StopObserving`, §Unhooking, §H7 — `MH_ALL_HOOKS` would have removed an overlay chained after us; corrected 2026-09-27), stop writing, stay dormant. The Agent sees the flag and finalizes the session as `degraded`.
|
||||
- Never `__try` around the call to the original function — only around *our* code, so we never mask a game bug as ours or vice versa.
|
||||
- **One exception, since train C (2026-11-13): the two driver getters the Overlay calls itself** (§Calls the Overlay makes into a driver) are under a guard of their own, `fl_reflex.h`'s, with the same filter. They are not "the original function" — the game did not make these calls, we did, so a fault in them is ours to answer for. It is counted once through `NoteFault`, and the read is switched off for the process in the same breath, so that one fault cannot become the three that self-disable. **A caught fault does not give back a lock the driver held**: the guard is containment, not safety, which is why nothing is called again after it.
|
||||
- The trampoline call to the original is always executed exactly once, on every path, including error paths.
|
||||
|
||||
## Unhooking
|
||||
@@ -812,94 +663,6 @@ Every hook body is wrapped:
|
||||
> foreign one in ctest `fl_unhook_inline` (the vtable form stays in `fl_unhook_preserves_foreign`), and
|
||||
> against the injected Overlay in ctest `fl_guard` `[log]`, where every patch reads `UNHOOK_RESTORED`
|
||||
> because the harness is alone in its process.
|
||||
>
|
||||
> **The registry refuses what it cannot hold, and a patch is registered before it can run (0.1.0-beta.42,
|
||||
> `fl_patch_registry.h`).** The registry was an array and a counter, and two things were wrong with it — found by
|
||||
> reading the code for the plan of the next two hooks, not by a failure. **Full meant silent:** `RegisterPatch`
|
||||
> wrote its entry only while it fitted, after `PatchTarget` had already enabled the hook, so a 49th patch would
|
||||
> have been live and unknown to the stop, with no line anywhere. (Twenty patch sites exist; the rule no longer
|
||||
> depends on that count being right, and a `static_assert` now checks the capacity against the inventory's own row
|
||||
> count plus the seven sites that are not rows.) **Enabled before registered:** `PatchTarget` enabled the hook,
|
||||
> re-read `g_observing`, and registered last; a stop between the re-read and the registration walked a table
|
||||
> that did not hold the patch yet, and the patch stayed in after "stopped". The DXGI three and the loader detour
|
||||
> registered after enabling too, with no re-read at all.
|
||||
>
|
||||
> One sequence now, `fl::patch::Install`: **take a slot — no slot, no patch, nothing created — create, enable,
|
||||
> commit the slot, then re-read the flag.** The stop clears the flag and then walks the committed slots. Each side
|
||||
> writes and then reads what the other wrote, sequentially consistent, so at least one sees the other: the walk
|
||||
> restores the patch, or the installer finds the flag clear and takes its own patch out (and retires the slot,
|
||||
> so the walk does not report it as somebody else's). A slot whose patch failed is free again; one that was ever
|
||||
> live is never reused — the walk reads it without a lock. Nothing is created once observing is off. A patch
|
||||
> that did not go in is logged once per target and reason, `PATCH_FAILED a=<reason>` (`2` stopped, `3` registry
|
||||
> full, `4` create failed, `5` enable failed, `6` the stop arrived meanwhile); until now every such failure was
|
||||
> silent. The three DXGI patches are still enabled together and keep the same rules by hand; when any step of
|
||||
> theirs fails, whatever a partial enable left in is taken out — it used to stay, unregistered, with init
|
||||
> reporting failure. And two stores that could overwrite a stop's reason no longer do: `READY` is written only
|
||||
> over `INIT`, and init's failure path stores nothing. No hook body changed. ctest `fl_unhook_inline` drives
|
||||
> the shipped sequence against real MinHook patches: a full registry leaves the target's bytes untouched and
|
||||
> MinHook unasked; a stop arranged between the enable and the re-read ends with the function unpatched; a failed
|
||||
> patch gives its slot back; a slot is invisible to the walk until committed.
|
||||
>
|
||||
> **Batches, 0.1.0-beta.46 (owner decision D134): one stop of the game's threads for a group of patches.** MinHook
|
||||
> writes a jump with every other thread of the process stopped — a snapshot of the system's threads, then a
|
||||
> suspend, a context read and a resume for each of the process's — and `MH_EnableHook` / `MH_DisableHook` for one
|
||||
> target do all of that for one jump. The owner's logs of 2026-11-13 put a number on it: the thirteen Streamline
|
||||
> patches took 0.74 s to 2.8 s of a game's start, 57 to 215 ms each, and a stop restored its patches the same way.
|
||||
> MinHook 1.3.4 can queue — `MH_QueueEnableHook` / `MH_QueueDisableHook` mark a hook, `MH_ApplyQueued` executes
|
||||
> every mark under one stop — and `fl_patch_registry.h` now has the two sequences that use it:
|
||||
> `fl::patch::Batch` (`Add`: slot and create, nothing marked; `Commit`: enable them all) and
|
||||
> `fl::patch::RestoreAll`, which is the stop's walk. `InstallUpscalerHooks` queues every row a tick finds
|
||||
> something for and commits once, before the families that are published "when whole"; `InstallRtHooks` batches
|
||||
> its two; `StopObserving` calls `RestoreAll`. A patch's `HOOK_INSTALLED` line, family bit and latch still come in
|
||||
> that order and only once it is in. The loader detour, OpenGL and the three DXGI patches of init are as they were.
|
||||
>
|
||||
> **What the queue makes dangerous, and what the code therefore never does** (the plan was reviewed against
|
||||
> `hook.c` before a line was written, and its first form was refused). `MH_ApplyQueued` applies **every** hook
|
||||
> whose mark differs from its state — the process has one table, not one per caller. So (1) **no mark is ever left
|
||||
> standing**: a hook that failed to enable has its mark removed, or the next apply — the stop's own — would enable
|
||||
> it; (2) **only a patch that is still ours is ever marked for a restore** (`StillOurs`, as before; §H7), and
|
||||
> nothing is marked "all" — the refused draft marked everything and then un-marked what it must not restore, and
|
||||
> un-marking a hook that is already out marks it for *enabling*: the stop would have put a patch back in after the
|
||||
> stop; (3) **mark, apply and commit happen inside a gate** (`MinHookEngine::BeginQueue`, a slim lock taken
|
||||
> exclusively) so the watchdog's apply cannot execute the stop's marks nor the stop's the watchdog's. The gate is
|
||||
> held for one apply and never across a symbol lookup, which takes the loader's lock. It is the one lock in the
|
||||
> Overlay, and it is on no hook body's path: the only way from a hook to it is the stop itself, which already
|
||||
> waited for MinHook's own lock and a stop of the threads for every patch. Its owner re-enters it without
|
||||
> waiting. **The verdict on an install is the engine's, not the bytes'**: a foreign overlay patching over us a
|
||||
> moment after the apply would read as "not in", and treating that as a failure would mark a restore nobody had
|
||||
> compared. `MH_ApplyQueued` stops at the first hook that fails and says only that one did; the ones after it
|
||||
> are then enabled — or, in the stop, restored — one at a time, so one bad patch still costs one patch.
|
||||
> The write-then-read pair is unchanged: the stop clears the flag and then walks; `Commit` commits its slots and
|
||||
> then re-reads the flag, and takes out — compared first — what it put in when the flag is clear. A stop that
|
||||
> lands before the commit enables nothing.
|
||||
>
|
||||
> **Measured** on `hook-harness`'s Streamline target, the development PC, three runs before and after (`fl_guard`
|
||||
> `[advanced]` prints them): the nine Advanced-only patches went in one by one over 0.60 s / 0.70 s / 0.60 s
|
||||
> from the first log line to the ninth, 76–88 ms each; as one batch they take **81 / 90 / 78 ms**. The stop restored
|
||||
> eighteen patches in 1.37 s / 1.56 s / 1.37 s; under one apply, **77 / 90 / 76 ms** — and from the Agent's request
|
||||
> to `UNHOOKED`, 1.27–1.48 s became 94–110 ms. One stop of the threads costs what it cost for one patch, whether it
|
||||
> covers four, nine or eighteen. A new log line says so in the field: `PATCH_BATCH install` / `restore`, `a` the
|
||||
> microseconds, `b` the patches. ~~**Not measured:** a real game — how long one stop of the threads is with a few
|
||||
> hundred of them, and whether any title minds patches arriving together (owner-only item 44).~~ **In real games**
|
||||
> (the owner's five sessions of 2026-11-13 on 0.1.0-beta.46 — Hogwarts Legacy, Phantom Blade Zero, Black Myth:
|
||||
> Wukong, Cyberpunk 2077, Clair Obscur: Expedition 33; eighteen install batches of two to sixteen patches): every
|
||||
> batch went in whole, with the hooks beta.45 installed and no `PATCH_FAILED`; **sixteen batches cost 81–262 ms
|
||||
> whatever they held**, which is what one patch cost in the same game before. Streamline's thirteen, first line to
|
||||
> last on beta.45 against the one batch now: Phantom Blade Zero 0.74–0.85 s → 88 ms, Cyberpunk 2077 1.18 s → 93 ms
|
||||
> (with three more patches in the batch), Black Myth: Wukong 1.65 s → 188 ms (twelve), Hogwarts Legacy 2.80 s →
|
||||
> **1.26 s**. That last one and a batch of three in Cyberpunk 2077 (**0.61 s**) are not explained: the cost does
|
||||
> not follow the count — sixteen patches in 93 ms, three in 609 ms — and **the log cannot tell one long stop from an
|
||||
> apply that failed part-way and was finished one patch at a time**, because a batch writes a line only for a patch
|
||||
> that fails for good. **Since 0.1.0-beta.47 the line says which** (owner decision D137): `install` or `restore` is a batch that went under its one apply; `install singly` or `restore singly` is one whose apply said it had failed, and the high half of `b` then counts the patches handed to MinHook one at a time (`b=0x0003000d`: thirteen in, three of them singly) — attempts, not stops: MinHook makes no stop for a patch the failed apply had already done. So a long `a=` on a plain `install` line is one long stop of the threads. ~~**Still not measured: the restore in a real game**~~ **The restore in a real game** (the owner, 2026-11-14,
|
||||
> Phantom Blade Zero, twice): twenty-nine patches out under one apply of **83 ms and 86 ms**, every one restored,
|
||||
> none declined, and the game went on for minutes and closed cleanly (owner-only item 44 (d)). One more thing the
|
||||
> queue changes for the better: MinHook's single-target disable does not move a thread that is suspended inside
|
||||
> the patched bytes (`hook.c` passes the enable action to its thread fix-up in both directions); the queued apply
|
||||
> does. ctest `fl_unhook_inline` drives `Batch` and `RestoreAll` against real MinHook (three in under one apply,
|
||||
> a duplicate target refused without holding the others up, a foreign patch left byte for byte) and against a
|
||||
> model of MinHook's table for what real MinHook cannot be made to do on demand: an apply that fails halfway or
|
||||
> not at all, a stop inside the apply, a committed patch that is already out — the refused draft's failure — and
|
||||
> that no mark is ever standing or made outside the gate.
|
||||
|
||||
~~`FlRequestUnhook()` (or the control flag) ⇒ `MH_DisableHook(MH_ALL_HOOKS)`, restore vtable entries **only where they are still ours**, flush the ring, set status.~~ *(Corrected 2026-10-04: both reach `StopObserving` — compare-and-restore per patch as the note above says, then the status; there is no `MH_ALL_HOOKS`, no vtable entry and no ring flush. The watchdog flushes the native log on its way out.)* **The DLL is not `FreeLibrary`'d from the live process** — a thread could still be inside a trampoline. It goes dormant and unloads with the process. This is deliberate and documented.
|
||||
|
||||
@@ -928,12 +691,6 @@ before it. And when the slot has changed, going dormant costs nothing: we stay
|
||||
loaded anyway, and our detour remains in someone else's chain doing nothing
|
||||
harmful.
|
||||
|
||||
> **Said plainly, 2026-11-13: for the inline patches that re-check has never been made.** MinHook owns the write
|
||||
> window — it stops the threads, changes the protection and writes — and `StillOurs` is asked before it is called,
|
||||
> not inside. Between the two a foreign overlay could patch over us, on a thread MinHook has not stopped yet. The
|
||||
> batches of 0.1.0-beta.46 neither close that window nor widen it: the comparison and the write are apart by one
|
||||
> stop of the threads, as they were for each patch, once instead of once a patch.
|
||||
|
||||
Verified by `hook-harness --probe-unhook` (ctest `fl_unhook_preserves_foreign`),
|
||||
which simulates the foreign hooker rather than depending on RTSS being
|
||||
installed, so it is deterministic and runs on CI. Both halves are asserted: we
|
||||
@@ -945,41 +702,13 @@ compare-and-restore that never restores is not a fix.
|
||||
No logging in hook bodies. A small fixed-size in-memory ring of structured events (hook installed, symbol missing, fault, unhook) is flushed to `logs\overlay-<pid>-*.log` by the init thread at session end, on unhook, or on Agent request — never mid-frame.
|
||||
|
||||
> **Built 2026-09-06 (P1 item 4), as specified, with the details a bug report needs.** A ring of 256 ×
|
||||
> ~~64-byte events (`qpc`, code, two operands, a 40-char name)~~ 96-byte events (`qpc`, code, two operands, a
|
||||
> 72-char name — 64 bytes and 40 characters until beta.42) appended with one `fetch_add` from init and
|
||||
> 64-byte events (`qpc`, code, two operands, a 40-char name) appended with one `fetch_add` from init and
|
||||
> watchdog paths and from a hook's **SEH handler** — `NoteFault` records the exception code and the hook's
|
||||
> `__func__` — never from a hook body. Codes: `RING_CREATED`, `PRESENT_HOOKS`, `HOOK_INSTALLED` (one per
|
||||
> patch, with the target address), `SYMBOL_MISSING` (once per pair, and only when the module IS mapped),
|
||||
> `FAULT`, `STOP` (the reason), `UNHOOK_RESTORED` / `UNHOOK_DECLINED` (one per patch), `LOADER_DETOUR`,
|
||||
> `SUPERVISION_LOST`, since beta.24 `STOP_FLUSHED` (the last line after a stop: `a=1` when the stop had finished
|
||||
> writing), and since beta.42 `PATCH_FAILED` (a patch that did not go in, once per target and reason — §Unhooking)
|
||||
> and `FFX_DISPATCH`, `FFX_QUERY`, `UPSCALE_ROUTE`, `RUNTIME_CENSUS` (the note at the end of this section), and
|
||||
> since beta.43 `FFX_CONFIGURE` — each configure type a hooked ffx module was handed, in a process where
|
||||
> `ffxConfigure` is hooked at all (one asked for Advanced metrics) — and since beta.46 `PATCH_BATCH`: one line an
|
||||
> apply, `install` or `restore`, `a` the microseconds it took and `b` the patches it covered (§Unhooking, Batches).
|
||||
> **`LATENCY` (train C, 0.1.0-beta.47)**: one line each time the state of the driver read changes — `a` the
|
||||
> `FlLatencyState`, the text what it means — and, when the module is found, two more with the end of the path
|
||||
> `nvapi64.dll` was loaded from and of the image its getters are in. Written by the watchdog; a fault in a getter
|
||||
> is a `FAULT` line from the presenting thread, as any fault is.
|
||||
> **`LATENCY_FRAMES` (0.1.0-beta.49, owner decisions D148, D151)**: the frames the driver reads summed, counted
|
||||
> for this log and nowhere else — nothing of it is published, stored or shown. Each summed frame is placed by its
|
||||
> own two numbers, the span between its two GPU marks and the driver's active render time: no start mark, a span
|
||||
> of no length, an active time with no span, a span with no active time, and — where a frame has both — *active
|
||||
> longer than the span* or *active within the span*, each with its count and both sums in microseconds. No
|
||||
> threshold: a span of one microsecond is a span. **A batch is seven lines and belongs to one state of the driver's
|
||||
> sleep status** — its low-latency switch, its "the game sleeps" switch and its frame-generation multiplier —
|
||||
> because the counts mean nothing apart from it: a read in another state closes the batch first (thirty-two such
|
||||
> closings a request, after which a batch runs to its length and its first line says what it held). A batch is
|
||||
> also written after a request's tenth read, its thirtieth and every sixtieth from there, when the Agent asks for
|
||||
> a flush, at a new request and at a stop. `a` is printed in decimal and `b` in hex: *reads* and the switches
|
||||
> seen on, off (`<<8`) and the multipliers seen (`<<16`); *frames summed* and refused; *GPU span absent* and of no
|
||||
> length; *active time with no span* and span with no active time; then the two heaps, `a` their frames and `b`
|
||||
> their span sum (`<<32`) and active sum; and the watchdog's own line — the *milliseconds the batch spans* and its
|
||||
> ticks in them, on time (`<<32`) and woken early: a read a second is a thousand milliseconds a read and as many
|
||||
> periodic ticks as reads (D150). **A game that exits by itself takes the batch in hand with it** — under a
|
||||
> minute of reads. About seven lines a minute while a session with *Advanced metrics* reads the driver; none
|
||||
> otherwise.
|
||||
> **Three flush points — four since beta.42, the same note —, none on a present path:** the end of `InitThread` (so the
|
||||
> `SUPERVISION_LOST`, and since beta.24 `STOP_FLUSHED` (the last line after a stop: `a=1` when the stop had finished
|
||||
> writing). **Three flush points, none on a present path:** the end of `InitThread` (so the
|
||||
> file exists from the start of the session and a crash mid-session still leaves it), the watchdog when
|
||||
> `FlControlBlock.logFlushRequested` changes (a counter the Agent bumps at session end; nothing clears it),
|
||||
> and the watchdog on its way out after any stop. Appended, never recreated; events overwritten before a
|
||||
@@ -990,59 +719,15 @@ No logging in hook bodies. A small fixed-size in-memory ring of structured event
|
||||
> it reads 0. When the stop ran on a presenting thread — `MayObserve`'s one-frame safety stop — the watchdog's one
|
||||
> final flush could run while that thread was still writing, and the lines after it (the kernelbase loader detour is
|
||||
> the last patch) reached the ring after the last flush ever made. The stop now says when its last line is in, and
|
||||
> wakes the watchdog; the final flush waits for that, bounded at 2 s *(a quarter of a second for every patch the registry can hold since beta.45; the stop is one apply since beta.46 and the bound is for its fallback)*, then writes `STOP_FLUSHED`. And each slot has a
|
||||
> wakes the watchdog; the final flush waits for that, bounded at 2 s, then writes `STOP_FLUSHED`. And each slot has a
|
||||
> commit word written after its fields: `LogNote` claims a slot with one `fetch_add` and fills it afterwards, so a
|
||||
> flush on another thread could print a slot still being filled. A flush now prints only slots whose writer has
|
||||
> finished — an ordinary flush stops at the first that is not, for the next one; the final flush names it in a `#`
|
||||
> line. Nothing on a present path changed. Path: `%LOCALAPPDATA%\FrameLedger\logs\overlay-<pid>-<yyyymmdd-hhmmss>.log`,
|
||||
> resolved by `SHGetKnownFolderPath` (§S21's rule, not the environment). No allocation: static ring,
|
||||
> static 64 KiB format buffer, static path. The CaptureHost prints the file and its `FAULT` / `STOP` /
|
||||
> `UNHOOK_*` / `SYMBOL_MISSING` / `PATCH_FAILED` / `SUPERVISION_LOST` lines at the end of every session
|
||||
> `UNHOOK_*` / `SYMBOL_MISSING` / `SUPERVISION_LOST` lines at the end of every session
|
||||
> (`Consume/OverlayLog.cs`).
|
||||
>
|
||||
> **The log outlives the game, and says what each ffx module was handed (0.1.0-beta.42, owner decision D121).**
|
||||
> Cyberpunk 2077, set to FSR upscaling with FSR frame generation, was recorded with frame generation measured and
|
||||
> the upscaler "unknown": PREPARE and FRAMEGENERATION dispatches arrived and no UPSCALE ever did. The log could
|
||||
> not say why. **It ended half a second into the session** — written at the end of init, then only when the Agent
|
||||
> asked or a stop ran, and a game that exits does neither: the watchdog dies with the process. And **it could not
|
||||
> have said much**: the two one-target rows logged their symbol and every other row the word `hook`, so four ffx
|
||||
> modules were one indistinguishable line each. Four changes, none of them a new patch site:
|
||||
>
|
||||
> 1. **A fourth flush point: the watchdog, on any tick that finds something new in the ring** (`FlushLogIfNew`:
|
||||
> one load on an uneventful tick, no file opened). Events are few and bounded — installs, first sights, three
|
||||
> faults at most — so this is a handful of appends a session. The init thread's flush moved to **before** the
|
||||
> watchdog is created: `FlushLog`'s state belongs to one thread at a time, and with the watchdog flushing on its
|
||||
> first tick the old order could run two at once.
|
||||
> 2. **Every install line names its module and its symbol** — `amd_fidelityfx_dx12.dll!ffxDispatch` — built at
|
||||
> compile time from the inventory row's own two spellings (`fl::inventory::NameOfRow`), so no second list of
|
||||
> names exists. The same name is on the `UNHOOK_*` and `PATCH_FAILED` lines. The event's text grew from 40 to
|
||||
> 72 characters for it (an event is 96 bytes; the ring 24 KiB, static), and `PatchTarget` lost its default
|
||||
> name, so a new call site cannot log `hook`.
|
||||
> 3. **`FFX_DISPATCH` / `FFX_QUERY`: each descriptor type a hooked ffx-api module was handed, once**
|
||||
> (`fl_ffx_types.h`). Text = the module, `b` = the type (`0x10001` UPSCALE, `0x20004` / `0x2000c` PREPARE,
|
||||
> `0x20003` FRAMEGENERATION, …); `a` ≠ 0 with `b=0` says what did not fit (`1` a ninth distinct type, `2` a
|
||||
> type of zero). The detour keeps the value of `type` — the member it reads already to choose an arm — in the
|
||||
> first free of eight slots per module and entry point; the watchdog writes it. A query's type is kept whatever
|
||||
> the vendor answered. `UPSCALE_ROUTE` names each source an UPSCALE came from, once (the FSR 3.0 host has no
|
||||
> descriptor type, so this is the only line that says its export was called), and `RUNTIME_CENSUS` repeats the
|
||||
> census word (`b`) whenever it gains a bit — both from words the detours kept before, at no cost to a hook.
|
||||
> 4. **`PATCH_FAILED`** (§Unhooking) is the fourth: a patch that did not go in used to leave no line at all.
|
||||
>
|
||||
> **This is a diagnostic, not a measurement, and it is not behind the Advanced-metrics switch** — like
|
||||
> `HOOK_INSTALLED`, it reaches the log file and nothing else: no record, no region of the shared memory, no session.
|
||||
> Rule 4: the only thing read is `type`, of a descriptor handed to a hooked call. Rule 5: no allocation, no lock,
|
||||
> no logging in the body; a type already kept costs loads and no write.
|
||||
>
|
||||
> **Measured overhead** (on `fl_ffx_types.h` itself with the Overlay's compile flags — `/O2 /GS /guard:cf
|
||||
> /Qspectre`, 50 million calls a run, three runs, i7-14700KF): a frame's three dispatch types in turn, **+3.8 ns a
|
||||
> dispatch** (3.79 / 3.87 / 3.81); a type in the first slot +0.9 to +1.0 ns; in the eighth, the worst steady
|
||||
> state, +8.1 to +8.4 ns. A new type costs one compare-exchange, once per type and module.
|
||||
>
|
||||
> ctest `fl_ffx_types` (the header, including eight threads meeting the same six types at once: each kept exactly
|
||||
> once) and `fl_guard` `[log]`: a harness on the 1.1.x monolith, generating frames and asking a ratio query, is
|
||||
> supervised and told **nothing else** — no flush request, no stop — and its log holds the two install lines by
|
||||
> module and symbol, the three dispatch types and the query type once each, the route and the census; the process
|
||||
> is then killed and the file is as it was, one header, no `STOP`.
|
||||
|
||||
> **Tests and the real logs folder (2026-09-15).** The injection tests use the shipped Overlay, so their harness
|
||||
> logs land in the user's real `logs\` too: measured that day, 2506 overlay logs, **2492 of them hook-harness's**,
|
||||
@@ -1068,7 +753,7 @@ verification a dev-machine-only affair before:
|
||||
- **WARP** (`D3D_DRIVER_TYPE_WARP`) — a software rasteriser, so no adapter is required.
|
||||
- **`CreateSwapChainForComposition`** — no `HWND`, so no dependency on a window station or an interactive session.
|
||||
|
||||
Current modes: `--probe-vtable` (§H4, ctest `fl_vtable_indices`), `--probe-proxy` (§H5, ctest `fl_proxy_swapchain`), `--probe-unhook` (§H7, ctest `fl_unhook_preserves_foreign`), `--probe-cost` (NFR-1, measurement only), **`--probe-frames`** (ctest `fl_frame_identity` — what counts as a frame, against `GetLastPresentCount`), **`--probe-d3d12`** (ctest `fl_d3d12_acquisition` — device → command queue → swapchain), `--present N`, `--hold N`, **`--real`** and **`--plus-ui K``**, **`--vulkan --hold-presenting N`** (P1 item 3, real loader, exit 77 = cannot run here) and **`--opengl --hold-presenting N`** (P1 item 4, gdi32 `SwapBuffers` on a hidden window, Microsoft's generic renderer — runs on CI). *(Added 2026-10-04, each with its own ctest: `--probe-d3d12-vtable`, `--probe-dxr`, `--probe-dxr-inputs`, `--probe-upscaler-resolve`, `--probe-sl-abi`, `--probe-ffx-resolve`, `--probe-sl-inputs`, `--probe-sl-seen`, `--probe-dxgi-count`; and the `--hold-presenting-*` injection fixtures with `--load` / `--load-after-ms`.)* *(Added 2026-11-12, Advanced metrics train B: `--probe-adv-fields`, ctest `fl_adv_fields` — `fl_adv_fields.h` alone: a struct of a lower version is not read past its end, the vendors' sentinels never leave as values, the summaries, the publication, a new request starting afresh; and `--advanced` / `--ffx-memory-query v1|v2`, which make the `--hold-presenting-upscaled` and `--hold-presenting-ffx` fixtures send what Advanced metrics reads.)*
|
||||
Current modes: `--probe-vtable` (§H4, ctest `fl_vtable_indices`), `--probe-proxy` (§H5, ctest `fl_proxy_swapchain`), `--probe-unhook` (§H7, ctest `fl_unhook_preserves_foreign`), `--probe-cost` (NFR-1, measurement only), **`--probe-frames`** (ctest `fl_frame_identity` — what counts as a frame, against `GetLastPresentCount`), **`--probe-d3d12`** (ctest `fl_d3d12_acquisition` — device → command queue → swapchain), `--present N`, `--hold N`, **`--real`** and **`--plus-ui K``**, **`--vulkan --hold-presenting N`** (P1 item 3, real loader, exit 77 = cannot run here) and **`--opengl --hold-presenting N`** (P1 item 4, gdi32 `SwapBuffers` on a hidden window, Microsoft's generic renderer — runs on CI). *(Added 2026-10-04, each with its own ctest: `--probe-d3d12-vtable`, `--probe-dxr`, `--probe-dxr-inputs`, `--probe-upscaler-resolve`, `--probe-sl-abi`, `--probe-ffx-resolve`, `--probe-sl-inputs`, `--probe-sl-seen`, `--probe-dxgi-count`; and the `--hold-presenting-*` injection fixtures with `--load` / `--load-after-ms`.)*
|
||||
|
||||
> **Every present here used to carry `DXGI_PRESENT_TEST`, which submits nothing.** Measured: 500 of them leave `GetLastPresentCount` at 0 while 37 real presents move it by 37. "N presents → N records" was therefore satisfiable only by a writer counting non-frames. `--real` issues real presents; the test-present path is kept as a named mode because it is what an alt-tabbed title actually runs.
|
||||
|
||||
|
||||
+2
-646
@@ -145,7 +145,7 @@ L1 gives no temperatures on its own (unless the D3DKMT probe pans out). That is
|
||||
|
||||
`LibreHardwareMonitorLib` ≥ 0.9.6, consumed as an **unmodified NuGet package**. It already implements per-vendor GPU sensor access internally — which means the vendor-interop licensing problem is one LHM has solved upstream, under a licence that works for us. That is the entire reason this layer exists.
|
||||
|
||||
- `Computer` opened with `IsGpuEnabled` always; ~~`IsCpuEnabled` + `IsMemoryEnabled` only when the Agent is elevated and PawnIO is available~~ nothing else, ever — the CPU temperature uses a separate `Computer` (below) (corrected 2026-10-04). *(2026-11-11: still true of THIS layer's `Computer`. Advanced metrics opens a third one, of its own — the graphics card, and as administrator with PawnIO the processor, memory and motherboard groups; D103, §Advanced metrics. Storage, the power supply, controllers, the battery and the network are opened by nothing.)*
|
||||
- `Computer` opened with `IsGpuEnabled` always; ~~`IsCpuEnabled` + `IsMemoryEnabled` only when the Agent is elevated and PawnIO is available~~ nothing else, ever — the CPU temperature uses a separate `Computer` (below) (corrected 2026-10-04).
|
||||
- Poll on a dedicated thread: `computer.Accept(updateVisitor)` then read mapped sensors. Never faster than 500 ms; default 1000 ms.
|
||||
- Sensor mapping by `SensorType` + name heuristics per vendor (`GPU Core`, `GPU Hot Spot`, `GPU Memory`, `GPU Package Power`, …), kept in `SensorMap.cs` with unit tests against captured sensor-tree fixtures.
|
||||
- **P0 verification items:** (a) which fields LHM actually returns per vendor on real hardware — fill the capability matrix below — **NVIDIA filled 2026-09-03, AMD/Intel deferred (§R5/§R6)**; (b) ~~whether GPU-only usage works **without** elevation and without PawnIO (expected yes, since GPU sensors go through user-mode vendor paths, but confirm — it determines whether the default unelevated Agent has temperatures at all)~~ — **confirmed 2026-09-03, §M5 row R1**: eight fields unelevated, the same eight elevated, PawnIO never opened; (c) ~~confirm LHM's sources are not marked with MPL-2.0 Exhibit B~~ — **done, 2026-08-02: clear.** No source file applies the notice; the only repository hit is the `LICENSE` template itself, and every file we depend on carries the permissive Exhibit A. Method and evidence in `docs/spike-notes.md` §0. Re-check on every version bump, and check *source headers*, never the LICENSE file — MPL-2.0's own text contains Exhibit B as a template, so grepping the licence finds it in every MPL project ever published.
|
||||
@@ -204,8 +204,6 @@ Still resolve **entry points defensively at runtime**: `nvapi64.dll` may be abse
|
||||
> **Not in this build, stated so nobody infers it from the table below:** VRAM (`FlNvSample.vram` is
|
||||
> reserved and its bit is never set — see the Memory row), power, hotspot temperature, per-domain
|
||||
> utilisation beyond the GPU domain, and anything Reflex (§M8: a hook fact, not a poller field).
|
||||
> *(2026-11-11: still true of `FlNvSample`, the 1 Hz telemetry layer's struct. The memory figures and the other
|
||||
> three utilisation domains are read since ABI 3 — below — into structs of their own, for Advanced metrics only.)*
|
||||
>
|
||||
> **ABI 2 (2026-09-25, beta.8): the driver profile, read-only.** The owner asked whether the NVIDIA App overrides a
|
||||
> game's DLSS (frame generation, ray reconstruction, the model preset). The NVIDIA App writes those overrides into the
|
||||
@@ -224,39 +222,6 @@ Still resolve **entry points defensively at runtime**: `nvapi64.dll` may be abse
|
||||
> ctest `fl_nvapi_bridge` (argument refusals, DEGRADED before init, the global profile of the test's own executable on
|
||||
> a GPU machine) and `NvapiBridgeMirrorTests` (`FlNvDriverProfileSize`, ABI 2).
|
||||
>
|
||||
> **ABI 3 (2026-11-11, owner decision D101): what "Advanced metrics" reads.** Five reads, each a struct with its
|
||||
> size first and a `present` mask, and each call behind it a query: `FlNvReadFacts` (what is true of the card whatever
|
||||
> is running — its type, bus, PCI ids, VBIOS version, architecture, core counts, the base and boost clocks, the
|
||||
> sensor's range, `NvAPI_GPU_GetMemoryInfoEx`'s four sizes, the frame-buffer sizes, the driver's package and base
|
||||
> branch, NVAPI's interface version, the chipset), `FlNvReadLive` (the same memory call's free figure with evictions
|
||||
> and promotions, the frame-buffer, video and bus utilisation, the video clock, the P-state, the board and
|
||||
> power-supply temperatures where the card has them, the throttle word, the encoder's session count and averages),
|
||||
> `FlNvReadDisplays` (per connected display: HDR formats and luminances, variable-refresh support, the adaptive-sync
|
||||
> flags), `FlNvSessionDisplay` (the display a GDI device name names: its variable-refresh state and the colour space
|
||||
> the driver reports for one process) and `FlNvProfileSettings` (every setting of the global profile, or only what a
|
||||
> game's own profile sets — a game no profile names is answered `GLOBAL` with nothing listed, never with the PC's
|
||||
> settings). No struct of ABI 2 changed size; `FL_NV_FIELD_VRAM` stays clear.
|
||||
>
|
||||
> **No identifier has an entry point** (D104): not `NvAPI_GPU_GetBoardInfo`, `NvAPI_GPU_GetUUID`, an EDID read, or
|
||||
> `NvAPI_GPU_GetEncoderSessionsInfo`, which lists WHICH programs encode. A display is passed on by its place in the
|
||||
> driver's list; NVAPI's display id is a handle of this boot and is neither stored nor shown.
|
||||
>
|
||||
> **Read-only is now a gate** (D108): `tools/nvapi-readonly-check.ps1` holds every `NvAPI_*` call of the bridge's
|
||||
> source to `tools/nvapi-allowed-calls.txt` in both directions — forty-four names — and refuses a name that sets,
|
||||
> saves, restores, registers or controls something, or that returns an identifier, **even when the list names it**.
|
||||
> Managed: `INvapiAdvancedBridge` (a port of its own beside `INvapiBridge`; `NativeNvapiBridge` implements both, and a
|
||||
> DLL that predates ABI 3 answers `Unavailable` rather than throwing) and `NvapiAdvancedReader`, which turns the five
|
||||
> structs into the catalog's facts and readings — every `nvapi.` entry whose reach is `Agent`, and no other, held by
|
||||
> `NvapiAdvancedReaderTests` in both directions. **Nothing composes the reader yet**: no Agent code calls it.
|
||||
>
|
||||
> **Measured on the dev box the day it was written** (RTX 5080, a driver of base branch `R620`, ctest `fl_nvapi_bridge`'s
|
||||
> AVAILABLE branch — `20_OPEN_QUESTIONS` §M12): all twenty facts answer (`present = 0xFFFFF`: discrete, desktop, PCI
|
||||
> Express, 84 ray-tracing and 336 tensor cores, base 2295 / boost 2670 MHz, 16,303 MiB dedicated, a DCH Game Ready
|
||||
> driver); eight of the ten live groups answer (`0x33F`) — **the board and power-supply temperatures do not exist on
|
||||
> this card**, as the memory temperature does not, and read N/A; the one display answers all four groups; the global
|
||||
> profile lists 24 settings. One thing the header had wrong: it misspells `NV_ENCODER_STATISTICS_VER` as
|
||||
> `NNV_ENCODER_STATISTICS_VER`, so the bridge names `NV_ENCODER_STATISTICS_VER1`.
|
||||
>
|
||||
> **The ctest could not fail on a GPU machine until the same day.** `fl_nvapi_bridge` was registered with
|
||||
> `PASS_REGULAR_EXPRESSION` alone, which makes ctest ignore the exit code: the AVAILABLE branch's reference-counting
|
||||
> check (two references, two releases, then a read expected to work) failed on every machine with an NVIDIA GPU while
|
||||
@@ -269,7 +234,7 @@ Still resolve **entry points defensively at runtime**: `nvapi64.dll` may be abse
|
||||
| Temperatures | `NvAPI_GPU_GetThermalSettings` (+ extended thermal query for hotspot/memory where available). **Bridge (2026-09-10):** the public enumeration only — core is the `GPU` target; memory is the `MEMORY` target when the driver lists one, and on the RTX 5080 it does not (bit clear → `null`); hotspot is not read |
|
||||
| Utilisation | `NvAPI_GPU_GetDynamicPstatesInfoEx` (GPU / FB / VID / BUS domains). **Bridge (2026-09-10):** the GPU domain only, as `loadPct` |
|
||||
| Clocks | `NvAPI_GPU_GetAllClockFrequencies` — **bridge (2026-09-10):** current graphics and memory clocks |
|
||||
| Memory | `NvAPI_GPU_GetMemoryInfoEx` — **not `NvAPI_GPU_GetMemoryInfo`**, which this table named until 2026-08-05. The vendored headers mark it `__nvapi_deprecated_function` ("deprecated in release 520"), so under `/W4 /WX` a call to it fails the native build. **Neither is called (2026-09-10):** ~~the vendored `nvapi.h` (`cd6918f6`) does not declare `GetMemoryInfoEx` at all — the deprecation message names a function the same header set does not ship~~ — so the bridge's `vram` field is **reserved**, its bit is never set, and VRAM stays L1's PDH adapter counter. ~~Taking a newer header set is the way to change that, not a call to the deprecated one~~ **Corrected 2026-11-11: the vendored set does declare it** — `nvapi_lite_common.h:600`, which `nvapi.h` includes, with `NV_GPU_MEMORY_INFO_EX_V1` above it and its id in `nvapi_interface.h`; the search that found nothing looked in `nvapi.h` alone. It was not called because of that sentence, from 2026-09-10 until now. The bridge calls it from ABI 3 for the advanced memory rows (§Advanced metrics); `FlNvSample.vram` stays reserved, so which layer fills the base `vram_adapter` series does not change |
|
||||
| Memory | `NvAPI_GPU_GetMemoryInfoEx` — **not `NvAPI_GPU_GetMemoryInfo`**, which this table named until 2026-08-05. The vendored headers mark it `__nvapi_deprecated_function` ("deprecated in release 520"), so under `/W4 /WX` a call to it fails the native build. **Neither is called (2026-09-10):** the vendored `nvapi.h` (`cd6918f6`) does not declare `GetMemoryInfoEx` at all — the deprecation message names a function the same header set does not ship — so the bridge's `vram` field is **reserved**, its bit is never set, and VRAM stays L1's PDH adapter counter. Taking a newer header set is the way to change that, not a call to the deprecated one |
|
||||
| **Throttle reasons** | `NvAPI_GPU_GetPerfDecreaseInfo` — not available from L1 or L2. **Bridge (2026-09-10):** the raw reason mask, and 0 is a measurement (no reason), not a clear bit |
|
||||
| Driver version | `NvAPI_SYS_GetDriverAndBranchVersion` — **bridge (2026-09-10):** `FlNvDriverVersion`, surfaced as `616.64 (r616_41)` |
|
||||
| **NGX per-process state** | `NvAPI_NGX_GetNGXOverrideState` (R570+) — the driver's feedback word per DLSS feature for a PID, read OUT OF PROCESS by `fl-probe-nvapi --ngx-state` and, since 2026-09-06, by the capture host beside each module snapshot — **in-process through the bridge since 2026-09-10** (`NvapiNgxStateProbe`; the spawn is retired and the words, the merge and the printed block are unchanged). Measured: the SR word's `CREATED \| EVALUATE` is set without an NVIDIA-app override; the FG word follows DLSS-G once created (`CREATED \| EVALUATE` at ×4, corrected the same day — the first reading was blind because it was early), the multiplier bits stay clear; `scalingRatio` is 0 even under an override. Identity only, SR and FG (`03_METRICS` §Upscaling) — and, since beta.24 (D63), the mode an NVIDIA App override set where the word says it applied; its `performanceMode` is in NGX's own numbering (Silent Hill 2, 2026-10-13: the App's Ultra Performance, profile value 5, reported as 3). *(Beta.27: never read after the game has gone — that reading, the last, had cleared `CREATED \| EVALUATE` on every stored session — and the two bits stand once a reading carried them: `03_METRICS` §The driver-reported rung.)* |
|
||||
@@ -528,612 +493,3 @@ alone could never catch.
|
||||
> (`NvapiTelemetrySource` over `FrameLedger.NvapiBridge.dll`, §L3). §M5 in particular (do LHM GPU
|
||||
> sensors work unelevated, without PawnIO?) decided whether the default unelevated
|
||||
> Agent has temperatures at all — **it does, on NVIDIA; row R1 above.**
|
||||
|
||||
## Advanced metrics (owner decisions D101–D108, 2026-11-11)
|
||||
|
||||
The owner asked for a setting, *"Thông số nâng cao"* (Advanced metrics), with a navigation item of its own, that shows
|
||||
as much as the Streamline and NVAPI headers and PawnIO make available — numbers, tables, charts — **with each value
|
||||
assigned to what it belongs to: one game session, or the PC**. Asked while planning, the owner chose: everything
|
||||
that can be reached inside a game as well, in stages, the route refused on 2026-08-09 re-examined; stored in full with
|
||||
the session; off by default, and off means nothing more is read; and the page never asks for administrator rights
|
||||
itself. This section is the design those answers gave, the decisions taken with it, and the inventory.
|
||||
|
||||
**Nothing here is built by the pull request that wrote it** except the catalog
|
||||
(`FrameLedger.Application.Advanced.AdvancedMetricCatalog`) and this section. Each later pull request of the train
|
||||
states here what it built.
|
||||
|
||||
### The decisions
|
||||
|
||||
- **D101 — the option.** `telemetry.advanced`, off by default, read by the Agent at each session's start. **Off means
|
||||
not read**: no additional call to NVAPI or LibreHardwareMonitor, nothing more stored, and the navigation item is
|
||||
hidden. A session recorded while it was off shows N/A for everything here — it is not filled in afterwards.
|
||||
- **D102 — where it is stored.** In two tables of their own (schema 0023), not in new columns of `sessions`: every
|
||||
read of a `sessions` row, the JSON export and the bug bundle carry the whole row, and a driver profile does not
|
||||
belong in a bug bundle. `machine_profiles` holds the facts of the PC, one row per distinct set, and a session points
|
||||
to the row that was true when it ran — the trend's hardware-change markers and `hardware_snapshots` are untouched.
|
||||
`session_advanced` holds one session's facts, its series' statistics and their directory. The series themselves go
|
||||
to `sensor_blobs` under names that start with `adv.`, **with NaN for a tick that has no reading**: the fixed series
|
||||
store −1 there and their readers drop every negative value, which would silently eat a −12 V rail.
|
||||
- **D103 — LibreHardwareMonitor's other groups.** CPU, memory and motherboard (its sensor chip and embedded
|
||||
controller) are opened **only when the Agent already runs as administrator and PawnIO is installed** — the existing
|
||||
admin mode (D34); the page says what is missing and links to that setting. **Refused**: the power-supply and
|
||||
fan-controller groups, which make the library search every USB HID device. **Deferred**: the battery group — and
|
||||
**storage**. The plan had storage in, temperature only and internal drives only, with one outcome written down
|
||||
before any run: *if the group cannot be opened without touching removable drives, it stays closed*. It cannot: the
|
||||
library's `StorageGroup` (0.9.6, read 2026-11-11) lists every drive through DiskInfoToolkit's `ReloadStorages` with
|
||||
no filter by bus, and subscribes to drives being plugged in afterwards. So `lhm.storage.*` is `Deferred`, a drive's
|
||||
temperature reads N/A, and `LhmGroups` — the only way this code can name a group to open — has no member for it
|
||||
(`20_OPEN_QUESTIONS` §M13). This amends §L2's "nothing else, ever" from the pull request that opened the three.
|
||||
- **D104 — identifiers are never read.** The card's board serial number and unique id, a display's EDID, and the list
|
||||
of programs that are encoding. They are named in the inventory so the page can say so; a test holds that no stored
|
||||
JSON has their keys. This is the only part of "everything" left out on purpose.
|
||||
- **D105 — the navigation item** is the last of the pane's items; Ctrl+1 to Ctrl+5 keep their pages and **Ctrl+6**
|
||||
opens it only while the option is on.
|
||||
- **D106 — the `.partial` file skips what it does not know.** A chunk of an unknown type whose checksum is right is
|
||||
passed over; until now it ended the read, so a build one release older lost everything after the first new chunk.
|
||||
- **D107 — with no game running**, the Agent reads sensors only while the page is open, through one reader shared
|
||||
with the sessions, closed again some seconds after the last use. A PC idling with FrameLedger in the tray reads
|
||||
nothing (NFR-2's "~0% idle").
|
||||
- **D108 — read-only, by a gate.** §Runtime policy's "never call a setter" becomes a build check: every `NvAPI_*`
|
||||
call in the bridge's source is compared with a committed list, in both directions, and a name that changes
|
||||
something or returns an identifier is refused whatever the list says. An entry point that both reads and writes by
|
||||
a command argument — the colour and info-frame controls — is refused like a writer: the check reads names, not
|
||||
arguments, and nothing on the list is one. *(Built with ABI 3: `tools/nvapi-readonly-check.ps1`.)*
|
||||
|
||||
### The reader (built 2026-11-11; composed by the Agent since the switch)
|
||||
|
||||
`Application.Advanced.IAdvancedHardware` is the port: `Acquire()` keeps the reader running until the handle is let
|
||||
go, `Latest` is the last tick without waiting, `ReadSessionFacts` reads one session's facts on the caller's thread.
|
||||
`Infrastructure.Telemetry.AdvancedHardwareHub` implements it — **one reader for the whole Agent, on a thread of its
|
||||
own (`fl-advanced`), running only while somebody holds it** and for a linger after, so that two sessions in a row,
|
||||
or a session ending as the page opens, do not close and reopen the sensors (D107). The Agent records several
|
||||
sessions at once, each with a poller; a reader per session would open the motherboard's sensor chip as many times.
|
||||
|
||||
What runs on that thread is `AdvancedHardwareReader`: NVAPI through `NvapiAdvancedReader`, and
|
||||
`LhmAdvancedReader` over a `Computer` of its own, opened with `LhmAdvancedReader.GroupsFor(elevated, pawnIo)` —
|
||||
`LhmGroups`, an enum that has a member for the four groups this project may open and for no other. Each sensor is a
|
||||
member of a catalog family by the device at the top of its tree and its type (`LhmAdvancedMap.FamilyOf`); its series
|
||||
is named from the library's own identifier (`/lpc/nct6798d/0/voltage/3` → `adv.lhm.board.voltage.lpc_nct6798d_0_3`)
|
||||
and labelled with the hardware's words. A sensor with no family is not read.
|
||||
|
||||
- **A source that is not there is a state** (`AdvancedSources`): no NVIDIA driver, not administrator, PawnIO
|
||||
missing. Never an exception, and never a value in its place.
|
||||
- **A device that throws twice is left alone** until the reader opens again; the others go on. The library's own
|
||||
traversal stops at the first exception, so each top-level device is refreshed in a guard of its own.
|
||||
- **NVAPI answering with no field, twice running, after it had answered**: released and initialised again, once
|
||||
(`20_OPEN_QUESTIONS` §M12).
|
||||
- **The cadence was set by a measurement, before anything composed the reader.** `FrameLedger.CaptureHost
|
||||
probe-advanced` runs this reader on the caller's own rights and prints what it read and what it cost. On the dev
|
||||
box (RTX 5080, unelevated, 2026-11-11): 35 facts and 58 readings a tick — 17 from NVAPI, 41 from the card's sensors;
|
||||
**one NVAPI live read costs 0.4 ms of processor time; one refresh of LibreHardwareMonitor's graphics-card group
|
||||
costs 14 ms (62 ms elapsed)**. Once a second that refresh alone is 1.4% of one core, above NFR-2's 1% for the
|
||||
whole Agent. So NVAPI is read every tick and **the sensor library every fifth** (0.28%), and on the ticks between a
|
||||
sensor has no reading — its last value is not repeated. The same refresh is what the L2 telemetry layer does once
|
||||
a second in every session: that cost is not this feature's, and is `20_OPEN_QUESTIONS` §M16 — measured in a real
|
||||
Agent on 2026-11-11 (1.93 % of one core off, 2.04 % on) and answered by amending NFR-2 to 2.5 % (D117).
|
||||
|
||||
### From the reader to the ledger (built 2026-11-11; fed since the switch)
|
||||
|
||||
- **The poller attaches, it does not read.** `TelemetryPoller` takes an optional `IAdvancedHardware`, holds it from
|
||||
`Start` to `Dispose`, and at each poll takes `Latest` — a read of one reference. A snapshot it has not taken yet
|
||||
rides on that poll's `TelemetrySample.Advanced`; one it has already taken is not attached again, because a
|
||||
reading is of one tick. Null — the option off — composes nothing, and a sample is what it always was.
|
||||
- **The `.partial`** carries those readings in a chunk of their own after the sensor chunk (type 9) and the
|
||||
session's context in another (type 10), so a recovered session keeps both; with the option off neither is
|
||||
written. An unknown chunk type is now skipped rather than the end of the file (D106). `06_DATA_MODEL` §The
|
||||
`.partial` file.
|
||||
- **The finalizer** (`AdvancedSessionBuilder`, both tiers) turns the samples' readings into one series each,
|
||||
aligned to `t_ms` with NaN for a tick with none, and builds the session's row: facts, sources, statistics,
|
||||
directory. Schema 0023 and the rule for NaN are `06_DATA_MODEL` §Blob encoding and §Migrations.
|
||||
|
||||
### The switch (built 2026-11-11, Advanced PR-5)
|
||||
|
||||
`telemetry.advanced` (`SettingsRegistry.TelemetryAdvanced`, Boolean, default `0`, read by the Agent) becomes
|
||||
`RecorderOptions.AdvancedMetrics` through `SettingsRecorderPolicy`, at each session's start like the other recording
|
||||
settings; exactly `1` is on. From there:
|
||||
|
||||
- **The process has one sensor library** *(2026-11-12)*. One *reader* was never the whole of it: a session's L2
|
||||
source and its CPU-temperature reader each open a LibreHardwareMonitor `Computer` of their own beside the
|
||||
Advanced reader's, and the library keeps part of its state — the driver it reads the processor through, its bus
|
||||
mutexes — per process. `Computer.Close()` lets go of that part whoever else is still reading. The first sessions
|
||||
recorded as administrator with PawnIO showed it (`20_OPEN_QUESTIONS` §M13): a processor device that faulted out
|
||||
some seconds after each session's sources closed, and one session whose reader could not open at all. Every
|
||||
`Computer` is now opened and closed through `Infrastructure.Telemetry.LhmLibrary` (`LhmComputerAdapter` is its
|
||||
user): opens and closes never run at once, and a `Computer` closed while another is in use is **parked** — left
|
||||
open, read by nobody, handed to the next user of the same groups — until the last user lets go, when all are
|
||||
closed. The reads are not serialised: the readers keep their own threads, so a sensor that hangs in one still
|
||||
holds up neither the other nor the pipe.
|
||||
- **The Agent has one reader** — `AgentServices` registers `AdvancedHardwareHub` as `IAdvancedHardware`, a tick a
|
||||
second and a linger of ten — and nothing starts it but a holder. `SessionRecorder` holds it for a session's length
|
||||
**only when the option is on**, and `AgentRecording` gives the session's `TelemetryPoller` the reader on the same
|
||||
condition. Off: not held, not asked, no chunk 9 or 10, no row (`SessionRecorderTests.WithAdvancedMetricsOff…`).
|
||||
- **A session's facts are read once, off the capture loop.** Fifteen seconds after the game's process is known — by
|
||||
then it has a window — or at the session's end if that comes first, `IAdvancedHardware.ReadSessionFacts` runs on a
|
||||
pool thread: asking the driver for a profile takes some hundred milliseconds. The finalize waits at most five
|
||||
seconds for a read still in flight and stores the session without its facts rather than hold it. A read that
|
||||
throws costs the facts, never the session.
|
||||
- **Which display is the game's** comes from Windows, not from the game: `WindowGeometryProbe.MonitorDeviceOf` — the
|
||||
monitor the process's largest visible window is on, as its GDI device name — which the reader hands to
|
||||
`FlNvSessionDisplay`. No window, or a display another adapter drives: the session's display facts are absent.
|
||||
- **The context reaches the crash file as it changes** (chunk 10), from `IAdvancedHardware.Latest` — a read of one
|
||||
reference on the capture loop's task — so a recovered session keeps its machine facts, its sources and its
|
||||
directory of series.
|
||||
- **A session recorded with the option on always stores a row**, if only one that says every source is `Unknown`:
|
||||
no row means "the option was off when this was recorded", which the page (PR-7) shows as such.
|
||||
|
||||
What elevation adds changed with this: an Agent running as administrator with PawnIO reads the processor, memory
|
||||
and motherboard groups in a session with the option on. The texts that state what the admin mode adds say so —
|
||||
Disclaimer 2.15 §5 and §5A (the owner's answer of 2026-11-11), the admin mode's disclosure (`agent-admin-dialog/2`),
|
||||
Settings, the first run, the guide and `LIMITATIONS.md` — and Privacy Policy 2.15 names what is read and stored.
|
||||
|
||||
### The page's feed (built 2026-11-11, Advanced PR-6; shown by the page since PR-7)
|
||||
|
||||
With no game running the Agent reads sensors **only while the page is open** (D107), and nothing tells the Agent
|
||||
that a page opened or closed:
|
||||
|
||||
- **`GetAdvancedMachine`** (`07_IPC` §Messages) is answered by `Application.Ipc.AdvancedMachineResponder` from
|
||||
`IAdvancedHardware.Latest` alone. The first request acquires the shared reader and each one renews a five-second
|
||||
lease; a lease after the last request the hold is let go, and the reader closes its sources ten seconds later
|
||||
unless a session holds it. A page that closes, an App that exits and a pipe that drops all look the same: no
|
||||
request. With the option off the answer is `Error AdvancedOff`, and nothing is held.
|
||||
- **`App.Services.AdvancedMachineFeed`** asks once a second while a page holds `Watch()`, and keeps the facts (asked
|
||||
for once, by their hash), **the last value of every series with the tick it was read on** — a sensor read every
|
||||
fifth tick is "1400, as of then", never shown as new — five minutes of each series for the live charts, and the
|
||||
sources' states. It stores nothing. Its states are the page's own words for why there is nothing to show: waiting
|
||||
for the first read, off, no agent (a viewer never has one), an older agent.
|
||||
|
||||
### The page (built 2026-11-11, Advanced PR-7)
|
||||
|
||||
`08_UI` §Advanced is the screen. What this document's model becomes there:
|
||||
|
||||
- **A machine fact** is under *This PC* ▸ *About this PC* while the Agent answers, and under *Session* as it was
|
||||
when that session was recorded (`machine_profiles`, one row per distinct set).
|
||||
- **A session fact** is under *Session* only.
|
||||
- **A series** is a row of *Right now* and a line of *Over time* while live — never stored then — and a row of the
|
||||
session's statistics and a line of its chart once a session stored it.
|
||||
- **An entry that is not read** is on *Sources* with its reason, in the same words as §Left out, by name.
|
||||
|
||||
`ISessionRepository.ListAdvancedAsync` lists the sessions that have a row; `SessionSeriesLoader.LoadAdvancedAsync`
|
||||
decodes their series against `t_ms`, leaving a NaN tick out and keeping a negative reading.
|
||||
|
||||
### What belongs to what
|
||||
|
||||
| Scope | What it is | Stored | Shown |
|
||||
|---|---|---|---|
|
||||
| `MachineFact` | true of the PC whatever is running: the card's firmware and architecture, the driver's package, what a display can do | `machine_profiles`, once per distinct set; a session points to its row | This PC |
|
||||
| `SessionFact` | true of one session: the game's display state, the settings the driver's profile for that game sets | `session_advanced.facts_json` | Session |
|
||||
| `Series`, during a session | a sensor of the PC sampled while the game ran | `sensor_blobs` (`adv.*`), statistics in `session_advanced.stats_json` | Session |
|
||||
| `Series`, with no session | the same sensor, read because the page is open | nowhere | This PC |
|
||||
|
||||
A third tab, **Sources**, lists every row of the inventory with its state on this PC — read, or N/A with the reason:
|
||||
not an NVIDIA card, the Agent is not administrator, PawnIO is not installed, the option was off when the session was
|
||||
recorded, the hook is not built, the route is refused, a vendor's licence. A PC without an NVIDIA card shows N/A for
|
||||
every `nvapi.` row; nothing is estimated in its place (FR-4.9).
|
||||
|
||||
### The trains
|
||||
|
||||
| Train | Release | What | Its gate |
|
||||
|---|---|---|---|
|
||||
| A | 0.1.0-beta.39 | read by the Agent only — NVAPI and LibreHardwareMonitor — storage, the page. **Nothing changes in code loaded into a game** | this section |
|
||||
| B | 0.1.0-beta.40, ~~.41, .42~~ ~~.42, .43~~ .42, .43, .44 *(three releases since D113, 2026-11-11; one was planned. Renumbered 2026-11-12, D118: 0.1.0-beta.41 is a fix release for the sensor library, not part of the train. **Four since D122, the same day**: the second step is beta.42 — no new patch site — and beta.43, the two new hooks; the third step is beta.44)* | inside the game: more fields of the Streamline and FidelityFX calls already hooked, and new hooks on functions `sl.interposer.dll` **exports** (`17_HOOK_ENGINE` §Hook inventory's ⏳ rows); shared-memory layout 5 — §Train B below | a plan of its own; overhead measured; each release after the first waits for the owner's run of the one before |
|
||||
| B, a fourth step | 0.1.0-beta.45 *(D130, 2026-11-12)* | six more of Streamline's core calls — is a feature supported, is it loaded, the game switching it, its resources allocated and freed, Streamline shut down | hooks installed only where asked for, as in the second and third steps; `slInit` is not among them (D129) |
|
||||
| C | ~~0.1.0-beta.41~~ ~~0.1.0-beta.43~~ ~~0.1.0-beta.44~~ ~~0.1.0-beta.45~~ after 0.1.0-beta.45 *(D118, D122, D130)* | Reflex latency per frame | a spike — written beside beta.45, a document only — then the owner's go or no |
|
||||
| D | ~~0.1.0-beta.42~~ ~~0.1.0-beta.44~~ ~~0.1.0-beta.45~~ ~~0.1.0-beta.46~~ after train C *(D118, D122, D130)* | the Streamline feature state behind `slGetFeatureFunction` — DLSS frame generation's, DLSS's, Reflex's | a spike, then the owner's go or no |
|
||||
|
||||
Rules 4 and 5, the hook inventory, the measured overhead and the anti-cheat guard bind B, C and D exactly as they bind
|
||||
every hook. `sl::Constants` is read without its camera position, axes and matrices: where the camera is, is where the
|
||||
player is (rule 4). NGX stays closed by its licence (`17_HOOK_ENGINE` §NGX).
|
||||
|
||||
**Closed 2026-11-14 (owner decision D154): train D is not built, and the refusal stands.** The ten entries it would have read — what a game sets and asks through Streamline's feature functions — have reach `RefusedRoute`: seeing those calls takes handing the game a function of FrameLedger's in place of Streamline's, and a game that fetched its functions before the attach would never call it. What follows is the plan as it stood. **Train D re-examines a refusal; it does not lift it.** `handoff/history/p0-queue-1-6.md` refused, on five grounds,
|
||||
hooking `slGetFeatureFunction` and patching the function it returns. The route to try is a different one:
|
||||
`slGetFeatureFunction` is itself an export (`vendor-exports.json`), so its hook is an ordinary inventory row, and
|
||||
what it hands back could be a wrapper for a fixed list of names instead of a patch at an address learned at run time
|
||||
— which would answer grounds 1 to 4, and turn ground 5 into "measured only when injected at launch". Two things it
|
||||
raises are the owner's: replacing the pointer the game receives is a **write**, which rule 4 forbids as written; and
|
||||
a wrapper must outlive the Overlay's own unhook. If the spike cannot answer all of it, the route stays refused and
|
||||
the page says so.
|
||||
|
||||
### Train B (planned 2026-11-11, owner decisions D110–D116)
|
||||
|
||||
What the catalog marks `HookedCall` and `NewHook`. Planned the day train A shipped, the owner's decisions asked while
|
||||
planning, the design reviewed against the code before it was approved.
|
||||
|
||||
- **D111 — off means off inside the game too.** The Agent writes one word of the control block
|
||||
(`advancedRequested`, ~~0 or 1~~ 0 or that session's request, unconditionally at attach) when the session records Advanced metrics. The Overlay
|
||||
reads a new field, and installs a new hook, only while it is set; with the option off it hooks and reads exactly
|
||||
what 0.1.0-beta.39's does.
|
||||
**Built 2026-11-12 (0.1.0-beta.40, PR-3), with one thing the plan did not have:** "on" is not a 1 but a
|
||||
*request* — a value no session of that ring used before. A game outlives a session, and the Overlay's summaries
|
||||
with it; a second session of a game that kept running would have read the first one's field of view and counts.
|
||||
The watchdog starts its summaries afresh at a request it has not seen and names the request in every publication;
|
||||
the Agent reads only what answers its own (`07_IPC` §Region 5). The detours consult one process-local flag, the
|
||||
watchdog is the region's one writer, and `fl_guard` shows the off half on a target that sends everything: every
|
||||
byte of the region zero until asked, untouched after an "off", a count that starts again at the next request.
|
||||
**The Agent and the App, 2026-11-12 (PR-4).** A session that records Advanced metrics says so through
|
||||
`ICaptureObserver.WantsInGameAdvanced`; `CaptureSession` writes the word either way as the ring is attached, before
|
||||
its first guard result, and from then on carries each publication of region 5 on `CaptureProgress.InGameAdvanced`
|
||||
— one instance a publication, the same one on the ten ticks between two. `Application.Capture.InGameAdvancedSampler`
|
||||
turns a publication into what a session stores: the session facts of the thirteen `Game` entries below (nineteen since 0.1.0-beta.43, twenty-one since 0.1.0-beta.44, twenty-three since 0.1.0-beta.45), in the
|
||||
vendor's own words (a preset is its letter, a member its name), and two series —
|
||||
`adv.ffx.upscale.frame_time_delta`, the mean of one second's dispatches, and `adv.ffx.memory_usage`, a point for
|
||||
each second the game asked. The facts are one list until a field they are made of moves, so the recorder's context
|
||||
is rewritten when a range widens and not once a second; the readings ride the newest telemetry sample of the tick.
|
||||
**No schema change**: the facts go into `session_advanced.facts_json` beside the driver's, the series into
|
||||
`sensor_blobs` under their `adv.` names, the `.partial`'s chunks 9 and 10 carry both. `AdvancedSources.InGame`
|
||||
(optional; absent in every row 0.1.0-beta.39 wrote) says what became of those entries in the session: `Reading`,
|
||||
`NothingSeen` — measured inside the game, and the game made none of the calls where they can be seen — or
|
||||
`NotHooked`. The page says it in the session's sources line and, on Sources, that such an entry is read inside a
|
||||
game FrameLedger measures when the game makes the call. The aliasable part of FSR's memory is published and not
|
||||
shown: the catalog has one memory entry.
|
||||
**The second step, 2026-11-12 (0.1.0-beta.43, PR-4).** Six more entries have reach `Game`: `sl.constants.jitter`,
|
||||
`.motion_vectors`, `.depth`, `.projection`, `.resets` and `ffx.framegen.config`, from the two calls hooked only
|
||||
for Advanced metrics (`17_HOOK_ENGINE` §Hook inventory, `slSetConstants` and `ffxConfigure`). The sampler makes
|
||||
them from members region 5 already had (layout 5 as it was; schema 23 as it was): a switch is `on`, `off` or
|
||||
`on_and_off` from the two words of what was seen, the flags are AMD's own names, the rectangle is the last one
|
||||
the game gave and is left out where the capture side could not state it, the field of view is a range (D114).
|
||||
**A field of view over π is said as given (owner decision D128, 0.1.0-beta.44).** Both vendors' headers say
|
||||
radians; Cyberpunk 2077 gives Streamline 51–90, and the row read `51.0055 – 90 rad (2922.4° – 5156.6°)`. Such a
|
||||
value is now the number alone, with a second row (`cameraFOV unit`, token `not_radians`) that says what it is
|
||||
not; it is never converted, which would store this project's guess at the unit as the game's word. A
|
||||
frame-generation configure that set no flag has a `flags` row of `none`, as an upscale does.
|
||||
**A count is not part of what makes the facts new** — `sl.constants.resets` grows all session, and a context
|
||||
rewritten on each would be one a second — so `InGameAdvancedSampler.Conclude` brings it up to the last
|
||||
publication once, when the session ends. `AdvancedSources.StreamlineConstants` and `.FsrFrameGeneration`
|
||||
(`AdvancedInGameCall`; null in every row written before, and in a session not measured inside the game) say for
|
||||
each call which of three things happened: `Read`; `NeverCalled` — the capture side published the hook's family
|
||||
(`FlHookFamily.SlConstants`, `.FfxConfigure` in the writer state's mask) and no publication carried the group; or
|
||||
`NotHooked` — the family was never published, which is a game that did not load the library, a Streamline 1.x
|
||||
interposer, or a patch that was refused. The page says it in one more sentence of the session's sources line.
|
||||
**The third step, 2026-11-12 (0.1.0-beta.44).** Two more entries have reach `Game`: `sl.feature.versions` and
|
||||
`sl.feature.requirements`, from what Streamline answers `slGetFeatureVersion` and `slGetFeatureRequirements`
|
||||
(`17_HOOK_ENGINE` §Hook inventory). The sampler makes them from region 5's twelve feature slots (layout 5 and
|
||||
schema 23 as they were): rows named `<feature> · <member>`, the feature by NVIDIA's constant (`kFeatureDLSS_G`;
|
||||
`feature 4242` for an id this build has no name for), a version as `major.minor.build`, the requirement flags by
|
||||
their enumerators. A version of all zeros is the vendor's "none" and has no row — a feature with no NGX model, a
|
||||
requirement nobody stated — except `versionSL`; a count of 0 is a count. One bit of the mask covers both
|
||||
questions, so which was answered is told by the slots (`InGameAdvancedSampler.FeatureCall`), and
|
||||
`AdvancedSources.StreamlineFeatureVersion` and `.StreamlineFeatureRequirements` say for each: `Read`;
|
||||
`NeverCalled` — hooked, and the game did not ask after that, ~~**the usual case, because a game asks while it
|
||||
starts**~~ *(not the usual case: measured 2026-11-12, six of six Streamline sessions on five games read both, bar
|
||||
Cyberpunk 2077's version question)*, and the page words it as "did not ask again"; or `NotHooked`. The slots are not emptied by a new request, so a second
|
||||
session of a game that kept running stores what the first one read. `sl.init.preferences` stays unread (D112).
|
||||
**The fourth step, 2026-11-12 (0.1.0-beta.45).** Two more entries have reach `Game`, from six calls
|
||||
(`17_HOOK_ENGINE` §Hook inventory): `sl.feature.support` — `<feature> · slIsFeatureSupported`, the `sl::Result`
|
||||
by NVIDIA's enumerator (`eOk`, `eErrorFeatureNotSupported`; `result 40` for a number past the forty this build
|
||||
names, `result 255` for a code a byte could not carry), and `<feature> · slIsFeatureLoaded`, `on` or `off` — and
|
||||
`sl.feature.lifecycle` — `<feature> · slSetFeatureLoaded` (`on`, `off`, `on_and_off`: what the game asked for
|
||||
during the session, not the state it left), `· slAllocateResources` and `· slFreeResources` (a count; `≥ 15`
|
||||
where the four bits stopped), and a row `slShutdown` with the number of shutdowns. All of it is word 1 of the
|
||||
twelve feature slots and one word that was reserved (layout 5 and schema 23 as they were). A feature with nothing
|
||||
to say has no row and a fact with no row is not stored. `AdvancedSources` has one member a call
|
||||
(`StreamlineFeatureSupported`, `…Loaded`, `StreamlineSetFeatureLoaded`, `StreamlineAllocateResources`,
|
||||
`StreamlineFreeResources`, `StreamlineShutdown`), `Read` / `NeverCalled` / `NotHooked` as before and null in a
|
||||
row written before; the page says the six in one sentence. The switching and the counts are a session's — the
|
||||
capture side clears them at a new request — so, unlike the answers, a second session does not inherit them.
|
||||
`sl.init.preferences` now has reach `BeforeAttach` (D129): not a later release, never.
|
||||
**Measured 2026-11-13** (six Streamline sessions on five games; `HANDOFF` item 43): `slIsFeatureSupported` was
|
||||
read in every one — refusals among the answers, `eErrorFeatureMissing` for ImGUI, NIS and DeepDVC —
|
||||
`slIsFeatureLoaded` in three games, `slSetFeatureLoaded` in two (every feature off and on), `slFreeResources`
|
||||
and `slShutdown` once in one game each, and `slAllocateResources` in none.
|
||||
- **D113 — three releases, because a new patch site cannot be proven in CI.** A crash in a game under the user-mode
|
||||
anti-cheat exception's trial ends that exception for good (D38), and every release already means restarting the
|
||||
game. **beta.40**: more fields of calls *already* hooked — `sl::DLSSOptions` where the game chains it into
|
||||
`slEvaluateFeature`, the FSR upscale dispatch, the FSR memory query — shared-memory layout 5, the Agent and the
|
||||
page; **no new patch site**. **~~beta.41~~ beta.42**: `slSetConstants` and `ffxConfigure`. **~~beta.42~~
|
||||
beta.43**: `slGetFeatureVersion` and `slGetFeatureRequirements` — the owner's words: a release of their own, still
|
||||
hooked. Each starts when the owner says the one before passed its owner-only item.
|
||||
- **D122 — the second step is two releases** (owner decision 2026-11-12, after the owner's sessions on beta.40
|
||||
and beta.41 and a review of the draft against the code). **0.1.0-beta.42 adds no patch site**: the session's
|
||||
upscaler label (D120, `03_METRICS` §Upscaling), a patch registry that refuses what it cannot register, a native
|
||||
log that survives the game's exit and says which descriptor types each ffx module saw — because Cyberpunk 2077,
|
||||
set to FSR upscaling, was named "unknown" and nothing in the field could say why (D121) — and FSR's infinite depth
|
||||
plane (D119). **0.1.0-beta.43 is `slSetConstants` and `ffxConfigure`**, begun only when that log was read. The
|
||||
third step (`slGetFeatureVersion`, `slGetFeatureRequirements`) is beta.44, train C beta.45, train D beta.46.
|
||||
- **D118 — 0.1.0-beta.41 is a fix release, and the train's numbers move by one** (owner decision 2026-11-12). The
|
||||
owner's first evening with beta.40 showed the sensor library being closed under its other users (the paragraph on
|
||||
`LhmLibrary` below; `20_OPEN_QUESTIONS` §M13); told that the fix would take the number D113 had given the train's
|
||||
second release, the owner chose to release it at once. So: second release beta.42, third beta.43, train C
|
||||
beta.44, train D beta.45. Text written before that day says beta.41 and beta.42 for the second and third — in
|
||||
the released changelogs and the moved HANDOFF sections, which are not edited, and in the comments of `fl_shm.h`
|
||||
and `ShmLayout.cs`, which the release that fills each member rewrites (they were left so that the code loaded
|
||||
into a game stayed 0.1.0-beta.40's, line for line, in a release that fixes something else).
|
||||
- **D112 — `slInit` is not hooked in train B.** A game calls it before FrameLedger attaches, so its preferences
|
||||
would almost never be seen. If it is ever hooked: `applicationId`, `projectId` and the paths are never read.
|
||||
- **D129 — `slInit` is not hooked at all** (owner decision 2026-11-12, asked to reopen D112 and shown what was
|
||||
found). No mode of the shipped product is in the game in time: *Play ▸ Start directly* does not create the game
|
||||
suspended — it waits for the presentation runtime, runs the guard, then injects; nothing is ever patched on a
|
||||
game's thread, so a hook lands some hundred milliseconds after its module appears (`17_HOOK_ENGINE`, the loader
|
||||
lock); and a hook that exists only for Advanced metrics waits for the Agent's request, which comes after the
|
||||
attach. A hook on it would be a patch that reads nothing. `sl.init.preferences` says so in the catalog. Most of
|
||||
what it would have told is read another way: which features are loaded (`slIsFeatureLoaded`), and whether a
|
||||
newer plugin than the game's own is in use (the versions of 0.1.0-beta.44).
|
||||
- **D130 — six more core calls in one release, 0.1.0-beta.45**: `slIsFeatureSupported`, `slIsFeatureLoaded`,
|
||||
`slSetFeatureLoaded`, `slAllocateResources`, `slFreeResources`, `slShutdown`. Trains C and D come after it; train
|
||||
C's spike is written beside it, as a document.
|
||||
- **D131 — the adapter a game asks `slIsFeatureSupported` about is never read**: `sl::AdapterInfo` holds its LUID
|
||||
or a Vulkan physical device. The feature's id and the result are all that is kept, and a build check refuses the
|
||||
names of the struct's members in the code loaded into a game.
|
||||
- **D114 — the field of view is a session's range**, lowest to highest, never a series: a series would say when the
|
||||
player aimed.
|
||||
- **D115 — a tail member is read only where it is proven to be there** (`17_HOOK_ENGINE` §Which struct version
|
||||
carries which field): the table from the upstream tags, not the one header in the tree.
|
||||
- **D116 — "never the camera" is a build check**, as "never a setter" is (D108): `tools/overlay-fields-check.ps1` —
|
||||
every read of a vendor struct in one header, each allowed member named and used, the camera's names refused
|
||||
anywhere in the Overlay and the Vulkan layer, no copy of `sl::Constants` by value. *(Built 2026-11-12:
|
||||
twenty-eight members on `tools/overlay-allowed-fields.txt`; `12_BUILD` gate 14f. Fifty-six since 0.1.0-beta.44,
|
||||
with the two answers about a feature.)*
|
||||
- **What will read N/A, and says why.** Many titles set their DLSS options through `slDLSSSetOptions`, which is not
|
||||
an export (train D), so `sl.dlss.*` is filled only for a title that passes its options with the evaluate call.
|
||||
`slGetFeatureVersion` and `slGetFeatureRequirements` are calls a game makes while starting.
|
||||
- **Privacy Policy 2.19** at beta.45 (approved with that release's plan): 2.18 named two of Streamline's answers
|
||||
about a feature; whether it is supported and loaded, the game switching it, allocating and freeing its resources
|
||||
and shutting Streamline down are in neither list, so they are named — with two more things never read: what
|
||||
identifies the graphics card a game hands over with its question, and the content of a graphics resource.
|
||||
- **Privacy Policy 2.18** at beta.44 (approved with that release's plan): 2.17 named two further calls and what
|
||||
they give; Streamline's answers about a feature are in neither list, so they are named, with what of the answer
|
||||
is never read — the lists it points to.
|
||||
- **Privacy Policy 2.21 and Disclaimer 2.17** at beta.48 (wording approved with the plan of 2026-11-14, D145):
|
||||
the Privacy Policy names the two further averages a session stores of the driver's report and that the
|
||||
frame-generation multiplier is every value the session saw; the Disclaimer changes only with the accuracy
|
||||
statement it carries, which now says two real games were read, that the stages overlap, and that the graphics
|
||||
card's stage includes its waiting. No new call: the paragraph on the call the component makes is as it was.
|
||||
- **Privacy Policy 2.20 and Disclaimer 2.16** at beta.47, train C (wording approved with the plan of
|
||||
2026-11-13): the first thing read inside a game that is **not an argument of a call the game made**. The Privacy
|
||||
Policy names what is stored — how long each stage of a frame took, as the driver reports it, and the driver's
|
||||
low-latency state; never a time of day, never an input's moment. The Disclaimer drops "API arguments and nothing
|
||||
else" for what is true, and §2 gains the paragraph on the one call the component makes itself: where, how often,
|
||||
on which thread, what it never calls, what ends it, and that a call which never returned could not be stopped.
|
||||
- **Privacy Policy 2.17** at beta.43 (approved with that release's plan): 2.16 listed DLSS's and FSR's upscaling
|
||||
parameters by name, and Streamline's per-frame constants and the frame-generation configuration are in neither
|
||||
list, so they are named — and §4 says the two calls are intercepted only once a session with the option on has
|
||||
started in the game.
|
||||
- **Privacy Policy 2.16** at beta.40, once for the three releases: with Advanced metrics on, for a game FrameLedger
|
||||
injects into, the parameters the game gives its upscaler and frame generation through the intercepted calls are
|
||||
*stored* — sizes, presets, exposure, sharpening, the jitter's, the depth's and the field of view's ranges, flags,
|
||||
versions — and never the camera's position, axes or matrices.
|
||||
|
||||
### Left out, by name
|
||||
|
||||
Present in the vendored `nvapi.h`, readable from the Agent, and not in the inventory — each is either not a
|
||||
measurement of how a game runs or exists on professional cards only: ECC status and errors, NVLINK, illumination
|
||||
(the card's lighting zones), licensable features, virtualization and GSP information, Quadro status, VR-ready data,
|
||||
the IRQ and bus slot numbers, logical GPUs and SLI state, HDCP support, scan-out configuration, the colour and
|
||||
info-frame controls. `NvAPI_DISP_GetTiming` calculates a timing from an input and reads nothing.
|
||||
`NV_GET_ADAPTIVE_SYNC_DATA`'s last-flip count and timestamp mean nothing sampled once a second.
|
||||
`NvAPI_GPU_ClientRegisterForUtilizationSampleUpdates` registers a callback, which is not a read.
|
||||
|
||||
### The inventory
|
||||
|
||||
One row per entry of `AdvancedMetricCatalog`, in its order; `AdvancedMetricCatalogTests` fails when this table and
|
||||
the catalog differ in either direction. **Reach** is where a value can be read from, or why it is not read: `Agent`
|
||||
(the Agent's own process), `AgentElevated` (the same, as administrator with PawnIO), `Game` (read inside a game
|
||||
FrameLedger measures, from the arguments of a call the Overlay hooks, while the session records Advanced metrics —
|
||||
since 0.1.0-beta.40), `HookedCall` (an argument of a call the Overlay already hooks, not read yet), `NewHook` (a hook
|
||||
that is not built — Train B; no entry carries it since 0.1.0-beta.45), `BeforeAttach` (a call the game makes once,
|
||||
before FrameLedger is inside it, so no hook could read it — D129), `Spike` (Trains C and D; no entry since D154), `Refused`, `Deferred`, `Identifier` (D104), `PlayerState`
|
||||
(rule 4), `Licence`, `NotInHeaders`. ~~Only the first two are read by a build of Train A.~~ The first three are read
|
||||
(`AdvancedMetric.IsRead`).
|
||||
|
||||
**NVAPI, the graphics card: facts**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `nvapi.gpu.type` | Integrated or discrete graphics | MachineFact | Nvapi | Agent | Text |
|
||||
| `nvapi.gpu.system_type` | Laptop or desktop, as the driver sees the PC | MachineFact | Nvapi | Agent | Text |
|
||||
| `nvapi.gpu.external` | The card is an external one | MachineFact | Nvapi | Agent | Flag |
|
||||
| `nvapi.gpu.bus_type` | The bus the card sits on | MachineFact | Nvapi | Agent | Text |
|
||||
| `nvapi.gpu.pci_ids` | PCI device, subsystem and revision ids - the model, not the unit | MachineFact | Nvapi | Agent | Text |
|
||||
| `nvapi.gpu.vbios_version` | Video BIOS version | MachineFact | Nvapi | Agent | Text |
|
||||
| `nvapi.gpu.architecture` | Chip architecture, implementation and revision | MachineFact | Nvapi | Agent | Text |
|
||||
| `nvapi.gpu.core_count` | Graphics cores | MachineFact | Nvapi | Agent | Count |
|
||||
| `nvapi.gpu.rt_cores` | Ray-tracing cores | MachineFact | Nvapi | Agent | Count |
|
||||
| `nvapi.gpu.tensor_cores` | Tensor cores | MachineFact | Nvapi | Agent | Count |
|
||||
| `nvapi.gpu.ram_bus_width` | Width of the card's memory bus | MachineFact | Nvapi | Agent | Bits |
|
||||
| `nvapi.gpu.clock_base_core` | Base core clock | MachineFact | Nvapi | Agent | Megahertz |
|
||||
| `nvapi.gpu.clock_base_memory` | Base memory clock | MachineFact | Nvapi | Agent | Megahertz |
|
||||
| `nvapi.gpu.clock_boost_core` | Boost core clock | MachineFact | Nvapi | Agent | Megahertz |
|
||||
| `nvapi.gpu.clock_boost_memory` | Boost memory clock | MachineFact | Nvapi | Agent | Megahertz |
|
||||
| `nvapi.gpu.temp_default_max` | The core sensor's default maximum temperature | MachineFact | Nvapi | Agent | Celsius |
|
||||
|
||||
**NVAPI, the card's memory**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `nvapi.vram.dedicated` | Dedicated video memory on the card | MachineFact | Nvapi | Agent | Mebibytes |
|
||||
| `nvapi.vram.dedicated_available` | Dedicated video memory available for surfaces | MachineFact | Nvapi | Agent | Mebibytes |
|
||||
| `nvapi.vram.system` | System memory the driver reserved at load | MachineFact | Nvapi | Agent | Mebibytes |
|
||||
| `nvapi.vram.shared` | Shared system memory the driver may commit | MachineFact | Nvapi | Agent | Mebibytes |
|
||||
| `nvapi.vram.framebuffer_physical` | Physical frame buffer size | MachineFact | Nvapi | Agent | Mebibytes |
|
||||
| `nvapi.vram.framebuffer_virtual` | Virtual frame buffer size | MachineFact | Nvapi | Agent | Mebibytes |
|
||||
| `nvapi.vram.available` | Dedicated video memory available now, all programs | Series | Nvapi | Agent | Mebibytes |
|
||||
| `nvapi.vram.in_use` | Dedicated video memory in use now, all programs: available for surfaces less available now | Series | Nvapi | Agent | Mebibytes |
|
||||
| `nvapi.vram.evictions_size` | Memory released by evictions since the driver loaded | Series | Nvapi | Agent | Mebibytes |
|
||||
| `nvapi.vram.eviction_count` | Evictions from dedicated video memory since the driver loaded | Series | Nvapi | Agent | Count |
|
||||
| `nvapi.vram.promotions_size` | Memory moved in by promotions since the driver loaded | Series | Nvapi | Agent | Mebibytes |
|
||||
| `nvapi.vram.promotion_count` | Promotions into dedicated video memory since the driver loaded | Series | Nvapi | Agent | Count |
|
||||
|
||||
**NVAPI, the card over time**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `nvapi.load.framebuffer` | Frame-buffer (memory controller) utilisation | Series | Nvapi | Agent | Percent |
|
||||
| `nvapi.load.video` | Video-engine utilisation | Series | Nvapi | Agent | Percent |
|
||||
| `nvapi.load.bus` | Bus-interface utilisation | Series | Nvapi | Agent | Percent |
|
||||
| `nvapi.clock.video` | Video clock | Series | Nvapi | Agent | Megahertz |
|
||||
| `nvapi.pstate` | The card's current performance state (P-state id) | Series | Nvapi | Agent | Count |
|
||||
| `nvapi.temp.board` | Board ambient temperature, where the card has the sensor | Series | Nvapi | Agent | Celsius |
|
||||
| `nvapi.temp.power_supply` | The card's power-supply temperature, where it has the sensor | Series | Nvapi | Agent | Celsius |
|
||||
| `nvapi.limit.ac_battery` | Held back by a switch to battery on the tick: 100 or 0 | Series | Nvapi | Agent | Percent |
|
||||
| `nvapi.limit.api` | Held back at a program's request on the tick: 100 or 0 | Series | Nvapi | Agent | Percent |
|
||||
| `nvapi.limit.insufficient_power` | Held back by a missing power connector on the tick: 100 or 0 | Series | Nvapi | Agent | Percent |
|
||||
| `nvapi.encoder.sessions` | Active hardware-encoder sessions, all programs | Series | Nvapi | Agent | Count |
|
||||
| `nvapi.encoder.fps` | Average encoding rate of the active sessions | Series | Nvapi | Agent | FramesPerSecond |
|
||||
| `nvapi.encoder.latency` | Average encoding latency | Series | Nvapi | Agent | Microseconds |
|
||||
|
||||
**NVAPI, the driver**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `nvapi.driver.package` | Game Ready, Studio or an RTX enterprise branch | MachineFact | Nvapi | Agent | Text |
|
||||
| `nvapi.driver.dch` | The driver is a DCH package | MachineFact | Nvapi | Agent | Flag |
|
||||
| `nvapi.driver.base_branch` | The driver's base branch | MachineFact | Nvapi | Agent | Text |
|
||||
| `nvapi.driver.interface_version` | NVAPI's own interface version | MachineFact | Nvapi | Agent | Text |
|
||||
| `nvapi.driver.chipset` | Chipset vendor and name, as the driver reports them | MachineFact | Nvapi | Agent | Text |
|
||||
| `nvapi.driver.global_profile` | Every setting of the driver's global profile, read-only | MachineFact | Nvapi | Agent | Table |
|
||||
| `nvapi.session.driver_profile` | The settings the driver's profile for this game sets itself, read-only | SessionFact | Nvapi | Agent | Table |
|
||||
|
||||
**NVAPI, displays**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `nvapi.display.hdr_formats` | HDR formats a display accepts: HDR10, HDR10+, HDR10+ Gaming, Dolby Vision, EDR | MachineFact, one per device | Nvapi | Agent | Text |
|
||||
| `nvapi.display.luminance_max` | A display's maximum luminance for HDR content | MachineFact, one per device | Nvapi | Agent | Nits |
|
||||
| `nvapi.display.luminance_min` | Its minimum luminance | MachineFact, one per device | Nvapi | Agent | Nits |
|
||||
| `nvapi.display.luminance_max_frame_average` | Its maximum frame-average light level | MachineFact, one per device | Nvapi | Agent | Nits |
|
||||
| `nvapi.display.vrr_support` | Variable refresh: supported, G-SYNC module or adaptive sync, ULMB, usable at the current mode | MachineFact, one per device | Nvapi | Agent | Text |
|
||||
| `nvapi.display.adaptive_sync_off` | Adaptive sync is switched off on the display | MachineFact, one per device | Nvapi | Agent | Flag |
|
||||
| `nvapi.display.max_frame_interval` | The longest frame interval adaptive sync is set to hold | MachineFact, one per device | Nvapi | Agent | Microseconds |
|
||||
| `nvapi.session.vrr_enabled` | Variable refresh was active on the game's display | SessionFact | Nvapi | Agent | Flag |
|
||||
| `nvapi.session.vrr_requested` | Variable refresh was requested for it | SessionFact | Nvapi | Agent | Flag |
|
||||
| `nvapi.session.vrr_possible` | Variable refresh was possible on it | SessionFact | Nvapi | Agent | Flag |
|
||||
| `nvapi.session.vrr_display_mode` | The display itself was in variable-refresh mode | SessionFact | Nvapi | Agent | Flag |
|
||||
| `nvapi.session.source_colorspace` | The colour space the game presented in, as the driver reports it for the process | SessionFact | Nvapi | Agent | Text |
|
||||
|
||||
**LibreHardwareMonitor, the graphics card (every vendor, unelevated)**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `lhm.gpu.temperature` | Every temperature sensor of the card | Series, one per device | Lhm | Agent | Celsius |
|
||||
| `lhm.gpu.load` | Every load of the card: its engines, its bus, its memory controller | Series, one per device | Lhm | Agent | Percent |
|
||||
| `lhm.gpu.memory` | The card's memory counters: total, free, used, Direct3D dedicated and shared | Series, one per device | Lhm | Agent | Mebibytes |
|
||||
| `lhm.gpu.clock` | Every clock of the card | Series, one per device | Lhm | Agent | Megahertz |
|
||||
| `lhm.gpu.power` | Every power reading of the card | Series, one per device | Lhm | Agent | Watts |
|
||||
| `lhm.gpu.fan` | Every fan of the card | Series, one per device | Lhm | Agent | Rpm |
|
||||
| `lhm.gpu.fan_control` | Each fan's duty | Series, one per device | Lhm | Agent | Percent |
|
||||
| `lhm.gpu.voltage` | Every voltage of the card | Series, one per device | Lhm | Agent | Volts |
|
||||
| `lhm.gpu.current` | Every current of the card | Series, one per device | Lhm | Agent | Amperes |
|
||||
| `lhm.gpu.throughput` | PCI Express traffic to and from the card | Series, one per device | Lhm | Agent | BytesPerSecond |
|
||||
|
||||
**LibreHardwareMonitor through PawnIO (the Agent as administrator, D103)**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `lhm.cpu.temperature` | Processor temperatures: the package and each core | Series, one per device | Lhm | AgentElevated | Celsius |
|
||||
| `lhm.cpu.load` | Processor load: the total and each core | Series, one per device | Lhm | AgentElevated | Percent |
|
||||
| `lhm.cpu.clock` | Each core's clock, and the bus clock | Series, one per device | Lhm | AgentElevated | Megahertz |
|
||||
| `lhm.cpu.power` | Processor power: the package, the cores | Series, one per device | Lhm | AgentElevated | Watts |
|
||||
| `lhm.cpu.voltage` | Processor voltages | Series, one per device | Lhm | AgentElevated | Volts |
|
||||
| `lhm.board.model` | The motherboard's maker and model | MachineFact | Lhm | AgentElevated | Text |
|
||||
| `lhm.board.sensor_chip` | The board's sensor chip | MachineFact | Lhm | AgentElevated | Text |
|
||||
| `lhm.board.temperature` | The board's temperature sensors | Series, one per device | Lhm | AgentElevated | Celsius |
|
||||
| `lhm.board.fan` | Each fan header's speed | Series, one per device | Lhm | AgentElevated | Rpm |
|
||||
| `lhm.board.fan_control` | Each fan header's duty | Series, one per device | Lhm | AgentElevated | Percent |
|
||||
| `lhm.board.voltage` | The board's voltage rails | Series, one per device | Lhm | AgentElevated | Volts |
|
||||
| `lhm.memory.modules` | The memory modules: size, speed, maker's part name - never a serial number | MachineFact | Lhm | AgentElevated | Table |
|
||||
| `lhm.memory.load` | Memory in use: physical and virtual | Series, one per device | Lhm | AgentElevated | Percent |
|
||||
| `lhm.memory.temperature` | Each memory module's temperature, where it has a sensor | Series, one per device | Lhm | AgentElevated | Celsius |
|
||||
|
||||
**What the Agent could reach and does not**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `lhm.psu` | Power-supply sensors: reading them makes the library search every USB device | MachineFact | Lhm | Refused | Table |
|
||||
| `lhm.controller` | Fan-controller sensors: the same search of USB devices | MachineFact | Lhm | Refused | Table |
|
||||
| `lhm.battery` | Battery sensors | MachineFact | Lhm | Deferred | Table |
|
||||
| `lhm.storage.models` | The drives' model names: the library cannot list drives without touching removable ones | MachineFact | Lhm | Deferred | Table |
|
||||
| `lhm.storage.temperature` | Each drive's temperature: the same, so the storage group is not opened | Series, one per device | Lhm | Deferred | Celsius |
|
||||
| `nvapi.gpu.board_serial` | The card's board serial number | MachineFact | Nvapi | Identifier | Text |
|
||||
| `nvapi.gpu.uuid` | The card's unique id | MachineFact | Nvapi | Identifier | Text |
|
||||
| `nvapi.display.edid` | A display's EDID block, which carries its serial number | MachineFact, one per device | Nvapi | Identifier | Text |
|
||||
| `nvapi.encoder.session_processes` | Which programs are encoding | Series | Nvapi | Identifier | Table |
|
||||
| `nvapi.gpu.power` | Card power through NVAPI (LibreHardwareMonitor reads it) | Series | Nvapi | NotInHeaders | Watts |
|
||||
| `nvapi.gpu.fan_duty` | Fan duty through NVAPI (LibreHardwareMonitor reads it) | Series | Nvapi | NotInHeaders | Percent |
|
||||
| `nvapi.gpu.voltage` | Card voltage through NVAPI (LibreHardwareMonitor reads it) | Series | Nvapi | NotInHeaders | Volts |
|
||||
| `nvapi.gpu.ram_type` | The card's memory type | MachineFact | Nvapi | NotInHeaders | Text |
|
||||
|
||||
**Inside the game: calls the Overlay already hooks**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `sl.dlss.output_size` | The output size the game gave DLSS | SessionFact | Streamline | Game | Text |
|
||||
| `sl.dlss.presets` | The DLSS model preset per quality mode | SessionFact | Streamline | Game | Table |
|
||||
| `sl.dlss.hdr_input` | The game told DLSS its colour buffers are HDR | SessionFact | Streamline | Game | Flag |
|
||||
| `sl.dlss.auto_exposure` | DLSS auto-exposure | SessionFact | Streamline | Game | Flag |
|
||||
| `sl.dlss.alpha_upscaling` | DLSS upscales the alpha channel | SessionFact | Streamline | Game | Flag |
|
||||
| `sl.dlss.exposure` | Pre-exposure and exposure scale given to DLSS | SessionFact | Streamline | Game | Table |
|
||||
| `ffx.upscale.sharpening` | FSR sharpening: on or off, and its strength | SessionFact | FidelityFx | Game | Table |
|
||||
| `ffx.upscale.jitter` | The largest jitter offset the game gave FSR | SessionFact | FidelityFx | Game | Table |
|
||||
| `ffx.upscale.exposure` | Pre-exposure given to FSR | SessionFact | FidelityFx | Game | Text |
|
||||
| `ffx.upscale.depth` | Near and far planes and the range of the field of view given to FSR | SessionFact | FidelityFx | Game | Table |
|
||||
| `ffx.upscale.flags` | The flags of the game's FSR dispatch | SessionFact | FidelityFx | Game | Text |
|
||||
| `ffx.upscale.frame_time_delta` | The frame time the game reported to FSR | Series | FidelityFx | Game | Milliseconds |
|
||||
| `ffx.memory_usage` | FSR's own video memory, when the game asks it | Series | FidelityFx | Game | Mebibytes |
|
||||
|
||||
**Inside the game: hooks that are not built**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `sl.constants.jitter` | The jitter offsets the game gave Streamline | SessionFact | Streamline | Game | Table |
|
||||
| `sl.constants.motion_vectors` | Motion-vector scale, and whether they are 3D, dilated, jittered | SessionFact | Streamline | Game | Table |
|
||||
| `sl.constants.depth` | Near and far planes, and whether depth is inverted | SessionFact | Streamline | Game | Table |
|
||||
| `sl.constants.projection` | Field of view, aspect ratio, orthographic or not | SessionFact | Streamline | Game | Table |
|
||||
| `sl.constants.resets` | How often the game reset the upscaler's history | SessionFact | Streamline | Game | Count |
|
||||
| `ffx.framegen.config` | The game's FSR frame-generation configuration | SessionFact | FidelityFx | Game | Table |
|
||||
| `sl.feature.versions` | Each Streamline feature's version and its NGX model version | SessionFact | Streamline | Game | Table |
|
||||
| `sl.feature.requirements` | What each Streamline feature requires: operating system, driver, buffers | SessionFact | Streamline | Game | Table |
|
||||
| `sl.feature.support` | Whether Streamline says each feature is supported, and loaded | SessionFact | Streamline | Game | Table |
|
||||
| `sl.feature.lifecycle` | Each feature switched on or off, its resources allocated and freed, Streamline shut down | SessionFact | Streamline | Game | Table |
|
||||
| `sl.init.preferences` | The preferences the game started Streamline with | SessionFact | Streamline | BeforeAttach | Text |
|
||||
| `sl.constants.camera` | Camera position, axes and matrices | SessionFact | Streamline | PlayerState | Text |
|
||||
|
||||
**Inside the game: what the graphics driver reports, asked for by the part inside the game itself** *(train C,
|
||||
owner decisions D132, D136, D138 — `17_HOOK_ENGINE` §Calls the Overlay makes into a driver; since 0.1.0-beta.47)*
|
||||
|
||||
Not an argument of a hooked call: the Overlay calls the driver's two read-only latency getters about once a second,
|
||||
only while a session records Advanced metrics, only for a Direct3D 12 game that had already loaded the driver's
|
||||
`nvapi64.dll`. The report becomes seven series — `adv.nvapi.reflex.frame_report.` and `simulation`,
|
||||
`render_submit`, `present`, `driver`, `os_queue`, `gpu_render`, `total` — each point the mean, in microseconds, of
|
||||
the frames one read summed; the sleep status becomes one table of the driver's five switches as seen over the
|
||||
session and, since 0.1.0-beta.48 (D144), every frame-generation multiplier it gave (it kept the last one, and a
|
||||
session that ended in a menu read 1). **Since 0.1.0-beta.48 (D142) two more series, an entry of their own** —
|
||||
`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). **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.
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `nvapi.reflex.mode` | Reflex: low-latency mode, boost, the frame-rate limit | SessionFact | Nvapi | RefusedRoute | Text |
|
||||
| `nvapi.reflex.sleep_status` | What the driver's low-latency state is | SessionFact | Nvapi | GameDriver | Table |
|
||||
| `nvapi.reflex.frame_report` | Latency per frame: simulation, render submit, present, driver, OS queue, GPU render | Series, one per device | Nvapi | GameDriver | Microseconds |
|
||||
| `nvapi.reflex.gpu_times` | The graphics card's time per frame, as the driver works it out: active render, frame to frame | Series, one per device | Nvapi | GameDriver | Microseconds |
|
||||
|
||||
**Inside the game: Streamline's feature functions — not read (D154, 2026-11-14)**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `sl.dlss.optimal_settings` | The render size and sharpness DLSS recommends | SessionFact | Streamline | RefusedRoute | Text |
|
||||
| `sl.dlss.vram_estimate` | DLSS's own estimate of its video memory | Series | Streamline | RefusedRoute | Mebibytes |
|
||||
| `sl.dlssg.options` | DLSS frame generation: mode, frames to generate | SessionFact | Streamline | RefusedRoute | Text |
|
||||
| `sl.dlssg.state` | DLSS frame generation: status, the most frames it can generate | SessionFact | Streamline | RefusedRoute | Text |
|
||||
| `sl.dlssg.frames_presented` | Frames DLSS frame generation presented, by its own count | Series | Streamline | RefusedRoute | Count |
|
||||
| `sl.dlssg.vram_estimate` | DLSS frame generation's estimate of its video memory | Series | Streamline | RefusedRoute | Mebibytes |
|
||||
| `sl.dlssd.options` | Ray reconstruction's options | SessionFact | Streamline | RefusedRoute | Text |
|
||||
| `sl.nis.options` | NVIDIA Image Scaling's options | SessionFact | Streamline | RefusedRoute | Text |
|
||||
| `sl.deepdvc.options` | RTX Dynamic Vibrance's options | SessionFact | Streamline | RefusedRoute | Text |
|
||||
| `sl.reflex.state` | Reflex through Streamline: availability and its frame reports | SessionFact | Streamline | RefusedRoute | Table |
|
||||
| `sl.pcl.markers` | PC-latency markers the game sets | Series | Streamline | RefusedRoute | Count |
|
||||
|
||||
**Closed by a licence**
|
||||
|
||||
| Id | What it is | Scope | Source | Reach | Unit |
|
||||
|---|---|---|---|---|---|
|
||||
| `ngx.parameters` | NGX parameters: the quality value, the DLSS hints | SessionFact | Ngx | Licence | Table |
|
||||
| `xess.options` | XeSS's options | SessionFact | Xess | Licence | Table |
|
||||
| `sl.nvperf` | Streamline's performance counters (NSight Perf SDK licence) | Series | Streamline | Licence | Table |
|
||||
@@ -60,30 +60,10 @@ Implemented in `FrameLedger.Injector` and reached from managed code through a th
|
||||
> at once), waits `kScanRetryPauseMs` (250 ms), takes a **fresh** scan set and scans it whole. A member still unreadable
|
||||
> then refuses `kProcessUnreadable`, as before; one that has gone is not in the new set; a target that has gone leaves
|
||||
> no set, which refuses `kProcessTreeUnavailable`. **`ERROR_ACCESS_DENIED` — a protected process — is never retried**,
|
||||
> and no other answer of any source is *(one more since D123, below)*. The sentence above stands: every failure still means REFUSE; what changed is
|
||||
> and no other answer of any source is. The sentence above stands: every failure still means REFUSE; what changed is
|
||||
> how many times "still loading" is asked before it counts as one. ctest `fl_guard` `[D48]` holds both directions,
|
||||
> against fakes and against the real source (a process created suspended, a pid with no process).
|
||||
>
|
||||
> **Amended 2026-11-12 (owner decision D123): a module list that changed while it was read is read again, at most
|
||||
> three times — never a pass.** The module check lists a process's modules and then asks each one's name. A game at
|
||||
> its launch loads and unloads modules for seconds, and a module that was in the list and could not be named a
|
||||
> moment later made the whole answer "incomplete": a refusal before injection, or — 0.5 s after it, at the first
|
||||
> supervision scan — a safety unhook with no frame recorded, the game then running on unrecorded. **Five such ends
|
||||
> in one PC's Agent logs in a week** (Phantom Blade Zero three times on 2026-11-05, Crown & Coin on 11-10,
|
||||
> Cyberpunk 2077 on 11-12), and twice in this repository's own gate. Asked with that, the owner chose: read it
|
||||
> again. Such a list is now `Collected::kUnsettled`; the pass finishes — **a blocklisted module among those that
|
||||
> were read still refuses at once** — waits `kScanRetryPauseMs`, takes a fresh scan set and reads it whole, up to
|
||||
> `kMaxUnsettledRereads` (3) times: four reads and 750 ms of pauses at most. A list still unsettled on the last
|
||||
> read refuses `kModuleScanFailed` ("a module list kept changing while it was read"). **What did not change:** a
|
||||
> list too long for the guard's buffer is still `kIncomplete` and refuses at once (a second read would be as
|
||||
> long); a protected process still refuses at once; D48's re-read is still one for the whole check; every read is
|
||||
> of the whole scan set, and the read that allows is one in which every member was read whole and none held a
|
||||
> finding. A failure to read is still never a pass — what changed is how many times a list that is moving is
|
||||
> asked before it counts as unreadable. The launch poll's presentation-runtime probe treats an unsettled list as
|
||||
> "ask again" rather than deciding on half of one. ctest `fl_guard` `[D123]`: against fakes, every direction
|
||||
> above; against the real source, a process that loads and frees a module in a loop — read some 3,600 times in
|
||||
> three seconds, about one read in four is unsettled and none is anything else.
|
||||
>
|
||||
> **Launch mode (2026-09-06, P1 item 2) does not weaken this.** `FlGuardedInjectWhenReady` polls
|
||||
> the same enumeration to learn *when* the launched target has mapped a presentation runtime, and a
|
||||
> failing enumeration there means "not yet" — the poll continues. That is not a pass: the poll
|
||||
@@ -1047,7 +1027,7 @@ injected or layered**.
|
||||
If `OpenProcess` with the needed rights fails (protected process, higher integrity), do **not** escalate creatively. Report "cannot attach" and offer Tier-2. Never attempt to acquire privileges beyond running the Agent elevated at the user's explicit request.
|
||||
|
||||
> **The explicit request exists since beta.10 (owner decision D34, 2026-09-27): the admin mode.** An option off by default,
|
||||
> turned on through a versioned disclosure (`Safety_AdminMode_*`, `agent-admin-dialog/2` *(`/1` until 2026-11-11, when Advanced metrics widened what the option adds — D101)*) that states what it adds, what it
|
||||
> turned on through a versioned disclosure (`Safety_AdminMode_*`, `agent-admin-dialog/1`) that states what it adds, what it
|
||||
> does not change, how Windows asks and the risk of a per-user install; then **Windows asks at every start of the Agent**
|
||||
> (`01_ARCHITECTURE` ADR-9). What it does NOT do, each held by code rather than by this paragraph:
|
||||
>
|
||||
@@ -1234,20 +1214,6 @@ outlives a rules change, a game update and *Change executable*; §What a finding
|
||||
hooked session's early abnormal end; the policy counted them, and two turned hooking off. It cannot tell either from
|
||||
the hang it exists for, so it stands as written; whether a witness — the same executable started again within
|
||||
seconds — may exempt a hand-off is the owner's decision, not taken. Users are told in `LIMITATIONS.md` §Play.
|
||||
- **The count starts again when the user switches hooking on (owner decision D126, 0.1.0-beta.44).** Until then
|
||||
`hook_crash_count` only ever grew: Lies of P had two such ends on 2026-10-19/20 (the hand-off above), its user
|
||||
switched hooking on again, and on 2026-11-12 one more early end — the game's own crash, by the owner, after a shader
|
||||
failed to compile — switched it off at once, under a reason that says *twice*. The consent grant, the only
|
||||
statement that turns hooking on, now sets the count to 0 (`SqliteGameConsentStore`). The policy still only
|
||||
disables, a block is still never cleared, and the user-mode exception's trial (D38) keeps its own record, which
|
||||
nothing sets back.
|
||||
- **A fault while the game is closing is not seen by a hooked session (owner decision D127: written down, not
|
||||
changed in 0.1.0-beta.44).** Hogwarts Legacy faults in the driver's `_nvngx.dll` at exit — six times in Windows'
|
||||
application log since 2026-11-06, hooked or not. The one unhooked session reads `crashed`; the five hooked ones
|
||||
read `normal` with exit code 0: the witness is looked for when the session is saved, which for a hooked session
|
||||
is before Windows has written the event. Looking again later would make every session of such a game `crashed`,
|
||||
and under a user-mode exception that ends the exception for good for a fault no hook caused — so it is a decision
|
||||
of its own, not a fix to slip in beside two new hooks.
|
||||
- **What reads as a crash changed in beta.14, in both directions** (`04_CAPTURE` §Crash & exit classification): a
|
||||
Windows report that is not a crash (a memory-leak or hang report) no longer makes one, and an engine's crash reporter
|
||||
started by a game that then left does — Unreal's crash ended with exit code 3 and read `normal`. Both feed this policy,
|
||||
|
||||
@@ -1549,16 +1549,6 @@ probe never showed a deadlock.
|
||||
> real-game leg — a title that pulls Streamline or D3D12 in lazily, hooked through the wake — which the
|
||||
> `loader detour:` report line will show as a non-zero wake count with the family present from the first
|
||||
> bucket.
|
||||
>
|
||||
> **0.1.0-beta.46 (owner decision D134): one suspension for a batch, and the rule is as it was.** The rows a
|
||||
> watchdog tick finds are enabled under one `MH_ApplyQueued` — one stop of the threads where there was one a row
|
||||
> (`17_HOOK_ENGINE` §Unhooking, Batches). Still only on the watchdog, never from the detour and never on a game's
|
||||
> thread; the gate around the queue is not held across a symbol lookup, so it is never held with the loader's lock
|
||||
> wanted. What a stop of the threads costs in a real game was read from the owner's logs of 2026-11-13: 57 to
|
||||
> 215 ms, thirteen times over for a Streamline title until this release. **On beta.46, the same evening** (five
|
||||
> games, eighteen batches): 81–262 ms a batch for sixteen of them, and two that took 0.61 s and 1.26 s while their
|
||||
> game was loading — one stop where there were three and thirteen, and still a second of every thread of Hogwarts
|
||||
> Legacy standing still. Not explained (`17_HOOK_ENGINE` §Unhooking, Batches).
|
||||
|
||||
### H11 ◐ · XeFG and FSR3-FG identity — **AMD built 2026-09-04 through the ffx-api leaves, complete 2026-09-06; Intel closed by licence; FSR 3.0 host route built 2026-09-05**
|
||||
|
||||
@@ -1870,11 +1860,6 @@ Moved verbatim, in this order.
|
||||
| M9 ✅ | **Closed 2026-08-02 by a decision.** The old file/module detection does not exist in this repository and the owner confirmed there is no copy elsewhere, so **"build a minimal static-hint detector as the measurement baseline" is now P0 item 3** (`15_ROADMAP`). It needs no guard and no injection. Until it exists, ADR-7's headline claim stays out of the README rather than being asserted unmeasured |
|
||||
| M10 ❓ | **§CPU — is the CPU temperature this build reads the right sensor, and does it read at all on the owner's machine?** `LhmCpuTemperatureReader` (2026-09-21) opens a CPU-only LibreHardwareMonitor `Computer` when the Agent is elevated AND `PawnIo.IsInstalled`, takes the package sensor (`CPU Package` / `Core (Tctl/Tdie)`) and falls back to the hottest core. It was written against LHM's sensor names and a fake `ILhmComputer`; **no elevated run with PawnIO has been taken.** | **The measurement is one session:** Agent elevated, PawnIO installed, a five-minute capture with HWiNFO or Ryzen Master open beside it. Pre-committed: `max_cpu_temp` within 3 °C of the reference's package peak → keep; a core sensor picked where a package sensor exists, or a reading tens of degrees off (a distance-to-TjMax sensor mistaken for a temperature) → fix `Pick` and re-run; nothing read at all → `cpu_temp` stays N/A and `legal/ACCURACY.md` says processor temperature is not measured. CPU **load** and memory are not in question: `TheRealCountersAnswerOnThisMachine` reads them on every gate run. |
|
||||
| M11 🅓 | **The game's VRAM budget and `budget_exceeded_pct` (FR-4.5's second half), 2026-10-03.** D43 reads the game's usage from outside (the `GPU Process Memory` counters); the budget the OS grants the process is what DXGI's `QueryVideoMemoryInfo` returns to the *calling* process (§M7), so only an in-process call — the Overlay's background thread, which today only checks for a stop — or `D3DKMTQueryStatistics`' `PROCESS_SEGMENT_GROUP` query (documented "Reserved for system use") could read it. **Deferred by decision:** neither is built; `vram_budget_exceeded_pct` stays NULL and the budget N/A, and the in-process route would change what the Disclaimer says the Overlay's thread does. Reopening it needs that decision, not a measurement. | — |
|
||||
| M12 ❓ | **Advanced metrics — which NVAPI rows answer on real hardware (D101, 2026-11-11).** `18_GPU_VENDOR_APIS` §The inventory lists sixty `nvapi.` rows whose reach is `Agent`. They are declared in the vendored headers; **none has been called on a GPU**, and CI has no driver, so it never takes that branch. Unknown per row: whether the RTX 5080 on the current driver answers or returns `NVAPI_NOT_SUPPORTED` (the memory-temperature target already does not exist on that card). | **The measurement is the bridge's probe on the owner's PC**, then the page itself (the release's owner-only item). Pre-committed: a call that does not answer → that row is N/A with NVAPI's own status as the reason, and nothing is put in its place; a call that hangs or faults twice → the row is off for the session (§Runtime policy); a value that contradicts the vendor's own tool → the row is withheld until it is explained. **Half answered the same day, by the bridge's own test on the dev box** (ctest `fl_nvapi_bridge`, AVAILABLE branch; RTX 5080): every fact answers (`present = 0xFFFFF`), eight of ten live groups answer (`0x33F` — no board and no power-supply temperature sensor on this card: N/A, by the first pre-committed outcome), the display answers its four groups, the global profile lists 24 settings; figures in `18_GPU_VENDOR_APIS` §L3. **Still open**: the same values on the page beside the vendor's own tool, and the session rows (`nvapi.session.*`), which need a game. **And one thing seen once and not explained**: in one test run of about a dozen that day, `FlNvReadLive` came back with no field at all although `FlNvReadFacts`, a moment earlier in the same process, had answered everything; nine further runs did not show it. A handle the driver invalidated is the usual cause of that shape, and nothing here re-enumerates after `FlNvInit`. Pre-committed for the reader that owns the thread: two readings in a row with no field → release and initialise the bridge again, once, and say so in the log; if that does not bring the fields back the layer is off for the session, as any layer that fails twice is. |
|
||||
| M13 ❓ | **Advanced metrics — LibreHardwareMonitor's CPU, memory, motherboard and storage groups, elevated, with PawnIO (D103, 2026-11-11).** Never opened by any build: §M10's elevated run has not been taken either, and this is a larger surface — a sensor chip on the LPC bus, the embedded controller, SPD over SMBus, SMART. Unknown: whether each group opens on the owner's board, what a refresh costs, whether opening the storage group touches removable drives (this PC once had a failing USB drive), and whether any group enables a privilege (`PrivilegeFootprintTests`). | **One elevated run with the probe verb, before the option exists.** Pre-committed: the storage group cannot be opened without touching removable drives → `lhm.storage.*` stays N/A in beta.39 and its reach reads `Deferred`; a node that throws twice → skipped for the session; the Agent above 1% of one core or 150 MB with the option on (NFR-2) → the slow groups are read less often or dropped before the release; a privilege enabled by a group → that group is not opened, and the owner is asked. **Two of the four answered 2026-11-11, before the option exists.** (1) **Storage: not opened, by the first outcome.** LibreHardwareMonitor 0.9.6's `StorageGroup` lists every drive through DiskInfoToolkit's `ReloadStorages` with no filter by bus and follows drives plugged in later — it cannot be opened without touching removable drives. `lhm.storage.*` reads `Deferred`, and `LhmGroups` has no member for it. (2) **Cost, unelevated, measured with `probe-advanced`** on the dev box: one refresh of the graphics-card group alone is 14 ms of processor time (62 ms elapsed) — 1.4% of one core at one a second, above NFR-2 — and one NVAPI read 0.4 ms. By the third outcome the sensor library is read every fifth tick (0.28%). **Still open, and the owner's**: the same probe as administrator with PawnIO — whether the processor, memory and motherboard groups open on this board, what they cost, and `PrivilegeFootprintTests`' new case on a token that holds the privileges (CI's does; the dev box's unelevated run passes by construction). **The first run was taken on 2026-11-12, by the owner, in ordinary use** (0.1.0-beta.40, the Agent as administrator with PawnIO, an i7-14700KF on a board with an IT8689E chip, an RTX 5080), and read here from a copy of the ledger and the Agent's log, not from a probe. **The groups open and read**: nine of ten sessions stored 119 processor series (a clock and a load per thread, temperatures, powers, voltages), 14 memory series and 21 motherboard series (six fans, six temperatures, nine voltages) beside the card's 41 — 195 from the sensor library in all. **No value was compared with another tool**; that is still the owner's. **Two faults, one cause** (`Infrastructure.Telemetry.LhmLibrary`): the Agent held up to three `Computer`s at once, and the library keeps the driver it reads the processor through and its bus mutexes per process — closing one `Computer` let go of them under the others. After seven sessions the Advanced reader's processor device threw `NullReferenceException` twice and was left alone (the page lost the processor until the reader reopened); once a session's start met another instance's close, the reader's `Open` threw `ObjectDisposedException`, and that session stored 17 series instead of 212. **Fixed 2026-11-12**: opens and closes are serialised and a `Computer` is parked, not closed, while another is in use. The cause is read from the log's timing and was not reproduced — it needs this elevation — so **whether the faults are gone is the owner's next sessions to show**: no `advanced: a device is left alone` and no `did not open` in the Agent's log. **First evidence, 2026-11-12, 0.1.0-beta.41, the same PC:** seven sessions between 06:38 and 07:01 with no `advanced:` line at all, each with the option on storing 212 or 213 series; on beta.40 that morning the processor device faulted out after each of six sessions (04:34–05:07) — thirteen of sixteen over the night. The reader failing to open was seen once in sixteen, so this is not yet enough to call that one gone. Still open: any value beside another tool. |
|
||||
| M16 ✅ | **The L2 telemetry layer's cost — the first number, and it is above NFR-2 (found 2026-11-11, measuring something else).** `LhmTelemetrySource` refreshes LibreHardwareMonitor's graphics-card group once a second in every recorded session. `probe-advanced` measured that refresh, through the same library and the same group, at **14 ms of processor time** on the dev box (RTX 5080, 41 mapped sensors, about twenty of them the Direct3D engine nodes the library enumerates per card) — 1.4% of one core, where NFR-2 allows the whole Agent 1% during capture and `14_TESTING` §Hook overhead's Agent figure has never been measured. This is a measurement of the call, not yet of a session: L2's own poller was not instrumented. | **Measure L2 in a session** (the Agent's processor time over a ten-minute capture, telemetry at 1000 ms and at 2000 ms). Pre-committed: at or under 1% → this row closes with the number; above → the owner chooses between a slower default for `telemetry.interval_ms`, reading the sensors the layer keeps from NVAPI on NVIDIA cards (L3 already has most, at 0.4 ms), or amending NFR-2 to what is measured. Not decided here, and nothing about L2 changes in the Advanced-metrics train. **Measured in a real Agent, 2026-11-11 (owner decision D110), and answered (D117).** `tools/agent-cost.ps1` runs the shipped `FrameLedger.Agent.exe --console capture` against a copy of hook-harness in a scratch data folder — a session that is not hooked, so the telemetry poller runs as in every session and nothing drains frames — and reads the Agent process's own processor time at exit; the cost per second is the slope between a 45 s and a 165 s session, two runs of each. Dev box (RTX 5080, not elevated, layers `l1+lhm+nvapi`): **19.3 ms of processor time per second of session = 1.93 % of one core with Advanced metrics off** (2,312 and 2,312 ms over 45 s; 4,594 and 4,656 ms over 165 s), **20.4 ms = 2.04 % with it on** (2,984 and 3,000; 5,547 and 5,344); peak working set 113 MiB and 119 MiB. A first pass with 30 s and 90 s sessions gave 1.56 % and 2.21 % — its two short runs differed by 670 ms, which is why the lengths were raised. So the probe's number holds in a session: the Agent's steady cost is about twice NFR-2's 1 %, nearly all of it the layer every session has always used, and the new option adds about a tenth of a percent. **The owner's answer: NFR-2 is amended to ≤ 2.5 % of one core** — the limit had never been measured, the sensors keep their one reading a second, and nothing in the code changes. Not measured: a hooked session (the drain's cost on top), a session with the Agent elevated and PawnIO's groups open, another PC. |
|
||||
| M14 ❓ | **Reflex latency per frame — is there a route within rules 4 and 5? (Train C, 2026-11-11.)** `17_HOOK_ENGINE` §Memory / latency names hooks on `NvAPI_D3D_SetSleepMode` / `SetLatencyMarker` and a call to `NvAPI_D3D_GetLatency`. NVAPI resolves all three through `nvapi_QueryInterface` by id — they are not exports, so a hook on them is a patch at an address learned at run time, the class refused on 2026-08-09. The route to try first needs no hook: the Overlay's own background thread **calls** `GetLatency` with the device of the swap chain it already hooks, once a second (the call returns the last 64 frames' reports). Unknown: whether calling into the driver from that thread is safe on every device kind, what it costs, what it returns when the game never enabled Reflex, and what it means for the Disclaimer's sentence about that thread. | **A spike on `hook-harness` and a stub first, then one real title.** Pre-committed: no route without a patch at a run-time address or a loader-lock call on the game's thread → Reflex stays N/A and the page says why; overhead above NFR-1 → the same. The owner says go or no on the spike's result. **2026-11-12 — the reading that comes before that spike is `spike-notes` §30** (owner decision D130: a document first, beside 0.1.0-beta.45; nothing was run). It finds: a hook on NVAPI's latency functions is the refused class, and a hook on Streamline's Reflex and PCL functions is train D's wrapper (§M15) — and would miss a game that fetched them before the attach, as `slInit` is missed (D129); the Overlay calling `slReflexGetState` itself breaks the thread contract the vendor's header states; **what remains is the route named in this row**, the Overlay calling two driver getters with the game's device, and a no-injection ETW route that gives the game-side markers only and makes the game post messages to its own window. Corrected there: `nvapi64.dll` exports **two** functions on the dev box (`nvapi_Direct_GetMethod` beside `nvapi_QueryInterface`), not one. The go or no is the owner's, and a go needs the owner's ruling that calling a driver getter with the game's device is inside rule 4. **2026-11-13 — the owner answered (D132, D133).** Route D goes to the spike this row names, on `hook-harness` and a stub `nvapi64.dll`, with the ruling: a driver's read-only getter called with the device of the swap chain the Overlay hooks is inside rule 4 (`CLAUDE.md`, the rule's note of that day). No real game before the owner has seen the result, and nothing shipped changes for the spike (`spike-notes` §31, written after 0.1.0-beta.46). Route C is **refused**; the ETW route **stays closed**, and §G is not reopened. **2026-11-13 — the harness spike is done (`spike-notes` §31), and none of its stop conditions fired.** With a stand-in module: nothing is called or loaded when `nvapi64.dll` is absent, a missing getter is refused whole, an error and a report of nothing read as what they are, and a call the driver holds for seconds stops only the thread that made it — so not the watchdog. With the installed driver (32.0.16.2114, RTX 5080), in the probe's own process and with the probe setting the markers a game would: no fault before `NvAPI_Initialize`, without markers, or across 38 million reads beside a marker-setting thread; a call costs half a microsecond to a microsecond and a half; the report is readable from markers alone, in microseconds; and the Direct3D 12 **device** — the object the Overlay already holds — is what the driver takes. What only a game can say is unanswered: a game's own device, a real report, another driver. **The owner's next word is go or no for one real title**; a go is a plan of its own first. **2026-11-13, the same evening — go (D136)**: a plan for one title, Cyberpunk 2077; no code before the plan is approved, and no release carrying it before a stop while a game runs has been exercised on 0.1.0-beta.46 (owner-only item 44 (d)). **2026-11-13, the plan and four more answers (D138–D141).** The read has **no switch of its own**: it is part of Advanced metrics, so after the release it reaches every Direct3D 12 game that loaded the driver's `nvapi64.dll`, for everyone who switched Advanced metrics on — "one title" is the order of the owner's first runs, not a limit in code (D138). The probe ran a leg with a sleep mode first (D139; `spike-notes` §31, *The leg with a sleep*): **the getters do not wait behind `NvAPI_D3D_Sleep`** — thirty-one million reads beside a thread that slept 97 % of the time, none of a millisecond; a read after a sleeping frame costs about 2.6 µs. An `nvapi64.dll` loaded from the game's own folder is refused with the reason (D140). One call of 2 ms or more switches the read off until the game exits (D141). The plan's design, as reviewed against the source, is in [`handoff/history/0.1.0-beta.46.md`](handoff/history/0.1.0-beta.46.md) §The train after 0.1.0-beta.46. **2026-11-13, night — written; released as 0.1.0Line truncated
|
||||
| M15 🅓 | **Decided 2026-11-14 (D154): not built. The owner closed Advanced metrics with the refusal standing; the ten entries are listed as not read, with the reason.** ~~**The Streamline state behind `slGetFeatureFunction` — re-examined, not reopened (Train D, 2026-11-11).**~~ The owner asked for the refusal in `handoff/history/p0-queue-1-6.md` to be looked at again. `18_GPU_VENDOR_APIS` §The trains states the route to try (hook the export, hand back a wrapper for a fixed list of names) and what it raises: the wrapper is a write to what the game receives, which rule 4 forbids as written; a wrapper must outlive the Overlay's unhook; a game that fetched its functions before the hook existed is never seen. | **A written design against each of the five grounds, then a spike.** Pre-committed: any ground unanswered → the route stays refused, and `sl.dlssg.*`, `sl.reflex.*` and the rest of that block read N/A with "refused" as the reason. Proceeding needs the owner's amendment of rule 4, asked with the rule quoted. |
|
||||
| M10 ✅ | ~~PDH `\GPU Engine(*)\Utilization Percentage` summed across engines does not reproduce the Task Manager figure the doc invokes. Decide what we actually report and label it accordingly~~ **Decided 2026-09-09 (PR-E1): L1 does not read the engine counters at all.** `LoadPct` is L2's vendor-reported `GPU Core` load (measured ✓ on NVIDIA, §M5 row R1) and is labelled *GPU load (vendor)* wherever it is shown; on a machine without L2 the field is N/A, never a sum that is not the number the user expects. What L1 does read from PDH is one counter, `\GPU Adapter Memory(luid_…_phys_0)\Dedicated Usage`, bound by LUID — the figure Task Manager labels "Dedicated GPU memory", measured 1301 MB at an idle desktop on the RTX 5080. Reopening this needs a measurement of `max(engine)` against Task Manager's own number, not a decision |
|
||||
|
||||
#### §M5 — the decision table, pre-committed 2026-09-03 BEFORE the first run
|
||||
|
||||
@@ -1,108 +0,0 @@
|
||||
# 21 — Input devices: controllers, and keyboard-and-mouse activity
|
||||
|
||||
What FrameLedger reads about game controllers and about the keyboard and mouse, from where, and what it never reads.
|
||||
The numbers a session makes of it are in [`03_METRICS.md`](03_METRICS.md) §Input; the columns are in
|
||||
[`06_DATA_MODEL.md`](06_DATA_MODEL.md).
|
||||
|
||||
> **Status, 2026-11-14 — nothing reads a device yet.** The model and the arithmetic exist (`FrameLedger.Domain.Input`,
|
||||
> `FrameLedger.Application.Input`, `Application.Recording.InputSessionBuilder`), under tests whose every byte and
|
||||
> reading was written by hand. The reader, the storage, the switch and the screens come in the pull requests after
|
||||
> it, and this note is rewritten by each. **No report from a real controller has passed through any of this code**
|
||||
> (owner decision D157): the developer has no controller, and what happens on a real one is owner-only item 48.
|
||||
|
||||
## The owner's request and decisions (2026-11-14)
|
||||
|
||||
The request: whether a game supports controllers, on the game's page; the share of a session played with a controller
|
||||
and with the keyboard; how often a controller connected and disconnected in a session; the battery state that lasted
|
||||
longest; switches between makers' controllers and each maker's share; stored, and drawn; Xbox controllers and the
|
||||
DualSense first.
|
||||
|
||||
| | Decision |
|
||||
|---|---|
|
||||
| **D155** | Controllers are read **by the Agent, from outside the game**. No hook is added to a game and CLAUDE.md rule 4 is untouched. A session that is not hooked has the numbers as a hooked one does. |
|
||||
| **D156** | The reading is **on unless switched off** (Settings ▸ Controllers and input, `capture.input_devices`), and **reads nothing until the Privacy Policy that describes it — 2.22 or later — has been accepted on the PC**. An Agent that the logon task started after an update records sessions without it until the App has been opened once. |
|
||||
| **D157** | **Built without a probe.** Asked whether to run a probe tool with real controllers first, the owner chose to build straight. So every source says what it did (§What the reader says about itself), and each pull request and `LIMITATIONS.md` say what was verified against hand-made data only. |
|
||||
| **D158** | Keyboard and mouse are **one class, known only by the time of the last input** (`GetLastInputInfo`). No Raw Input registration for a keyboard or a mouse, no hook: no key ever enters FrameLedger's process. |
|
||||
| **D159** | **Nothing is ever sent to a controller**: no output report, no feature-report request, no `XInputSetState`. A DualSense on Bluetooth therefore has a battery level only when Steam or the game has already switched it to its long report (§DualSense). |
|
||||
| **D160** | The numbers are **in the CSV/JSON export and in a bug bundle** — they are columns of `sessions`, as the display mode's are — and the Privacy Policy's §3A says so. |
|
||||
| **D161** | **A session that is not hooked is: duration, hardware telemetry, the reason — and what the Agent reads from outside the game** (the game's memory since beta.12, controllers now). Every field measured inside the game still reads N/A. CLAUDE.md's sentence is amended with the pull request that makes it true. |
|
||||
| **D162** | Also built: the number of switches between a controller and the keyboard and mouse, and the share of time with no input; marks on the frame-time chart where a controller connected, dropped or ran low; a battery's first and last level and its rate; the kind of connection; a note where Steam Input presented the controller as an Xbox pad; a trend metric, a row in Compare, and "usually played with" on the game's page. |
|
||||
| **D163** | "Supports controllers" is **three pieces of evidence, never a verdict**: what Steam's own file on the disk says (no network: rule 8), which input libraries the game loaded, and how the game was actually played. From outside a game one can know that a controller was in use while the game was in front — not what the game did with it. |
|
||||
|
||||
## What is read, and from where
|
||||
|
||||
Everything is a Windows API in a library Windows ships. **No third-party library is added.**
|
||||
|
||||
| Source | What it gives | Why this one |
|
||||
|---|---|---|
|
||||
| Raw Input (`RegisterRawInputDevices`, usage page 1, usages 4 and 5, `RIDEV_INPUTSINK \| RIDEV_DEVNOTIFY`) | the reports game controllers send, while the Agent is in the background; a controller arriving and leaving; its vendor and product ids | the documented way to receive a HID controller's reports without being in front, and it opens no handle to the device |
|
||||
| `hid.dll`'s parser (`HidP_GetCaps`, `HidP_GetUsages`, `HidP_GetUsageValue`) | which usages of a report are set | a parser, not I/O: it reads the bytes Raw Input handed over |
|
||||
| XInput 1.4 (`XInputGetState`, `XInputGetCapabilities`, `XInputGetBatteryInformation`) | each of its four pads: its state, wired or wireless, a battery in four levels | what an Xbox pad's battery is reported through |
|
||||
| `GetLastInputInfo` | the time of the last keyboard or mouse input in the user's session | a time and nothing else (D158) |
|
||||
| `GetForegroundWindow`, `GetWindowThreadProcessId` | whose window is in front | already used for the focus sample (`04_CAPTURE`) |
|
||||
| Steam's `appcache\appinfo.vdf`, on the disk | whether the store lists controller support for a library game | a local file: no request is made (rule 8) |
|
||||
|
||||
**Rejected, with the reason** (the checklist of `18_GPU_VENDOR_APIS` §Checklist applies to any library):
|
||||
|
||||
- **Windows.Gaming.Input** — its readings stop when the program is not in front, which the Agent never is.
|
||||
- **GameInput** — on a PC it is a NuGet package under Microsoft's licence terms with a redistributable to install.
|
||||
- **Opening the HID device** (`CreateFile`) — a handle of FrameLedger's on a controller can make a game's, or a
|
||||
remapper's, exclusive open of it fail. Raw Input needs none.
|
||||
- **A sixth native library** — parsing bytes a device controls in C++, inside an Agent that may run as administrator.
|
||||
The reader is C#, and what parses a report is `FrameLedger.Domain.Input`, with no pointer in it.
|
||||
|
||||
## What is never read
|
||||
|
||||
Which button, where a stick or a trigger is, the motion sensors, the touchpad; which key, what was typed, where the
|
||||
mouse is; a controller's serial number, its Bluetooth address, its device path. A report is looked at to answer one
|
||||
question — *is anything on this pad in use?* — and, for a DualSense, to take its battery byte; the answer is kept and
|
||||
the report is not. `InputSessionBuilderTests` hold the stored JSON to a list of keys, so a key that could carry an
|
||||
identifier has to be added to a test first.
|
||||
|
||||
## Who a controller is
|
||||
|
||||
By its USB vendor and product ids only (`Domain.Input.ControllerCatalog`): Microsoft is the Xbox family, Sony
|
||||
PlayStation, Nintendo Nintendo, anything else *other* — except that a pad Windows presents through XInput is in the
|
||||
Xbox family whoever made it, because that is all Windows says of it. A model has a name only where the catalog lists
|
||||
its ids; a wrong name would be worse than none. Two pads of one model on one kind of connection cannot be told apart
|
||||
across a reconnect, and are not.
|
||||
|
||||
## XInput
|
||||
|
||||
A state is a pad *in use* when a button is down, a trigger is past `XINPUT_GAMEPAD_TRIGGER_THRESHOLD` or a stick is
|
||||
outside its `XINPUT_GAMEPAD_*_THUMB_DEADZONE` (`Domain.Input.XInputPad`) — a stick held counts, one that drifts inside
|
||||
the dead zone does not. Its battery is XInput's words: a wired pad, or four levels with no word for charging.
|
||||
|
||||
Two things about XInput are not established and are what item 48 is for: Microsoft's page for `XInputEnable` says
|
||||
that on Windows 10 and later "game controller input is automatically enabled/disabled by the system based on the
|
||||
application window focus", which may mean a program in the background reads a neutral state; and a pad on Bluetooth
|
||||
is reported not to answer `XInputGetBatteryInformation`. XInput also has no documented way to say which device one of
|
||||
its four pads is.
|
||||
|
||||
## DualSense
|
||||
|
||||
Sony's 054C:0CE6, and the Edge, 054C:0DF2 (`Domain.Input.DualSenseReport`). Three reports:
|
||||
|
||||
| Connection | Report | What it carries |
|
||||
|---|---|---|
|
||||
| USB | `0x01`, 64 bytes | sticks, triggers, buttons — and the battery: a level in tenths and what the battery is doing |
|
||||
| Bluetooth, as connected | `0x01`, 10 bytes | sticks, buttons, triggers. **No battery** |
|
||||
| Bluetooth, once switched | `0x31`, 78 bytes | the USB report's body, one byte later |
|
||||
|
||||
The pad sends the short report until some program asks it for a feature report or sends it an output report; from then
|
||||
until it reconnects it sends the long one. **FrameLedger never asks** (D159): a game that reads the short report through
|
||||
DirectInput would lose its input. So over Bluetooth the level is there when Steam or the game switched the pad, and is
|
||||
not otherwise. Windows hands every report of a device over at the length of the device's longest, so the short report
|
||||
arrives padded to 78 bytes with the id the USB report has: the connection, not the length, says which layout a report
|
||||
`0x01` has.
|
||||
|
||||
The layout was written from the open descriptions of the protocol. No code was taken from the Linux kernel's driver,
|
||||
which is under a licence this project cannot take code from.
|
||||
|
||||
## What the reader says about itself
|
||||
|
||||
`Application.Input.InputHealth`, carried by every reading and stored with the session: whether Windows accepted the
|
||||
registration, how many reports came and how many could not be read, whether XInput's library was there and how many
|
||||
states it returned, how often a controller's own reports said *in use* while XInput said nothing, whether the time of
|
||||
the last input could be read, how many slices were taken and how much processor time the reader's thread used. Counts
|
||||
and yes-or-no answers; nothing in it names a device.
|
||||
+86
-713
@@ -76,150 +76,111 @@ owner-only items stay below; the history of every train, the passed owner-only i
|
||||
| `§beta.34` | [`handoff/history/0.1.0-beta.34.md`](handoff/history/0.1.0-beta.34.md) |
|
||||
| `§beta.35` | [`handoff/history/0.1.0-beta.35.md`](handoff/history/0.1.0-beta.35.md) |
|
||||
| `§beta.36` | [`handoff/history/0.1.0-beta.36.md`](handoff/history/0.1.0-beta.36.md) |
|
||||
| `§beta.37` | [`handoff/history/0.1.0-beta.37.md`](handoff/history/0.1.0-beta.37.md) |
|
||||
| `§beta.38`, `§NEXT` (the owner's request of 2026-11-11, the four trains) | [`handoff/history/0.1.0-beta.38.md`](handoff/history/0.1.0-beta.38.md) |
|
||||
| `§beta.39`, train B's plan as approved (its `§NEXT`) | [`handoff/history/0.1.0-beta.39.md`](handoff/history/0.1.0-beta.39.md) |
|
||||
| `§beta.40`, what the owner's first sessions with it showed, train B's traps | [`handoff/history/0.1.0-beta.40.md`](handoff/history/0.1.0-beta.40.md) |
|
||||
| `§beta.41`, what the owner's sessions on beta.40 and beta.41 showed, the plan of 2026-11-12 (D119–D122) | [`handoff/history/0.1.0-beta.41.md`](handoff/history/0.1.0-beta.41.md) |
|
||||
| `§beta.42`, what the owner's seven sessions on beta.42 showed (D121 answered, the guard's lost launches), beta.43's design as planned | [`handoff/history/0.1.0-beta.42.md`](handoff/history/0.1.0-beta.42.md) |
|
||||
| `§beta.43`, what the owner's nine sessions on beta.43 showed, session by session (item 41), the traps of that train | [`handoff/history/0.1.0-beta.43.md`](handoff/history/0.1.0-beta.43.md) |
|
||||
| `§beta.44`, what the owner's eight sessions on beta.44 showed, session by session (item 42), this release's facts, the traps of that train | [`handoff/history/0.1.0-beta.44.md`](handoff/history/0.1.0-beta.44.md) |
|
||||
| `§beta.45`, what the owner's seven sessions on beta.45 showed, session by session (item 43), that release's facts and SonarCloud's gate on its commit, the traps of that train | [`handoff/history/0.1.0-beta.45.md`](handoff/history/0.1.0-beta.45.md) |
|
||||
| `§beta.46`, what the owner's five sessions on beta.46 showed (item 44), the design of the train that followed as the plan's review left it (`§The train after 0.1.0-beta.46`), that release's facts, the traps of that train | [`handoff/history/0.1.0-beta.46.md`](handoff/history/0.1.0-beta.46.md) |
|
||||
| `§beta.47`, what that release decided beyond D136–D141, what item 44's last part showed, that release's facts, the traps of that train, its NEXT as the owner's sessions of 2026-11-14 changed it | [`handoff/history/0.1.0-beta.47.md`](handoff/history/0.1.0-beta.47.md) |
|
||||
| `§beta.48`, what that release decided beyond D142–D147, that release's facts, the traps of that train, its NEXT and its "Left open" as item 46 changed them | [`handoff/history/0.1.0-beta.48.md`](handoff/history/0.1.0-beta.48.md) |
|
||||
| `§Owner-only`, an open item | [§Owner-only](#owner-only--no-pr-can-close-these) below |
|
||||
| `§Owner-only`, a passed item (3, 12, 14–19, 38, 39) | [`handoff/owner-only-passed.md`](handoff/owner-only-passed.md) |
|
||||
| `§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) |
|
||||
| `Dnn` | [§Decisions index](#decisions-index) below |
|
||||
|
||||
---
|
||||
|
||||
## **START HERE** — 2026-11-14, 0.1.0-beta.49: item 46 read; the frames counted for the log, Reflex and frame generation together; a read a second on a grid; the Agent keeps the reading that waits
|
||||
## **START HERE** — 2026-11-11, 0.1.0-beta.37: the main line on .NET 11, what an alpha is now, and why no C# 15 yet
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.49.md`; this is what no other file carries.* The owner ran item 46 on
|
||||
beta.48 the afternoon it was released — ten sessions, then eight more — and said: check (#455, and item 46's last
|
||||
paragraphs, below). The read works, the samples are a second apart, both games give both of the driver's own
|
||||
times, the multipliers are listed, off means off, **and the owner's word: no hitch**. Two things were left, the
|
||||
owner said *do both*, and four answers given while planning made the train (D148–D151): #456 (the Overlay counts
|
||||
each summed frame for its log), #457 (the watchdog's periodic tick on a grid), #458 (the Agent keeps the reading
|
||||
that waits; the guide on whose switches the table shows), and this release. **beta.48's own section, its traps
|
||||
and its release facts are [`handoff/history/0.1.0-beta.48.md`](handoff/history/0.1.0-beta.48.md).**
|
||||
*Status is `docs/changelog/0.1.0-beta.37.md`; this is what no other file carries.* The owner, with two screenshots — a
|
||||
Qodana Ultimate licence in the JetBrains console, and the Qodana Cloud project's setup page: "Bạn có thể bắt đầu với phiên
|
||||
cải tiến cho .net 11 và set up cho qodana cho tất cả ngôn ngữ (gói ultimate) nhé." The session D92 had left for after
|
||||
.NET 11's release (2026-11-10), and Qodana for every language on the Ultimate licence. One plan, approved whole, in
|
||||
three parts: **beta.37** (#376 the move, #379 what an alpha is, #380 .NET 11's API and the C# 15 finding, and this
|
||||
release) → **alpha.4** → **Qodana Ultimate in two reports**. This section is the first part; the other two follow it on
|
||||
`main` the same way.
|
||||
|
||||
### What this release decided, beyond D148–D151
|
||||
**Decisions (asked while planning, do not re-ask):**
|
||||
|
||||
- **The counts are of each frame's own two numbers, with sums, and no threshold.** The draft counted spans of no
|
||||
length; a sample whose mean span is half a microsecond says spans of one or two microseconds exist, and a count
|
||||
of exact zeros would have read "the driver's" where it was "ours". So the frames that have both a span and an
|
||||
active time are kept in two heaps — active longer than the span, or not — each with its count and both sums.
|
||||
- **A batch's state is three things**: the driver's low-latency switch, its "the game sleeps" switch
|
||||
(`bUseGameSleep`: NVAPI's "is `NvAPI_D3D_Sleep()` being called") and its frame-generation multiplier. The second
|
||||
was added on the owner's word — Reflex goes with frame generation in the owner's games, and the low-latency
|
||||
switch can be the NVIDIA App's override — and Clair Obscur's two sessions read exactly that: `bUseGameSleep`
|
||||
off throughout without frame generation, on with ×3.
|
||||
- **Only the driver read and the publication are the periodic tick's.** The request is still followed on every
|
||||
tick, so the hooks a session asks for go in on the tick the loader woke — a game that has just loaded
|
||||
Streamline calls it at once. A draft that moved the whole block would have missed those calls.
|
||||
- **One read is armed at every periodic tick, and the grid is what keeps two apart**: half a second at the least,
|
||||
after a tick that ran that late. "At most once a second" is no longer said anywhere.
|
||||
- **A session's first publication may hold a moment's worth.** A request seen on a woken tick is published by the
|
||||
periodic tick that follows, however soon. One test read a single publication as complete and had to stop.
|
||||
- **The Agent keeps two sets, and an empty one does not wait.** A reading can stand at the sample after the one it
|
||||
would have ridden — a second later. With the sensor interval above a second the oldest is still pushed out.
|
||||
- **No legal text changed (D149)**, although a bug report carries the Overlay's logs and so these lines: the
|
||||
owner was told and chose it. The Privacy Policy names the logs of the component loaded into games.
|
||||
- **The plan was reviewed against the source by a second reader before the owner saw it, and sixteen things in
|
||||
the draft were wrong** — among them the three above, and the whole of the Agent's half, which the draft did not
|
||||
have.
|
||||
- **D94 — the main line moves to .NET 11 now.** Asked whether the betas move or only alpha.4 — with
|
||||
`20_OPEN_QUESTIONS` §G's table quoted: two alphas on the released runtime and an owner's run of a hooked title first —
|
||||
the owner chose "Chuyển main sang .NET 11 ngay". Condition (a) of that table was **set aside, not met**;
|
||||
`12_BUILD` §The main line's .NET says what stood in for it, and owner-only item 34 is the run it asked for.
|
||||
- **D95 — Windows 10 22H2 is not blocked, and is stated as untested and unsupported** ("Vẫn chạy, ghi rõ không được hỗ
|
||||
trợ"). NFR-8 is amended; a processor needs SSE4.2 and POPCNT.
|
||||
- **D96 — C# 15 in the same release** ("Áp dụng cả C# 15 ngay trong beta.37"). The plan narrowed it in writing, and was
|
||||
approved with that: a construct only where the build, CodeQL and Qodana all read it.
|
||||
- **D97 — all three legal texts reworded** ("Sửa cả ba văn bản"): EULA 1.7, Disclaimer 2.14, Alpha notice 1.1. Their
|
||||
text was in the plan and approved with it.
|
||||
- **D98 — alpha.4, then the alpha line rests** until a newer .NET has a preview ("alpha.4 rồi nghỉ tới .NET 12
|
||||
Preview").
|
||||
- **The order**: beta.37 → alpha.4 first, Qodana after; and Qodana in **two reports from the start** (the third part's
|
||||
decision, D99).
|
||||
|
||||
### Traps this train left
|
||||
**Choices made here:**
|
||||
|
||||
- **A cause I offered and then counted away**: "the holes are the sensor library's fifth tick" — 25 of 134 fell on
|
||||
one. The pattern that was there (46 of 134 exactly five samples apart) was the Agent's own attach rule, found
|
||||
by reading `SessionRecorder`, not by looking harder at the Overlay.
|
||||
- **A fixture that proved nothing**: the case for a woken watchdog first churned `sl.common.dll`, which wakes
|
||||
nobody — it is in neither the inventory nor the census — and passed. It was caught only because the case
|
||||
asserts, from the log, that the watchdog *was* woken (0 early ticks). **A test of a mechanism asserts that the
|
||||
mechanism ran.** `opengl32.dll` is the wake that unloads nothing under a hook.
|
||||
- **Qodana's native report reads the tests**: `static_cast<unsigned long long>(a * b)` is
|
||||
`bugprone-implicit-widening-of-multiplication-result`. Widen an operand, not the product.
|
||||
- **A here-document with an apostrophe in it failed again.** Edit scripts are files.
|
||||
- **No edit while a gate runs still holds when CI asks for one**: the Qodana fix went into a second worktree of
|
||||
the lower branch, and reached the upper one by a merge.
|
||||
- **The item's own text said "nothing is lost by it" of the holes**, on a reading of the Overlay alone. A reading
|
||||
was lost at every return to step. Say what was looked at.
|
||||
- **No C# 15 construct is used, although the owner asked for them.** The rule decided it, not a preference:
|
||||
ReSharper's engine, which Qodana runs, reads none of the four (`13_CI_CD` §C# 15 and the analyses, `spike-notes`
|
||||
§29). Unions would not have been the form in any case — the SDK's own CA1815 asks every union to hand-write its
|
||||
equality, and the shapes that wanted one are closed record hierarchies. What the release takes is API.
|
||||
- **.NET 11's `IHost.RunAsync` is accepted, not wrapped**: a failed background service now ends the Agent through its
|
||||
crash report. A catch there would hide a fault, and could not reproduce .NET 10's exit exactly either.
|
||||
- **A resting alpha says so in the build, not only in its notes**: the anti-cheat list reaches a user only inside a
|
||||
release, so an alpha nobody updates carries an ageing one. `FlAlphaLineRests` is stamped on both lines; the `alpha`
|
||||
branch sets it to false when it next tries a .NET.
|
||||
- **"A prerelease .NET" is said only by a build that runs on one**, read from the runtime's own description — the next
|
||||
preview alpha says it again with no change to the code.
|
||||
- **`release.yml` names the .NET 10 runtime `vpk` needs**, rather than relying on the hosted image carrying one.
|
||||
- **The Community Qodana job was kept alive across the move** by installing the SDK into its container — an interim;
|
||||
the Ultimate linter replaces the job in the third part.
|
||||
- **The 2026-10-31 forms stay where they read as well** (`json.AsSpan().TrimStart().StartsWith('[')` avoids a string):
|
||||
.NET 11's `char` overloads replaced a span only where the span was there for .NET 10's sake.
|
||||
|
||||
### NEXT
|
||||
**Measured on the way** (`spike-notes` §28 and §29): the gate on SDK 11.0.100 — two analyzer sites beyond RC3's
|
||||
twenty-one, both in tests written after the last alpha; `IHost.RunAsync` rethrowing, observed for the first time; the
|
||||
first delta across two runtime majors (372 of 443 files patched, 72.6 MB on the rehearsal); `main`'s first full CodeQL
|
||||
C# analysis on `net11.0` (1,221 of 1,221 files, the same 23 unresolved `Windows.Win32` types as on .NET 10); the
|
||||
SonarScanner 12.0.0 on the 11.0 runtime; InspectCode 2026.2.3.1 and 2026.3.0 against each C# 15 construct.
|
||||
|
||||
1. ~~**The owner runs item 47**~~ **Run and read 2026-11-14** (item 47, *Run 2026-11-14*): the difference in
|
||||
Cyberpunk 2077 is the driver's, the holes are gone from steady play, off means off, and the stop fired once.
|
||||
2. **The two GPU labels were reworded on the owner's word** (D152, 2026-11-14; strings in three languages, the
|
||||
guide — in `[Unreleased]`, not in a release yet). **D141's stop stays as it is, and nothing more of Reflex is read** (D153, the owner
|
||||
the same evening: "it only has to tell whether the game has it or not; Kingdom Come: Deliverance II has no
|
||||
Reflex in its settings" — so that session lost nothing to the stop). (f) and (g) are said: the App's *Low
|
||||
Latency Mode* is off, and no hitch.
|
||||
3. **`slAllocateResources`** keeps its patch (D135); looked at again when there are more sessions.
|
||||
4. ~~**Train D**~~ **Advanced metrics is closed (D154, 2026-11-14): train D is not built.** The owner was shown
|
||||
the catalog — 140 entries, 110 read — and what the ten entries of reach `Spike` hold (Streamline's own headers,
|
||||
2.14.16: DLSS frame generation's options and state, the video-memory estimates, ray reconstruction's, Image
|
||||
Scaling's and Dynamic Vibrance's options, the PCL markers), with what reading them takes: a function of ours
|
||||
handed to the game in place of Streamline's (rule 4), which a game that fetched its functions before the
|
||||
attach never calls. The owner: "Đóng luôn". The ten are `RefusedRoute` now, the guide no longer says a later
|
||||
release reads more, and §M15 is decided. **What is next is the controller feature**, planned in a session of
|
||||
its own.
|
||||
**Traps met on the way:**
|
||||
|
||||
### Left open by this session
|
||||
- **A pull request's CodeQL C# run is an overlay analysis**: it extracts the changed files on top of `main`'s cached
|
||||
database, and its "scanned N out of N" is `main`'s baseline. #376 wrote "CodeQL reads `net11.0` whole" from one and
|
||||
was corrected, dated, two pull requests later with `main`'s own run. For anything the extractor has not met, dispatch
|
||||
`codeql.yml` on the branch (it takes `workflow_dispatch` since #380).
|
||||
- **`ShmDrainIntegrationTests.TheGuardInjectsTheOverlayAndTheReaderDrainsRealFrames` failed once on the dev box** —
|
||||
"our own harness must not start matching the blocklist mid-run": the guard's re-scan refused the harness in one gate
|
||||
run of five. The class passed three times in a row straight after and no guard code had changed; not looked into.
|
||||
- **A wiki page names no version** (`wiki-check`): "since 0.1.0-alpha.4" in `wiki/Releasing.md` was red. The guide's
|
||||
pages may.
|
||||
- **The runner queue**: with three workflows per pull request and a probe's pull request open beside the train,
|
||||
`check` waited about 25 minutes for a runner. Cancel a probe's runs once it has told what it can.
|
||||
- **A Bash heredoc halves the backslashes** of an inline Python regex — write the script with the Write tool.
|
||||
- **`x.Should().NotBeNull(); x!.Member`**: ReSharper reads the `!` as redundant (Qodana's one finding on #376) and the
|
||||
compiler wants it. Keep the value the assertion needs, not the object.
|
||||
- **CA2025** on a lambda that captures a `using` variable in a test: await inside a `try`, assert after.
|
||||
- **A local gate reseeds `%LOCALAPPDATA%\FrameLedger\rules`** while the owner's installed copy runs beside it: the
|
||||
files were hashed before and after every gate (identical each time — the repository's rules were the installed ones).
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request, with what SonarCloud and Qodana said.~~ **Recorded
|
||||
2026-11-14: 0.1.0-beta.49 was released 2026-11-14T11:12:44Z** (18:12 in the owner's time zone) from the signed
|
||||
tag on `afe4984` (#459), by run 43587336452 — green at the first attempt, one run for the one tag push. Eight
|
||||
assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed, and the portable package hashed
|
||||
here equals its line; the five native libraries in it carry `FL_BUILD_ID v0.1.0-beta.49`, none of them
|
||||
`-dirty`. The delta from beta.48 is 1 100 211 bytes beside a full package of 110 803 443 — "Delta processed
|
||||
0452 files. 0023 patched, 0429 unchanged". The wiki was published by run 43588972123. **Two rehearsals on the
|
||||
release branch**: run 43580081466 at `1ab2809`, and — after a test-only fix reached the branch — run
|
||||
43581734484 at `9f94356`, whose tree is the released one (a delta of 1 134 949 bytes, the same file counts).
|
||||
**SonarCloud analysed `afe4984`: the quality gate passed and no issue is open on `main`. Qodana's two reports,
|
||||
CodeQL and `check` are green on that commit.** On the way two advisory checks did find something, each in a
|
||||
test of this train and each fixed before its pull request merged: Qodana's native report on #456 (two
|
||||
products widened after the multiplication), SonarCloud on #457 (a line of the log handed to `printf`). **The
|
||||
train stopped once for the owner**: two signed merges timed out at the passphrase prompt after #457; it went on
|
||||
when the owner had unlocked the key. The tag's message reads `FrameLedger 0.1.0-beta.49` where the tags before
|
||||
it read the bare version — nothing reads it, and a pushed tag is not moved.
|
||||
- **Why Cyberpunk 2077's active render is longer than its span without frame generation** — item 47's to say. A
|
||||
third session that afternoon repeated it (233: 3.40 against 3.13 ms at 292 of 296 samples) and a session of
|
||||
menus did not (232: 0 of 126).
|
||||
- **The Agent's half of the holes is read from the code and fits the ledger; it is not measured.** And with both
|
||||
sides on a second a slip of phase can still leave a sample without a report: item 47 counts them.
|
||||
- **A game that exits by itself loses the batch of counts in hand** — under a minute. Not changed: nothing runs
|
||||
at a process's exit.
|
||||
- **Where the third of a second of a poll goes is not established** (the history file of beta.48 has what is
|
||||
known). Not looked at in this train.
|
||||
- **With the sensor interval above one second, some readings of the driver's report are not stored** — the oldest
|
||||
of the two that wait is pushed out. Said in the guide; not changed.
|
||||
- **No test runs the whole path through the real Agent**: the injected tests stop at the shared memory, the
|
||||
sampler's and the pending queue's start from it.
|
||||
- **Two install batches of beta.46 took 0.61 s and 1.26 s and nothing explains them.** Item 46's ten sessions had none
|
||||
above 191 ms.
|
||||
- **The Japanese strings are unreviewed**, as every `ja` string is; this release added none.
|
||||
- **(c) and (h) of item 43**, which only the owner sees, are still not exercised.
|
||||
- **Valor Mortis's crash at 51 s** (twice, beta.40 and beta.44) **and Black Myth: Wukong's fault in Steam's crash
|
||||
handler at every exit** are not explained. One session of each with hooking off is the comparison that is missing.
|
||||
- **What item 41 left unexercised**: a configure through the FidelityFX 2.3 loader (Cyberpunk 2077 with FSR frame
|
||||
generation), a game with neither library.
|
||||
- **A fault while a game is closing is not seen by a hooked session** (D127: written down, not changed).
|
||||
- **`docs/LIST_GAME_TESTED.md` is as of 2026-11-06**: refreshing it is a new copy of the ledger and the owner's review.
|
||||
- **Item 40 (d)** was not exercised and the owner has not said item 40 passed. **Items 36 (d) and 37 are still open.**
|
||||
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
|
||||
sensors "have never been read on real hardware"** — the owner's to reword. The alpha line still rests (D98).
|
||||
**Owner-only:** item 34 — beta.37 on real hardware, a hooked session on .NET 11.0.0, and Windows 10 if a PC with it is
|
||||
at hand.
|
||||
|
||||
### 0.1.0-alpha.4 — the fourth alpha, the same day, and the last for now (D98)
|
||||
|
||||
`alpha` takes main at this pull request — `v0.1.0-beta.37` and these notes, no other change — by a merge commit. **This
|
||||
sync is not like the three before it**: main now holds what the switch held (`global.json`, the TFM, the three
|
||||
packages, `legal/licenses/nuget/`, the *Transitive* row), so every switch file conflicts, and each is resolved by
|
||||
taking main's — the branch's RC3 lines go, `RELEASE_LINE` stays `alpha`, and `git diff --name-only origin/main` on the
|
||||
merged tree must print that one name. Its gate must pass on `alpha` before the pull request is merged by hand (the
|
||||
branch has no auto-merge); the release runs from the signed tag `v0.1.0-alpha.4` on `alpha`, with its delta from
|
||||
alpha.3. Its notes are `docs/changelog/0.1.0-alpha.4.md`: the warning, and that it is the last alpha for now.
|
||||
|
||||
- **After it the line rests** (`12_BUILD` §The alpha line): no sync follows a beta and no alpha is cut until a newer
|
||||
.NET has a preview. `FlAlphaLineRests` in `Directory.Build.props` says so to the build; the next trial sets it to
|
||||
`false` on `alpha` with the rest of the switch.
|
||||
- **What a resting alpha costs its user** is in its notes, the guide and its banner: no update, the anti-cheat list
|
||||
included; and once ten betas have followed it, a copy of alpha.3 or older no longer finds alpha.4 (Velopack reads
|
||||
the newest ten releases).
|
||||
|
||||
**Owner-only:** item 35 — the fourth alpha on real hardware, and the beta installed over it.
|
||||
|
||||
**Owner-only:** item 47; one session each of Valor Mortis and Black Myth: Wukong with hooking off; what item 41
|
||||
left unexercised; item 40 (d).
|
||||
|
||||
## Owner-only — no PR can close these
|
||||
|
||||
*The items that passed — 3, 12, 14–19, and 38 and 39 on 2026-11-12 — moved verbatim to [`handoff/owner-only-passed.md`](handoff/owner-only-passed.md) (the first eight on 2026-10-19, D66); the numbers are kept, and a number is never reused.*
|
||||
*The items that passed — 3, 12, 14–19 — moved verbatim to [`handoff/owner-only-passed.md`](handoff/owner-only-passed.md) on 2026-10-19 (D66); the numbers are kept, and a number is never reused.*
|
||||
|
||||
1. **§S23-2 — branch protection.** `Rules / validate` is not a required status check on
|
||||
`main`, so the gate that makes the anti-cheat blocklist un-removable is advisory.
|
||||
@@ -489,529 +450,6 @@ left unexercised; item 40 (d).
|
||||
experimental-build warning — and Help ▸ About reads *Alpha build — runs on .NET 11.0.0*, with no "prerelease".
|
||||
(d) **Then install beta.37 over it**: the installer asks to replace it; the beta opens the ledger, shows no Alpha
|
||||
notice, and its update channel is no longer locked.
|
||||
36. **beta.38, and the two Qodana reports** (D99, D100). (a) **The update from beta.37**: Help ▸ Check for updates
|
||||
offers beta.38 — a small download — and *Restart to update* installs it; no terms window. (b) **Links still open**:
|
||||
the documentation from the Help menu, a document's page on GitHub from its window, a link inside the user guide
|
||||
and inside the update notes, and the source link in Help ▸ About each open in the browser, as before. (c) **Qodana Cloud**: the projects `frameledger` and
|
||||
`frameledger-cpp` each show a report from `main` with no problem. A job's log says *Qodana license plan: Ultimate*
|
||||
and the day the subscription is active until; when it lapses both jobs go red — advisory, never a blocked merge —
|
||||
and `qodana.yaml` says the way back. (d) **`LogNoteW`**: the Overlay has one function nothing calls
|
||||
(`src/native/FrameLedger.Overlay/src/dllmain.cpp`). Say whether it is removed — a pull request of its own, eleven
|
||||
lines — or kept; either way the `.editorconfig` section that names it is then removed or reworded.
|
||||
37. **beta.39, Advanced metrics on real hardware** (D101–D109). (a) **The update from beta.38**: the terms window
|
||||
shows the **Privacy Policy 2.15** and the **Disclaimer 2.15** once; the ledger moves to schema 23 and every
|
||||
earlier session opens as before. (b) **The switch**: Settings ▸ Recording ▸ *Advanced metrics* on — **Advanced**
|
||||
appears as the last item on the left at once, **Ctrl+6** opens it; off — it goes, and Ctrl+6 does nothing.
|
||||
(c) **This PC, on the RTX 5080**: the facts (firmware, cores, memory sizes, the display's HDR and variable
|
||||
refresh), the *Right now* table beside the NVIDIA app or HWiNFO — the first comparison of any of these values
|
||||
with another tool — and the chart moving; a fan's *Read at* a few seconds behind the memory's. Leave the page: the
|
||||
Agent's log says the reader closes some fifteen seconds later, and opens again when the page does. (d) **A
|
||||
session with a real game, the option on**: it is on *Session* with its statistics and its chart; its summary has
|
||||
**Advanced metrics…** and the button opens it there; *variable refresh was active* and the colour space against
|
||||
what the game and the display really did; the driver's settings for the game against the NVIDIA app. A session
|
||||
recorded with the option off is not on the list. (e) **As administrator, with PawnIO installed** — the first run
|
||||
there has ever been (`20_OPEN_QUESTIONS` §M10, §M13): the processor per core, the memory and the motherboard's
|
||||
sensors appear on *This PC* and *Sources* says *Read*; watch for a pause or a hang when the page first opens,
|
||||
and compare a few values with HWiNFO. Without it, *Sources* gives the reason in words. (f) **What it costs**: the
|
||||
Agent's processor time and memory during a session with the option on and with it off (NFR-2: ~~1 %~~ 2.5 % of one
|
||||
core since D117, 150 MB) — ~~and with that in hand, the answer to §M16~~ §M16 was measured without a game and
|
||||
answered on 2026-11-11; what is left for a real game is the hooked session and the elevated one. (g) **The words**: the `vi` strings read as a Vietnamese
|
||||
speaker would write them; the `ja` strings marked `review`. (h) **A copy of the ledger** (`--data-dir`) that holds
|
||||
such a session: the page is there, opens on *Session*, and *This PC* says it is a copy.
|
||||
40. **beta.42 — the log that answers D121, the label, the plane at infinity** (D119–D122). (a) **The update from
|
||||
beta.41**: Help ▸ Check for updates, *Restart to update* with no game running; no terms window. (b) **Cyberpunk
|
||||
2077 with FSR upscaling** (FSR 3 or 4, with or without FSR frame generation — as it was when the upscaler read
|
||||
"unknown"): one session of a few minutes of play, then **quit the game from its own menu**. Nothing else is
|
||||
needed: `%LOCALAPPDATA%\FrameLedger\logs\overlay-<pid>-….log` of that session is what is read. If the session
|
||||
now names FSR, say so — nothing in this release should have changed that. (c) **A game that gave one depth
|
||||
plane** — Lies of P, Clair Obscur or Dying Light: The Beast, FSR upscaling, **Advanced metrics on**: the
|
||||
session's Advanced page shows both planes, one of them "∞". If it still shows one, the missing plane is not
|
||||
`FLT_MAX` and the log of (b)'s kind says nothing about it — say so. (d) **A session that changes upscaler** —
|
||||
Dying Light: The Beast as it was (DLSS evaluated, then FSR), or any game switched between DLSS and FSR in its
|
||||
menu during one session: the summary names the one that ran longest, with that one's quality and render size,
|
||||
and says *settings changed during session*. (e) **Any hooked game, ended by quitting it**: its overlay log has
|
||||
lines after the first second — `HOOK_INSTALLED` with a module and a function, `RUNTIME_CENSUS` — and no
|
||||
`PATCH_FAILED`; if there is one, its `a=` number is the reason.
|
||||
**Four sessions were run on 2026-11-12 and read the same morning** (START HERE §What the owner's first four
|
||||
sessions on beta.42 showed): (a) happened — the sessions carry the beta.42 build; (b) read, and D121 answered:
|
||||
the session upscaled with FSR 2.1, built into the game; (c) Lies of P and Dying Light show `cameraNear = ∞`;
|
||||
(e) all four logs are whole and none has a `PATCH_FAILED`. **(d) was not exercised**, and the owner has not
|
||||
said the item passed.
|
||||
41. **beta.43 — the first real games with the two new hooks, and the guard's re-read** (D123–D125). **Not first on
|
||||
a game under the user-mode exception's trial** (D38): a crash there ends the exception for good. (a) **The
|
||||
update from beta.42**: Help ▸ Check for updates, *Restart to update* with no game running; **the terms window
|
||||
shows once, with Privacy Policy 2.17**. (b) **The guard**: over the games played, the Agent's log
|
||||
(`logs\agent-<date>.log`) has no session that ended at a game's launch with `guard=ModuleScanFailed`. If one
|
||||
does, its signal now says which kind — *kept changing while it was read* (four reads were not enough) or *came
|
||||
back incomplete* — say which. (c) **A Streamline game with Advanced metrics on** (Dying Light: The Beast, or
|
||||
Cyberpunk 2077 with DLSS): a session of a few minutes, quit from the game's menu. Its Advanced page shows the
|
||||
Streamline rows — jitter, motion vectors, depth, projection, resets — and the line under the session says
|
||||
*read*. **Read them for sense**: a field of view between about 0.3 and 2.5 rad, an aspect ratio near the
|
||||
screen's, a jitter under 1, planes that are not both zero. Values that make no sense mean the game's struct is
|
||||
not laid out as the one FrameLedger was built against: say so, with the numbers, and do not run further games.
|
||||
(d) **FSR frame generation on** (Cyberpunk 2077 or Lies of P), Advanced metrics on: the page shows the
|
||||
frame-generation rows — on, asynchronous or not, the flags, the rectangle — and the line says *read*. (e) **The
|
||||
three answers of the line**: a game with neither library says *not hooked* for both; a game where it says
|
||||
*hooked — the game did not make the call* for a library the game plainly uses is a finding, not a pass — say
|
||||
which game. (f) **Off means off**: with Advanced metrics off, **start a game afresh** and record a session; it
|
||||
has no Advanced button, and its `logs\overlay-<pid>-….log` has no `HOOK_INSTALLED` line naming `slSetConstants`
|
||||
or `ffxConfigure`. (A game that was already running when a session with the option on was recorded keeps the
|
||||
two patches until it exits — that is by design, and its log will have the lines.) (g) **Nothing else moved**:
|
||||
no crash, no `PATCH_FAILED` in any overlay log, frame rates and the frame-generation factor as on beta.42 for
|
||||
the same game and settings.
|
||||
**What each outcome means, written before the run.** (c) or (d) empty with *not hooked*: the log of that
|
||||
session says why — no `HOOK_INSTALLED` for the function (the library is a 1.x interposer or lacks the export)
|
||||
or a `PATCH_FAILED` (its `a=` number is the reason). Empty with *hooked — the game did not make the call*: the
|
||||
game reaches Streamline or FSR by a way that does not pass the export — beta.44's plan needs to know. A crash,
|
||||
or a game that will not start: say so at once; *Disable all hooking* (Settings ▸ Capture) and switching Advanced
|
||||
metrics off are the two ways to run without the hooks, and which of them cured it says which hook it was.
|
||||
**Nine sessions were run on 2026-11-12 and read the same afternoon** ([`handoff/history/0.1.0-beta.43.md`](handoff/history/0.1.0-beta.43.md) §What the owner's nine
|
||||
sessions on beta.43 showed): (a) happened — Privacy Policy 2.17 accepted once, at the update; (b) held — no
|
||||
`guard=ModuleScanFailed` since the update; (c) read on Phantom Blade Zero, Cyberpunk 2077 and Hogwarts Legacy,
|
||||
every value sane but one: **Cyberpunk 2077 gives its field of view in degrees** (51–90), and the page labels it
|
||||
radians — the struct is laid out as expected, the label is wrong; (d) read on Lies of P, **not exercised through
|
||||
the FidelityFX 2.3 loader**; (e) the three answers were each seen and none is a finding, **a game with neither
|
||||
library was not run**; (f) held on Lies of P started afresh; (g) no `PATCH_FAILED`, no fault, frame rates as
|
||||
before — Lies of P's 35 s end with exit code 3 is, by the owner, the game's own crash after a shader failed to
|
||||
compile, and Hogwarts Legacy's fault at exit is in Windows' log six times since 2026-11-06, hooked or not.
|
||||
**Judged passed 2026-11-12, on the owner's word to go on if it did**; the two parts in bold stay open.
|
||||
42. **beta.44 — the two questions about a feature in real games, and what the nine sessions found, fixed**
|
||||
(D126–D128). **Not first on a game under the user-mode exception's trial** (D38): a crash there ends the
|
||||
exception for good. (a) **The update from beta.43**: Help ▸ Check for updates, *Restart to update* with no game
|
||||
running; **the terms window shows once, with Privacy Policy 2.18**. (b) **Cyberpunk 2077 with Advanced metrics
|
||||
on**, a session of a minute or two: its Advanced page shows the field of view as the game gives it —
|
||||
`51.0055 – 90`, or whatever the game's setting makes it — with a line under it that says *Not radians*, and no
|
||||
"rad" beside the number. The two sessions of 2026-11-12 keep `51.0055 – 90 rad (2922.4° – 5156.6°)`: they were
|
||||
stored that way. (c) **Any Streamline game with Advanced metrics on** (Phantom Blade Zero, Hogwarts Legacy,
|
||||
Cyberpunk 2077): the line under the session has one more sentence — *Which version each Streamline feature is:
|
||||
…. What each requires: ….* — and for each it says *read*, or *hooked - the game asks this while it starts, and
|
||||
did not ask again after FrameLedger attached*. **The second is the expected answer** for a game that was already
|
||||
past its start-up when FrameLedger attached; it is not a failure. If it says *read*: the page lists features by
|
||||
NVIDIA's names (`kFeatureDLSS`, `kFeatureDLSS_G`) with versions and requirements — check that the driver version
|
||||
it shows as *detected* is the installed driver's, and that Streamline's version is the game's `sl.*.dll` file
|
||||
version. (d) **Which games, if any, say *read***: nothing to set up — FrameLedger attaches as soon as it sees the
|
||||
game — but say, for each Streamline game run, which of the two answers each call got. Hogwarts Legacy loaded its
|
||||
Streamline library some six seconds after FrameLedger attached on 2026-11-12, so it is the likeliest to say
|
||||
*read*; Phantom Blade Zero and Cyberpunk 2077 had it loaded already. (e) **A game with no Streamline** (Lies of P, Kingdom Come:
|
||||
Deliverance II): both say *not hooked*. (f) **Off means off**: with Advanced metrics off, **start a game
|
||||
afresh** and record a session; its `logs\overlay-<pid>-….log` has no `HOOK_INSTALLED` line naming
|
||||
`slGetFeatureVersion`, `slGetFeatureRequirements`, `slSetConstants` or `ffxConfigure`. (g) **Nothing else
|
||||
moved**: no crash, no `PATCH_FAILED` in any overlay log, frame rates and the frame-generation factor as on
|
||||
beta.43 for the same game and settings. With Advanced metrics on, a Streamline game's log has
|
||||
`slGetFeatureVersion` and `slGetFeatureRequirements` as its **first two** Streamline `HOOK_INSTALLED` lines.
|
||||
(h) **The count of early ends** (D126) is not something to provoke: if a game whose hooking you switched back
|
||||
on ends once within a minute of starting, hooking stays on; a second such end switches it off, as before.
|
||||
**What each outcome means, written before the run.** (c) *not hooked* on a Streamline game: the log says why —
|
||||
no `HOOK_INSTALLED` for the function (a 1.x interposer, or the export is missing) or a `PATCH_FAILED`. (c) and
|
||||
(d) both *did not ask again* on every game: the calls are made before any attach can be in — then these two
|
||||
hooks give nothing in attach mode, and whether they are worth their two patches is the owner's to say before
|
||||
train C. *Read* with numbers that make no sense (a driver version that is not the installed one, a feature
|
||||
named `feature <number>`): say so with the numbers — an id with no name only means NVIDIA added a feature this
|
||||
build does not know. A crash, or a game that will not start: say so at once; *Disable all hooking*
|
||||
(Settings ▸ Capture) and switching Advanced metrics off are the two ways to run without the hooks, and which
|
||||
of them cured it says which hook it was.
|
||||
**Eight sessions were run on 2026-11-12 and read the same evening** ([`handoff/history/0.1.0-beta.44.md`](handoff/history/0.1.0-beta.44.md) §What the owner's
|
||||
eight sessions on beta.44 showed): (a) happened — Privacy Policy 2.18 accepted once; (b) held — Cyberpunk 2077 reads
|
||||
`51.0055 – 90` and *not radians*; (c), (d) **both questions read on five games, six sessions of six** — the
|
||||
expected answer was the other one — with the driver, Windows and NGX versions agreeing with the PC, and one
|
||||
reading no file could give: frame generation's Streamline plugin is 2.14.16 on three games that ship an older
|
||||
one; Cyberpunk's version question was *not asked again*; (e) held on Kingdom Come: Deliverance II; (g) no
|
||||
`PATCH_FAILED`, no fault, the two rows first; (h) seen for real — Valor Mortis's second early end switched
|
||||
hooking off, the owner switched it on, the count is 0. **(f) was not exercised.** Valor Mortis crashed 51 s
|
||||
into a hooked session exactly as on beta.40, and Black Myth: Wukong faults in Steam's crash handler at every
|
||||
exit: neither is explained, and neither began with this release. **Taken as passed on the owner's "update and
|
||||
go on", 2026-11-12**; (f) and the two comparisons stay open.
|
||||
43. **beta.45 — six more Streamline calls in real games** (D129–D131). **Not first on a game under the user-mode
|
||||
exception's trial** (D38): a crash there ends the exception for good. (a) **The update from beta.44**: Help ▸
|
||||
Check for updates, *Restart to update* with no game running; **the terms window shows once, with Privacy Policy
|
||||
2.19**. (b) **Any Streamline game with Advanced metrics on** (Phantom Blade Zero, Clair Obscur, Valor Mortis,
|
||||
Black Myth: Wukong, Cyberpunk 2077), a session of a few minutes that includes **changing a graphics setting
|
||||
that touches frame generation or DLSS** if the game lets you: its Advanced page has two more tables —
|
||||
*Whether Streamline says each feature is supported, and loaded* (`kFeatureDLSS_G · slIsFeatureSupported` =
|
||||
`eOk`, `· slIsFeatureLoaded` = *On* or *Off*) and *Each feature switched on or off, its resources allocated and
|
||||
freed, Streamline shut down* — and the line under the session ends with one more sentence: *Streamline's other
|
||||
calls - read: …; hooked, the game did not make the call: …; not hooked: ….* Say, for each game, which calls
|
||||
are in which group. (c) **Check one number you can know**: a feature the game has switched off in its own menu
|
||||
and that reads *On* under `slIsFeatureLoaded`, or the reverse, is worth saying — "loaded" is Streamline's word
|
||||
for the plugin being in, not for the feature being in use, and what a real game does here is not known.
|
||||
(d) **A game with no Streamline** (Lies of P, Kingdom Come: Deliverance II): all six are in *not hooked*.
|
||||
(e) **The way out**: close each game the way you usually do. **Black Myth: Wukong and Hogwarts Legacy already
|
||||
fault while closing** (Steam's `crashhandler64.dll`, `_nvngx.dll`); what matters is whether anything is
|
||||
*different* — a new fault in Windows' application log (Event Viewer ▸ Windows Logs ▸ Application, *Application
|
||||
Error*) naming another module, a game that hangs on exit, a game that used to close cleanly and does not.
|
||||
(f) **Off means off**: with Advanced metrics off, **start a game afresh** and record a session; its
|
||||
`logs\overlay-<pid>-….log` has no `HOOK_INSTALLED` line naming any of the ten: `slSetConstants`, `ffxConfigure`,
|
||||
`slGetFeatureVersion`, `slGetFeatureRequirements`, `slIsFeatureSupported`, `slIsFeatureLoaded`,
|
||||
`slSetFeatureLoaded`, `slAllocateResources`, `slFreeResources`, `slShutdown`. (This is item 42 (f), which was
|
||||
not run.) (g) **Nothing else moved**: no crash, no `PATCH_FAILED` in any overlay log, frame rates and the
|
||||
frame-generation factor as on beta.44 for the same game and settings; with Advanced metrics on the log ends
|
||||
with an `UNHOOK_RESTORED` line for each patch and no "the stop was still writing". (h) **The Advanced page's
|
||||
catalog**: *The preferences the game started Streamline with* reads *Not read: the game makes this call once,
|
||||
before FrameLedger is inside it*.
|
||||
**What each outcome means, written before the run.** A call in *hooked, the game did not make the call* in
|
||||
every game: the game does that before FrameLedger is in, or never — then that hook gives nothing in attach
|
||||
mode, and whether it keeps its patch is the owner's to say. `slIsFeatureSupported` with a result that is not
|
||||
`eOk` for a feature the game then uses: say which — the row is Streamline's answer to the game, and the game
|
||||
may have asked about another graphics card. A count of `≥ 15`: the game allocates or frees every few frames;
|
||||
the number stopped, nothing is wrong. *Not hooked* on a Streamline game: the log says why — no `HOOK_INSTALLED`
|
||||
for the function (a 1.x interposer, or the export is missing) or a `PATCH_FAILED`. **A new fault on the way
|
||||
out, a hang on exit, or a crash in play**: say so at once, with the game; switching Advanced metrics off and
|
||||
starting the game afresh runs it without any of the ten hooks, and if that cures it the hook is one of the
|
||||
six new ones or the four before — the overlay log's last `HOOK_INSTALLED` lines and Windows' fault entry say
|
||||
which is nearer. A game that will not start at all: *Disable all hooking* (Settings ▸ Capture).
|
||||
**Seven sessions were run on 2026-11-13 and read the same day** ([`handoff/history/0.1.0-beta.45.md`](handoff/history/0.1.0-beta.45.md) §What the owner's
|
||||
seven sessions on beta.45 showed): (a) happened — Privacy Policy 2.19 accepted once; (b) five Streamline games, six sessions —
|
||||
`slIsFeatureSupported` read in all, `slIsFeatureLoaded` in three games, `slSetFeatureLoaded` in two,
|
||||
`slFreeResources` and `slShutdown` once in one game each, **`slAllocateResources` in none**; (d) held on Kingdom
|
||||
Come: Deliverance II; (e) **nothing different**: Hogwarts Legacy and Black Myth: Wukong fault while closing in
|
||||
the same module at the same offset as before, the other four games leave no fault; (g) no `PATCH_FAILED`, no
|
||||
fault counted, rates as before — and no session was stopped while its game ran, so the part about
|
||||
`UNHOOK_RESTORED` lines was not exercised and was worded wrongly. **(f) was not exercised; (c) and (h) are the
|
||||
owner's to say.** Taken as passed on the owner's "check the logs and go on", 2026-11-13; (f) stays open.
|
||||
`slAllocateResources` keeps its patch (D135, the same day).
|
||||
44. **beta.46 — hooks in and out under one stop of the threads, in real games** (D134). **Not first on a game under
|
||||
the user-mode exception's trial** (D38): a crash there ends the exception for good. (a) **The update from
|
||||
beta.45**: Help ▸ Check for updates, *Restart to update* with no game running; **the terms window does not
|
||||
show** (nothing new is read). (b) **Any Streamline game with Advanced metrics on** (Hogwarts Legacy first — its
|
||||
thirteen patches took 2.8 s on beta.45 — then Phantom Blade Zero, Cyberpunk 2077, Dying Light: The Beast, Black
|
||||
Myth: Wukong): play as usual and close the game. Its `logs\overlay-<pid>-….log` has `PATCH_BATCH install`
|
||||
lines, and the `sl.interposer.dll` `HOOK_INSTALLED` lines above each carry **the same time** to the thousandth
|
||||
of a second, not times 0.06–0.2 s apart. Say the `a=` of each `PATCH_BATCH` line: it is the microseconds the
|
||||
game's threads were stopped for that batch. (c) **How the game's start feels**: no worse than on beta.45 — the
|
||||
hitching while a game with Streamline starts should, if anything, be shorter. (d) **A stop while the game
|
||||
runs**, which no session has exercised since beta.43: with a game running and being recorded, switch *Disable
|
||||
all hooking* on in Settings ▸ Capture; the part inside the game stops at its next safety scan, within 30
|
||||
seconds. The game must go on running without a freeze of seconds; the log then has `STOP`, an `UNHOOK_RESTORED`
|
||||
line for every patch, one `PATCH_BATCH restore` line and `STOP_FLUSHED … a=1`. Switch it back off afterwards. (e) **A game with no
|
||||
Streamline** (Kingdom Come: Deliverance II, Lies of P): its FSR rows are under `PATCH_BATCH` lines as well, and
|
||||
the session reads as before. (f) **Nothing else moved**: no crash, no `PATCH_FAILED`, no `UNHOOK_DECLINED`
|
||||
unless another overlay is running, the same hooks in `HOOK_INSTALLED` as on beta.45 for the same game, frame
|
||||
rates and the frame-generation factor as before, the Advanced rows as before. (g) **Off means off** (item 43
|
||||
(f), never run): with Advanced metrics off, start a game afresh; no `HOOK_INSTALLED` line names any of the ten
|
||||
Advanced-only calls.
|
||||
**What each outcome means, written before the run.** A `PATCH_BATCH install` whose `a=` is about what one
|
||||
patch cost on beta.45 (60 000–220 000) is the expected answer: one stop of the threads. An `a=` of a second or
|
||||
more: one stop is long in that game — say which game and the number; it is still one where there were thirteen,
|
||||
but it is what would decide whether batches need a ceiling. `HOOK_INSTALLED` lines of one batch with different
|
||||
times: the batch fell back to one patch at a time — the log then also has a `PATCH_FAILED` — say so with the
|
||||
log. A game that hitches at its start as it did not on beta.45, or freezes at (d): say so at once, with the
|
||||
game; 0.1.0-beta.45 is the build without this change. A hook that was in on beta.45 and is not on beta.46
|
||||
(compare the `HOOK_INSTALLED` lines), or a session that reads *not hooked* where it read *read*: the batch lost
|
||||
a patch — the log's `PATCH_FAILED` line names it and why. A crash in play or at exit that is new: say so at
|
||||
once; *Disable all hooking* runs the game with nothing patched after the start.
|
||||
**Five sessions were run on 2026-11-13 and read the same day** ([`handoff/history/0.1.0-beta.46.md`](handoff/history/0.1.0-beta.46.md)
|
||||
§What the owner's five sessions on beta.46 showed): (a) held — the terms window did not show; (b) five Streamline games — every batch's lines carry one
|
||||
time; `a=` is 81 417–261 920 for sixteen of the eighteen batches, **1 260 835 for Hogwarts Legacy's thirteen
|
||||
and 608 700 for three of Cyberpunk 2077's**, neither explained — and the sentence above about a fallback is
|
||||
wrong: a batch finished one patch at a time leaves no line unless a patch fails for good, so the log cannot say
|
||||
which of the two a long `a=` was; (f) held — no crash in play, no `PATCH_FAILED`, no `UNHOOK_DECLINED`, the
|
||||
same hooks as on beta.45, rates and factor as before, the two known faults on the way out at their old offsets.
|
||||
**(d), (e) and (g) were not exercised; (c) is the owner's to say.** Not passed: (d) is the half of this release
|
||||
that no real game has run.
|
||||
**2026-11-14, three more sessions (203–205), read the same morning — (d) is still not exercised.** *Disable all
|
||||
hooking* was switched on **before** the games were started, not while one was being recorded: Cyberpunk 2077
|
||||
(06:34) and Phantom Blade Zero (06:38) were each recorded as `RefusedKillSwitch` — tier 2, nothing injected, no
|
||||
overlay log for either process, which is FR-2.4 doing what it says and not what (d) asks. With the switch off
|
||||
again, Phantom Blade Zero (06:46, 518 s) was hooked from its start to its exit: twenty-two patches under one
|
||||
batch of 84 ms and ray tracing's two under one of 81 ms, ×3.0 at 89 → 268, no fault, a clean exit — and **no
|
||||
`STOP`, no `UNHOOK_RESTORED`, no `PATCH_BATCH restore` line**, because nothing stopped it while it ran. Windows'
|
||||
application log has no fault since 06:30. **How (d) is run**: start the game with the switch **off** and wait
|
||||
until FrameLedger shows it recording; **then**, with the game still running, switch *Disable all hooking* on;
|
||||
play on for half a minute; switch it off; close the game.
|
||||
**2026-11-14, the second try (sessions 206 and 207, Phantom Blade Zero): (d) held, twice.** The game started with
|
||||
the switch off and was being recorded; the switch was turned on while it ran. Each log has `STOP` at the next
|
||||
safety scan, an `UNHOOK_RESTORED` line for every one of the twenty-nine patches at one time, one `PATCH_BATCH
|
||||
restore` — `a=83309` and `a=85578`, `b=0x1d` — and `STOP_FLUSHED … a=1`; no `UNHOOK_DECLINED`. Both sessions
|
||||
ended `KillSwitchEngaged`, tier 1, no fault, nothing dropped; the game ran on for three and four minutes and
|
||||
closed with nothing in Windows' application log. Whether a hitch was felt at the stop is the owner's to say.
|
||||
**Taken as passed for what 0.1.0-beta.47 was held on** — (a), (b), (d), (f). **(e) and (g) were never run**: they
|
||||
are (f) and (g) of item 45.
|
||||
45. **beta.47 — NVIDIA's latency report, read inside a game** (D132, D136, D138–D141). **Cyberpunk 2077 first**
|
||||
(D136), **and not first on a game under the user-mode exception's trial** (D38): a crash there ends the exception for good.
|
||||
This is the first release in which the part inside a game *makes a call of its own* — into the graphics driver,
|
||||
about once a second, on the game's presenting thread — so read (a) before (b). (a) **The update**: Help ▸ Check
|
||||
for updates, *Restart to update* with no game running; **the terms window shows once, with Privacy Policy 2.20
|
||||
and Disclaimer 2.16** — the Disclaimer's §2 has a new paragraph, *One call it makes itself, into the graphics
|
||||
driver*. Settings ▸ *Advanced metrics* says the same in its description. (b) **Cyberpunk 2077, Advanced metrics
|
||||
on, frame generation OFF, Reflex on in the game's menu**, five minutes of play, then close the game as usual.
|
||||
Its `logs\overlay-<pid>-….log` has `LATENCY` lines: *reading the driver's latency report*, and two more with
|
||||
the end of two paths — `…\System32\nvapi64.dll` and `…\nvapi64_impl.dll`. On the Advanced page, the session
|
||||
has a group **Latency**: the table *What the driver's low-latency state is* (five rows by NVIDIA's names, and
|
||||
`fgMultiplier`) and, in the chart's list, *Latency per frame* with seven lines. The line under the session ends
|
||||
with *NVIDIA's latency report, which FrameLedger asks the graphics driver for inside the game: read.* Say the
|
||||
*total* line's usual value, and **whether the game felt any different with the option on** — a hitch once a
|
||||
second is the thing to look for. (c) **The same with frame generation ON** (DLSS ×2 or more): the driver's
|
||||
pacer is another thread, and this is the arrangement the probe could not make. (d) **Reflex switched off in the
|
||||
game's menu**, if the game lets you: say what the line reads — *read* or *asked, and the driver reported no
|
||||
frame*; both are possible and neither is wrong. (e) **Only after (b) and (c) are clean, a second game** that
|
||||
uses Reflex through Streamline (Phantom Blade Zero, Clair Obscur, Black Myth: Wukong, Hogwarts Legacy). (f) **A
|
||||
game that is not Direct3D 12 or has no NVIDIA library** (Kingdom Come: Deliverance II, Lies of P): the line
|
||||
reads *not read*, with which of the two. (g) **Off means off**: with Advanced metrics off, start a game afresh;
|
||||
its log has no `LATENCY` line. (h) **Nothing else moved**: no fault counted, frame rates and the
|
||||
frame-generation factor as before, the game closes as it did.
|
||||
**What each outcome means, written before the run.** *Read*, with a total of a few to a few tens of
|
||||
milliseconds that moves with the frame rate: route D works in a real game; what comes next — more titles, the
|
||||
session summary — is the owner's to say. *Asked, and the driver reported no frame* in a game whose Reflex is
|
||||
on: the driver has a report for another object than the device FrameLedger holds; nothing is harmed, and the
|
||||
title is not readable this way. *Not read — the game has not loaded nvapi64.dll* in Cyberpunk 2077: what its
|
||||
files said did not happen at run time; another title is tried. *Stopped — a call took N µs*: **one call of a few
|
||||
thousand microseconds, once, is most likely a pause of the game's thread on a busy PC** (`spike-notes` §31, *A
|
||||
run on a busy PC*) — start the game again and see whether it repeats; if it repeats, or N is ten thousand or
|
||||
more, the driver holds the call in that game and **route D stops for it** — say so with the number. *Stopped — a
|
||||
call into the driver faulted*, or a fault counted in the session: **route D stops** (the commitment of §30) —
|
||||
say so at once, with the log. **A game that freezes** with a `LATENCY` line saying a call has not returned, or
|
||||
that freezes at all with the option on and not with it off: close it, say so at once; Advanced metrics off is
|
||||
the way to play it, and route D ends. **A hitch once a second** with the option on that is not there with it
|
||||
off: say so at once — the two-millisecond latch did not catch what a player can feel. **The game closing by
|
||||
itself a second or two after it starts, only with the option on** (Windows' Application log: exception
|
||||
`0xc0000409`): a Control Flow Guard refusal of the call — say so at once with the entry; that game enforces
|
||||
what the probe could only check for this driver. Spans that make no sense — a part larger than the total, a
|
||||
line that is always zero: say which; they are the driver's numbers and are shown as it reported them.
|
||||
**Three sessions were run on 2026-11-14 and read the same morning — in Phantom Blade Zero, not Cyberpunk 2077**
|
||||
(sessions 208–210, Direct3D 12, Streamline 2.14.1). **The read works in a real game.** (a) held: the terms were
|
||||
accepted once, Disclaimer 2.16 and Privacy Policy 2.20. In all three the overlay log has `LATENCY … reading the
|
||||
driver's latency report` four to five seconds after the attach, with `C:\WINDOWS\SYSTEM32\nvapi64.dll` and
|
||||
`…\nvapi64_impl.dll` on the two lines after it, and **no later `LATENCY` line**: no error, no slow call, no
|
||||
fault, no stall. Each session's line reads *read*, and the slowest call into the driver was **24, 20 and 45 µs**.
|
||||
Frame generation on: session 208, ×3.0 at 85 → 256 — and the driver's own `fgMultiplier` read 3. Off: sessions
|
||||
209 and 210, multiplier 1. Seven series in each, 227 / 24 / 823 points: 90 %, 62 % and 98 % of the Agent's own
|
||||
once-a-second samples (the short session spent its first seconds before the module was found). With frame
|
||||
generation ×3: total 23.4 ms, simulation 4.4, render submit 10.3, present 0.7, driver 10.9, OS queue 13.0, GPU
|
||||
render 11.5 (means). The driver's switches: `bLowLatencyMode`, `bUseGameSleep` and `bFullscreenIFlip` *on at
|
||||
times, off at others*; `bFsVrr` and `bCplVsyncOn` *off* — so in a game the low-latency switch does read on,
|
||||
which it never did for the probe. No fault counted, nothing dropped, a normal exit each time, nothing about the
|
||||
game in Windows' application log; rates as on beta.46 for the same game.
|
||||
**One outcome the list above names: a part larger than the total.** *GPU render* reads 16.4 ms where the *total*
|
||||
reads 5.4 ms (session 209), and about equals it in session 210 (16.0 against 15.9 ms). The span is the driver's
|
||||
`gpuRenderStartTime` to `gpuRenderEndTime`, and in this game that start lies **before** the frame's own
|
||||
simulation start: it reads like the time between two frames' GPU ends, idle time included — a reading, not a
|
||||
fact; the driver has a field of its own for the active time (`gpuActiveRenderTimeUs`), which FrameLedger does
|
||||
not read. It is shown as the driver reported it. The spans also overlap — render submit, driver and OS queue
|
||||
together are longer than the total — so they are not parts that add up, and the page does not say they are.
|
||||
**Not run**: Cyberpunk 2077, which (b) and (c) name; (d) Reflex off in the game's menu; (f) a game that is not
|
||||
Direct3D 12 or has no NVIDIA library; (g) off means off. **Not said**: whether the game felt any different with
|
||||
the option on. Not passed as written; what the three sessions were run for is answered.
|
||||
**Five more sessions the same morning (211–215), read at 09:15: Cyberpunk 2077 twice, and three games the
|
||||
read must leave alone.** (b), (c) **Cyberpunk 2077** (Streamline 2.14.1, DLSS): session 211 with frame
|
||||
generation ×2.0 for 42 % of it (166 → 330) and menus for the rest, session 212 without, at 238 FPS. The module
|
||||
was found 4.8 s and 2.6 s after the attach, in the same two files; each session's line reads *read*; **the
|
||||
slowest call took 34 and 65 µs**; no later `LATENCY` line. 190 of 195 and 429 of 438 samples carry a report.
|
||||
The total: 13.5 ms while frames were generated, 4.1 ms in the menus, 11.7 ms at 238 FPS without generation.
|
||||
**GPU render is 2.7 ms there and never longer than the total** (0 of 429 samples; 1 of 190) — so what the
|
||||
three sessions above showed is Phantom Blade Zero's, not the route's. `bLowLatencyMode` *on* throughout. The
|
||||
table's `fgMultiplier` reads **1 in the session that held ×2 for 105 seconds**: the row keeps the last value
|
||||
read, and that session ended in a menu — a row that lists what was seen would not mislead. D137's first
|
||||
Cyberpunk batches: eight of them, 85–221 ms, every one `install` in one apply; beta.46's 0.61 s did not recur.
|
||||
(f) **Not Direct3D 12**: Crown & Coin (213) and Psycho-Sleuth (214), both Direct3D 11 — one `LATENCY no
|
||||
Direct3D 12 device` line each, nothing after it, the session's line reads *not read — not Direct3D 12*.
|
||||
**Direct3D 12 with no NVIDIA library**: Dread Fields (215) — `the game has not loaded nvapi64.dll`, said once,
|
||||
*not read*. The three ran at the same time and were recorded apart. (h) held in all five: no fault counted,
|
||||
nothing dropped, normal exits, nothing in Windows' application log.
|
||||
**A correction to the paragraph above**: the Agent's samples are **1.32 s apart, not one second** (the `t_ms`
|
||||
series; so in every session looked at back to beta.42, while `sensor_blobs.hz` says 1.0 — not looked into),
|
||||
so the shares are 227 of 258, 24 of 39 and 823 of 846 samples, and the gaps are the first seconds of a session.
|
||||
**The owner's answer on the *GPU render* line (2026-11-14): read the driver's active time** — planned as one
|
||||
train with what else is open. **Left of this item**: (d) Reflex off in the game's menu, (g) off means off, and
|
||||
the owner's word on how the games felt; the owner runs what is left once, with that train's release.
|
||||
**They are (d), (e) and (g) of item 46.**
|
||||
46. **beta.48 — the driver's own GPU times, the multipliers seen, samples a second apart; and what item 45 left**
|
||||
(D142–D146). **One batch**, as the owner asked: any Direct3D 12 games that use Reflex, as many as wanted, with
|
||||
*Advanced metrics* on — **not first on a game under the user-mode exception's trial** (D38). Then say *check*;
|
||||
the sessions are read from a copy of the ledger and the logs.
|
||||
(a) **The update** shows the terms window once, with **Privacy Policy 2.21 and Disclaimer 2.17**.
|
||||
(b) **Phantom Blade Zero and Cyberpunk 2077 again**, a few minutes of play each: on the Advanced page, under
|
||||
**Latency**, a second chart — *the graphics card's time per frame, as the driver works it out* — with two lines,
|
||||
*GPU active render* and *GPU frame time*; and the old line reads *GPU render, start to end (idle time included)*.
|
||||
(c) **A session with both a menu and frame generation**: the table's `fgMultiplier` row lists both — *1, 2*, or
|
||||
*1, 3* — not the last one.
|
||||
(d) **Reflex switched off in a game's menu**, if a game lets you (item 45 (d)): say what the session's line reads.
|
||||
(e) **Off means off** (item 45 (g)): switch *Advanced metrics* off, start a game afresh, play a minute, close
|
||||
it; switch it back on afterwards.
|
||||
(f) **Any other games of the batch** — Clair Obscur, Black Myth: Wukong, Hogwarts Legacy, Dread Fields, a
|
||||
Direct3D 11 game: nothing to do but play and close them.
|
||||
(g) **How the games felt** with the option on — a hitch once a second is the thing to look for; nobody but the
|
||||
player can say it.
|
||||
**Read from the ledger, nothing for the owner to do**: the samples of every session are one second apart, not
|
||||
1.32 s, and `hz` says what they were.
|
||||
**What each outcome means, written before the run.** *The two lines are there, and active render is shorter
|
||||
than GPU render*: D142 did what it was for; in Phantom Blade Zero the reading of 2026-11-14 expects *GPU frame
|
||||
time* near the 16 ms the old line showed, and *active render* well under it — **if active render is as long as
|
||||
the old line there, that reading was wrong**, and the span is long for another reason: say the numbers. *The
|
||||
second chart is not there, and the seven lines are*: the driver gave zero for both figures in every frame —
|
||||
nothing is wrong with the read, and the texts already say a driver may give neither; say which game. *One line
|
||||
and not the other*: the same, for one figure. *Active render longer than GPU render, start to end*: they are the
|
||||
driver's numbers and are shown as reported — say which game and by how much. *`fgMultiplier` shows one value in
|
||||
a session that had both*: the driver's status did not change with the menu in that game, or the mask is wrong —
|
||||
say the game; the log's `LATENCY` lines and the frame-generation mix of the session tell the two apart. *Samples
|
||||
still 1.3 s apart*: the period is not kept — the poll takes longer than the interval, or the change is not in
|
||||
the build: stop and say so. *Samples a second apart and the Agent's processor use visibly higher*: a poll that
|
||||
took a third of 1.32 s now takes a third of a second — say so; where that time goes is not established
|
||||
(§Left open). *(d) reads "read"*: the driver reports frames with the game's Reflex off — both that and *asked,
|
||||
and the driver reported no frame* are possible and neither is wrong. *(e) the log has a `LATENCY` line*: off
|
||||
does not mean off — say so at once, with the log. **A fault, a freeze, a game closing by itself, a hitch every
|
||||
second, or a session that says *stopped***: as item 45 says for each — say so at once.
|
||||
**Run 2026-11-14, 12:49–14:12, and read the same afternoon** from a copy of the ledger and the logs: ten
|
||||
sessions on beta.48 — Phantom Blade Zero seven times (217, 219, 220, 223–226), Cyberpunk 2077 three times (218,
|
||||
221, 222). Every one tier 1, exit code 0, no fault counted, nothing dropped; nothing in Windows' application
|
||||
log. (Session 216, an hour of Phantom Blade Zero, was still beta.47 — it ran while the release was cut — and
|
||||
is 1.32 s apart like the ones before it.)
|
||||
**The samples are a second apart**: the median gap is 996–1002 ms in all ten (session 223: 2 294 of 2 394 gaps
|
||||
round to 1.00 s, the rest lie between 0.80 and 1.27 s), and `hz` reads 1.000–1.017.
|
||||
(a) `legal_acceptance` holds Privacy Policy 2.21 and Disclaimer 2.17, accepted at 12:48:40.
|
||||
(b) **Both figures were given by both games, in every frame report**: in the nine sessions with the option on,
|
||||
every sample that has a *GPU render* span has both (3 834 of 3 834). **Phantom Blade Zero is what the reading of
|
||||
2026-11-14 expected**: at 60 FPS (217) the span's median is 16.39 ms, *GPU frame time* 16.67 ms and *GPU active
|
||||
render* **9.59 ms**; in the menu (224) 16.39 / 16.67 / **2.77**; at 91 FPS (225) 11.49 / 11.79 / 10.05; with
|
||||
frame generation ×5 (223) 15.67 / 15.88 / 14.08. So in that game the span is the time from one frame to the
|
||||
next less a third of a millisecond, whatever the card did in it, and active render is never longer than it
|
||||
(0 of 3 406 samples). **Cyberpunk 2077 is the outcome written above as "active render longer than GPU render,
|
||||
start to end"**: without frame generation it is longer at 157 of 158 samples (218: medians 3.17 against
|
||||
2.79 ms, frame time 6.02) and at 48 of 48 (221: 2.03 against 1.82, frame time 2.37); with frame generation ×2
|
||||
(222) it is shorter at all 222 (4.85 against 6.35, frame time 6.67). Shown as reported. **Why is not
|
||||
established**, and two things could do it: the two are averages over different frames — the span over every
|
||||
summed frame, one of no length included (the smallest mean span of a sample there is 0.5 µs, the smallest active
|
||||
time 0.29 ms), active render over the frames that gave one — or the driver counts work the two marks do not
|
||||
enclose. The ledger cannot tell them apart; a count of the frames whose span has no length would.
|
||||
(c) `fgMultiplier` reads **1, 2** in Cyberpunk 2077 (222: ×2.0 for 69 % of it), **1, 5** in Phantom Blade Zero
|
||||
(220: ×5.0 for 71 %, 30 → 151 FPS; 223: ×5.0 for 95 %, 63 → 316) and **1** in the seven sessions that generated
|
||||
nothing.
|
||||
(d) **Session 221** (Cyberpunk 2077, 59 s of menus at 421 FPS) is the only Cyberpunk session whose
|
||||
`bLowLatencyMode` reads *on and off* — 218 and 222 read *on*, as 211 and 212 did — and is taken to be the one
|
||||
where Reflex was switched off; the owner has not said which it was. Its line reads *read*, 48 of 57 samples
|
||||
carry a report, every one from the first on, and the slowest call took 19 µs: the driver goes on reporting
|
||||
frames.
|
||||
(e) **Off means off, on a real game for the first time**: session 226 (`telemetry.advanced` 0) has no
|
||||
`session_advanced` row and 19 series where the others have 240; its log has ten hooks, none of the ones
|
||||
Advanced metrics adds, and **no `LATENCY` line**. The setting was still off when the ledger was copied.
|
||||
(f) No other game was in the batch.
|
||||
**The read itself**: one `reading the driver's latency report` line a session, 1.4–6.7 s after the attach, in
|
||||
the same two files, and none after it; the slowest call of a session 18–123 µs; no latch. The install batches
|
||||
took 75–191 ms, every one `install`.
|
||||
**Samples with no report**: after a session's first report, 0.4–7.3 % of its samples carry none (1 of 223 in
|
||||
222; 134 of 2 377 in 223, minutes of four in five there). They are not the sensor library's ticks (25 of the 134
|
||||
fall on one, 24 just after one). What the code says, not measured: the watchdog ticks once a second and arms a
|
||||
read when a second has passed since the last arm, so a tick that comes a moment early waits for the next one —
|
||||
the reads are a second apart or two, the samples exactly one. Nothing is lost by it; a sample shows a gap.
|
||||
(g) **The owner's answer, asked whether a game hitched once a second with the option on (2026-11-14): no
|
||||
hitch.** What the frames say, in the sessions without frame
|
||||
generation: a frame three times the median of the 120 before it and 8 ms longer comes 0.33 times a second
|
||||
with the option on (225) and 0.32 with it off (226), and such frames do not gather at a period of one second
|
||||
(vector strength 0.05–0.10 where chance gives 0.10–0.20; 217, 218 and 222 the same). Sessions with frame
|
||||
generation cannot be judged that way. **Not seen in the ledger**: what the page looked like, and the Agent's
|
||||
processor use now that a poll comes every second.
|
||||
**Read, and (g) answered**: (a)–(g) each have their answer; ~~whether session 221 was (d) is inferred, and the
|
||||
owner's to say~~ (d) is withdrawn in the next paragraph. The owner has not said the item is passed.
|
||||
**Eight more sessions the same afternoon (227–234), read at once, and three things the owner said.** Still
|
||||
beta.48: Cyberpunk 2077 three times (227 with the option off — no `LATENCY` line, no row; 232 mostly menus; 233
|
||||
five minutes without frame generation), Phantom Blade Zero three times (228, 231, 234), Clair Obscur:
|
||||
Expedition 33 twice (229 with frame generation ×3 for 79 % of it, 230 without). All tier 1, exit code 0, no
|
||||
fault, nothing dropped; samples a second apart; slowest calls 10–29 µs; `fgMultiplier` *1, 3* in 229.
|
||||
**The owner's words**: *Reflex is checked together with frame generation — without frame generation the game
|
||||
does not switch Reflex on*; *a value that reads on and off is the NVIDIA App's override* (the App's page for
|
||||
Phantom Blade Zero: **Low Latency Mode — Ultra**); and a session with Reflex off may be read. **So (d) above
|
||||
is withdrawn as written**: session 221 was not "the one where Reflex was switched off in a menu", and nothing
|
||||
here says what its `bLowLatencyMode` *on and off* was. What the sessions do read: **Clair Obscur without frame
|
||||
generation has `bUseGameSleep` off throughout (230) and with ×3 on and off (229)** — the game's own Reflex
|
||||
goes with its frame generation, as the owner said; **Phantom Blade Zero has `bLowLatencyMode` off throughout
|
||||
in 234**; and in both the read is what it is with Reflex on — one `reading` line, a report at every read, the
|
||||
two new figures in every one. **Cyberpunk 2077 without frame generation again has active render longer than
|
||||
the span** (233: 3.40 against 3.13 ms at 292 of 296 samples), **and its menus do not** (232: 0 of 126; active
|
||||
0.39 ms inside a span of 1.18).
|
||||
**The holes are larger in short sessions**: 11.3 %, 16.2 % and 11.1 % of the samples after the first report
|
||||
in 228, 229 and 231; 6.0 % in 230; 0.8 % in 232. **And "nothing is lost by it", above, was wrong**: it was
|
||||
written on a reading of the Overlay alone. The Agent kept one set of readings until a sample carried it and
|
||||
overwrote it — a publication that landed just after a sample left that sample without, and the set that had
|
||||
waited was replaced at the next return to step (46 of session 223's 134 holes are exactly five samples
|
||||
apart). The Overlay's part is the other half: its ticks were a second and their own work apart, and a tick the
|
||||
loader woke published the read and armed none. Both are mended in 0.1.0-beta.49 (D150); neither is measured in
|
||||
a game yet.
|
||||
47. **beta.49 — whose the difference is in Cyberpunk 2077's GPU times; and the holes** (D148–D151). **One batch,
|
||||
in pairs**: the same game with frame generation off and with it on, *Advanced metrics* on. Reflex is not
|
||||
switched by hand — it goes with frame generation. **Not first on a game under the user-mode exception's
|
||||
trial** (D38). Then say *check*; the logs and a copy of the ledger are read.
|
||||
(a) **The update shows no terms window**: no legal text changed.
|
||||
(b) **Cyberpunk 2077**: six minutes or more of play **without frame generation**, in a scene like session
|
||||
218's; six minutes or more with **frame generation ×2**; two minutes of menus only.
|
||||
(c) **Phantom Blade Zero**: six minutes or more without frame generation — the control — and six or more with.
|
||||
(d) **About eight short sessions**, three minutes each, any Direct3D 12 game that uses Reflex: the step between
|
||||
the game's side and the Agent's is different in every session, and one long session shows one of them.
|
||||
(e) **One session with *Advanced metrics* off**; switch it back on afterwards.
|
||||
(f) **What *Low Latency Mode* is set to for Cyberpunk 2077 in the NVIDIA App** — a word is enough.
|
||||
(g) **How the games felt**, as always.
|
||||
A game closed by itself loses its last batch of counts, under a minute: that is why six minutes and not two.
|
||||
**What each outcome means, written before the run.** The log's `LATENCY_FRAMES` batches each carry the state
|
||||
they belong to, so every one is read as *this state, these counts*.
|
||||
*Cyberpunk without frame generation: nearly every frame that has both is in "active longer than span", and
|
||||
their mean span is near the 2.8 ms the chart shows* — **the difference is the driver's**: it counts work the
|
||||
two marks do not enclose. The numbers are shown as reported and the label "idle time included" is what is
|
||||
wrong for that game: the owner decides its wording.
|
||||
*"Active longer" is a minority whose spans are next to nothing, the rest have active within the span, and
|
||||
spans of no length or of a microsecond are about as many as that minority* — **the difference is ours**: the
|
||||
span's mean is pulled down by frames that have none. The owner decides whether the mean is taken over the
|
||||
frames that have a span.
|
||||
*Both heaps are large, with real spans* — both; the heaps' sums give the like-for-like figure, and it is said
|
||||
with them.
|
||||
*"GPU span absent" is not zero* — those reads published no GPU point at all, and were never in the comparison.
|
||||
*Phantom Blade Zero shows many frames in "active longer"* — suspect the count before the driver: say so.
|
||||
*The counts differ between a batch with `bUseGameSleep` on and one with it off, in the same game* — that is
|
||||
the owner's point, measured: say the two side by side.
|
||||
*The batches say a thousand milliseconds a read and as many periodic ticks as reads, and every session has
|
||||
next to no sample without a report* — D150 did what it was for.
|
||||
*The log says a thousand milliseconds a read and some sessions still lack a report at a steady share of their
|
||||
samples* — the Agent's rule is not the whole of it: say the sessions and the share.
|
||||
*The log says more than a thousand milliseconds a read* — the Overlay is still uneven; the line's tick counts
|
||||
say whether the loader was waking it.
|
||||
*(e) has a `LATENCY` or `LATENCY_FRAMES` line* — off does not mean off: say so at once, with the log.
|
||||
**A fault, a freeze, a game closing by itself, a hitch every second, or a session that says *stopped***: as
|
||||
item 45 says for each — say so at once.
|
||||
**Run 2026-11-14 (sessions 236–245, ten on 0.1.0-beta.49), read the same day** from a copy of the ledger and
|
||||
the Overlay's logs. All ten tier 1, exit code 0, no fault, nothing dropped. Phantom Blade Zero twice (236
|
||||
without frame generation, 1 108 s; 237 with ×2, 811 s), Kingdom Come: Deliverance II (238), Clair Obscur (239),
|
||||
Black Myth: Wukong (240), Lies of P (241, and 245 with the option off), Hogwarts Legacy (242), Dying Light: The
|
||||
Beast (243), Cyberpunk 2077 (244). 239 and 240 ran at the same time, and so did 241, 242 and 243.
|
||||
(a) **No new acceptance row** after the update: the terms window did not appear.
|
||||
(b) **Cyberpunk 2077 was one session of 125 s without frame generation** (374 FPS); ×2 and the menus were not
|
||||
run. It is enough for the question. 88 reads in one state — low-latency mode on, the game sleeping, ×1 — summed
|
||||
5 394 frames: **4 917 in "active longer than span", mean span 1 571 µs, mean active 1 849 µs**; 96 within
|
||||
(3 866 / 3 431 µs); 381 with a span of no length and an active time; none absent, none refused. **So the
|
||||
difference is the driver's**: on frames that have a real span, its active time is 278 µs (18 %) longer than
|
||||
the two marks are apart. A small part is ours as well — 7 % of the frames have a span of no length and pull the
|
||||
span's mean down (the stored means are 1 892 and 2 138 µs). With frame generation on it is not measured on
|
||||
this build (0.1.0-beta.48's means: never longer).
|
||||
(c) **The count is not what is wrong**: in the six other sessions that reported (five games), **not one frame of 129 900** is
|
||||
in "active longer", and no span is absent or of no length. Phantom Blade Zero: without frame generation
|
||||
63 123 frames, span 16.4 ms, active 11.1 ms; with ×2 21 209 frames, span 33.2 ms, active 12.6 ms.
|
||||
(d) **The holes**: in batches of twenty reads or more a read took 1 000.94 ms (236), 997.18 (237), 999.99 (242,
|
||||
244), and up to 1 013 ms in the sessions that shared the PC with another game. Samples without a
|
||||
report: 236 — 40 of 1 106, **39 of them in the first 46**, while the game started; 237 — 36 of 809, in the first 42 and
|
||||
the last two; 244 — 9 of 123, in the first ten. Before, they were spread through a session (0.4–16 %). **D150 did what
|
||||
it was for.** Where two or three games ran at once the holes are blocks in which the game did not present
|
||||
(240: 103 of 477; 242: 80 of 402, 68 of them at its start; 243: 37 of 414; 239: 23 of 184): a read is taken on
|
||||
the presenting thread, so a game that presents nothing is not read — Lies of P's log has sixty reads in 189 s.
|
||||
(e) **Off means off**: session 245 has no `LATENCY` line and no Advanced row.
|
||||
**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. **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
|
||||
low-latency mode **off** (1 062 reads) and switches it on with ×2; Clair Obscur without frame generation has
|
||||
both off and still reports its frames. The logs cannot say whether a game's menu or the NVIDIA App switched
|
||||
the mode on. NVIDIA's own guide makes frame generation need Reflex and not the reverse
|
||||
(`spike-notes` §30, *Added 2026-11-14*). Hogwarts Legacy gave a multiplier of 6 for seventeen reads.
|
||||
(f), (g) **The owner, the same evening: "App reflex off, không khựng"** — *Low Latency Mode* is off in the
|
||||
NVIDIA App, and no hitch. Read with (f) as it was asked, for Cyberpunk 2077: the low-latency mode its 88
|
||||
reads show at a multiplier of 1 is then the game's own Reflex and not the App's override — Reflex on without
|
||||
frame generation, as NVIDIA's guide allows. **Then shown, in two screenshots**: the NVIDIA App's *Program
|
||||
Settings* for Cyberpunk 2077 have *Low Latency Mode* **Off**, set for that program (the rows that follow the
|
||||
global setting read "Global - …"; this one does not); and the game's own *Video* page has **NVIDIA Reflex Low
|
||||
Latency: On**, V-Sync off, borderless at 2560×1440, 378 FPS on the game's counter. So the driver's
|
||||
`bLowLatencyMode` on, at a multiplier of 1, is the game's menu, seen from both sides. **The owner's**: the wording of the two GPU labels — *idle time excluded /
|
||||
included* does not describe a game whose active time is the longer.
|
||||
|
||||
**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 —
|
||||
@@ -1124,71 +562,6 @@ Where each owner decision is recorded — the file and its section, and a label
|
||||
| D96 | [`13_CI_CD.md`](13_CI_CD.md) §C# 15 and the analyses | C# 15 on the main line from beta.37, a construct only where the build, CodeQL and Qodana read it — none of the four yet (Qodana's engine reads none, 2026-11-11), so beta.37 takes .NET 11's API and no syntax; no preview feature |
|
||||
| D97 | [`../legal/ALPHA_NOTICE.md`](../legal/ALPHA_NOTICE.md) | an alpha is "a beta's source built to try a newer version of .NET, at times a prerelease one": EULA 1.7, Disclaimer 2.14 (with a paragraph on Windows and the processor), Alpha notice 1.1, approved with the plan; the App says "a prerelease .NET" only where the runtime is one |
|
||||
| D98 | [`12_BUILD.md`](12_BUILD.md) §The alpha line | alpha.4 is beta.37's source on .NET 11.0.0, and then the alpha line rests until a newer .NET has a preview; a resting alpha tells its user to install the beta |
|
||||
| D99 | [`13_CI_CD.md`](13_CI_CD.md) §Qodana | Qodana for .NET on the Ultimate licence, in two reports from the start: the managed code to the Qodana Cloud project `frameledger`, the C++ to `frameledger-cpp` |
|
||||
| D100 | [`13_CI_CD.md`](13_CI_CD.md) §Qodana | an inspection is switched off where the engine that raised it reads — ReSharper's in `.editorconfig`, the rest in `qodana.yaml` (amends D93); hints are off as a severity; in code loaded into a game only defects are fixed |
|
||||
| D101 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced metrics | "Thông số nâng cao" — Advanced metrics: the option `telemetry.advanced`, off by default, and off means nothing more is read or stored and the navigation item is hidden; everything reachable inside a game follows in stages, four trains A–D |
|
||||
| D102 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced metrics | stored in full with the session, in tables of their own (`machine_profiles`, `session_advanced`, schema 0023) and not in columns of `sessions`; series under `adv.` names with NaN, not −1, for a tick with no reading |
|
||||
| D103 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced metrics | LibreHardwareMonitor's CPU, memory, motherboard and storage groups only when the Agent already runs as administrator with PawnIO — the page links to that setting and never asks; power-supply and fan-controller groups refused, battery deferred |
|
||||
| D104 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced metrics | identifiers are never read: the card's serial number and unique id, a display's EDID, the list of programs that are encoding |
|
||||
| D105 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced metrics | the navigation item is the pane's last; Ctrl+1–5 keep their pages and Ctrl+6 opens it only while the option is on |
|
||||
| D106 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced metrics | a `.partial` chunk of an unknown type with a right checksum is skipped, where it ended the read |
|
||||
| D107 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced metrics | with no game running the Agent reads sensors only while the page is open |
|
||||
| D108 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced metrics | "never call a setter" is a build gate: every `NvAPI_*` call of the bridge is held to a committed list |
|
||||
| D110 | [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) §M16 | the L2 telemetry layer's cost is measured in a real Agent before anything is changed (`tools/agent-cost.ps1`); what to do about the number is asked after |
|
||||
| D117 | [`02_SPEC.md`](02_SPEC.md) NFR-2 | asked with the measurement in hand (1.93 % off, 2.04 % on): NFR-2 is amended to ≤ 2.5 % of one core during capture; the sensors keep one reading a second and no code changes |
|
||||
| D111 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B | inside the game too, off means nothing more is read: the Overlay reads new fields and installs new hooks only while the Agent's control word says the session records Advanced metrics |
|
||||
| D112 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B | `slInit` is not hooked in train B; if ever, never `applicationId`, `projectId` or the paths |
|
||||
| D113 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B | train B is three releases: beta.40 fields of calls already hooked (no new patch site), beta.41 `slSetConstants` + `ffxConfigure`, beta.42 `slGetFeatureVersion` + `slGetFeatureRequirements`; each waits for the owner's run of the one before; C is beta.43, D beta.44 |
|
||||
| D114 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B | the field of view is stored as a session's range, never as a series |
|
||||
| D115 | [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Which struct version carries which field | a tail member of a vendor struct is read only where the upstream tags prove it is there |
|
||||
| D116 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B | "never the camera" is a build gate: `tools/overlay-fields-check.ps1` |
|
||||
| D118 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B | told that the sensor-library fix would take the number D113 gave train B's second release, the owner chose to release it at once as 0.1.0-beta.41: the train's second and third releases are beta.42 and beta.43, train C beta.44, train D beta.45 |
|
||||
| D119 | [`07_IPC.md`](07_IPC.md) §Region 5 | `FLT_MAX` (or +infinity) in an FSR depth plane is stored and shown as "infinite" — three engines pass it for the plane at infinity; for FSR only: for Streamline `FLT_MAX` is the "not set" sentinel and stays absent |
|
||||
| D120 | [`03_METRICS.md`](03_METRICS.md) §Upscaling | a session's upscaler is the technology named on the most samples, and its quality and render size are read from that technology's samples — not the first one named, with the others' values beside it |
|
||||
| D121 | [`HANDOFF.md`](HANDOFF.md) §NEXT | Cyberpunk 2077 was set to FSR upscaling and FrameLedger named none: a detection gap, to be investigated — which first needs a native log that survives the game's exit |
|
||||
| D122 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B | train B's second step is split: **beta.42** has no new patch site (D119–D121 and the patch registry's hardening); **beta.43** is the two new hooks, begun only after the owner has run Cyberpunk on beta.42 and its log was read. The third release is beta.44, train C beta.45, train D beta.46 |
|
||||
| D123 | [`19_SAFETY_AND_ANTICHEAT.md`](19_SAFETY_AND_ANTICHEAT.md) §Pre-injection checks, check 1 | a module list that changed while the guard read it is read again, at most three times, before it refuses — five real sessions on one PC in a week had ended as a safety unhook with no frame recorded; a list that never settles still refuses, and nothing else about what refuses changed |
|
||||
| D124 | [`HANDOFF.md`](HANDOFF.md) §NEXT | the guard's re-read (D123) ships with 0.1.0-beta.43 and not as a release of its own — the train's numbers do not move a third time; until then a launch can still be lost that way on beta.42 |
|
||||
| D125 | [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Hook inventory | an FSR UPSCALE is counted at the first source that saw one and at no other — a precaution for a loader that hands a dispatch on to the leaf's export (Cyberpunk 2077's 2.3.0 does, for frame generation); no title run so far upscales through one |
|
||||
| D126 | [`19_SAFETY_AND_ANTICHEAT.md`](19_SAFETY_AND_ANTICHEAT.md) §Crash & stability safety | the count of early abnormal ends starts again when the user switches hooking on (the consent grant sets it to 0) — it was never set back, so a game once switched off was switched off again by every single such end, under a reason that says "twice" (Lies of P, 2026-11-12) |
|
||||
| D127 | [`19_SAFETY_AND_ANTICHEAT.md`](19_SAFETY_AND_ANTICHEAT.md) §Crash & stability safety | a fault while a game is closing, which a hooked session does not see (Hogwarts Legacy, the driver's `_nvngx.dll`, hooked or not), is written down and not changed in 0.1.0-beta.44 — seeing it would end a user-mode exception for a fault no hook caused; a decision of its own |
|
||||
| D128 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B | a field of view over π is shown as the game gave it, with a row that says it is not radians, and is never converted — Cyberpunk 2077 gives Streamline degrees; converting would store a guess at the unit as the game's word |
|
||||
| D129 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B | `slInit` is not hooked at all — asked to reopen D112 and shown that no shipped mode is in the game in time (launch mode waits for the presentation runtime, no patch is ever made on a game's thread, an Advanced-only hook waits for the Agent's request), the owner kept it out; a hook there would be a patch that reads nothing |
|
||||
| D130 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B | six more Streamline core calls are hooked in one release, 0.1.0-beta.45 — `slIsFeatureSupported`, `slIsFeatureLoaded`, `slSetFeatureLoaded`, `slAllocateResources`, `slFreeResources`, `slShutdown`; trains C and D come after it, and train C's spike is written beside it as a document |
|
||||
| D131 | [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Hook inventory | the adapter a game asks `slIsFeatureSupported` about (`sl::AdapterInfo`: a LUID, or a Vulkan physical device) is never read — the feature's id and the result only; a build check refuses the struct's member names in code loaded into a game |
|
||||
| D132 | [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) §M14, `CLAUDE.md` rule 4's note of 2026-11-13 | Reflex route D goes to a spike on `hook-harness` and a stub first — and the ruling a go needed: calling a driver's read-only getter with the device of the swap chain the Overlay hooks is inside rule 4. No real game before the owner has seen the result |
|
||||
| D133 | [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) §M14, [`spike-notes/30-reflex-latency.md`](spike-notes/30-reflex-latency.md) | Reflex route C (the Overlay calling `slReflexGetState`) is refused; the no-injection ETW route stays closed, and §G with it |
|
||||
| D134 | [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Unhooking, *Batches* | installs and restores are batched through MinHook's queue — one stop of the game's threads for a batch, not one a patch — in a pull request of its own, measured, released alone (0.1.0-beta.46) |
|
||||
| D135 | [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Hook inventory | `slAllocateResources` keeps its patch although no game called it in the first six sessions; looked at again when there are more |
|
||||
| D136 | [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) §M14, [`spike-notes/31-reflex-route-d-harness.md`](spike-notes/31-reflex-route-d-harness.md) §The question for the owner | Reflex route D goes on to one real title, Cyberpunk 2077 — a plan of its own first, no code before it is approved, and no release carrying it before item 44 (d) has been run |
|
||||
| D137 | [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Unhooking, *Batches* | the `PATCH_BATCH` line says how a batch ended — one apply, or finished one patch at a time — after two batches in real games took 0.61 s and 1.26 s and the log could not say which; with the next release, not one of its own |
|
||||
| D138 | [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) §M14, [`handoff/history/0.1.0-beta.46.md`](handoff/history/0.1.0-beta.46.md) §The train after 0.1.0-beta.46 | the Reflex read has no switch of its own: it is part of Advanced metrics — so it reaches every Direct3D 12 game that loaded the driver's `nvapi64.dll`, for everyone who switched Advanced metrics on; "one title" is the order of the owner's first runs (item 45), not a limit in code |
|
||||
| D139 | [`spike-notes/31-reflex-route-d-harness.md`](spike-notes/31-reflex-route-d-harness.md) §The leg with a sleep | before any Overlay code the probe runs a leg with `NvAPI_D3D_SetSleepMode` and `NvAPI_D3D_Sleep` — writes, in the probe's own process, on its own device, in no shipped binary |
|
||||
| D140 | [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) §M14 | an `nvapi64.dll` loaded from the game's own folder — a replacement, not the driver's — is refused, and the session says why |
|
||||
| D141 | [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) §M14 | one call into the driver of 2 ms or more switches the Reflex read off until the game exits |
|
||||
| D142 | [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Calls the Overlay makes into a driver | asked on 2026-11-14 with Phantom Blade Zero's *GPU render* longer than its total: read the driver's `gpuActiveRenderTimeUs`, and with it `gpuFrameTimeUs` — two more members of the report already fetched, no further call |
|
||||
| D143 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §The inventory | the start-to-end *GPU render* line stays, stored and shown, under a label that says it includes the card's idle time |
|
||||
| D144 | [`07_IPC.md`](07_IPC.md) §Region 5 | the driver's frame-generation multiplier is kept as every value a session saw, not the last one |
|
||||
| D145 | [`../legal/ACCURACY.md`](../legal/ACCURACY.md) | the accuracy statement, the README and the guide say two real games were read on one driver (they said none); Privacy Policy 2.21 and Disclaimer 2.17 with it |
|
||||
| D146 | [`06_DATA_MODEL.md`](06_DATA_MODEL.md) §sensor_blobs | the Agent's samples were 1.32 s apart under a 1 s setting (it waited the whole interval after its work): sample on a fixed period, and store the rate the samples had |
|
||||
| D147 | [`03_METRICS.md`](03_METRICS.md) | the session summary's latency fields stay N/A: the driver's total is simulation start to GPU end, not input to display |
|
||||
| D148 | [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Native logging | asked on 2026-11-14 with item 46's Cyberpunk 2077 numbers (active render longer than the span between the GPU marks): count the frames, and write the counts **only to the Overlay's native log** — no layout, schema, App or string change |
|
||||
| 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 |
|
||||
| D154 | [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §The trains, [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) §M15 | Advanced metrics is closed: train D is not built, the ten Streamline entries that waited for a spike are not read (`RefusedRoute`), rule 4 is not amended for them. Nothing shipped is removed |
|
||||
| D155 | [`21_INPUT_DEVICES.md`](21_INPUT_DEVICES.md) §The owner's request and decisions | controllers are read by the Agent, from outside the game: no hook is added, rule 4 is untouched, and a session that is not hooked has the numbers too |
|
||||
| D156 | [`21_INPUT_DEVICES.md`](21_INPUT_DEVICES.md) §The owner's request and decisions | the reading is on unless switched off (`capture.input_devices`), and reads nothing until the Privacy Policy that describes it (2.22 or later) has been accepted on the PC |
|
||||
| D157 | [`21_INPUT_DEVICES.md`](21_INPUT_DEVICES.md) §The owner's request and decisions | built without a probe run on real controllers first ("Xây thẳng"): every source reports what it did, and what was verified against hand-made data only is said in each pull request |
|
||||
| D158 | [`21_INPUT_DEVICES.md`](21_INPUT_DEVICES.md) §The owner's request and decisions | keyboard and mouse are one class known only by `GetLastInputInfo`'s time: no Raw Input for them, no hook, no key in the process |
|
||||
| D159 | [`21_INPUT_DEVICES.md`](21_INPUT_DEVICES.md) §DualSense | nothing is ever sent to a controller; a DualSense on Bluetooth has a battery level only where Steam or the game switched it |
|
||||
| D160 | [`21_INPUT_DEVICES.md`](21_INPUT_DEVICES.md) §The owner's request and decisions | the numbers are columns of `sessions`, so they are in the CSV/JSON export and in a bug bundle, and the Privacy Policy's §3A says so |
|
||||
| D161 | [`21_INPUT_DEVICES.md`](21_INPUT_DEVICES.md) §The owner's request and decisions | a session that is not hooked is duration, hardware telemetry, the reason — and what the Agent reads from outside the game; CLAUDE.md's sentence is amended with the pull request that makes it true |
|
||||
| D162 | [`03_METRICS.md`](03_METRICS.md) §Input | also built: switches of method and the share with no input, marks on the frame-time chart, a battery's first and last level and its rate, the kind of connection, the Steam Input note, a trend metric, a Compare row, "usually played with" |
|
||||
| D163 | [`21_INPUT_DEVICES.md`](21_INPUT_DEVICES.md) §The owner's request and decisions | "supports controllers" is three pieces of evidence and never a verdict: Steam's own file on the disk (no network), the input libraries the game loaded, how the game was played |
|
||||
| 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`) |
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -69,7 +69,6 @@ are safety items, and something listed there as unresolved should not be built t
|
||||
| [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) | Telemetry layers (DXGI/PDH, LibreHardwareMonitor, NVAPI), the game process's memory, licences |
|
||||
| [`19_SAFETY_AND_ANTICHEAT.md`](19_SAFETY_AND_ANTICHEAT.md) | The anti-cheat guard, what a finding does, the user-mode exception, what will never be built |
|
||||
| [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) | Every unresolved question, defect and measurement, with its status marker |
|
||||
| [`21_INPUT_DEVICES.md`](21_INPUT_DEVICES.md) | Controllers and keyboard-and-mouse activity: what is read from outside the game, from where, and what never is |
|
||||
| [`HANDOFF.md`](HANDOFF.md) | Sequencing, the open owner-only items, the index of the owner's decisions |
|
||||
| [`handoff/`](handoff/) | Since beta.24 (D66): the history of every train and phase, the passed owner-only items, the traps — moved out of `HANDOFF.md` verbatim |
|
||||
| [`open-questions/`](open-questions/) | Since beta.24 (D66): the entries §S24 marks resolved, moved out of `20_OPEN_QUESTIONS.md` verbatim — a table there lists them |
|
||||
|
||||
@@ -1,69 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.38 was cut, 2026-11-11 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.38] - 2026-11-11
|
||||
|
||||
**The thirty-eighth pre-release: the App opens web and mail links only.** One small hardening, and nothing else you
|
||||
see, record or measure changes. The one place in the App that hands a link to Windows now refuses any address that is
|
||||
not `http`, `https` or `mailto`, where it trusted each caller to have checked — Windows runs whatever it is handed, and
|
||||
a `file:` address is a program. Every link the App shows already was one of those three, so no link you could click
|
||||
before stops working. The rest of this release is for developers: Qodana — JetBrains' code analysis — now reads the C#
|
||||
with its Rider-based linter and, as a second report, the C++. The same unsigned installer: verify its hash against
|
||||
`SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**Updating from `0.1.0-beta.37`:** Help ▸ Check for updates, then *Restart to update* with no game running. The legal
|
||||
texts keep their versions, so nothing is shown for you to accept; the ledger stays at schema 22 and the detection rules
|
||||
at `2026.11.2`. Nothing about capture or measurement changes: the code FrameLedger loads into a game is
|
||||
0.1.0-beta.37's, line for line.
|
||||
|
||||
**No alpha follows this release**: the alpha line rests (`guide/11-alpha-builds.md`).
|
||||
|
||||
### Changed
|
||||
|
||||
- **Every place that starts a process was read, and the App now opens web and mail links only.** JetBrains' rule for
|
||||
"a process started with something that is not a literal" reported 35 places — 11 in the product, 24 in tests. Each
|
||||
was read: what it starts, and where the path and the arguments come from (the table in `docs/13_CI_CD.md` §Qodana).
|
||||
None takes a value from outside the PC or from a file FrameLedger did not write, except the path and arguments of
|
||||
the game the user added. One was hardened: `ShellUrlOpener` — what opens a link in the browser or the mail client —
|
||||
now refuses any address that is not `http`, `https` or `mailto` itself, where it trusted each caller to have
|
||||
checked; the shell runs whatever it is handed, and a `file:` address is a program. Every caller already passed one
|
||||
of the project's own pages or a link held to those schemes, so no link you could click before stops working. The
|
||||
rule stays on: the files its results were read in are listed in `qodana.yaml`, so a new file that starts a
|
||||
process is reported — by path on the plugin's one inspection, since a rule's own id is honoured nowhere (three
|
||||
runs measured it). And a test of the repository's own, `ProcessStartSitesTests`, in the gate, fails on a new file
|
||||
that starts a process, or registers a scheduled task, until it has been read and listed.
|
||||
- **Qodana for .NET, on the Ultimate licence, reads the managed code** (developers only; owner decisions D99 and D100).
|
||||
The owner took an Ultimate licence for the Qodana Cloud organisation and asked for Qodana over every language. The
|
||||
job — `managed`, *Qodana (managed)* in a pull request's checks — now runs Qodana for .NET (Rider's engine) in native
|
||||
mode on a Windows runner, after a `dotnet build`, where the Community linter ran in a Linux container. Besides the
|
||||
C#, the XAML and the `.resx` it reads the Markdown and XML around the solution, and JetBrains' security rules read
|
||||
the C#. Its first run reported 3,953 problems, 3,607 of them **hints** — the level an editor offers without
|
||||
underlining anything, which the Community linter never reported; hints are off as a severity. Of the 347 left: a vi
|
||||
or ja string equal to the English one (271) is off in `.editorconfig` for `.resx` files — names, units and format
|
||||
strings are not translated; two Markdown inspections (table padding, and anchors computed otherwise than GitHub
|
||||
does) and the application manifest's XML are off in `qodana.yaml`; six results in `PrimaryDisplay.cs` are the
|
||||
linter's own fault (an internal assertion, in its log) and are excluded for that file; one test expression was
|
||||
simplified. The gate stays zero problems and the job stays advisory. An inspection is now switched off **where the
|
||||
engine that raised it reads** — one of ReSharper's in `.editorconfig`, what has no key there in `qodana.yaml` — which
|
||||
amends D93's "never in `qodana.yaml`" (`docs/13_CI_CD.md` §Qodana). The C++ goes to a second report, the next pull
|
||||
request's.
|
||||
- **Qodana reads the C++ too, as a second report** (developers only; owner decision D99). The job `native` has CMake
|
||||
write a Visual Studio solution for `src/native` (the preset `x64-vs-analysis`; nothing ships from it) and runs
|
||||
Qodana for .NET over it — ReSharper's C++ inspections and the clang-tidy checks they bundle — with settings of its
|
||||
own (`qodana-native.yaml`), reporting to a Qodana Cloud project of its own. Its first run reported 4,695 problems,
|
||||
4,040 of them hints; of the 655 left, 494 are distinct (a file compiled into three targets is reported three
|
||||
times). Nearly all of them are not faults, and `.editorconfig` now says why in fifty-four lines, each with its
|
||||
reason: clang's opinion of code that only MSVC builds (`__try`, a function pointer got by name, struct padding);
|
||||
the engine misreading `std::atomic_ref`, zero-initialised API structures and tests of `constexpr` functions;
|
||||
proposals to restate working code in a newer idiom; and what a probe or a test does on purpose. Eleven things
|
||||
were fixed, none changing what a shipped binary does: `std::size` for four hand-written array lengths, two
|
||||
multiplications done in a narrower type than their result, two unused member functions, an unused type alias, two
|
||||
unused includes. **In code loaded into a game nothing was changed**: the report found no defect there, and what it
|
||||
did say about those files is listed in `docs/13_CI_CD.md` §Qodana — among it one function in the Overlay that
|
||||
nothing calls (`LogNoteW`), which is recorded for the owner and not removed (D100). The gate is zero problems and the job is advisory, like the other.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **A test that failed on a busy machine** (developers only). `ShmDrainIntegrationTests`' drain under supervision
|
||||
ended after one guard evaluation whenever the first scan was slow enough for fifty presents to be waiting, and
|
||||
then failed its own "supervised more than once"; the loop now supervises at least twice whatever the first
|
||||
drain holds.
|
||||
@@ -1,125 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.39 was cut, 2026-11-11 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.39] - 2026-11-11
|
||||
|
||||
**The thirty-ninth pre-release: Advanced metrics.** A new setting, **off unless you switch it on** — Settings ▸
|
||||
Recording ▸ *Advanced metrics* — and a page of its own. With it on, the capture agent reads more from the graphics
|
||||
driver and the hardware sensors during a session and keeps it with the session: the graphics card's memory, load,
|
||||
clocks, fans, voltages and power in detail; what each display can do with HDR and variable refresh, and what the
|
||||
game's display did; the driver's settings, global and for the game; and — when the agent runs as administrator with
|
||||
PawnIO installed — the processor per core, the memory and the motherboard's sensors. The **Advanced** page (the last
|
||||
item on the left, **Ctrl+6**) shows it under what it belongs to: **This PC**, read only while the page is open and
|
||||
never stored; **Session**, what one session kept, in tables and a chart; **Sources**, every reading FrameLedger knows
|
||||
of and, for each one it does not read, why. With the setting off, nothing more is read or stored and the page is not
|
||||
there. The same unsigned installer: verify its hash against `SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**What it is not, yet.** None of these readings has been checked against another tool. The processor's, the memory's
|
||||
and the motherboard's sensors have never been read on real hardware — the first run as administrator with PawnIO is
|
||||
still to come. The driver's own figures exist on NVIDIA cards only, and no AMD or Intel card was tested. A drive's
|
||||
temperature is not read. Nothing is read inside the game by this release: the readings that need a hook come with
|
||||
later ones. `LIMITATIONS.md` §Sensors lists every limit.
|
||||
|
||||
**Updating from `0.1.0-beta.38`:** Help ▸ Check for updates, then *Restart to update* with no game running. The terms
|
||||
window shows the **Privacy Policy 2.15** and the **Disclaimer 2.15** once — they name what Advanced metrics reads and
|
||||
stores, only while it is on, and that PawnIO and the administrator mode then read more than the CPU temperature. The
|
||||
ledger moves to **schema 23** (two tables are added; nothing that was there changes), so a 0.1.0-beta.38 cannot open
|
||||
it afterwards. The detection rules stay at `2026.11.2`. With the setting off, nothing about capture or measurement
|
||||
changes: the code FrameLedger loads into a game — the overlay, the Vulkan layer, the shared-memory layout, the
|
||||
injector — is 0.1.0-beta.38's, line for line.
|
||||
|
||||
*The entries below are in the order the seven pull requests landed. One that says "not yet" describes that pull
|
||||
request; a later entry is what followed.*
|
||||
|
||||
### Added
|
||||
|
||||
- **"Advanced metrics" is planned, and its inventory is written — nothing reads it yet.** The owner asked for a
|
||||
setting, *Thông số nâng cao*, with a navigation item of its own that shows as much as the NVAPI and Streamline
|
||||
headers and PawnIO make available, each value under what it belongs to: one game session, or the PC. This pull
|
||||
request is the first of that train and changes nothing you can see or record. It adds the list everything else in
|
||||
the train reads — `AdvancedMetricCatalog`, 137 entries: what the Agent will read from NVAPI and
|
||||
LibreHardwareMonitor (the card's firmware, architecture and cores; its memory with evictions and promotions; its
|
||||
utilisation by domain; what a display can do with HDR and variable refresh; the driver's profile; and, as
|
||||
administrator with PawnIO, the processor per core, the motherboard, the memory modules and the drives'
|
||||
temperatures), what can only be read inside a game and waits for a later release, **and what is never read with the
|
||||
reason** — a serial number, a display's EDID, the list of programs that are encoding, the camera's position, what
|
||||
a vendor's licence closes. `docs/18_GPU_VENDOR_APIS.md` §Advanced metrics holds the design, the owner's decisions
|
||||
D101–D108 and the same list as a table; a test fails when the table and the catalog differ in either direction.
|
||||
|
||||
- **The NVIDIA bridge can read what Advanced metrics will show — and nothing calls it yet.**
|
||||
`FrameLedger.NvapiBridge.dll`, the library the Agent loads into its own process and never into a game, gains five
|
||||
reads (its ABI 3): the card's facts — firmware version, architecture, ray-tracing and tensor core counts, base and
|
||||
boost clocks, its memory sizes, the driver's package; what it says now — free and used video memory with evictions
|
||||
and promotions, the frame-buffer, video and bus utilisation, the performance state, the encoder's load; what each
|
||||
connected display can do with HDR and variable refresh; the state of the display a game presents on; and every
|
||||
setting of a driver profile. On the development PC's RTX 5080 all twenty facts and eight of the ten live groups
|
||||
answer — the card has no board or power-supply temperature sensor, so those two will read N/A.
|
||||
**It reads no identifier**: no serial number, no unique id, no display EDID, and not which programs are encoding.
|
||||
- **"The bridge never calls a setter" is now a build check.** A new gate, `tools/nvapi-readonly-check.ps1`, compares
|
||||
every NVAPI call in the bridge's source with a committed list of forty-four reads, in both directions, and refuses a
|
||||
name that sets, saves, restores, registers or controls something — or returns an identifier — even when someone
|
||||
adds it to the list.
|
||||
|
||||
- **The reader behind Advanced metrics exists, was measured on a real PC, and is still not switched on.** One
|
||||
reader for the whole Agent, on a thread of its own, that runs only while a session or the page needs it: NVIDIA's
|
||||
figures every second, and every sensor LibreHardwareMonitor has for the graphics card — each fan and its duty, the
|
||||
core voltage, PCI Express traffic, the load of every engine. When the Agent runs as administrator with PawnIO
|
||||
installed it will also read the processor per core, the memory and the motherboard's sensor chip.
|
||||
**A drive's temperature is not read**: the library cannot list drives without touching removable ones, so that
|
||||
group is never opened and the value will read N/A with that reason.
|
||||
- **`FrameLedger.CaptureHost probe-advanced`** (a developer tool, not shipped): runs that reader for a few seconds
|
||||
on your own rights and prints everything it read and what it cost. On the development PC it read 35 facts and 58
|
||||
values a second — and showed that one refresh of the sensor library takes 14 ms of processor time, so the reader
|
||||
refreshes it every five seconds, where NVIDIA's own figures (0.4 ms) stay at one a second.
|
||||
|
||||
- **The ledger can hold Advanced metrics — and holds none yet.** Schema 23 adds two tables: one for the facts of
|
||||
the PC, stored once per distinct set, and one for what a session recorded with the option on knows — its own
|
||||
facts, which sources answered and why the others did not, and the statistics of its extra series. Nothing is
|
||||
added to the session row itself, so what the JSON export and a bug bundle carry does not grow. The extra series
|
||||
are stored beside the others under names of their own, with a real "no reading" for a second in which a sensor
|
||||
was not read. One hour of them is about 0.2 MB. **A session recorded with the option off stores nothing of this**,
|
||||
and the option does not exist yet. *A 0.1.0-beta.38 cannot open a ledger a later build has migrated.*
|
||||
|
||||
- **Settings ▸ Recording ▸ Advanced metrics — the switch exists, off by default.** On, the capture agent reads more
|
||||
from the graphics driver and the hardware sensors during a session and stores it with the session: the graphics
|
||||
card's memory, load, clocks, fans, voltages and power in detail, what each display can do with HDR and variable
|
||||
refresh and what the game's display did, the driver's settings for the game — and, when the agent runs as
|
||||
administrator with PawnIO installed, the processor per core, the memory and the motherboard's sensors. **Off,
|
||||
nothing more is read or stored**, and the shared reader is not even started. It applies from the next session, and
|
||||
a session recorded while it was off is not filled in later. NVIDIA's figures are read once a second, the sensors
|
||||
every five. **No page shows what is stored yet** — that is the next pull requests' — and none of it is in an
|
||||
export or a bug report.
|
||||
- **The App can ask the agent what this PC reads right now — and no page asks yet.** A new request,
|
||||
`GetAdvancedMachine`, answers what the agent's shared reader last read: the PC's facts, the newest value of every
|
||||
series, and which sources answer or why they do not. It never touches a sensor itself, so it cannot hold up the
|
||||
pipe. Each request also keeps the reader running for five seconds, which is how "with no game running, sensors are
|
||||
read only while the page is open" works without anything telling the agent that a page closed. With Advanced
|
||||
metrics off it answers that it is off, and nothing is read. On the App's side `AdvancedMachineFeed` asks once a
|
||||
second while a page watches it and keeps each value with the moment it was read.
|
||||
- **The Advanced page.** While Advanced metrics is on, **Advanced** is the last item in the list on the left, and
|
||||
**Ctrl+6** opens it. **This PC** shows what the graphics driver and the sensors say right now — the card's
|
||||
firmware, cores and memory, what each display can do, the driver's settings, and every reading with the time it
|
||||
was read at and a chart of its last five minutes. It is read only while the page is open, and is not stored.
|
||||
**Session** shows what a session recorded with the option on kept: the PC as it was, what belonged to that session,
|
||||
the lowest, average and highest of each reading, and a chart over the session. **Sources** lists every reading
|
||||
FrameLedger knows of and, for each one it does not read, why — the agent is not an administrator, PawnIO is not
|
||||
installed, it comes with a later release, or it is never read. A session's summary has an **Advanced metrics…**
|
||||
button that opens that session there. In `en`, `vi` and `ja`; the user guide has a page for it.
|
||||
- **The terms window shows the Privacy Policy 2.15 and the Disclaimer 2.15 once.** The Privacy Policy names what
|
||||
Advanced metrics reads and stores, only while it is on, and what it never reads: a serial number, a display's
|
||||
identification data, a list of other programs. The Disclaimer's two sentences about PawnIO and about running the
|
||||
agent as administrator said "the CPU temperature"; they now also name the processor's, the memory's and the
|
||||
motherboard's sensors, read with Advanced metrics on. The same sentence changed in Settings, the first run, the
|
||||
administrator dialog, the guide and `LIMITATIONS.md`.
|
||||
|
||||
### Changed
|
||||
|
||||
- **A crash file from a newer build no longer loses its tail in an older one.** The file a session writes as it goes
|
||||
(so that a crash keeps what was recorded) is made of chunks; a reader that met a chunk of a kind it did not know
|
||||
stopped there. It now passes over a whole chunk it does not know and reads on.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **A sentence in the documents that kept a function from being called.** `docs/18_GPU_VENDOR_APIS.md` said the
|
||||
vendored NVAPI headers do not declare `NvAPI_GPU_GetMemoryInfoEx`. They do — in `nvapi_lite_common.h`, which
|
||||
`nvapi.h` includes; the search that found nothing had looked in `nvapi.h` alone. The row is corrected, and the
|
||||
bridge will call it for the advanced memory rows. Nothing about the memory figures FrameLedger shows today changes.
|
||||
@@ -1,99 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.40 was cut, 2026-11-12 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.40] - 2026-11-12
|
||||
|
||||
**The fortieth pre-release: Advanced metrics, inside the game.** With **Advanced metrics** on (Settings ▸ Recording;
|
||||
off unless you switch it on), a session of a game FrameLedger measures from inside now also keeps **what the game
|
||||
itself tells its upscaler**: for DLSS the output size, the model preset for each quality mode, whether the game said
|
||||
its colour buffers are HDR, auto-exposure, alpha upscaling and the exposure values; for FSR the sharpening, the
|
||||
largest jitter offset, the exposure, the near and far planes, the **range** of the field of view, the flags, the
|
||||
frame time the game reported and FSR's own video memory when the game asked for it. The **Advanced** page shows them
|
||||
under the session, in the vendor's own notation, and the session says in a sentence what became of them. With the
|
||||
setting off nothing more is read inside a game: the component in the game runs the same reads as before, and a test
|
||||
that injects into a window sending all of it finds the new memory region empty to the last byte. The same unsigned
|
||||
installer: verify its hash against `SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**What it is not, yet.** **None of this has been read from a real game** — only from the project's own test window.
|
||||
**Many games will show nothing**: most set their DLSS options through a call FrameLedger cannot intercept, and the
|
||||
FSR rows need FSR 3.1 or later through AMD's own library (a game that upscales through the older FSR 3.0 interface
|
||||
shows none). The session then says *the game made none of the calls these are read from* — which never means the
|
||||
game uses no upscaler; its summary names the upscaler as before. These are the game's words to the upscaler, not a
|
||||
check of what the upscaler did. **Never read:** where the camera is, which way it looks, its matrices — a build
|
||||
check refuses those names anywhere in the code loaded into a game. No new hook is installed by this release; two
|
||||
further steps of this train add hooks, each after this one has been run on real games. `LIMITATIONS.md` §Sensors
|
||||
lists every limit.
|
||||
|
||||
**Updating from `0.1.0-beta.39`:** Help ▸ Check for updates, then *Restart to update* with no game running. The terms
|
||||
window shows the **Privacy Policy 2.16** once — it names what is stored of the game's upscaler parameters, only with
|
||||
Advanced metrics on and only for a game FrameLedger injects into, and what is never read. The Disclaimer stays 2.15.
|
||||
**A game that is running when you update must be restarted before FrameLedger measures it again**: the shared memory
|
||||
between the game and the agent has a new layout (version 5), and the component inside the game is new. The ledger
|
||||
stays at schema 23 and the detection rules at `2026.11.2`.
|
||||
|
||||
*The entries below are in the order the four pull requests landed. One that says "not yet" describes that pull
|
||||
request; a later entry is what followed.*
|
||||
|
||||
### Added
|
||||
|
||||
- **Advanced metrics inside the game is planned — three releases, and nothing reads it yet.** The readings that
|
||||
exist only inside a game — the options a game gives DLSS and FSR, FSR's own memory, later the constants a game
|
||||
gives Streamline and its frame-generation configuration — come in three steps (owner decisions D110–D116):
|
||||
first more fields of calls FrameLedger already intercepts, with no new hook; then two new hooks; then two more.
|
||||
Each step waits for the one before to be run on real games. With Advanced metrics off, nothing more is read
|
||||
inside a game either. This pull request changes nothing you can see or record: it records the decisions, and
|
||||
**which version of each vendor struct carries which field**, compared across every upstream release of Streamline
|
||||
2.x and of the FidelityFX API — a field is read only where it is proven to be there.
|
||||
- **`tools/agent-cost.ps1`** (a developer tool): what the shipped capture agent costs while it records, measured on
|
||||
the real program against the project's own test window, with Advanced metrics off and on.
|
||||
|
||||
- **The shared memory between a game and the agent has room for what a game tells its upscaler — and nothing
|
||||
writes it yet.** Its layout is version 5: one new region, sized once for the three releases of this train, and
|
||||
one new word by which the agent says "this session records Advanced metrics". With that word at zero — every
|
||||
session, until the next pull request, and afterwards every session with the option off — the region stays empty and
|
||||
the component inside the game does exactly what it did before. **A game that is running when you update must be
|
||||
restarted before FrameLedger measures it again**, as after every update.
|
||||
|
||||
- **The component inside a game can read what the game tells its upscaler — and only when asked.** For a game
|
||||
FrameLedger injects into, and only while the agent asks for it (nothing asks yet: that is the next pull request,
|
||||
and then only with Advanced metrics on), the calls FrameLedger already intercepts are read a little further: the
|
||||
options a game hands DLSS with each evaluation (output size, presets, exposure, three switches), what it hands
|
||||
FSR with each upscale (sharpening, the jitter's size, exposure, the depth range, the field of view as a range,
|
||||
flags, the frame time it reports), and FSR's own memory when the game itself asks for it. **No new hook**, and
|
||||
with the request off the same code as before runs: a test injects into a window that sends all of it and finds
|
||||
the new memory region empty to the last byte. **Never the camera's position, its axes or its matrices** — a
|
||||
build check now refuses those names anywhere in the code loaded into a game (`tools/overlay-fields-check.ps1`).
|
||||
Many games set their DLSS options through a call that cannot be intercepted, and will show nothing here.
|
||||
Measured cost while asked: 22–23 billionths of a second per frame for FSR, 10–12 for DLSS; not measurable when
|
||||
not asked.
|
||||
- **A second session of a game that kept running starts its summaries afresh.** The ranges and counts kept inside the
|
||||
game belong to the session that asked for them: each session asks with a request of its own, and the agent reads
|
||||
only what answers it.
|
||||
|
||||
- **Advanced metrics: what the game tells DLSS and FSR, kept with the session.** With Advanced metrics on, a session
|
||||
of a game FrameLedger measures from inside now also keeps what the game itself handed to its upscaler: for DLSS the
|
||||
output size, the model preset for each quality mode, whether the game said its colour buffers are HDR,
|
||||
auto-exposure, alpha upscaling and the exposure values; for FSR the sharpening, the largest jitter offset, the
|
||||
exposure, the near and far planes, the **range** of the field of view, the flags, the frame time the game reported
|
||||
(as a chart) and FSR's own video memory at the moments the game asked. The Advanced page shows them under the
|
||||
session, in the vendor's own notation. **Many games will show nothing**, and the session says why — most games
|
||||
set their DLSS options through a call FrameLedger cannot see, and the FSR rows need FSR 3.1 or later through AMD's
|
||||
library; it never means the game uses no upscaler. **Never read:** where the camera is, which way it looks, its
|
||||
matrices. With the option off nothing more is read inside a game, exactly as before. Not yet read from a real game.
|
||||
- **Privacy Policy 2.16** names the above: what is stored, only with the option on and only for a game FrameLedger
|
||||
injects into, and what is never read. You are shown it once after updating.
|
||||
|
||||
### Changed
|
||||
|
||||
- **The agent's processor budget says what was measured.** The specification promised that the capture agent uses
|
||||
at most 1 % of one processor core while recording; nobody had measured it. Measured on the development PC it is
|
||||
1.93 % — 2.04 % with Advanced metrics on — nearly all of it the once-a-second read of the graphics card's sensors
|
||||
that every session has always made, and its memory is 113 MiB (119 with the option on) against a limit of 150.
|
||||
The owner chose to keep the readings and amend the limit: **NFR-2 is now ≤ 2.5 % of one core** (D117). Nothing the
|
||||
agent does changes.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **A crash dump is tried up to three times.** When FrameLedger or its agent stops on an error it never expected, a
|
||||
small helper writes a dump of the program for a bug report - while the program's other threads are still
|
||||
running. Windows can fail that once when the program changes under it, and one failure used to mean no dump at
|
||||
all. It is now tried again, twice, a moment apart.
|
||||
@@ -1,41 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.41 was cut, 2026-11-12 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.41] - 2026-11-12
|
||||
|
||||
**The forty-first pre-release: one fix, for Advanced metrics with the agent as administrator.** If you run the
|
||||
capture agent as administrator with PawnIO installed and have **Advanced metrics** on, 0.1.0-beta.40 and
|
||||
0.1.0-beta.39, which has the same code and where it was not looked for, could lose sensors: after most sessions the Advanced page stopped showing the processor's readings
|
||||
until it was reopened, and now and then a whole session was stored with the graphics driver's seventeen readings
|
||||
and none of the two hundred from the sensor library. The agent was closing the sensor library in one place while
|
||||
another place was still reading it. It now opens and closes it in one place only, and never while something is
|
||||
reading. If you do not use that combination, nothing changes for you. The same unsigned installer: verify its hash
|
||||
against `SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**What it is not, yet.** The fix was made from the agent's log of ten real sessions; the fault needs an
|
||||
administrator's agent with PawnIO to show, and has not been seen to be gone on such a PC yet. After a few sessions
|
||||
the agent's log (Logs page) should no longer say *a device is left alone* or *the sensor library did not open*.
|
||||
Everything 0.1.0-beta.40's notes say is not yet done still stands.
|
||||
|
||||
**Updating from `0.1.0-beta.40`:** Help ▸ Check for updates, then *Restart to update* with no game running. No
|
||||
terms to read again, no change to the ledger (schema 23), the detection rules stay at `2026.11.2`. **The code
|
||||
FrameLedger loads into a game — the overlay, the Vulkan layer, the shared-memory layout, the injector — is
|
||||
0.1.0-beta.40's, line for line**; as after every update, a game that was running across it must be restarted
|
||||
before it is measured again.
|
||||
|
||||
**A note on numbers.** The plan for Advanced metrics had named 0.1.0-beta.41 for its next step inside the game (two
|
||||
new hooks). This fix took the number; that step is now 0.1.0-beta.42, and the ones after it move by one as well.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Advanced metrics: the processor's sensors no longer drop out after a session, and a session no longer loses its
|
||||
sensors at the start.** With the agent running as administrator and PawnIO installed, the sensor library was being
|
||||
closed by one part of the agent while another part was still reading it. After most sessions the Advanced page
|
||||
lost the processor's readings until it was reopened, and one session in ten stored only the graphics driver's
|
||||
seventeen series instead of two hundred and twelve. The agent now opens and closes the sensor library in one
|
||||
place, and does not close it while anything is still reading. Found in the first sessions recorded that way; the
|
||||
cause was read from the log and could not be reproduced without that setup, so the next sessions will show
|
||||
whether it is gone — the agent's log should no longer say *a device is left alone* or *the sensor library did not
|
||||
open*. Nothing changes in the code loaded into a game.
|
||||
- **Two comparisons in the Advanced-metrics code say what they mean.** Whether a game gave FSR one field of view or
|
||||
a range of them was decided by comparing two decimal numbers for equality; it is now decided by comparing the two
|
||||
stored values bit for bit. Nothing you see changes. (Found by SonarCloud after 0.1.0-beta.40 was merged.)
|
||||
@@ -1,62 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.42 was cut, 2026-11-12 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.42] - 2026-11-12
|
||||
|
||||
**The forty-second pre-release: groundwork, and a log that can answer a question.** Four changes, none of which
|
||||
adds a hook to a game. A session that saw two upscalers is now named after the one it ran — one real session had
|
||||
been stored as "DLSS" with FSR's quality mode and FSR's render size. The part of FrameLedger inside the game can no
|
||||
longer leave a hook in after it has stopped. Its log is now written during the session rather than only at the
|
||||
start and the end, so it is whole after a game that simply exits, and it says which module each hook went into and
|
||||
what kinds of call each AMD FidelityFX module received. And with **Advanced metrics** on, an FSR depth plane at
|
||||
infinity is shown as "∞" where it used to be missing. The same unsigned installer: verify its hash against
|
||||
`SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**What it is not, yet.** It does not fix a game whose upscaler reads "unknown" — Cyberpunk 2077 set to FSR is the
|
||||
one known — it makes the next session of such a game say why, in `logs\overlay-<pid>-….log`. The two new readings
|
||||
planned for Advanced metrics (the frame-generation settings a game gives FSR, and what a game tells Streamline
|
||||
about each frame) are the next pre-release, after that log has been read. No real game has been run on this
|
||||
build: the changes inside the game were tested with FrameLedger's own test program, and their cost was measured
|
||||
on the code itself (about 4 billionths of a second per FidelityFX call for the log's new lines; nothing measurable
|
||||
for the rest). Everything 0.1.0-beta.41's notes say is not yet done still stands.
|
||||
|
||||
**Updating from `0.1.0-beta.41`:** Help ▸ Check for updates, then *Restart to update* with no game running. No
|
||||
terms to read again, no change to the ledger (schema 23), the detection rules stay at `2026.11.2`. **The code
|
||||
loaded into a game changed in this release** — the first time since 0.1.0-beta.40 — so a game that was running
|
||||
during the update keeps the old part until it is started again. Sessions already stored are not rewritten: one
|
||||
that was named after the wrong upscaler keeps that name.
|
||||
|
||||
### Added
|
||||
|
||||
- **Advanced metrics: FSR's depth plane at infinity is shown as "∞".** Engines with an infinite depth range tell
|
||||
FSR that one of the two camera planes is at infinity, and FrameLedger took that value for "not set" — so a
|
||||
session's depth range showed one plane where the game had given two. The plane at infinity is now stored and
|
||||
shown as such. Only for FSR, and only while Advanced metrics is on; nothing else about what is read changed.
|
||||
|
||||
### Changed
|
||||
|
||||
- **The Overlay's log is whole after a game exits, and says more.** The log FrameLedger's part inside the game
|
||||
writes (`logs\overlay-<pid>-….log`) used to hold only the first half second of a session unless the session
|
||||
ended while the game was still running: a game that exits takes the thread that writes the log with it. It is
|
||||
now written during the session, whenever something new was noted. Each hook that went in is named by its module
|
||||
and function (four AMD modules used to be four identical lines), a hook that could not go in says why, and the
|
||||
log lists which kinds of call each AMD FidelityFX module received and which upscaling and frame-generation
|
||||
modules the game loaded, and when. This is for finding out why a game's upscaler reads "unknown" — nothing in
|
||||
it is a measurement, and nothing from it is stored in a session. Measured cost: about 4 billionths of a second
|
||||
per FidelityFX call.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **The part inside the game can no longer leave a hook in after it has stopped.** Two gaps in how the Overlay keeps
|
||||
track of its own patches, found by reading the code and not by a failure: a patch made while the table of patches
|
||||
was full would have been made anyway and never taken out, and a stop that arrived at the exact moment a hook was
|
||||
going in could miss it. A patch now takes its place in the table before it is made — no place, no patch — and is
|
||||
recorded before it can run, so the stop either removes it or the installer does. A patch that could not be made
|
||||
is written to the Overlay's log with the reason, where it used to be silent. No hook's own code changed.
|
||||
|
||||
- **A session that saw two upscalers is named after the one it ran, with that one's quality and render size.** The
|
||||
session's upscaler used to be the first one FrameLedger saw named, while the quality mode and the render size
|
||||
came from whichever frames carried them. A game that evaluated DLSS briefly and then ran FSR was stored as "DLSS"
|
||||
with FSR's quality and FSR's render size. The name is now the technology named on the most frames, the quality
|
||||
and the size are read from that technology's frames only, and such a session is marked "settings changed during
|
||||
session". What that technology did not say reads N/A rather than borrowing the other's value. Sessions already
|
||||
stored are not rewritten.
|
||||
@@ -1,86 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.43 was cut, 2026-11-12 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.43] - 2026-11-12
|
||||
|
||||
**The forty-third pre-release: a game that was still loading is no longer lost, and two more readings inside the
|
||||
game.** Two fixes first. A game that FrameLedger looked at while it was still loading its modules could be left
|
||||
unrecorded — the session ended as a safety stop with nothing in it; FrameLedger now reads the list again before it
|
||||
gives up, and what stops a session has not changed. And an FSR upscale is counted once per frame whichever way the
|
||||
game's FidelityFX loader passes it on. Then, with **Advanced metrics** on, a session of a game measured from inside
|
||||
also keeps what the game tells NVIDIA Streamline about each frame and how it configures FSR frame generation —
|
||||
from two calls FrameLedger hooks only once Advanced metrics has been asked for in that game. The same unsigned
|
||||
installer: verify its hash against `SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**What it is not, yet.** The two new readings have been tested with FrameLedger's own test program and **have not
|
||||
been run in a real game**: this release is the first time either hook is put into one. They are what the game
|
||||
asked for, not a check of what happened, and Streamline's values are those of the first view a game draws.
|
||||
Streamline 1.x is not read. Where the game's camera is, which way it looks and its matrices are never read — they
|
||||
sit in the same data, and a check in the build refuses code that names them. The cost was measured on the code
|
||||
itself: about 20 billionths of a second per frame for Streamline's call and 15 per call for FSR's while the option
|
||||
is on, under 2 while it is off; nothing measurable for the two fixes. A game whose FSR is built in (Cyberpunk 2077's
|
||||
FSR 2.1) still reads "unknown" as its upscaler. Everything 0.1.0-beta.42's notes say is not yet done still stands.
|
||||
|
||||
**Updating from `0.1.0-beta.42`:** Help ▸ Check for updates, then *Restart to update* with no game running. **The
|
||||
terms are shown once: Privacy Policy 2.17**, which names the two new readings. No change to the ledger (schema 23),
|
||||
the detection rules stay at `2026.11.2`. **The code loaded into a game changed in this release**, so a game that
|
||||
was running during the update keeps the old part until it is started again.
|
||||
|
||||
### Added
|
||||
|
||||
- **Advanced metrics: a session now shows what the game told Streamline each frame and how it configured FSR frame
|
||||
generation.** For a game FrameLedger measures from inside, a session recorded with **Advanced metrics** on keeps
|
||||
— beside what the game told DLSS and FSR — the largest jitter offset, the motion-vector scale and how motion
|
||||
vectors are stored, the near and far planes and whether depth is inverted, the range of the field of view, the
|
||||
aspect ratio, whether the projection is orthographic and how often the game reset the upscaler's history
|
||||
(Streamline); and whether FSR frame generation was configured on, whether it may run asynchronously, its flags,
|
||||
whether only generated frames are presented, and the part of the picture it generates in. A setting the game
|
||||
changed during the session reads *on and off*. The line under the session now also says, for each of the two,
|
||||
whether it was read, hooked and never called by the game, or not hooked because the game did not load the
|
||||
library — so an empty page says which it is. These are what the game asked for, not a check of what happened;
|
||||
neither has been confirmed on a real game yet. Never read: where the camera is, which way it looks, its
|
||||
matrices.
|
||||
|
||||
- **The terms are shown once after this update: Privacy Policy 2.17.** It names the two new readings above and says
|
||||
that the two calls they come from are intercepted in a game only once a session with Advanced metrics on has
|
||||
started there. Nothing is sent anywhere, as before.
|
||||
|
||||
- **Advanced metrics, inside the game: how the game configures FSR frame generation** (the part inside the game;
|
||||
what a session shows of it comes with the same release). With **Advanced metrics** on, FrameLedger now also
|
||||
reads, from the call a game makes to configure AMD's frame generation, whether generation is on, whether it may
|
||||
run asynchronously, its flags, whether only generated frames are presented, and the part of the picture it
|
||||
generates in. Nothing else of that call is read. Like the Streamline hook, this one is put into a game only once
|
||||
Advanced metrics has been asked for. Measured cost: about 15 billionths of a second per call while the option is
|
||||
on, under 2 while it is off.
|
||||
|
||||
- **Advanced metrics, inside the game: what the game tells NVIDIA Streamline about each frame** (the part inside the
|
||||
game; what a session shows of it comes with the same release). With **Advanced metrics** on, FrameLedger now also
|
||||
reads, from a call a Streamline game makes every frame, the size of the jitter, the motion-vector scale, the depth
|
||||
range, the range of the field of view, the aspect ratio and seven on/off settings (inverted depth, how motion
|
||||
vectors are stored, whether the upscaler's history was reset). It never reads where the game's camera is, which
|
||||
way it looks, or its matrices, which sit in the same data — a check in the build refuses any code that names
|
||||
them. This is the first reading that needs a hook of its own, and that hook is put into a game only once
|
||||
Advanced metrics has been asked for: with the option off, nothing in the game is touched for it. Measured cost:
|
||||
about 20 billionths of a second per frame while the option is on, under one billionth while it is off.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **FSR upscaling is counted once per frame whichever way the game's FidelityFX loader passes it on.** Newer
|
||||
FidelityFX loaders hand a call on to the library behind them in a way that brought the same upscale to
|
||||
FrameLedger twice; with frame generation off, the count of frames the game rendered would have doubled — Native
|
||||
FPS twice too high. Seen in how Cyberpunk 2077's loader passes on its frame-generation calls; no game tested so
|
||||
far upscales through such a loader, so this is a precaution. The upscale is now counted where the game calls it,
|
||||
and nowhere else. (Owner decision D125. Measured cost: none that can be told from noise.)
|
||||
|
||||
- **A game is no longer left unrecorded because it was still loading when FrameLedger looked at it.** Before it
|
||||
hooks a game, and again right after, FrameLedger lists the modules the game has loaded and checks them against
|
||||
the anti-cheat list. A game that is starting loads and unloads modules for several seconds, and when the list
|
||||
changed in the middle of being read FrameLedger treated it as unreadable and stopped: the session ended as a
|
||||
safety stop with nothing recorded, and the game ran on unmeasured until it was restarted. It now reads the list
|
||||
again — up to three more times, a quarter of a second apart — and only stops if the list never holds still. What
|
||||
stops a session has not changed: an anti-cheat module found in any read stops it at once, a protected process
|
||||
still stops it at once, and a list that cannot be read in the end is still a stop, never a pass. (Owner decision
|
||||
D123; seen five times in one PC's logs in a week.)
|
||||
|
||||
- **A test of the Overlay's log reads its lines without `strlen`.** The helper that looks for a line in the log
|
||||
took its text as C strings and measured one with `strlen`; it takes strings now. Test code only: nothing in the
|
||||
installed software changes. (Found by SonarCloud after 0.1.0-beta.42 was merged.)
|
||||
@@ -1,83 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.44 was cut, 2026-11-12 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.44] - 2026-11-12
|
||||
|
||||
**The forty-fourth pre-release: what the first real games on 0.1.0-beta.43 showed, fixed — and two more readings
|
||||
inside the game.** Nine sessions on five games were read the day 0.1.0-beta.43 came out. Its two new readings
|
||||
worked on four of them; three things did not read right, and are fixed first. Cyberpunk 2077 tells NVIDIA
|
||||
Streamline its field of view in degrees, and FrameLedger labelled the number as radians: a value too large to be
|
||||
radians is now shown as the game gave it, and says so. A game whose hooking had once been switched off after two
|
||||
early ends was switched off again by every single one after that: the count now starts again each time you switch
|
||||
hooking back on. And an FSR frame-generation configuration with no flag set now says *None*. Then, with
|
||||
**Advanced metrics** on, a session of a game measured from inside can also keep what Streamline answers when the
|
||||
game asks **which version a feature is and what it requires** — from two more calls FrameLedger hooks only once
|
||||
Advanced metrics has been asked for in that game. The same unsigned installer: verify its hash against
|
||||
`SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**What it is not, yet.** **Most sessions will show nothing of the two new readings.** A game asks Streamline about
|
||||
its features while it starts, and FrameLedger is usually not in the game yet; the session then says the call was
|
||||
hooked and the game did not ask again — which is the expected answer, not a fault. They have been tested with
|
||||
FrameLedger's own test program and **have not been run in a real game**: this release is the first time either
|
||||
hook is put into one. What they give is Streamline's answer as the game received it — not FrameLedger's own check
|
||||
of the PC — and never the lists that answer points to (which buffers, which Vulkan extensions). A game that faults
|
||||
while it is closing can still read *ended normally* in a session measured from inside; that is written down, not
|
||||
changed. The two Cyberpunk 2077 sessions recorded on 0.1.0-beta.43 keep the line they were stored with. The cost
|
||||
was measured on the code itself: 15 and 21 billionths of a second per call while the option is on, under 1 while
|
||||
it is off, for calls a game makes a handful of times. Everything 0.1.0-beta.43's notes say is not yet done still
|
||||
stands.
|
||||
|
||||
**Updating from `0.1.0-beta.43`:** Help ▸ Check for updates, then *Restart to update* with no game running. **The
|
||||
terms are shown once: Privacy Policy 2.18**, which names the two new readings. No change to the ledger (schema 23),
|
||||
the detection rules stay at `2026.11.2`. **The code loaded into a game changed in this release**, so a game that
|
||||
was running during the update keeps the old part until it is started again.
|
||||
|
||||
### Added
|
||||
|
||||
- **Two more calls are hooked inside a game, only where Advanced metrics was asked for** (Advanced metrics train B,
|
||||
the third step): `slGetFeatureVersion` and `slGetFeatureRequirements` of `sl.interposer.dll` — what Streamline
|
||||
answers when a game asks which version a feature is and what it requires. The original call runs first and its
|
||||
answer is read only when it succeeded: the feature's Streamline and NGX versions; the graphics APIs it supports,
|
||||
whether V-Sync must be off and hardware-accelerated GPU scheduling on, how many threads, viewports and buffers,
|
||||
and the Windows and driver versions found beside the ones required. **The lists the answer points to — the
|
||||
buffer tags, the names of Vulkan extensions and features — are never followed.** As with `slSetConstants`,
|
||||
neither patch is made in a game no session has asked, and each stays for the life of the process once made. A
|
||||
game asks these while it starts, so the two rows are the first the Overlay patches — and most sessions, attached
|
||||
later, will still not see the calls. Nothing is shown of them yet: the Agent and the App read them in the next
|
||||
pull request. No layout change (5), no schema change (23).
|
||||
|
||||
- **A session shows which version each Streamline feature is, and what it requires** (Advanced metrics). Two
|
||||
catalog entries are now read inside the game: `sl.feature.versions` and `sl.feature.requirements` — Streamline's
|
||||
answers to the two questions a game asks about a feature, in NVIDIA's own names (`kFeatureDLSS_G · versionNGX`,
|
||||
`kFeatureDLSS · driverVersionRequired`). The line under the session says for each of the two calls whether it was
|
||||
read, not hooked, or — the usual case — *hooked — the game asks this while it starts, and did not ask again after
|
||||
FrameLedger attached*. **Most sessions will show nothing here**: a game asks before FrameLedger is in it. A game
|
||||
that asks later is read then, and a second session of a game that kept running keeps what the first read. The
|
||||
Agent's end-to-end tests now run a Streamline target as well as an FSR one.
|
||||
|
||||
### Changed
|
||||
|
||||
- **Privacy Policy 2.18**: it names what Streamline answers about a feature — the features asked about, their
|
||||
versions, what each requires — and what of that answer is never read (the lists it points to: the buffers' names,
|
||||
the names of Vulkan extensions and features); "two further calls" is four. The terms window shows once after the
|
||||
update. The Disclaimer stays 2.15.
|
||||
- **Switching hooking back on starts the count of early abnormal ends again** (owner decision D126). The count was
|
||||
never set back, so a game that had once been switched off — after two ends within 60 seconds of injection — was
|
||||
switched off again by every single such end after its user switched it on, under a reason that still said
|
||||
"twice". Seen on 2026-11-12: Lies of P, two ends in October, one crash of its own that day. Two are needed again
|
||||
each time. Nothing else about the rule moves: it only switches off, an anti-cheat block is never cleared, and the
|
||||
user-mode exception's trial keeps its own record.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **A field of view a game gives in degrees is no longer labelled radians** (Advanced metrics; owner decision
|
||||
D128). Cyberpunk 2077 gives NVIDIA Streamline 51–90 where the library expects radians, and the session read
|
||||
`51.0055 – 90 rad (2922.4° – 5156.6°)`. A value too large to be radians is now shown as the game gave it, with a
|
||||
line that says it is not radians, and is not converted. Sessions recorded on 0.1.0-beta.43 keep the line they
|
||||
were stored with.
|
||||
- **An FSR frame-generation configuration with no flag set says "None"** (Advanced metrics). The row was missing,
|
||||
where an upscale with no flag has always said so.
|
||||
- **The accuracy statement and the limitations no longer say that what a game tells Streamline, and how it
|
||||
configures FSR frame generation, have not been read from a real game**: they were, on 2026-11-12 — three games
|
||||
and one. What is still unconfirmed is named: the DLSS options, and a configuration that reaches FSR through
|
||||
AMD's 2.3 loader. A fault while a game is closing, which a session measured from inside the game does not see,
|
||||
is written down as a limit (owner decision D127: not changed in this release).
|
||||
@@ -1,80 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.45 was cut, 2026-11-12 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.45] - 2026-11-12
|
||||
|
||||
**The forty-fifth pre-release: what a game does with NVIDIA Streamline's features.** With **Advanced metrics** on,
|
||||
a session of a game measured from inside can now also keep, for each Streamline feature the game asks about or
|
||||
controls: whether Streamline says it is **supported** — in NVIDIA's own word, a refusal included — whether it is
|
||||
**loaded**, whether the game **switched it on or off** while it ran, how many times the game **allocated and
|
||||
freed** what the feature needs, and how many times it **shut Streamline down**. They come from six more calls,
|
||||
which FrameLedger hooks only once Advanced metrics has been asked for in that game. The pages that said most
|
||||
sessions would show nothing of 0.1.0-beta.44's two readings are corrected: the first real sessions read both in
|
||||
every Streamline game. The same unsigned installer: verify its hash against `SHA256SUMS.txt`, then *More info →
|
||||
Run anyway*.
|
||||
|
||||
**What it is not, yet.** The six new calls have been tested with FrameLedger's own test program and **have not
|
||||
been run in a real game**: this release is the first time any of them is patched in one, and it is six at once.
|
||||
Two of them sit on a game's way out — freeing a feature's resources, shutting Streamline down — and two of the
|
||||
games run so far already fault while closing without them; whether anything changes there is for the first real
|
||||
sessions to say. What is shown are **calls the game made after FrameLedger was in it**, counted to fifteen: not
|
||||
what the game did while it started, and not a statement that a feature ran or drew anything. **What a game
|
||||
started Streamline with is not read and will not be**: the game makes that call once, before FrameLedger can be
|
||||
inside it, and the Advanced page now says so instead of "a later release". Which graphics card a game asks about
|
||||
is never read. The cost was measured on the code itself: at most 13 billionths of a second per call while the
|
||||
option is on, under 2 while it is off, for calls a game makes a few times a second at most. A stop restores every
|
||||
patch, each taking about a sixth of a second, and a Streamline game with Advanced metrics on now has six more of
|
||||
them; the Overlay's log waits for them.
|
||||
Everything 0.1.0-beta.44's notes say is not yet done still stands.
|
||||
|
||||
**Updating from `0.1.0-beta.44`:** Help ▸ Check for updates, then *Restart to update* with no game running. **The
|
||||
terms are shown once: Privacy Policy 2.19**, which names the new readings and two things that are never read. No
|
||||
change to the ledger (schema 23), the detection rules stay at `2026.11.2`. **The code loaded into a game changed
|
||||
in this release**, so a game that was running during the update keeps the old part until it is started again.
|
||||
|
||||
### Added
|
||||
|
||||
- **Three more of Streamline's calls are hooked inside a game, only where Advanced metrics was asked for** (owner
|
||||
decisions D129–D131): `slIsFeatureSupported`, `slIsFeatureLoaded` and `slSetFeatureLoaded` — whether Streamline
|
||||
says a feature is supported (its answer, a refusal included), whether it is loaded, and the game switching a
|
||||
feature off and on while it runs. No vendor struct is read for these: the feature's id, a result code, a yes or
|
||||
no. **The adapter a game names when it asks whether a feature is supported is never read**, and the build now
|
||||
refuses code that names what identifies it. As with the four hooks before them, none of the three patches is made
|
||||
in a game no session has asked. Nothing is shown of them yet: the Agent and the App read them in a later pull
|
||||
request. No layout change (5), no schema change (23).
|
||||
- **And three more, counted only**: `slAllocateResources`, `slFreeResources` and `slShutdown` — how many times a
|
||||
game allocated and freed a feature's resources (up to fifteen each) and how many times it shut Streamline down.
|
||||
The feature's id is the only argument looked at; the two that sit on a game's way out note the call and then
|
||||
call the original, and run nothing after it. Six new calls in all in this release, each patched only where a
|
||||
session asked.
|
||||
- **`slInit` is not hooked, and will not be** (D129). A game starts Streamline once, before FrameLedger can be in
|
||||
it — also when FrameLedger starts the game itself — so a hook there would be a patch that reads nothing. The
|
||||
Advanced page's entry for what a game started Streamline with now gives that reason instead of "a later release".
|
||||
- **A session shows whether each Streamline feature is supported and loaded, and what the game did with it**
|
||||
(Advanced metrics). Two catalog entries are read from the six calls above: `sl.feature.support` — Streamline's
|
||||
answer by NVIDIA's own name (`kFeatureDLSS_G · slIsFeatureSupported` = `eOk`; a refusal is named, and it is an
|
||||
answer) and whether the feature is loaded — and `sl.feature.lifecycle` — the game switching a feature on, off or
|
||||
both, how many times it allocated and freed the feature's resources (`≥ 15` past fifteen), and how many times it
|
||||
shut Streamline down. The line under the session names the six calls in one sentence: read; hooked, the game did
|
||||
not make the call; not hooked. They begin when FrameLedger is in the game — what a game did while it started is
|
||||
not there — and they are calls the game made, not a statement that a feature ran. Not confirmed on a real game.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **A stop that restores many patches no longer leaves its last lines out of the Overlay's log.** Restoring a patch
|
||||
takes about 160 ms, and the wait for the stop's log lines was two seconds whatever the number of patches: with
|
||||
fifteen the log ended "the stop was still writing". The patches were restored; the log did not say so. The wait
|
||||
is now sized to the number of patches a game can hold.
|
||||
|
||||
### Changed
|
||||
|
||||
- **Privacy Policy 2.19**: it names, for each Streamline feature a game asks about or controls, whether Streamline
|
||||
says it is supported and loaded, the game switching it on or off, and how many times its resources were allocated
|
||||
and freed, and how many times the game shut Streamline down — and two more things that are never read: what
|
||||
identifies the graphics card a game hands over with its question, and the content of a graphics resource. "Four
|
||||
further calls" is ten. The terms window shows once after the update. The Disclaimer stays 2.15.
|
||||
- **The limitations, the accuracy statement and the user guide no longer say that most sessions will show nothing
|
||||
of what Streamline answers about a feature.** 0.1.0-beta.44's notes expected that, because a game asks while it
|
||||
starts. The first real sessions (2026-11-12, five games) read both answers in every Streamline session: the
|
||||
Unreal Engine games ask again later. The pages now say what was seen — and two things the readings showed: the
|
||||
version Streamline gives for a feature can be newer than the file in the game's folder, and a game that does not
|
||||
upscale through Streamline lists frame generation there and no upscaler. No code changes.
|
||||
@@ -1,42 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.46 was cut, 2026-11-13 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.46] - 2026-11-13
|
||||
|
||||
**The forty-sixth pre-release: hooks go into a game together, and come out together.** Putting a hook in or taking
|
||||
it out stops every thread of the game for a moment. Until now that happened once for every hook: in the first real
|
||||
sessions on 0.1.0-beta.45 the thirteen NVIDIA Streamline hooks took between 0.7 and 2.8 seconds of a game's start,
|
||||
and stopping a session took about a sixth of a second for each hook. The hooks FrameLedger finds something for at
|
||||
one moment are now put in under **one** stop of the game's threads, and a stop takes all of them out under one.
|
||||
This release is that change and nothing else in the part that runs inside a game; the pages are also brought up to
|
||||
date with what those first sessions showed. The same unsigned installer: verify its hash against `SHA256SUMS.txt`,
|
||||
then *More info → Run anyway*.
|
||||
|
||||
**What it is not, yet.** It has **not been run in a real game**. On FrameLedger's own test program nine hooks go
|
||||
in within 78–90 thousandths of a second where they took 0.6–0.7 seconds, and eighteen come out within 76–90 where
|
||||
they took 1.4–1.6 seconds; how long one stop of the threads is in a game with a few hundred of them, and whether
|
||||
any game minds its hooks arriving together, are for the first real sessions to say. Nothing new is read and
|
||||
nothing a hook reads has changed, so the terms are the ones you accepted. Of 0.1.0-beta.45's six new readings five
|
||||
have now been read in real games; no game run so far set up a feature's resources after FrameLedger was in it, so
|
||||
that row has not been seen. Everything 0.1.0-beta.45's notes say is not yet done still stands.
|
||||
|
||||
**Updating from `0.1.0-beta.45`:** Help ▸ Check for updates, then *Restart to update* with no game running. **The
|
||||
terms are not shown again** (Privacy Policy 2.19 as before). No change to the ledger (schema 23), the detection
|
||||
rules stay at `2026.11.2`. **The code loaded into a game changed in this release**, so a game that was running
|
||||
during the update keeps the old part until it is started again.
|
||||
|
||||
### Changed
|
||||
|
||||
- **Hooks go into a game together, and come out together** (owner decision D134). Putting a hook in or taking it
|
||||
out stops every thread of the game for a moment, and until now that happened once for every hook: the thirteen
|
||||
Streamline hooks took 0.7 to 2.8 seconds of a game's start in real sessions (2026-11-13), and stopping a session
|
||||
took about a sixth of a second for each hook — two to three seconds, sometimes on the thread that draws. The
|
||||
hooks a moment finds are now put in under **one** stop of the threads, and a stop takes all of them out under
|
||||
one. On FrameLedger's own test program: nine hooks in 78–90 ms where they took 0.6–0.7 s; eighteen out in
|
||||
76–90 ms where they took 1.4–1.6 s. What a hook reads and when it is installed are unchanged, and no hook's own
|
||||
code changed. The log of the part inside the game has a new line for each such moment (`PATCH_BATCH`, with the
|
||||
time it took and the number of hooks). **Not run in a real game yet.**
|
||||
|
||||
- **The limitations, the accuracy statement and the user guide say what the first real sessions on 0.1.0-beta.45
|
||||
showed** (2026-11-13, six games): five of its six new readings were read in real games — every Streamline game
|
||||
asked whether its features are supported — and no game allocated a feature's resources after FrameLedger was in
|
||||
it, so that row has not been seen. No code changes.
|
||||
@@ -1,92 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.47 was cut, 2026-11-14 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.47] - 2026-11-14
|
||||
|
||||
**The forty-seventh pre-release: with Advanced metrics on, FrameLedger reads NVIDIA's own report of where a frame's
|
||||
time goes.** On an NVIDIA card, in a Direct3D 12 game that uses NVIDIA Reflex, a session recorded with *Advanced
|
||||
metrics* on now also stores how long the graphics driver says each stage of a frame took — simulation, render
|
||||
submit, present, driver, the operating system's queue, the graphics card — as seven lines under *Latency* on the
|
||||
Advanced page, with a table of the driver's low-latency state. **They are the driver's numbers, not a measurement
|
||||
by FrameLedger**, and they are not the delay from a click to the screen. The same unsigned installer: verify its
|
||||
hash against `SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**This is the first release in which the part inside a game makes a call of its own.** Until now it only read what
|
||||
a game itself passed to the graphics calls FrameLedger intercepts. To read this report it asks the graphics driver,
|
||||
about once a second, on the game's own thread that presents its frames — two functions of the driver that only
|
||||
read. It reaches them through NVIDIA's library only where the game had already loaded it, and never loads that
|
||||
library itself; a copy sitting in the game's own folder is not the driver's and is not used. It is built to step
|
||||
back rather than disturb a game: a request that takes two thousandths of a second or more, or that goes wrong, is
|
||||
the last one until the game is closed, and the session says so. **With Advanced metrics off — the default — none
|
||||
of this happens.** The Disclaimer and the Privacy Policy say all of it; the terms window shows once.
|
||||
|
||||
**What it is not, yet.** **No real game has been read.** The reading was written and tested against FrameLedger's
|
||||
own test program with a stand-in for NVIDIA's library, and measured with a test tool against one driver on one
|
||||
card (GeForce RTX 5080, driver 32.0.16.2114): there a request takes about three millionths of a second, and none
|
||||
took a thousandth while the tool, like a game using Reflex, slept between frames. What a game's own threads, frame
|
||||
generation, another driver or another card do with it is for the first real sessions to say; a game that enforces
|
||||
Windows' Control Flow Guard on a driver that tool was not run against is not covered. On a busy PC the
|
||||
two-thousandths limit will now and then switch the reading off for a pause that was Windows' and not the driver's;
|
||||
the session then says *stopped* with the time, and the next start of the game reads again. The session summary's
|
||||
latency fields still read N/A, and nothing here is read on Direct3D 11, Vulkan or OpenGL. No test runs the whole
|
||||
path from the game to the ledger through the real capture agent; the Japanese texts are new and unreviewed.
|
||||
|
||||
**Also in this release.** The log of the part inside a game now says how a group of hooks went in or came out —
|
||||
in one go, or one hook at a time — after two groups in the first real sessions on 0.1.0-beta.46 took far longer than
|
||||
the rest and the log could not say why. And 0.1.0-beta.46's other half has now been seen in a real game: stopping
|
||||
the part inside a running game took all twenty-nine hooks out under one stop of 83–86 thousandths of a second,
|
||||
twice, and the game went on.
|
||||
|
||||
**Measured overhead this release.** A presented frame: one more read of one word; too small to measure on the
|
||||
test program. The request to the driver, once a second while Advanced metrics is on: 2.5–2.6 millionths of a second
|
||||
at the median after a frame that slept, 8–67 at worst, in three runs alone; 3.4 and 130 on a busy PC. Not measured
|
||||
in a game.
|
||||
|
||||
**Updating from `0.1.0-beta.46`:** Help ▸ Check for updates, then *Restart to update* with no game running. **The
|
||||
terms are shown once** — Privacy Policy 2.20 and Disclaimer 2.16. No change to the ledger (schema 23) or to the
|
||||
shared memory's layout (5); the detection rules stay at `2026.11.2`. **The code loaded into a game changed in this
|
||||
release**, so a game that was running during the update keeps the old part until it is started again.
|
||||
|
||||
### Changed
|
||||
|
||||
- **The log of the part inside a game says how a group of hooks went in or came out** (owner decision D137). Since
|
||||
0.1.0-beta.46 hooks are put into a game in groups, the game's threads stopped once for a group. In the owner's
|
||||
first sessions two groups took much longer than the others (0.6 s and 1.3 s against 0.1-0.3 s), and the log
|
||||
could not tell one long stop from a group that had to be finished one hook at a time. The `PATCH_BATCH` line now
|
||||
reads `install` or `restore` for a group that went in one go, and `install singly` or `restore singly`, with a
|
||||
count, for one that did not. Nothing else about hooking changed, and what a game is measured by is the same.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **For developers: a native test that is cut short no longer counts as passed.** The quality gate's native tests
|
||||
were judged by their exit code alone, and a test program that was stopped early with a clean exit code read as
|
||||
*Passed* - seen once, when security software removed the test program while the gate ran. Every native test now
|
||||
has to print the line it ends on, a test added without one stops the build's configure step, and four tests
|
||||
exist only to prove the rule goes red when it should. Nothing a user installs changed.
|
||||
|
||||
### Added
|
||||
|
||||
- **The part inside a game can read NVIDIA's own latency report, with Advanced metrics on** (owner decisions D132, D136,
|
||||
D138-D141). While a session records Advanced metrics, and only then, it asks the graphics driver about once a
|
||||
second for its report of a frame's stages - simulation, render submit, present, driver, the operating system's
|
||||
queue, the graphics card - and for its low-latency state. It is a call FrameLedger makes itself, on the thread
|
||||
that presents the game's frames, through NVIDIA's `nvapi64.dll` only where the game had already loaded it;
|
||||
Direct3D 12 only. A copy of that library sitting in the game's own folder is refused. A call that faults or takes
|
||||
two milliseconds is the last one until the game is closed. **The Advanced page shows it** under *Latency*: seven
|
||||
lines, one a stage, and a table of the driver's low-latency state; the line under a session says what became of
|
||||
the read - read, the driver reported no frame, not read and why, or stopped and why. They are the driver's
|
||||
numbers, not a measurement by FrameLedger, and no real game had been read when this was written. **Privacy
|
||||
Policy 2.20 and Disclaimer 2.16** say what is stored and what the part inside a game now does; the terms window
|
||||
will show once.
|
||||
|
||||
- **For developers: room in the shared memory for NVIDIA Reflex latency** (owner decisions D136, D138). Ten reserved
|
||||
words of the block that carries Advanced metrics from a game are now named for the driver's latency report -
|
||||
where the read stands, and a sum for each stage of a frame. Nothing writes them yet and nothing reads them; the
|
||||
shared memory's layout version did not change.
|
||||
|
||||
- **For developers, nothing a user installs: a probe for NVIDIA Reflex latency** (owner decision D132). An
|
||||
unshipped tool, `fl-probe-reflex`, and a stand-in `nvapi64.dll` among the test fixtures measure what it would take
|
||||
to read the driver's latency report from inside a game - on FrameLedger's own test program and against the
|
||||
installed driver, never in a game. What it found is `docs/spike-notes/31-reflex-route-d-harness.md`. A further
|
||||
leg (owner decision D139) measured the same reads while the probe itself used Reflex's sleep, as a game does:
|
||||
the reads do not wait behind it. The owner has said to go on to a real game (D136); that work is not in any
|
||||
release yet. Nothing in the App, the Agent or the part that runs inside a game changed.
|
||||
@@ -1,90 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.48 was cut, 2026-11-14 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.48] - 2026-11-14
|
||||
|
||||
**The forty-eighth pre-release: NVIDIA's latency report has now been read in real games, and what they showed is
|
||||
in it.** On the day 0.1.0-beta.47 came out the owner recorded eight sessions with *Advanced metrics* on. The
|
||||
report was read in Phantom Blade Zero and in Cyberpunk 2077, with frame generation on and off: the driver answered
|
||||
every second, the slowest request took 65 millionths of a second, nothing was switched off, and no game was
|
||||
disturbed that the logs can show. Two games that are not Direct3D 12 and one that never loaded NVIDIA's library
|
||||
were left alone, each with its one line saying why. The same unsigned installer: verify its hash against
|
||||
`SHA256SUMS.txt`, then *More info → Run anyway*.
|
||||
|
||||
**What the first game showed, and what this release does about it.** In Phantom Blade Zero the line called *GPU
|
||||
render* was longer than the whole frame — 16 thousandths of a second where the total was 5. That line runs from
|
||||
the moment the graphics card starts on a frame to the moment it ends, **and includes the time the card waited in
|
||||
between**. NVIDIA's driver also works out the figure without the waiting, and the time from one frame's end to the
|
||||
next. Both are in the report FrameLedger already asks for, and a session now stores them as **a second chart under
|
||||
*Latency*, with two lines**: *GPU active render* and *GPU frame time*. Nothing more is asked of the driver. The
|
||||
old line stays, under a name that says what it includes. **The stages of a frame overlap; they were never parts
|
||||
that add up to the total**, and the texts now say so.
|
||||
|
||||
**Three more things the sessions showed.**
|
||||
- The table of the driver's low-latency state kept only the *last* frame-generation multiplier: a session that
|
||||
generated frames at ×2 and ended in a menu showed 1. It now lists every value the session saw — *1, 2*.
|
||||
- **Sensors were read every 1.3 seconds where the setting says every second** — on the owner's PC, in nearly every
|
||||
session since the series began. The capture agent waited the whole interval *after* each reading, and a reading
|
||||
there takes about a third of a second. It now keeps the period. No chart was wrong, because every sample is
|
||||
stored with its own time; but a session now has about a third more samples, and readings of the latency report
|
||||
no longer fall between two of them. What makes a reading take that long there is not established.
|
||||
- A session could begin with the last reading of the session before it, in a game that kept running between the
|
||||
two. It no longer does.
|
||||
|
||||
**What it is not.** Two games on one driver and one card (GeForce RTX 5080, driver 32.0.16.2114) are not every
|
||||
game. The two new figures have not been seen from a real game yet: a driver may give neither, and the chart is
|
||||
then simply not there. Reflex switched off in a game's menu, and a game started with Advanced metrics off, have
|
||||
still not been tried on a real game. They remain the driver's numbers, not a measurement by FrameLedger, and not
|
||||
the delay from a click to the screen; the session summary's latency fields still read N/A. Nothing here is read
|
||||
on Direct3D 11, Vulkan or OpenGL. The Japanese texts are new and unreviewed.
|
||||
|
||||
**Measured overhead this release.** A presented frame: unchanged. The request to the driver, once a second while
|
||||
Advanced metrics is on: summing the two further figures adds about 36 billionths of a second to work that follows
|
||||
the request itself. In the real games of 2026-11-14 the slowest request took 20 to 65 millionths of a second.
|
||||
|
||||
**Updating from `0.1.0-beta.47`:** Help ▸ Check for updates, then *Restart to update* with no game running. **The
|
||||
terms are shown once** — Privacy Policy 2.21 and Disclaimer 2.17. No change to the ledger (schema 23) or to the
|
||||
shared memory's layout (5); the detection rules stay at `2026.11.2`. **The code loaded into a game changed in this
|
||||
release**, so a game that was running during the update keeps the old part until it is started again.
|
||||
|
||||
### Added
|
||||
|
||||
- **Two more lines from NVIDIA's latency report: how long the graphics card was really at work** (owner decision
|
||||
D142). In a real game the driver's *GPU render* stage turned out longer than the whole frame: it runs from the
|
||||
card's start to its end and includes the time the card waited. With Advanced metrics on, a session now also
|
||||
stores two figures the driver works out itself — **GPU active render**, the same stage without the waiting, and
|
||||
**GPU frame time**, from the end of one frame's work to the end of the next — as a second chart under *Latency*.
|
||||
They come from the report FrameLedger already asks the driver for; nothing more is asked. A driver may give
|
||||
neither, and the chart is then not there. Sessions recorded before this release do not have them.
|
||||
|
||||
- **For developers: the part inside a game reads two more figures of NVIDIA's latency report, and keeps every
|
||||
frame-generation multiplier a session saw** (owner decisions D142, D144). In a real game the driver's span between its two GPU marks was longer than the frame's whole
|
||||
— it includes the card's waiting. The driver's own *active* render time and its GPU frame time are members of
|
||||
the report FrameLedger already fetches; they are read from it, with **no further call into the driver**. Four
|
||||
reserved words of the shared memory carry them and the multipliers seen (layout 5 as it was). `fl_reflex_summary`
|
||||
and the injected `[latency]` cases hold it. Measured: +36 ns a read, once a second.
|
||||
|
||||
### Changed
|
||||
|
||||
- **The *GPU render* line says what it includes** (owner decision D143): *GPU render, start to end (idle time
|
||||
included)*, in the three languages. The numbers are the same.
|
||||
- **The driver's frame-generation multiplier is every value the session saw** (owner decision D144). The table of
|
||||
the driver's low-latency state kept only the last one: a session that generated frames at ×2 and ended in a menu
|
||||
showed 1. It now shows *1, 2*. Sessions already recorded keep what they stored.
|
||||
- **The texts say what was read** (owner decision D145). The accuracy statement, the README and the guide said no
|
||||
real game had been read; two have been, on one driver. They also say now that the stages overlap and do not add
|
||||
up to the total. **Privacy Policy 2.21** names the two new averages; **Disclaimer 2.17** changes only with the
|
||||
accuracy statement it carries. The terms window shows once.
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Sensors were read less often than the setting says** (owner decision D146). With the sensor interval at
|
||||
1000 ms, nearly every session on the owner's PC got a sample every 1.3 seconds: the Agent waited the whole
|
||||
interval *after* each reading, and a reading there takes about a third of a second (what in it does is not
|
||||
established; on a PC where the Agent is not run as administrator it takes a millisecond, and the samples were
|
||||
already a second apart). It now keeps the period. No chart was wrong — every sample is stored with its own time — but a session
|
||||
has about a third more samples now, and about a quarter of the readings of NVIDIA's latency report no longer
|
||||
fall between two samples. For developers: `sensor_blobs.hz` was the constant 1 and is now the rate the
|
||||
session's samples had.
|
||||
- **A session could start with the last read of the session before it.** In a game that kept running between two
|
||||
sessions, a read of the driver's latency report that ended after the first session's last tick was taken as the
|
||||
second session's first point. A new session now drops it.
|
||||
@@ -1,79 +0,0 @@
|
||||
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.49 was cut, 2026-11-14 (D66). CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-beta.49] - 2026-11-14
|
||||
|
||||
**The forty-ninth pre-release: what the owner's sessions on 0.1.0-beta.48 showed, the same day.** Eighteen
|
||||
sessions, sixteen of them with *Advanced metrics* on — Phantom Blade Zero, Cyberpunk 2077 and Clair Obscur:
|
||||
Expedition 33, with frame generation on and off, with Reflex on and off. Sensors are now read every second; NVIDIA's driver gave both
|
||||
of its own GPU times in every report of every game; the table lists every frame-generation multiplier; a game
|
||||
started with the option off was left alone; the driver was read just the same with Reflex off; and the owner's
|
||||
word on how the games felt: no hitch. The same unsigned installer: verify its hash against `SHA256SUMS.txt`, then
|
||||
*More info → Run anyway*. **No legal text changed, so the terms window does not appear.**
|
||||
|
||||
**Two things those sessions showed, and what this release does about each.**
|
||||
- **The *Latency* charts had holes.** After a session's first reading, between 0.4 and 16 % of its samples had
|
||||
none. There were two reasons, one on each side. The part inside the game did its once-a-second round a second
|
||||
*after* the last one finished — so it fell behind — and whenever the game loaded a library it was woken early,
|
||||
published what it had, and asked the driver for nothing new. And the capture agent kept one reading until a
|
||||
sample could carry it, and replaced it if another arrived first. Both are mended: the round inside the game is
|
||||
now due at fixed moments, and the agent keeps the reading that waits.
|
||||
- **In Cyberpunk 2077 without frame generation, NVIDIA's *GPU active render* time is longer than the time from the
|
||||
card's start on a frame to its end** — which should contain it. Nothing stored can say whether that is the
|
||||
driver's arithmetic or the way FrameLedger averages the two (one over every frame, one only over the frames that
|
||||
gave a time). **This release changes no number you see.** It counts, frame by frame, how the two stand to each
|
||||
other, and writes the counts to the game component's own log, together with the driver's low-latency state and
|
||||
its frame-generation multiplier — the owner asked that Reflex and frame generation always be read together. The
|
||||
next sessions say which it is; what to do about it is decided then.
|
||||
|
||||
**What it is not.** Not a promise that every sample now carries a reading: with both sides on one second a slip
|
||||
can still leave one without, and the log says how often. The reason given for the agent's half was read from the
|
||||
code and fits the pattern in the ledger; it has not been measured in a session. Nothing here is read on
|
||||
Direct3D 11, Vulkan or OpenGL, and the figures remain the driver's, not a measurement by FrameLedger. The log of
|
||||
the component inside a game grows by about seven lines a minute while *Advanced metrics* reads the driver — a few
|
||||
tens of kilobytes an hour — and a bug report carries those logs, as it always carried them. A game that closes by
|
||||
itself loses the last batch of counts, under a minute.
|
||||
|
||||
**Measured overhead this release.** A presented frame: unchanged — no line that runs with a present was touched.
|
||||
The reading of the driver's report, once a second while a session with *Advanced metrics* runs in a Direct3D 12
|
||||
game: 65 billionths of a second more (424–435 → 490–499 billionths, the same instrument as before), after the
|
||||
request's own time has been taken. The background thread inside the game: ten readings in 9 996 ms, twenty in
|
||||
20 002, sixty in 59 997 on the test harness — and the same with another thread waking it eighteen thousand times
|
||||
in ten seconds, where the code before it published 35 720 times in eight seconds and read nine times.
|
||||
|
||||
### Added
|
||||
|
||||
- **The frames NVIDIA's latency report gives are counted, for the Overlay's own log** (owner decisions D148,
|
||||
D151; nothing new is stored, shown, asked of the driver or read from its report). The owner's sessions on
|
||||
0.1.0-beta.48 showed both of the driver's own GPU times in two games — and in Cyberpunk 2077 without frame
|
||||
generation an *active render* time longer than the span from the card's start on a frame to its end, which the
|
||||
two averages cannot explain: one is over every frame, one only over the frames that gave a time. While a session
|
||||
with *Advanced metrics* reads the driver, the Overlay now places each frame by its own two numbers and writes
|
||||
the counts to `overlay-<pid>-….log` as `LATENCY_FRAMES` lines, in batches that each belong to **one state of
|
||||
the driver's low-latency status and its frame-generation multiplier** — the counts are read together with
|
||||
Reflex and frame generation, never apart. About six lines a minute; a game that exits by itself loses the last
|
||||
batch, under a minute. A bug report carries those logs, as it carried them before. Measured: 65 billionths of a
|
||||
second more for each reading of the report, once a second; a presented frame costs what it did.
|
||||
|
||||
### Changed
|
||||
|
||||
- **The guide says whose switches the latency table shows**: the driver's, not the game's menu. `bLowLatencyMode`
|
||||
is also on when *Low Latency Mode* is set for the game in the NVIDIA App, and `bUseGameSleep` says whether the
|
||||
game itself paces its frames through Reflex — in some games only with frame generation on (the owner's word,
|
||||
2026-11-14, and what Clair Obscur's sessions of that afternoon read).
|
||||
|
||||
### Fixed
|
||||
|
||||
- **NVIDIA's latency report is read on a grid of one second, and a busy loader no longer leaves holes in it**
|
||||
(owner decision D150; the Overlay's half). After a session's first report, 0.4 to 16 % of its samples carried
|
||||
none — the *Latency* charts had gaps. The Overlay's background thread waited a second *after* each round of its
|
||||
work, so it fell behind the capture agent, which samples exactly every second; and whenever the game loaded a
|
||||
library that thread was woken early, published what it had and asked for no new reading, so the round after it
|
||||
had nothing to publish. Its once-a-second round is now due at fixed moments whatever the work took, and a round
|
||||
woken early no longer publishes or takes a reading. Two readings are never less than half a second apart.
|
||||
Nothing on a game's own threads changed.
|
||||
- **A reading that waits for a sample is no longer overwritten by the next one** (D150; the capture agent's
|
||||
half). The agent kept one reading from the game until a sensor sample could carry it, and replaced it when
|
||||
another arrived first. When a reading landed just after a sample, that sample went without and a reading was
|
||||
lost a little later — in one session of the owner's, one sample in five for four minutes. Two readings may now
|
||||
wait and the older is stored first; a point can stand up to a second after its reading was taken. With the
|
||||
sensor interval above one second, not every reading is stored, as before.
|
||||
@@ -1,205 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.37
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.38 was cut, 2026-11-11 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then.*
|
||||
|
||||
## **START HERE** — 2026-11-11, 0.1.0-beta.37: the main line on .NET 11, what an alpha is now, and why no C# 15 yet
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.37.md`; this is what no other file carries.* The owner, with two screenshots — a
|
||||
Qodana Ultimate licence in the JetBrains console, and the Qodana Cloud project's setup page: "Bạn có thể bắt đầu với phiên
|
||||
cải tiến cho .net 11 và set up cho qodana cho tất cả ngôn ngữ (gói ultimate) nhé." The session D92 had left for after
|
||||
.NET 11's release (2026-11-10), and Qodana for every language on the Ultimate licence. One plan, approved whole, in
|
||||
three parts: **beta.37** (#376 the move, #379 what an alpha is, #380 .NET 11's API and the C# 15 finding, and this
|
||||
release) → **alpha.4** → **Qodana Ultimate in two reports**. This section is the first part; the other two follow it on
|
||||
`main` the same way.
|
||||
|
||||
**Decisions (asked while planning, do not re-ask):**
|
||||
|
||||
- **D94 — the main line moves to .NET 11 now.** Asked whether the betas move or only alpha.4 — with
|
||||
`20_OPEN_QUESTIONS` §G's table quoted: two alphas on the released runtime and an owner's run of a hooked title first —
|
||||
the owner chose "Chuyển main sang .NET 11 ngay". Condition (a) of that table was **set aside, not met**;
|
||||
`12_BUILD` §The main line's .NET says what stood in for it, and owner-only item 34 is the run it asked for.
|
||||
- **D95 — Windows 10 22H2 is not blocked, and is stated as untested and unsupported** ("Vẫn chạy, ghi rõ không được hỗ
|
||||
trợ"). NFR-8 is amended; a processor needs SSE4.2 and POPCNT.
|
||||
- **D96 — C# 15 in the same release** ("Áp dụng cả C# 15 ngay trong beta.37"). The plan narrowed it in writing, and was
|
||||
approved with that: a construct only where the build, CodeQL and Qodana all read it.
|
||||
- **D97 — all three legal texts reworded** ("Sửa cả ba văn bản"): EULA 1.7, Disclaimer 2.14, Alpha notice 1.1. Their
|
||||
text was in the plan and approved with it.
|
||||
- **D98 — alpha.4, then the alpha line rests** until a newer .NET has a preview ("alpha.4 rồi nghỉ tới .NET 12
|
||||
Preview").
|
||||
- **The order**: beta.37 → alpha.4 first, Qodana after; and Qodana in **two reports from the start** (the third part's
|
||||
decision, D99).
|
||||
|
||||
**Choices made here:**
|
||||
|
||||
- **No C# 15 construct is used, although the owner asked for them.** The rule decided it, not a preference:
|
||||
ReSharper's engine, which Qodana runs, reads none of the four (`13_CI_CD` §C# 15 and the analyses, `spike-notes`
|
||||
§29). Unions would not have been the form in any case — the SDK's own CA1815 asks every union to hand-write its
|
||||
equality, and the shapes that wanted one are closed record hierarchies. What the release takes is API.
|
||||
- **.NET 11's `IHost.RunAsync` is accepted, not wrapped**: a failed background service now ends the Agent through its
|
||||
crash report. A catch there would hide a fault, and could not reproduce .NET 10's exit exactly either.
|
||||
- **A resting alpha says so in the build, not only in its notes**: the anti-cheat list reaches a user only inside a
|
||||
release, so an alpha nobody updates carries an ageing one. `FlAlphaLineRests` is stamped on both lines; the `alpha`
|
||||
branch sets it to false when it next tries a .NET.
|
||||
- **"A prerelease .NET" is said only by a build that runs on one**, read from the runtime's own description — the next
|
||||
preview alpha says it again with no change to the code.
|
||||
- **`release.yml` names the .NET 10 runtime `vpk` needs**, rather than relying on the hosted image carrying one.
|
||||
- **The Community Qodana job was kept alive across the move** by installing the SDK into its container — an interim;
|
||||
the Ultimate linter replaces the job in the third part.
|
||||
- **The 2026-10-31 forms stay where they read as well** (`json.AsSpan().TrimStart().StartsWith('[')` avoids a string):
|
||||
.NET 11's `char` overloads replaced a span only where the span was there for .NET 10's sake.
|
||||
|
||||
**Measured on the way** (`spike-notes` §28 and §29): the gate on SDK 11.0.100 — two analyzer sites beyond RC3's
|
||||
twenty-one, both in tests written after the last alpha; `IHost.RunAsync` rethrowing, observed for the first time; the
|
||||
first delta across two runtime majors (372 of 443 files patched, 72.6 MB on the rehearsal); `main`'s first full CodeQL
|
||||
C# analysis on `net11.0` (1,221 of 1,221 files, the same 23 unresolved `Windows.Win32` types as on .NET 10); the
|
||||
SonarScanner 12.0.0 on the 11.0 runtime; InspectCode 2026.2.3.1 and 2026.3.0 against each C# 15 construct.
|
||||
|
||||
**Traps met on the way:**
|
||||
|
||||
- **A pull request's CodeQL C# run is an overlay analysis**: it extracts the changed files on top of `main`'s cached
|
||||
database, and its "scanned N out of N" is `main`'s baseline. #376 wrote "CodeQL reads `net11.0` whole" from one and
|
||||
was corrected, dated, two pull requests later with `main`'s own run. For anything the extractor has not met, dispatch
|
||||
`codeql.yml` on the branch (it takes `workflow_dispatch` since #380).
|
||||
- **`ShmDrainIntegrationTests.TheGuardInjectsTheOverlayAndTheReaderDrainsRealFrames` failed once on the dev box** —
|
||||
"our own harness must not start matching the blocklist mid-run": the guard's re-scan refused the harness in one gate
|
||||
run of five. The class passed three times in a row straight after and no guard code had changed; not looked into.
|
||||
- **A wiki page names no version** (`wiki-check`): "since 0.1.0-alpha.4" in `wiki/Releasing.md` was red. The guide's
|
||||
pages may.
|
||||
- **The runner queue**: with three workflows per pull request and a probe's pull request open beside the train,
|
||||
`check` waited about 25 minutes for a runner. Cancel a probe's runs once it has told what it can.
|
||||
- **A Bash heredoc halves the backslashes** of an inline Python regex — write the script with the Write tool.
|
||||
- **`x.Should().NotBeNull(); x!.Member`**: ReSharper reads the `!` as redundant (Qodana's one finding on #376) and the
|
||||
compiler wants it. Keep the value the assertion needs, not the object.
|
||||
- **CA2025** on a lambda that captures a `using` variable in a test: await inside a `try`, assert after.
|
||||
- **A local gate reseeds `%LOCALAPPDATA%\FrameLedger\rules`** while the owner's installed copy runs beside it: the
|
||||
files were hashed before and after every gate (identical each time — the repository's rules were the installed ones).
|
||||
|
||||
**The release (the tag, 2026-11-11).** Rehearsed first (`release.yml` dispatched on the release branch, run
|
||||
42926539241), then the signed tag `v0.1.0-beta.37` on `1a7fbf3`: run 42930394186, published 2026-11-11T00:36:54Z.
|
||||
Eight assets, the seven listed in `SHA256SUMS.txt` equal to the digests GitHub computed; `FL_BUILD_ID v0.1.0-beta.37`
|
||||
in the shipped natives. The delta across two major runtimes exists — the stop condition the plan had named: "Delta
|
||||
processed 0443 files. 0373 patched, 0070 unchanged, 0009 new, 0017 removed", 72,681,960 bytes beside a full package of
|
||||
110,325,368. The wiki was published by its own run (42932792575).
|
||||
|
||||
**Owner-only:** item 34 — beta.37 on real hardware, a hooked session on .NET 11.0.0, and Windows 10 if a PC with it is
|
||||
at hand.
|
||||
|
||||
### 0.1.0-alpha.4 — the fourth alpha, the same day, and the last for now (D98)
|
||||
|
||||
`alpha` takes main at this pull request — `v0.1.0-beta.37` and these notes, no other change — by a merge commit. **This
|
||||
sync is not like the three before it**: main now holds what the switch held (`global.json`, the TFM, the three
|
||||
packages, `legal/licenses/nuget/`, the *Transitive* row), so every switch file conflicts, and each is resolved by
|
||||
taking main's — the branch's RC3 lines go, `RELEASE_LINE` stays `alpha`, and `git diff --name-only origin/main` on the
|
||||
merged tree must print that one name. Its gate must pass on `alpha` before the pull request is merged by hand (the
|
||||
branch has no auto-merge); the release runs from the signed tag `v0.1.0-alpha.4` on `alpha`, with its delta from
|
||||
alpha.3. Its notes are `docs/changelog/0.1.0-alpha.4.md`: the warning, and that it is the last alpha for now.
|
||||
|
||||
- **After it the line rests** (`12_BUILD` §The alpha line): no sync follows a beta and no alpha is cut until a newer
|
||||
.NET has a preview. `FlAlphaLineRests` in `Directory.Build.props` says so to the build; the next trial sets it to
|
||||
`false` on `alpha` with the rest of the switch.
|
||||
- **What a resting alpha costs its user** is in its notes, the guide and its banner: no update, the anti-cheat list
|
||||
included; and once ten betas have followed it, a copy of alpha.3 or older no longer finds alpha.4 (Velopack reads
|
||||
the newest ten releases).
|
||||
|
||||
**The sync and the release (2026-11-11).** #382 put the notes on main (`428b723`); #383 merged main into `alpha` by
|
||||
hand (`134115b`): twenty-seven conflicts, every one resolved to main's side, and `git diff --name-only origin/main
|
||||
origin/alpha` prints `RELEASE_LINE` alone. Rehearsed on `alpha` (run 42933603983: channel `alpha`, a delta from
|
||||
alpha.3), then the signed tag `v0.1.0-alpha.4`: run 42935876535, published 2026-11-11T01:16:22Z as *FrameLedger
|
||||
0.1.0-alpha.4 (experimental alpha)*, a pre-release. Eight assets, seven of seven digests equal; "Delta processed 0448
|
||||
files. 0369 patched, 0079 unchanged, 0004 new, 0005 removed", 18,207,557 bytes; `FrameLedger.App-alpha-Setup.exe`,
|
||||
`releases.alpha.json`; the wiki run skipped, as it does for an alpha.
|
||||
|
||||
- **One tag push started two release runs** (42935876535 and 42935878584, both `push`, created in the same second;
|
||||
the tag was pushed once). `release.yml`'s concurrency group made the second wait for the first, and it then began
|
||||
the whole build again. It was cancelled once the first had published: it could only have ended red, at
|
||||
`gh release create` on a release that existed. If a tag ever shows two runs, let the first finish, verify the
|
||||
release, then cancel the other.
|
||||
|
||||
**Owner-only:** item 35 — the fourth alpha on real hardware, and the beta installed over it.
|
||||
|
||||
|
||||
### Qodana for .NET on the Ultimate licence — the managed report (D99, D100)
|
||||
|
||||
*Status is `docs/13_CI_CD.md` §Qodana and `CHANGELOG.md`; this is what no other file carries.* The third part of the
|
||||
plan, in two pull requests: this one moves the existing job to Qodana for .NET (Rider's engine, native on a Windows
|
||||
runner) and settles what it reports over the managed code; the next adds the C++ as a second report.
|
||||
|
||||
**Decisions:**
|
||||
|
||||
- **D99 — two reports from the start** ("Hai báo cáo ngay từ đầu"). The owner made a second Qodana Cloud project,
|
||||
`frameledger-cpp`, and the secret `QODANA_TOKEN_NATIVE`; the managed report goes to `frameledger` with
|
||||
`QODANA_TOKEN`. Both secrets are the owner's; no token was ever read or handled here.
|
||||
- **D100 — where an inspection is switched off** (the plan's design, approved with it; it amends D93's "never in
|
||||
`qodana.yaml`"): in the place the engine that raised it reads — one of ReSharper's in `.editorconfig`; what has no
|
||||
key there in `qodana.yaml`. Hints are off as a severity. In code loaded into a game only defects are fixed.
|
||||
|
||||
**Choices made here:**
|
||||
|
||||
- **JetBrains' security rules stay on, scoped by path — which took four runs to find.** Every result was read first
|
||||
(the table in `13_CI_CD` §Qodana), and one place hardened (`ShellUrlOpener` refuses anything but `http`, `https`
|
||||
and `mailto`). Then the files read had to be told to the linter, and a rule's own id is honoured nowhere:
|
||||
`ignore`, an `exclude` path and `enabled: false` each left all 36 results standing. The report's own
|
||||
`log/effective.profile.xml` and `qodana_inspections_summary.csv` gave the answer — one inspection,
|
||||
`OpenGrepInspection`, produces every rule's results, and it does take a path. Between the third run and the
|
||||
fourth the rules were written as off, with a test in their place; the test stayed (`ProcessStartSitesTests`, in
|
||||
the gate, and wider than the rule), the rules came back on.
|
||||
- **`PrimaryDisplay.cs` was not changed to please the linter.** Its six results come from an internal assertion in
|
||||
this linter's build (in the job's `backend.log`), not from the file; the first guess — that the engine misreads an
|
||||
`unsafe` tuple — was wrong, and a rewrite made on it was reverted. Two inspections are excluded for that one file,
|
||||
to be removed when a linter build reads it.
|
||||
- **What the Ultimate licence offers and this job does not use**: quick-fixes (the job cannot push, on purpose), code
|
||||
coverage in Qodana, FlexInspect. If the licence lapses the job is red and advisory; the way back is in `qodana.yaml`.
|
||||
|
||||
**Traps:**
|
||||
|
||||
- **A security rule's id is not an inspection.** The OpenGrep plugin's rules all report through
|
||||
`OpenGrepInspection`; only that name works in `qodana.yaml`, and only by path. Read
|
||||
`log/qodana_inspections_summary.csv` in the report artifact to see which inspection produced a result before
|
||||
spending a run on a guess.
|
||||
- **A report artifact is a zip inside the download, with backslash paths**: `unzip` extracts it and exits non-zero
|
||||
on the warnings, so do not chain on its exit code.
|
||||
- **A linter result can be the linter's fault**: read the job's log directory (the report artifact carries it) for an
|
||||
`AssertionException` before changing the code it points at.
|
||||
- **A Qodana run of the managed job takes fifteen to seventeen minutes**, most of it the scan; a pull request's own run
|
||||
reads the whole solution (`pr-mode: false`), so there is no quick partial run to iterate on.
|
||||
|
||||
**Then:** the native report, in the pull request after it — the next section.
|
||||
|
||||
|
||||
### Qodana — the native report: the C++ through a solution CMake writes (D99, D100)
|
||||
|
||||
*Status is `docs/13_CI_CD.md` §Qodana and `CHANGELOG.md`; this is what no other file carries.* The second pull request
|
||||
of the third part: the job `native`, `qodana-native.yaml`, the preset `x64-vs-analysis`, fifty-four `.editorconfig`
|
||||
lines for the C++ and eleven small fixes outside code loaded into a game.
|
||||
|
||||
**Choices made here:**
|
||||
|
||||
- **One linter for both reports.** Qodana for .NET is the only linter of JetBrains' that reads this C++ (MSVC-only;
|
||||
`qodana-cpp` and `qodana-clang` are Linux images), and it wants a Visual Studio solution — so CMake writes one. The
|
||||
generated solution is never built from, beyond the one header a build generates.
|
||||
- **No `.clang-tidy` file.** The plan had expected one. Every clang-tidy check and clang diagnostic the engine runs
|
||||
has an `.editorconfig` key of ReSharper's, so D100's "where the engine reads" is one file for all of the C++, and
|
||||
the repository gains no clang-tidy configuration that a developer's editor would start obeying.
|
||||
- **Most of what it reported is not a fault, and the settings say why, line by line**: clang's opinion of code only
|
||||
MSVC builds; the engine misreading `atomic_ref`, zero-initialised API structures and constexpr tests; proposals of
|
||||
a newer idiom. Eleven things were fixed. **In code loaded into a game nothing was changed**: no defect was found
|
||||
there.
|
||||
- **`LogNoteW` (`FrameLedger.Overlay/src/dllmain.cpp`) is dead code, and it is still there — the owner's call.**
|
||||
Nothing calls it. D100 changes code loaded into a game for a defect only, and an unused function is not one, so
|
||||
it was not removed on a linter's word; `.editorconfig` leaves that one file unread for an unused function, in a
|
||||
section that says to remove it with the function. Removing it is eleven lines with no caller: a pull request of
|
||||
its own, whose overhead statement is that the function was never reached.
|
||||
- **"Possibly unused `#include`" is off, not obeyed.** Ten of the twelve reported outside the game are a file
|
||||
including what it uses (`<cstring>` for `std::memset`) although `<windows.h>` already brought it; removing them
|
||||
would have made the files depend on an accident.
|
||||
|
||||
**Traps:**
|
||||
|
||||
- **InspectCode cannot load the native solution on the owner's PC** (Visual Studio 18 Insiders' MSBuild crashes it,
|
||||
2026.2.3.1 and 2026.3.0 alike), so C++ results are read from CI: dispatch `qodana.yml` on the branch, download
|
||||
`qodana-report-native`, unzip the inner `qodana-report.zip`.
|
||||
- **A file compiled into three targets is reported three times**: count distinct results (rule, file, line), not rows.
|
||||
- **A shortened line is a clang-format change two lines away**: the gate's clang-format step failed on an alignment
|
||||
that the edit above it had made possible. Run clang-format on every native file touched before the gate.
|
||||
- **Do not switch branches while a gate runs** — a probe branch was made during a local native build, which changed
|
||||
and restored two sources under it. Nothing came of it; the next gate was run on a still tree.
|
||||
@@ -1,104 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.38
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.39 was cut, 2026-11-11 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`.*
|
||||
|
||||
## **START HERE** — 2026-11-11, 0.1.0-beta.38: Qodana Ultimate in two reports — and the next work is the owner's "Thông số nâng cao"
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.38.md`; this is what no other file carries.* This release closes the plan of
|
||||
2026-11-11 — **beta.37** → **alpha.4** → **Qodana Ultimate in two reports**. The plan was one session's, and its START
|
||||
HERE was moved whole: all three parts, the decisions D94–D100, the choices and the traps are
|
||||
[`handoff/history/0.1.0-beta.37.md`](handoff/history/0.1.0-beta.37.md) — the two Qodana sections are its last two.
|
||||
#384 moved the managed job to Qodana for .NET and settled what it reports; #385 added the C++ as a second report; this
|
||||
release ships the one change to shipped code that came of it: the App's link opener refuses anything but a web or a
|
||||
mail address.
|
||||
|
||||
### NEXT — the owner's request of 2026-11-11, for the session(s) after this one
|
||||
|
||||
Sent while this session was still running, and recorded here as it was written:
|
||||
|
||||
> "Xong phiên này, bạn cập nhật (những) phiên tiếp theo với các phiên bản về Setting "Thông số nâng cao" hoặc tương tự
|
||||
> và hiển thị tại 1 navigation riêng, khai thác số liệu, dữ liệu, biểu đồ mức tối đa, toản bộ mà các header `.h` của
|
||||
> Streamline và NVAPI hoặc pawnIO có thể sử dụng và hiển thị nhé."
|
||||
|
||||
That is: once this session is done, the following session or sessions — and their versions — are about a setting
|
||||
called *"Thông số nâng cao"* (advanced metrics) or similar, shown in **a navigation item of its own**, that exploits
|
||||
to the maximum the numbers, the data and the charts that the `.h` headers of **Streamline** and **NVAPI**, or
|
||||
**PawnIO**, make available.
|
||||
|
||||
**Nothing of it was designed or begun here.** It is a new task, and it starts the way every train does — a plan, with
|
||||
the owner's decisions asked while planning. What follows is this session's reading, not the owner's words:
|
||||
|
||||
- **An inventory comes first, from the headers in the tree**: `src/native/third_party/streamline`, `nvapi`,
|
||||
`fidelityfx`; and what LibreHardwareMonitorLib reads through PawnIO (CPU and board sensors — optional, elevated
|
||||
only). For each item: what it is, and **where it can be read from** — the Agent's own process (NVAPI through
|
||||
`FrameLedger.NvapiBridge`, LibreHardwareMonitor) or only inside the game, through a hook (Streamline).
|
||||
- **Anything read inside a game is a hook**, and the rules that govern hooks are not this feature's to bend: rules 4
|
||||
and 5, `17_HOOK_ENGINE` §Hook inventory, the overhead stated, the open S-series of `20_OPEN_QUESTIONS`; the
|
||||
anti-cheat guard and rule 2 untouched. Rule 6 governs any frame rate it shows beside frame generation, rule 7 any
|
||||
Yes/No it shows, and rule 8 says it calls nothing on the network.
|
||||
- **Questions that are the owner's**: on or off by default; what is stored in the ledger (a schema change, the size
|
||||
of a session) and what is shown live only; what a PC without an NVIDIA card shows (N/A, never a guess); whether
|
||||
the page asks for the elevation PawnIO needs; how many releases, and in what order.
|
||||
- **What a new page owes**: strings in `en`, `vi`, `ja`; `ACCESSIBILITY.md` §For contributors for the page and each
|
||||
chart; `LIMITATIONS.md` and the guide; `08_UI`.
|
||||
|
||||
#### Planned 2026-11-11, and approved by the owner — four trains, the first begun
|
||||
|
||||
The plan was made the same day, the owner's decisions asked while planning. **The design, the decisions D101–D108 and
|
||||
the inventory are [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced metrics**; what follows is only what that
|
||||
section does not carry — the order, and what was asked.
|
||||
|
||||
- **The owner's four answers.** (1) Inside the game: **everything, in stages — and the refusal of 2026-08-09 is
|
||||
re-examined**, not taken as final. (2) **Stored in full with the session.** (3) **Off by default, and off means
|
||||
nothing more is read or stored**; the navigation item is hidden. (4) PawnIO: **the page says what is missing and
|
||||
links to the admin mode's setting** (D34); it never asks for the rights itself.
|
||||
- **Four trains, one release each, in this order**: **A** (0.1.0-beta.39) what the Agent can read — NVAPI,
|
||||
LibreHardwareMonitor — with storage and the page, **and nothing changed in code loaded into a game**; **B**
|
||||
(beta.40) inside the game, on calls already hooked and on functions Streamline exports, shared-memory layout 5;
|
||||
**C** (beta.41) Reflex latency, after a spike; **D** (beta.42) the Streamline state behind `slGetFeatureFunction`,
|
||||
after a spike. **Why this order**: A needs no hook, so it ships the page, the storage and the option first and
|
||||
every later train only fills rows; B is hooks of a kind already built; C and D are routes nobody has proven safe,
|
||||
and each ends in the owner's go or no.
|
||||
- **The approval covers train A whole** — its eight pull requests through the release. **B, C and D each begin with a
|
||||
plan of their own**, their decisions asked then. For D the owner will be asked one thing nothing else has needed:
|
||||
handing the game a wrapper in place of the function it asked for is a write, and rule 4 as written forbids it.
|
||||
- **Train A's pull requests**: (1) decisions, inventory, the catalog; (2) the NVAPI bridge's ABI 3 and the read-only
|
||||
gate; (3) LibreHardwareMonitor's groups and the shared reader, not yet composed; (4) the `.partial` chunks and
|
||||
schema 0023, produced by nobody yet; (5) the option goes live, with Privacy 2.15; (6) the pipe request and the
|
||||
App's feed; (7) the page, the navigation item, Ctrl+6; (8) the release. A setting and its guide text, a navigation
|
||||
item and its guide text, a schema script and its writer each land in ONE pull request — the guide tests, the
|
||||
viewer-mode test and the registry test are red otherwise.
|
||||
- **What the owner will be asked to run** (the release's owner-only item): the NVAPI rows on the RTX 5080 — CI has no
|
||||
driver and never takes that branch; one run as administrator with PawnIO, which is also the first there has ever
|
||||
been (`20_OPEN_QUESTIONS` §M10); the Agent's processor time and memory with the option on and off (NFR-2).
|
||||
- **A trap already paid for**: LibreHardwareMonitor's storage group may touch every drive when it opens, and this
|
||||
PC once had a failing USB drive. If the group cannot be opened without touching removable drives, storage stays
|
||||
N/A in beta.39 — decided before the first run, not after it. **It cannot (read in the library's source,
|
||||
2026-11-11), so it is not opened**: a drive's temperature reads N/A in beta.39, and the reason is on the page.
|
||||
- **Measure before composing.** `FrameLedger.CaptureHost probe-advanced` ran the reader on this PC before any Agent
|
||||
code used it, and found the sensor library's refresh at 14 ms of processor time — so the reader reads it every
|
||||
fifth tick. The same number says the telemetry layer every session already uses costs more than NFR-2 allows
|
||||
(`20_OPEN_QUESTIONS` §M16): **not this train's to fix, and the owner's to decide** — ask it when this train is out.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- **`LogNoteW`** (`src/native/FrameLedger.Overlay/src/dllmain.cpp`): a function nothing calls, found by the native
|
||||
report and **not removed** — D100 changes code loaded into a game for a defect only, and dead code is not one. The
|
||||
owner says whether it goes (owner-only item 36 (d)); `.editorconfig` has a section, naming it, that goes with it.
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request, as beta.37's and alpha.4's were in #384.~~ **Recorded
|
||||
2026-11-11, in the first pull request of the Advanced-metrics train: 0.1.0-beta.38 was released
|
||||
2026-11-11T02:56:51Z** from the signed tag on `b7d6550`, by run 42947853293 — one run for the one tag push, where
|
||||
alpha.4's push had started two. Eight assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed;
|
||||
the shipped natives carry `FL_BUILD_ID v0.1.0-beta.38`. The delta from beta.37 is 699,201 bytes beside a full
|
||||
package of 110,325,438 — "Delta processed 0452 files. 0022 patched, 0430 unchanged". The wiki was published by run
|
||||
42949461191. The rehearsal on the release branch (run 42944533749) had made a delta of 727,036 bytes with the same
|
||||
file counts.
|
||||
- **The Qodana licence** is read from the job's log (*Qodana license plan: Ultimate*, and the day the subscription is
|
||||
active until). When it lapses both jobs are red and advisory; `qodana.yaml`'s first comment is the way back.
|
||||
- **C# 15's constructs** wait for a ReSharper engine that reads them (`20_OPEN_QUESTIONS` §G, the row added with
|
||||
beta.37): the linter is now Qodana for .NET, whose engine is the same one — re-run the canary (`spike-notes` §29)
|
||||
when the action's pin moves.
|
||||
- **The alpha line rests** (D98). No sync and no alpha follow this release.
|
||||
|
||||
**Owner-only:** item 36 — beta.38 on real hardware, the links, the two Qodana Cloud projects, and `LogNoteW`.
|
||||
@@ -1,111 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.39
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.40 was cut, 2026-11-12 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`.*
|
||||
|
||||
## **START HERE** — 2026-11-11, 0.1.0-beta.39: Advanced metrics, train A — and train B begins with a plan of its own
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.39.md`; this is what no other file carries.* The owner's request of 2026-11-11
|
||||
— a setting, *Thông số nâng cao*, with a navigation item of its own — was planned the same day, approved, and its
|
||||
**first train of four is this release**: what the Agent can read (NVAPI, LibreHardwareMonitor), stored with the
|
||||
session, shown on a page, and **nothing changed in code loaded into a game**. Seven pull requests and this one:
|
||||
#387 (decisions, inventory, the catalog), #388 (the NVAPI bridge's ABI 3, the read-only gate), #389 (the shared
|
||||
reader, measured before composed), #390 (schema 0023, the `.partial` chunks), #391 (the switch, Privacy 2.15,
|
||||
Disclaimer 2.15), #392 (the pipe request, the App's feed), #393 (the page, the navigation item, Ctrl+6). **The
|
||||
design, the decisions D101–D108 and the inventory are [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced
|
||||
metrics; the screen is `08_UI` §Advanced.** The request as the owner wrote it, the four answers and the order of the
|
||||
four trains are [`handoff/history/0.1.0-beta.38.md`](handoff/history/0.1.0-beta.38.md) §NEXT.
|
||||
|
||||
### What this train decided that the plan had not
|
||||
|
||||
- **D109 — the Disclaimer goes to 2.15 with the Privacy Policy.** The plan approved the Privacy Policy's content only.
|
||||
Writing #391 found two sentences of the Disclaimer (§5, §5A) that said PawnIO and the admin mode were for the CPU
|
||||
temperature alone, which the option makes false; the owner was asked with both quoted and chose to amend them. The
|
||||
admin mode's own disclosure followed (`agent-admin-dialog/2`).
|
||||
- **Storage is not read at all** (D103's outcome, decided before the first run): LibreHardwareMonitor cannot list
|
||||
drives without touching removable ones, so the group is never opened and a drive's temperature is N/A with that
|
||||
reason. Power supplies and fan controllers are refused for the same kind of reason (a search of every USB device).
|
||||
- **The sensors are read every fifth second**, NVIDIA's figures every second — set by a measurement
|
||||
(`CaptureHost probe-advanced`: 14 ms of processor time per refresh of the sensor library), not by taste.
|
||||
- **The page's hold on the reader is the request itself**: nothing tells the Agent that a page opened or closed
|
||||
(`07_IPC` `GetAdvancedMachine`). A design with an "open" and a "close" message was not written, because a pipe
|
||||
that drops would leave the reader running.
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**Ask the owner `20_OPEN_QUESTIONS` §M16 before anything else.**~~ **Asked 2026-11-11 — D110: measure it in a
|
||||
real Agent first.** `tools/agent-cost.ps1` does, and §M16 holds the numbers: 1.93 % of one core with Advanced
|
||||
metrics off, 2.04 % on. **D117: NFR-2 is amended to ≤ 2.5 %**; nothing in the code changes.
|
||||
2. ~~**Train B (0.1.0-beta.40) starts with a plan of its own**~~ **Train B was planned and approved the same day**
|
||||
(D111–D116): [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B is the design. What that section does not
|
||||
carry:
|
||||
- **The approval covers 0.1.0-beta.40 whole** — five pull requests: (1) the decisions, the struct-version table,
|
||||
§M16 measured; (2) shared-memory layout 5, written by nobody yet; (3) the Overlay reads the extra fields of the
|
||||
calls it already hooks, behind the control word, with `overlay-fields-check` and the overhead measured; (4) the
|
||||
Agent's sampler, the catalog's new reach, the page's words, Privacy 2.16; (5) the release, owner-only item 38.
|
||||
- **beta.41 and beta.42 are designed and not begun.** Each starts only when the owner says the release before it
|
||||
passed its owner-only item on real games — that wait is what the split is for.
|
||||
- **The design was reviewed against the code before approval, and the review changed it**: the split itself; the
|
||||
struct-version table (the tree holds one version of each header); storing a vendor `Boolean` or preset as its
|
||||
value plus one and refusing the vendors' sentinels (`INVALID_FLOAT` is FLT_MAX); flags as "ever seen" masks and
|
||||
the frame time as a sum the watchdog drains, since a value sampled once a second aliases a per-frame one; the
|
||||
new region written by the watchdog alone and only while requested; `AdvancedSources`' new member optional, so a
|
||||
beta.39 row still parses; `kMaxPatches = 48` to be checked before a patch is added.
|
||||
3. **Trains C and D** (Reflex latency; the Streamline state behind `slGetFeatureFunction`) each begin with a spike
|
||||
and end in the owner's go or no. D needs an amendment of rule 4 if it goes ahead — handing the game a wrapper is
|
||||
a write — and that question is put to the owner then, not assumed.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request, as beta.38's were in #387.~~ **Recorded 2026-11-11, in the
|
||||
first pull request of train B: 0.1.0-beta.39 was released 2026-11-11T13:52:07Z** from the signed tag on `e63cd49`
|
||||
(#394), by run 43031168146 — green at the first attempt, one run for the one tag push. Eight assets; the seven
|
||||
digests of `SHA256SUMS.txt` equal the ones GitHub computed; the shipped natives carry `FL_BUILD_ID v0.1.0-beta.39`.
|
||||
The delta from beta.38 is 3,144,205 bytes beside a full package of 110,678,706 — "Delta processed 0452 files. 0026
|
||||
patched, 0426 unchanged". The wiki was published by run 43033077805. The rehearsal on the release branch (run
|
||||
43026873256) had made a delta of 3,159,090 bytes with the same file counts.
|
||||
- **Nothing here was seen in the running App.** The page was rendered to images from a test over fixture data and
|
||||
looked at; a chart does not render into such an image. No real Agent answered a real App, no session was recorded
|
||||
with the option on, and no value was compared with another tool. All of that is owner-only item 37.
|
||||
- **The first run as administrator with PawnIO is still to come** (`20_OPEN_QUESTIONS` §M10, §M13): the processor,
|
||||
memory and motherboard groups have been opened on no PC. The reader leaves a device alone after two faults, and
|
||||
runs on a thread of its own, so a sensor that hangs holds up neither a session's samples nor the pipe — that is
|
||||
the design, and it has not been tried.
|
||||
- **The `vi` strings were written by the assistant and the `ja` ones are marked `review`** — 245 keys each, every
|
||||
catalog entry among them.
|
||||
- **`LogNoteW`** is still there (owner-only item 36 (d)), and the alpha line still rests (D98): no alpha follows this
|
||||
release.
|
||||
|
||||
### Traps this train paid for
|
||||
|
||||
- **A pull request whose workflows never start.** #390 was opened and GitHub started none of its three workflows —
|
||||
`gh pr checks` said "no checks reported" ten minutes later, with nothing queued. Closing and reopening the pull
|
||||
request starts them (`pull_request: reopened`); **closing drops auto-merge, so enable it again.** After every
|
||||
`gh pr create`, ask the API for the runs of the head commit before walking away.
|
||||
- **`ShmDrainIntegrationTests.TheGuardInjectsTheOverlayAndTheReaderDrainsRealFrames` was red once** in a local gate
|
||||
(#392's first run): the guard's re-scan refused the harness mid-run, under the gate's load. It passed alone and in
|
||||
the rerun; nothing in that pull request is on its path; it was not diagnosed. ~~If it shows again, read the verdict's
|
||||
reason first — the assertion prints only that it was a refusal.~~ **It showed again the same day** (train B's first
|
||||
local gate), on another line: the Overlay's status was still `Init` with fifty records already drained. That one
|
||||
is a race in the test and is fixed — the Overlay publishes `Ready` after its last hook, later than its first
|
||||
record, so the test now waits `Init` out, bounded. The refusal was not reproduced; the assertion now prints the
|
||||
verdict, so the next one says why.
|
||||
- **`PagesLoadTests.EveryTextFollowsAThemeSwitch` was red once on a hosted runner** (#393's first run, green three
|
||||
times locally): *Settings: "Processor" shows in a fresh one only*. Every build of the Settings page in that fixture
|
||||
made a `SystemInfoViewModel` of its own, whose lines arrive from the thread pool, so two pages built a moment apart
|
||||
could differ by a row. The fixture now loads one and awaits it (`Surfaces.SystemInfo`) — fixed in the release's
|
||||
pull request, test code only. A surface whose view model loads by itself is loaded once, awaited, then shared.
|
||||
- **SonarCloud's coverage of new code** (advisory, 80 % asked) was 75.3 % on #391: the uncovered part was Win32
|
||||
(`WindowGeometryProbe.MonitorDeviceOf`). A lookup that takes a named window, as `Observe` does, can be tested
|
||||
against the harness's window; one that only searches for a visible window cannot, on a hosted runner.
|
||||
- **The App's own accessibility tests will refuse a page** that sets `AutomationProperties.LiveSetting` in XAML, that
|
||||
names a page-local resource key, whose item types have no `ToString`, or whose grid has an unnamed filler column —
|
||||
and a navigation item or a guide page that the guide's contents do not name. All of it is one test run away:
|
||||
run `FrameLedger.App.Tests` whole before the gate.
|
||||
- **An image of a page from a test** (`RenderTargetBitmap` over the hosted frame) shows the layout and the text, and
|
||||
costs a temporary test; ScottPlot draws nothing into it.
|
||||
- **`sed -i` on a file the Write tool made** is harmless only because both are LF until the normalising step; on a
|
||||
CRLF file it is the trap `handoff/traps.md` already names.
|
||||
|
||||
**Owner-only:** item 37 — beta.39 on real hardware: the update and its two terms, the switch and the page, a session
|
||||
with a real game, the first run as administrator with PawnIO, and what the Agent costs with the option on and off.
|
||||
@@ -1,148 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.40
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.41 was cut, 2026-11-12 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`. **Its release numbers are those of the day it was written**: what it calls beta.41 and beta.42 are train B's second and third releases, now beta.42 and beta.43 (D118).*
|
||||
|
||||
## **START HERE** — 2026-11-12, 0.1.0-beta.40: Advanced metrics inside the game, the first of train B's three releases
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.40.md`; this is what no other file carries.* Train B of the owner's
|
||||
"Thông số nâng cao" was planned and approved on 2026-11-11 (D110–D117) as **three releases**, and this is the first:
|
||||
what a hooked game tells its upscaler, read from **calls the Overlay already hooked — no new patch site** — only
|
||||
while the session records Advanced metrics. Four pull requests and this one: #395 (the decisions, the struct-version
|
||||
table, §M16 measured, NFR-2 amended), #396 (shared-memory layout 5, region 5), #397 (the Overlay's reads, the
|
||||
`overlay-fields-check` gate, the overhead measured), #398 (the Agent's sampler, the catalog's reach `Game`, the
|
||||
page's words, Privacy Policy 2.16). **The design is [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B; the
|
||||
contract of the new region is [`07_IPC.md`](07_IPC.md) §Region 5; what each hooked call reads is
|
||||
[`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Hook inventory.** The plan as approved, the review that changed it and the
|
||||
order of the trains are [`handoff/history/0.1.0-beta.39.md`](handoff/history/0.1.0-beta.39.md) §NEXT.
|
||||
|
||||
### What this train decided that the plan had not
|
||||
|
||||
None of these is an owner decision; each was found while building, and is written where it binds.
|
||||
|
||||
- **"On" is a request of the session's own, not a 1** (#397, `07_IPC` §Region 5). The plan had the control word as
|
||||
0 or 1. A game outlives a session, and the Overlay's summaries with it — a second session of a game that kept
|
||||
running would have read the first one's field-of-view range and counts. The Agent now writes a value no session of
|
||||
that ring used, the watchdog starts its summaries afresh at a value it has not seen and names it in every
|
||||
publication, and the reader keeps only a publication that names its own. Found while writing the injected test,
|
||||
before anything shipped; layout 5 was changed in place (`reserved0` became `request`), which was possible only
|
||||
because no release had carried it.
|
||||
- **One module's calls are counted**, for the memory query as for the dispatch: a loader that passes a call on to a
|
||||
leaf's export is seen at two hooks.
|
||||
- **Five of the thirteen entries are tables**, not text (`sl.dlss.presets`, `sl.dlss.exposure`,
|
||||
`ffx.upscale.sharpening`, `.jitter`, `.depth`): a row's name is the vendor's own member name, so nothing but a
|
||||
switch's on/off and a flag's name needs translating. The catalog's unit and two summaries changed; no id did.
|
||||
- **What became of the in-game entries is stored with the session** (`AdvancedSources.InGame`): read, nothing seen,
|
||||
not hooked. Without it a session whose game set its DLSS options through `slDLSSSetOptions` would look like a
|
||||
game with no upscaler.
|
||||
- **The Disclaimer stays 2.15.** The accuracy statement gained an item, as in beta.19, beta.20 and beta.25, none of
|
||||
which moved it; the Privacy Policy went to 2.16 with the content the plan approved.
|
||||
- **A crash dump is tried three times** (#398). Not this train's subject: `CrashDumpHelperTests` failed under the
|
||||
full gate for the third time in two days, and the cause — `MiniDumpWriteDump` of a running process that changes
|
||||
under it — costs a real crash its only dump in exactly the same way.
|
||||
|
||||
### NEXT
|
||||
|
||||
1. **The owner runs item 38** — this release on real games. **Nothing of train B is begun before that**: the wait
|
||||
is what the split into three releases is for (D113).
|
||||
2. **0.1.0-beta.41, when the owner says item 38 passed**: two new hooks, `slSetConstants` and `ffxConfigure`. The
|
||||
design is in `18` §Train B and the plan in [`handoff/history/0.1.0-beta.39.md`](handoff/history/0.1.0-beta.39.md)
|
||||
§NEXT; region 5 already has their members (`sl*`, `ffxFg*`), so no layout changes. What to settle first, in a
|
||||
plan of its own: `kMaxPatches = 48` against the patch count with the new rows; the window of `sl::Constants` that
|
||||
is read, pinned by `static_assert` so that the camera members stay outside it; the overhead of a call made every
|
||||
frame for every viewport, measured before the merge; `overlay-fields-check`'s list and its parameters for the two
|
||||
new structs.
|
||||
3. **0.1.0-beta.42, when the owner says the one before passed**: `slGetFeatureVersion` and
|
||||
`slGetFeatureRequirements` — calls a game makes while starting, so most sessions will say the game did not make
|
||||
them after FrameLedger attached. The release notes and the page say so.
|
||||
4. **Trains C and D** (Reflex latency → beta.43; the Streamline state behind `slGetFeatureFunction` → beta.44) each
|
||||
begin with a spike and end in the owner's go or no. D needs an amendment of rule 4 if it goes ahead.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request, as beta.39's were in #395.~~ **Recorded 2026-11-12, in the
|
||||
pull request after the release: 0.1.0-beta.40 was released 2026-11-11T19:30:13Z** (02:30 on the 12th in the
|
||||
owner's time zone, which is the date the changelog carries; the legal documents' *Effective* date is the UTC one,
|
||||
2026-11-11 — the fifth release to straddle midnight that way, after beta.9, .10, .12 and .14) from the signed tag
|
||||
on `5268332` (#399), by run 43085044822 — green at the first attempt, one run for the one tag push. Eight assets;
|
||||
the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed; the shipped natives carry `FL_BUILD_ID
|
||||
v0.1.0-beta.40`. The delta from beta.39 is 2,413,166 bytes beside a full package of 110,707,319 — "Delta processed
|
||||
0452 files. 0025 patched, 0427 unchanged". The wiki was published by run 43087844607. The rehearsal on the release
|
||||
branch (run 43082208739) had made a delta of 2,426,184 bytes with the same file counts.
|
||||
- **Nothing here was read from a real game, and nothing was seen in the running App.** The values come from
|
||||
`hook-harness --advanced` and the FidelityFX stub; the page's new rows were loaded by its tests and looked at by
|
||||
nobody. All of it is owner-only item 38.
|
||||
- **Whether any shipping title chains `sl::DLSSOptions` into `slEvaluateFeature`** is not known. If none of the
|
||||
owner's games does, the six `sl.dlss.*` entries read N/A everywhere until train D, and the page already says why.
|
||||
- **The aliasable part of FSR's memory** is read and published and not shown: the catalog has one memory entry.
|
||||
- **What the owner's first evening with it showed** (2026-11-12, read from a copy of the ledger and the Agent's log;
|
||||
ten hooked sessions on eight games, no fault in any, the Overlay `Ready` at every end):
|
||||
- **Read from a real game for the first time: Lies of P** (FSR 3 through `amd_fidelityfx_dx12.dll` 1.0.1, the
|
||||
SDK 1.1.x monolith) — sharpening on at 0.5, jitter up to 0.48 / 0.49 of a pixel, pre-exposure 0.25–1, a vertical
|
||||
field of view from 21.6° to 73.7°, no flag, and a reported frame time whose median is 16.67 ms beside a native
|
||||
rate of 55.6 FPS. The series starts 83 seconds in and has no gap after. Whether these match the game's own
|
||||
settings is still the owner's to say (item 38 (c)).
|
||||
- **`cameraNear` is absent there and `cameraFar` is 10.** Most likely the game runs an inverted, infinite depth
|
||||
and passes `FLT_MAX` for the plane at infinity, which the Overlay refuses as a value nobody set. "Infinite" would
|
||||
be the true answer. It is a change in code loaded into a game: decide it in beta.41's plan, not before.
|
||||
- **Every other game said *the game made none of the calls***, as expected: all ran DLSS. Dying Light: The Beast
|
||||
evaluates DLSS through Streamline and chains no `DLSSOptions` — the first evidence on that open question, and
|
||||
it is a no. Valor Mortis, Phantom Blade Zero, Clair Obscur and Kingdom Come: Deliverance II ship AMD's FSR 3.1+
|
||||
libraries and did not upscale through them in these sessions, so **no FSR 3.1+ title has been read yet**.
|
||||
- **The option off stored nothing** (Black Myth: Wukong, one session each way), and **a game under the user-mode
|
||||
anti-cheat exception ran with it on** (Girls' Frontline 2, trial 1 of 2).
|
||||
- **Valor Mortis ended with an access violation 51 seconds after injection, once**; the next launch ran fourteen
|
||||
minutes on the same build. The Overlay counted no fault and Windows logged no application error. Not attributed
|
||||
and not ruled out; its crash count stands at 1, and a second such end switches its hooking off.
|
||||
- **The sensor library was closed under its other users** — a defect of train A that only an elevated Agent with
|
||||
PawnIO can show. `20_OPEN_QUESTIONS` §M13 has what was seen; `LhmLibrary` is the fix; the owner's next sessions
|
||||
say whether it holds.
|
||||
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
|
||||
sensors "have never been read on real hardware".** They have now been read on one PC and compared with nothing.
|
||||
The sentence is the owner's to reword.
|
||||
- ~~**SonarCloud on #398** had not answered when this was written; #397's three findings are fixed in #398.~~
|
||||
**It answered after the merge, with three findings on new code**, handled in the pull request after the release:
|
||||
two `csharpsquid:S1244` in `InGameAdvancedSampler` — a lowest and a highest float compared with `==` to tell one
|
||||
value from a range; they are now told apart by their bits, which is what was meant — and one
|
||||
`csharpsquid:S3869`, a blocker, on `ParentDump`'s `DangerousGetHandle`. That one is **not new and not fixed**: the
|
||||
owner accepted it in beta.24 (`13_CI_CD` §SonarCloud), #398 moved the same expression into a new method, and
|
||||
SonarCloud tracks an issue by its place. It needs the owner's *Accept* again — item 38 (j).
|
||||
- **The `vi` strings were written by the assistant and the `ja` ones are marked `review`** — fourteen more keys and
|
||||
the reworded Settings text.
|
||||
- **`LogNoteW`** is still there (owner-only item 36 (d)), item 37 is still unrun, and the alpha line still rests
|
||||
(D98): no alpha follows this release.
|
||||
|
||||
### Traps this train paid for
|
||||
|
||||
- **A library that is "one object per user" may still be one per process underneath.** Three `Computer`s of
|
||||
LibreHardwareMonitor shared a driver handle and mutexes; each was tested alone, unelevated, where the shared part
|
||||
is never opened. Before composing a second instance of anything that talks to a driver, ask what its `Close`
|
||||
closes. And `first ??= TryClose(x)` in a loop stops closing at the first throw — the test for "all are closed
|
||||
even when one throws" caught it in the fix itself.
|
||||
- **A heredoc in the tool's shell breaks on an odd number of apostrophes** — a script with `game's` in it fails with
|
||||
"unexpected EOF while looking for matching `'`" before Python ever runs. Write the script to a file and run the
|
||||
file.
|
||||
- **A region that outlives its reader needs to say whose data it holds.** Region 4 never had the problem — it is
|
||||
the swap chain's state, the same for any session. Region 5 holds summaries, and a summary has a beginning. Ask of
|
||||
any new shared state: what does the second session of the same process read in its first second?
|
||||
- **SonarCloud's engine does not see a Catch2 `REQUIRE` end a path**: `REQUIRE(OpenRingFor(pid, r))` followed by
|
||||
`r.st->…` is a null dereference to it (`cpp:S2259`, a failed gate on new code). An explicit `return` after the
|
||||
`REQUIRE` is what it follows. And a `LARGE_INTEGER` read through `QuadPart` is initialised through `QuadPart`
|
||||
(`cpp:S6232`) — `13_CI_CD` §SonarCloud has had the rule since #336; new code still forgot it.
|
||||
- **SonarCloud fails after the merge.** Its job is advisory and slower than the required checks, so auto-merge lands
|
||||
the pull request first. Read its result on the merged pull request before building on it.
|
||||
- **`MA0051` counts sixty lines, comments included**, and `CaptureSession.SuperviseAsync` was at fifty-nine: one
|
||||
line more is a build error. What a session asks once belongs where the session's state is made, not in the loop.
|
||||
- **`RCS1242` refuses `in` for a struct that is not `readonly`** — the mirror structs are not. Pass the object that
|
||||
holds the struct and take `ref readonly` inside.
|
||||
- **`/W4 /WX` refuses `alignas` on a struct it then has to pad** (C4324): align the variable, not the type.
|
||||
- **The `.resx` files hold a literal apostrophe**, not `'`: an edit script that searches for the entity finds
|
||||
nothing and stops half-way through.
|
||||
- **`ISessionRepository.FindAdvancedSensorsAsync` returns `t_ms` too**: "no advanced series" is "no series under
|
||||
`adv.`", not an empty list.
|
||||
- **PowerShell reads a backtick in a double-quoted string as an escape** (`` `r `` is a carriage return) and
|
||||
`"$name: text"` as a scoped variable: in a gate's messages, quote names with apostrophes and write `${name}:`.
|
||||
|
||||
**Owner-only:** item 38 — beta.40 on real games: the update and the Privacy Policy 2.16, a game that was running
|
||||
across the update, an FSR 3.1+ title and a DLSS title with the option on, the same with it off, a second session of
|
||||
a game that kept running, a game under the user-mode anti-cheat exception, and what the Agent costs.
|
||||
@@ -1,131 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.41
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.42 was cut, 2026-11-12 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`. **Its release numbers are those of the hour it was written**: its item 3 calls train B's third step beta.43 and its item 4 calls trains C and D beta.44 and beta.45 — since D122, later the same day, they are beta.44, beta.45 and beta.46, and beta.43 is the two new hooks.*
|
||||
|
||||
## **START HERE** — 2026-11-12, 0.1.0-beta.41: one fix — the sensor library is no longer closed under its other users
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.41.md`; this is what no other file carries.* 0.1.0-beta.40 was released in the
|
||||
small hours of 2026-11-12 and the owner ran it that same night on eight games, as administrator with PawnIO — the
|
||||
first elevated run there has been. A copy of the ledger and the Agent's log showed the in-game readings working
|
||||
(Lies of P, the first real game read) and **a defect of train A that only that elevation can show**: three
|
||||
LibreHardwareMonitor `Computer`s in one Agent, and the library's per-process state closed by one under the others.
|
||||
This release is that fix and nothing else: #400 (0.1.0-beta.40's release facts; two comparisons SonarCloud flagged),
|
||||
#401 (`LhmLibrary`), and this one. **Everything about train B — what was built, what the owner's sessions showed,
|
||||
the traps — is [`handoff/history/0.1.0-beta.40.md`](handoff/history/0.1.0-beta.40.md)**; the fix is
|
||||
[`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Advanced metrics and [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md)
|
||||
§M13.
|
||||
|
||||
### What this release decided
|
||||
|
||||
- **D118 — the fix is released at once as 0.1.0-beta.41, and train B's numbers move by one.** D113 had named
|
||||
beta.41 for the train's second release. Told so, the owner chose to release the fix now. The train's second
|
||||
release is **beta.42**, its third **beta.43**, train C **beta.44**, train D **beta.45**. Released changelogs and
|
||||
moved HANDOFF sections keep the numbers of their day; so do the comments in `fl_shm.h` and `ShmLayout.cs` (the
|
||||
members "0.1.0-beta.41" and "beta.42" fill), **deliberately**: touching them would have changed source that is
|
||||
loaded into a game in a release that says the game-side code is beta.40's line for line. The release that fills
|
||||
a member rewrites its comment.
|
||||
- **The reads of the sensor library are not put under one lock**, only its opens and closes. A lock around every
|
||||
read would have put a session's once-a-second poll behind the Advanced reader's, undoing the separate threads
|
||||
that keep a hanging sensor from holding up the other reader.
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**The owner runs item 39** (this fix, on the PC that showed the fault) **and the rest of item 38** (an FSR 3.1+
|
||||
title; two sessions of one running game; the cost; the values of Lies of P against the game's own settings).~~
|
||||
**Both passed on 2026-11-12, on the owner's word** ("Bạn có thể đánh dấu là pass và tiếp tục") after the thirteen
|
||||
sessions below; [`handoff/owner-only-passed.md`](handoff/owner-only-passed.md) says what those sessions covered and
|
||||
what they did not.
|
||||
2. **Planned and approved 2026-11-12 (D119–D122): the second step is two releases.** **0.1.0-beta.42 has no new
|
||||
patch site** — five pull requests: (1) the session's upscaler label (D120); (2) the Overlay's patch registry
|
||||
refuses a patch it cannot register, and registers before it enables; (3) the native log is flushed whenever
|
||||
something new was logged, every inventory row's install line names its module and symbol, a failed patch says
|
||||
why, and the first sight of each ffx descriptor type on each module is logged — so that one Cyberpunk session on
|
||||
beta.42 says where its upscale goes (D121); (4) FSR's infinite depth plane (D119); (5) the release, owner-only
|
||||
item 40. **0.1.0-beta.43 is the two new hooks** and begins only when that log was read; its design — reviewed
|
||||
against the code, which changed it — is in the plan of that day and below. What the review found that the first
|
||||
draft had wrong: there is no "dominant segment" (segments split on output size only), so the label is the modal
|
||||
name over the dominant stream; the patch table drops a patch silently when full; the init thread's flush runs
|
||||
after the watchdog starts; a second NaN pattern for "infinite" would have been dropped by the Agent — real
|
||||
+infinity is stored instead; the new rows must be gated before `ResolveScoped`, which takes a module reference a
|
||||
call; `slSetConstants` needs the struct's GUID checked on every call; `ffxConfigure` needs an owner slot of its
|
||||
own; summaries across viewports must come from the first viewport seen.
|
||||
~~**0.1.0-beta.42 — train B's second release — when the owner says item 38 passed begins now, with its plan**~~: `slSetConstants` and
|
||||
`ffxConfigure`. A plan of its own first. What it must settle, beside what
|
||||
[`handoff/history/0.1.0-beta.40.md`](handoff/history/0.1.0-beta.40.md) §NEXT lists (`kMaxPatches = 48`, the window
|
||||
of `sl::Constants` pinned outside the camera members, the per-call overhead, the gate's list for the two new
|
||||
structs):
|
||||
- ~~**`FLT_MAX` in an FSR depth plane.** Lies of P gave `cameraFar = 10` and no `cameraNear`; most likely the
|
||||
plane at infinity is `FLT_MAX`, which the Overlay refuses as "nobody set this". Decide whether it is stored as
|
||||
"infinite" — an Overlay change, with its overhead stated.~~ *(Decided, D119, and built in beta.42:
|
||||
`FL_ADV_FLOAT_INFINITE`, shown "∞". Whether Lies of P's missing plane IS `FLT_MAX` is still the hypothesis it
|
||||
was — item 40 reads it.)*
|
||||
- ~~**Valor Mortis.** One exit by access violation 51 seconds after injection under beta.40, none under an earlier
|
||||
build, not attributed. Its crash count is 1; a second such end switches its hooking off. Before adding a hook
|
||||
to that game's process, ask the owner whether it happened again.~~ **Answered by the owner, 2026-11-12: it was
|
||||
the game's own — a shader-compilation error on entering the game, shown in the game's own crash dialog.** Not
|
||||
FrameLedger's. It ran normally under beta.41 afterwards. Its crash count still stands at 1, because the crash
|
||||
policy counts an abnormal end within 60 seconds of injection whoever caused it: a second one, from any cause,
|
||||
switches its hooking off, and the owner then switches it on again from the game's page.
|
||||
- **The release numbers in the comments** of `fl_shm.h`, `ShmLayout.cs`, `hook-harness` and `guard_test.cpp` for
|
||||
the members that release fills (D118).
|
||||
3. **0.1.0-beta.43 — the third — when the owner says the one before passed**: `slGetFeatureVersion` and
|
||||
`slGetFeatureRequirements`.
|
||||
4. **Trains C and D** (beta.44, beta.45) each begin with a spike and end in the owner's go or no.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request.~~ **Recorded 2026-11-12: 0.1.0-beta.41 was released
|
||||
2026-11-11T22:38:39Z** (05:38 on the 12th in the owner's time zone) from the signed tag on `a6b95e8` (#402), by
|
||||
run 43111028661 — green at the first attempt, one run for the one tag push. Eight assets; the seven digests of
|
||||
`SHA256SUMS.txt` equal the ones GitHub computed; the shipped natives carry `FL_BUILD_ID v0.1.0-beta.41`. The delta
|
||||
from beta.40 is 807,692 bytes beside a full package of 110,708,416 — "Delta processed 0452 files. 0022 patched,
|
||||
0430 unchanged". The wiki was published by run 43113525941. The rehearsal on the release branch (run 43108189693)
|
||||
had made a delta of 841,038 bytes with the same file counts.
|
||||
- ~~**The fix has not been seen to work.** It was written from the log's timing; the fault needs an elevated Agent with
|
||||
PawnIO. Item 39 is the check, and `20_OPEN_QUESTIONS` §M13 stays open until then.~~ **The owner's first seven
|
||||
sessions on beta.41 show no fault** (2026-11-12, 06:38–07:01, read from the Agent's log and a copy of the ledger):
|
||||
not one `advanced:` line, and every session with the option on stored its 212 or 213 series, the processor's 119
|
||||
among them. On beta.40 the same morning the processor device faulted out after **each** of the six sessions
|
||||
recorded between 04:34 and 05:07. The rarer fault — the reader failing to open — was one session in sixteen, so
|
||||
seven clean ones do not yet say it is gone. ~~Whether item 39 has passed is the owner's to say.~~ The owner
|
||||
marked it passed the same day.
|
||||
- **What those sessions say of train B's first release** (the same log and ledger; the owner named which games are
|
||||
first-person — Kingdom Come: Deliverance II, Cyberpunk 2077, Dying Light: The Beast, Valor Mortis — the rest
|
||||
third-person, and Psycho-Sleuth 2D):
|
||||
- **The first FSR 3.1 title read: Kingdom Come: Deliverance II** (FSR 3.1 chosen in the game;
|
||||
`amd_fidelityfx_upscaler_dx12.dll` 4.0.2 behind the loader). Performance mode, 1280×720 to 2560×1440;
|
||||
sharpening on at 0.5; `cameraNear` 0.05 and `cameraFar` 8000 — **both planes, the only title that gives both**;
|
||||
one vertical field of view for the whole session, 63.1°; a reported frame time of 16.67 ms. A 41-second session
|
||||
of the same game that never left its menu read nothing and says so.
|
||||
- **Dying Light: The Beast** upscaling with FSR: sharpening off, 75.4°–78° vertical, 7.5 ms. **Clair Obscur**:
|
||||
sharpening off, 5.7°–90.7° over four minutes. So far the two first-person titles hold a narrow range and the
|
||||
two third-person ones a wide one (Lies of P 21.6°–73.7°) — what one would expect of cutscene and aiming
|
||||
cameras, and no more than that: four titles.
|
||||
- **Three engines give `cameraFar` alone, as a small number** — 10 (Lies of P), 1 (Clair Obscur), 0.1 (Dying
|
||||
Light) — which is the near plane of an inverted, infinite depth with the other plane at `FLT_MAX`. That is the
|
||||
case beta.42's plan has to decide.
|
||||
- **Clair Obscur reports a frame time of 0.001 ms in some seconds.** It is what the game hands FSR, stored as it
|
||||
was said; the lowest value of that series is not a frame time anyone saw.
|
||||
- **Cyberpunk 2077 read nothing**, with FSR frame generation running and the render size known: its upscaling did
|
||||
not come through an ffx-api upscale dispatch in those sessions. Which upscaler it was set to is the owner's to
|
||||
say; `ffxConfigure` (beta.42) is where its frame generation would be read.
|
||||
- **One session of Dying Light names DLSS as its upscaler and carries FSR's quality byte and render size** (81
|
||||
seconds, both an FSR dispatch and a DLSS evaluation seen, "settings changed" not set). Not this train's code —
|
||||
the session summary's choice between two upscalers seen in one session — and not looked into. **The owner,
|
||||
2026-11-12: Dying Light and Expedition 33 were set, in the game, to FSR upscaling with DLSS frame generation.**
|
||||
So "FSR beside DLSS frame generation" in their other sessions is the setting, not a misreading; in this one the
|
||||
summary picked the wrong one of the two for its upscaler line, which is still to be looked at.
|
||||
- **A session without consent says so**: two Cyberpunk sessions before its consent dialog was accepted are
|
||||
Tier 2, and their Advanced row says *not measured inside the game*. **The option off stored nothing** again,
|
||||
this time on a title that upscales with FSR 3.1 (Dying Light, beta.41).
|
||||
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
|
||||
sensors "have never been read on real hardware".** They have been read on one PC and compared with nothing. The
|
||||
owner's to reword.
|
||||
- **SonarCloud's `csharpsquid:S3869` on `ParentDump.cs`** is open on `main` until the owner accepts it again (it was item
|
||||
38 (j), the one part of that item not done; the owner said on 2026-11-12 that they will). Until then `main`'s `sonarcloud` job is red on that one line.
|
||||
- **Items 36 (d) (`LogNoteW`) and 37 are still open**; the ledger shows part of 37 (e) happened — the elevated
|
||||
groups opened and read — and nothing of it was compared with another tool. The alpha line still rests (D98).
|
||||
|
||||
**Owner-only:** ~~item 39~~ passed 2026-11-12, with item 38. Nothing new is open from this release; items 36 (d)
|
||||
and 37 still are.
|
||||
@@ -1,204 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.42
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.43 was cut, 2026-11-12 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`. **Its §NEXT item 2 says 0.1.0-beta.43 is "under way"**: it was released the same day, and what it built and decided is HANDOFF.md's section for it.*
|
||||
|
||||
## **START HERE** — 2026-11-12, 0.1.0-beta.42: no new patch site — the label, the registry, a log that outlives the game, the plane at infinity
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.42.md`; this is what no other file carries.* The owner marked items 38 and 39
|
||||
passed on 2026-11-12 and train B's second step was planned the same morning. A review of the draft against the code
|
||||
changed it, and the owner split it (D122): **this release adds no patch site**, and the two new hooks are
|
||||
0.1.0-beta.43. Four pull requests and this one: #406 (the session's upscaler label, D120; the decisions D119–D122),
|
||||
#407 (the patch registry), #408 (the native log and the descriptor-type census, D121), #409 (FSR's plane at
|
||||
infinity, D119; Qodana's native report). **What the owner's sessions on beta.40 and beta.41 showed, and the plan as
|
||||
approved, are [`handoff/history/0.1.0-beta.41.md`](handoff/history/0.1.0-beta.41.md)**; what each pull request built
|
||||
is [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Unhooking and §Native logging, [`03_METRICS.md`](03_METRICS.md)
|
||||
§Upscaling and [`07_IPC.md`](07_IPC.md) §Region 5.
|
||||
|
||||
### What this release decided, beyond D119–D122
|
||||
|
||||
- **The descriptor-type census is not behind the Advanced-metrics switch.** It is a diagnostic that reaches the log
|
||||
file and nothing else — no record, no shared memory, no session — like `HOOK_INSTALLED`. Behind the switch it
|
||||
could not answer D121 for a session recorded with the switch off, which is most of them. Its cost was measured
|
||||
and stated instead (+3.8 ns a dispatch).
|
||||
- **The log's text grew to 72 characters; nothing else about the ring did.** 256 events, static, 24 KiB.
|
||||
- **A slot of the patch registry that was ever live is never reused**, and a failed create or enable leaves the
|
||||
hook created in MinHook as it always did. Both are the smaller change: the first keeps the stop's walk lock-free
|
||||
without a second word per slot, the second changes no failure path that has never been seen to run.
|
||||
- **The live card still names the first upscaler a session saw** (`FgLadder.UpscalerIdentity`). The stored
|
||||
session's name is the modal one (D120); for a session in progress the question is a different one.
|
||||
- **Qodana's "never used" on the registry test's stand-in engines is switched off for that file**, not answered by
|
||||
turning the template into function pointers: the header is loaded into a game, and D100 changes such code only
|
||||
for a defect.
|
||||
|
||||
### What the owner's first four sessions on beta.42 showed (2026-11-12, 09:40–09:53)
|
||||
|
||||
Dying Light: The Beast, Kingdom Come: Deliverance II, Cyberpunk 2077 and Lies of P, each quit from its own menu;
|
||||
read from the four `overlay-<pid>-….log` files, a copy of the ledger, and — for Cyberpunk — the game's own settings
|
||||
file and executable on disk. All four hooked, no fault, no `PATCH_FAILED`, the Agent's log without an `advanced:`
|
||||
line.
|
||||
|
||||
- **D121 is answered, and it is not a detection gap: in that session Cyberpunk 2077 upscaled with FSR 2.1, which is
|
||||
compiled into the game.** Its `UserSettings.json`, written when the session ended, has `ResolutionScaling = FSR2`,
|
||||
`FSR2 = Quality`, `FrameGeneration = FSR3`, `FSR3_FrameGeneration = true` — FSR **2** for the upscale, FSR **3**
|
||||
for frame generation only. Quality is a ratio of 1.5, and the session's render size is 1707×960 at 2560×1440.
|
||||
`Cyberpunk2077.exe` carries FSR 2's own function names (`ffxFsr2GetJitterPhaseCount`,
|
||||
`ffxFsr2GetUpscaleRatioFromQualityMode`) and names one FidelityFX module, the loader; its folder has no FSR 2
|
||||
DLL. **The log says the same from the other side**: the loader (2.3.0), the upscaler leaf (4.1.1) and the
|
||||
frame-generation leaf (4.0.1) were all patched; the loader and the frame-generation leaf were handed `0x20004`
|
||||
(PREPARE) and `0x20003` (FRAMEGENERATION); the loader and the upscaler leaf were asked `0x10002` (the ratio of a
|
||||
quality mode) once at start; **no module was ever handed `0x10001`**, and there is no `UPSCALE_ROUTE` line. The
|
||||
NVIDIA driver's words for the session say DLSS was not running. So the upscale goes through no export at all —
|
||||
the case `LIMITATIONS.md` already names ("FSR 2 and upscalers built into the game are not identified"), and
|
||||
"unknown" beside a measured render size is the true reading. ~~**The owner had said FSR 3 or 4; that the setting is
|
||||
FSR 2.1 is read from the file, and is the owner's to confirm.**~~ **Confirmed by the owner the same morning with
|
||||
a screenshot of the game's Graphics menu: Resolution Scaling reads "AMD FidelityFX Super Resolution 2.1"** (the
|
||||
file's `FSR2`), with its own quality and sharpening rows under it. Nothing to fix for it in beta.43.
|
||||
- **The loader of SDK 2.3 passes a dispatch on to the leaf's export — the older loader does not — and that is a
|
||||
double count waiting for the first title that upscales through it.** In Cyberpunk each frame-generation dispatch
|
||||
type is logged on the loader AND on the frame-generation leaf: the game calls the loader, the loader calls the
|
||||
leaf's exported `ffxDispatch`. In Kingdom Come and Dying Light (loader 1.0.2) the UPSCALE is logged on the loader
|
||||
alone, which is what `fl_hook_inventory.h` measured in September and what the fixture's loader stub copies.
|
||||
Frame generation is unharmed — PREPARE is counted by its frame number, FRAMEGENERATION is a bit, and the
|
||||
session's factor is ×2.0001. **An UPSCALE is counted once per hooked module that sees it**
|
||||
(`g_ffxSeen`'s count): through a 2.3 loader that would be two a frame, and with frame generation off — no
|
||||
PREPARE, so the count falls back to UPSCALE dispatches — the application-frame count would double. Not
|
||||
observed: no UPSCALE was dispatched. **One session answers it: Cyberpunk with Resolution Scaling set to FSR 3
|
||||
and frame generation off** — the log shows whether `0x10001` is on both modules, and the session's frame
|
||||
counts show whether it was counted twice. If so, the fix is beta.43's: count at the first module seen, as
|
||||
`fl::adv::Owns` already does for the Advanced reads.
|
||||
- **The plane at infinity is measured, not a hypothesis any more (D119).** Lies of P: `cameraNear = ∞`,
|
||||
`cameraFar = 10`. Dying Light: `cameraNear = ∞`, `cameraFar = 0.1`. Both gave one plane on beta.41. Kingdom
|
||||
Come still gives both as numbers (0.05 and 8000). Clair Obscur was not run.
|
||||
- **The logs are whole.** Each has its installs by module and symbol, the census as it grew, and lines long after
|
||||
the first second — Dying Light's first UPSCALE at 71.6 s, Kingdom Come's at 37.5 s, when play began. One line
|
||||
looks odd and was not looked into: Cyberpunk's frame-generation leaf's `ffxDispatch` is at `0x241cde7ba10`, far
|
||||
from where the other modules sit (`0x7ff…`); the patch went in and was called.
|
||||
- **Dying Light was named FSR, Quality, with DLSS frame generation ×3.99** — its settings as the owner gave them.
|
||||
No session changed upscaler part-way, so D120's case was not exercised.
|
||||
|
||||
### And three more starts of Cyberpunk 2077, 10:05–10:15 the same morning
|
||||
|
||||
Asked for as "Resolution Scaling = FSR 3, frame generation off". Read the same way.
|
||||
|
||||
- **The game was still on FSR 2.** After the last of them `UserSettings.json` has `ResolutionScaling = FSR2`,
|
||||
`FSR2 = Performance` (it was `Quality` at 09:50), `FSR3 = Auto` untouched, `FrameGeneration = Off`. So the quality
|
||||
and the frame generation were changed and the upscaler was not: **the owner's screenshot of the menu, taken after
|
||||
them, shows Resolution Scaling = "AMD FidelityFX Super Resolution 2.1", Performance, Frame Generation Off** —
|
||||
the file's `FSR2` is the menu's FSR 2.1. Both
|
||||
stored sessions (215 s and 158 s, attached to a game already running) agree with FSR 2.1 built in and frame
|
||||
generation off: every hook in, **not one ffx dispatch or query of any type**, no Streamline evaluation, no render
|
||||
size, upscaler "unknown", factor 1.0 from Streamline's frame tokens, ~290 FPS. **So the 2.3 loader's double count
|
||||
is still unobserved either way**: what answers it is a session in which `UserSettings.json` says
|
||||
`ResolutionScaling = FSR3` afterwards.
|
||||
- **The first start was lost to the transient this file recorded an hour earlier — in a real session this time.**
|
||||
10:05:20 the game appeared; the Overlay went in at 10:05:23; 0.47 s later it was told to stop, and the Agent's
|
||||
log says why: `SafetyUnhook; Discarded (tier 1, exit=UnhookedSafety, frames=0); guard=ModuleScanFailed/a module
|
||||
list came back incomplete`. The Overlay's log shows the four patches restored within 0.75 s. The game ran on
|
||||
unrecorded for two minutes until the owner restarted it. **It is not new and not rare**: the Agent's logs kept on
|
||||
this PC (2026-11-05 onwards) hold five such ends — Phantom Blade Zero three times on 2026-11-05 (two safety
|
||||
unhooks and one refusal before injection), Crown & Coin on 2026-11-10, Cyberpunk today — beside the two test
|
||||
runs. Each is a module list read while the target was still loading modules, at a launch. **The question for the
|
||||
owner is no longer hypothetical**: a list that cannot be read is not a finding, and rule 2 treats it as a refusal
|
||||
so that an unreadable game is never hooked; reading it again a bounded number of times before refusing would
|
||||
keep that — a list that stays unreadable still refuses — and stop losing sessions to a moment of loading. It
|
||||
changes what the guard does on a check, so it is the owner's decision, and it is not made here. *(Made the same
|
||||
day: D123, §NEXT item 1b.)*
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**The owner runs item 40** — above all **one session of Cyberpunk 2077 with FSR upscaling** on beta.42, then
|
||||
quits the game the ordinary way. Its `logs\overlay-<pid>-….log` is what beta.43 waits for.~~ **Run 2026-11-12;
|
||||
the section above is what it showed.** What is left of item 40 is (d), a session that changes upscaler, and
|
||||
the owner's word on the rest.
|
||||
1a. ~~**Before beta.43's plan: one session of Cyberpunk 2077 with Resolution Scaling = FSR 3, frame generation
|
||||
off** (the second bullet above), and a second with it on. It says whether FrameLedger names FSR 3 there —
|
||||
the route through the loader that D121 was first taken to be about — and whether the 2.3 loader counts an
|
||||
UPSCALE twice. *(Tried 2026-11-12 10:08 and 10:12: the game was still on FSR 2 — the section above. The check
|
||||
that the right thing ran is the file: `ResolutionScaling = FSR3`.)*~~
|
||||
**It cannot be run, the owner said the same day: Cyberpunk 2077 has FSR 2.1 as its only FSR upscaler and
|
||||
FSR 3.1 as frame generation only — two separate settings, not a pair; there is no FSR 3 under Resolution
|
||||
Scaling.** So D121 is closed for good — every Cyberpunk session upscaling with FSR reads "unknown", by the
|
||||
limit `LIMITATIONS.md` states — and **no title run so far upscales through a 2.3 loader**. The double
|
||||
count stays unobserved. What IS measured is that this loader hands a frame-generation dispatch to the leaf's
|
||||
export; an UPSCALE through the same `ffxDispatch` would take the same path. beta.43's plan therefore counts
|
||||
an UPSCALE at the first hooked module that sees it (as `fl::adv::Owns` does) as a precaution, with a fixture
|
||||
whose loader forwards to the leaf's export — rather than wait for a session that cannot be had.
|
||||
1b. ~~**The owner's decision on the guard's module-list read** (the section above): refuse at the first incomplete
|
||||
list, as now, or read again a bounded number of times first. If the second, it is a pull request of its own
|
||||
in the guard (`FrameLedger.Injector`), with `19_SAFETY` amended in it, before or with beta.43.~~ **Decided
|
||||
2026-11-12 — read again (D123) — and built the same day**: `Collected::kUnsettled`, up to three re-reads,
|
||||
`19_SAFETY` amended. Not released: it ships with the next pre-release, and until then a launch can still be
|
||||
lost this way on beta.42. What the owner then checks is the Agent's log: no `guard=ModuleScanFailed` end at a
|
||||
game's launch, and if one comes its signal now says which kind — *kept changing while it was read* (four reads
|
||||
were not enough) or *came back incomplete* (more modules than the guard's buffer holds).
|
||||
2. **0.1.0-beta.43 — planned and approved 2026-11-12 (D123–D125), and under way.** The guard's re-read (D123,
|
||||
#413) ships with it and not on its own (D124). Five pull requests after it: (1) an UPSCALE is counted at the
|
||||
first source that saw one (D125) — the fixture's loader bound through the leaves' exports read K = 1 as 2.0
|
||||
before it; (2) `slSetConstants`; (3) `ffxConfigure` on the four ffx modules; (4) the Agent, the App and the
|
||||
Privacy Policy 2.17, whose wording the plan carried and the owner approved with it; (5) the release, owner-only
|
||||
item 41. The design is the one below, as the review of 2026-11-12's first plan left it; nothing in the logs
|
||||
changed it except D125.
|
||||
~~**Read that log, then plan 0.1.0-beta.43**~~ — `slSetConstants` and `ffxConfigure`, and the fix for D121 if the
|
||||
log shows the route. What to look for: which `HOOK_INSTALLED` lines there are (which of the four ffx modules and
|
||||
the FSR 3.0 host were patched); the `FFX_DISPATCH` lines — is `b=0x10001` (UPSCALE) on any module, or only
|
||||
`0x20004` / `0x2000c` / `0x20003`; an `UPSCALE_ROUTE` line; `PATCH_FAILED`; the last `RUNTIME_CENSUS` word.
|
||||
**No UPSCALE type anywhere and no route line means the upscale does not come through any export the Overlay
|
||||
patches** — statically linked, or a module the inventory does not name — and then the fix is not a new arm in
|
||||
a detour. The design for the two hooks, as the review left it, is the plan of 2026-11-12 (moved with the
|
||||
section above) and these points: the new rows are gated at the top of `InstallByFamily`, **before**
|
||||
`ResolveScoped`, and installed only once the process was ever asked; hook families 13 and 14 with latches of
|
||||
their own; `slSetConstants` checks the struct's GUID and `structVersion ≥ 1` on every call and reads only
|
||||
`jitterOffset`, `mvecScale`, `cameraNear` … `cameraAspectRatio` and the seven Booleans — never bytes 368..423,
|
||||
pinned by `offsetof` of the allowed members; summaries from the first viewport seen; `ffxConfigure` has an
|
||||
owner slot of its own and reads `frameGenerationEnabled`, `allowAsyncWorkloads`, `flags`,
|
||||
`onlyPresentGenerated`, `generationRect` and nothing else; the detours also consult `MayObserve()`;
|
||||
`overlay-fields-check` gains three parameter names, `structType` among the shared members and an `offsetof` per
|
||||
listed `sl::Constants` member. The registry holds 48 and the worst case becomes 25
|
||||
(`kPatchSitesOutsideTheInventory` stays 7; the inventory's row count goes from 13 to 18 and its
|
||||
`static_assert` says so).
|
||||
3. **0.1.0-beta.44** — `slGetFeatureVersion` and `slGetFeatureRequirements` — when the owner says beta.43 passed.
|
||||
4. **Trains C and D** (beta.45, beta.46) each begin with a spike and end in the owner's go or no.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request.~~ **Recorded 2026-11-12: 0.1.0-beta.42 was released
|
||||
2026-11-12T02:31:07Z** (09:31 in the owner's time zone) from the signed tag on `a708ae8` (#410), by run
|
||||
43139775713 — green at the first attempt, one run for the one tag push. Eight assets; the seven digests of
|
||||
`SHA256SUMS.txt` equal the ones GitHub computed; the four shipped natives carry `FL_BUILD_ID v0.1.0-beta.42`. The
|
||||
delta from beta.41 is 710,943 bytes beside a full package of 110,716,228 — "Delta processed 0452 files. 0023
|
||||
patched, 0429 unchanged". The wiki was published by run 43142009098. The rehearsal on the release branch (run
|
||||
43137520796) had made a delta of 735,485 bytes with the same file counts.
|
||||
- **No real game was run on this build.** The four changes were tested with the harness and the cost measured on
|
||||
the headers. Item 40 is the first real session.
|
||||
- **Whether the missing plane of Lies of P, Clair Obscur and Dying Light is `FLT_MAX`** is still the reading their
|
||||
small `cameraFar` values point to, not a measurement. Item 40 (c).
|
||||
- **A flake with a cause now, and a question in it for the owner.**
|
||||
`ShmDrainIntegrationTests.TheGuardInjectsTheOverlayAndTheReaderDrainsRealFrames` was red once in this release's
|
||||
local gate (and once on 2026-11-11, when the assertion did not yet print the verdict): the supervisor's first
|
||||
re-scan, 0.8 s after the injection, came back `ModuleScanFailed` — *a module list came back incomplete* — while
|
||||
the harness was still loading modules. The same gate was green on the same code before and after. In the test
|
||||
it is a re-run. **In a real session the same answer is a safety unhook**: a re-scan that cannot read the module
|
||||
list of a game that is still running stops the session (`19_SAFETY` §During a session; D48 covers only a game
|
||||
that has exited). Whether the guard should read the list a second time before refusing is a change to rule 2's
|
||||
checks and is the owner's to decide; nothing was changed. **A second one within the hour, in the gate of the pull
|
||||
request that records the release's facts:**
|
||||
`ToolhelpProcessSnapshotSourceTests.ThisProcessIsInTheSnapshotWithItsNormalisedImagePathAndACreationTime` got an
|
||||
empty snapshot — `ToolhelpProcessSnapshotSource.Take` returns an empty list when the snapshot cannot be taken or
|
||||
walked, and says nothing. Green on the run after. Both are Windows refusing, for a moment, to enumerate something
|
||||
on a PC that was building, testing and running FrameLedger itself at once; what an empty snapshot does to the
|
||||
watcher's tick in a real session was not looked into.
|
||||
- ~~**SonarCloud has not answered for #406–#409**: `main`'s `sonarcloud` job was cancelled by the next merge each
|
||||
time. It runs to its end on this release's commit; read it then.~~ **It answered on `a708ae8`: the quality gate
|
||||
passed, and one issue was open on `main`** — `cpp:S5813`, a `strlen` in the helper the new log case of
|
||||
`guard_test.cpp` reads lines with (#408). Fixed in the pull request that records these facts: the helper takes
|
||||
strings. **`csharpsquid:S3869` on `ParentDump.cs` is no longer open** — SonarCloud shows it accepted at
|
||||
2026-11-11T21:13Z (04:13 on the 12th, the owner's time), which is before the texts that still called it open
|
||||
were written; they were not checked against SonarCloud then. **Qodana's two reports are green on the release's
|
||||
commit**; the native one was red from #407 to #408 on seven problems in test code, answered in #409.
|
||||
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
|
||||
sensors "have never been read on real hardware"** — the owner's to reword. ~~**SonarCloud's `csharpsquid:S3869` on
|
||||
`ParentDump.cs`** is the owner's to accept.~~ *(Done — the line above.)* **Items 36 (d) and 37 are still open.** The alpha line still rests
|
||||
(D98).
|
||||
|
||||
**Owner-only:** item 40.
|
||||
@@ -1,154 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.43
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.44 was cut, 2026-11-12 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`. **Its §NEXT item 2 says 0.1.0-beta.44 is planned**: it was released the same day, and what it built and decided is HANDOFF.md's section for it.*
|
||||
|
||||
## **START HERE** — 2026-11-12, 0.1.0-beta.43: two hooks installed only where asked for, the guard reads a moving list again, an UPSCALE counted once
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.43.md`; this is what no other file carries.* The owner ran beta.42 the morning
|
||||
it was released; seven sessions, a copy of the ledger and the logs answered D121 (Cyberpunk 2077's FSR is 2.1, built
|
||||
into the game), showed the guard losing launches to a module list that moved while it was read, and showed the
|
||||
FidelityFX 2.3 loader handing a call on to the leaf's export. The owner decided D123–D125 and approved the plan the
|
||||
same morning, Privacy Policy 2.17's wording with it. Five pull requests and this one: #413 (the guard reads again,
|
||||
D123), #414 (an UPSCALE is counted at the first source that saw one, D125; D124), #415 (`slSetConstants`), #416
|
||||
(`ffxConfigure` on the four ffx-api modules), #417 (the Agent, the App, Privacy Policy 2.17). **What the owner's
|
||||
sessions on beta.42 showed, and the design as planned, are
|
||||
[`handoff/history/0.1.0-beta.42.md`](handoff/history/0.1.0-beta.42.md)**; what each pull request built is
|
||||
[`19_SAFETY_AND_ANTICHEAT.md`](19_SAFETY_AND_ANTICHEAT.md) §Pre-injection checks,
|
||||
[`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Hook inventory (the two rows, with their measured cost) and
|
||||
[`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B.
|
||||
|
||||
### What this release decided, beyond D123–D125
|
||||
|
||||
- **A hook that exists only for Advanced metrics is not put into a game that was never asked.** The two rows are
|
||||
gated at the top of `InstallByFamily`, before the symbol is resolved (resolving holds the module). Once a
|
||||
session with the option on has started in a process, the patch goes in on that watchdog tick and **stays for the
|
||||
life of the process**: a later session with the option off finds the detour there, forwarding without looking.
|
||||
Removing a patch between sessions would be a second patch event in a running game for nothing gained. So "off
|
||||
means off" (D111) is, for these two: nothing read, nothing published — and, in a game no session ever asked,
|
||||
nothing patched. Privacy Policy 2.17 §4 says it that way.
|
||||
- **Privacy Policy 2.17, not 2.16 stretched.** beta.40's plan had 2.16 stand "once for the three releases"; its
|
||||
text then listed DLSS's and FSR's parameters by name, and neither list holds Streamline's constants or the
|
||||
frame-generation configuration. The plan of beta.43 carried the new sentences and the owner approved them with it.
|
||||
**beta.44 reads feature versions and requirements — check 2.17's lists the same way before assuming it covers
|
||||
them.**
|
||||
- **For each of the two calls a session says which of three things happened** (`AdvancedInGameCall`): read; hooked
|
||||
and the game never called; not hooked. "Not hooked" is three causes the session does not tell apart — the game
|
||||
did not load the library, a Streamline 1.x interposer (refused), a patch the registry refused — and the Overlay's
|
||||
log does: a `HOOK_INSTALLED` line naming the function, or a `PATCH_FAILED`.
|
||||
- **A count is not part of what makes a session's facts new.** `sl.constants.resets` grows all session; the
|
||||
recorder's context would be rewritten each second. `InGameAdvancedSampler.Conclude` brings it up to date once, at
|
||||
the end. A session recovered after a crash holds the count as of the last time some other field moved — a lower
|
||||
bound.
|
||||
- **Streamline's summaries are the first viewport's**, and the configure count has an owner slot of its own (the
|
||||
2.3 loader would otherwise bring one configure to two modules, as D125's dispatch).
|
||||
- **The accuracy statement no longer says nothing of what a game tells its upscaler was read from a real game.**
|
||||
FSR's upscaling values were (beta.41, beta.42: Lies of P, Dying Light: The Beast, Kingdom Come: Deliverance II).
|
||||
The DLSS options, Streamline's constants and the frame-generation configuration are still unconfirmed, and the
|
||||
three copies say so.
|
||||
|
||||
### Traps this train left
|
||||
|
||||
- **An unpatched export may already begin with a jump.** The loader stub's `ffxConfigure` starts with `E9` in the
|
||||
file: "the first byte is not a jump" is not a test of "not patched". `ReadTargetExportBytes` compares the target's
|
||||
bytes with the file's own (`inFile`).
|
||||
- **A branch stacked on a pull request that is then squashed**: `git rebase --onto origin/main <the old tip>`, and
|
||||
`git diff <old tip> <squash>` empty says the gate that ran still stands.
|
||||
- **`mcp__ccd_pr__set_auto_merge` says "not bound" for a pull request opened from a script**: `gh pr merge <n>
|
||||
--auto --squash`. A run's artifacts while it is still in progress: `gh api
|
||||
repos/…/actions/artifacts/<id>/zip`.
|
||||
- **clang-format re-wraps what an edit script wrote**, so a second script's anchors must be read from the formatted
|
||||
file; a multi-file script that fails part-way has already written the earlier files.
|
||||
- **One local gate printed 871 App tests where every other printed 872**, green. Not looked into.
|
||||
|
||||
### What the owner's nine sessions on beta.43 showed (2026-11-12)
|
||||
|
||||
Run 15:42–16:21 in the owner's time zone, read the same afternoon from a copy of the ledger (sessions 171–179), the
|
||||
Agent's log, the nine overlay logs and Windows' application log. Advanced metrics was on for the first eight and off
|
||||
for the last.
|
||||
|
||||
| # | Game | What it showed |
|
||||
|---|---|---|
|
||||
| 171 | Phantom Blade Zero, 649 s, DLSS frame generation ×3.0 | Streamline 2.14.1: **read** — jitter ≤ 0.47, motion-vector scale 0.0009 / 0.0016, near 0.01 and far 75,000 with depth inverted, field of view 0.6545–1.3612 rad, aspect 1.7767, 1 reset. FSR frame generation: hooked on the loader and both leaves, the game never called |
|
||||
| 172 | Lies of P, 35 s, exit code 3 | 542 frames, nothing evaluated. **The owner: the game crashed after a shader failed to compile.** The crash policy counted it and turned the game's hooking off (below) |
|
||||
| 173 | Lies of P, 130 s | Tier 2 — hooking was off; the owner switched it on again at 16:02 |
|
||||
| 174 | Lies of P, 94 s, FSR 3 + FSR frame generation ×2.0 | **`ffxConfigure` read** on the one-module `amd_fidelityfx_dx12.dll`: frame generation on and off, not asynchronous, generated frames not presented alone, 2560 × 1440 at 0, 0; the log has `FFX_CONFIGURE` types `0x10007` and `0x20002`. Streamline: not hooked (the game has none) |
|
||||
| 175 | Cyberpunk 2077, 72 s, no upscaler named, no frame generation | Streamline 2.14.1: **read** — jitter ≤ 0.5, motion-vector scale 1 / 1, near 0.02 and far 16,000 inverted, aspect 1.7778, **field of view 51.0055–90**, 2,575 resets |
|
||||
| 176 | Cyberpunk 2077, 145 s, DLSS + DLSS frame generation ×2.0 | the same values; 1,821 resets. FSR frame generation: hooked on the loader and both leaves, never called |
|
||||
| 177 | Kingdom Come: Deliverance II, 135 s, FSR | Streamline: not hooked. `ffxConfigure` hooked on the loader and the upscaler, never called — the game ships no frame generation |
|
||||
| 178 | Hogwarts Legacy, 158 s, DLSS frame generation ×4.0 | Streamline 2.14.16: **read** — jitter ≤ 0.47, field of view 0.8872–2.0071 rad, aspect 1.7763, near 0.01 and far 75,000 inverted, 11 resets. `ffxConfigure` hooked on `amd_fidelityfx_dx12.dll`, never called |
|
||||
| 179 | Lies of P, 129 s, **Advanced metrics off**, a new Agent, the game started afresh | no Advanced row; bits 13 and 14 clear in `hooks_installed_mask`; the log has `ffxDispatch` and `ffxQuery` and **no `ffxConfigure` line** |
|
||||
|
||||
- **The two hooks did what they were built to do on four real games**, three Streamline builds apart (2.14.1 twice,
|
||||
2.14.16) and one FSR library. No `PATCH_FAILED`, no fault counted, in nine logs. `legal_acceptance` holds Privacy
|
||||
Policy 2.17 accepted once, four seconds after the update; no session since the update ended with
|
||||
`guard=ModuleScanFailed` (the day's one is beta.42's, at 10:05).
|
||||
- **Cyberpunk 2077 gives Streamline its field of view in degrees.** The vendor's header says radians; the game
|
||||
passes 51–90. Every other field of the same struct is sane (the aspect ratio beside it is 1.7778), so the layout
|
||||
is not in question — the game's unit is. The page prints `51.0055 – 90 rad (2922.4° – 5156.6°)`: **a defect of
|
||||
the label, not of the reading**, and beta.44's first pull request. The two stored sessions keep the string they
|
||||
were stored with.
|
||||
- **A resets count has no denominator.** 2,575 in a 72 s session that was mostly menus and 1,821 in 145 s on
|
||||
Cyberpunk, beside 1 and 11 on the two Unreal games. It is what the game said (`reset == eTrue`, the first
|
||||
viewport's calls); the page does not say out of how many calls.
|
||||
- **A frame-generation configuration with no flag set has no flags row**, where an upscale with none says `none`.
|
||||
- **Lies of P's 35 s end turned its hooking off, and one such end is now enough.** `hook_crash_count` is never set
|
||||
back: the game's two ends of 2026-10-19/20 (`19_SAFETY` §Crash & stability safety, the hand-off to Steam) had
|
||||
brought it to 2, the owner had switched hooking on again, and today's single early end made 3 — at or over
|
||||
`CrashesToDisable`, so hooking went off at once, under a reason that says *twice*. Whether switching hooking back
|
||||
on starts the count again is the owner's decision; it is asked with beta.44's plan.
|
||||
- **Hogwarts Legacy faults in the driver's `_nvngx.dll` as it exits, hooked or not.** Windows' application log has
|
||||
the same fault (0xc0000005 at +0x6aa85, `_nvngx.dll` 32.0.16.2114) six times since 2026-11-06, each at the end
|
||||
of one of the game's seven recorded sessions — the first of them session 131, which nothing was injected into.
|
||||
That one reads `crashed`; the five hooked ones, today's 178 among them, read `normal` with exit code 0, the
|
||||
fault logged in the second the session was saved. **Why a hooked session does not see the crash event that an
|
||||
unhooked one does was not looked into.**
|
||||
- **Frame rates as before**, where the settings were: Lies of P 59 → 118 (beta.42: 58.9 → 118.0), Kingdom Come 59.3
|
||||
(59.4), Hogwarts Legacy 58.8 → 235.8 at ×4 (alpha.3: 56.1 → 225.1). Phantom Blade Zero's factor moves between
|
||||
sessions under the driver's dynamic mode (×2.9 to ×4.1 since 2026-11-05) and Cyberpunk was run with other settings.
|
||||
- **Not exercised**: a configure through the FidelityFX 2.3 loader (Cyberpunk 2077 with FSR frame generation) — the
|
||||
configure count's owner slot has not met a real game; a game with neither library; Dying Light: The Beast.
|
||||
Phantom Blade Zero and Hogwarts Legacy name no upscaler beside DLSS frame generation, as on every release before.
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**The owner runs item 41**~~ **Run and read 2026-11-12** (§What the owner's nine sessions on beta.43 showed).
|
||||
The owner's word was to go on if it passed, and it is judged passed: both hooks read real games, nothing
|
||||
failed to patch, off meant off. What was not exercised is listed there and stays open.
|
||||
2. **0.1.0-beta.44** — first the field of view a game gives in degrees (and what else the nine sessions found),
|
||||
then `slGetFeatureVersion` and `slGetFeatureRequirements`. Both are calls a game makes while starting, so most
|
||||
sessions will have missed them: plan what "not seen" says. ~~**Planned with the owner before any code.**~~ **The
|
||||
plan was approved 2026-11-12 with three decisions, D126–D128** (the count of early abnormal ends starts again
|
||||
at a grant; the fault at exit is written down only; a field of view over π is shown as given), and with Privacy
|
||||
Policy 2.18's wording. Four pull requests: the fixes; the two hooks in the Overlay; the Agent, the App and the
|
||||
policy; the release.
|
||||
3. **Trains C and D** (beta.45, beta.46) each begin with a spike and end in the owner's go or no.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request, with what SonarCloud and Qodana said of #413–#417 (the
|
||||
`sonarcloud` job on `main` is cancelled by the next merge, so it answers on the release's commit).~~ **Recorded
|
||||
2026-11-12: 0.1.0-beta.43 was released 2026-11-12T06:57:57Z** (13:57 in the owner's time zone) from the signed
|
||||
tag on `6c7ba74` (#418), by run 43169675460 — green at the first attempt, one run for the one tag push. Eight
|
||||
assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed; the four shipped natives carry
|
||||
`FL_BUILD_ID v0.1.0-beta.43`. The delta from beta.42 is 1,934,264 bytes beside a full package of 110,736,398 —
|
||||
"Delta processed 0452 files. 0025 patched, 0427 unchanged". The wiki was published by run 43171842051. The
|
||||
rehearsal on the release branch (run 43167388933, the same tree before it was rebased onto #417's squash) had
|
||||
made a delta of 1,944,086 bytes with the same file counts. **SonarCloud answered on `6c7ba74`: the quality gate
|
||||
passed and no issue is open on `main`. Qodana's two reports are green on that commit**, and were on #417's.
|
||||
- ~~**No real game was run on this build.** Two new patch sites, tested with the harness and the stubs; their cost
|
||||
measured on the headers. Whether a real `sl.interposer.dll` 2.x lays `sl::Constants` out as the vendored header
|
||||
does is checked on every call by the struct's GUID and version, not by a real game yet.~~ **Nine sessions on five
|
||||
games, 2026-11-12** (§What the owner's nine sessions on beta.43 showed): interposers 2.14.1 and 2.14.16 lay the
|
||||
struct out as the header does. **The accuracy statement's three copies and `LIMITATIONS.md` still say Streamline's
|
||||
constants and the frame-generation configuration "have not been confirmed" on a real game** — reworded with
|
||||
beta.44's first pull request. **`docs/LIST_GAME_TESTED.md` is as of 2026-11-06**: refreshing it is a new copy and
|
||||
the owner's review.
|
||||
- **Item 40 (d)** — a session that changes upscaler — was not exercised, and the owner has not said item 40 passed.
|
||||
**Items 36 (d) and 37 are still open.**
|
||||
- **What an empty process snapshot does to the watcher's tick in a real session** was not looked into
|
||||
(`ToolhelpProcessSnapshotSource.Take` returns an empty list and says nothing; seen once in a test on 2026-11-12).
|
||||
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
|
||||
sensors "have never been read on real hardware"** — the owner's to reword. The alpha line still rests (D98).
|
||||
|
||||
**Owner-only:** what item 41 left unexercised — (d) through the FidelityFX 2.3 loader, (e) a game with neither library; item 40 (d).
|
||||
@@ -1,182 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.44
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.45 was cut, 2026-11-12 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`. **Its §NEXT says 0.1.0-beta.45 is planned**: it was released the same day, and what it built and decided is HANDOFF.md's section for it.*
|
||||
|
||||
## **START HERE** — 2026-11-12, 0.1.0-beta.44: what the first real games on beta.43 found, fixed; Streamline's answers about a feature, hooked only where asked
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.44.md`; this is what no other file carries.* The owner ran nine sessions on
|
||||
beta.43 the afternoon it was released and said: read them, write down the result, go on if it passes. They were read
|
||||
from a copy of the ledger, the Agent's log, nine overlay logs and Windows' application log (#420); item 41 was judged
|
||||
passed, and the owner decided D126–D128 and approved the plan the same afternoon, Privacy Policy 2.18's wording with
|
||||
it. Four pull requests and this one: #421 (the fixes: a field of view in degrees, the count of early abnormal ends,
|
||||
`flags` of `none`; D126–D128), #422 (`slGetFeatureVersion` and `slGetFeatureRequirements` in the Overlay), #423
|
||||
(the Agent, the App, Privacy Policy 2.18). **What the nine sessions showed, session by session, is
|
||||
[`handoff/history/0.1.0-beta.43.md`](handoff/history/0.1.0-beta.43.md)**; what each pull request built is
|
||||
[`19_SAFETY_AND_ANTICHEAT.md`](19_SAFETY_AND_ANTICHEAT.md) §Crash & stability safety,
|
||||
[`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Hook inventory (the row of the two calls, with their measured cost) and
|
||||
[`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B.
|
||||
|
||||
### What this release decided, beyond D126–D128
|
||||
|
||||
- **What is read of these two calls is the answer, and only a good one.** The detours call the original first and
|
||||
read the struct the game passed when it returned `eOk`; a refusal leaves the struct as the game made it, and the
|
||||
fixture's stub leaves 99s in it to prove nothing of a refused answer is kept. The pointers the answer carries —
|
||||
the list of required buffer tags, the names of Vulkan extensions and features — are never followed; the stub's
|
||||
are wild, and no fault is counted.
|
||||
- **The feature slots are the one group of region 5 a new request does not empty.** Every other group is a
|
||||
session's — ranges, counts, switches seen. Which version a feature is and what it requires are facts about the
|
||||
process, and a game asks once: a second session of a game that kept running would have nothing where the first
|
||||
had the answer. `Reset` keeps the slots and their bit of the mask. They were read only while a session asked.
|
||||
- **The two rows are the first of the table, because rows are patched in the table's order.** Nothing in the
|
||||
Overlay paces the installs: the 0.1–0.25 s between `HOOK_INSTALLED` lines in the owner's logs is MinHook stopping
|
||||
every thread of the game for each patch. In a process that was asked, the two calls a game makes while starting
|
||||
are the ones that cannot wait behind five others; in a process never asked, the two rows are passed over before
|
||||
anything is resolved.
|
||||
- **"Hooked, and the game did not call" has words of its own for a call made while starting**
|
||||
(`AdvInGameCall_NotAskedAgain`). For a call made every frame it is a finding about the game; for these two it is
|
||||
what every late attach will say. One bit of the mask covers both questions, so which was answered is told by the
|
||||
slots (`InGameAdvancedSampler.FeatureCall`).
|
||||
- **Privacy Policy 2.18, not 2.17 stretched**: 2.17 says "two further calls" and lists what they give. 2.18 also
|
||||
says what of the answer is never read.
|
||||
- **The rows are the vendor's words**: `kFeatureDLSS_G · versionNGX`, the requirement flags by their enumerators,
|
||||
an id this build has no name for as `feature <number>`. A version of all zeros has no row, except `versionSL`.
|
||||
- **The Agent's end-to-end tests run a Streamline target now** (until this release only an FSR one): the constants
|
||||
and the two answers, through the shipped Agent and the real Overlay.
|
||||
- **A field of view over π is two rows** (D128): the number, and `cameraFOV unit` with the token `not_radians` —
|
||||
a token replaces a row's value in the App, so a note beside a number is a row of its own.
|
||||
- **The count of early abnormal ends is set back by the consent grant and by nothing else** (D126) — the one
|
||||
statement that turns hooking on. `hook_autodisabled_reason` and `_at` stay as the row's history; the App shows
|
||||
them only while hooking is off.
|
||||
|
||||
### Traps this train left
|
||||
|
||||
- **`vswhere -latest` names SQL Server Management Studio on this PC.** Ask for the C++ tools as `build.ps1` does
|
||||
(`-requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64`). The `x64-release` preset writes no
|
||||
`compile_commands.json`: `ninja -C build/native/x64-release -t commands FrameLedger.Overlay` gives the Overlay's
|
||||
flags for a bench.
|
||||
- **Run clang-format on the native files an edit script wrote before the gate** — the format check comes after the
|
||||
native build and tests, and a miss costs the whole run.
|
||||
- **`tools/resx-gen.ps1` needs `-Resx src/FrameLedger.App/Strings.resx`**; started without it from a shell that
|
||||
has no console it waits for the missing parameter until it is stopped.
|
||||
- **A Python script passed to a shell as a here-document loses its backslashes** before Python sees them: write
|
||||
the script to a file.
|
||||
- **`gh pr checks --watch` returns at once when no check has started yet**; wait a moment before starting it.
|
||||
- **Qodana's native report is advisory, and auto-merge does not wait for it.** On #422 it reported three
|
||||
`bugprone-implicit-widening-of-multiplication-result` in the test and the harness (an index into the feature
|
||||
slots computed as a product of two 32-bit values: compute it in `size_t`) while the required checks were still
|
||||
running; auto-merge was switched off until the fix was pushed. A finished job's log while its run is still going:
|
||||
`gh api repos/…/actions/jobs/<id>/logs --allow-escape-sequences`; the report's SARIF is a zip inside the
|
||||
artifact's zip.
|
||||
- **GPG's pinentry timed out once** (the cache had expired); the second attempt went through when the owner was
|
||||
at the keyboard.
|
||||
|
||||
### What the owner's eight sessions on beta.44 showed (2026-11-12)
|
||||
|
||||
Run 19:52–20:46 in the owner's time zone, read the same evening from a copy of the ledger (sessions 181–188), the
|
||||
Agent's log, eight overlay logs and Windows' application log. Advanced metrics was on throughout.
|
||||
|
||||
| # | Game | What it showed |
|
||||
|---|---|---|
|
||||
| 181 | Phantom Blade Zero, 796 s, DLSS frame generation ×4.0 | Streamline 2.14.1. **Both questions read**: versions of `kFeatureReflex`, `kFeatureDLSS_G`, `kFeaturePCL`; requirements of those and `kFeatureDeepDVC`. The constants as on beta.43 |
|
||||
| 182 | Clair Obscur: Expedition 33, 107 s, FSR + DLSS frame generation ×3.0 | Streamline 2.7.30. **Both read** (`kFeatureDLSS_G`, `kFeatureReflex`, `kFeaturePCL`); the constants and FSR's upscale values read beside them |
|
||||
| 183 | Valor Mortis (Microsoft Store), 51 s, **crashed** — exit code `0xC0000005` | Streamline 2.14.1. Both read before it ended. The game's second early abnormal end, so hooking went off (below) |
|
||||
| 184 | Valor Mortis, 935 s, ×6.0 | hooking switched on again at 20:11; both read; ended normally |
|
||||
| 185 | Black Myth: Wukong, 167 s, ×4.0 | Streamline 2.7.4. Both read |
|
||||
| 186 | Cyberpunk 2077, 257 s, DLSS + DLSS frame generation ×2.0 | **The field of view reads `51.0055 – 90` with a row `cameraFOV unit` = *not radians*** (D128). Requirements **read** for `kFeatureDLSS`, `kFeatureDLSS_RR`, `kFeatureDLSS_G`, `kFeatureReflex`, `kFeatureNIS`; the version question *hooked, not asked again* |
|
||||
| 187, 188 | Kingdom Come: Deliverance II, 39 s and 289 s | no Streamline: the constants and both questions *not hooked*; `ffxConfigure` hooked and never called. Neither session reached an FSR dispatch (the upscaler's first query came 11 s before the second one ended) |
|
||||
|
||||
- **The two questions were read in six of six Streamline sessions, on five games** — the plan, the release notes
|
||||
and four documents said most sessions would show nothing, because a game asks while it starts. Unreal's
|
||||
Streamline plugin (four of the five games) asks again after the attach, and Cyberpunk 2077 asks for requirements
|
||||
again; only Cyberpunk's version question was *not asked again*. The three answers of the line were each seen.
|
||||
The documents are corrected in the same pull request as this text.
|
||||
- **What was read agrees with the PC.** `driverVersionDetected` 621.14.0 is the snapshot's driver
|
||||
(`32.0.16.2114`), `osVersionDetected` 10.0.29648 its Windows build, `versionNGX` of `kFeatureDLSS_G` the file
|
||||
version of the game's `nvngx_dlssg.dll` (310.9.1, 310.6.0), `versionSL` of Reflex and PCL the interposer's.
|
||||
- **`kFeatureDLSS_G`'s `versionSL` is 2.14.16 on three games that ship 2.14.1 or 2.7.30** (Phantom Blade Zero,
|
||||
Valor Mortis, Clair Obscur): Streamline answers for a newer frame-generation plugin than the game's own folder
|
||||
holds. Which file that is was not looked into — an updated plugin delivered by NVIDIA's app is the likely one.
|
||||
It is the first value of this kind that a file's version could not have given.
|
||||
- **No Unreal game asked about `kFeatureDLSS`.** Their DLSS upscaling does not go through Streamline (Cyberpunk's
|
||||
does: it is asked about, and the session names DLSS). That is the likely reason Phantom Blade Zero, Hogwarts
|
||||
Legacy, Valor Mortis and Black Myth: Wukong name no upscaler beside DLSS frame generation — the question left
|
||||
open since beta.43. Naming it would take a hook on NGX, which this project does not have.
|
||||
- **Valor Mortis crashed 51 s into a hooked session, as it did on beta.40.** Session 141 (2026-11-12 02:44,
|
||||
beta.40: `0xC0000005` after 51 s, 498 frames) and session 183 (20:09, beta.44: the same code after 51 s, 8,077
|
||||
frames); the session after each ran normally under the same build. So it is not this release's hooks. Whether
|
||||
FrameLedger has any part in it is not known: Windows logged no event for either (a Store package), and there is
|
||||
no unhooked start to compare. **The crash policy did what D126 says**: today's was the game's second early end, so
|
||||
hooking went off at 20:09:52; the owner switched it on at 20:11:03 and the count is 0.
|
||||
- **Black Myth: Wukong faults in Steam's `crashhandler64.dll` as it exits** (0xc0000409 at +0x39b49) — at each of
|
||||
its three recorded exits, all hooked (beta.40 twice, beta.44 once); each session reads `normal`, the shape D127
|
||||
wrote down for Hogwarts Legacy. **There is no unhooked exit to compare**: one session of it with hooking off
|
||||
would say whether FrameLedger has a part.
|
||||
- **No `PATCH_FAILED`, no fault counted, in eight logs**; Privacy Policy 2.18 was accepted once, eight seconds
|
||||
after the update. The two new rows are the first Streamline `HOOK_INSTALLED` lines of every log. Frame rates as
|
||||
before where the settings were: Clair Obscur 106 → 323 (beta.41: 106 → 318), Valor Mortis 39.6 → 237 (37.7 →
|
||||
228). Wukong's native rate was 90 where beta.40's two sessions had 124; nothing says whether the scene and
|
||||
settings were the same.
|
||||
- **Not exercised: off means off** — every session had Advanced metrics on. And, from item 41: a configure through
|
||||
the FidelityFX 2.3 loader.
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**The owner runs item 42**~~ **Run and read 2026-11-12** (§What the owner's eight sessions on beta.44
|
||||
showed): both hooks read real games — far more often than planned for — the degrees fix reads right on
|
||||
Cyberpunk 2077, a game with no Streamline says *not hooked*. *Off means off* was not exercised.
|
||||
2. **The next version, by the owner's word of 2026-11-12: `slInit`, `slIsFeatureSupported` "and some other parts"**
|
||||
— said the evening beta.44 came out, to be done if beta.44 passed, and then "update and go on" once these
|
||||
sessions were in. It reopens D112 (`slInit` is not hooked in train B; if ever: never `applicationId`,
|
||||
`projectId`, the paths), and `slIsFeatureSupported` is handed an `sl::AdapterInfo` whose `deviceLUID` and
|
||||
`vkPhysicalDevice` are not to be read (D104). ~~**Planned with the owner before any code**: which other parts,
|
||||
what of each is read, the Privacy Policy's wording, and where train C goes.~~ **Planned and approved 2026-11-12
|
||||
(D129–D131)**: `slInit` stays out — shown why it cannot be seen, the owner chose so; six calls go in, in one
|
||||
release, **0.1.0-beta.45** — `slIsFeatureSupported`, `slIsFeatureLoaded`, `slSetFeatureLoaded`,
|
||||
`slAllocateResources`, `slFreeResources`, `slShutdown`; Privacy Policy 2.19's wording approved with the plan.
|
||||
Pull requests: three hooks, three hooks, the Agent and the App with the policy, the release.
|
||||
3. **Train C (Reflex latency per frame)**: its spike is written beside beta.45, a document only; code waits for the
|
||||
owner's go after reading it. **Train D** after that, the same way.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request, with what SonarCloud and Qodana said.~~ **Recorded
|
||||
2026-11-12: 0.1.0-beta.44 was released 2026-11-12T12:24:26Z** (19:24 in the owner's time zone) from the signed
|
||||
tag on `f9e9fdb` (#424), by run 43214789700 — green at the first attempt, one run for the one tag push. Eight
|
||||
assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed; the four shipped natives carry
|
||||
`FL_BUILD_ID v0.1.0-beta.44`. The delta from beta.43 is 1,866,183 bytes beside a full package of 110,750,960 —
|
||||
"Delta processed 0452 files. 0025 patched, 0427 unchanged". The wiki was published by run 43217647799. The
|
||||
rehearsal on the release branch (run 43204362797, at `56b1157` — the released tree but for two namespace
|
||||
qualifiers #423 dropped afterwards) had made a delta of 1,878,774 bytes with the same file counts. **SonarCloud
|
||||
answered on `f9e9fdb`: the quality gate passed and no issue is open on `main`. Qodana's two reports are green on
|
||||
that commit.** Qodana found two things on the way, each fixed before its pull request merged: three index
|
||||
products in the injected test and the harness (#422, native), and two namespace qualifiers a new `using` made
|
||||
redundant (#423, managed) — #423's auto-merge was held until that report was in. **`check` failed once on
|
||||
#424**, a pull request that changes no code: the CaptureHost's launch-mode end-to-end test
|
||||
(`LaunchModeStartsTheHarnessItselfAndReportsWhatRanUnhooked`) read 19.8 presented frames a second from the
|
||||
harness on a slow runner where it asks for more than 30; the job was run again and passed. A rate asserted
|
||||
against a wall clock on a shared runner — the one flake of this train, not looked into further.
|
||||
- ~~**No real game was run on this build.** Two new patch sites, tested with the harness and the stub; their cost
|
||||
measured on the headers.~~ **Eight sessions on six games, 2026-11-12** (§What the owner's eight sessions on
|
||||
beta.44 showed). **The release notes on GitHub still say "most sessions will show nothing of the two new
|
||||
readings"** — a prediction the sessions did not bear out; `docs/changelog/0.1.0-beta.44.md` is a released file
|
||||
and is not edited, and the published notes were left as they are.
|
||||
- **Valor Mortis's crash at 51 s** (twice, beta.40 and beta.44) **and Black Myth: Wukong's fault in Steam's crash
|
||||
handler at every exit** are not explained. One session of each with hooking off is the comparison that is missing.
|
||||
- **What item 41 left unexercised**: a configure through the FidelityFX 2.3 loader (Cyberpunk 2077 with FSR frame
|
||||
generation), a game with neither library.
|
||||
- **A fault while a game is closing is not seen by a hooked session** (D127: written down, not changed). Looking
|
||||
again later would make every session of Hogwarts Legacy `crashed`, and under a user-mode exception would end the
|
||||
exception for a fault no hook caused; the decision is the owner's, and is not taken.
|
||||
- ~~**Phantom Blade Zero and Hogwarts Legacy name no upscaler beside DLSS frame generation**, as on every release
|
||||
before; not looked into.~~ **Likely answered 2026-11-12**: no Unreal game asks Streamline about `kFeatureDLSS`, so
|
||||
their DLSS upscaling does not pass through the calls this project hooks.
|
||||
- **`docs/LIST_GAME_TESTED.md` is as of 2026-11-06**: refreshing it is a new copy of the ledger and the owner's review.
|
||||
- **Item 40 (d)** was not exercised and the owner has not said item 40 passed. **Items 36 (d) and 37 are still open.**
|
||||
- **What an empty process snapshot does to the watcher's tick in a real session** was not looked into (seen once in
|
||||
a test on 2026-11-12).
|
||||
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
|
||||
sensors "have never been read on real hardware"** — the owner's to reword. The alpha line still rests (D98).
|
||||
|
||||
**Owner-only:** item 42 (f), and one session each of Valor Mortis and Black Myth: Wukong with hooking off; what
|
||||
item 41 left unexercised; item 40 (d).
|
||||
@@ -1,175 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.45
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.46 was cut, 2026-11-13 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`. **Its §NEXT says 0.1.0-beta.46 is to come**: it was released the next day, and what it built and decided is HANDOFF.md's section for it.*
|
||||
|
||||
## **START HERE** — 2026-11-12, 0.1.0-beta.45: six more of Streamline's calls, hooked only where asked; `slInit` stays out; the Reflex spike as a document
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.45.md`; this is what no other file carries.* The owner ran eight sessions on
|
||||
beta.44 the evening it was released and said: add the three new ones, update, go on. They were read from a copy of
|
||||
the ledger and the logs (#426); asked to reopen D112, the owner was shown why `slInit` cannot be seen and chose to
|
||||
leave it out (D129), chose six other calls for one release (D130), and approved the plan with Privacy Policy 2.19's
|
||||
wording. Four pull requests and this one: #427 (`slIsFeatureSupported`, `slIsFeatureLoaded`, `slSetFeatureLoaded`
|
||||
in the Overlay; D129–D131), #428 (`slAllocateResources`, `slFreeResources`, `slShutdown`), #429 (the Agent, the
|
||||
App, Privacy Policy 2.19), #430 (train C's spike, a document: `spike-notes` §30). **What the eight sessions on
|
||||
beta.44 showed, session by session, is [`handoff/history/0.1.0-beta.44.md`](handoff/history/0.1.0-beta.44.md)**;
|
||||
what each pull request built is [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Hook inventory (the two rows of the six
|
||||
calls, with their measured cost) and [`18_GPU_VENDOR_APIS.md`](18_GPU_VENDOR_APIS.md) §Train B (the fourth step).
|
||||
|
||||
### What this release decided, beyond D129–D131
|
||||
|
||||
- **Everything the six calls give is word 1 of a feature's slot, and one reserved word.** Bits 2–4 the two answers
|
||||
(supported, with the `sl::Result` in bits 8..15; loaded and its value), bits 5–6 the game switching the feature
|
||||
off and on, bits 16..19 and 20..23 two counts that stop at fifteen and never carry; `slShutdowns` took the first
|
||||
of three reserved words (@308). Layout 5 and schema 23 as they were. **The answers are the process's and a new
|
||||
request keeps them; the switching, the counts and the shutdowns are a session's and a new request clears them.**
|
||||
- **A refusal is the answer.** `slIsFeatureSupported`'s detour calls the original first and keeps whatever it
|
||||
returned; the page names it by NVIDIA's enumerator (forty codes, the same order at sixteen upstream tags from
|
||||
v2.0.0 to v2.14.16), `result <n>` past the list, 255 for a code a byte could not carry.
|
||||
- **The two calls on a game's way out note the call, then call the original, and run nothing after it** —
|
||||
`slFreeResources` and `slShutdown`. The fixture shuts Streamline down and goes on using the stub through every
|
||||
detour.
|
||||
- **The adapter is never read** (D131), and the build refuses the names of `sl::AdapterInfo`'s members in the code
|
||||
loaded into a game (`overlay-fields-check`); the fixture hands a wild LUID pointer.
|
||||
- **A stop restores its patches one after another, about 160 ms each.** MinHook stops every thread of the process
|
||||
for each `MH_DisableHook`. With six more patches the stop's last log lines were cut at the two seconds the
|
||||
Overlay waited for them; the wait is now sized to the patch table (`250 ms × kMaxPatches`). The patches were
|
||||
always restored; `UNHOOKED` is written after the last. **Not changed, and proposed**: queueing the restores (and
|
||||
the installs) so the threads are stopped once — a change to the hook engine's order of operations, which wants
|
||||
its own pull request, its own measurement and the owner's word. Until then a stop in a Streamline game with
|
||||
Advanced metrics on takes two to three seconds on the thread that stops.
|
||||
- **Six calls are one sentence on the page**, each by its function's name under which of three things became of
|
||||
it; a row stored before this release has none of the six and no such sentence.
|
||||
- **`AdvancedReach.BeforeAttach` is a reason of its own** for `sl.init.preferences`: not "a later release". No
|
||||
catalog entry carries `NewHook` any more; the value stays, for rows a later train may add.
|
||||
- **Where the rows sit in the table** (rows are patched in its order): the two questions after beta.44's two, at
|
||||
the head; `slSetFeatureLoaded` after `slSetConstants`; the three counted calls last of the Streamline block.
|
||||
- **Train C's spike is a reading** (`spike-notes` §30): hooking NVAPI's or Streamline's latency functions is
|
||||
refused or is train D's wrapper; the Overlay calling `slReflexGetState` breaks the vendor's thread contract;
|
||||
what remains is the Overlay calling two driver getters with the game's device, and a no-injection ETW route
|
||||
that gives half the number. It ends in three questions that are the owner's.
|
||||
|
||||
### Traps this train left
|
||||
|
||||
- **The catalog table of `18_GPU_VENDOR_APIS` is compared with the catalog row for row by a test**: a catalog
|
||||
entry and its row go in the same commit, or the Application tests are red.
|
||||
- **Qodana's native report again found an index into the feature slots computed as a 32-bit product** (#427, the
|
||||
harness's probe): write `size_t{2} * FL_ADV_FEATURE_WORDS`. It is advisory and auto-merge does not wait for it;
|
||||
both reports were read before each merge.
|
||||
- **A second `region` inside the probe's block is C4456**, and warnings are errors: name the inner one otherwise.
|
||||
- **A test method over sixty lines is MA0051** in the test projects too; split the assertions by what they cover.
|
||||
- **The injected test waits for the stop**: with eighteen patches a stop takes about three seconds, so its wait is
|
||||
200 iterations.
|
||||
- **The shell tool refuses `sleep N; command`**: wait in a background `until` loop.
|
||||
- **After a lower pull request is squashed**, `git diff <old tip> origin/main` empty proves the squash is the
|
||||
branch; then `git rebase --onto origin/main <old tip> <next branch>` and a forced push with lease.
|
||||
|
||||
### What the owner's seven sessions on beta.45 showed (2026-11-13)
|
||||
|
||||
The owner ran seven sessions on six games the day after the release and said: check the logs and go on. Read from
|
||||
a copy of the ledger (sessions 190–196), the seven overlay logs, the Agent's log and Windows' application log —
|
||||
no FrameLedger binary was run against the owner's data. **Every session is hooked, `normal`, with no fault
|
||||
counted, no dropped record and no `PATCH_FAILED`; the count of early ends is 0 on all six games.** The update
|
||||
showed the terms once: Privacy Policy 2.19 was accepted at 07:23:36.
|
||||
|
||||
| Game (session, length) | Interposer | `slIsFeatureSupported` | `slIsFeatureLoaded` | `slSetFeatureLoaded` | allocate | free | shutdown |
|
||||
|---|---|---|---|---|---|---|---|
|
||||
| Phantom Blade Zero (190, 2 h 48 min; 191, 1 h 32 min) | 2.14.1 | **read** — Reflex, DLSS frame generation, PCL `eOk`; ImGUI and DeepDVC `eErrorFeatureMissing` | **read** — Reflex, frame generation *on* | not called | not called | **read** — frame generation, 1 | not called |
|
||||
| Cyberpunk 2077 (193, 7 min) | 2.14.1 | **read** — frame generation, DLSS, ray reconstruction, Reflex `eOk`; NIS `eErrorFeatureMissing` | **read** — the four *on* | **read** — the four, *on and off* | not called | not called | not called |
|
||||
| Dying Light: The Beast (194, 4 min) | 2.8.0 | **read** — DLSS, frame generation, PCL, Reflex, NIS `eOk` | not called | **read** — all five, *on and off* | not called | not called | **read** — 1 |
|
||||
| Hogwarts Legacy (195, 4 min) | 2.14.16 | **read** — frame generation, Reflex, DeepDVC, DLSS 5's `kFeatureDLSS_NR`, PCL `eOk`; ImGUI `eErrorFeatureMissing` | **read** — the first four *on* | not called | not called | not called | not called |
|
||||
| Black Myth: Wukong (196, 3 min) | 2.7.4 | **read** — frame generation, Reflex, PCL `eOk` | not called | not called | not called | not called | not called |
|
||||
| Kingdom Come: Deliverance II (192, 4 min) | none | not hooked | not hooked | not hooked | not hooked | not hooked | not hooked |
|
||||
|
||||
- **`slIsFeatureSupported` was read in every Streamline session, and `slAllocateResources` in none.** Item 43
|
||||
wrote the meaning of that before the run: a call no game makes after the attach gives nothing in attach mode, and
|
||||
whether it keeps its patch is the owner's to say. `slFreeResources` and `slShutdown` were each read once, in one
|
||||
game each; `slIsFeatureLoaded` in three games, `slSetFeatureLoaded` in two.
|
||||
- **A refusal reads as one.** Phantom Blade Zero and Hogwarts Legacy ask about `kFeatureImGUI`, Streamline's
|
||||
debug overlay, and are told it is missing; Cyberpunk 2077 is told the same of NIS, which Dying Light is told is
|
||||
supported. Phantom Blade Zero is told DeepDVC is missing although Streamline answered its requirements.
|
||||
- **The count says how often, not when.** Dying Light's one shutdown and Phantom Blade Zero's one freeing of frame
|
||||
generation's resources may each be the game closing; nothing in a session says. Dying Light switched all five
|
||||
features off and on.
|
||||
- **The way out is as it was.** Hogwarts Legacy faulted at its exit in `_nvngx.dll`, `0xc0000005` at offset
|
||||
`0x6aa85` — the offset of its six before, since 2026-11-06, hooked or not — and Black Myth: Wukong in
|
||||
Steam's `crashhandler64.dll`, `0xc0000409` at `0x39b49`, the offset of its three before (Steam's file is now
|
||||
11.23.65.88). Windows' log has no fault for the other four games; the two hooks on a game's way out were in all
|
||||
five Streamline games.
|
||||
- **Rates are where they were**, for what a comparison without the same scene is worth: Phantom Blade Zero ×4 at
|
||||
64 → 255 (beta.44: 63 → 251), Wukong 85 → 341 (90 → 361), Cyberpunk 2077 164 → 327 (137 → 275), Dying Light ×4
|
||||
at 48 → 194 (beta.42: 54 → 216), Kingdom Come 58.8 presented (59.3).
|
||||
- **An install stops the game's threads once a patch, as a restore does.** The thirteen interposer patches took
|
||||
0.74 s on Phantom Blade Zero, 1.2 s on Cyberpunk 2077, 1.7 s on Dying Light and Wukong (twelve there) and
|
||||
**2.8 s on Hogwarts Legacy** — 57 to 215 ms a patch, while the game starts. That is the cost the proposal to
|
||||
queue patches (§What this release decided) would cut, measured on real games.
|
||||
- **No stop was exercised.** Every session ended with the game closing, so no log has an `UNHOOK_RESTORED` line.
|
||||
Item 43 (g) said a log "ends with an `UNHOOK_RESTORED` line for each patch": that is true only of a session
|
||||
stopped while its game runs, and the item was worded wrongly.
|
||||
- **Not exercised: off means off** — Advanced metrics was on in every session. **Not visible in the data**: (c), whether *loaded* agrees with the game's own menu, and (h), the
|
||||
catalog's wording on the page — both are what the owner sees.
|
||||
- **For train C's spike**: Streamline says Reflex is supported in all five games and loaded in the three that
|
||||
ask; Cyberpunk 2077 and Dying Light switch it off and on (`spike-notes` §30 has the note).
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**The owner runs item 43**~~ **Run and read 2026-11-13** (§What the owner's seven sessions on beta.45
|
||||
showed): five of the six calls read in real games, nothing different on the way out, no fault. *Off means off*
|
||||
was not exercised, and `slAllocateResources` was called by no game.
|
||||
2. ~~**The owner reads `spike-notes` §30 and answers its three questions.**~~ **Answered 2026-11-13 (D132,
|
||||
D133)**: route D goes to a spike on `hook-harness` and a stub — the owner ruled that a driver's read-only getter
|
||||
called with the device of the hooked swap chain is inside rule 4 — and no real game is touched before the owner
|
||||
has seen its result (`spike-notes` §31, to be written after 0.1.0-beta.46 is tagged); route C is refused; the
|
||||
ETW route stays closed. No shipped code changes for the spike.
|
||||
3. ~~**The stop's cost** (above): whether to batch the restores is the owner's to say.~~ **Decided 2026-11-13
|
||||
(D134): batch them, installs too** — a pull request of its own, measured on the harness, released alone as
|
||||
**0.1.0-beta.46**. The plan was reviewed against MinHook's source before it was approved: `MH_ApplyQueued`
|
||||
applies every entry whose queued state differs, not only the caller's, so the queue-to-apply sequence is
|
||||
serialised, only targets that are still ours are ever queued for a restore, and nothing is queued "for all".
|
||||
4. **`slAllocateResources` keeps its patch** (D135); looked at again with more sessions.
|
||||
5. **Train D** after train C, the same way: a spike first.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request, with what SonarCloud and Qodana said.~~ **Recorded
|
||||
2026-11-12: 0.1.0-beta.45 was released 2026-11-12T16:40:42Z** (23:40 in the owner's time zone) from the signed
|
||||
tag on `550d830` (#431), by run 43257803723 — green at the first attempt, one run for the one tag push. Eight
|
||||
assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed; the four shipped natives carry
|
||||
`FL_BUILD_ID v0.1.0-beta.45`. The delta from beta.44 is 1,762,465 bytes beside a full package of 110,767,499 —
|
||||
"Delta processed 0452 files. 0024 patched, 0428 unchanged". The wiki was published by run 43261335359. The
|
||||
rehearsal on the release branch (run 43253780609, at `f4e3fe2`, the released tree) had made a delta of 1,779,418
|
||||
bytes with the same file counts. **Qodana's two reports are green on `550d830`.** On the way Qodana's native
|
||||
report found two index products in the harness's probe (#427), fixed before that pull request merged; every
|
||||
later report was clean, and each was read before its merge. No required check failed on this train.
|
||||
**SonarCloud's quality gate failed on `550d830`, on one condition: duplicated lines on new code, 3.7 % where the
|
||||
gate allows 3 %.** No issue is open and coverage on new code is 98.6 %. The 39 lines are the six new members of
|
||||
`FlHookFamily` (`ShmLayout.cs`) and of its Domain mirror `HookFamilies` — two enums that are the same on purpose
|
||||
(Domain references nothing, and `MetricEnumMirrorTests` fails when they differ), which six members at once took
|
||||
over a threshold that two at a time had stayed under. The job is advisory and the release was already cut. The
|
||||
pull request that records this leaves the Domain's mirror out of duplication detection, with the reason in
|
||||
`SonarQube.Analysis.xml` and in `13_CI_CD` §SonarCloud; **whether the gate is green again is for the analysis of
|
||||
that commit on `main` to say**, and it is not in this text. *(It said so the same night: green on `d3e8dd3`,
|
||||
duplicated lines on new code 0.0 %, no issue open.)* One more thing the train showed: main's branch
|
||||
protection wants a pull request up to date, so of two that were green at once the second (#430) had to be
|
||||
rebased after the first merged, and ran its checks again.
|
||||
- ~~**No real game was run on this build.** Six new patch sites, tested with the harness and the stub; their cost
|
||||
measured on the headers.~~ **Seven sessions on six games, 2026-11-13** (§What the owner's seven sessions on
|
||||
beta.45 showed). The published release notes say the six calls "have not been run in a real game"; a released
|
||||
file is not edited.
|
||||
- **`slAllocateResources` has a patch no game has used**: not called after the attach in any of six sessions on
|
||||
five games. ~~Whether it stays is the owner's.~~ It stays for now (D135, 2026-11-13).
|
||||
- **Off means off (item 42 (f)) has never been exercised on a real game**; it is item 43 (f) now, for all ten.
|
||||
- **Valor Mortis's crash at 51 s** (twice, beta.40 and beta.44) **and Black Myth: Wukong's fault in Steam's crash
|
||||
handler at every exit** are not explained. One session of each with hooking off is the comparison that is missing.
|
||||
- **What item 41 left unexercised**: a configure through the FidelityFX 2.3 loader (Cyberpunk 2077 with FSR frame
|
||||
generation), a game with neither library.
|
||||
- **A fault while a game is closing is not seen by a hooked session** (D127: written down, not changed).
|
||||
- **`docs/LIST_GAME_TESTED.md` is as of 2026-11-06**: refreshing it is a new copy of the ledger and the owner's review.
|
||||
- **Item 40 (d)** was not exercised and the owner has not said item 40 passed. **Items 36 (d) and 37 are still open.**
|
||||
- **What an empty process snapshot does to the watcher's tick in a real session** was not looked into (seen once in
|
||||
a test on 2026-11-12).
|
||||
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
|
||||
sensors "have never been read on real hardware"** — the owner's to reword. The alpha line still rests (D98).
|
||||
|
||||
**Owner-only:** item 43; the three questions of `spike-notes` §30; one session each of Valor Mortis and Black
|
||||
Myth: Wukong with hooking off; what item 41 left unexercised; item 40 (d).
|
||||
@@ -1,247 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.46
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.47 was cut, 2026-11-14 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`. **Its §The train after 0.1.0-beta.46 says the release is held**: item 44 (d) was run on 2026-11-14 and 0.1.0-beta.47 was released that day; what it built and decided is HANDOFF.md's section for it.*
|
||||
|
||||
## **START HERE** — 2026-11-13, 0.1.0-beta.46: patches go in and come out under one stop of the game's threads; Reflex route D goes to a harness spike
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.46.md`; this is what no other file carries.* The owner ran seven sessions on
|
||||
beta.45 the day after it was released and said: check the logs and go on. They were read from a copy of the ledger
|
||||
and the logs (#433), and the same day the owner took four decisions on what they showed (D132–D135) and approved
|
||||
the plan. Two pull requests and this one: #433 (what the sessions showed; the decisions; rule 4's note in
|
||||
`CLAUDE.md`), #434 (the batches, D134). **What the seven sessions on beta.45 showed, session by session, is
|
||||
[`handoff/history/0.1.0-beta.45.md`](handoff/history/0.1.0-beta.45.md)**; what the batches are, what the queue
|
||||
makes dangerous and what was measured is [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Unhooking, *Batches*.
|
||||
|
||||
### What this release decided, beyond D132–D135
|
||||
|
||||
- **The first design was wrong, and reading MinHook's source before writing a line is what found it.** It marked
|
||||
every hook for disabling and then un-marked the ones it must not restore. `MH_ApplyQueued` applies every hook
|
||||
whose mark differs from its state; un-marking a hook that is already out marks it for *enabling*, and the stop's
|
||||
own apply would have put a patch back in after the stop — logged as "declined", with the status `UNHOOKED`. The
|
||||
rules that replaced it are in `fl_patch_registry.h`: no mark left standing, only a patch that is still ours
|
||||
marked for a restore, nothing marked "all", and mark–apply–commit inside a gate.
|
||||
- **The gate is the Overlay's one lock, and it is on no hook body's path.** A slim lock, exclusive, held for one
|
||||
apply, never across a symbol lookup (the loader's lock). The one way from a hook to it is the stop, which always
|
||||
waited for MinHook's own lock and a stop of the threads. Its owner re-enters it without waiting: a slim lock taken
|
||||
twice by one thread never returns.
|
||||
- **The verdict on an install is the engine's, not the bytes'.** Reading the target back after the apply would take
|
||||
a foreign overlay that patched over us in that instant for a failure, and mark a restore nobody had compared.
|
||||
- **An apply stops at its first failure and says only that one failed.** The hooks after it are enabled — in the
|
||||
stop, restored — one at a time, so one bad patch still costs one patch, and a stop still takes everything out.
|
||||
- **One stop of the threads costs what it cost for one patch**: 77–91 ms on the fixture for four, nine or eighteen.
|
||||
What it costs in a game with a few hundred threads is not known; the `PATCH_BATCH` line's `a=` is there to say.
|
||||
- **Init's three DXGI patches, the loader detour and OpenGL are as they were** — three already went in together,
|
||||
the other two are one each. Ray tracing's two are a batch of their own, apart from the upscaler rows', so that a
|
||||
batch's size in a test does not depend on which tick a D3D12 device appeared in.
|
||||
- **`fl_guard`'s timing assertion is on the restore only** (under a second for eighteen patches): the time from an
|
||||
Advanced request to its families includes the wait for the watchdog's tick, and batching changes the tick's
|
||||
phase, so that number went *up* in the test while the install itself went from 0.6 s to 0.08 s. The install is
|
||||
asserted by count — every lazily installed patch under a `PATCH_BATCH` line — not by time.
|
||||
- ~~**The spike of route D is still to be written**~~ **The spike of route D was run the same day** (`spike-notes`
|
||||
§31; `tools/fl-probe-reflex`, ctest `fl_reflex_probe_stub`): a decision table written before the runs, a stand-in
|
||||
`nvapi64.dll`, then the installed driver in the probe's own process. None of §30's stop conditions fired. Two
|
||||
things it decided that a plan must keep: **the call belongs on the presenting thread, once a second** — a call
|
||||
the driver holds stops the thread that made it, so not the watchdog, and at a microsecond or so it needs no thread
|
||||
of its own — and **the newest frames of a report are not final** (one run read a span of half an hour in the
|
||||
newest frame). Rule 4's note (D132) is in `CLAUDE.md`; nothing shipped calls a driver.
|
||||
|
||||
### Traps this train left
|
||||
|
||||
- **GPG's agent had restarted and the pinentry timed out three times in a row**; nothing could be committed until
|
||||
the owner unlocked the key (`echo test | gpg --clearsign` in the owner's own terminal). Say so and go on with
|
||||
what needs no commit — planning did not.
|
||||
- **A here-document still eats backslashes** (a `\n` inside a C++ string in an edit script): write the script to a
|
||||
file. It cost one failed edit again.
|
||||
- **A Catch2 `WARN` longer than the console's width wraps**, and a filter on its first words loses the number at
|
||||
its end: keep a measured line short.
|
||||
- **To measure the old build beside the new one**: `git stash push -- <the changed sources>`, build, run the one
|
||||
test case by name (its `INFO` log prints when a new assertion fails, which it does on the old build), `git stash
|
||||
pop`, build again.
|
||||
- **SonarCloud's gate was red on #434 before it merged, on three things it was right about**: a `LARGE_INTEGER`
|
||||
initialised with `{}` and read through `QuadPart` (cpp:S6232 - write `{.QuadPart = 0}`, as the rest of the file
|
||||
does since #336), a `strlen` in a test, and a test model indexed with what a lookup returned unchecked. Its job is
|
||||
advisory and auto-merge does not wait for it: the pull request was held until the fix was analysed.
|
||||
- **`docs/14_TESTING` and the changelog are where a non-per-present cost goes**; "measured overhead" in a pull
|
||||
request body means what the change can move — here the install and the stop, not a present.
|
||||
|
||||
### What the owner's five sessions on beta.46 showed (item 44, read 2026-11-13)
|
||||
|
||||
The owner updated at 20:29 (+07) the day of the release, ran five Streamline games with Advanced metrics on — one
|
||||
session each, four to nine minutes, sessions 198–202 — and said: check and go on. Read from a copy of the ledger
|
||||
and the logs, and from Windows' application log. None of the five is under the user-mode exception.
|
||||
|
||||
| Session | Game | Install batches in the log's order: `a=` in microseconds · patches | The interposer's patches on beta.45, first line to last |
|
||||
|---|---|---|---|
|
||||
| 198 | Hogwarts Legacy | **1 260 835 · 13** (Streamline) — 261 920 · 3 — 227 061 · 2 | 2.80 s, 0.19–0.31 s a patch |
|
||||
| 199 | Phantom Blade Zero | 81 417 · 3 — 92 512 · 6 — 88 455 · 13 (Streamline) — 99 253 · 2 | 0.74 s and 0.85 s |
|
||||
| 200 | Black Myth: Wukong | 187 931 · 12 (Streamline) — 157 010 · 3 — 109 025 · 2 | 1.65 s |
|
||||
| 201 | Cyberpunk 2077 | 93 168 · 16 (Streamline's thirteen and the FSR loader's three) — **608 700 · 3** — 177 970 · 3 — 120 878 · 2 | 1.18 s |
|
||||
| 202 | Clair Obscur: Expedition 33 | 168 527 · 3 — 165 405 · 16 (Streamline's thirteen and FSR frame generation's three) — 218 172 · 2 | no session on beta.45 |
|
||||
|
||||
- **The batches went in whole.** In every log the `HOOK_INSTALLED` lines above a `PATCH_BATCH install` carry one
|
||||
time to the thousandth of a second; there is no `PATCH_FAILED` and no `UNHOOK_DECLINED`; and the hooks are the
|
||||
ones beta.45 installed for the same game, compared name for name (four games; Clair Obscur had no log on beta.45).
|
||||
- **Sixteen of the eighteen batches cost 81–262 ms, whatever they held** — two patches or sixteen. That is what one
|
||||
patch cost in the same game on beta.45, as expected.
|
||||
- **Two did not, and neither is explained.** Hogwarts Legacy's thirteen took **1.26 s** — under half the 2.8 s they
|
||||
took one by one, and about five times what one stop cost in that game the same afternoon. Three of Cyberpunk
|
||||
2077's took **0.61 s**, which is what three patches cost there one by one. **The log cannot tell one long stop
|
||||
from an apply that failed part-way and was finished one patch at a time**: a batch writes a line only for a patch
|
||||
that fails for good (item 44's text said a fallback leaves a `PATCH_FAILED`; that was wrong). What speaks for one
|
||||
long stop: the queued apply fails only where a page's protection cannot be changed, and thirteen single stops in
|
||||
Hogwarts Legacy would have cost 2.5 s or more. *A reading, not a measurement*: a stop waits until every thread of
|
||||
the game has taken its suspension, and how long that takes follows what the game is doing at that instant — both
|
||||
happened while the game was loading — and not how many patches the stop covers.
|
||||
- **What that means for a ceiling on a batch** (item 44's own words for a second or more, written before the run):
|
||||
the eighteen batches say the cost does not follow the count — sixteen patches in 93 ms, three in 609 ms — so
|
||||
splitting a batch would add stops, not shorten one. What is missing is the line that says how a batch ended.
|
||||
- **Nothing else moved.** All five hooked, `normal`, no fault counted, no record dropped. Rates and factor beside
|
||||
each game's earlier sessions: Cyberpunk 2077 149 → 298 (×2.0) beside 164 → 327 and 137 → 275; Hogwarts Legacy
|
||||
61 → 245 (×4.0) beside 59 → 236; Black Myth: Wukong 78 → 315 (×4.0) beside 85 → 341; Phantom Blade Zero 87 → 261
|
||||
(×3.0) beside 81 → 244 at ×3.0 on beta.43; Clair Obscur 112 → 339 (×3.0) beside 106 → 323 on beta.44.
|
||||
- **The way out is as it was.** Hogwarts Legacy faults in `_nvngx.dll` at `0x6aa85` and Black Myth: Wukong in
|
||||
Steam's `crashhandler64.dll` at `0x39b49` — the module and the offset of every build read so far. The other
|
||||
three games leave nothing in Windows' application log.
|
||||
- **The Advanced rows are as on beta.45**, and Clair Obscur gave its first reading of the six calls (interposer
|
||||
2.7.30): `slIsFeatureSupported` and `slIsFeatureLoaded` read, among them a feature no session had named before,
|
||||
`kFeatureLatewarp` (Streamline's answer: `eErrorFeatureMissing`). `slAllocateResources` and `slShutdown` were
|
||||
called in none of the five (D135 stands). That game's `hook_crash_count` of 3 is old: it dates from 2026-10-20
|
||||
and is the same in the copy read for item 43.
|
||||
- **Not exercised: the stop.** Every session ended with its game exiting; no log has a `STOP` or a `PATCH_BATCH
|
||||
restore` line. **`RestoreAll` has still run in no real game** — item 44 (d). Nor (e), a game with no Streamline,
|
||||
nor (g), off means off: `telemetry.advanced` was on throughout. (c), how a game's start feels, is the owner's to
|
||||
say. (a) held: the terms window did not show.
|
||||
|
||||
### The train after 0.1.0-beta.46: Reflex route D in a game, and D137 (plan approved 2026-11-13)
|
||||
|
||||
*Nothing of this is in a release. The release pull request is not opened before the owner has run item 44 (d).*
|
||||
**Where it stands (2026-11-14):** all five are merged — #440 (PR-0), #441 (D137), #442 (the words), #443 (the
|
||||
Overlay), #444 (the Agent, the App, the legal texts, owner-only item 45); `main` is `cd4f69a`. What is left is the
|
||||
release, which waits for the owner: **item 44 (d) was tried on 2026-11-14 and not exercised** (the switch was on
|
||||
before the games started — item 44's last paragraph). **Not verified by any test: the whole path through the real Agent** —
|
||||
the injected tests stop at the shared memory, the sampler's tests start from it; no end-to-end case loads the
|
||||
stand-in module under an Agent session. The Japanese strings are new and unreviewed, as every `ja` string is.
|
||||
The owner approved the plan the evening item 44 was read. Its order: **PR-0** the decisions and the probe's leg
|
||||
with a sleep (done: `spike-notes` §31 — no stop condition) → **PR-1** D137 → **PR-2** the words in region 5, written
|
||||
by nobody → **PR-3** the Overlay, the gates, the fixtures → **PR-4** the Agent, the App, strings, documents, legal
|
||||
texts and owner-only item 45 → **the release, held**. What the plan's review against the source decided — a draft
|
||||
of mine was wrong in six places — and that no other file carries yet:
|
||||
|
||||
- **Resolve on the watchdog, once for the process; call on the presenting thread.** The watchdog asks Windows for
|
||||
an `nvapi64.dll` that is *already loaded* (never loads it), only while a session asks for Advanced metrics and a
|
||||
Direct3D 12 device is held; it keeps one reference and never releases it; it refuses a module in the executable's
|
||||
own folder (D140); it fetches `nvapi_QueryInterface` and the two ids under a guard and checks with `VirtualQuery`
|
||||
that both addresses lie inside ~~that module~~ an image the process has loaded. "No getter" and "refused" are
|
||||
final for the process; "no module" is asked again each second. **Found when the header was run against the
|
||||
installed driver: `nvapi64.dll` is a shim and the two getters are in `nvapi64_impl.dll`** (`spike-notes` §31,
|
||||
*What moving the sequence into the Overlay found*) — so the check accepts another loaded image, a reference is
|
||||
kept on that image as well, and the code that is called *is* a Control Flow Guard image (the plan's review had
|
||||
reasoned from the shim, which is not).
|
||||
- **One atomic gate with four states** — idle, armed, reading, off — not a busy flag beside accumulators (two
|
||||
presenting threads could read back to back, and the watchdog could drain half a read). The watchdog drains only
|
||||
when it sees *idle* and arms at most once a second by its own clock (the loader detour wakes it more often); a
|
||||
present does one relaxed load, takes *armed* to *reading*, reads into a static buffer (the report is 15.4 KB: never
|
||||
on a game thread's stack), and stores *idle* or *off*. A request that goes off takes *armed* back.
|
||||
- **After the record is published, and only for a swap chain whose device is the one held** (`g_d3d12Device` is the
|
||||
first device seen, not "this chain's": a flag in the chain's slot, set in `ResolveApi`).
|
||||
- **The latches, each until the game exits**: a fault in a getter (its own guard with `FlFilter`; counted once
|
||||
through `NoteFault`, so the session shows it and it cannot reach the three that self-disable); one call of 2 ms or
|
||||
more (D141); the watchdog finding *reading* on two ticks running — logged and flushed at once, published as
|
||||
stalled, and **nothing can stop a call that does not return**. An error status or an empty report is recorded and
|
||||
reading goes on.
|
||||
- **What D141 costs, measured once on a busy PC** (`spike-notes` §31, *A run on a busy PC*): the 2 ms latch will
|
||||
sometimes fire on a pause that was Windows' and not the driver's — a few sessions in a hundred at worst, by a
|
||||
reading of one run. The owner chose one call over two knowing it errs towards the game; item 45's outcomes must
|
||||
say how the two are told apart (the microseconds published with *slow*). **Asked again with this run in hand,
|
||||
the owner kept it: one call (2026-11-13). Do not re-ask.**
|
||||
- **The summary**: only frames newer than the last one summed; the two newest of a report skipped (§31: not final);
|
||||
a zero end point is "span not reported" (published as all ones), not a refused frame; a frame is refused for a
|
||||
span that runs backwards, one over a second, or no total; frame ids that go backwards restart the sequence.
|
||||
- **Layout 5 stays**: the ten reserved words of region 5's first line take it (`slShutdowns` is the precedent; the
|
||||
handshake compares the build id anyway, and a trial must be removable without a layout 7). The sleep interval is
|
||||
not stored. No new request word (D138). `FL_HOOK_REFLEX`, `FL_MEASURED_LATENCY` and `reflexLatencyUs` stay unset:
|
||||
there is no hook, and the numbers are a series beside the frames; `sessions.reflex_active` stays NULL.
|
||||
- **Managed side**: a new reach, `GameDriver`, not a relaxed test of `Game` (whose meaning is "the arguments of a
|
||||
call the Overlay hooks"); `nvapi.reflex.frame_report` as seven series, `nvapi.reflex.sleep_status` as a table of
|
||||
switches *seen on / seen off*; `nvapi.reflex.mode`, `sl.reflex.state` and `sl.pcl.markers` become *refused* with
|
||||
the reason; `InGameAdvancedSampler.Take` must read the latency state when the mask is zero and keep the new bit
|
||||
out of `SawAnything`.
|
||||
- **The gates**: `overlay-fields-check` learns the two NVAPI structs (`frameID` joins the shared members; `version`
|
||||
is written outside the header); `nvapi-readonly-check` gets a pass over the Overlay — no `NvAPI_*(` token, every
|
||||
id that equals one of `nvapi_interface.h`'s on a list of exactly two, `Sleep` a writer verb; `hookinventory-check`
|
||||
refuses an `nvapi` import. The injected tests prove nothing about Control Flow Guard (the harness does not enforce
|
||||
it): the probe includes the header that ships, so `fl_reflex_probe_stub` tests the shipped sequence under it.
|
||||
- **The legal texts change in PR-4** (Disclaimer 2.16, Privacy Policy 2.20, the accuracy statement): the part
|
||||
inside the game now *makes a call of its own*, once a second, on the game's presenting thread.
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**The owner runs item 44**~~ **Read 2026-11-13** (§What the owner's five sessions on beta.46 showed): the
|
||||
install half held in five games. **Still to run, the owner's: (d) a stop while a game runs** — *Disable all
|
||||
hooking* with a game being recorded — which is the half of beta.46 no real game has exercised; (e) a game with
|
||||
no Streamline; (g) off means off. Not first on a game under the user-mode exception's trial (D38).
|
||||
~~**Proposed, not done: `PATCH_BATCH` says how the batch ended**~~ **Decided the same evening (D137):
|
||||
`PATCH_BATCH` says how the batch ended** — under one apply, or finished one patch at a time, and how many — so
|
||||
that a long `a=` can be read. It goes with the next release, not in one of its own. **Written 2026-11-13**:
|
||||
`install` / `restore` for one apply, `install singly` / `restore singly` with the count in the high half of `b`
|
||||
(`17_HOOK_ENGINE` §Unhooking, *Batches*). It explains nothing about the two long batches already seen; it makes
|
||||
the next one readable.
|
||||
2. ~~**The spike of Reflex route D on `hook-harness`**~~ **Done 2026-11-13** (`spike-notes` §31): on the harness
|
||||
and against the installed driver the two getters are harmless, cost about a microsecond and return a readable
|
||||
report, and the Direct3D 12 device the Overlay holds is what the driver takes. **The owner's next word is go or no
|
||||
for one real title** — a go is a plan of its own before any code (where the numbers go, the Disclaimer's and the
|
||||
Privacy Policy's wording, `nvapi-readonly-check` over the Overlay). Routes C and E are closed (D133).
|
||||
**The owner said go on 2026-11-13 (D136): a plan first, for Cyberpunk 2077.** No code before the plan is
|
||||
approved, and no release that carries it before item 44 (d) — the stop while a game runs — has been run.
|
||||
**The plan was approved the same evening, with D138–D141** (§The train after 0.1.0-beta.46).
|
||||
3. **`slAllocateResources`** keeps its patch (D135); looked at again when there are more sessions.
|
||||
4. **Train D** after train C, the same way: a spike first — and §30 found its hook would miss a game that fetched
|
||||
its functions before the attach.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request, with what SonarCloud and Qodana said.~~ **Recorded
|
||||
2026-11-13: 0.1.0-beta.46 was released 2026-11-13T11:10:28Z** (18:10 in the owner's time zone) from the signed
|
||||
tag on `47f010a` (#435), by run 43412434074 — green at the first attempt, one run for the one tag push. Eight
|
||||
assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed; the four shipped natives carry
|
||||
`FL_BUILD_ID v0.1.0-beta.46`. The delta from beta.45 is 634,023 bytes beside a full package of 110,767,120 —
|
||||
"Delta processed 0452 files. 0021 patched, 0431 unchanged". The wiki was published by run 43414965433. The
|
||||
rehearsal on the release branch (run 43409330961, at `7b4ecd7`, the released tree) had made a delta of 668,012
|
||||
bytes with the same file counts. **SonarCloud answered on `47f010a`: the quality gate passed and no issue is open
|
||||
on `main`. Qodana's two reports are green on that commit.** On the way SonarCloud was red on #434 (six issues
|
||||
in the new code, fixed before it merged — §Traps), and no required check failed.
|
||||
- **A local gate once counted `fl_guard` as passed after 0.66 s** (2026-11-13 17:30, the spike's branch). The
|
||||
security software on the development PC was switched on for three minutes while the gate ran; the freshly linked
|
||||
`fl_guard_test.exe` was removed from the build tree, **ctest reported the run that was cut short as `Passed`**
|
||||
(the suite takes 181 s), and the gate went red only because the next test, `fl_prescan`, runs the same executable
|
||||
and could not find it. Run again with that software off, the gate was green. Nothing was changed for it: a test
|
||||
whose process ends early with a zero exit code is a pass to ctest, and the suite has no line it must print to
|
||||
count. ~~Worth a guard of its own (a `PASS_REGULAR_EXPRESSION` on Catch2's last line, or a minimum number of test
|
||||
cases); proposed, not done.~~ **Done the same evening, on the owner's word**: every native test names the line it
|
||||
ends on and ctest requires it; a test registered without one fails the configure; four canaries prove the rule
|
||||
red and green (`14_TESTING` §Native unit tests; `src/native/CMakeLists.txt`). Two things it turned up: four tests
|
||||
passed on a line they print in the middle of their run, and `fl_nvapi_probe` passed whatever it printed after its
|
||||
branch line — a pass expression makes ctest ignore the exit code.
|
||||
- ~~**No real game was run on this build.**~~ Five were, on 2026-11-13 (above): the order in which patches reach a
|
||||
game changed for every game, and the five took it. **The restore under one apply has run in no real game.**
|
||||
- **Two batches took 1.26 s and 0.61 s and nothing explains them** (Hogwarts Legacy, Cyberpunk 2077); the log has
|
||||
no line that tells a long stop from a batch finished one patch at a time.
|
||||
- **Off means off has never been exercised on a real game** (item 43 (f), now item 44 (g)); nor (c) and (h) of
|
||||
item 43, which only the owner sees.
|
||||
- **Valor Mortis's crash at 51 s** (twice, beta.40 and beta.44) **and Black Myth: Wukong's fault in Steam's crash
|
||||
handler at every exit** are not explained. One session of each with hooking off is the comparison that is missing.
|
||||
- **What item 41 left unexercised**: a configure through the FidelityFX 2.3 loader (Cyberpunk 2077 with FSR frame
|
||||
generation), a game with neither library.
|
||||
- **A fault while a game is closing is not seen by a hooked session** (D127: written down, not changed).
|
||||
- **For the inline patches the comparison has never been re-made under the write window** (`17_HOOK_ENGINE`
|
||||
§Compare-and-restore says so now): MinHook owns that window.
|
||||
- **`docs/LIST_GAME_TESTED.md` is as of 2026-11-06**: refreshing it is a new copy of the ledger and the owner's review.
|
||||
- **Item 40 (d)** was not exercised and the owner has not said item 40 passed. **Items 36 (d) and 37 are still open.**
|
||||
- **What an empty process snapshot does to the watcher's tick in a real session** was not looked into (seen once in
|
||||
a test on 2026-11-12).
|
||||
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
|
||||
sensors "have never been read on real hardware"** — the owner's to reword. The alpha line still rests (D98).
|
||||
|
||||
**Owner-only:** item 44 (d), (e), (g) and what (c) felt like — **(d) is what the next release waits for**; item 45 once that release exists; the go or no on `spike-notes` §31 (one real title); one session each of Valor Mortis and
|
||||
Black Myth: Wukong with hooking off; what item 41 left unexercised; item 40 (d).
|
||||
@@ -1,146 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.47
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.48 was cut, 2026-11-14 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`. **Its NEXT and its "Left open" were written through the morning of 2026-11-14 as the owner's sessions were read**: what they led to is HANDOFF.md's section for 0.1.0-beta.48.*
|
||||
|
||||
## **START HERE** — 2026-11-14, 0.1.0-beta.47: the part inside a game asks NVIDIA's driver for its latency report; the batch log says how a batch ended
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.47.md`; this is what no other file carries.* The owner ran five sessions on
|
||||
beta.46 the evening it was released and said: check and go on. They were read (#439), the owner took six decisions
|
||||
(D136–D141) and approved the plan of the train the same evening, and the five pull requests of it were merged
|
||||
overnight: #440 (the decisions; the probe's leg with a sleep mode), #441 (D137), #442 (the latency words of region
|
||||
5), #443 (the Overlay makes the read; the gates; the fixtures), #444 (the Agent, the App, the legal texts,
|
||||
owner-only item 45). The release was held for item 44 (d), which the owner ran on 2026-11-14 (#445, and below).
|
||||
**What the five sessions showed, the design of the train as the plan's review left it, and the traps of beta.46
|
||||
are [`handoff/history/0.1.0-beta.46.md`](handoff/history/0.1.0-beta.46.md)**; what the read is and what bounds it
|
||||
is [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Calls the Overlay makes into a driver; what was measured is
|
||||
[`spike-notes/31-reflex-route-d-harness.md`](spike-notes/31-reflex-route-d-harness.md).
|
||||
|
||||
### What this release decided, beyond D136–D141
|
||||
|
||||
- **It is the first thing the Overlay does in a game that is not reading a hooked call's arguments**, and it is
|
||||
listed as that — its own table in `17_HOOK_ENGINE`, its own reach in the catalog (`GameDriver`, not a stretched
|
||||
`Game`), its own paragraph in the Disclaimer. A second call of this kind needs a ruling of the same kind (D132).
|
||||
- **Resolve on the watchdog, once for the process; call on the presenting thread, after the record is published,
|
||||
behind one gate of four states** — idle, armed, reading, off. The plan's first draft had a busy flag beside
|
||||
accumulators: two presenting threads could have read back to back, and the watchdog could have published half a
|
||||
read. The whole design as reviewed is in the history file, §The train after 0.1.0-beta.46.
|
||||
- **`nvapi64.dll` is a shim.** The check that the two addresses lie inside the module it asked refused the real
|
||||
driver: the getters are in `nvapi64_impl.dll`, in the driver's store. An address is accepted when it is executable
|
||||
code of a loaded image, and a reference is kept on that image too. Only the run against the installed driver
|
||||
could find it — the stand-in answers with addresses of its own.
|
||||
- **The code that is called is a Control Flow Guard image**; the plan's review had reasoned from the shim, which is
|
||||
not. The probe enforces CFG and makes the calls from the header that ships, so this driver's getters are valid
|
||||
targets. A CFG-enforcing game on another driver is not covered, and a refusal there is a fast-fail.
|
||||
- **The layout stayed 5**: ten reserved words of region 5 took the read. `FL_HOOK_REFLEX`, `FL_MEASURED_LATENCY`
|
||||
and `reflexLatencyUs` stay unset — there is no hook, and the numbers are series beside the frames.
|
||||
- **D141 was asked twice.** A run on a busy PC showed the 2 ms latch can fire on a pause that was Windows'; the
|
||||
owner kept one call. Do not re-ask without a real game's numbers.
|
||||
- **What the game asked of Reflex, and Reflex through Streamline, are `RefusedRoute`** — a patch at a run-time
|
||||
address, and a call the vendor forbids from another thread (D133). `sl.pcl.markers` waits for train D's spike.
|
||||
|
||||
### What item 44's last part showed (2026-11-14)
|
||||
|
||||
- **A first try did not exercise it** (sessions 203–205, #445): *Disable all hooking* was on before the games were
|
||||
started, so two sessions were `RefusedKillSwitch` with nothing injected, and the hooked one ran to its exit.
|
||||
- **The second try did, twice, in Phantom Blade Zero** (sessions 206 and 207): the game started with the switch
|
||||
off, was recorded for a minute and a half, and the switch was turned on while it ran. Each log has `STOP` at the
|
||||
next safety scan, **an `UNHOOK_RESTORED` line for every one of the twenty-nine patches, all at one time**, one
|
||||
`PATCH_BATCH restore` — **83 309 µs and 85 578 µs for twenty-nine** — and `STOP_FLUSHED … a=1`. Nothing was
|
||||
declined. Both sessions ended `KillSwitchEngaged`, tier 1, no fault, no record dropped, writer status
|
||||
*unhooked*; the game ran on for three and four minutes and closed with nothing in Windows' application log.
|
||||
Restoring twenty-nine one by one would have cost about 2.4 s at this game's 84 ms a stop.
|
||||
- **Not said by the logs**: whether the owner felt a hitch at the stop. Not exercised: (e) a game with no
|
||||
Streamline and (g) off means off — both are parts of item 45 now.
|
||||
|
||||
### Traps this train left
|
||||
|
||||
- **A bash here-document ate backslashes again** and wrote a NUL byte into a `.cpp`. Edit scripts are files.
|
||||
- **A file made by the Write tool is LF**; `dotnet format --verify-no-changes` fails a new `.cs` for it. Convert.
|
||||
- **`NvAPI_Status(__cdecl*)(…)` is a call by name to `nvapi-readonly-check`**: the status type has an alias in
|
||||
`fl_reflex.h`. And a member of the Overlay's own named like a vendor's (`fgMultiplier`) fails
|
||||
`overlay-fields-check` outside the header.
|
||||
- **A copy of the harness in `%TEMP%` leaves an overlay log the run's sweep does not own** (it matches this
|
||||
build's harness by path): the test that makes the copy sweeps it.
|
||||
- **Stacked pull requests, with a dirty tree**: once the lower one is squash-merged GitHub retargets the next to
|
||||
`main`; `gh pr update-branch` works while the upper branch only adds, and conflicts once it edited lines the
|
||||
lower one added — then `git rebase -S --onto origin/main <lower tip> <branch>` and a forced push with lease.
|
||||
- **Advisory checks found real things after the local gate was green**: SonarCloud a `wcslen`, Qodana's native
|
||||
report a `switch` that did not name two enumerators, its managed report two redundant qualifiers and a
|
||||
redundant `!`. Hold a merge until both have reported.
|
||||
- **The probe's numbers depend on what else the PC does**: a run beside a build read 3.4 µs where three alone read
|
||||
2.6, and saw reads of 2 ms. Say which kind a number is.
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**The owner runs item 45**~~ **Run on 2026-11-14 in Phantom Blade Zero, three sessions: the read works in a
|
||||
real game** (item 45's last paragraphs) — the driver was found, read every second, and no call took more than
|
||||
45 µs. **Cyberpunk 2077 followed the same morning, twice, and three games the read must leave alone** (sessions
|
||||
211–215): read, 65 µs at the slowest, and *not read* where it should be. **Still to run of it**: Reflex off in
|
||||
a game's menu, off means off; and the owner's word on whether the games felt different.
|
||||
2. **The owner answered on the *GPU render* line (2026-11-14): read the driver's active time.** Two more members
|
||||
of the report FrameLedger already fetches — no further call into the driver. ~~**Plan first**~~ **Planned and
|
||||
approved the same day as the train of 0.1.0-beta.48 (D142–D147)**: the native half first, then the Agent, the
|
||||
App and the texts, then the sampling period, then the release and owner-only item 46 — one batch of tests for
|
||||
the owner, with what is left of item 45 in it. What the plan gathered: the multiplier row that keeps only the last value, the pages that still say no real game
|
||||
was read, the Agent's 1.32 s between samples beside `hz` 1.0. The owner tests what is left once, on that
|
||||
release. Still the owner's to say: more titles; the session summary's latency fields; D141 (the slowest call
|
||||
seen in a game is 65 µs, thirty times under it).
|
||||
3. **`slAllocateResources`** keeps its patch (D135); looked at again when there are more sessions.
|
||||
4. **Train D** after train C, the same way: a spike first — `sl.pcl.markers` waits for it, and §30 found its hook
|
||||
would miss a game that fetched its functions before the attach.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request, with what SonarCloud and Qodana said.~~ **Recorded
|
||||
2026-11-14: 0.1.0-beta.47 was released 2026-11-14T01:11:19Z** (08:11 in the owner's time zone) from the signed
|
||||
tag on `3d7c273` (#446), by run 43537436561 — green at the first attempt, one run for the one tag push. Eight
|
||||
assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed; the four shipped natives carry
|
||||
`FL_BUILD_ID v0.1.0-beta.47`. The delta from beta.46 is 1 820 144 bytes beside a full package of 110 795 507 —
|
||||
"Delta processed 0452 files. 0024 patched, 0428 unchanged". The wiki was published by run 43539059710. The
|
||||
rehearsal on the release branch (run 43534606602, at `43426fe`, the released tree) had made a delta of 1 838 295
|
||||
bytes with the same file counts. **SonarCloud answered on `3d7c273`: the quality gate passed and no issue is open
|
||||
on `main`. Qodana's two reports, CodeQL and `check` are green on that commit.** On the way the advisory checks
|
||||
found three things after local gates were green (§Traps), and no required check failed.
|
||||
- **The release branch's local gate was red once, for a reason outside the code** (2026-11-14 07:20): the freshly
|
||||
linked `fl_guard_test.exe` was gone from the build tree seconds after the gate began — Windows Defender's log has
|
||||
three configuration changes at 07:20:53–56 and no detection; which security program removed the file is not
|
||||
known, and nothing of its settings was looked at further or touched. `fl_guard` ended after 0.72 s **and was
|
||||
counted as failed, not passed**: the rule of #438 (a native test names the line it ends on) did what it was
|
||||
written for. Run again, the gate was green.
|
||||
- ~~**No real game has run the read.**~~ Two have (Phantom Blade Zero and Cyberpunk 2077, 2026-11-14). **The accuracy
|
||||
statement, `LIMITATIONS.md` and the guide still say no real game had been read**: true when written, to be
|
||||
brought up to date with the next release, as beta.46's pages were.
|
||||
- **In Phantom Blade Zero the driver's *GPU render* span is longer than its total** (item 45): shown as reported,
|
||||
not explained. In Cyberpunk 2077 it is not. The owner's answer: read the driver's active time (NEXT 2).
|
||||
- ~~**The Agent's samples are 1.32 s apart while `sensor_blobs.hz` says 1.0**~~ (seen 2026-11-14 in the `t_ms`
|
||||
series). **Looked into the same day (D146)**: the poller waited its whole interval after a poll's work; only
|
||||
the App's series loader reads `hz`, and only where a row has no `t_ms`, so no chart was wrong. The poller now
|
||||
keeps a fixed period and `hz` is measured from the samples (`06_DATA_MODEL` §sensor_blobs) — in no release yet.
|
||||
- **Where the third of a second goes is not established.** Unelevated, a poll takes about a millisecond (the
|
||||
layers composed as the Agent composes them, each read under a stopwatch). In the owner's ledger 180 of 186
|
||||
sessions are 1.32 s apart and six are 1.0 s: the two with no `cpu_temp` series (an Agent not elevated) are among
|
||||
the six — which points at the sensor library's processor update, run on the poll's thread as administrator
|
||||
with PawnIO — **but four sessions that have the series kept one second** (22, 72, 73, 136). **Not measured**:
|
||||
that call itself (it needs elevation), and whether it is processor time or waiting. Not changed; the period no
|
||||
longer depends on it. The owner's to say whether it is worth timing on their PC and moving off the poll's thread.
|
||||
- **No test runs the whole path through the real Agent**: the injected tests stop at the shared memory and the
|
||||
sampler's start from it; no end-to-end case loads the stand-in module under an Agent session.
|
||||
- **Two install batches of beta.46 took 0.61 s and 1.26 s and nothing explains them** (Hogwarts Legacy, Cyberpunk
|
||||
2077). Since this release the log says whether a batch went singly; the next long one can be read.
|
||||
- **The Japanese strings are new and unreviewed**, as every `ja` string is.
|
||||
- **Off means off has never been exercised on a real game** (item 43 (f), item 44 (g), now item 45 (g)); nor (c)
|
||||
and (h) of item 43, which only the owner sees.
|
||||
- **Valor Mortis's crash at 51 s** (twice, beta.40 and beta.44) **and Black Myth: Wukong's fault in Steam's crash
|
||||
handler at every exit** are not explained. One session of each with hooking off is the comparison that is missing.
|
||||
- **What item 41 left unexercised**: a configure through the FidelityFX 2.3 loader (Cyberpunk 2077 with FSR frame
|
||||
generation), a game with neither library.
|
||||
- **A fault while a game is closing is not seen by a hooked session** (D127: written down, not changed).
|
||||
- **`docs/LIST_GAME_TESTED.md` is as of 2026-11-06**: refreshing it is a new copy of the ledger and the owner's review.
|
||||
- **Item 40 (d)** was not exercised and the owner has not said item 40 passed. **Items 36 (d) and 37 are still open.**
|
||||
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
|
||||
sensors "have never been read on real hardware"** — the owner's to reword. The alpha line still rests (D98).
|
||||
|
||||
**Owner-only:** what is left of item 45 (Reflex off in a game's menu; off means off; how it felt); one session
|
||||
each of Valor Mortis and Black Myth: Wukong with hooking off; what item 41 left unexercised;
|
||||
item 40 (d).
|
||||
@@ -1,115 +0,0 @@
|
||||
# HANDOFF history — 0.1.0-beta.48
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.49 was cut, 2026-11-14 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then, and a path it writes is relative to `docs/`. **Its NEXT and its "Left open" were written through the afternoon of 2026-11-14 as item 46 was read**: what they led to is HANDOFF.md's section for 0.1.0-beta.49.*
|
||||
|
||||
## **START HERE** — 2026-11-14, 0.1.0-beta.48: two real games read; the driver's own GPU times beside a span that includes idle; every multiplier seen; samples a second apart
|
||||
|
||||
*Status is `docs/changelog/0.1.0-beta.48.md`; this is what no other file carries.* The owner ran eight sessions on
|
||||
beta.47 the morning it was released and said, twice: check. They were read (#448, #449): Phantom Blade Zero three
|
||||
times, Cyberpunk 2077 twice, two Direct3D 11 games and a Direct3D 12 game with no NVIDIA library — **the read
|
||||
works in real games**, and four things came out of it that the owner ruled on the same morning (D142–D147) and
|
||||
approved as one train: #450 (the Overlay reads two more members of the report and keeps the multipliers seen),
|
||||
#451 (the Agent, the App, the texts — Privacy Policy 2.21, Disclaimer 2.17), #452 (the poller's period), and this
|
||||
release. **What the eight sessions showed is item 45's last paragraphs, below; beta.47's own section, its traps
|
||||
and its release facts are [`handoff/history/0.1.0-beta.47.md`](handoff/history/0.1.0-beta.47.md)**; what the
|
||||
read is and what bounds it is [`17_HOOK_ENGINE.md`](17_HOOK_ENGINE.md) §Calls the Overlay makes into a driver.
|
||||
|
||||
### What this release decided, beyond D142–D147
|
||||
|
||||
- **Two more members of a report already fetched are not a new call.** Rule 4's note stands as written: the same
|
||||
two getters, the Overlay's own buffer, the two names on `tools/overlay-allowed-fields.txt`. The owner ruled on
|
||||
them by name (D142); a third member is asked the same way.
|
||||
- **The driver's own times have a count each, and zero means not given.** An older driver leaves both zero, and
|
||||
so did the probe's frames. They are added after the frame is accepted, so which frames the seven spans are made
|
||||
of did not move — a session's old series mean what they meant.
|
||||
- **An entry of their own in the catalog** (`nvapi.reflex.gpu_times`), not an eighth and ninth line of the frame
|
||||
report: `AdvancedPresenter.MaxLines` is 8, and nine series of one entry are drawn as a band.
|
||||
- **The layout stayed 5 again**: line 0 of region 5 was full, so the four words came out of the seven reserved
|
||||
words that ended the `sl::DLSSOptions` line. Three remain there, two on the `sl::Constants` line, two on the
|
||||
FidelityFX line.
|
||||
- **The fact's key no longer holds the last multiplier.** It held it since beta.47, so every menu rewrote the
|
||||
session's context.
|
||||
- **`hz` is measured from the samples, not taken from the setting**: the finalizer cannot see the setting, and a
|
||||
session recovered from a `.partial` file never knew it.
|
||||
- **The plan named `tools/agent-cost` for the poller's change and it was not run**: it runs the Agent unelevated,
|
||||
where a poll takes a millisecond and the period was already a second. Said in #452 rather than run for show.
|
||||
|
||||
### Traps this train left
|
||||
|
||||
- **A cause I wrote down before checking it.** "The third of a second is the processor's temperature" went into
|
||||
five files on two facts — unelevated a poll takes a millisecond; the sessions without a `cpu_temp` series are a
|
||||
second apart — and then four sessions *with* the series turned out to be a second apart too. The texts were
|
||||
taken back to what is established before the commit. **Count the exceptions before naming a cause.**
|
||||
- **A bash here-document ate a backslash again** (a Python one-liner with `'\\'`). Edit scripts are files — the
|
||||
rule already existed.
|
||||
- **`FETCH_HEAD` belongs to the worktree that fetched.** A merge in a second worktree needs the commit's id.
|
||||
- **A squash-merge of the lower pull request conflicts the upper one in `CHANGELOG.md` every time** both added to
|
||||
`[Unreleased]`. With Auto-fix on, the app asks for a merge of `main`, not a rebase: do it in a worktree of its
|
||||
own when a gate is running in the main one, keep the upper branch's file (it is the superset), and check that
|
||||
the merged tree equals the branch's tip — then the gate already run still stands.
|
||||
- **The gate script's last lines do not reach a background task's output**: read the log's last line and hash the
|
||||
`rules` folder by hand.
|
||||
- **An analyzer wants a `<summary>` once any `<param>` is written** (RCS1139).
|
||||
|
||||
### NEXT
|
||||
|
||||
1. ~~**The owner runs item 46**~~ **Run and read 2026-11-14** (the item, below): the samples are a second apart,
|
||||
both games gave both figures, the multipliers are listed, off means off. **The owner's word, the same day: no
|
||||
hitch.** What is left of it is whether session 221 was the one with Reflex off.
|
||||
2. **Then the owner's to say**: more titles; D141 on a larger sample (the slowest call seen in a game is 65 µs);
|
||||
whether the processor update is worth timing on their PC and moving off the poll's thread (below).
|
||||
3. **`slAllocateResources`** keeps its patch (D135); looked at again when there are more sessions.
|
||||
4. **Train D** after it, the same way: a spike first — `sl.pcl.markers` waits for it, and §30 found its hook
|
||||
would miss a game that fetched its functions before the attach.
|
||||
|
||||
### Left open by this session
|
||||
|
||||
- ~~**This release's own facts** — the tag's run, the digests, the delta — are not in any file yet: the release is cut
|
||||
after this text. Record them in the next pull request, with what SonarCloud and Qodana said.~~ **Recorded
|
||||
2026-11-14: 0.1.0-beta.48 was released 2026-11-14T04:49:19Z** (11:49 in the owner's time zone) from the signed
|
||||
tag on `aec1736` (#453), by run 43556901499 — green at the first attempt, one run for the one tag push. Eight
|
||||
assets; the seven digests of `SHA256SUMS.txt` equal the ones GitHub computed, and the portable package hashed
|
||||
here equals its line; the five native libraries in it carry `FL_BUILD_ID v0.1.0-beta.48`, none of them
|
||||
`-dirty`. The delta from beta.47 is 1 944 037 bytes beside a full package of 110 800 248 — "Delta processed
|
||||
0452 files. 0024 patched, 0428 unchanged". The wiki was published by run 43558546949. The rehearsal on the
|
||||
release branch (run 43555020289, at `0c210d0`, the released tree) had made a delta of 1 966 174 bytes with the
|
||||
same file counts. **SonarCloud answered on `aec1736`: the quality gate passed and no issue is open on `main`. Qodana's two reports, CodeQL and `check` are green on that
|
||||
commit**, as they were on each of #450–#453 before its merge; no advisory check found anything in this train.
|
||||
- ~~**No real game has given the two new figures yet.**~~ **Two have (item 46, 2026-11-14)**, in every frame
|
||||
report: Phantom Blade Zero's active render is the short number the reading expected (9.6 ms inside a span of
|
||||
16.4 ms at 60 FPS). **In Cyberpunk 2077 without frame generation active render is longer than the span between
|
||||
the two GPU marks** (3.17 against 2.79 ms) **and why is not established** — the two averages are over different
|
||||
frames, or the driver counts work outside the marks. The label says *idle time included*, which that game's
|
||||
numbers do not show; the texts say the figures are the driver's own. Not changed.
|
||||
- **After a session's first report, 0.4–7.3 % of its samples carry none** (item 46): the Overlay's reads are a
|
||||
second apart or two — its watchdog's tick — and the Agent's samples exactly one. Read in the code, not measured;
|
||||
not changed.
|
||||
- **Where the third of a second of a poll goes is not established.** Unelevated, a poll takes about a millisecond
|
||||
(the layers composed as the Agent composes them, each read under a stopwatch). In the owner's ledger 180 of 186
|
||||
sessions are 1.32 s apart and six are 1.0 s: the two with no `cpu_temp` series (an Agent not elevated) are among
|
||||
the six — which points at the sensor library's processor update, run on the poll's thread as administrator
|
||||
with PawnIO — **but four sessions that have the series kept one second** (22, 72, 73, 136). **Not measured**:
|
||||
that call itself (it needs elevation), and whether it is processor time or waiting. The period no longer
|
||||
depends on it; a poll that takes a third of every second is still a poll that takes a third of every second.
|
||||
- **With the sensor interval above one second, some readings of the driver's report are not stored**: the newest
|
||||
stands until a sample carries it (`SessionRecorder`). Said in the guide; not changed.
|
||||
- **No test runs the whole path through the real Agent**: the injected tests stop at the shared memory and the
|
||||
sampler's start from it; no end-to-end case loads the stand-in module under an Agent session.
|
||||
- **Two install batches of beta.46 took 0.61 s and 1.26 s and nothing explains them.** Cyberpunk 2077's eight
|
||||
batches on beta.47 took 85–221 ms, each in one apply; Hogwarts Legacy has not been run since.
|
||||
- **The Japanese strings are new and unreviewed**, as every `ja` string is.
|
||||
- ~~**Off means off has never been exercised on a real game**~~ **It was, 2026-11-14** (item 46 (e), session
|
||||
226: no `LATENCY` line, none of the hooks Advanced metrics adds, no row). (c) and (h) of item 43, which only the
|
||||
owner sees, are still not.
|
||||
- **Valor Mortis's crash at 51 s** (twice, beta.40 and beta.44) **and Black Myth: Wukong's fault in Steam's crash
|
||||
handler at every exit** are not explained. One session of each with hooking off is the comparison that is missing.
|
||||
- **What item 41 left unexercised**: a configure through the FidelityFX 2.3 loader (Cyberpunk 2077 with FSR frame
|
||||
generation), a game with neither library.
|
||||
- **A fault while a game is closing is not seen by a hooked session** (D127: written down, not changed).
|
||||
- **`docs/LIST_GAME_TESTED.md` is as of 2026-11-06**: refreshing it is a new copy of the ledger and the owner's review.
|
||||
- **Item 40 (d)** was not exercised and the owner has not said item 40 passed. **Items 36 (d) and 37 are still open.**
|
||||
- **`LIMITATIONS.md` and the accuracy statement still say the processor's, the memory's and the motherboard's
|
||||
sensors "have never been read on real hardware"** — the owner's to reword. The alpha line still rests (D98).
|
||||
|
||||
**Owner-only:** one session each of Valor Mortis and Black Myth: Wukong with hooking off; what item 41 left
|
||||
unexercised; item 40 (d).
|
||||
@@ -1,6 +1,6 @@
|
||||
# Owner-only items that passed
|
||||
|
||||
*Moved verbatim from `docs/HANDOFF.md` §Owner-only on 2026-10-19 (beta.24, owner decision D66): the items the owner reported passed or took, numbers kept — a number is never reused. The open ones stay in `docs/HANDOFF.md`. Items that passed later are added below as they pass (38 and 39 on 2026-11-12).*
|
||||
*Moved verbatim from `docs/HANDOFF.md` §Owner-only on 2026-10-19 (beta.24, owner decision D66): the items the owner reported passed or took, numbers kept — a number is never reused. The open ones stay in `docs/HANDOFF.md`.*
|
||||
|
||||
3. ~~**Which titles** go in `blockedExecutables` — a product decision with false-refusal
|
||||
consequences. The list ships empty until it is taken.~~ **Taken 2026-09-25 (D30):** per-title
|
||||
@@ -66,40 +66,4 @@
|
||||
page and choose its longest session, switch the page's tabs; visit the Dashboard a few times, then end a session —
|
||||
one "Session saved". (e) The Privacy Policy 2.11 is shown once after the update. (f) The `ja` strings marked
|
||||
`review`.
|
||||
38. ~~**beta.40, Advanced metrics inside a real game**~~ **Passed 2026-11-12** — the owner ran it on ten games over one night (beta.40, then beta.41), was shown what a copy of the ledger and the Agent's log said of those sessions, and answered: "Bạn có thể đánh dấu là pass và tiếp tục." What the sessions covered: (b) the option off storing nothing, on a DLSS title and on an FSR 3.1 one; (c) three titles upscaling through FSR 3.1 — Kingdom Come: Deliverance II (chosen in the game), Dying Light: The Beast and Clair Obscur: Expedition 33, the last two with **FSR upscaling beside DLSS frame generation, which is how the owner had set them in the game** — and Lies of P through FSR 3; (d) every DLSS title saying *the game made none of the calls*, none chaining its options into the evaluation; (e) the sentence under the session in each of its three forms; (g) Girls' Frontline 2 under the user-mode exception. **Not exercised, and passed on the owner's word**: (f) two sessions of one game that kept running; (h) the cost; (i) the words. **(j) is not done**: the SonarCloud acceptance is still the owner's to click, and stands in HANDOFF §Left open. Valor Mortis's one crash was the game's own (a shader-compilation error, its own crash dialog — the owner). *(The item as written:)* (D111–D116; train B's first release — beta.41 is not begun
|
||||
until this passes). (a) **The update from beta.39**: the terms window shows the **Privacy Policy 2.16** once, and
|
||||
not the Disclaimer; a game that was **running across the update** is refused until it is restarted, with the
|
||||
reason, and measured normally after. (b) **The option off, a hooked game that uses DLSS or FSR**: the game runs
|
||||
and is measured as in beta.39; the session is not on the Advanced page's list; nothing in the Agent's or the
|
||||
Overlay's log mentions the upscaler's options. (c) **The option on, a title that upscales through FSR 3.1 or
|
||||
later** (AMD's `amd_fidelityfx_*.dll` in its folder; a title on the older FSR 3.0 interface, such as one that
|
||||
ships `ffx_fsr3_x64.dll` alone, is expected to show none): on *Session*, under Upscaling, sharpening on or off
|
||||
and its strength against the game's own setting; the field of view as a range, against the game's slider (it is
|
||||
the **vertical** angle, in radians with degrees beside it) — and wider after zooming or aiming; the near and far
|
||||
planes; the flags; the chart of the frame time the game reported beside the session's own frame time; FSR's
|
||||
memory only if the game asks for it. (d) **The option on, a DLSS title**: most are expected to say *the game made
|
||||
none of the calls these are read from*. If one shows rows, this is the first sight of them anywhere: the output
|
||||
size against the display resolution, the preset letters against the NVIDIA app's override or the DLSS
|
||||
indicator, HDR input against the game's HDR setting. Write down which title did. (e) **The sentence under the
|
||||
session** says which of the three it was, and the session's summary still names the upscaler and its quality as
|
||||
before. (f) **Two sessions of one game that kept running**, both with the option on: the second one's field-of-
|
||||
view range and counts are its own, not the first one's carried over. (g) **A game under the user-mode anti-cheat
|
||||
exception**, the option on: it runs, the session is hooked, and its trial is not ended by anything new. (h) **What
|
||||
it costs**: the game's own frame rate with the option on and off, and the Agent's processor time in a hooked
|
||||
session (NFR-2: 2.5 % of one core). (i) **The words**: the fourteen new `vi` strings and the Settings text; the
|
||||
`ja` ones are marked `review`. (j) **SonarCloud**: accept `csharpsquid:S3869` on
|
||||
`src/FrameLedger.Infrastructure/Diagnostics/ParentDump.cs` again — the same call the acceptance of beta.24 covers,
|
||||
raised anew because #398 moved it (`13_CI_CD` §SonarCloud says why it is safe); until then `main`'s reliability
|
||||
rating on new code shows E for that one line.
|
||||
39. ~~**beta.41, the sensor library on the PC that showed the fault**~~ **Passed 2026-11-12** — the same answer. Seven sessions on beta.41 as administrator with PawnIO, no `advanced:` line in the Agent's log, 212 or 213 series in each session with the option on; on beta.40 the same morning the processor device faulted out after each of six sessions. **Not exercised**: (c) the page after a session was not looked at by anyone but the owner; (d) the unelevated run; (e) no value beside HWiNFO — that stays item 37 (e). The rarer fault, the reader failing to open, was one session in sixteen; `20_OPEN_QUESTIONS` §M13 keeps the count. *(The item as written:)* (D118; `20_OPEN_QUESTIONS` §M13). (a) **The
|
||||
update from beta.40**: no terms window, the ledger opens as before; a game running across the update is refused
|
||||
until restarted, as after every update. (b) **As administrator with PawnIO, Advanced metrics on**: five or more
|
||||
sessions of different games, some with the Advanced page left open on *This PC* throughout, some with it closed,
|
||||
one started within a few seconds of another ending. **Afterwards the Agent's log (Logs page, or
|
||||
`agent-<date>.log`) holds no `advanced: a device is left alone` and no `advanced: the sensor library did not
|
||||
open`**, and every one of those sessions has its processor, memory and motherboard readings on *Session* (about
|
||||
two hundred series; a session with seventeen is the fault). (c) **The page after a session ends**: the
|
||||
processor's rows on *This PC* are still there and still moving, without reopening the page. (d) **Not as
|
||||
administrator**: nothing differs from beta.40 — the card's sensors and the driver's figures, and *Sources* says
|
||||
why the rest is not read. (e) While there, the part of item 37 (e) nobody has done: a few of the processor's and
|
||||
the motherboard's values beside HWiNFO.
|
||||
|
||||
@@ -63,120 +63,6 @@ are kept because they record what each version changed and why (owner decision D
|
||||
>
|
||||
> Version 2.5 (2026-09-27, 0.1.0-beta.10) adds how a tracked game's window is shown — read from Windows — and the engine build name read from an Unreal Engine game's executable. It is also the first version to say two things the software already did: it reads the **content** of a library game's executable (markers in its first 8 MB and its import table, since the detection of engines and features; and, when a session starts, the graphics-library markers in the whole file), and it reads the processor load and the memory in use (since 0.1.0-beta.3). Nothing here leaves your device, as before.
|
||||
|
||||
### What version 2.21 of the Privacy Policy and 2.17 of the Disclaimer changed (0.1.0-beta.48)
|
||||
|
||||
**Two real games had been read, and the texts still said none** (owner decisions D142–D145; the wording's main
|
||||
points approved with the plan of 2026-11-14). The accuracy statement — and so the README and the Disclaimer, which
|
||||
carry it — said the driver's report had been "read with a test program against one driver and one card; no real
|
||||
game had been read when this was written". On 2026-11-14 the owner read it in Phantom Blade Zero and Cyberpunk
|
||||
2077, and the first of them showed something the statement did not say: the stages overlap, and the graphics
|
||||
card's stage — the driver's start mark to its end mark — includes the card's waiting and was longer than the whole
|
||||
frame. So the statement now says both, names the two figures of the driver's own that are shown beside that stage
|
||||
since this release, and says a driver may give neither. The **Privacy Policy** (2.21) adds those two averages to
|
||||
what a session stores, and "its frame-generation multiplier" becomes the multipliers the driver gave during the
|
||||
session. The **Disclaimer** (2.17) changes nowhere else: the component makes no new call, so §2's paragraph on the
|
||||
one call it makes stands as written.
|
||||
|
||||
### What version 2.20 of the Privacy Policy and 2.16 of the Disclaimer changed (0.1.0-beta.47, train C)
|
||||
|
||||
**The part inside a game makes a call of its own** (owner decisions D132, D136, D138–D141; the wording's main
|
||||
points approved with the plan of 2026-11-13). Every earlier version could say that the component reads only what a
|
||||
game passes to the graphics calls it intercepts. With Advanced metrics on, in a Direct3D 12 game that had loaded
|
||||
NVIDIA's driver library, it now also asks the driver, about once a second, for the driver's report of the last
|
||||
frames' stages and its low-latency state. So: the **Privacy Policy** (2.20) names what a session stores of it —
|
||||
durations and five switches, never a time of day, never the moment of an input — in §1's item on Advanced metrics
|
||||
and in §4's list of what the component observes. The **Disclaimer** (2.16) changes three places: "What it observes
|
||||
inside the game" names the report; the sentence "API arguments and nothing else" is replaced by what is true; and
|
||||
§2, after the paragraph on the background thread, gains the paragraph on this call — that it is made on the game's
|
||||
presenting thread, through a library the game loaded and FrameLedger never loads, that two files are kept loaded
|
||||
for it, that it calls nothing that sets or delays, what ends it, and **that a call which never returned could not be
|
||||
stopped**. The accuracy statement loses "PC latency (Reflex)" from "not measured at all" — end-to-end latency
|
||||
still is not measured — and gains the item saying these are the driver's numbers, read from no real game when it
|
||||
was written.
|
||||
|
||||
### What version 2.19 of the Privacy Policy changed (0.1.0-beta.45)
|
||||
|
||||
**Six more calls read inside the game, only while Advanced metrics is on** (train B's fourth step, owner decisions
|
||||
D129–D131; the wording approved with the plan of 0.1.0-beta.45). Version 2.18 named Streamline's answers to two
|
||||
questions about a feature — its version, what it requires — and "four further calls". This release reads two more
|
||||
answers and four things the game does, none of which is in that list, so the version moves. §1's item on Advanced
|
||||
metrics gains, **for each Streamline feature the game asks about or controls: whether Streamline answers that it is
|
||||
supported, whether it is loaded, whether the game switched it on or off while it ran, and how many times its
|
||||
resources were allocated and freed; and whether the game shut Streamline down, and how many times**. It also says
|
||||
two more things that are never read: **what identifies the graphics card that the game hands over with its
|
||||
question** — `slIsFeatureSupported` takes an `sl::AdapterInfo`, the adapter's LUID or a Vulkan physical device,
|
||||
which D131 forbids and a check in the build refuses by name — and **the content of a graphics resource**: the two
|
||||
resource calls take a command buffer and a viewport, forwarded and never looked at. §4's "four further calls" is
|
||||
ten, its "two questions" are four, and its list of what is stored names the new facts and repeats that what
|
||||
identifies the card is not among them. What the game started Streamline with (`slInit`) is not in the policy
|
||||
because it is not read, and will not be (D129). The accuracy block's item says what the new rows are — calls the
|
||||
game made, counted to fifteen, not a statement that a feature ran. The Disclaimer stays 2.15. §2 is unchanged:
|
||||
nothing is sent.
|
||||
|
||||
### What version 2.18 of the Privacy Policy changed (0.1.0-beta.44)
|
||||
|
||||
**Two more calls read inside the game, only while Advanced metrics is on** (train B's third step, owner decisions
|
||||
D126–D128 beside it; the wording approved with the plan of 0.1.0-beta.44). Version 2.17 named Streamline's per-frame
|
||||
constants and the frame-generation configuration, and "two further calls"; this release reads what Streamline
|
||||
**answers** when the game asks about a feature, which is in neither list, so the version moves. §1's item on
|
||||
Advanced metrics gains **which features the game asked about, the version of each and of its NGX model, and what
|
||||
each requires** — the graphics APIs it supports, whether V-Sync must be off and hardware-accelerated GPU scheduling
|
||||
on, how many processor threads, viewports and buffers, and the versions of Windows and of the graphics driver that
|
||||
Streamline found beside the ones the feature needs. It also says what of that answer is never read: **the lists it
|
||||
points to** — the buffers' names, the names of Vulkan extensions and features — which a check in the build holds
|
||||
(the count of required buffers is read; its list is not). §4's "two further calls" is four, and its list of what is
|
||||
stored names the versions and requirements. The versions of Windows and of the driver are the ones Streamline
|
||||
reports to the game; FrameLedger already stores the driver's version with a session's hardware. The accuracy
|
||||
block's item says what these are — Streamline's answers, not a check of the PC — and that a game asks while it
|
||||
starts, so most sessions have none. The Disclaimer stays 2.15. §2 is unchanged: nothing is sent.
|
||||
|
||||
### What version 2.17 of the Privacy Policy changed (0.1.0-beta.43)
|
||||
|
||||
**Two more calls read inside the game, only while Advanced metrics is on** (train B's second step, owner decisions
|
||||
D122–D125; the wording approved with the plan of 0.1.0-beta.43). Version 2.16 named what a session stores of DLSS and
|
||||
of FSR's upscaling item by item, and neither list holds what this release reads, so the version moves rather than
|
||||
the words being stretched. §1's item on Advanced metrics gains **what the game told NVIDIA Streamline about each
|
||||
frame** — the size of the jitter, the motion-vector scale, the depth range and whether depth is inverted, the lowest
|
||||
and highest field of view, the aspect ratio, whether the projection is orthographic, how its motion vectors are
|
||||
stored and how often it reset the upscaler's history — and **how it configured FSR frame generation** — on or off,
|
||||
whether it may run asynchronously, its flags, whether only generated frames are presented, and the rectangle it
|
||||
generates in. The sentence on what is never read (where the camera is, which way it looks, its matrices) stands as
|
||||
it was: those sit in the same data as Streamline's constants, and a check in the build refuses code that names them.
|
||||
§4 says what is new about *how*: until now every parameter read was of a call FrameLedger intercepted anyway; these
|
||||
two calls are intercepted in a game **only once a session with the option on has started there**, and with the
|
||||
option off nothing in the game is touched for them. The accuracy block's item on what a game tells its upscaler
|
||||
names the two, and no longer says none of it was read from a real game — FSR's upscaling values were, on
|
||||
0.1.0-beta.41 and beta.42. The Disclaimer stays 2.15, as before. §2 is unchanged: nothing is sent.
|
||||
|
||||
### What version 2.16 of the Privacy Policy changed (0.1.0-beta.40)
|
||||
|
||||
**Advanced metrics inside the game** (train B, owner decisions D111–D116; the content approved with the plan, once
|
||||
for the train's three releases). §1's item on Advanced metrics gains what a session stores **for a game FrameLedger
|
||||
injects into, only while the option is on**: what the game passed to its upscaler in the calls FrameLedger
|
||||
intercepts — the output size, presets and exposure values it gave DLSS, whether it said its colour buffers are HDR,
|
||||
auto-exposure and alpha upscaling; the sharpening, the jitter's size, the exposure, the depth range, the lowest and
|
||||
highest field of view and the flags it gave FSR, the frame time it reported, FSR's own memory when the game asked —
|
||||
and what is never read: where the camera is, which way it looks, its matrices. It also says that switching the option
|
||||
off stops the reading inside a game as well. §4 had always named "the parameters your games pass to the graphics APIs
|
||||
it intercepts"; it now says that with the option on more of the upscaling calls' parameters are read **and stored**,
|
||||
which is what is new. The accuracy block gains an item: these are the game's words to the upscaler, not a check of
|
||||
what the upscaler did, and many games show none. The Disclaimer stays 2.15, as the accuracy statement's additions
|
||||
have not moved it before (beta.19, beta.20, beta.25). §2 is unchanged: nothing is sent.
|
||||
|
||||
### What version 2.15 of the Privacy Policy and of the Disclaimer changed (0.1.0-beta.39)
|
||||
|
||||
**Advanced metrics** (owner decisions D101–D108; the Privacy Policy's content approved with the plan, the Disclaimer's
|
||||
two sentences by the owner's answer of 2026-11-11). Privacy Policy §1 gains one item — what a session stores **only
|
||||
while the option is on**: more sensor series of the graphics card, and of the processor, the memory and the motherboard
|
||||
when the Agent runs as administrator with PawnIO; a description of the hardware; what each display can do and what the
|
||||
game's display did; the graphics driver's settings, global and for the game — and what is never read: a serial
|
||||
number, a display's EDID, a list of other programs. §3A says an export and a bug report do not carry it. §4 names the
|
||||
same as things the software can observe, only while the option is on. The Disclaimer's §5 and §5A said PawnIO and the
|
||||
admin mode were for the CPU temperature alone; both now name the processor's, the memory's and the motherboard's
|
||||
sensors with the option on. The accuracy block gains an item that says none of these readings has been checked
|
||||
against another tool. §2 is unchanged: nothing is sent, as before. (Versions 2.12 to 2.14 of the Privacy Policy and
|
||||
2.12 to 2.14 of the Disclaimer are recorded in the changelog of the release that carried each.)
|
||||
|
||||
### What version 2.11 of the Privacy Policy changed (0.1.0-beta.23)
|
||||
|
||||
A game's page shows its artwork (beta.23 PR-3, owner decisions D60/D61; the wording approved with the plan). §1 adds the
|
||||
|
||||
@@ -53,5 +53,3 @@ Each section below lives in its own file under `docs/spike-notes/`, moved verbat
|
||||
| §27 | Switching to Games, and a language change that lands elsewhere (2026-11-06, beta.34) | [`spike-notes/27-games-page-2026-11-06.md`](spike-notes/27-games-page-2026-11-06.md) |
|
||||
| §28 | The main line on .NET 11's release — the whole gate, and what the analyses read (2026-11-11, beta.37, D94–D96) | [`spike-notes/28-dotnet11-main.md`](spike-notes/28-dotnet11-main.md) |
|
||||
| §29 | C# 15 against the checks — the canary, and where its constructs would go (2026-11-11, beta.37, D96) | [`spike-notes/29-csharp15-canary.md`](spike-notes/29-csharp15-canary.md) |
|
||||
| §30 | Reflex latency per frame — the routes there are, and what each would cost; a reading, nothing run (2026-11-12, beside beta.45, D130; §M14) | [`spike-notes/30-reflex-latency.md`](spike-notes/30-reflex-latency.md) |
|
||||
| §31 | Reflex route D on the harness — the driver's two getters called from an unshipped probe, against a stand-in module and the installed driver; no game touched (2026-11-13, after beta.46, D132; §M14) | [`spike-notes/31-reflex-route-d-harness.md`](spike-notes/31-reflex-route-d-harness.md) |
|
||||
@@ -99,7 +99,7 @@ The last thing P1 owes (§R4 moved it here because it needs P2's drain and recor
|
||||
| 2 | OFF | | | |
|
||||
| 3 | OFF | | | |
|
||||
|
||||
Gates: FPS delta ≤ 0.5 %, Agent CPU ≤ 1 % of a core *(≤ 2.5 % since 2026-11-11, D117)*, Agent RSS ≤ 150 MB. **Overlay resident ≤ 8 MB is
|
||||
Gates: FPS delta ≤ 0.5 %, Agent CPU ≤ 1 % of a core, Agent RSS ≤ 150 MB. **Overlay resident ≤ 8 MB is
|
||||
not measured by the runbook** and is left blank rather than guessed: it is a module inside the game
|
||||
process, and reading the target's memory is what CLAUDE.md rule 4 forbids — an external tool that
|
||||
inspects module sizes is the way to fill it.
|
||||
|
||||
@@ -1,232 +0,0 @@
|
||||
## 30 · Reflex latency per frame — the routes there are, and what each would cost *(2026-11-12, written beside 0.1.0-beta.45, owner decision D130; `20_OPEN_QUESTIONS` §M14)*
|
||||
|
||||
**Why this was written.** Train C of Advanced metrics is "Reflex latency per frame" (`18_GPU_VENDOR_APIS` §The
|
||||
trains). §M14 asks whether any route to it stays inside rules 4 and 5, and pre-commits the answer for the case
|
||||
that none does. The owner decided on 2026-11-12 (D130) that this spike is written beside 0.1.0-beta.45 **as a
|
||||
document**, and that no code of train C is written until the owner has read it and said go or no.
|
||||
|
||||
**What this is, and what it is not.** A reading — of the vendored NVAPI headers
|
||||
(`src/native/third_party/nvapi/nvapi.h`, `nvapi_interface.h`), of Streamline's public headers and plugin source
|
||||
at tag `v2.14.16` (`include/sl_reflex.h`, `include/sl_pcl.h`, `source/plugins/sl.reflex/reflexEntry.cpp`,
|
||||
`source/plugins/sl.pcl/pclstats.h`, `pclImpl.h`; fetched through GitHub's API, not vendored), of this
|
||||
repository's own hook engine, and of a copy of the owner's ledger; one file on the dev box was looked at, the
|
||||
export table of the installed `nvapi64.dll`. **Nothing was run in a game and no shipped code changed.** Every
|
||||
"unknown" below is unknown, not assumed either way.
|
||||
|
||||
### What Reflex's numbers are, and who holds each
|
||||
|
||||
| What | Where it lives | The catalog entry that wants it |
|
||||
|---|---|---|
|
||||
| **The per-frame report**: for each of the last 64 frames, the times of input sample, simulation start/end, render submit start/end, present start/end, driver start/end, OS render queue start/end, GPU render start/end, and two durations (`gpuActiveRenderTimeUs`, `gpuFrameTimeUs`) | The **driver**. A program gets it by calling `NvAPI_D3D_GetLatency(pDev, NV_LATENCY_RESULT_PARAMS*)` with the game's own device; Streamline's `slReflexGetState` makes that call and hands the same 64 reports back as `sl::ReflexState::frameReport` | `nvapi.reflex.frame_report`, `sl.reflex.state` |
|
||||
| **The driver's low-latency state**: low-latency mode on, the last sleep interval, whether the game calls the sleep, the frame-generation multiplier last used | The driver: `NvAPI_D3D_GetSleepStatus(pDev, …)` | `nvapi.reflex.sleep_status` |
|
||||
| **What the game asked for**: low latency or low latency with boost, the frame-rate limit, whether markers may steer the driver | Only the **arguments** of `NvAPI_D3D_SetSleepMode` or of Streamline's `slReflexSetOptions` — no getter returns boost or the limit | `nvapi.reflex.mode` |
|
||||
| **The markers the game sets** each frame (simulation start … present end, the latency ping, the flash trigger) | The arguments of `NvAPI_D3D_SetLatencyMarker` / `slPCLSetMarker`; the PCL plugin also writes each as an ETW event | `sl.pcl.markers` |
|
||||
|
||||
`FlFrameRecord.reflexLatencyUs` (@48, "0 = unavailable") has waited for this since the record was designed, and
|
||||
`03_METRICS` lists *PC latency* as "mean/p95 of `reflexLatencyUs` when Reflex reports it". **A report cannot go
|
||||
into its own frame's record**: the driver completes a frame's report after that frame's GPU work ends, several
|
||||
presents after the record was written, and a ring record is never rewritten. Whatever route is taken, latency
|
||||
arrives as a series beside the frames, not as a column of them.
|
||||
|
||||
### What the owner's sessions already say
|
||||
|
||||
From 0.1.0-beta.44's `sl.feature.versions` / `sl.feature.requirements` (sessions 181–186 of the ledger's copy;
|
||||
`docs/HANDOFF.md`, item 42):
|
||||
|
||||
| Game (session) | Interposer | Asked Streamline about `kFeatureReflex` | about `kFeaturePCL` |
|
||||
|---|---|---|---|
|
||||
| Phantom Blade Zero (181) | 2.14.1 | version and requirements | version and requirements |
|
||||
| Clair Obscur: Expedition 33 (182) | 2.7.30 | version and requirements | version and requirements |
|
||||
| Valor Mortis (183, 184) | 2.14.1 | version and requirements | version and requirements |
|
||||
| Black Myth: Wukong (185) | 2.7.4 | version and requirements | version and requirements |
|
||||
| Cyberpunk 2077 (186) | 2.14.1 | requirements only | not asked |
|
||||
|
||||
So **every Streamline game run asks about Reflex**, and the four Unreal Engine games about PCL as well. That a
|
||||
game asks about a feature is not that it uses it; 0.1.0-beta.45's `slIsFeatureLoaded` and `slSetFeatureLoaded`
|
||||
rows will say whether Reflex and PCL are loaded and switched, on the owner's next sessions. No session says
|
||||
anything about a game that uses Reflex without Streamline: none of the hooks sees NVAPI.
|
||||
|
||||
**Added 2026-11-13, from the first sessions on 0.1.0-beta.45** (190–196): Streamline answers `eOk` for
|
||||
`kFeatureReflex` in all five Streamline games run, and `slIsFeatureLoaded` says it is loaded in the three that ask
|
||||
(Phantom Blade Zero, Cyberpunk 2077, Hogwarts Legacy); Cyberpunk 2077 and Dying Light: The Beast switch it off and
|
||||
on through `slSetFeatureLoaded`. `kFeaturePCL` is supported in the four games that ask about it. Loaded is still
|
||||
not in use: whether a game sets markers is what no hook sees.
|
||||
|
||||
### The routes
|
||||
|
||||
**A — hook NVAPI's own functions** (`SetLatencyMarker`, `SetSleepMode`; what `17_HOOK_ENGINE` §Memory / latency
|
||||
still names). The `nvapi64.dll` on the dev box (driver 32.0.16.2114, its export table dumped for this note)
|
||||
exports two functions, `nvapi_QueryInterface` and `nvapi_Direct_GetMethod` — §M14 said one — and no latency
|
||||
function: each of those is an address `nvapi_QueryInterface` returns for an id (`nvapi_interface.h`:
|
||||
`NvAPI_D3D_GetLatency` is `0x1a587f9c`). A hook on one is a patch at an address
|
||||
learned at run time — the class refused on 2026-08-09 — or a wrapper returned from a hooked
|
||||
`nvapi_QueryInterface`, which is a write to what the game receives (rule 4). **Refused, as §M14 pre-committed.**
|
||||
|
||||
**B — hook Streamline's Reflex and PCL functions** (`slReflexSetOptions`, `slPCLSetMarker`, `slReflexGetState`).
|
||||
None is an export of `sl.interposer.dll`. The game gets each through the exported `slGetFeatureFunction(feature,
|
||||
name, &fn)`, and Streamline's own header does that **once**: `SL_FEATURE_FUN_IMPORT_STATIC` keeps the pointer in
|
||||
a function-local static after the first call. Two consequences. A hook on `slGetFeatureFunction` could only see
|
||||
the game's calls by handing back a wrapper — train D's question (§M15), which needs rule 4 amended. And a hook
|
||||
that exists only for Advanced metrics is installed after the attach (D111), by which time a game that has
|
||||
presented a frame has fetched its functions: **the same reason `slInit` is not hooked (D129) applies to the
|
||||
fetch.** Not a route for train C; it stays train D's, and this finding weakens train D as well.
|
||||
|
||||
**C — the Overlay calls `slReflexGetState` itself**, having asked the interposer's exported, documented-thread-safe
|
||||
`slGetFeatureFunction` for it. No patch, no wrapper, and Streamline uses the device it already holds. But the
|
||||
header says of `slReflexGetState`: *"This method is NOT thread safe"*, and the source shows why — the function
|
||||
**writes** two fields of the plugin's context (`lowLatencyAvailable`, `latencyReportAvailable`) from the result
|
||||
of the two driver calls it makes, with no lock, and then calls into the PCL plugin. The game calls the same
|
||||
function from a thread FrameLedger cannot know (the call is not hooked), so the Overlay cannot keep its call
|
||||
from overlapping the game's. It would be FrameLedger breaking the vendor's stated contract inside the game, and
|
||||
writing plugin state the game reads back. **Recommended refused**, on the header's own words.
|
||||
|
||||
**D — the Overlay calls the driver's two getters itself**: `NvAPI_D3D_GetLatency` and `NvAPI_D3D_GetSleepStatus`,
|
||||
resolved through `nvapi_QueryInterface` of an `nvapi64.dll` **the game already loaded** (never loaded by
|
||||
FrameLedger), with the device of the swap chain the Overlay already hooks. This is §M14's "route to try first".
|
||||
What it would be:
|
||||
|
||||
- **No patch and no new hook.** Two calls, both getters; `tools/nvapi-readonly-check.ps1`'s list (D108) would
|
||||
gain them, and the check would have to cover the Overlay as well as the bridge. The Overlay would not link
|
||||
`nvapi64.lib`: it needs the two ids and the two structs from the vendored MIT headers.
|
||||
- **It works without Streamline** — any Direct3D game that uses Reflex — and not on Vulkan (the Vulkan layer has
|
||||
no NVAPI device; Reflex there is a Vulkan extension, a different study).
|
||||
- **It gives** the report (`nvapi.reflex.frame_report`) and the sleep status (`nvapi.reflex.sleep_status`), and
|
||||
through them most of `sl.reflex.state`. **It does not give** what the game asked for (boost, the limit:
|
||||
`nvapi.reflex.mode` stays N/A, with the reason) or a count of markers.
|
||||
- **First of its kind in two ways**, and both are the owner's to rule on. The Overlay would call a *vendor's
|
||||
driver interface on its own initiative* inside the game — today it only forwards the game's calls and reads
|
||||
their arguments. And it would use *the game's device object* for a call the game did not make: rule 4 allows
|
||||
"COM/handle objects we legitimately own", and the device is the game's. The nearest precedent is the read of
|
||||
`IDXGISwapChain::GetLastPresentCount` on the hooked chain (rule 6, 2026-09-06), a getter on the game's swap
|
||||
chain inside the present detour.
|
||||
- **Unknown, and what the spike would have to measure**: which object NVAPI wants for a Direct3D 12 game (the
|
||||
device behind the queue the swap chain was made on — not verified); whether the getters are safe on a thread
|
||||
that is not the game's — the header is silent; Streamline's own plugin calls them on whatever thread the game
|
||||
asks for its state while the render thread sets markers, which suggests the driver tolerates it, and is an
|
||||
inference; what a call costs, on the presenting thread or on the Overlay's own; what it returns in a game that
|
||||
never set a marker (the header: valid only after markers with rising frame ids); whether a call that blocks
|
||||
in the driver can be bounded — an SEH guard does not bound a wait.
|
||||
- **How often**: one call returns 64 frames. At 240 presents a second that is four calls a second to lose none;
|
||||
once a second keeps the newest 64 and says how many it skipped.
|
||||
- **What else moves**: a series through region 5 (a layout change, or the reserved words), the Agent's sampler,
|
||||
the page; the Disclaimer's sentence about what the Overlay's own thread does (a version of its own, the
|
||||
owner's wording); the Privacy Policy (what is stored: times, no content).
|
||||
|
||||
**E — from outside the game: the PCL statistics ETW provider.** Streamline's PCL plugin (and the Reflex SDK's
|
||||
`pclstats.h` in a game without Streamline) registers `PCLStatsTraceLoggingProvider`
|
||||
(`{0d216f06-82a6-4d49-bc4f-8f38ae56efab}`) and writes an event for every marker (`PCLStatsEvent`: `Marker`,
|
||||
`FrameID`), which is what NVIDIA's own overlay listens to. No injection, so it would also be the only route for
|
||||
a game the guard refuses. What it costs:
|
||||
|
||||
- **It gives the game-side markers only** — simulation, render submit, present, the ping. The driver, OS queue
|
||||
and GPU times are not in these events; NVIDIA's overlay has them from the driver.
|
||||
- **A trace session needs administrator rights** (or membership of *Performance Log Users*); the Agent is
|
||||
unelevated by default (D34).
|
||||
- **Listening changes what the game does.** Enabling the provider sets the game's `g_PCLStatsEnable`, and its own
|
||||
ping thread then posts a registered window message — or, where the game chose a key, `F13`–`F15` key messages
|
||||
— to the game's window every 100–300 ms. It is the game's code and the vendor's design, and it is what any
|
||||
listener causes; FrameLedger would still be the cause, in a game it is not even injected into.
|
||||
- **It reopens a closed decision**: ETW left the product on 2026-08-27/28 (Tier 2 is not a measurement;
|
||||
`20_OPEN_QUESTIONS` §G keeps the question of a no-injection measurement).
|
||||
|
||||
**F — NVAPI from the Agent.** `NvAPI_D3D_GetLatency` takes the game's device. Another process has none. Not a
|
||||
route.
|
||||
|
||||
### What each catalog entry would become
|
||||
|
||||
| Entry | Route A, B | C | D | E |
|
||||
|---|---|---|---|---|
|
||||
| `nvapi.reflex.frame_report` | refused | (refused) | **read**, Direct3D | game-side times only |
|
||||
| `nvapi.reflex.sleep_status` | refused | part | **read**, Direct3D | — |
|
||||
| `nvapi.reflex.mode` | refused | — | N/A: no getter returns it | — |
|
||||
| `sl.reflex.state` | refused | (refused) | the same numbers, under the NVAPI entries | — |
|
||||
| `sl.pcl.markers` | refused | — | — | counted |
|
||||
|
||||
### What this reading settles, and what it leaves to the owner
|
||||
|
||||
- **Settled by reading**: A and B are the refused classes; C breaks the vendor's own contract; F does not exist.
|
||||
§M14's pre-committed "no route without a patch at a run-time address" does **not** fire — D has no patch and E
|
||||
has no injection — so the entries do not go to N/A on this document alone.
|
||||
- **The owner's**, because each crosses a line the rules draw today:
|
||||
1. **Route D — go to a spike, or no?** A go means: `hook-harness` and a stub `nvapi64.dll` first (the call
|
||||
made, the report read, the overhead measured against NFR-1, a blocked call and a missing module shown to be
|
||||
harmless), then one real title of the owner's choice, never first in a game inside the anti-cheat
|
||||
exception's trial (D38). Pre-committed for that spike: a fault or a hang attributable to the call, an
|
||||
overhead above NFR-1, or a Direct3D 12 device that cannot be obtained without reading what rule 4 forbids
|
||||
→ Reflex latency stays N/A and the page says why. A go also needs the owner's ruling that calling a
|
||||
driver getter with the game's device is inside rule 4, asked with the rule quoted, as §M15 asks for its
|
||||
own amendment.
|
||||
2. **Route C — recorded as refused?** (Recommended: yes.)
|
||||
3. **Route E — leave §G closed, or reopen it for latency markers?** (Recommended: leave it; the route gives
|
||||
the smaller half of the number and makes a game post messages to itself.)
|
||||
- **Not looked into**: Reflex on Vulkan; AMD Anti-Lag 2 and Intel XeLL, which have their own interfaces; what
|
||||
`nvapi_Direct_GetMethod` is (the vendored headers do not declare it; the vendored import library names it; nothing here
|
||||
would use it); what a
|
||||
real game's interposer and its Reflex and PCL plugins export (the above is the headers' and the source's word,
|
||||
not a dump of a game's files).
|
||||
|
||||
### The owner's answers (2026-11-13, D132 and D133)
|
||||
|
||||
1. **Route D: go — to the spike on `hook-harness` and a stub first.** With it the ruling a go needed: calling a
|
||||
driver's read-only getter with the device of the swap chain the Overlay hooks is inside rule 4 (`CLAUDE.md`
|
||||
carries the note). No real game until the owner has seen the spike's result; no shipped code changes for it.
|
||||
2. **Route C: refused.**
|
||||
3. **Route E: left closed**; §G is not reopened.
|
||||
|
||||
The spike is [`spike-notes` §31](31-reflex-route-d-harness.md), run on 2026-11-13: none of the stop conditions
|
||||
above fired on the harness, and it ends in the question of one real title.
|
||||
|
||||
### Added 2026-11-14: Streamline's two programming guides, read against this note and the code
|
||||
|
||||
`docs/ProgrammingGuideReflex.md` and `docs/ProgrammingGuideDLSS_RR.md` of NVIDIA's Streamline repository, both
|
||||
"Version 2.14.16", fetched as text and read whole — at the owner's request. What they add, and what they change.
|
||||
|
||||
**Reflex**
|
||||
|
||||
- **Low latency and frame generation: the dependency runs one way.** The guide lists the plugin's parts as
|
||||
"distinct to each other without any cross-dependencies", wants Reflex's default to be *On*, and its checklist
|
||||
tests *Reflex On* with frame generation **off**. Frame generation is what needs Reflex. The owner's "without
|
||||
frame generation the game cannot switch Reflex on" is true of some of the owner's games' menus, not of Reflex.
|
||||
The sessions of 2026-11-14 agree (HANDOFF, item 47): low-latency mode on at a multiplier of 1 in four games;
|
||||
Phantom Blade Zero switches it on with frame generation; Clair Obscur without frame generation has it off.
|
||||
- **The sleep and the markers are sent whatever the mode.** "`slReflexSleep` and `slPCLSetMarker` must always be
|
||||
called even when Reflex Low Latency mode is Off"; the verification overlay's *App Called Sleep* stays 1 with
|
||||
Reflex off. So `bUseGameSleep` says the game calls the sleep, **not** that Reflex is on, and a report exists
|
||||
with Reflex off — which is what the sessions on 0.1.0-beta.48 showed (HANDOFF, item 46). Phantom Blade Zero
|
||||
without frame generation is exactly this: the game sleeps, low-latency mode off, 1 062 reads.
|
||||
- **`slReflexSetOptions` is called once, and again only when an option changes.** A hook on it would see nothing
|
||||
in most sessions even if it could be placed: `nvapi.reflex.mode` stays refused for a second reason.
|
||||
- **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** — **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`).
|
||||
- **The stages, in NVIDIA's words** (the verification overlay's table): *driver* is from the first buffer
|
||||
submission to the last present submission; *OS queue* from the first significant buffer submission to the end
|
||||
of the GPU's work; *GPU* from where its rendering starts to where it ends; *total render time* is "time spent
|
||||
by GPU rendering". With frame generation the test's own columns split the GPU's part at "DLSS FG start". **Not
|
||||
reconciled with what is stored**: an OS queue that ends with the GPU's work should not be shorter than the
|
||||
GPU's span, and in Phantom Blade Zero it is (12.9 ms beside 16.4 ms). The guide's table describes an overlay,
|
||||
not the fields of `NV_LATENCY_RESULT_PARAMS`; nothing is concluded from it, and no label was changed on it.
|
||||
- **Where Reflex helps**, by the guide: GPU-bound, or V-Sync with variable refresh; not CPU-bound. FrameLedger
|
||||
shows the driver's switches and draws no conclusion about benefit.
|
||||
|
||||
**DLSS Ray Reconstruction**
|
||||
|
||||
- **The code already has it right, and two comments had the reason wrong.** The guide: "When DLSS-RR is switched
|
||||
on, it completely overrides DLSS (Super Resolution)", in the quality mode set for DLSS, through
|
||||
`slEvaluateFeature(sl::kFeatureDLSS_RR, …)`. That is the present detour's RR arm (upscaler DLSS, the RR fact
|
||||
beside it), measured on Cyberpunk 2077 on 2026-08-15. `fl_shm.h` and `dllmain.cpp` still said super resolution
|
||||
and RR "run together" / "in the SAME frame"; they do not, and the comments now say what is true.
|
||||
- **Off is a mode, not a release**: "set `sl::DLSSDOptions.mode` to `sl::DLSSDMode::eOff`, note that this does
|
||||
NOT release any resources". So *loaded* and *allocated* (the Advanced tables of 0.1.0-beta.45) are not *in
|
||||
use*; the RR verdict is taken from evaluations and from nothing else, which is why it is right.
|
||||
- **If `sl.dlssd.options` is ever read** (it is a spike entry, set through a call no hook sees): the structure
|
||||
carries `worldToCameraView` and `cameraViewToWorld` — camera matrices, never read (rule 4) — and RR ignores the
|
||||
DLSS options `sharpness` and `useAutoExposure`, so a session's DLSS rows do not describe RR on those two.
|
||||
What the entry would add is RR's preset for each mode and how normals and roughness are packed. Little.
|
||||
- **No dynamic resolution under RR**: a change of input size re-initialises the denoiser. Nothing here depends
|
||||
on it.
|
||||
@@ -1,221 +0,0 @@
|
||||
## 31 · Reflex route D on the harness — the driver's two getters, called from a probe *(2026-11-13, after 0.1.0-beta.46, owner decisions D132, D133; `20_OPEN_QUESTIONS` §M14)*
|
||||
|
||||
**Why this was measured.** §30 read the routes to Reflex latency per frame and left one that needs no patch: the
|
||||
Overlay calling the driver's two getters, `NvAPI_D3D_GetLatency` and `NvAPI_D3D_GetSleepStatus`, with the device of
|
||||
the swap chain it hooks. The owner said go on 2026-11-13 (D132) — **to a spike on the harness first** — and ruled
|
||||
that such a call is inside rule 4 (`CLAUDE.md`, the rule's note). This is that spike. **No shipped code changed and
|
||||
no game was touched**: the call sequence lives in an unshipped probe, and nothing loaded into a game includes it.
|
||||
|
||||
**The instrument.** `src/native/tools/fl-probe-reflex` (built with the Overlay's flags; ctest
|
||||
`fl_reflex_probe_stub` for the half a build machine can run):
|
||||
|
||||
- `fl_reflex_candidate.h` — what would move into the Overlay: find `nvapi64.dll` **if the process already holds
|
||||
it** (never load it), ask its export `nvapi_QueryInterface` for the two getters by the ids of the vendored
|
||||
`nvapi_interface.h`, call them SEH-guarded, summarise the sixty-four frames. It does not link `nvapi64.lib`:
|
||||
the static library loads the DLL itself, from a trusted location and with a signature check.
|
||||
- `--stub`: against `tools/vendor-stubs/stub_nvapi64.cpp`, a stand-in module with knobs for what a driver cannot be
|
||||
made to do on demand.
|
||||
- `--real`: against the installed driver on this PC's NVIDIA adapter, **with the probe playing the game's part** —
|
||||
it loads `nvapi64.dll`, calls `NvAPI_Initialize`, and **sets latency markers on its own device** for a few
|
||||
hundred frames. That is a write, and it is said here plainly: a getter has nothing to return without it, the
|
||||
process is the probe's own, and no shipped binary contains the call (D108's read-only rule is about the Agent's
|
||||
bridge; rule 4's note is about a game). The owner was told and approved it with the plan.
|
||||
|
||||
### The decision table, written before any run
|
||||
|
||||
| # | Measured | Outcome → consequence |
|
||||
|---|---|---|
|
||||
| M1 | Stub: the module absent; a getter absent; an error; a report of nothing; sixty-four reports; both device kinds | Anything called or loaded when the module is absent, or a wrong classification → the candidate is wrong and is fixed before any driver run. Otherwise: these cases are harmless as written. |
|
||||
| M2 | Stub: a call that does not return for 1.5 s, made on a thread of its own and made by a thread that has other work | Made by the busy thread, that thread stands still → **the call may not be made on the Overlay's watchdog** (it supervises, installs and flushes): a thread of its own, or the presenting thread if M6 allows. A thread of its own is a second background thread, and the Disclaimer's sentence about "one" changes. |
|
||||
| M3 | Real: the getters **before** `NvAPI_Initialize` | A fault → a game that holds the module but has not initialised it would fault under us, and the Overlay cannot initialise NVAPI itself (not a getter): **route D stops** unless initialisation can be known without a call. An error status → harmless: read as "not available". |
|
||||
| M4 | Real: initialised, 120 frames, **no marker** | Zero frames or an error → as the header says: a game that does not use Reflex reads N/A. Frames with content → record what the driver fills in by itself. |
|
||||
| M5 | Real: 300 frames **with markers** | Frames with sensible spans → the report is readable by a third party in the process. Zero frames → markers alone are not enough (a sleep mode is needed too): route D reads only games that set one, and the note says so. |
|
||||
| M6 | Real: the cost of one call (2000 calls, on the presenting thread) | NFR-1 allows 1 µs a present. Once a second on the presenting thread costs `call / presents-a-second` a present: at 60 a second a call may cost 60 µs. Median within that → the presenting thread, once a second, is allowed. Above it, or a worst case over 1 ms → **never on the presenting thread**; a thread of its own (M2). |
|
||||
| M7 | Real: the getters on another thread four times a second for 60 s, beside a thread that presents and sets markers | **Any fault → route D stops** (pre-committed, §30). Error statuses or empty reports → recorded; they decide whether a read is trusted. Frames a second beside the poller more than 0.5 % below alone → the rate is too high or the route too costly: lower it and measure again, or stop. |
|
||||
| M8 | Real, Direct3D 12: read with the device, read with the queue, markers on each | The device works → the Overlay already holds it (`g_d3d12Device`). **Only the queue works → Direct3D 12 is out of reach**: the Overlay does not hold the queue (`ResolveApi`: `GetDevice` does not return it) and may not go looking for it. Route D would then be Direct3D 11 only. |
|
||||
| M9 | Real: the unit of the report's times | The gap between two frames' `simStartTime` against the probe's own frame time. Whatever it is, is recorded; a unit that cannot be told → the spans are not shown as times. |
|
||||
|
||||
Not in this spike, whatever it shows: anything in a game; where the numbers would go (shared memory, the Agent, the
|
||||
page); the wording of the Disclaimer and the Privacy Policy. Those are a plan of their own, after the owner's go.
|
||||
|
||||
### Results
|
||||
|
||||
**Where.** The dev box of §Environment: Windows 11 Pro build 29648, RTX 5080, NVIDIA driver 32.0.16.2114
|
||||
(`nvapi64.dll` of the same version), 2026-11-13. `--stub` on software devices; `--real` three times (and a fourth,
|
||||
shorter, after a fix to the probe — row M6), on the NVIDIA
|
||||
adapter, each with a 256×256 composition swap chain presented without a wait — some 14,000 to 17,000 frames a
|
||||
second, which is what makes the cost of anything beside it visible and is nothing like a game.
|
||||
|
||||
| # | What was seen | Against the table |
|
||||
|---|---|---|
|
||||
| M1 | Stub, all 20 checks pass: with the module absent `Resolve` says so, calls nothing and loads nothing; a module without the getters is refused whole; an error comes back as the error; a report of nothing is zero frames; sixty-four reports are read as the header lays them out; the driver is handed the device and only the device, Direct3D 11 and Direct3D 12 alike; no device, no call. | Harmless as written. |
|
||||
| M2 | A call held for 1.5 s on a thread of its own: another thread ticked 16 times in its first second. The same call made by that ticking thread: **0 ticks** in the second. | **Not on the watchdog.** A thread of its own, or the presenting thread (M6). |
|
||||
| M3 | The getters **before** `NvAPI_Initialize`, with the module loaded: both resolve, `GetLatency` returns `NVAPI_OK` and sixty-four empty frames. No fault, three runs. | Harmless: an uninitialised NVAPI reads as "nothing reported". |
|
||||
| M4 | Initialised, 120 frames, no marker: `NVAPI_OK`, zero frames with anything; the sleep status is `NVAPI_OK` with every field zero. | As the header says. A game that does not use Reflex reads N/A, and the read costs it nothing else. |
|
||||
| M5 | 300 frames with markers, **no sleep mode set**: sixty-four frames, the newest one or two ids behind the last frame drawn. Per frame the driver fills simulation end, render submit start/end, present start/end, driver end, OS queue start/end and GPU start/end; `inputSampleTime` and `driverStartTime` stay zero (the probe sets no input marker). | **Readable by a third party in the process, from markers alone.** |
|
||||
| M6 | 2000 calls back to back on the presenting thread: `GetLatency` median **0.50 µs** in the three runs (mean 0.53–0.54, worst 1.2 / 1.5 / 3.0 µs) and **1.50 µs in a fourth**, made that evening after a fix to the probe, with the PC doing other things (mean 1.54, worst 70 µs); `GetSleepStatus` median 0.10 µs in all four, worst 0.7 / 0.8 / 62 / 12 µs. | **Far within NFR-1 once a second**: at 60 presents a second a call may cost 60 µs, and the medians are 0.5–1.5. **Not within it at every present**: the fourth run's median alone is over the microsecond NFR-1 allows a present, and single calls of 62 and 70 µs were seen. Once a second is what is proposed. |
|
||||
| M7 | 60 s, four reads a second from another thread beside the presenting, marker-setting thread, three runs: **228 reads each, none not OK, none faulted, none empty**; worst read 103 / 112 / 248 µs on the polling thread; no marker error. Frames a second beside the poller against alone: −1.3 % (one 60 s leg against one 5 s leg), then in six alternating 10 s legs −1.4 % and −0.6 % — **with single legs between +5.9 % and −9.9 %**. | **No fault: the route does not stop.** The half-percent line cannot be read off this: the loop's own drift from leg to leg is ten times it, in both directions. So a dose was measured instead — next row. |
|
||||
| M7b | The same poller **never pausing**: 38.3 million reads in 30 s (**1.28 million a second**), none not OK, none faulted, worst read 2.7 ms; frames a second −3.3 % (legs −1.1 %, −5.3 %, −3.7 %). | Three hundred thousand times the proposed rate costs about three percent of an uncapped loop. Four reads a second is that divided by 320,000: not measurable, and not half a percent. **The driver also took 38 million reads beside some three million marker calls without an error** — the concurrency §30 could only infer. |
|
||||
| M8 | Direct3D 12: markers set with the **device** — no error; read with the device and read with the queue both return the same sixty-four frames; the sleep status is `NVAPI_OK` with either; markers set with the queue work as well and are read back with the device. | **The device works**, and it is the object the Overlay already holds. |
|
||||
| M9 | `simStartTime` of two neighbouring frames 91 and 43 apart in two runs where the probe measured 81 and 64 µs a frame, and the absolute values are the time of day (1 794 560 148 756 529 on 2026-11-13). | **Microseconds, on the clock of the Unix epoch.** Spans are differences of two of them. |
|
||||
|
||||
**One thing seen that is not understood.** In the first of the three runs the newest frame of the Direct3D 11
|
||||
report had a `presentEndTime` 1 844 674 519 µs — half an hour — after its own `simStartTime`; the other two runs
|
||||
show 36–72 µs there, and the Direct3D 12 reads 46–51 µs every time. The frame was the newest in the report, read
|
||||
within microseconds of being presented. Whatever it was, **the newest frames of a report are not final**: a reader
|
||||
must not take the last few as complete, and must refuse a span that no frame can have.
|
||||
|
||||
### What this settles, and what it does not
|
||||
|
||||
- **Settled, on this driver and this adapter**: the two getters can be found without loading anything and called
|
||||
with a Direct3D 11 device or the Direct3D 12 device the Overlay holds; they do not fault before initialisation,
|
||||
without markers, or beside a thread that sets markers at 16,000 frames a second; a call costs half a microsecond
|
||||
to a microsecond and a half;
|
||||
the report is readable from markers alone and its unit is known. None of §30's stop conditions fired: no fault or
|
||||
hang attributable to the call, no overhead near NFR-1, and the Direct3D 12 device is the one already held.
|
||||
- **Decided by M2 and M6 together**: the call belongs on the **presenting thread, once a second** — a microsecond
|
||||
or so a second, with a worst case seen of 70 µs — not on the watchdog and not on a new thread. So the Disclaimer's "one background thread"
|
||||
would not change; what would change is its list of what the part inside the game does at a present.
|
||||
- **Not settled, because only a game can say**: a game's own device — many threads, deferred contexts, a device a
|
||||
game is about to release; what a real title's report holds (input sample, the GPU times of a real frame, frame
|
||||
generation's `aiFrameTimeUs`); whether a title that uses Reflex through Streamline alone leaves `nvapi64.dll`
|
||||
findable by name (not looked at); a driver other than 32.0.16.2114, and any card but this
|
||||
one; a call that blocks — the stub shows what a block does to its thread, and nothing here made the driver block.
|
||||
- **Not looked into**: Direct3D 11 in the Overlay, which keeps no D3D11 device today (`ResolveApi` releases it):
|
||||
reading there means holding one, a reference the Overlay does not take now; and the incomplete newest frame above.
|
||||
|
||||
### The question for the owner
|
||||
|
||||
**Go to one real title, or stop here?** A go means a plan of its own before any code: the two calls in the present
|
||||
detour once a second, **only while a session asks for Advanced metrics** (D111), only where the game already
|
||||
loaded `nvapi64.dll`, Direct3D 12 first (the device is already held); a place for the numbers — a series beside the
|
||||
frames, since a report arrives after its frame's record is written (§30); `nvapi-readonly-check` extended to the
|
||||
Overlay and taught that `Sleep` is a writer; the Disclaimer's and the Privacy Policy's wording; the first run on a
|
||||
title of the owner's choosing that is not inside the anti-cheat exception's trial (D38), with what each outcome
|
||||
means written before it. A no leaves `nvapi.reflex.*` and `sl.reflex.*` at N/A with the reason, and this note as
|
||||
the record of why it was within reach.
|
||||
|
||||
**Answered 2026-11-13 (owner decision D136): go, to a plan.** The title is Cyberpunk 2077. No code before the plan
|
||||
is approved, and no release that carries the calls before a stop while a game runs has been exercised on
|
||||
0.1.0-beta.46 (owner-only item 44 (d)).
|
||||
|
||||
### The leg with a sleep (owner decision D139) — the table, written before the run
|
||||
|
||||
The plan's review found the largest thing the runs above never touched: **no run set a sleep mode or called
|
||||
`NvAPI_D3D_Sleep`**, and a game that uses Reflex does both, every frame. If the driver makes a getter wait behind
|
||||
the game's sleep, a read on the presenting thread holds a present for as long as the sleep lasts. The owner said:
|
||||
measure it in the probe first (D139). The probe plays the game's part once more — `NvAPI_D3D_SetSleepMode` (low
|
||||
latency on, a minimum interval of 4 166 µs, markers used) and `NvAPI_D3D_Sleep` at the start of every frame, on its
|
||||
own Direct3D 12 device, in its own process. **Both are writes**, as the markers were; no shipped binary contains
|
||||
either, and the sleep mode is switched back off before the device is released.
|
||||
|
||||
| # | What is measured | What it decides |
|
||||
|---|---|---|
|
||||
| S1 | The sleep mode takes: `SetSleepMode` returns OK, the sleep status then reads low-latency on, and a frame takes about the interval | Not OK, or the status does not change → the leg did not exercise a sleep; said so, nothing concluded from S2–S4. |
|
||||
| S2 | The two getters on the thread that sleeps and presents: one `GetLatency` after each of 2000 frames, and 2000 calls back to back | **Median above 60 µs → stop** (NFR-1 at 60 presents a second). **Any call of 2 ms or more → stop**: on a presenting thread that is the latch of D141, in every game that uses Reflex. |
|
||||
| S3 | The getters on **another** thread four times a second for 20 s, and without a pause for 10 s, while the first thread sleeps and presents — against the same two runs on the same device **before** the sleep mode was set | **A fault → stop** (§30). Reads of 2 ms or more that the control does not have → the getter waits behind the sleep: **stop**, and the note says the route reads only games that do not sleep. Reads of 1 ms or more at the same rate as the control → the scheduler, not the sleep. |
|
||||
| S4 | What the report holds once the game sleeps: frames with anything, and the sleep status's fields | Recorded: it is what a real title's report would look like more closely than M5's. An empty report → a sleep mode changes what markers alone gave; recorded, the reader's "nothing reported" covers it. |
|
||||
|
||||
A stop here means no Overlay code is written and the owner is asked again.
|
||||
|
||||
### The leg with a sleep — results
|
||||
|
||||
Three runs of `fl-probe-reflex --real 10` on 2026-11-13 (RTX 5080, driver 32.0.16.2114), the leg after R5.
|
||||
**No stop condition fired.**
|
||||
|
||||
| # | What was seen | Reading |
|
||||
|---|---|---|
|
||||
| S1 | `SetSleepMode` returned OK in all three runs. A frame then took 4 159 µs (the interval asked for is 4 166), 4 037–4 041 of them inside `NvAPI_D3D_Sleep`; no sleep error. The sleep status afterwards: interval 4 166 µs, `bUseGameSleep` 1 — and **`bLowLatencyMode` 0**, although the mode was set with it on. | The sleep was exercised: the thread stood inside it 97 % of the time. **The status's low-latency field is not the flag the game set**, on this driver; why is not known. It is shown as the driver's word, never as "the game switched Reflex on". |
|
||||
| S2 | One `GetLatency` after each of 2000 sleeping frames, on the thread that sleeps and presents: median **2.5 / 2.6 / 2.6 µs**, mean 2.7–2.8, worst 66.9 / 16.8 / 8.0 µs, none of 2 ms. Back to back: median 0.7 µs (worst 10.2 / 81.6 / 4.1); `GetSleepStatus` median 0.2 µs. | Far inside both limits. A read after a frame that slept costs four or five times a read made back to back — a cold cache, by the look of it — and that is the Overlay's case: **about 2.6 µs, once a second**. |
|
||||
| S3 | From another thread while the first slept and presented at 240 frames a second. Four reads a second for 20 s: 80 reads a run, none not OK, none faulted, worst 64 / 82 / 12 µs (the control before the sleep mode: 92 / 209 / 119 µs). Without a pause for 10 s: **10.26 / 10.26 / 10.43 million reads**, none not OK, none faulted, worst 442 / 635 / 286 µs, **none of a millisecond** (the control: 9.97 / 9.94 / 9.89 million, worst 1 605 / 1 390 / 203 µs, one read of a millisecond in two of the three runs). | **The getter does not wait behind the sleep.** Thirty-one million reads were made while another thread was inside the sleep nearly all the time, and none took a millisecond; the slow reads there are belong to the control. |
|
||||
| S4 | The report: sixty-four frames with content. `driverStartTime` is filled in all sixty-four — it was zero in M5, without a sleep mode; `inputSampleTime` in none (the probe sets no input marker). Simulation start to present end 102–151 µs, to GPU end 150–191 µs; `gpuActiveRenderTimeUs` 0. | With a sleep mode the driver span is reported. A reader that treats a zero end point as "span not reported" covers both shapes. |
|
||||
|
||||
**What it does not say**: a game's own sleep, on a game's own threads, with a real frame's work between the sleep
|
||||
and the present; frame generation's pacer; another driver. Those are what the first real title is for (D136).
|
||||
|
||||
### What moving the sequence into the Overlay found (2026-11-13, the same evening)
|
||||
|
||||
The call sequence became `FrameLedger.Overlay/include/fl_reflex.h`, with one check the candidate did not have: that
|
||||
the two addresses the module answers with are code of the module. **Run against the installed driver, that check
|
||||
refused the driver.** `C:\Windows\System32\nvapi64.dll` is a shim: it answers both ids with addresses inside
|
||||
`nvapi64_impl.dll`, in the driver's own store (`…\DriverStore\FileRepository\nv_dispi.inf_amd64_…`), an image of
|
||||
its own. Three consequences, all in the header now:
|
||||
|
||||
- An address is accepted when it is **executable code of an image the process has loaded** — which still refuses
|
||||
the heap, a stack and nowhere — not only when it is inside `nvapi64.dll`.
|
||||
- **A reference is kept on that image too.** The addresses are code only while `nvapi64_impl.dll` stays loaded, and
|
||||
what the shim does with it when a game unloads NVAPI was not looked at.
|
||||
- **The note above was wrong about Control Flow Guard.** It reasoned from `nvapi64.dll`, which is not a CFG image;
|
||||
the code that is called is in `nvapi64_impl.dll`, which is one (`dumpbin`: instrumented, a function table of
|
||||
5 332 entries). The probe enforces CFG and has made the calls from the shipped header, so on this driver the two
|
||||
getters are valid targets. A game that enforces CFG, on a driver the probe was not run against, is not covered:
|
||||
a target that were not valid is a fast-fail no guard catches.
|
||||
|
||||
The stand-in module answers with addresses of its own, which is why the stub leg could not find this; only the
|
||||
real run could. The probe's `--real` now prints the image each address lies in.
|
||||
|
||||
### A run on a busy PC, and what it says about the 2 ms latch (D141)
|
||||
|
||||
The run that confirmed the corrected header (`Resolve` OK, the reads as before) was made while a native build and an
|
||||
injected test ran on the same PC — the probe's own loop made 9 000 frames a second where it had made 16 000. It is
|
||||
the only run so far that was not alone, and it is the nearer one to a game:
|
||||
|
||||
| | Alone (three runs) | Busy (one run) |
|
||||
|---|---|---|
|
||||
| `GetLatency` after a sleeping frame, on the thread that sleeps and presents (2000 reads) | median 2.5–2.6 µs, worst 8–67 µs | median 3.4 µs, worst 130 µs, none of 2 ms |
|
||||
| From another thread without a pause, while the first sleeps: reads of 1 ms or more / of 2 ms or more | 0 / 0 in 10.3 million | **536 / 25 in 2.9 million**, worst 3.5 ms |
|
||||
| The same before the sleep mode was set | 1 / 0 in 9.9 million | 6 / 2 in 3.2 million, worst 2.2 ms |
|
||||
| Four reads a second for 20 s | worst 12–82 µs | worst 110 µs, none of 1 ms |
|
||||
|
||||
**A reading, not a measurement of a game**: a thread that does nothing but call is taken off its processor now and
|
||||
then on a busy PC, and a read that was under way then is as long as the pause. Twenty-five such pauses of 2 ms or
|
||||
more in ten seconds of calling is 2.5 a second; a read of 3 µs made once a second is inside one of them about once
|
||||
in a hundred thousand reads. **So the latch of D141 will, on a busy PC, sometimes switch the read off for a pause
|
||||
that was Windows' and not the driver's** — of the order of a few sessions in a hundred, for sessions of two hours,
|
||||
if a game's presenting thread is paused as often as this probe's poller was; a presenting thread usually is not.
|
||||
The session then says *stopped: slow* with the microseconds, and the next start of the game reads again. That is the
|
||||
trade the owner chose with D141 (one call, not two): it errs towards the game. The number published with the state
|
||||
is what tells the two apart afterwards — a driver that holds a call does it again and for longer; a pause is a few
|
||||
milliseconds, once.
|
||||
|
||||
**The owner was asked again with this table in hand and kept D141 as it is: one call** (2026-11-13).
|
||||
|
||||
### The first real game (2026-11-14, 0.1.0-beta.47, the owner's sessions 208–210)
|
||||
|
||||
Phantom Blade Zero, Direct3D 12, three sessions — frame generation ×3, then off twice. What only a game could say,
|
||||
and now has for one title on this driver:
|
||||
|
||||
- **The game's own device is the one the driver takes**, and `nvapi64.dll` is findable by name in a game that uses
|
||||
Reflex through Streamline: resolved four to five seconds after the attach, the shim in System32 and the getters
|
||||
in `nvapi64_impl.dll`.
|
||||
- **No latch fired in 1 515 seconds of reading**: the slowest call was 24, 20 and 45 µs, under a game's real load
|
||||
and with frame generation's pacer running. The busy-PC reading above put a false latch at a few sessions in a
|
||||
hundred at worst; three sessions cannot confirm or deny that.
|
||||
- **The report is real**: with frame generation ×3 the total is 23 ms; without it, 5.4 ms at 149 presents a second
|
||||
and 15.9 ms at 67. `inputSampleTime` is not read; `driverStartTime` is reported (the driver series has points).
|
||||
- **The sleep status' low-latency switch reads on in a game** (on at times, off at others) — it never did for the
|
||||
probe. And the driver's `fgMultiplier` read 3 in the session FrameLedger measured at ×3.0.
|
||||
- **`gpuRenderStartTime` lies before `simStartTime` in this game**: start to end is 16.4 ms where simulation start
|
||||
to GPU end is 5.4 ms. The span includes whatever the GPU did before this frame's simulation began — it reads
|
||||
like the interval between two frames' GPU ends. The header's `gpuActiveRenderTimeUs` is the active time and is
|
||||
not read by FrameLedger. The probe could not show this: its frames have no GPU work to speak of.
|
||||
|
||||
Not said by these sessions: ~~Cyberpunk 2077 (REDengine's own NVAPI use)~~, a game that enforces Control Flow
|
||||
Guard, another driver, and whether the player feels the read.
|
||||
|
||||
**Cyberpunk 2077, the same morning (sessions 211 and 212).** Frame generation ×2 for 105 s of the first, off in
|
||||
the second at 238 FPS. Read in both; the slowest call 34 and 65 µs; a report in 97 % and 98 % of the samples.
|
||||
|
||||
- **The spans are sane there**: total 11.7 ms at 238 FPS, GPU render 2.7 ms, never longer than the total (0 of
|
||||
429 samples). With frames generated the total is 13.5 ms; in the menus 4.1 ms. So `gpuRenderStartTime` before
|
||||
`simStartTime` is Phantom Blade Zero's, where *GPU render* sits at 16.4 ms whether the game presents 149 or 67
|
||||
times a second.
|
||||
- **`fgMultiplier` read 1 in the session that generated ×2**: the word carries the last value, and the session
|
||||
ended in a menu. The table needs the values seen, not the last one.
|
||||
- **Samples are 1.32 s apart** (the Agent's `t_ms`), reads one second apart: a read is not always the one sampled.
|
||||
- **Left alone as designed**: two Direct3D 11 games (state 1, one line) and a Direct3D 12 game that never loaded
|
||||
`nvapi64.dll` (state 2, said once, asked again each second without a line).
|
||||
|
||||
**The owner's ruling on the span (2026-11-14): read the driver's active time** — `gpuActiveRenderTimeUs`, which
|
||||
the header defines as the same interval "excluding the idles in between", and with it `gpuFrameTimeUs`. Both are
|
||||
members of the report already fetched.
|
||||
+2
-11
@@ -20,7 +20,7 @@ What each part of FrameLedger shows and what each button does. What the numbers
|
||||
update** (it waits while a game is being recorded); and the safety notices — a game's hooking refused, measurement
|
||||
stopped, hooking turned off — each with one button that only says you have read it.
|
||||
|
||||
**The pages** are on the left: **Dashboard**, **Games**, **Compare**, **Logs**, and **Settings** at the bottom. **Advanced** joins them, after Logs, while Advanced metrics is switched on.
|
||||
**The pages** are on the left: **Dashboard**, **Games**, **Compare**, **Logs**, and **Settings** at the bottom.
|
||||
|
||||
## The menus
|
||||
|
||||
@@ -107,7 +107,6 @@ It opens from a session row, from the Dashboard, and from the notice when a sess
|
||||
- **Frame generation in this session** — a bar and a table of every frame-generation state the session held, when it
|
||||
held more than one, with how frame generation was set.
|
||||
- **Tags and notes** with **Save**, and **Export CSV**, **Export JSON**, **Export PNG**.
|
||||
- **Advanced metrics…**, for a session recorded with Advanced metrics on: it opens that session on the Advanced page.
|
||||
|
||||
## Compare
|
||||
|
||||
@@ -121,13 +120,6 @@ not) and **frame generation** — a session you ticked stays in the list. **Clea
|
||||
What FrameLedger and its agent wrote down. Choose **App** or **Agent**, a level, and search; **Pause** stops the view from
|
||||
following new lines. **Open logs folder**, and **Export bug bundle**, which does the same as Help ▸ Report a bug….
|
||||
|
||||
## Advanced
|
||||
|
||||
There only while Settings ▸ Recording ▸ **Advanced metrics** is on. Three tabs: **This PC** — what the graphics
|
||||
driver and the sensors say right now, read only while the page is open; **Session** — what a session recorded with
|
||||
the option on kept, in a table and a chart; **Sources** — every reading FrameLedger knows of, and for each one it
|
||||
does not read, why. [Advanced metrics](12-advanced-metrics.md) describes each.
|
||||
|
||||
## Settings
|
||||
|
||||
Every switch and box is described in [Every setting](08-settings.md).
|
||||
@@ -141,8 +133,7 @@ is ready.
|
||||
|
||||
## Keyboard and mouse
|
||||
|
||||
- **Ctrl+1** … **Ctrl+5** open Dashboard, Games, Compare, Logs and Settings, and put the keyboard in that page;
|
||||
**Ctrl+6** opens Advanced while Advanced metrics is on.
|
||||
- **Ctrl+1** … **Ctrl+5** open Dashboard, Games, Compare, Logs and Settings, and put the keyboard in that page.
|
||||
- **Alt** or **F10** moves to the menus; **Alt** with a menu's underlined letter opens it (**Alt+F**, **Alt+T** and
|
||||
**Alt+H** for File, Tools and Help in English).
|
||||
- **Esc** closes a dialog the way its Close or Cancel button does.
|
||||
|
||||
@@ -20,9 +20,8 @@ The link under them, *Read what the hook does and does not do*, opens the safety
|
||||
| Setting | What it does | Default |
|
||||
|---|---|---|
|
||||
| **Minimum session length (s)** | A shorter session is not kept. 5 to 600 seconds. *Agent.* | 30 |
|
||||
| **Sensor interval (ms)** | How often the PC's sensors are read during a session. 500 to 2000 ms. With a value above 1000, not every reading of NVIDIA's latency report — made about once a second inside the game — becomes a point: each point is still one reading ([Advanced metrics](12-advanced-metrics.md)). *Agent.* | 1000 |
|
||||
| **Sensor interval (ms)** | How often the PC's sensors are read during a session. 500 to 2000 ms. *Agent.* | 1000 |
|
||||
| **Raw series kept per game** | How many of each game's newest sessions keep their per-frame data; older ones keep their statistics. 0 keeps everything. *Agent.* | 20 |
|
||||
| **Advanced metrics** | Reads more from the graphics driver and the hardware sensors during a session — the graphics card's memory and load in detail, each fan and voltage, what your display can do, the driver's settings for the game — and stores it with the session. In a game FrameLedger measures from inside it also reads what the game tells DLSS, Streamline and FSR, and — on an NVIDIA card, in a Direct3D 12 game that uses NVIDIA's library — asks the graphics driver about once a second how long each stage of a frame took ([Advanced metrics](12-advanced-metrics.md)). Off: nothing more is read or stored. It applies from the next session; a session recorded while it was off is not filled in later. While it is on, the **Advanced** page is in the list on the left ([Advanced metrics](12-advanced-metrics.md)). *Agent.* | Off |
|
||||
|
||||
## Data
|
||||
|
||||
@@ -35,7 +34,7 @@ The link under them, *Read what the hook does and does not do*, opens the safety
|
||||
|
||||
| Setting | What it does | Default |
|
||||
|---|---|---|
|
||||
| **Run the agent as administrator** | Lets FrameLedger measure games that run as administrator, and — with PawnIO installed — read CPU temperature and, when *Advanced metrics* is on, the processor's, the memory's and the motherboard's sensors. Windows asks every time the agent starts, at logon too. A warning explains the risk first; read [Limitations](../LIMITATIONS.md#running-the-agent-as-administrator). The agent restarts to apply it, or at its next start if a game is being recorded. | Off |
|
||||
| **Run the agent as administrator** | Lets FrameLedger measure games that run as administrator, and read CPU temperature with PawnIO installed. Windows asks every time the agent starts, at logon too. A warning explains the risk first; read [Limitations](../LIMITATIONS.md#running-the-agent-as-administrator). The agent restarts to apply it, or at its next start if a game is being recorded. | Off |
|
||||
| **Start the agent at logon** | **Register**, **Repair** or **Remove** a task that starts the agent when you log on, for your user only and without administrator rights. Without it, FrameLedger starts the agent when you open it. | Not installed |
|
||||
|
||||
## Appearance
|
||||
|
||||
@@ -32,7 +32,7 @@ While the game runs, a notice may say *hooking refused*.
|
||||
| The game runs in an app container, or Windows protects it in a way the component can neither load into nor hook. | Nothing: an older Microsoft Store app (UWP), or a game under code protection, is recorded, not measured ([Limitations](../LIMITATIONS.md#xbox-app-and-microsoft-store-games)). |
|
||||
| **Disable all hooking** is on. | Switch it off in Settings ▸ Capture. |
|
||||
| The game was already running when FrameLedger was updated. | Close the game and start it again. |
|
||||
| Hooking was switched off after the game crashed twice soon after it started. | Switch it on again in the game's page if the cause may be gone — after a driver update, for example. The count starts again when you do (since 0.1.0-beta.44). |
|
||||
| Hooking was switched off after the game crashed twice soon after it started. | Switch it on again in the game's page if the cause may be gone — after a driver update, for example. |
|
||||
| Hooking was switched off after **Play** started the game directly twice, and each time the game handed itself to Steam or closed at once. | Switch it on again, and set Settings ▸ Games ▸ **Play button** to *Through the store*: some Steam games will not start any other way. |
|
||||
| The game's file is gone. | If only its drive letter changed, FrameLedger follows it within about 15 seconds; otherwise **Change executable…** on the game's page. |
|
||||
| The component could not be loaded into the game. | [Report a problem](#report-a-problem). |
|
||||
|
||||
@@ -1,178 +0,0 @@
|
||||
# Advanced metrics
|
||||
|
||||
A session's summary shows the figures most people want. **Advanced metrics** is for looking closer: everything the
|
||||
graphics driver and the hardware sensors will say about your PC, kept with each session and shown on a page of its
|
||||
own.
|
||||
|
||||
It is **off unless you switch it on**, and while it is off nothing more is read or stored.
|
||||
|
||||
## Switch it on
|
||||
|
||||
Settings ▸ Recording ▸ **Advanced metrics**. A new item, **Advanced**, appears at the end of the list on the left
|
||||
(**Ctrl+6**). Sessions you record from then on keep the extra readings; a session recorded while it was off is not
|
||||
filled in later.
|
||||
|
||||
## This PC
|
||||
|
||||
What your PC says right now.
|
||||
|
||||
- **About this PC** — the graphics card's firmware, architecture and cores, its memory sizes, the driver's package,
|
||||
what each display can do with HDR and variable refresh, and the driver's global settings. A row with a number in
|
||||
brackets unfolds into a list.
|
||||
- **Right now** — every reading with the time it was read at. NVIDIA's own figures are read every second; the
|
||||
sensors (fans, voltages, loads) every five seconds, so a sensor's value can be a few seconds old, and its time
|
||||
says so.
|
||||
- **Over time** — choose a reading and see its last five minutes. More than eight lines at once cannot be told
|
||||
apart, so a reading with many parts (every processor core, say) is drawn as its lowest, average and highest.
|
||||
|
||||
These readings are taken **only while this page is open or a game is being recorded**, and what the page shows is
|
||||
not stored.
|
||||
|
||||
## Session
|
||||
|
||||
Choose a session recorded with Advanced metrics on. You see the PC as it was then, what belonged to that session
|
||||
alone — whether variable refresh was in use on the display the game ran on, the colour space the game presented in,
|
||||
the driver's settings for that game — the lowest, average and highest of every reading, and a chart over the
|
||||
session's length.
|
||||
|
||||
### What the game told its upscaler
|
||||
|
||||
For a game FrameLedger measures **from inside** (hooking is on for it), a session recorded with Advanced metrics on
|
||||
also keeps what the game itself handed to DLSS and FSR:
|
||||
|
||||
- **DLSS** — the output size, the model preset for each quality mode, whether the game said its colour buffers are
|
||||
HDR, auto-exposure, alpha upscaling, and the exposure values.
|
||||
- **FSR** — sharpening (on or off, and how strong), the largest jitter offset, the exposure, the near and far planes,
|
||||
the **range** of the field of view over the session, the flags of the call, the frame time the game reported, and
|
||||
FSR's own video memory at the moments the game asked for it.
|
||||
- **Streamline** (NVIDIA's library that games use for DLSS; since 0.1.0-beta.43) — what the game tells it about
|
||||
each frame: the largest jitter offset, the motion-vector scale and how the motion vectors are stored, the near and
|
||||
far planes and whether depth is inverted, the **range** of the field of view, the aspect ratio, whether the
|
||||
projection is orthographic, and how many times the game reset the upscaler's history (a camera cut, a loading
|
||||
screen). Where a game draws several views, these are the first view's.
|
||||
- **FSR frame generation** (since 0.1.0-beta.43) — how the game configured it: on or off, whether it may run
|
||||
asynchronously, its flags, whether only generated frames are presented, and the part of the picture it generates
|
||||
in. A setting the game changed during the session reads *on and off*. This is what the game **asked for**; how
|
||||
many frames were generated is in the session's summary, as before.
|
||||
|
||||
- **Streamline's features** (since 0.1.0-beta.44) — what Streamline answered when the game asked about a feature:
|
||||
which version it is (Streamline's own, and the DLSS model's), and what it requires — the graphics APIs it works
|
||||
with, whether V-Sync must be off, whether hardware-accelerated GPU scheduling must be on, how many threads,
|
||||
viewports and buffers, and the Windows and driver versions Streamline found beside the ones the feature needs.
|
||||
The features carry NVIDIA's own names: `kFeatureDLSS` is DLSS, `kFeatureDLSS_G` DLSS frame generation,
|
||||
`kFeatureDLSS_RR` ray reconstruction, `kFeatureReflex` Reflex. A game asks these while it starts; many ask
|
||||
again later, and then they are read. Where a game asks only at its start, the line under the session says
|
||||
*hooked — the game asks this while it starts, and did not ask again*. The version shown is the one Streamline
|
||||
reports, which can be newer than the file in the game's folder.
|
||||
- **Whether a feature is supported and loaded, and what the game did with it** (since 0.1.0-beta.45) — two more
|
||||
tables, one row for each feature and call. `kFeatureDLSS_G · slIsFeatureSupported` is Streamline's answer in
|
||||
NVIDIA's own word: `eOk` is yes, and a refusal is named (`eErrorFeatureNotSupported`, `eErrorFeatureMissing`).
|
||||
`· slIsFeatureLoaded` is *on* or *off*. `· slSetFeatureLoaded` says whether the game switched the feature *on*,
|
||||
*off* or *on and off* during the session; `· slAllocateResources` and `· slFreeResources` count how many times it
|
||||
set up and released what the feature needs (up to 15, then `≥ 15`); `slShutdown` counts how many times it shut
|
||||
Streamline down. These begin when FrameLedger is in the game: what the game did while it started is not there.
|
||||
In the games run so far every one asks whether its features are supported; the other rows appear in some games
|
||||
and not in others, and no game has shown an allocation.
|
||||
|
||||
These are the game's own words to the upscaler, shown in the vendor's notation (`preExposure`, preset `K`).
|
||||
FrameLedger does not check what the upscaler did with them.
|
||||
|
||||
The last four are read from calls FrameLedger hooks **only for Advanced metrics** — ten calls in all: in a game
|
||||
where no session has been recorded with the option on since it started, those hooks are not there. The line under
|
||||
the session says, for each call, whether it was *read*, *hooked — the game did not make the call*, or *not hooked —
|
||||
the game did not load the library that has the call*; the six calls of 0.1.0-beta.45 are named in one sentence,
|
||||
under which of the three happened to each.
|
||||
|
||||
### What NVIDIA's driver says about each frame's stages
|
||||
|
||||
On an NVIDIA card, in a **Direct3D 12** game that has **NVIDIA Reflex** built in, a session with Advanced metrics
|
||||
on also stores the driver's own latency report — whether Reflex is on or off in the game's menu, because a game
|
||||
with Reflex marks its frames either way: how long the driver says each stage of a frame took — *simulation*,
|
||||
*render submit*, *present*, *driver*, *operating system's render queue*, *GPU render*, and the *total* from the start
|
||||
of simulation to the end of the graphics card's work. They are seven lines under **Latency**, one point about every
|
||||
second, each the average of the frames of one reading, in microseconds. A table beside them shows the driver's
|
||||
low-latency state as five switches, by NVIDIA's own names, each *On*, *Off* or *On at times, off at others*, and
|
||||
`fgMultiplier`: every frame-generation multiplier the driver gave during the session (*1, 2* is a session that
|
||||
generated frames at ×2 for part of it). **They are the driver's switches, not the game's menu.** `bLowLatencyMode`
|
||||
is on when the game switched Reflex on *and* when **Low Latency Mode** is set for that game in the NVIDIA App —
|
||||
an override there shows here, and can read *On at times, off at others* in a game whose own setting never
|
||||
changed. `bUseGameSleep` says whether the game calls Reflex's sleep each frame. NVIDIA asks games to call it even
|
||||
while Reflex is off, so *On* there does not say Reflex is on — `bLowLatencyMode` does; some games call it only
|
||||
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* 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:
|
||||
|
||||
- **They are the driver's numbers, not FrameLedger's.** FrameLedger does not measure these stages; it stores what
|
||||
the driver reports and has not checked it against another tool. They are not the delay from a click to the screen.
|
||||
- **FrameLedger asks for them from inside the game**, about once a second — the one thing it does in a game that is
|
||||
not reading what the game itself passes along. It asks only through NVIDIA's library where the game had already
|
||||
loaded it, and never loads that library itself. A copy of the library sitting in the game's own folder (some
|
||||
mods put one there) is not the driver's, and FrameLedger does not use it.
|
||||
- **It switches itself off rather than disturb the game.** If one request takes two thousandths of a second or
|
||||
more, or goes wrong, FrameLedger makes no further request until the game is closed. The line under the session
|
||||
then says *stopped*, and why; the next time the game starts it reads again. On a busy PC this can happen for a
|
||||
pause that was Windows' and not the driver's.
|
||||
|
||||
The line under the session says what happened: *read*; *asked, and the driver reported no frame* (the game does not
|
||||
use Reflex); *not read* with the reason — the game does not present through Direct3D 12, it has not loaded NVIDIA's
|
||||
library, or that library is in the game's own folder; or *stopped*.
|
||||
|
||||
**Many games will show nothing here**, and the line under the session says why: *the game made none of the calls
|
||||
these are read from* — most games set their DLSS options through a call FrameLedger cannot see, and only games that
|
||||
use FSR 3.1 or later through AMD's own library show the FSR rows — or *the session was not measured inside the game*.
|
||||
It never means the game uses no upscaler; the session's summary still names the upscaler as before.
|
||||
|
||||
**Where the camera is, which way it looks and its matrices are never read.** The field of view is kept as a lowest
|
||||
and a highest value, never as a line over time.
|
||||
|
||||
**A game may use a unit of its own.** NVIDIA's and AMD's libraries expect the field of view in radians, and
|
||||
FrameLedger shows it that way with the degrees beside it. Some games give degrees instead (Cyberpunk 2077 does, to
|
||||
Streamline): a value too large to be radians is shown as the game gave it, with a line that says *Not radians*, and
|
||||
is not converted — FrameLedger shows what the game said, not what it may have meant. The number of **resets** is
|
||||
the number of calls in which the game told the upscaler to drop its history; menus and loading screens raise it. A
|
||||
frame-generation configuration with no flag set says *None*.
|
||||
|
||||
A session's summary has an **Advanced metrics…** button that opens that session here.
|
||||
|
||||
## Sources
|
||||
|
||||
Every reading FrameLedger knows of, with what it belongs to (this PC, a session, or a session over time), where it
|
||||
comes from, and whether it is read. Where it is not, the reason is written out:
|
||||
|
||||
- **the capture agent is not running as administrator**, or **PawnIO is not installed** — the processor's, the
|
||||
memory's and the motherboard's sensors need both ([Every setting](08-settings.md), *Run the agent as
|
||||
administrator*);
|
||||
- **not present on this PC** — the driver's own figures exist on NVIDIA cards only;
|
||||
- **read inside a game FrameLedger measures, when the game makes the call** — what the game tells DLSS and FSR
|
||||
(above);
|
||||
- **read inside a game FrameLedger measures, from the graphics driver** — NVIDIA's latency report (above);
|
||||
- **not read: it would take a patch at an address found while the game runs, a function of FrameLedger's handed
|
||||
to the game in place of the vendor's, or a call the vendor forbids from outside the game's own threads** — what
|
||||
the game asked of Reflex, Reflex's state through Streamline, and what a game sets and asks through Streamline's
|
||||
own functions for a feature: DLSS frame generation's options and state, the video memory DLSS estimates for
|
||||
itself, and the options of ray reconstruction, Image Scaling and Dynamic Vibrance. No later release will read
|
||||
these;
|
||||
- **the game makes this call once, before FrameLedger is inside it** — what the game started Streamline with. It is
|
||||
not read, and no later release will read it;
|
||||
- **never read** — a serial number, a display's identification data, which other programs are encoding, the camera's
|
||||
position in the game. FrameLedger does not read these at all.
|
||||
|
||||
## Good to know
|
||||
|
||||
- A reading that could not be taken is **N/A**, never a guess and never a zero.
|
||||
- **A drive's temperature is not read**: the sensor library cannot list drives without touching removable ones.
|
||||
- None of these readings has been checked against another tool yet.
|
||||
- They are not part of an exported session or a bug report.
|
||||
|
||||
More limits are on the [Limitations](../LIMITATIONS.md) page, under *Sensors*.
|
||||
+2
-3
@@ -4,7 +4,7 @@ FrameLedger records how your games run on this PC — frame rate, frame times, t
|
||||
with, temperatures, and how much memory the game uses — and keeps every session so you can compare them later.
|
||||
Everything stays on your PC.
|
||||
|
||||
Each page below takes a minute or two to read. The first six are the guide; the next six are there to look things up.
|
||||
Each page below takes a minute or two to read. The first six are the guide; the next five are there to look things up.
|
||||
|
||||
1. [Install and first start](01-install.md)
|
||||
2. [Record a game](02-record-a-game.md)
|
||||
@@ -17,8 +17,7 @@ Each page below takes a minute or two to read. The first six are the guide; the
|
||||
9. [When something goes wrong](09-troubleshooting.md)
|
||||
10. [Words FrameLedger uses](10-glossary.md)
|
||||
11. [Alpha builds](11-alpha-builds.md) — the experimental builds on a new .NET, and how to go back
|
||||
12. [Advanced metrics](12-advanced-metrics.md) — everything the driver and the sensors say, if you switch it on
|
||||
13. [The terms, in plain words](terms-in-plain-words.md)
|
||||
12. [The terms, in plain words](terms-in-plain-words.md)
|
||||
|
||||
What FrameLedger cannot do is listed on its own page: [Limitations](../LIMITATIONS.md) (in the app: Help ▸
|
||||
Limitations). How it works with the keyboard alone, a screen reader or a contrast theme, and how to report a problem:
|
||||
|
||||
+3
-40
@@ -11,8 +11,8 @@
|
||||
that changes what FrameLedger.Overlay or the capture host does; date the change.
|
||||
HTML comments are not part of the block.
|
||||
-->
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-11-11.** The software is a beta; its latest
|
||||
> **beta is `0.1.0-beta.49`** (2026-11-14), an unsigned installer built from that tag with its
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-11-06.** The software is a beta; its latest
|
||||
> **beta is `0.1.0-beta.37`** (2026-11-11), an unsigned installer built from that tag with its
|
||||
> checksums published beside it (alphas — experimental builds that try a newer .NET — are published apart). The source holds the desktop app
|
||||
> (library, store import, charts, settings) and the background Agent, which records a session when a
|
||||
> game in the library runs (unless you switched its recording off), injects only into games you enabled
|
||||
@@ -86,18 +86,8 @@
|
||||
> mean, median and peak. The game's other processes (launchers, helpers) are not counted.
|
||||
> - **Video memory:** in use on the whole graphics card, recorded from Windows and GPU-driver telemetry
|
||||
> and charted. **Not measured at all:** the video-memory budget Windows gives a game, which frame
|
||||
> spikes were shader compilation, end-to-end PC latency, and HDR. Stutter count and stutter time are
|
||||
> spikes were shader compilation, PC latency (Reflex), and HDR. Stutter count and stutter time are
|
||||
> measured from frame times.
|
||||
> - **NVIDIA's latency report (only with Advanced metrics on; Direct3D 12; a game that uses NVIDIA Reflex):** how
|
||||
> long the driver says each stage of a frame took — simulation, render submit, present, driver, the operating
|
||||
> system's queue, the graphics card — read from the graphics driver about once a second and shown as the driver
|
||||
> reported it: **the driver's numbers, not a measurement by FrameLedger**, an average of the frames of one read,
|
||||
> never checked against another tool, and not the delay from a click to the screen. **The stages overlap and do
|
||||
> not add up to the total.** The graphics card's stage runs from its start to its end and includes the time the
|
||||
> card waited — in one game it was longer than the whole frame — so since beta.48 two figures the driver works
|
||||
> out itself are shown beside it: the card's active time, and the time from one frame's end to the next. A
|
||||
> driver may give neither, and then there is no line. Read in two real games, on one driver and one card
|
||||
> (2026-11-14). A game that does not use Reflex has none. The session summary's latency fields stay N/A.
|
||||
> - **Pacing, VSync and the graphics card (since beta.14):** the share of the time below 30 FPS, below 60 FPS and below
|
||||
> the monitor's refresh rate, measured from frame times with small margins so that a game held at its limit is not
|
||||
> counted as below it (a rate less than 2 % under the line reads partly as at it), and how much one frame's time
|
||||
@@ -111,33 +101,6 @@
|
||||
> Windows once a second and charted. Processor temperature is read only when the Agent runs as
|
||||
> administrator — an option, off by default, for which Windows asks at every start of the Agent — with
|
||||
> PawnIO installed, and that reading has not yet been checked on real hardware; everywhere else it is `N/A`.
|
||||
> - **Advanced metrics (since beta.39; off unless you switch it on in Settings):** with it on, a session also stores
|
||||
> what the graphics driver and the sensor library report about the hardware — the graphics card's memory, load,
|
||||
> clocks, fans, voltages and power in detail, what a display can do, the driver's settings for the game — as they
|
||||
> report it: NVIDIA's figures once a second, the sensor library's every five seconds. None of these readings has
|
||||
> been checked against another tool. The processor's, the memory's and the motherboard's need the Agent as
|
||||
> administrator with PawnIO and have never been read on real hardware; a drive's temperature is not read. The
|
||||
> Advanced page shows them as they were stored, and what the PC reads at the moment only while that page is open.
|
||||
> - **What a game tells its upscaler (since beta.40; only with Advanced metrics on, only for a game measured from
|
||||
> inside):** the output size, presets and exposure a game hands DLSS, and the sharpening, jitter, exposure, depth
|
||||
> range, field-of-view range, flags and frame time it hands FSR, are read from the arguments of the calls
|
||||
> FrameLedger intercepts and shown as the game stated them — not checked against what the upscaler did. Most games
|
||||
> set their DLSS options through a call that cannot be intercepted and show none; the FSR values need FSR 3.1 or
|
||||
> later through AMD's own library. Since beta.43 also what a game tells NVIDIA Streamline about each frame (jitter,
|
||||
> motion-vector scale, depth range, field-of-view range, how often it reset the upscaler's history — for the first
|
||||
> viewport that called, where a game has several) and how it configures FSR frame generation (the settings it asked
|
||||
> for, not whether frames were generated). Since beta.44 also what Streamline answers when a game asks about a
|
||||
> feature — its version, and what it requires (graphics APIs, V-Sync, GPU scheduling, Windows and driver versions):
|
||||
> Streamline's answer as the game received it, not a check of the PC. A game that asks only while it starts has
|
||||
> none and the session says so; the Unreal Engine games run so far ask again later, and were read. Since beta.45
|
||||
> also whether Streamline says each feature is supported and whether it is loaded, and what the game did with it
|
||||
> after FrameLedger attached — switched it on or off, allocated and freed its resources (counted to fifteen), shut
|
||||
> Streamline down: calls the game made, not a statement that a feature ran or produced anything. FSR's upscaling
|
||||
> values, Streamline's constants (seven games), its answers about a feature (seven games), the
|
||||
> frame-generation configuration (one game) and five of beta.45's six calls (five games) have been read from
|
||||
> real games; no game run so far allocated a feature's resources after FrameLedger attached, and the DLSS
|
||||
> options have not been confirmed on one yet. A game may give a value in a unit of its own: one gives
|
||||
> Streamline its field of view in degrees, and it is shown as given.
|
||||
> - **Safety:** every pre-injection check runs before injection, including the signed-by-a-known-vendor
|
||||
> half of the suspicious-module rule. During every capture the Agent re-runs the checks every 30 s and
|
||||
> stops capturing on a refusal: a Direct3D or OpenGL game's hooks are removed, and the Vulkan layer
|
||||
|
||||
+9
-51
@@ -1,6 +1,6 @@
|
||||
# FrameLedger — Disclaimer
|
||||
|
||||
**Version:** 2.17 · **Effective:** {{RELEASE_DATE}}
|
||||
**Version:** 2.14 · **Effective:** {{RELEASE_DATE}}
|
||||
|
||||
## 0. This is pre-release software
|
||||
|
||||
@@ -43,11 +43,11 @@ Be precise about what that does and does not promise, because the shorter versio
|
||||
|
||||
Install it somewhere only you can write to, and verify the published SHA-256 checksums.
|
||||
|
||||
**What it observes inside the game:** arguments the game passes to graphics APIs we intercept (presentation, upscaling, ray tracing, pipeline creation) — and, only while Advanced metrics is on, one thing that is not an argument: the graphics driver's own report of how long the stages of the game's last frames took, which the component asks NVIDIA's driver for itself (§2 says exactly how).
|
||||
**What it observes inside the game:** arguments the game passes to graphics APIs we intercept (presentation, upscaling, ray tracing, pipeline creation).
|
||||
|
||||
**What it reads about the game from outside it, in every session:** the game process's own memory use — its dedicated and shared video memory and its working sets, the figures Windows' Task Manager shows — from Windows' performance counters and process-memory information. For a game it does not inject into, FrameLedger opens the game's process for this with the least access Windows offers, once a second, and closes it again; it reads nothing inside the process.
|
||||
|
||||
> **What of that list is observed today is stated once, in §4 below** (the block `legal/ACCURACY.md` carries, dated). The list here describes what the software is designed to observe, and the boundary — API arguments, and the one report asked of the graphics driver that the line above names; nothing of the game's own memory — holds for all of it.
|
||||
> **What of that list is observed today is stated once, in §4 below** (the block `legal/ACCURACY.md` carries, dated). The list here describes what the software is designed to observe, and the boundary — API arguments and nothing else — holds for all of it.
|
||||
|
||||
**What it never does:** read or write the game's memory outside those API arguments; read save files, input, chat, or network traffic; modify game behavior; hide itself from any security software; or install a kernel driver of its own.
|
||||
|
||||
@@ -72,11 +72,7 @@ FrameLedger is designed to reduce that risk substantially:
|
||||
the game exits.
|
||||
- FrameLedger contains **no evasion techniques of any kind** — it does not hide, rename, obfuscate, or disguise itself. It is intended to be plainly identifiable to any security software that looks.
|
||||
|
||||
For completeness about what it *does* run inside the game: besides the intercepted calls themselves, the component starts **one background thread**. It wakes once a second, or when the game loads a library, and then: checks FrameLedger's own shared memory for a request to stop and for the heartbeat of the safety scan described above; asks Windows, by name, whether the graphics, upscaling and frame-generation libraries it knows about are loaded, and puts its interception into the ones that are (for ray tracing it creates one command list on the game's own Direct3D 12 device, to find the functions to intercept); writes its counters to FrameLedger's shared memory; and writes FrameLedger's own log file.
|
||||
|
||||
**One call it makes itself, into the graphics driver — only while Advanced metrics is on.** In a Direct3D 12 game that had already loaded NVIDIA's driver library (`nvapi64.dll`), the component asks that library — by name, among what the game loaded; it never loads it — for two of the driver's read-only functions, and keeps the library and the driver file those functions are in from being unloaded for as long as the game runs. Then, about once a second, **on the game's own thread that presents its frames**, right after a frame has been handed over, it calls them: one returns the driver's report of how long the stages of the last frames took, the other the driver's low-latency state. It calls no function that sets, marks or delays anything. A library of that name sitting in the game's own folder is not the driver's and is not called. What this costs the game is the length of that call, once a second — a few millionths of a second where it was measured. A call that faults is caught, counted once, and not repeated; a call that takes two thousandths of a second or more is the last one until the game is closed. **A call that never returns would hold the game's presenting thread, and FrameLedger cannot stop it** — it has not happened in any test, and it is said here because it is the one thing in this component whose length FrameLedger's own code does not bound. With Advanced metrics off — the default — none of this happens.
|
||||
|
||||
It does not scan the game's memory, list the modules or processes on the system, or query Windows services — deliberately, because software that does those things from inside a game process looks like the thing this tool is trying not to be mistaken for.
|
||||
For completeness about what it *does* run inside the game: besides the intercepted calls themselves, the component starts **one background thread**. It wakes once a second, or when the game loads a library, and then: checks FrameLedger's own shared memory for a request to stop and for the heartbeat of the safety scan described above; asks Windows, by name, whether the graphics, upscaling and frame-generation libraries it knows about are loaded, and puts its interception into the ones that are (for ray tracing it creates one command list on the game's own Direct3D 12 device, to find the functions to intercept); writes its counters to FrameLedger's shared memory; and writes FrameLedger's own log file. It does not scan the game's memory, list the modules or processes on the system, or query Windows services — deliberately, because software that does those things from inside a game process looks like the thing this tool is trying not to be mistaken for.
|
||||
- FrameLedger injects into a game only after you enable that game individually. For every other game — and for any game where the safety checks refuse — it records the session's start, end and duration together with whatever hardware sensor readings your machine provides and the game's own memory use as Windows reports it (§1), and reports every other measurement as not available. **There is no measurement mode that works without injecting**; an earlier version of this document described one, and it was never built. FrameLedger never estimates a value it could not measure, and it always shows which of the two modes produced a session. Neither mode requires administrator rights.
|
||||
|
||||
**However, these protections cannot be complete:**
|
||||
@@ -124,8 +120,8 @@ Software running inside another process can, in principle, destabilize it. Frame
|
||||
Frame timing is derived from high-resolution timestamps taken at the moment the game presents each frame; upscaling, frame-generation and ray-tracing state are read from the parameters the game passes to those APIs. This is substantially more accurate than inferring settings from files on disk, but **no measurement is guaranteed to be exact**:
|
||||
|
||||
<!-- accuracy-block:begin -->
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-11-11.** The software is a beta; its latest
|
||||
> **beta is `0.1.0-beta.49`** (2026-11-14), an unsigned installer built from that tag with its
|
||||
> ⚠ **What FrameLedger actually measures today — 2026-11-06.** The software is a beta; its latest
|
||||
> **beta is `0.1.0-beta.37`** (2026-11-11), an unsigned installer built from that tag with its
|
||||
> checksums published beside it (alphas — experimental builds that try a newer .NET — are published apart). The source holds the desktop app
|
||||
> (library, store import, charts, settings) and the background Agent, which records a session when a
|
||||
> game in the library runs (unless you switched its recording off), injects only into games you enabled
|
||||
@@ -199,18 +195,8 @@ Frame timing is derived from high-resolution timestamps taken at the moment the
|
||||
> mean, median and peak. The game's other processes (launchers, helpers) are not counted.
|
||||
> - **Video memory:** in use on the whole graphics card, recorded from Windows and GPU-driver telemetry
|
||||
> and charted. **Not measured at all:** the video-memory budget Windows gives a game, which frame
|
||||
> spikes were shader compilation, end-to-end PC latency, and HDR. Stutter count and stutter time are
|
||||
> spikes were shader compilation, PC latency (Reflex), and HDR. Stutter count and stutter time are
|
||||
> measured from frame times.
|
||||
> - **NVIDIA's latency report (only with Advanced metrics on; Direct3D 12; a game that uses NVIDIA Reflex):** how
|
||||
> long the driver says each stage of a frame took — simulation, render submit, present, driver, the operating
|
||||
> system's queue, the graphics card — read from the graphics driver about once a second and shown as the driver
|
||||
> reported it: **the driver's numbers, not a measurement by FrameLedger**, an average of the frames of one read,
|
||||
> never checked against another tool, and not the delay from a click to the screen. **The stages overlap and do
|
||||
> not add up to the total.** The graphics card's stage runs from its start to its end and includes the time the
|
||||
> card waited — in one game it was longer than the whole frame — so since beta.48 two figures the driver works
|
||||
> out itself are shown beside it: the card's active time, and the time from one frame's end to the next. A
|
||||
> driver may give neither, and then there is no line. Read in two real games, on one driver and one card
|
||||
> (2026-11-14). A game that does not use Reflex has none. The session summary's latency fields stay N/A.
|
||||
> - **Pacing, VSync and the graphics card (since beta.14):** the share of the time below 30 FPS, below 60 FPS and below
|
||||
> the monitor's refresh rate, measured from frame times with small margins so that a game held at its limit is not
|
||||
> counted as below it (a rate less than 2 % under the line reads partly as at it), and how much one frame's time
|
||||
@@ -224,33 +210,6 @@ Frame timing is derived from high-resolution timestamps taken at the moment the
|
||||
> Windows once a second and charted. Processor temperature is read only when the Agent runs as
|
||||
> administrator — an option, off by default, for which Windows asks at every start of the Agent — with
|
||||
> PawnIO installed, and that reading has not yet been checked on real hardware; everywhere else it is `N/A`.
|
||||
> - **Advanced metrics (since beta.39; off unless you switch it on in Settings):** with it on, a session also stores
|
||||
> what the graphics driver and the sensor library report about the hardware — the graphics card's memory, load,
|
||||
> clocks, fans, voltages and power in detail, what a display can do, the driver's settings for the game — as they
|
||||
> report it: NVIDIA's figures once a second, the sensor library's every five seconds. None of these readings has
|
||||
> been checked against another tool. The processor's, the memory's and the motherboard's need the Agent as
|
||||
> administrator with PawnIO and have never been read on real hardware; a drive's temperature is not read. The
|
||||
> Advanced page shows them as they were stored, and what the PC reads at the moment only while that page is open.
|
||||
> - **What a game tells its upscaler (since beta.40; only with Advanced metrics on, only for a game measured from
|
||||
> inside):** the output size, presets and exposure a game hands DLSS, and the sharpening, jitter, exposure, depth
|
||||
> range, field-of-view range, flags and frame time it hands FSR, are read from the arguments of the calls
|
||||
> FrameLedger intercepts and shown as the game stated them — not checked against what the upscaler did. Most games
|
||||
> set their DLSS options through a call that cannot be intercepted and show none; the FSR values need FSR 3.1 or
|
||||
> later through AMD's own library. Since beta.43 also what a game tells NVIDIA Streamline about each frame (jitter,
|
||||
> motion-vector scale, depth range, field-of-view range, how often it reset the upscaler's history — for the first
|
||||
> viewport that called, where a game has several) and how it configures FSR frame generation (the settings it asked
|
||||
> for, not whether frames were generated). Since beta.44 also what Streamline answers when a game asks about a
|
||||
> feature — its version, and what it requires (graphics APIs, V-Sync, GPU scheduling, Windows and driver versions):
|
||||
> Streamline's answer as the game received it, not a check of the PC. A game that asks only while it starts has
|
||||
> none and the session says so; the Unreal Engine games run so far ask again later, and were read. Since beta.45
|
||||
> also whether Streamline says each feature is supported and whether it is loaded, and what the game did with it
|
||||
> after FrameLedger attached — switched it on or off, allocated and freed its resources (counted to fifteen), shut
|
||||
> Streamline down: calls the game made, not a statement that a feature ran or produced anything. FSR's upscaling
|
||||
> values, Streamline's constants (seven games), its answers about a feature (seven games), the
|
||||
> frame-generation configuration (one game) and five of beta.45's six calls (five games) have been read from
|
||||
> real games; no game run so far allocated a feature's resources after FrameLedger attached, and the DLSS
|
||||
> options have not been confirmed on one yet. A game may give a value in a unit of its own: one gives
|
||||
> Streamline its field of view in degrees, and it is shown as given.
|
||||
> - **Safety:** every pre-injection check runs before injection, including the signed-by-a-known-vendor
|
||||
> half of the suspicious-module rule. During every capture the Agent re-runs the checks every 30 s and
|
||||
> stops capturing on a refusal: a Direct3D or OpenGL game's hooks are removed, and the Vulkan layer
|
||||
@@ -292,15 +251,14 @@ be the difference between a game that runs and one that does not. Turn hooking o
|
||||
|
||||
## 5. Hardware and drivers
|
||||
|
||||
FrameLedger reads GPU telemetry through vendor libraries that ship with your graphics driver. It **only reads** — it never changes clocks, fan curves, power limits, or any other hardware setting. Optional CPU-temperature support — and, with Advanced metrics on, reading the processor's, the memory's and the motherboard's sensors — relies on the separate third-party **PawnIO** driver, which you install at your own discretion under its own license; some anti-cheat systems object to third-party kernel drivers regardless of what they are used for.
|
||||
FrameLedger reads GPU telemetry through vendor libraries that ship with your graphics driver. It **only reads** — it never changes clocks, fan curves, power limits, or any other hardware setting. Optional CPU-temperature support relies on the separate third-party **PawnIO** driver, which you install at your own discretion under its own license; some anti-cheat systems object to third-party kernel drivers regardless of what they are used for.
|
||||
|
||||
## 5A. Running the capture agent as administrator — optional, and your decision
|
||||
|
||||
Since 0.1.0-beta.10 a Settings option, off unless you turn it on, starts FrameLedger's capture agent as administrator.
|
||||
**Windows asks you every time the agent starts** — also when you sign in — and the prompt names an unknown publisher,
|
||||
because FrameLedger is not code-signed. It lets FrameLedger open and measure a game that itself runs as administrator,
|
||||
and read the CPU temperature — and, with Advanced metrics on, the processor's, the memory's and the motherboard's
|
||||
sensors — where PawnIO is installed. It changes nothing in the anti-cheat guard (§2, §2A), opens no
|
||||
and read the CPU temperature where PawnIO is installed. It changes nothing in the anti-cheat guard (§2, §2A), opens no
|
||||
process that Windows or an anti-cheat driver protects, and never starts a game as administrator: games you start from
|
||||
FrameLedger run with your standard rights.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# FrameLedger — Privacy Policy
|
||||
|
||||
**Version:** 2.21 · **Effective:** {{RELEASE_DATE}}
|
||||
**Version:** 2.14 · **Effective:** {{RELEASE_DATE}}
|
||||
|
||||
**Short version: everything stays on your PC. FrameLedger has no accounts, no telemetry, no analytics, and never uploads your data anywhere.**
|
||||
|
||||
@@ -11,7 +11,6 @@ Stored in `%LOCALAPPDATA%\FrameLedger` on your device:
|
||||
- Your game library entries (names, executable paths, metadata you or the app filled in, and whether each one is recorded).
|
||||
- Images you choose for a game (Edit…), copied into the `covers` folder; choosing the store's image again, or removing the game together with its sessions, deletes the copy. Artwork a store's app keeps on your PC, or a game ships in its own folder, is shown from where it is and not copied.
|
||||
- Performance sessions: frame timing series, computed statistics, hardware sensor series (temperatures, load, power, memory usage, and the graphics card's clock speeds, fan speed, memory temperature and whether its power limit or heat held it back), the game's own memory use (its dedicated and shared video memory, private working set, working set and commit, once a second), session duration, crash flags, the graphics driver's settings the game ran under (NVIDIA only), how the game's window was shown (full-screen, borderless or windowed, for how long, its size and the monitor's), tags and notes you write.
|
||||
- **Only while Settings ▸ Advanced metrics is on** (it is off unless you switch it on), with each session: more hardware sensor series — the graphics card's memory use in detail, its load by part, its clocks, voltages, currents, power, each fan and its video encoder's use; and, when the capture agent runs as administrator with PawnIO installed, the processor's temperatures, load, clocks, power and voltages by core, the memory in use and its modules' temperatures, and the motherboard's temperatures, fans and voltages — and a description of the hardware: the graphics card's firmware version, architecture, bus and memory sizes, the graphics driver's package and the chipset it names, the motherboard's and the memory modules' model names, what each connected display can do (the HDR formats it accepts, its brightness range, variable refresh), whether variable refresh was in use on the display the game ran on and the colour space the game presented in, and the graphics driver's settings — its global ones and the ones it holds for the game (NVIDIA only). For a game FrameLedger injects into, a session then also stores what the game itself passed to its upscaler in the calls FrameLedger intercepts: the output size, the model presets and the exposure values it gave DLSS, whether it said its colour buffers are HDR, auto-exposure and alpha upscaling; and the sharpening, the size of the jitter, the exposure, the depth range, the lowest and highest field of view and the flags it gave FSR, the frame time it reported to FSR, and FSR's own video memory when the game asked for it; what the game told NVIDIA Streamline about each frame — the size of the jitter, the motion-vector scale, the depth range and whether depth is inverted, the lowest and highest field of view, the aspect ratio, whether the projection is orthographic, how its motion vectors are stored and how often it reset the upscaler's history; and how it configured FSR frame generation — on or off, whether it may run asynchronously, its flags, whether only generated frames are presented, and the rectangle it generates in; and what NVIDIA Streamline answered when the game asked it about a feature — which features the game asked about, the version of each and of its NGX model, and what each requires: the graphics APIs it supports, whether V-Sync must be off and hardware-accelerated GPU scheduling on, how many processor threads, viewports and buffers, and the versions of Windows and of the graphics driver that Streamline found beside the ones the feature needs ; and, for each Streamline feature the game asks about or controls: whether Streamline answers that it is supported, whether it is loaded, whether the game switched it on or off while it ran, and how many times its resources were allocated and freed; and whether the game shut Streamline down, and how many times — never the lists Streamline's answer points to (the buffers' names, the names of Vulkan extensions and features), never what identifies the graphics card that the game hands over with its question, never the content of a graphics resource, and never where the game's camera is, which way it looks, or its matrices. For a Direct3D 12 game that had itself loaded NVIDIA's driver library, a session also stores what the graphics driver reports about the game's frames when FrameLedger asks it, about once a second, from inside the game: how long each stage of a frame took — simulation, render submit, present, the driver, the operating system's queue and the graphics card, and the whole from the start of simulation to the end of the graphics card's work — as averages in microseconds, with two figures the driver works out itself (how long the graphics card was actually at work on a frame, and the time from the end of one frame's work to the end of the next), and the driver's low-latency state (five switches it reports, and the frame-generation multipliers it gave during the session) — never a time of day, and never the moment the player pressed anything. No serial number, no display identification data (EDID) and no list of other programs is read or stored. Switching the option off stops the reading, inside a game as well; what earlier sessions stored stays with them until you delete those sessions.
|
||||
- A hardware snapshot per session (CPU/GPU model, driver version, RAM size, OS build, display mode) used for the "what changed between sessions" feature.
|
||||
- App settings, logs (rotated daily — the app keeps 7 days, the capture agent 14 — including the logs written by the component loaded into games), and, after a crash of the app itself, crash dump files.
|
||||
- Which games you enabled code injection for, and when you consented.
|
||||
@@ -39,11 +38,11 @@ The "Report a bug" feature builds a zip file **on your device**, shows you exact
|
||||
|
||||
## 3A. Sharing an export or a bug report
|
||||
|
||||
An exported session (CSV or JSON) and a bug report can contain your games' names and **the paths to their files** — which include your **Windows user name** when a game is installed under your user folder — your hardware model, graphics driver and Windows build, the times you played, and your tags and notes. What a session stores only while Advanced metrics is on (§1) is in neither: an export and a bug report carry what they carried before. A bug report removes user directory paths from its logs; an export is written as it is. Look at a file before you share it. Once you share it, it is outside FrameLedger: whoever receives it, and the site you post it to, can read it under their own terms.
|
||||
An exported session (CSV or JSON) and a bug report can contain your games' names and **the paths to their files** — which include your **Windows user name** when a game is installed under your user folder — your hardware model, graphics driver and Windows build, the times you played, and your tags and notes. A bug report removes user directory paths from its logs; an export is written as it is. Look at a file before you share it. Once you share it, it is outside FrameLedger: whoever receives it, and the site you post it to, can read it under their own terms.
|
||||
|
||||
## 4. What the app can technically observe
|
||||
|
||||
To do its job, FrameLedger observes: which of *your tracked* executables — the entries in your library whose recording is on — are running, and their process trees; whether a game you enabled hooking for runs in an app container, and which of Windows' code-protection settings it runs under (for example, accepting only Microsoft-signed code), read from Windows before any injection; the parameters your games pass to the graphics APIs it intercepts (presentation, upscaling, ray tracing, pipeline creation) — and, only while Advanced metrics is on, more of the parameters of the upscaling calls, and the parameters of ten further calls it begins to intercept in a game only once a session with that option on has started there (the constants the game gives NVIDIA Streamline for each frame, the game's configuration of FSR frame generation, Streamline's answers to the game's four questions about a feature — which version it is, what it requires, whether it is supported and whether it is loaded — and the game switching a feature on or off, allocating and freeing its resources, and shutting Streamline down), which are then stored with the session (sizes, presets, exposure, sharpening, the jitter's size, the motion-vector scale, the depth range, the range of the field of view, flags, the reported frame time, the upscaler's own memory, how frame generation is configured, the versions and requirements of Streamline's features, whether each is supported and loaded, and how often the game switched it, allocated and freed its resources and shut Streamline down), never the camera's position, direction or matrices, and never what identifies the graphics card; and — only while Advanced metrics is on, only in a Direct3D 12 game that had itself loaded NVIDIA's driver library — the graphics driver's own report of the game's last frames and its low-latency state, which the component asks that driver for itself about once a second (it makes that call; the game does not), keeping only how long each stage took; the memory use of a tracked game's process — its dedicated and shared video memory, from Windows' GPU performance counters, and its working sets and commit, from Windows' process-memory information, for which a game it does not inject into is opened with the least access Windows offers and closed again (never its memory's content); loaded module names of a game being captured, the version information of its upscaling, frame-generation and neural-rendering libraries, and whether each was loaded from the game's folder or from the graphics driver's own copy (for detection and for the anti-cheat safety check); the names of the files in each library game's install folder, the version information of its executable and of the upscaling and neural-rendering libraries it ships, the content of its executable file (the markers of the engine and of the graphics libraries it carries, the libraries it imports, and the engine build name an Unreal Engine game carries), the version marks an engine keeps in its own files (Unity's player library and the header of its data file, the header of a Godot data pack, an RPG Maker game's title, core script and Game.ini, the library Game.ini names, and the version file of a Ren'Py game's engine), and the store files that name it (Steam's and GOG's, on your disk) and, for a game the Xbox app or the Microsoft Store installed, the package files in its install folder that describe it (`MicrosoftGame.config` and `appxmanifest.xml`) — to detect its engine, its engine version and its features and to check it for anti-cheat before any injection is possible; the lists of installed games that the Steam, GOG GALAXY, Epic Games and itch apps keep on your disk, and where GOG GALAXY is installed, the folders the Xbox app installs games into on each drive (named by the `.GamingRoot` file at the drive's root) with each game's package files, and Windows' answer to whether that game's package is installed for you — read when you import your library and when you press Play, to find the store that installed a game and hand the game to that store's app — Steam's and GOG GALAXY's also when you open a game's page, to find the artwork their apps keep for it; the cover and banner images that the Steam and GOG GALAXY apps keep on your disk for a game in your library and the logo and splash-screen images a game from the Xbox app ships in its own folder — read to show them on its page, never copied or sent anywhere; the size, position and state of a tracked game's window and the monitor it is on, read from Windows and not from the game, and — for a game FrameLedger injects into — whether the game asked for exclusive full-screen; the NVIDIA driver's settings for your tracked executables (read only: the DLSS and frame-generation overrides the NVIDIA App set); hardware sensor values from your graphics driver's own libraries; and — only while Advanced metrics is on — that driver's description of the graphLine truncated
|
||||
To do its job, FrameLedger observes: which of *your tracked* executables — the entries in your library whose recording is on — are running, and their process trees; whether a game you enabled hooking for runs in an app container, and which of Windows' code-protection settings it runs under (for example, accepting only Microsoft-signed code), read from Windows before any injection; the parameters your games pass to the graphics APIs it intercepts (presentation, upscaling, ray tracing, pipeline creation); the memory use of a tracked game's process — its dedicated and shared video memory, from Windows' GPU performance counters, and its working sets and commit, from Windows' process-memory information, for which a game it does not inject into is opened with the least access Windows offers and closed again (never its memory's content); loaded module names of a game being captured, the version information of its upscaling, frame-generation and neural-rendering libraries, and whether each was loaded from the game's folder or from the graphics driver's own copy (for detection and for the anti-cheat safety check); the names of the files in each library game's install folder, the version information of its executable and of the upscaling and neural-rendering libraries it ships, the content of its executable file (the markers of the engine and of the graphics libraries it carries, the libraries it imports, and the engine build name an Unreal Engine game carries), the version marks an engine keeps in its own files (Unity's player library and the header of its data file, the header of a Godot data pack, an RPG Maker game's title, core script and Game.ini, the library Game.ini names, and the version file of a Ren'Py game's engine), and the store files that name it (Steam's and GOG's, on your disk) and, for a game the Xbox app or the Microsoft Store installed, the package files in its install folder that describe it (`MicrosoftGame.config` and `appxmanifest.xml`) — to detect its engine, its engine version and its features and to check it for anti-cheat before any injection is possible; the lists of installed games that the Steam, GOG GALAXY, Epic Games and itch apps keep on your disk, and where GOG GALAXY is installed, the folders the Xbox app installs games into on each drive (named by the `.GamingRoot` file at the drive's root) with each game's package files, and Windows' answer to whether that game's package is installed for you — read when you import your library and when you press Play, to find the store that installed a game and hand the game to that store's app — Steam's and GOG GALAXY's also when you open a game's page, to find the artwork their apps keep for it; the cover and banner images that the Steam and GOG GALAXY apps keep on your disk for a game in your library and the logo and splash-screen images a game from the Xbox app ships in its own folder — read to show them on its page, never copied or sent anywhere; the size, position and state of a tracked game's window and the monitor it is on, read from Windows and not from the game, and — for a game FrameLedger injects into — whether the game asked for exclusive full-screen; the NVIDIA driver's settings for your tracked executables (read only: the DLSS and frame-generation overrides the NVIDIA App set); hardware sensor values from your graphics driver's own libraries; how busy the processor is and how much memory is in use, from Windows' own counters; the crash reports Windows keeps in its Application log about a tracked game's executable while it ran (to tell a crash from an ordinary exit — the reports are read, never sent anywhere); and the names of the programs a tracked game starts, so that a game's own crash reporter is recognised.
|
||||
|
||||
It does **not** read game memory outside those API parameters, and does not read game saves, chat, input content, network traffic, or anything unrelated to performance measurement. It records only for programs you added to your library and did not switch recording off for — a program whose recording is off is not watched at all — and injects only into games you individually enabled.
|
||||
|
||||
|
||||
@@ -1,45 +0,0 @@
|
||||
# Qodana's settings for the `native` job of .github/workflows/qodana.yml (owner decision D99, 2026-11-11;
|
||||
# docs/13_CI_CD.md §Qodana).
|
||||
#
|
||||
# The C++ of src/native, read by Qodana for .NET (qodana-dotnet: Rider's engine, whose C++ is ReSharper C++) in native
|
||||
# mode on a Windows runner. That linter is the only one that can: the native layer is MSVC-only, and JetBrains' two
|
||||
# C/C++ linters (qodana-cpp, qodana-clang) are Linux images. It reads C++ through a Visual Studio solution, and
|
||||
# src/native is a CMake tree, so the job generates one first - the `x64-vs-analysis` preset - and builds from it only
|
||||
# the one header a build generates (the blocklist floor). Nothing else is compiled.
|
||||
#
|
||||
# A report of its own, in a Qodana Cloud project of its own (`frameledger-cpp`, the QODANA_TOKEN_NATIVE secret): the
|
||||
# managed report (qodana.yaml) leaves src/native out, so every file is in exactly one of the two.
|
||||
version: "1.0"
|
||||
linter: qodana-dotnet
|
||||
withinDocker: false
|
||||
|
||||
profile:
|
||||
base:
|
||||
name: qodana.recommended
|
||||
groups:
|
||||
- groupId: Hints
|
||||
groups:
|
||||
- "severity:TYPO"
|
||||
inspections:
|
||||
- group: Hints
|
||||
enabled: false
|
||||
|
||||
dotnet:
|
||||
solution: build/native/x64-vs-analysis/FrameLedgerNative.slnx
|
||||
# The flags the shipped binaries are built with (the x64-release preset's build type).
|
||||
configuration: RelWithDebInfo
|
||||
platform: x64
|
||||
|
||||
# What is not FrameLedger's code: what CMake generates and fetches (MinHook, Catch2, jsmn, the floor header), the
|
||||
# vendored SDK headers, the fixtures that carry the vendors' names on purpose, a compiled shader as a byte array.
|
||||
exclude:
|
||||
- name: All
|
||||
paths:
|
||||
- build
|
||||
- src/native/third_party
|
||||
- src/native/tools/vendor-stubs
|
||||
- src/native/tools/hook-harness/dxr_raygen_dxil.h
|
||||
|
||||
failureConditions:
|
||||
severityThresholds:
|
||||
any: 0
|
||||
+15
-99
@@ -1,113 +1,29 @@
|
||||
# Qodana's settings for the `managed` job of .github/workflows/qodana.yml (owner decisions D93, 2026-11-10, and D99,
|
||||
# 2026-11-11; docs/13_CI_CD.md §Qodana).
|
||||
# Qodana's settings for .github/workflows/qodana.yml (owner decision D93, 2026-11-10; docs/13_CI_CD.md §Qodana).
|
||||
#
|
||||
# The linter is Qodana for .NET (qodana-dotnet: Rider's engine), in NATIVE mode - on the job's own Windows runner, with
|
||||
# the .NET SDK global.json names, no container. It needs the Ultimate licence the Qodana Cloud organisation holds since
|
||||
# 2026-11-10; the Community linter (qodana-cdnet, InspectCode in a Linux container) ran here until then, and is the way
|
||||
# back if the subscription ever lapses - `linter: qodana-cdnet`, and the job on ubuntu-latest again.
|
||||
# The linter is Qodana Community for .NET (ReSharper's InspectCode in a Linux container), and not Qodana for .NET
|
||||
# (Rider): that one needs an Ultimate licence, and the Qodana Cloud organisation holds a 30-day trial, so a job
|
||||
# built on it would turn red the day the trial ends. The Community linter runs under every licence.
|
||||
#
|
||||
# It reads the solution's C#, XAML and .resx, and what Rider's own plugins read of the repository around it (Markdown,
|
||||
# XML, and JetBrains' security rules over the C#). Not the C++: that is qodana-native.yaml's report, over the Visual
|
||||
# Studio solution CMake generates, sent to a Qodana Cloud project of its own.
|
||||
# It analyses the C# of FrameLedger.slnx - and its XAML and .resx - and nothing native: src/native is a CMake
|
||||
# tree no solution names, and it is MSVC-only, which no Linux container compiles. CodeQL and SonarCloud read the C++.
|
||||
#
|
||||
# Everything a run needs to know is here and nothing is an action argument, so `qodana scan` on a developer's PC reads
|
||||
# the same settings. The linter's version is the action's (the action pins the CLI, the CLI its linter), so the one pin
|
||||
# is the action's commit in the workflow.
|
||||
# The linter's image is the action's own version (the action pins the CLI, the CLI its image), so the one pin is the
|
||||
# action's commit in the workflow.
|
||||
version: "1.0"
|
||||
linter: qodana-dotnet
|
||||
withinDocker: false
|
||||
linter: qodana-cdnet
|
||||
|
||||
# WHERE AN INSPECTION IS SWITCHED OFF (docs/13_CI_CD.md §Qodana, CLAUDE.md §Coding conventions): one of ReSharper's -
|
||||
# C#, XAML, .resx - in .editorconfig, where Rider reads it too. Here only what has no key there: a whole severity and
|
||||
# the IntelliJ platform's own inspections (Markdown, XML) under `profile`; and, under `exclude` further down, the files
|
||||
# JetBrains' security rules were read in, and one file the linter itself fails on. Each with its reason above it.
|
||||
profile:
|
||||
base:
|
||||
name: qodana.recommended
|
||||
groups:
|
||||
# A HINT is what the editor offers without underlining anything (ReSharper's lowest level; this linter files it as
|
||||
# TYPO, Qodana as Low): "invert if", "convert to LINQ", a trailing comma, and every Roslyn analyzer message below
|
||||
# the level this build makes an error. The Community linter never reported them, and the rule D93 set is about
|
||||
# warnings and suggestions. 3,607 of this job's first 3,953 results were hints (run 42923079119).
|
||||
- groupId: Hints
|
||||
groups:
|
||||
- "severity:TYPO"
|
||||
inspections:
|
||||
- group: Hints
|
||||
enabled: false
|
||||
# Rider wants a table's columns padded to one width. The tables here are written to be diffed: a cell's text changes
|
||||
# and its row alone moves.
|
||||
- inspection: MarkdownIncorrectTableFormatting
|
||||
enabled: false
|
||||
# It computes a heading's anchor its own way; the documents are read on GitHub, whose anchors these links follow
|
||||
# (`#display-mode--both-tiers-beta10` for "Display mode — both tiers (beta.10)"), and tools/wiki-build.ps1 checks
|
||||
# the links of every page it publishes. All three it reported resolve on GitHub.
|
||||
- inspection: MarkdownUnresolvedHeaderReference
|
||||
enabled: false
|
||||
# A Windows application manifest: the linter has no schema for urn:schemas-microsoft-com:asm.v1 and reports every
|
||||
# element of the file as undeclared.
|
||||
- inspection: XmlHighlighting
|
||||
ignore:
|
||||
- "src/FrameLedger.App/app.manifest"
|
||||
# INTERIM, from beta.37's move to .NET 11 (D94, 2026-11-11) until the Ultimate linter's pull request replaces this
|
||||
# file: the linter's image carries the .NET SDKs 8 to 10, and main builds on 11. The SDK global.json names is installed
|
||||
# into the container before the build, with the line JetBrains' page gives for an SDK the image lacks.
|
||||
bootstrap: curl -fsSL https://dot.net/v1/dotnet-install.sh | bash -s -- --jsonfile /data/project/global.json -i /usr/share/dotnet
|
||||
|
||||
dotnet:
|
||||
solution: FrameLedger.slnx
|
||||
configuration: Release
|
||||
|
||||
# What is not FrameLedger's code, or not code at all - SonarQube.Analysis.xml's list, for its reasons - and what the
|
||||
# other report reads.
|
||||
exclude:
|
||||
- name: All
|
||||
paths:
|
||||
- src/native
|
||||
- src/FrameLedger.App/Strings.Designer.cs
|
||||
- tests/fixtures
|
||||
- legal/licenses
|
||||
- docs/vendor-exports.json
|
||||
- src/FrameLedger.Infrastructure/Persistence/Migrations
|
||||
- build
|
||||
- out
|
||||
# JETBRAINS' SECURITY RULES (the OpenGrep plugin: pattern rules, several hundred of them) stay on, and the files
|
||||
# their results were READ in are listed here - so a new file that starts a process, or builds an SQL text, is
|
||||
# reported. Two rules fired, 36 times, on 2026-11-11: "a process is started with something that is not a literal"
|
||||
# (35) - and starting processes is part of what FrameLedger is: the Agent beside the App, the game the user added,
|
||||
# Explorer on a folder, the browser on a link - and the same for an SQL text (1: a constant field, every value a
|
||||
# parameter). docs/13_CI_CD.md §Qodana has each place, what it starts and where that comes from.
|
||||
#
|
||||
# The name is the PLUGIN'S ONE INSPECTION, not a rule's: every rule's result is produced by OpenGrepInspection, and
|
||||
# a rule's own id is honoured nowhere - not by `ignore`, not by an `exclude` path, not by `enabled: false` (three
|
||||
# runs, 42932842462, 42935752891 and 42938295264: all 36 stood each time; the server is handed every rule file
|
||||
# whatever the profile says). So a file listed here is left out of ALL of the plugin's rules, which is the price.
|
||||
# ProcessStartSitesTests, in the gate, names the same files and fails on a new one.
|
||||
- name: OpenGrepInspection
|
||||
paths:
|
||||
- src/FrameLedger.App/Services/AgentLauncher.cs
|
||||
- src/FrameLedger.App/Services/AgentTool.cs
|
||||
- src/FrameLedger.App/Services/Explorer.cs
|
||||
- src/FrameLedger.App/Services/ShellStarter.cs
|
||||
- src/FrameLedger.App/Services/ShellUrlOpener.cs
|
||||
- src/FrameLedger.App/ViewModels/SettingsViewModel.cs
|
||||
- src/FrameLedger.Infrastructure/Capture/ProcessLauncher.cs
|
||||
- src/FrameLedger.Infrastructure/Diagnostics/CrashDumpWriter.cs
|
||||
- src/FrameLedger.Infrastructure/Startup/AgentElevation.cs
|
||||
- src/FrameLedger.Infrastructure/Startup/LogonTask.cs
|
||||
- src/FrameLedger.Infrastructure/Persistence/SqliteSessionRepository.cs
|
||||
# The tests start what they test - the harness, the Agent, a process to hold a handle on (24 of the 35).
|
||||
- tests
|
||||
# THE LINTER'S OWN FAULT, not the file's: resolving `PInvoke.EnumDisplaySettings(null, ...)` - the `null` to PCWSTR
|
||||
# conversion - the engine of this linter's build (QDNET-262.12299) fails an internal assertion
|
||||
# ("IsStandardImplicitConversionFromExpression(conversion.Kind)", in its log), loses the method, and reports its
|
||||
# three locals and the file's three usings as unused. The compiler builds it with warnings as errors, and
|
||||
# InspectCode 2026.2.3.1 and 2026.3.0 report nothing there. To be removed when a linter build reads the file.
|
||||
- name: UnusedVariable.Compiler
|
||||
paths:
|
||||
- src/FrameLedger.Infrastructure/Recording/PrimaryDisplay.cs
|
||||
- name: RedundantUsingDirective
|
||||
paths:
|
||||
- src/FrameLedger.Infrastructure/Recording/PrimaryDisplay.cs
|
||||
|
||||
# The gate: no problem at all. What the linter reports is settled where it is found - fixed, or its inspection
|
||||
# switched off with the reason beside it - so a count above zero is something new.
|
||||
# switched off in .editorconfig with the reason beside it (InspectCode reads its severities there, and so does
|
||||
# Rider) - so a count above zero is something new.
|
||||
failureConditions:
|
||||
severityThresholds:
|
||||
any: 0
|
||||
@@ -1,7 +1,6 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
using FrameLedger.Application.Advanced;
|
||||
using FrameLedger.Application.AntiCheat;
|
||||
using FrameLedger.Application.Capture;
|
||||
using FrameLedger.Application.Consent;
|
||||
@@ -44,7 +43,6 @@ internal sealed class AgentRecording
|
||||
private readonly WindowGeometryProbe _display = new();
|
||||
private readonly UserModeExceptionLapsePolicy _exceptionLapse;
|
||||
private readonly ICrashReporterSightings _reporters;
|
||||
private readonly IAdvancedHardware _advanced;
|
||||
|
||||
public AgentRecording(
|
||||
IGameConsentStore store,
|
||||
@@ -69,10 +67,8 @@ internal sealed class AgentRecording
|
||||
IUserModeExceptionSwitch exceptions,
|
||||
IOverlayToleranceChannel tolerance,
|
||||
UserModeExceptionLapsePolicy exceptionLapse,
|
||||
ICrashReporterSightings reporters,
|
||||
IAdvancedHardware advanced)
|
||||
ICrashReporterSightings reporters)
|
||||
{
|
||||
_advanced = advanced;
|
||||
_reporters = reporters;
|
||||
_profiles = profiles;
|
||||
_exceptions = exceptions;
|
||||
@@ -123,21 +119,18 @@ internal sealed class AgentRecording
|
||||
_partials,
|
||||
_finalizer,
|
||||
_crashes,
|
||||
options => Poller(options.TelemetryInterval, options.AdvancedMetrics ? _advanced : null),
|
||||
static options => Poller(options.TelemetryInterval),
|
||||
TimeProvider.System,
|
||||
new RecorderOptions { MinimumSessionLength = minimum, PartialFlushInterval = flush },
|
||||
_observer,
|
||||
_policy,
|
||||
_profiles,
|
||||
_exceptionLapse,
|
||||
_reporters,
|
||||
_advanced);
|
||||
_reporters);
|
||||
}
|
||||
|
||||
/// <summary>L1 + L2 + L3 under the composite, one poller per session; the poller owns and disposes the layers. The interval is the session's (<c>telemetry.interval_ms</c>, D16).</summary>
|
||||
/// <param name="interval">Between two polls.</param>
|
||||
/// <param name="advanced">The Agent's shared advanced reader when the session records Advanced metrics (D101); null — the option off — composes none.</param>
|
||||
public static TelemetryPoller Poller(TimeSpan interval, IAdvancedHardware? advanced = null)
|
||||
public static TelemetryPoller Poller(TimeSpan interval)
|
||||
{
|
||||
// Ownership walks up one step at a time and each local is nulled at its hand-off, so a throw
|
||||
// anywhere below disposes exactly what nobody owns yet.
|
||||
@@ -168,7 +161,7 @@ internal sealed class AgentRecording
|
||||
// The game process's own memory (beta.12, D43): read from outside it through FrameLedger.ProcessStats.dll, for
|
||||
// whichever process the capture loop tells the poller to follow. Absent DLL = N/A, never a fault.
|
||||
game = new GameMemoryReader(new NativeProcessStats());
|
||||
var poller = new TelemetryPoller(composite, new TelemetryPollerOptions { Interval = interval }, TimeProvider.System, ownsSource: true, system, game, advanced);
|
||||
var poller = new TelemetryPoller(composite, new TelemetryPollerOptions { Interval = interval }, TimeProvider.System, ownsSource: true, system, game);
|
||||
composite = null;
|
||||
system = null;
|
||||
game = null;
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
using FrameLedger.Agent.Hosting;
|
||||
using FrameLedger.Application.Advanced;
|
||||
using FrameLedger.Application.AntiCheat;
|
||||
using FrameLedger.Application.Capture;
|
||||
using FrameLedger.Application.Consent;
|
||||
@@ -121,15 +120,6 @@ internal static class AgentServices
|
||||
services.AddSingleton<ISeriesCodec, DeflateSeriesCodec>();
|
||||
services.AddSingleton<SessionFinalizer>();
|
||||
services.AddSingleton(static sp => new PartialRecovery(sp.GetRequiredService<IPartialSessionStore>(), sp.GetRequiredService<SessionFinalizer>()));
|
||||
// Advanced metrics (owner decisions D101 and D107): ONE reader for the whole Agent, on a thread of its own, that
|
||||
// runs only while a session recorded with the option on - or the App's page - holds it, and closes ten seconds
|
||||
// after the last lets go. Constructing it opens nothing; a PC idling with the Agent in the tray reads no sensor
|
||||
// for this. The container disposes it with the host.
|
||||
services.AddSingleton<IAdvancedHardware>(static _ => new AdvancedHardwareHub(
|
||||
static () => AdvancedHardwareReader.OverThisPc(TimeProvider.System, static line => Serilog.Log.Information("{Line}", line)),
|
||||
interval: TimeSpan.FromSeconds(1),
|
||||
linger: TimeSpan.FromSeconds(10),
|
||||
static line => Serilog.Log.Information("{Line}", line)));
|
||||
services.AddSingleton<AgentRecording>();
|
||||
}
|
||||
|
||||
@@ -256,18 +246,11 @@ internal static class AgentServices
|
||||
services.AddSingleton<CapturePause>();
|
||||
services.TryAddSingleton<IAgentLifetime, NoAgentLifetime>();
|
||||
services.AddSingleton(static sp => CommandHandler(sp));
|
||||
// GetAdvancedMachine (D101/D107): the App's page asks once a second while it is open, and each request is its
|
||||
// hold on the shared reader for a few seconds - so nothing has to tell the Agent that the page closed.
|
||||
services.AddSingleton(static sp => new AdvancedMachineResponder(
|
||||
sp.GetRequiredService<IAdvancedHardware>(),
|
||||
ct => sp.GetRequiredService<RegisteredSettings>().GetBooleanAsync(SettingsRegistry.TelemetryAdvanced, ct),
|
||||
TimeProvider.System));
|
||||
services.AddSingleton<IIpcRequestHandler>(static sp => new AgentRequestHandler(
|
||||
AgentIdentityFactory.OfThisProcess(sp.GetRequiredService<AgentPaths>().VkLayerDirectory, sp.GetService<AgentElevationState>()?.Outcome),
|
||||
TelemetryDescriptor(),
|
||||
() => sp.GetRequiredService<SessionEventPublisher>().Status,
|
||||
() => sp.GetRequiredService<AgentCommandHandler>(),
|
||||
sp.GetRequiredService<AdvancedMachineResponder>()));
|
||||
() => sp.GetRequiredService<AgentCommandHandler>()));
|
||||
services.AddSingleton(static sp => new PipeServer(
|
||||
sp.GetRequiredService<PipeServerOptions>(),
|
||||
sp.GetRequiredService<IIpcRequestHandler>(),
|
||||
|
||||
@@ -108,10 +108,6 @@ public partial class App : System.Windows.Application
|
||||
LoggingLevel.SetDebug(await registered.GetBooleanAsync(SettingsRegistry.LogDebug).ConfigureAwait(true));
|
||||
FpsDecimals.Two = await registered.GetBooleanAsync(SettingsRegistry.UiFpsDecimals).ConfigureAwait(true);
|
||||
ScrollBarHiding.Apply(await registered.GetBooleanAsync(SettingsRegistry.UiHideScrollBars).ConfigureAwait(true));
|
||||
// Advanced metrics (D101/D105): the page is offered while the option is on - and in a viewer also when the copy holds
|
||||
// a session recorded with it on, since that is what a copy is opened to look at.
|
||||
AdvancedOption.IsOn = await registered.GetBooleanAsync(SettingsRegistry.TelemetryAdvanced).ConfigureAwait(true)
|
||||
|| (UiPaths.IsViewer && (await new SqliteSessionRepository(_db).ListAdvancedAsync(1).ConfigureAwait(true)).Count > 0);
|
||||
var closePolicy = new WindowClosePolicy { MinimizeToTray = await registered.GetBooleanAsync(SettingsRegistry.UiMinimizeToTray).ConfigureAwait(true) };
|
||||
|
||||
_host = BuildHost(_db, appearance, registered, closePolicy);
|
||||
@@ -363,9 +359,6 @@ public partial class App : System.Windows.Application
|
||||
builder.Services.AddTransient<GameDetailViewModel>();
|
||||
builder.Services.AddTransient<ComparePage>();
|
||||
builder.Services.AddTransient<CompareViewModel>();
|
||||
builder.Services.AddTransient<AdvancedPage>();
|
||||
builder.Services.AddTransient<AdvancedViewModel>();
|
||||
builder.Services.AddSingleton<AdvancedSelection>();
|
||||
builder.Services.AddTransient<LogsPage>();
|
||||
builder.Services.AddTransient<LogsViewModel>();
|
||||
builder.Services.AddTransient<SettingsPage>();
|
||||
@@ -490,9 +483,6 @@ public partial class App : System.Windows.Application
|
||||
sp.GetRequiredService<Application.Play.IGogGalaxyLocator>(),
|
||||
sp.GetRequiredService<IShellStarter>(),
|
||||
sp.GetRequiredService<IAgentRequests>()));
|
||||
// Advanced metrics (D101/D107): "this PC, now" for its page. It asks the Agent only while a page watches it, and a
|
||||
// viewer's link is never connected - so it says "no agent" there.
|
||||
services.AddSingleton(static sp => new AdvancedMachineFeed(sp.GetRequiredService<IAgentRequests>(), TimeProvider.System));
|
||||
services.AddSingleton<IExecutableIdentitySource, ExecutableIdentitySource>();
|
||||
services.AddSingleton(static sp => new LibraryImporter(
|
||||
sp.GetServices<IStoreLibrarySource>(),
|
||||
|
||||
@@ -1,11 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
namespace FrameLedger.App.Charts;
|
||||
|
||||
/// <summary>One line of the Advanced page's chart: its legend text and its points.</summary>
|
||||
/// <param name="Label">What the line is.</param>
|
||||
/// <param name="Xs">Seconds from the session's start, or OLE automation dates for a live chart.</param>
|
||||
/// <param name="Ys">The values, in the unit of the catalog entry.</param>
|
||||
[System.Diagnostics.CodeAnalysis.SuppressMessage("Performance", "CA1819:Properties should not return arrays", Justification = "a data carrier for the chart, as SensorSeries is")]
|
||||
public sealed record AdvancedChartLine(string Label, double[] Xs, double[] Ys);
|
||||
@@ -1,13 +0,0 @@
|
||||
<!-- SPDX-License-Identifier: GPL-3.0-only -->
|
||||
<!-- Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE -->
|
||||
|
||||
<UserControl x:Class="FrameLedger.App.Charts.AdvancedSeriesChart"
|
||||
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
|
||||
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
|
||||
xmlns:charts="clr-namespace:FrameLedger.App.Charts"
|
||||
xmlns:res="clr-namespace:FrameLedger.App"
|
||||
MinHeight="260">
|
||||
<!-- 08_UI §Advanced: one catalog entry over time - its series, or their lowest, average and highest above eight. The
|
||||
table beside it on the page lists the same readings (A11y_ChartData_Advanced). -->
|
||||
<charts:ChartPlot x:Name="Plot" AutomationProperties.Name="{x:Static res:Strings.A11y_Chart_Advanced}" AutomationProperties.HelpText="{x:Static res:Strings.A11y_ChartData_Advanced}" />
|
||||
</UserControl>
|
||||
@@ -1,90 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
using System.Windows.Controls;
|
||||
using ScottPlot;
|
||||
using ScottPlot.Plottables;
|
||||
|
||||
namespace FrameLedger.App.Charts;
|
||||
|
||||
/// <summary>
|
||||
/// The Advanced page's chart (owner decision D101): the series of one catalog entry over time. <see cref="TimeOfDay"/>
|
||||
/// says what the horizontal axis is — the clock, for what the PC reads now, or seconds from a session's start — and is
|
||||
/// set once, before the first <see cref="Show"/>: a date axis replaces the bottom axis and is not swapped back.
|
||||
/// </summary>
|
||||
/// <remarks>
|
||||
/// Lines differ by pattern and marker as well as by colour (<see cref="ChartPatterns"/>), so a chart read without
|
||||
/// colour still tells them apart; and a series with one reading is a point, not an invisible line.
|
||||
/// </remarks>
|
||||
public partial class AdvancedSeriesChart : UserControl
|
||||
{
|
||||
private bool _dateAxis;
|
||||
|
||||
public AdvancedSeriesChart()
|
||||
{
|
||||
InitializeComponent();
|
||||
ChartTheme.Attach(Plot);
|
||||
}
|
||||
|
||||
/// <summary>True when the points' x values are OLE automation dates (a live chart); false for seconds from a session's start.</summary>
|
||||
public bool TimeOfDay { get; set; }
|
||||
|
||||
public Plot ScottPlot => Plot.Plot;
|
||||
|
||||
/// <summary>How many lines the last <see cref="Show"/> drew — what a test reads.</summary>
|
||||
public int DrawnLines { get; private set; }
|
||||
|
||||
/// <summary>Draws <paramref name="lines"/> against <paramref name="unit"/>; no line clears the chart.</summary>
|
||||
public void Show(IReadOnlyList<AdvancedChartLine> lines, string unit)
|
||||
{
|
||||
ArgumentNullException.ThrowIfNull(lines);
|
||||
Plot plot = Plot.Plot;
|
||||
plot.Clear();
|
||||
if (TimeOfDay && !_dateAxis)
|
||||
{
|
||||
// Before the theme and the labels: the date axis REPLACES the bottom axis and would drop both (TrendChart).
|
||||
plot.Axes.DateTimeTicksBottom();
|
||||
_dateAxis = true;
|
||||
}
|
||||
|
||||
ChartTheme.Apply(plot);
|
||||
plot.XLabel(TimeOfDay ? Strings.Advanced_Chart_Time : Strings.Advanced_Chart_Seconds);
|
||||
plot.YLabel(unit ?? string.Empty);
|
||||
|
||||
ChartPalette p = ChartTheme.Current;
|
||||
Color[] palette = [p.Native, p.Displayed, p.Percentile, p.Sensor, p.SensorSecondary, p.Stutter, p.Histogram, p.Segment];
|
||||
int drawn = 0;
|
||||
foreach (AdvancedChartLine line in lines)
|
||||
{
|
||||
if (line.Xs.Length == 0 || line.Xs.Length != line.Ys.Length)
|
||||
{
|
||||
continue;
|
||||
}
|
||||
|
||||
Scatter scatter = plot.Add.Scatter(line.Xs, line.Ys, palette[drawn % palette.Length]);
|
||||
scatter.LineWidth = 2;
|
||||
scatter.MarkerSize = line.Xs.Length == 1 ? 7 : 0;
|
||||
scatter.LegendText = line.Label;
|
||||
ChartPatterns.Line(scatter, drawn);
|
||||
if (line.Xs.Length == 1)
|
||||
{
|
||||
ChartPatterns.Points(scatter, drawn);
|
||||
}
|
||||
|
||||
drawn++;
|
||||
}
|
||||
|
||||
DrawnLines = drawn;
|
||||
if (drawn > 0)
|
||||
{
|
||||
plot.Axes.AutoScale();
|
||||
plot.ShowLegend(Alignment.UpperLeft);
|
||||
}
|
||||
else
|
||||
{
|
||||
plot.HideLegend();
|
||||
}
|
||||
|
||||
Plot.Refresh();
|
||||
}
|
||||
}
|
||||
@@ -37,49 +37,6 @@ public sealed class SessionSeriesLoader
|
||||
public Task<IReadOnlyList<SensorSeries>> LoadSensorsAsync(long sessionId, CancellationToken ct = default) =>
|
||||
Task.Run(async () => (IReadOnlyList<SensorSeries>)DecodeSensors(await _sessions.FindSensorsAsync(sessionId, ct).ConfigureAwait(false), offsetS: 0), ct);
|
||||
|
||||
/// <summary>
|
||||
/// The session's advanced series (owner decision D102), timed from the session's start by the same <c>t_ms</c> clock
|
||||
/// as the sensors. A tick with no reading — NaN, and most ticks of a sensor read every fifth — is left out, never drawn
|
||||
/// as a zero; a series may be negative, so nothing else is. Empty for a session recorded with the option off. On the
|
||||
/// thread pool, as <see cref="LoadAsync"/>.
|
||||
/// </summary>
|
||||
public Task<IReadOnlyList<SensorSeries>> LoadAdvancedAsync(long sessionId, CancellationToken ct = default) =>
|
||||
Task.Run(async () => DecodeAdvanced(await _sessions.FindAdvancedSensorsAsync(sessionId, ct).ConfigureAwait(false)), ct);
|
||||
|
||||
/// <summary>The advanced blobs decoded: <c>t_ms</c> is their clock, NaN is "no reading".</summary>
|
||||
public static IReadOnlyList<SensorSeries> DecodeAdvanced(IReadOnlyList<SensorBlob> blobs)
|
||||
{
|
||||
ArgumentNullException.ThrowIfNull(blobs);
|
||||
SensorBlob? clock = blobs.FirstOrDefault(static s => string.Equals(s.Series, "t_ms", StringComparison.Ordinal));
|
||||
float[]? tMs = clock is null || !string.Equals(clock.Codec, SeriesCodec.Tag, StringComparison.Ordinal) ? null : SeriesCodec.DecodeFloat32(clock.Data.ToArray());
|
||||
var result = new List<SensorSeries>();
|
||||
foreach (SensorBlob blob in blobs)
|
||||
{
|
||||
if (string.Equals(blob.Series, "t_ms", StringComparison.Ordinal) || !string.Equals(blob.Codec, SeriesCodec.Tag, StringComparison.Ordinal))
|
||||
{
|
||||
continue;
|
||||
}
|
||||
|
||||
float[] values = SeriesCodec.DecodeFloat32(blob.Data.ToArray());
|
||||
var xs = new List<double>();
|
||||
var ys = new List<double>();
|
||||
for (int i = 0; i < values.Length; i++)
|
||||
{
|
||||
if (float.IsNaN(values[i]))
|
||||
{
|
||||
continue;
|
||||
}
|
||||
|
||||
xs.Add(tMs is not null && i < tMs.Length ? tMs[i] / 1000.0 : i / Math.Max(blob.Hz, 0.001));
|
||||
ys.Add(values[i]);
|
||||
}
|
||||
|
||||
result.Add(new SensorSeries(blob.Series, [.. xs], [.. ys]));
|
||||
}
|
||||
|
||||
return result;
|
||||
}
|
||||
|
||||
private async Task<SessionSeries?> ReadAndDecodeAsync(long sessionId, CancellationToken ct)
|
||||
{
|
||||
FrameBlobs? frames = await _sessions.FindFramesAsync(sessionId, ct).ConfigureAwait(false);
|
||||
|
||||
@@ -24,14 +24,11 @@
|
||||
<KeyBinding Command="{Binding ViewModel.NavigateToCommand}" CommandParameter="3" Key="D3" Modifiers="Control" />
|
||||
<KeyBinding Command="{Binding ViewModel.NavigateToCommand}" CommandParameter="4" Key="D4" Modifiers="Control" />
|
||||
<KeyBinding Command="{Binding ViewModel.NavigateToCommand}" CommandParameter="5" Key="D5" Modifiers="Control" />
|
||||
<!-- Ctrl+6 (owner decision D105): the Advanced page, only while its option is on - ShellShortcuts refuses it otherwise. -->
|
||||
<KeyBinding Command="{Binding ViewModel.NavigateToCommand}" CommandParameter="6" Key="D6" Modifiers="Control" />
|
||||
<KeyBinding Command="{Binding ViewModel.NavigateToCommand}" CommandParameter="1" Key="NumPad1" Modifiers="Control" />
|
||||
<KeyBinding Command="{Binding ViewModel.NavigateToCommand}" CommandParameter="2" Key="NumPad2" Modifiers="Control" />
|
||||
<KeyBinding Command="{Binding ViewModel.NavigateToCommand}" CommandParameter="3" Key="NumPad3" Modifiers="Control" />
|
||||
<KeyBinding Command="{Binding ViewModel.NavigateToCommand}" CommandParameter="4" Key="NumPad4" Modifiers="Control" />
|
||||
<KeyBinding Command="{Binding ViewModel.NavigateToCommand}" CommandParameter="5" Key="NumPad5" Modifiers="Control" />
|
||||
<KeyBinding Command="{Binding ViewModel.NavigateToCommand}" CommandParameter="6" Key="NumPad6" Modifiers="Control" />
|
||||
</ui:FluentWindow.InputBindings>
|
||||
|
||||
<!--
|
||||
@@ -189,11 +186,6 @@
|
||||
<ui:NavigationViewItem Content="{x:Static res:Strings.Nav_Logs}"
|
||||
Icon="{ui:SymbolIcon DocumentText24}"
|
||||
TargetPageType="{x:Type pages:LogsPage}" />
|
||||
<!-- Advanced metrics (owner decisions D101/D105): last in the menu, and there only while the option is on. -->
|
||||
<ui:NavigationViewItem Content="{x:Static res:Strings.Nav_Advanced}"
|
||||
Icon="{ui:SymbolIcon DataUsage24}"
|
||||
TargetPageType="{x:Type pages:AdvancedPage}"
|
||||
Visibility="{Binding Path=(services:AdvancedOption.IsOn), Converter={StaticResource BoolToVis}}" />
|
||||
</ui:NavigationView.MenuItems>
|
||||
<ui:NavigationView.FooterMenuItems>
|
||||
<ui:NavigationViewItem Content="{x:Static res:Strings.Nav_Settings}"
|
||||
|
||||
@@ -1,183 +0,0 @@
|
||||
<!-- SPDX-License-Identifier: GPL-3.0-only -->
|
||||
<!-- Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE -->
|
||||
|
||||
<Page x:Class="FrameLedger.App.Pages.AdvancedPage"
|
||||
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
|
||||
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
|
||||
xmlns:ui="http://schemas.lepo.co/wpfui/2022/xaml"
|
||||
xmlns:charts="clr-namespace:FrameLedger.App.Charts"
|
||||
xmlns:controls="clr-namespace:FrameLedger.App.Controls"
|
||||
xmlns:res="clr-namespace:FrameLedger.App"
|
||||
xmlns:vm="clr-namespace:FrameLedger.App.ViewModels"
|
||||
Title="{x:Static res:Strings.Advanced_Header}"
|
||||
Foreground="{DynamicResource TextFillColorPrimaryBrush}"
|
||||
ScrollViewer.CanContentScroll="False">
|
||||
<!--
|
||||
08_UI §Advanced (owner decision D101). Three tabs, by what a value belongs to: This PC - what the Agent reads now,
|
||||
asked only while this page is on screen (D107) and never stored; Session - what a session recorded with the option
|
||||
on stored; Sources - every entry of the catalog with whether it is read, or why not. A reason is always words,
|
||||
never a colour alone, and each chart has its readings in a table beside it.
|
||||
-->
|
||||
<Page.Resources>
|
||||
<!-- One fact: label and value in two columns that line up within a group; a table-valued fact unfolds its rows.
|
||||
Both templates are implicit - found by the type they show - so nothing on the page names a resource key. -->
|
||||
<DataTemplate DataType="{x:Type vm:AdvancedFactRow}">
|
||||
<StackPanel>
|
||||
<Grid Margin="0,2,0,0" Visibility="{Binding HasDetails, Converter={StaticResource InverseBoolToVis}}">
|
||||
<Grid.ColumnDefinitions>
|
||||
<ColumnDefinition Width="Auto" SharedSizeGroup="AdvancedFactLabel" />
|
||||
<ColumnDefinition Width="*" />
|
||||
</Grid.ColumnDefinitions>
|
||||
<TextBlock MaxWidth="460" Style="{StaticResource FieldLabel}" Text="{Binding Label}" TextWrapping="Wrap" />
|
||||
<TextBlock Grid.Column="1" Style="{StaticResource FieldValue}" Text="{Binding Value}" TextWrapping="Wrap" />
|
||||
</Grid>
|
||||
<Expander Margin="0,2,0,4" Visibility="{Binding HasDetails, Converter={StaticResource BoolToVis}}">
|
||||
<Expander.Header>
|
||||
<TextBlock TextWrapping="Wrap">
|
||||
<Run Text="{Binding Label, Mode=OneWay}" /><Run Text=" (" /><Run Text="{Binding Value, Mode=OneWay}" /><Run Text=")" />
|
||||
</TextBlock>
|
||||
</Expander.Header>
|
||||
<ItemsControl Margin="12,4,0,0" Focusable="False" Grid.IsSharedSizeScope="True" ItemsSource="{Binding Details}">
|
||||
<ItemsControl.ItemTemplate>
|
||||
<DataTemplate DataType="{x:Type vm:AdvancedDetailRow}">
|
||||
<Grid>
|
||||
<Grid.ColumnDefinitions>
|
||||
<ColumnDefinition Width="Auto" SharedSizeGroup="AdvancedDetailName" />
|
||||
<ColumnDefinition Width="*" />
|
||||
</Grid.ColumnDefinitions>
|
||||
<TextBlock MaxWidth="460" Style="{StaticResource FieldLabel}" Text="{Binding Name}" TextWrapping="Wrap" />
|
||||
<TextBlock Grid.Column="1" Style="{StaticResource FieldValue}" Text="{Binding Value}" TextWrapping="Wrap" />
|
||||
</Grid>
|
||||
</DataTemplate>
|
||||
</ItemsControl.ItemTemplate>
|
||||
</ItemsControl>
|
||||
</Expander>
|
||||
</StackPanel>
|
||||
</DataTemplate>
|
||||
|
||||
<!-- A group of the catalog under its heading. -->
|
||||
<DataTemplate DataType="{x:Type vm:AdvancedFactGroup}">
|
||||
<StackPanel Margin="0,12,0,0">
|
||||
<ui:TextBlock AutomationProperties.HeadingLevel="Level3" FontTypography="BodyStrong" Text="{Binding Title}" />
|
||||
<ItemsControl Margin="0,4,0,0" Focusable="False" Grid.IsSharedSizeScope="True" ItemsSource="{Binding Rows}" />
|
||||
</StackPanel>
|
||||
</DataTemplate>
|
||||
</Page.Resources>
|
||||
|
||||
<ScrollViewer VerticalScrollBarVisibility="Auto">
|
||||
<StackPanel Style="{StaticResource PageRoot}">
|
||||
<ui:TextBlock AutomationProperties.HeadingLevel="Level1" FontTypography="Title" Text="{x:Static vm:AdvancedViewModel.Header}" />
|
||||
|
||||
<TabControl Margin="0,16,0,0" SelectedIndex="{Binding ViewModel.SelectedTab, Mode=TwoWay}">
|
||||
<!-- This PC: read now, by the Agent, only while this page is open. -->
|
||||
<TabItem Header="{x:Static vm:AdvancedViewModel.TabMachine}">
|
||||
<StackPanel Margin="0,12,0,0">
|
||||
<ui:TextBlock Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Machine_Intro}" TextWrapping="Wrap" />
|
||||
<ui:TextBlock Margin="0,8,0,0" Text="{Binding ViewModel.MachineStatus}" TextWrapping="Wrap" />
|
||||
<ui:TextBlock Margin="0,4,0,0" Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Elevation_Hint}" TextWrapping="Wrap"
|
||||
Visibility="{Binding ViewModel.ShowElevationHint, Converter={StaticResource BoolToVis}}" />
|
||||
|
||||
<ui:TextBlock Margin="0,20,0,0" AutomationProperties.HeadingLevel="Level2" FontTypography="Subtitle" Text="{x:Static res:Strings.Advanced_Facts_Header}" />
|
||||
<ItemsControl Focusable="False" ItemsSource="{Binding ViewModel.MachineGroups}" />
|
||||
|
||||
<ui:TextBlock Margin="0,20,0,0" AutomationProperties.HeadingLevel="Level2" FontTypography="Subtitle" Text="{x:Static res:Strings.Advanced_Now_Header}" />
|
||||
<DataGrid MaxHeight="360" Margin="0,8,0,0" AutoGenerateColumns="False" AutomationProperties.Name="{x:Static res:Strings.Advanced_Now_Header}"
|
||||
CanUserAddRows="False" HeadersVisibility="Column" IsReadOnly="True" ItemsSource="{Binding ViewModel.LiveRows}" SelectionMode="Single">
|
||||
<DataGrid.Columns>
|
||||
<DataGridTextColumn Width="Auto" MinWidth="320" Binding="{Binding Label}" Header="{x:Static res:Strings.Advanced_Col_Name}" />
|
||||
<DataGridTextColumn Width="Auto" MinWidth="120" Binding="{Binding Value}" Header="{x:Static res:Strings.Advanced_Col_Value}" />
|
||||
<DataGridTextColumn Width="Auto" MinWidth="110" Binding="{Binding ReadAt}" Header="{x:Static res:Strings.Advanced_Col_ReadAt}" />
|
||||
<DataGridTemplateColumn Width="*" CanUserResize="False" CanUserSort="False" IsReadOnly="True" controls:CellName.Path="Label" />
|
||||
</DataGrid.Columns>
|
||||
</DataGrid>
|
||||
|
||||
<ui:TextBlock Margin="0,20,0,0" AutomationProperties.HeadingLevel="Level2" FontTypography="Subtitle" Text="{x:Static res:Strings.Advanced_Chart_Header}" />
|
||||
<StackPanel Margin="0,8,0,0" Orientation="Horizontal">
|
||||
<ui:TextBlock Margin="0,0,8,0" VerticalAlignment="Center" Text="{x:Static res:Strings.Advanced_Chart_Metric}" />
|
||||
<ComboBox MinWidth="360" AutomationProperties.Name="{x:Static res:Strings.A11y_Advanced_Metric}" DisplayMemberPath="Label"
|
||||
ItemsSource="{Binding ViewModel.LiveMetrics}" SelectedItem="{Binding ViewModel.SelectedLiveMetric, Mode=TwoWay}" />
|
||||
</StackPanel>
|
||||
<ui:TextBlock Margin="0,6,0,0" Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Chart_LiveNote}" TextWrapping="Wrap" />
|
||||
<ui:TextBlock Margin="0,4,0,0" Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Chart_Band}" TextWrapping="Wrap"
|
||||
Visibility="{Binding ViewModel.LiveBand, Converter={StaticResource BoolToVis}}" />
|
||||
<ui:TextBlock Margin="0,12,0,0" Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Chart_Empty}"
|
||||
Visibility="{Binding ViewModel.LiveChartEmpty, Converter={StaticResource BoolToVis}}" />
|
||||
<charts:AdvancedSeriesChart x:Name="LiveChart" Height="320" Margin="0,8,0,0" TimeOfDay="True"
|
||||
Visibility="{Binding ViewModel.LiveChartEmpty, Converter={StaticResource InverseBoolToVis}}" />
|
||||
</StackPanel>
|
||||
</TabItem>
|
||||
|
||||
<!-- Session: what one session recorded with the option on stored. -->
|
||||
<TabItem Header="{x:Static vm:AdvancedViewModel.TabSession}">
|
||||
<StackPanel Margin="0,12,0,0">
|
||||
<ui:TextBlock Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Session_Empty}" TextWrapping="Wrap"
|
||||
Visibility="{Binding ViewModel.NoSessions, Converter={StaticResource BoolToVis}}" />
|
||||
<StackPanel Visibility="{Binding ViewModel.NoSessions, Converter={StaticResource InverseBoolToVis}}">
|
||||
<StackPanel Orientation="Horizontal">
|
||||
<ui:TextBlock Margin="0,0,8,0" VerticalAlignment="Center" Text="{x:Static res:Strings.Advanced_Session_Pick}" />
|
||||
<ComboBox MinWidth="420" AutomationProperties.Name="{x:Static res:Strings.A11y_Advanced_Session}" DisplayMemberPath="Text"
|
||||
ItemsSource="{Binding ViewModel.SessionOptions}" SelectedItem="{Binding ViewModel.SelectedSession, Mode=TwoWay}" />
|
||||
</StackPanel>
|
||||
<ui:TextBlock Margin="0,8,0,0" Style="{StaticResource SecondaryText}" Text="{Binding ViewModel.SessionSources}" TextWrapping="Wrap"
|
||||
Visibility="{Binding ViewModel.SessionSources, Converter={StaticResource NullToCollapsed}}" />
|
||||
|
||||
<ui:TextBlock Margin="0,20,0,0" AutomationProperties.HeadingLevel="Level2" FontTypography="Subtitle" Text="{x:Static res:Strings.Advanced_Session_Facts}" />
|
||||
<ItemsControl Focusable="False" ItemsSource="{Binding ViewModel.SessionGroups}" />
|
||||
|
||||
<ui:TextBlock Margin="0,20,0,0" AutomationProperties.HeadingLevel="Level2" FontTypography="Subtitle" Text="{x:Static res:Strings.Advanced_Session_Stats}" />
|
||||
<ui:TextBlock Margin="0,8,0,0" Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Session_NoStats}" TextWrapping="Wrap"
|
||||
Visibility="{Binding ViewModel.SessionHasNoStats, Converter={StaticResource BoolToVis}}" />
|
||||
<DataGrid MaxHeight="360" Margin="0,8,0,0" AutoGenerateColumns="False" AutomationProperties.Name="{x:Static res:Strings.Advanced_Session_Stats}"
|
||||
CanUserAddRows="False" HeadersVisibility="Column" IsReadOnly="True" ItemsSource="{Binding ViewModel.SessionStats}" SelectionMode="Single"
|
||||
Visibility="{Binding ViewModel.SessionHasNoStats, Converter={StaticResource InverseBoolToVis}}">
|
||||
<DataGrid.Columns>
|
||||
<DataGridTextColumn Width="Auto" MinWidth="320" Binding="{Binding Label}" Header="{x:Static res:Strings.Advanced_Col_Name}" />
|
||||
<DataGridTextColumn Width="Auto" MinWidth="90" Binding="{Binding Samples}" Header="{x:Static res:Strings.Advanced_Col_Samples}" />
|
||||
<DataGridTextColumn Width="Auto" MinWidth="110" Binding="{Binding Min}" Header="{x:Static res:Strings.Advanced_Min}" />
|
||||
<DataGridTextColumn Width="Auto" MinWidth="110" Binding="{Binding Mean}" Header="{x:Static res:Strings.Advanced_Mean}" />
|
||||
<DataGridTextColumn Width="Auto" MinWidth="110" Binding="{Binding Max}" Header="{x:Static res:Strings.Advanced_Max}" />
|
||||
<DataGridTemplateColumn Width="*" CanUserResize="False" CanUserSort="False" IsReadOnly="True" controls:CellName.Path="Label" />
|
||||
</DataGrid.Columns>
|
||||
</DataGrid>
|
||||
|
||||
<ui:TextBlock Margin="0,20,0,0" AutomationProperties.HeadingLevel="Level2" FontTypography="Subtitle" Text="{x:Static res:Strings.Advanced_Chart_Header}" />
|
||||
<ui:TextBlock Margin="0,8,0,0" Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Session_NoSeries}" TextWrapping="Wrap"
|
||||
Visibility="{Binding ViewModel.SessionSeriesGone, Converter={StaticResource BoolToVis}}" />
|
||||
<StackPanel Margin="0,8,0,0" Orientation="Horizontal">
|
||||
<ui:TextBlock Margin="0,0,8,0" VerticalAlignment="Center" Text="{x:Static res:Strings.Advanced_Chart_Metric}" />
|
||||
<ComboBox MinWidth="360" AutomationProperties.Name="{x:Static res:Strings.A11y_Advanced_Metric}" DisplayMemberPath="Label"
|
||||
ItemsSource="{Binding ViewModel.SessionMetrics}" SelectedItem="{Binding ViewModel.SelectedSessionMetric, Mode=TwoWay}" />
|
||||
</StackPanel>
|
||||
<ui:TextBlock Margin="0,4,0,0" Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Chart_Band}" TextWrapping="Wrap"
|
||||
Visibility="{Binding ViewModel.SessionBand, Converter={StaticResource BoolToVis}}" />
|
||||
<ui:TextBlock Margin="0,12,0,0" Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Chart_Empty}"
|
||||
Visibility="{Binding ViewModel.SessionChartEmpty, Converter={StaticResource BoolToVis}}" />
|
||||
<charts:AdvancedSeriesChart x:Name="SessionChart" Height="320" Margin="0,8,0,0"
|
||||
Visibility="{Binding ViewModel.SessionChartEmpty, Converter={StaticResource InverseBoolToVis}}" />
|
||||
</StackPanel>
|
||||
</StackPanel>
|
||||
</TabItem>
|
||||
|
||||
<!-- Sources: the whole catalog, read or not, with the reason. -->
|
||||
<TabItem Header="{x:Static vm:AdvancedViewModel.TabSources}">
|
||||
<StackPanel Margin="0,12,0,0">
|
||||
<ui:TextBlock Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Sources_Intro}" TextWrapping="Wrap" />
|
||||
<ui:TextBlock Margin="0,8,0,0" Text="{Binding ViewModel.SourcesNow}" TextWrapping="Wrap"
|
||||
Visibility="{Binding ViewModel.SourcesNow, Converter={StaticResource NullToCollapsed}}" />
|
||||
<ui:TextBlock Margin="0,4,0,0" Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Advanced_Elevation_Hint}" TextWrapping="Wrap" />
|
||||
<DataGrid MaxHeight="560" Margin="0,12,0,0" AutoGenerateColumns="False" AutomationProperties.Name="{x:Static vm:AdvancedViewModel.TabSources}"
|
||||
CanUserAddRows="False" HeadersVisibility="Column" IsReadOnly="True" ItemsSource="{Binding ViewModel.SourceRows}" SelectionMode="Single">
|
||||
<DataGrid.Columns>
|
||||
<DataGridTextColumn Width="Auto" MinWidth="320" MaxWidth="520" Binding="{Binding Label}" Header="{x:Static res:Strings.Advanced_Col_Name}" />
|
||||
<DataGridTextColumn Width="Auto" MinWidth="120" Binding="{Binding Scope}" Header="{x:Static res:Strings.Advanced_Col_Scope}" />
|
||||
<DataGridTextColumn Width="Auto" MinWidth="140" Binding="{Binding Source}" Header="{x:Static res:Strings.Advanced_Col_Source}" />
|
||||
<DataGridTextColumn Width="Auto" MinWidth="260" Binding="{Binding Status}" Header="{x:Static res:Strings.Advanced_Col_Status}" />
|
||||
<DataGridTemplateColumn Width="*" CanUserResize="False" CanUserSort="False" IsReadOnly="True" controls:CellName.Path="Label" />
|
||||
</DataGrid.Columns>
|
||||
</DataGrid>
|
||||
</StackPanel>
|
||||
</TabItem>
|
||||
</TabControl>
|
||||
</StackPanel>
|
||||
</ScrollViewer>
|
||||
</Page>
|
||||
@@ -1,47 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
using FrameLedger.App.ViewModels;
|
||||
using Wpf.Ui.Abstractions.Controls;
|
||||
|
||||
namespace FrameLedger.App.Pages;
|
||||
|
||||
/// <summary>
|
||||
/// The Advanced page (owner decision D101; <c>08_UI</c> §Advanced). The view model asks the Agent about this PC only
|
||||
/// between <c>Loaded</c> and <c>Unloaded</c> — which is what lets the Agent stop reading sensors when no game runs
|
||||
/// and the page is closed (D107) — and the two charts are drawn here from the lines it presents.
|
||||
/// </summary>
|
||||
public partial class AdvancedPage : INavigableView<AdvancedViewModel>
|
||||
{
|
||||
public AdvancedPage(AdvancedViewModel viewModel)
|
||||
{
|
||||
ViewModel = viewModel ?? throw new ArgumentNullException(nameof(viewModel));
|
||||
DataContext = this;
|
||||
InitializeComponent();
|
||||
|
||||
ViewModel.LivePresented += OnLivePresented;
|
||||
ViewModel.SessionPresented += OnSessionPresented;
|
||||
OnLivePresented(this, EventArgs.Empty);
|
||||
OnSessionPresented(this, EventArgs.Empty);
|
||||
Loaded += (_, _) => ViewModel.Attach();
|
||||
Unloaded += (_, _) => ViewModel.Detach();
|
||||
IsVisibleChanged += (_, e) =>
|
||||
{
|
||||
// A window hidden to the tray is not on screen either: the Agent is not asked for a page nobody sees.
|
||||
if (e.NewValue is true && IsLoaded)
|
||||
{
|
||||
ViewModel.Attach();
|
||||
}
|
||||
else if (e.NewValue is false)
|
||||
{
|
||||
ViewModel.Detach();
|
||||
}
|
||||
};
|
||||
}
|
||||
|
||||
public AdvancedViewModel ViewModel { get; }
|
||||
|
||||
private void OnLivePresented(object? sender, EventArgs e) => LiveChart.Show(ViewModel.LiveLines, ViewModel.LiveUnit);
|
||||
|
||||
private void OnSessionPresented(object? sender, EventArgs e) => SessionChart.Show(ViewModel.SessionLines, ViewModel.SessionUnit);
|
||||
}
|
||||
@@ -214,19 +214,6 @@
|
||||
SpinButtonPlacementMode="Inline"
|
||||
Value="{Binding ViewModel.RetentionRawSessions, Mode=TwoWay}" />
|
||||
</ui:CardControl>
|
||||
<!-- Advanced metrics (owner decision D101, 2026-11-11): off by default, and off means nothing more is read or
|
||||
stored. The Agent reads it at each session's start, so it is off in a viewer like every setting it reads. -->
|
||||
<ui:CardControl Margin="0,8,0,0" Icon="{ui:SymbolIcon DataUsage24}">
|
||||
<ui:CardControl.Header>
|
||||
<StackPanel>
|
||||
<ui:TextBlock FontTypography="BodyStrong" Text="{x:Static res:Strings.Settings_Advanced_Label}" />
|
||||
<ui:TextBlock MaxWidth="560" HorizontalAlignment="Left" Style="{StaticResource SecondaryText}" Text="{x:Static res:Strings.Settings_Advanced_Body}" TextWrapping="Wrap" />
|
||||
</StackPanel>
|
||||
</ui:CardControl.Header>
|
||||
<ui:ToggleSwitch AutomationProperties.Name="{x:Static res:Strings.Settings_Advanced_Label}"
|
||||
IsChecked="{Binding ViewModel.AdvancedMetrics, Mode=TwoWay}"
|
||||
IsEnabled="{Binding ViewModel.ActsOnThisPc}" />
|
||||
</ui:CardControl>
|
||||
<!-- beta.12: "Record games launched outside FrameLedger" stood here; nothing read it (capture.background,
|
||||
06_DATA_MODEL §Settings registry), and with no way to start a game from the App "off" could only have
|
||||
meant recording nothing. Removed until a launch path exists. -->
|
||||
|
||||
@@ -1,26 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
namespace FrameLedger.App.Services;
|
||||
|
||||
/// <summary>What <see cref="AdvancedMachineFeed"/> last learnt from the Agent about "this PC, now" (owner decision D101).</summary>
|
||||
public enum AdvancedFeedState
|
||||
{
|
||||
/// <summary>Nobody watches: nothing is asked, and the Agent's reader is not held for the page.</summary>
|
||||
Stopped,
|
||||
|
||||
/// <summary>Asked, and the Agent's reader has not finished its first read.</summary>
|
||||
Waiting,
|
||||
|
||||
/// <summary>The last request was answered with a snapshot.</summary>
|
||||
Live,
|
||||
|
||||
/// <summary>The Agent answered that Advanced metrics is off: it reads nothing.</summary>
|
||||
Off,
|
||||
|
||||
/// <summary>No Agent answered — not connected, a viewer, a request that timed out or failed. What was shown stays, as old as it is.</summary>
|
||||
NoAgent,
|
||||
|
||||
/// <summary>The Agent is an older one that does not know the request.</summary>
|
||||
OlderAgent,
|
||||
}
|
||||
@@ -1,12 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
using System.Runtime.InteropServices;
|
||||
|
||||
namespace FrameLedger.App.Services;
|
||||
|
||||
/// <summary>One live reading of an advanced series: its value and when the Agent's reader read it.</summary>
|
||||
/// <param name="At">The tick it was read on, by the Agent's clock.</param>
|
||||
/// <param name="Value">The value, in the unit of its catalog entry.</param>
|
||||
[StructLayout(LayoutKind.Auto)]
|
||||
public readonly record struct AdvancedLivePoint(DateTimeOffset At, double Value);
|
||||
@@ -1,296 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
using FrameLedger.Application.Advanced;
|
||||
using FrameLedger.Infrastructure.Ipc;
|
||||
using FrameLedger.Shared.Ipc;
|
||||
using Serilog;
|
||||
|
||||
namespace FrameLedger.App.Services;
|
||||
|
||||
/// <summary>
|
||||
/// "This PC, now" for the Advanced page (owner decisions D101 and D107): while somebody watches, asks the Agent
|
||||
/// <c>GetAdvancedMachine</c> once a second and keeps what it answered — the facts, the last value of every series, a
|
||||
/// short history of each for the live charts, and which sources answer.
|
||||
/// </summary>
|
||||
/// <remarks>
|
||||
/// <para>
|
||||
/// <b>Watching is what makes the Agent read.</b> Each request keeps the Agent's shared reader running for a few
|
||||
/// seconds (<c>Application.Ipc.AdvancedMachineResponder</c>), so nothing is asked — and with no game running no sensor
|
||||
/// is read — unless a page holds <see cref="Watch"/>. The page lets go when it is unloaded or its window is hidden.
|
||||
/// </para>
|
||||
/// <para>
|
||||
/// <b>Nothing here is stored.</b> The history lives in memory, a few minutes long, and is gone with the App; what a
|
||||
/// session stores is the Agent's, in the ledger.
|
||||
/// </para>
|
||||
/// <para>
|
||||
/// It fires <see cref="Changed"/> on the thread pool, like the Agent's link; a view model marshals through
|
||||
/// <c>UiThread</c>.
|
||||
/// </para>
|
||||
/// </remarks>
|
||||
public sealed class AdvancedMachineFeed : IDisposable
|
||||
{
|
||||
/// <summary>How many points of each series are kept for the live charts: five minutes at one a second.</summary>
|
||||
public const int HistoryPoints = 300;
|
||||
|
||||
private static readonly TimeSpan _defaultInterval = TimeSpan.FromSeconds(1);
|
||||
|
||||
private readonly IAgentRequests _agent;
|
||||
private readonly TimeProvider _clock;
|
||||
private readonly TimeSpan _interval;
|
||||
private readonly Lock _gate = new();
|
||||
private readonly Dictionary<string, AdvancedLivePoint> _values = new(StringComparer.Ordinal);
|
||||
private readonly Dictionary<string, Queue<AdvancedLivePoint>> _history = new(StringComparer.Ordinal);
|
||||
|
||||
private IReadOnlyList<AdvancedFact> _facts = [];
|
||||
private string? _factsHash;
|
||||
private long _lastTick = long.MinValue;
|
||||
private IReadOnlyList<AdvancedSeriesInfo> _series = [];
|
||||
private AdvancedSources _sources = AdvancedSources.Unknown;
|
||||
private int _watchers;
|
||||
private CancellationTokenSource? _stop;
|
||||
private volatile AdvancedMachineView _current = AdvancedMachineView.Stopped;
|
||||
|
||||
/// <summary>Over the App's requests to the Agent — a viewer's link is never connected, and the feed says so.</summary>
|
||||
public AdvancedMachineFeed(IAgentRequests agent, TimeProvider clock, TimeSpan? interval = null)
|
||||
{
|
||||
_agent = agent ?? throw new ArgumentNullException(nameof(agent));
|
||||
_clock = clock ?? throw new ArgumentNullException(nameof(clock));
|
||||
_interval = interval ?? _defaultInterval;
|
||||
}
|
||||
|
||||
/// <summary>After every request while watched, and once when the last watcher lets go.</summary>
|
||||
public event EventHandler? Changed;
|
||||
|
||||
/// <summary>What was last learnt.</summary>
|
||||
public AdvancedMachineView Current => _current;
|
||||
|
||||
/// <summary>
|
||||
/// Asks the Agent once a second until the returned handle is disposed. The first watcher starts the asking and the
|
||||
/// last one stops it; a handle disposed twice counts once.
|
||||
/// </summary>
|
||||
public IDisposable Watch()
|
||||
{
|
||||
lock (_gate)
|
||||
{
|
||||
if (_watchers++ == 0)
|
||||
{
|
||||
var stop = new CancellationTokenSource();
|
||||
_stop = stop;
|
||||
_ = Task.Run(() => RunAsync(stop.Token), CancellationToken.None);
|
||||
}
|
||||
}
|
||||
|
||||
return new Watcher(this);
|
||||
}
|
||||
|
||||
/// <summary>The kept points of one series, oldest first; empty for a series never read.</summary>
|
||||
public IReadOnlyList<AdvancedLivePoint> HistoryOf(string series)
|
||||
{
|
||||
lock (_gate)
|
||||
{
|
||||
return _history.TryGetValue(series, out Queue<AdvancedLivePoint>? points) ? [.. points] : [];
|
||||
}
|
||||
}
|
||||
|
||||
/// <summary>One request and what it came to. The loop's body, and what a test calls.</summary>
|
||||
public async Task PollOnceAsync(CancellationToken ct = default)
|
||||
{
|
||||
AdvancedFeedState state;
|
||||
AdvancedMachineAck? ack = null;
|
||||
try
|
||||
{
|
||||
string? hash;
|
||||
lock (_gate)
|
||||
{
|
||||
hash = _factsHash;
|
||||
}
|
||||
|
||||
IpcEnvelope envelope = await _agent.RequestAsync(IpcMessageType.GetAdvancedMachine, new GetAdvancedMachineRequest(hash), ct).ConfigureAwait(false);
|
||||
ack = IpcCodec.Payload<AdvancedMachineAck>(envelope);
|
||||
state = ack switch
|
||||
{
|
||||
null => AdvancedFeedState.NoAgent,
|
||||
{ Ready: false } => AdvancedFeedState.Waiting,
|
||||
_ => AdvancedFeedState.Live,
|
||||
};
|
||||
}
|
||||
catch (IpcRequestException ex) when (string.Equals(ex.Code, IpcErrorCode.AdvancedOff, StringComparison.Ordinal))
|
||||
{
|
||||
state = AdvancedFeedState.Off;
|
||||
}
|
||||
catch (IpcRequestException ex) when (string.Equals(ex.Code, IpcErrorCode.UnknownType, StringComparison.Ordinal))
|
||||
{
|
||||
state = AdvancedFeedState.OlderAgent;
|
||||
}
|
||||
catch (IpcRequestException ex)
|
||||
{
|
||||
Log.Warning("advanced: GetAdvancedMachine failed ({Code}: {Message})", ex.Code, ex.Message);
|
||||
state = AdvancedFeedState.NoAgent;
|
||||
}
|
||||
catch (Exception ex) when (ex is InvalidOperationException or TimeoutException or System.IO.IOException)
|
||||
{
|
||||
// Not connected (a viewer never is), no answer in time, or the pipe dropped: the next second asks again.
|
||||
state = AdvancedFeedState.NoAgent;
|
||||
}
|
||||
|
||||
if (!ct.IsCancellationRequested)
|
||||
{
|
||||
// A request still in flight when the last watcher let go answers nobody: "stopped" was already said.
|
||||
Publish(state, ack);
|
||||
}
|
||||
}
|
||||
|
||||
public void Dispose()
|
||||
{
|
||||
CancellationTokenSource? stop;
|
||||
lock (_gate)
|
||||
{
|
||||
_watchers = 0;
|
||||
stop = _stop;
|
||||
_stop = null;
|
||||
}
|
||||
|
||||
stop?.Cancel();
|
||||
stop?.Dispose();
|
||||
}
|
||||
|
||||
private async Task RunAsync(CancellationToken ct)
|
||||
{
|
||||
using var timer = new PeriodicTimer(_interval, _clock);
|
||||
try
|
||||
{
|
||||
do
|
||||
{
|
||||
await PollOnceAsync(ct).ConfigureAwait(false);
|
||||
}
|
||||
while (await timer.WaitForNextTickAsync(ct).ConfigureAwait(false));
|
||||
}
|
||||
catch (OperationCanceledException)
|
||||
{
|
||||
// The last watcher let go.
|
||||
}
|
||||
}
|
||||
|
||||
private void Release()
|
||||
{
|
||||
CancellationTokenSource? stop;
|
||||
lock (_gate)
|
||||
{
|
||||
if (_watchers == 0 || --_watchers > 0)
|
||||
{
|
||||
return;
|
||||
}
|
||||
|
||||
stop = _stop;
|
||||
_stop = null;
|
||||
}
|
||||
|
||||
stop?.Cancel();
|
||||
stop?.Dispose();
|
||||
Publish(AdvancedFeedState.Stopped, ack: null);
|
||||
}
|
||||
|
||||
private void Publish(AdvancedFeedState state, AdvancedMachineAck? ack)
|
||||
{
|
||||
AdvancedMachineView view;
|
||||
lock (_gate)
|
||||
{
|
||||
if (state == AdvancedFeedState.Off)
|
||||
{
|
||||
// Off means nothing is read: what was shown is not "now" any more, and is not kept as if it were.
|
||||
Forget();
|
||||
}
|
||||
else if (state == AdvancedFeedState.Live && ack is not null)
|
||||
{
|
||||
Apply(ack);
|
||||
}
|
||||
|
||||
view = new AdvancedMachineView(
|
||||
state,
|
||||
_lastTick == long.MinValue ? null : DateTimeOffset.FromUnixTimeMilliseconds(_lastTick),
|
||||
_facts,
|
||||
new Dictionary<string, AdvancedLivePoint>(_values, StringComparer.Ordinal),
|
||||
_series,
|
||||
_sources);
|
||||
}
|
||||
|
||||
_current = view;
|
||||
Changed?.Invoke(this, EventArgs.Empty);
|
||||
}
|
||||
|
||||
private void Forget()
|
||||
{
|
||||
_values.Clear();
|
||||
_history.Clear();
|
||||
_facts = [];
|
||||
_factsHash = null;
|
||||
_lastTick = long.MinValue;
|
||||
_series = [];
|
||||
_sources = AdvancedSources.Unknown;
|
||||
}
|
||||
|
||||
private void Apply(AdvancedMachineAck ack)
|
||||
{
|
||||
if (ack.FactsJson is not null)
|
||||
{
|
||||
_facts = AdvancedJson.ParseFacts(ack.FactsJson);
|
||||
_factsHash = ack.FactsHash;
|
||||
}
|
||||
else if (!string.Equals(ack.FactsHash, _factsHash, StringComparison.Ordinal))
|
||||
{
|
||||
// The Agent holds other facts than the ones kept here and sent none: ask for them outright next time.
|
||||
_factsHash = null;
|
||||
}
|
||||
|
||||
_sources = new AdvancedSources(StatusOf(ack.Nvapi), ack.NvapiCode, StatusOf(ack.Sensors), StatusOf(ack.ElevatedSensors));
|
||||
var series = new List<AdvancedSeriesInfo>(ack.Series.Count);
|
||||
foreach (AdvancedSeriesLabel label in ack.Series)
|
||||
{
|
||||
series.Add(new AdvancedSeriesInfo(label.Series, label.MetricId, label.Label));
|
||||
}
|
||||
|
||||
_series = series;
|
||||
if (ack.TakenAtUnixMs == _lastTick)
|
||||
{
|
||||
// The same tick as a second ago - the reader's interval and this one are not in step: no new point.
|
||||
return;
|
||||
}
|
||||
|
||||
_lastTick = ack.TakenAtUnixMs;
|
||||
DateTimeOffset at = DateTimeOffset.FromUnixTimeMilliseconds(ack.TakenAtUnixMs);
|
||||
foreach (AdvancedReadingValue reading in ack.Readings)
|
||||
{
|
||||
var point = new AdvancedLivePoint(at, reading.Value);
|
||||
_values[reading.Series] = point;
|
||||
if (!_history.TryGetValue(reading.Series, out Queue<AdvancedLivePoint>? points))
|
||||
{
|
||||
points = new Queue<AdvancedLivePoint>();
|
||||
_history[reading.Series] = points;
|
||||
}
|
||||
|
||||
points.Enqueue(point);
|
||||
while (points.Count > HistoryPoints)
|
||||
{
|
||||
points.Dequeue();
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
/// <summary>A state by its name on the wire; a name this build does not know — a newer Agent's — is unknown, never a guess.</summary>
|
||||
private static AdvancedSourceStatus StatusOf(string? name) =>
|
||||
Enum.TryParse(name, ignoreCase: false, out AdvancedSourceStatus status) && Enum.IsDefined(status) ? status : AdvancedSourceStatus.Unknown;
|
||||
|
||||
private sealed class Watcher(AdvancedMachineFeed feed) : IDisposable
|
||||
{
|
||||
private int _released;
|
||||
|
||||
public void Dispose()
|
||||
{
|
||||
if (Interlocked.Exchange(ref _released, 1) == 0)
|
||||
{
|
||||
feed.Release();
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -1,37 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
using FrameLedger.Application.Advanced;
|
||||
|
||||
namespace FrameLedger.App.Services;
|
||||
|
||||
/// <summary>
|
||||
/// "This PC, now" as the App last learnt it from the Agent (owner decision D101). Immutable: the feed publishes a new
|
||||
/// one after each request and a page keeps whichever it took.
|
||||
/// </summary>
|
||||
/// <param name="State">What the last request came to.</param>
|
||||
/// <param name="TakenAt">The Agent's tick the newest values are of; null before the first snapshot.</param>
|
||||
/// <param name="Facts">The PC's facts, as the ledger would store them.</param>
|
||||
/// <param name="Values">
|
||||
/// The last value seen of each series, with the tick it was read on. A slow source is read every few ticks and its
|
||||
/// value is not repeated between, so "the value now" is the last one seen — and its age is part of it.
|
||||
/// </param>
|
||||
/// <param name="Series">The members of the catalog's families the reader has met, with the hardware's own labels.</param>
|
||||
/// <param name="Sources">Which sources answer, and why the others do not.</param>
|
||||
public sealed record AdvancedMachineView(
|
||||
AdvancedFeedState State,
|
||||
DateTimeOffset? TakenAt,
|
||||
IReadOnlyList<AdvancedFact> Facts,
|
||||
IReadOnlyDictionary<string, AdvancedLivePoint> Values,
|
||||
IReadOnlyList<AdvancedSeriesInfo> Series,
|
||||
AdvancedSources Sources)
|
||||
{
|
||||
/// <summary>Nothing asked, nothing known.</summary>
|
||||
public static AdvancedMachineView Stopped { get; } = new(
|
||||
AdvancedFeedState.Stopped,
|
||||
TakenAt: null,
|
||||
[],
|
||||
new Dictionary<string, AdvancedLivePoint>(StringComparer.Ordinal),
|
||||
[],
|
||||
AdvancedSources.Unknown);
|
||||
}
|
||||
@@ -1,39 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
using System.ComponentModel;
|
||||
|
||||
namespace FrameLedger.App.Services;
|
||||
|
||||
/// <summary>
|
||||
/// Whether the Advanced page is offered (owner decisions D101 and D105): its navigation item is there, and Ctrl+6
|
||||
/// opens it, only while this is on. Set at start from <c>telemetry.advanced</c> and again whenever Settings moves the
|
||||
/// switch; in a viewer it is also on when the copy holds a session recorded with the option on, since that is what a
|
||||
/// copy is opened to look at.
|
||||
/// </summary>
|
||||
/// <remarks>
|
||||
/// A static that XAML binds to, as <see cref="ContrastTheme"/> is: the shell's navigation item lives in the window's
|
||||
/// XAML, which a language change rebuilds, and a setting read once at start would not follow the switch.
|
||||
/// </remarks>
|
||||
public static class AdvancedOption
|
||||
{
|
||||
private static bool _isOn;
|
||||
|
||||
/// <summary>WPF's change notice for a static property: what a binding to <see cref="IsOn"/> listens to, weakly.</summary>
|
||||
public static event EventHandler<PropertyChangedEventArgs>? StaticPropertyChanged;
|
||||
|
||||
public static bool IsOn
|
||||
{
|
||||
get => _isOn;
|
||||
set
|
||||
{
|
||||
if (_isOn == value)
|
||||
{
|
||||
return;
|
||||
}
|
||||
|
||||
_isOn = value;
|
||||
StaticPropertyChanged?.Invoke(null, new PropertyChangedEventArgs(nameof(IsOn)));
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -1,26 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
namespace FrameLedger.App.Services;
|
||||
|
||||
/// <summary>
|
||||
/// The session the Advanced page should show when it next opens: a session's summary names it, then navigates. One
|
||||
/// slot, taken once — a page opened from the navigation pane afterwards shows its newest session as usual.
|
||||
/// </summary>
|
||||
public sealed class AdvancedSelection
|
||||
{
|
||||
private long _sessionId;
|
||||
|
||||
/// <summary>A session was asked for: a page already on screen takes it now.</summary>
|
||||
public event EventHandler? Requested;
|
||||
|
||||
/// <summary>Asks the page to show <paramref name="sessionId"/> - now if it is on screen, else the next time it opens.</summary>
|
||||
public void Request(long sessionId)
|
||||
{
|
||||
Interlocked.Exchange(ref _sessionId, sessionId);
|
||||
Requested?.Invoke(this, EventArgs.Empty);
|
||||
}
|
||||
|
||||
/// <summary>The session asked for since the last call, or null.</summary>
|
||||
public long? Take() => Interlocked.Exchange(ref _sessionId, 0) is > 0 and long id ? id : null;
|
||||
}
|
||||
@@ -41,7 +41,6 @@ public static class EmbeddedDocuments
|
||||
"guide/09-troubleshooting.md",
|
||||
"guide/10-glossary.md",
|
||||
"guide/11-alpha-builds.md",
|
||||
"guide/12-advanced-metrics.md",
|
||||
"guide/terms-in-plain-words.md",
|
||||
];
|
||||
|
||||
|
||||
@@ -60,7 +60,6 @@ public sealed class SessionSummaryOpener : ISessionSummaryOpener, ISessionWindow
|
||||
new TriStateOverridePrompt(() => window!.Dialogs),
|
||||
_services.GetRequiredService<IFileSaver>(),
|
||||
_services.GetRequiredService<IMessageStrip>());
|
||||
viewModel.ShowAdvanced = ShowAdvanced;
|
||||
window = new SessionSummaryWindow(viewModel, _services.GetRequiredService<IThemeApplier>(), _services.GetRequiredService<AppearanceSettings>())
|
||||
{
|
||||
Owner = _shell.Current,
|
||||
@@ -86,17 +85,6 @@ public sealed class SessionSummaryOpener : ISessionSummaryOpener, ISessionWindow
|
||||
}
|
||||
|
||||
/// <summary>The open window, back in front of the user: out of the taskbar first if it was minimised.</summary>
|
||||
/// <summary>The summary's "Advanced metrics…": the page is asked for that session, opened, and the main window brought forward.</summary>
|
||||
private void ShowAdvanced(long sessionId)
|
||||
{
|
||||
_services.GetRequiredService<AdvancedSelection>().Request(sessionId);
|
||||
_services.GetRequiredService<IPageNavigator>().Navigate<Pages.AdvancedPage>();
|
||||
if (_shell.Current is { } main)
|
||||
{
|
||||
BringForward(main);
|
||||
}
|
||||
}
|
||||
|
||||
private static void BringForward(Window window)
|
||||
{
|
||||
if (window.WindowState == WindowState.Minimized)
|
||||
|
||||
@@ -31,10 +31,6 @@ public static class ShellShortcuts
|
||||
case "4":
|
||||
navigator.Navigate<LogsPage>();
|
||||
return true;
|
||||
case "6" when AdvancedOption.IsOn:
|
||||
// Owner decision D105: the Advanced page keeps its number free while its option is off.
|
||||
navigator.Navigate<AdvancedPage>();
|
||||
return true;
|
||||
case "5":
|
||||
navigator.Navigate<SettingsPage>();
|
||||
return true;
|
||||
|
||||
@@ -6,30 +6,12 @@ using System.Diagnostics;
|
||||
|
||||
namespace FrameLedger.App.Services;
|
||||
|
||||
/// <summary>
|
||||
/// <see cref="IUrlOpener"/> through the shell (<c>UseShellExecute</c>), the same launch every other link in the App makes; a
|
||||
/// refusal is logged, never thrown. The shell runs whatever it is handed - a <c>file:</c> address is a program - so this
|
||||
/// opens web and mail links only, and says so itself rather than trusting each caller to have checked (2026-11-11: every
|
||||
/// caller passes one of the project's own pages or a link <c>MarkdownLinks</c> has already held to these schemes).
|
||||
/// </summary>
|
||||
/// <summary><see cref="IUrlOpener"/> through the shell (<c>UseShellExecute</c>), the same launch every other link in the App makes; a refusal is logged, never thrown.</summary>
|
||||
public sealed class ShellUrlOpener : IUrlOpener
|
||||
{
|
||||
/// <summary>Whether <paramref name="url"/> is a link the shell may be handed: absolute, and <c>http</c>, <c>https</c> or <c>mailto</c>.</summary>
|
||||
public static bool IsOpenable(Uri url)
|
||||
{
|
||||
ArgumentNullException.ThrowIfNull(url);
|
||||
return url.IsAbsoluteUri && url.Scheme is "https" or "http" or "mailto";
|
||||
}
|
||||
|
||||
public bool Open(Uri url)
|
||||
{
|
||||
ArgumentNullException.ThrowIfNull(url);
|
||||
if (!IsOpenable(url))
|
||||
{
|
||||
Serilog.Log.Warning("ui: not opened - {Url} is neither a web nor a mail link", url);
|
||||
return false;
|
||||
}
|
||||
|
||||
try
|
||||
{
|
||||
using Process? _ = Process.Start(new ProcessStartInfo(url.AbsoluteUri) { UseShellExecute = true });
|
||||
|
||||
Generated
-891
@@ -29,12 +29,9 @@ public static class Strings
|
||||
/// <summary>Every key, for an audit that walks them.</summary>
|
||||
public static IReadOnlyList<string> Keys { get; } =
|
||||
[
|
||||
nameof(A11y_Advanced_Metric),
|
||||
nameof(A11y_Advanced_Session),
|
||||
nameof(A11y_Agent_Connected),
|
||||
nameof(A11y_Change_Format),
|
||||
nameof(A11y_ChangeMarker_Format),
|
||||
nameof(A11y_Chart_Advanced),
|
||||
nameof(A11y_Chart_Clocks),
|
||||
nameof(A11y_Chart_Compare),
|
||||
nameof(A11y_Chart_ControlType),
|
||||
@@ -48,7 +45,6 @@ public static class Strings
|
||||
nameof(A11y_Chart_Temps),
|
||||
nameof(A11y_Chart_Trend),
|
||||
nameof(A11y_Chart_Vram),
|
||||
nameof(A11y_ChartData_Advanced),
|
||||
nameof(A11y_ChartData_Compare),
|
||||
nameof(A11y_ChartData_Latency),
|
||||
nameof(A11y_ChartData_Sessions),
|
||||
@@ -106,295 +102,6 @@ public static class Strings
|
||||
nameof(AddGame_Dialog_Title),
|
||||
nameof(AddGame_Failed_Format),
|
||||
nameof(AddGame_Filter),
|
||||
nameof(Adv_ffx_framegen_config),
|
||||
nameof(Adv_ffx_memory_usage),
|
||||
nameof(Adv_ffx_upscale_depth),
|
||||
nameof(Adv_ffx_upscale_exposure),
|
||||
nameof(Adv_ffx_upscale_flags),
|
||||
nameof(Adv_ffx_upscale_frame_time_delta),
|
||||
nameof(Adv_ffx_upscale_jitter),
|
||||
nameof(Adv_ffx_upscale_sharpening),
|
||||
nameof(Adv_lhm_battery),
|
||||
nameof(Adv_lhm_board_fan),
|
||||
nameof(Adv_lhm_board_fan_control),
|
||||
nameof(Adv_lhm_board_model),
|
||||
nameof(Adv_lhm_board_sensor_chip),
|
||||
nameof(Adv_lhm_board_temperature),
|
||||
nameof(Adv_lhm_board_voltage),
|
||||
nameof(Adv_lhm_controller),
|
||||
nameof(Adv_lhm_cpu_clock),
|
||||
nameof(Adv_lhm_cpu_load),
|
||||
nameof(Adv_lhm_cpu_power),
|
||||
nameof(Adv_lhm_cpu_temperature),
|
||||
nameof(Adv_lhm_cpu_voltage),
|
||||
nameof(Adv_lhm_gpu_clock),
|
||||
nameof(Adv_lhm_gpu_current),
|
||||
nameof(Adv_lhm_gpu_fan),
|
||||
nameof(Adv_lhm_gpu_fan_control),
|
||||
nameof(Adv_lhm_gpu_load),
|
||||
nameof(Adv_lhm_gpu_memory),
|
||||
nameof(Adv_lhm_gpu_power),
|
||||
nameof(Adv_lhm_gpu_temperature),
|
||||
nameof(Adv_lhm_gpu_throughput),
|
||||
nameof(Adv_lhm_gpu_voltage),
|
||||
nameof(Adv_lhm_memory_load),
|
||||
nameof(Adv_lhm_memory_modules),
|
||||
nameof(Adv_lhm_memory_temperature),
|
||||
nameof(Adv_lhm_psu),
|
||||
nameof(Adv_lhm_storage_models),
|
||||
nameof(Adv_lhm_storage_temperature),
|
||||
nameof(Adv_ngx_parameters),
|
||||
nameof(Adv_nvapi_clock_video),
|
||||
nameof(Adv_nvapi_display_adaptive_sync_off),
|
||||
nameof(Adv_nvapi_display_edid),
|
||||
nameof(Adv_nvapi_display_hdr_formats),
|
||||
nameof(Adv_nvapi_display_luminance_max),
|
||||
nameof(Adv_nvapi_display_luminance_max_frame_average),
|
||||
nameof(Adv_nvapi_display_luminance_min),
|
||||
nameof(Adv_nvapi_display_max_frame_interval),
|
||||
nameof(Adv_nvapi_display_vrr_support),
|
||||
nameof(Adv_nvapi_driver_base_branch),
|
||||
nameof(Adv_nvapi_driver_chipset),
|
||||
nameof(Adv_nvapi_driver_dch),
|
||||
nameof(Adv_nvapi_driver_global_profile),
|
||||
nameof(Adv_nvapi_driver_interface_version),
|
||||
nameof(Adv_nvapi_driver_package),
|
||||
nameof(Adv_nvapi_encoder_fps),
|
||||
nameof(Adv_nvapi_encoder_latency),
|
||||
nameof(Adv_nvapi_encoder_session_processes),
|
||||
nameof(Adv_nvapi_encoder_sessions),
|
||||
nameof(Adv_nvapi_gpu_architecture),
|
||||
nameof(Adv_nvapi_gpu_board_serial),
|
||||
nameof(Adv_nvapi_gpu_bus_type),
|
||||
nameof(Adv_nvapi_gpu_clock_base_core),
|
||||
nameof(Adv_nvapi_gpu_clock_base_memory),
|
||||
nameof(Adv_nvapi_gpu_clock_boost_core),
|
||||
nameof(Adv_nvapi_gpu_clock_boost_memory),
|
||||
nameof(Adv_nvapi_gpu_core_count),
|
||||
nameof(Adv_nvapi_gpu_external),
|
||||
nameof(Adv_nvapi_gpu_fan_duty),
|
||||
nameof(Adv_nvapi_gpu_pci_ids),
|
||||
nameof(Adv_nvapi_gpu_power),
|
||||
nameof(Adv_nvapi_gpu_ram_bus_width),
|
||||
nameof(Adv_nvapi_gpu_ram_type),
|
||||
nameof(Adv_nvapi_gpu_rt_cores),
|
||||
nameof(Adv_nvapi_gpu_system_type),
|
||||
nameof(Adv_nvapi_gpu_temp_default_max),
|
||||
nameof(Adv_nvapi_gpu_tensor_cores),
|
||||
nameof(Adv_nvapi_gpu_type),
|
||||
nameof(Adv_nvapi_gpu_uuid),
|
||||
nameof(Adv_nvapi_gpu_vbios_version),
|
||||
nameof(Adv_nvapi_gpu_voltage),
|
||||
nameof(Adv_nvapi_limit_ac_battery),
|
||||
nameof(Adv_nvapi_limit_api),
|
||||
nameof(Adv_nvapi_limit_insufficient_power),
|
||||
nameof(Adv_nvapi_load_bus),
|
||||
nameof(Adv_nvapi_load_framebuffer),
|
||||
nameof(Adv_nvapi_load_video),
|
||||
nameof(Adv_nvapi_pstate),
|
||||
nameof(Adv_nvapi_reflex_frame_report),
|
||||
nameof(Adv_nvapi_reflex_gpu_times),
|
||||
nameof(Adv_nvapi_reflex_mode),
|
||||
nameof(Adv_nvapi_reflex_sleep_status),
|
||||
nameof(Adv_nvapi_session_driver_profile),
|
||||
nameof(Adv_nvapi_session_source_colorspace),
|
||||
nameof(Adv_nvapi_session_vrr_display_mode),
|
||||
nameof(Adv_nvapi_session_vrr_enabled),
|
||||
nameof(Adv_nvapi_session_vrr_possible),
|
||||
nameof(Adv_nvapi_session_vrr_requested),
|
||||
nameof(Adv_nvapi_temp_board),
|
||||
nameof(Adv_nvapi_temp_power_supply),
|
||||
nameof(Adv_nvapi_vram_available),
|
||||
nameof(Adv_nvapi_vram_dedicated),
|
||||
nameof(Adv_nvapi_vram_dedicated_available),
|
||||
nameof(Adv_nvapi_vram_eviction_count),
|
||||
nameof(Adv_nvapi_vram_evictions_size),
|
||||
nameof(Adv_nvapi_vram_framebuffer_physical),
|
||||
nameof(Adv_nvapi_vram_framebuffer_virtual),
|
||||
nameof(Adv_nvapi_vram_in_use),
|
||||
nameof(Adv_nvapi_vram_promotion_count),
|
||||
nameof(Adv_nvapi_vram_promotions_size),
|
||||
nameof(Adv_nvapi_vram_shared),
|
||||
nameof(Adv_nvapi_vram_system),
|
||||
nameof(Adv_sl_constants_camera),
|
||||
nameof(Adv_sl_constants_depth),
|
||||
nameof(Adv_sl_constants_jitter),
|
||||
nameof(Adv_sl_constants_motion_vectors),
|
||||
nameof(Adv_sl_constants_projection),
|
||||
nameof(Adv_sl_constants_resets),
|
||||
nameof(Adv_sl_deepdvc_options),
|
||||
nameof(Adv_sl_dlss_alpha_upscaling),
|
||||
nameof(Adv_sl_dlss_auto_exposure),
|
||||
nameof(Adv_sl_dlss_exposure),
|
||||
nameof(Adv_sl_dlss_hdr_input),
|
||||
nameof(Adv_sl_dlss_optimal_settings),
|
||||
nameof(Adv_sl_dlss_output_size),
|
||||
nameof(Adv_sl_dlss_presets),
|
||||
nameof(Adv_sl_dlss_vram_estimate),
|
||||
nameof(Adv_sl_dlssd_options),
|
||||
nameof(Adv_sl_dlssg_frames_presented),
|
||||
nameof(Adv_sl_dlssg_options),
|
||||
nameof(Adv_sl_dlssg_state),
|
||||
nameof(Adv_sl_dlssg_vram_estimate),
|
||||
nameof(Adv_sl_feature_lifecycle),
|
||||
nameof(Adv_sl_feature_requirements),
|
||||
nameof(Adv_sl_feature_support),
|
||||
nameof(Adv_sl_feature_versions),
|
||||
nameof(Adv_sl_init_preferences),
|
||||
nameof(Adv_sl_nis_options),
|
||||
nameof(Adv_sl_nvperf),
|
||||
nameof(Adv_sl_pcl_markers),
|
||||
nameof(Adv_sl_reflex_state),
|
||||
nameof(Adv_xess_options),
|
||||
nameof(Advanced_Chart_Band),
|
||||
nameof(Advanced_Chart_Empty),
|
||||
nameof(Advanced_Chart_Header),
|
||||
nameof(Advanced_Chart_LiveNote),
|
||||
nameof(Advanced_Chart_Metric),
|
||||
nameof(Advanced_Chart_Seconds),
|
||||
nameof(Advanced_Chart_Time),
|
||||
nameof(Advanced_Col_Name),
|
||||
nameof(Advanced_Col_ReadAt),
|
||||
nameof(Advanced_Col_Samples),
|
||||
nameof(Advanced_Col_Scope),
|
||||
nameof(Advanced_Col_Source),
|
||||
nameof(Advanced_Col_Status),
|
||||
nameof(Advanced_Col_Value),
|
||||
nameof(Advanced_Elevation_Hint),
|
||||
nameof(Advanced_Facts_Header),
|
||||
nameof(Advanced_Header),
|
||||
nameof(Advanced_InGameCallsLine),
|
||||
nameof(Advanced_InGameDriverLine),
|
||||
nameof(Advanced_InGameFeatureCallsLine),
|
||||
nameof(Advanced_InGameLine),
|
||||
nameof(Advanced_InGameMoreCallsLine),
|
||||
nameof(Advanced_Machine_Intro),
|
||||
nameof(Advanced_Max),
|
||||
nameof(Advanced_Mean),
|
||||
nameof(Advanced_Min),
|
||||
nameof(Advanced_Now_Header),
|
||||
nameof(Advanced_Session_Empty),
|
||||
nameof(Advanced_Session_Facts),
|
||||
nameof(Advanced_Session_NoSeries),
|
||||
nameof(Advanced_Session_NoStats),
|
||||
nameof(Advanced_Session_Pick),
|
||||
nameof(Advanced_Session_Stats),
|
||||
nameof(Advanced_Sources_Intro),
|
||||
nameof(Advanced_SourcesLine),
|
||||
nameof(Advanced_State_Live),
|
||||
nameof(Advanced_State_NoAgent),
|
||||
nameof(Advanced_State_Off),
|
||||
nameof(Advanced_State_OlderAgent),
|
||||
nameof(Advanced_State_Viewer),
|
||||
nameof(Advanced_State_Waiting),
|
||||
nameof(Advanced_Status_InGame),
|
||||
nameof(Advanced_Status_InGameDriver),
|
||||
nameof(Advanced_Status_Read),
|
||||
nameof(Advanced_Status_Readable),
|
||||
nameof(Advanced_Status_SourceSilent),
|
||||
nameof(Advanced_Tab_Machine),
|
||||
nameof(Advanced_Tab_Session),
|
||||
nameof(Advanced_Tab_Sources),
|
||||
nameof(AdvDriverRead_Error),
|
||||
nameof(AdvDriverRead_Faulted),
|
||||
nameof(AdvDriverRead_NoDirect3D12),
|
||||
nameof(AdvDriverRead_NoGetter),
|
||||
nameof(AdvDriverRead_NoModule),
|
||||
nameof(AdvDriverRead_NothingReported),
|
||||
nameof(AdvDriverRead_Read),
|
||||
nameof(AdvDriverRead_Refused),
|
||||
nameof(AdvDriverRead_Slow),
|
||||
nameof(AdvDriverRead_Stalled),
|
||||
nameof(AdvDriverRead_Unknown),
|
||||
nameof(AdvGroup_Board),
|
||||
nameof(AdvGroup_Cpu),
|
||||
nameof(AdvGroup_Display),
|
||||
nameof(AdvGroup_Driver),
|
||||
nameof(AdvGroup_FrameGeneration),
|
||||
nameof(AdvGroup_Gpu),
|
||||
nameof(AdvGroup_GpuMemory),
|
||||
nameof(AdvGroup_Latency),
|
||||
nameof(AdvGroup_Memory),
|
||||
nameof(AdvGroup_Storage),
|
||||
nameof(AdvGroup_Upscaling),
|
||||
nameof(AdvInGame_NothingSeen),
|
||||
nameof(AdvInGame_NotHooked),
|
||||
nameof(AdvInGame_Reading),
|
||||
nameof(AdvInGame_Unknown),
|
||||
nameof(AdvInGameCall_NeverCalled),
|
||||
nameof(AdvInGameCall_NotAskedAgain),
|
||||
nameof(AdvInGameCall_NotHooked),
|
||||
nameof(AdvInGameCall_Read),
|
||||
nameof(AdvInGameCall_Unknown),
|
||||
nameof(AdvReach_BeforeAttach),
|
||||
nameof(AdvReach_Deferred),
|
||||
nameof(AdvReach_Game),
|
||||
nameof(AdvReach_HookedCall),
|
||||
nameof(AdvReach_Identifier),
|
||||
nameof(AdvReach_Licence),
|
||||
nameof(AdvReach_NewHook),
|
||||
nameof(AdvReach_NotInHeaders),
|
||||
nameof(AdvReach_PlayerState),
|
||||
nameof(AdvReach_Refused),
|
||||
nameof(AdvReach_RefusedRoute),
|
||||
nameof(AdvReach_Spike),
|
||||
nameof(AdvScope_MachineFact),
|
||||
nameof(AdvScope_Series),
|
||||
nameof(AdvScope_SessionFact),
|
||||
nameof(AdvSource_Faulted),
|
||||
nameof(AdvSource_NotElevated),
|
||||
nameof(AdvSource_NotPresent),
|
||||
nameof(AdvSource_PawnIoMissing),
|
||||
nameof(AdvSource_Reading),
|
||||
nameof(AdvSource_Unknown),
|
||||
nameof(AdvToken_active_render),
|
||||
nameof(AdvToken_adaptive_sync),
|
||||
nameof(AdvToken_agp),
|
||||
nameof(AdvToken_axi),
|
||||
nameof(AdvToken_bt2100_pq),
|
||||
nameof(AdvToken_desktop),
|
||||
nameof(AdvToken_discrete),
|
||||
nameof(AdvToken_dolby_vision),
|
||||
nameof(AdvToken_draw_debug_view),
|
||||
nameof(AdvToken_driver),
|
||||
nameof(AdvToken_driver_default),
|
||||
nameof(AdvToken_edr),
|
||||
nameof(AdvToken_fpci),
|
||||
nameof(AdvToken_frame_time),
|
||||
nameof(AdvToken_game_ready),
|
||||
nameof(AdvToken_gpu_render),
|
||||
nameof(AdvToken_gsync_module),
|
||||
nameof(AdvToken_hdr10),
|
||||
nameof(AdvToken_hdr10_plus),
|
||||
nameof(AdvToken_hdr10_plus_gaming),
|
||||
nameof(AdvToken_integrated),
|
||||
nameof(AdvToken_laptop),
|
||||
nameof(AdvToken_no_profile_for_game),
|
||||
nameof(AdvToken_non_linear_color_pq),
|
||||
nameof(AdvToken_non_linear_color_srgb),
|
||||
nameof(AdvToken_none),
|
||||
nameof(AdvToken_not_a_number),
|
||||
nameof(AdvToken_not_radians),
|
||||
nameof(AdvToken_not_supported),
|
||||
nameof(AdvToken_off),
|
||||
nameof(AdvToken_on),
|
||||
nameof(AdvToken_on_and_off),
|
||||
nameof(AdvToken_os_queue),
|
||||
nameof(AdvToken_pci),
|
||||
nameof(AdvToken_pci_express),
|
||||
nameof(AdvToken_present),
|
||||
nameof(AdvToken_render_submit),
|
||||
nameof(AdvToken_rtx_new_feature),
|
||||
nameof(AdvToken_rtx_production),
|
||||
nameof(AdvToken_scrgb_linear),
|
||||
nameof(AdvToken_simulation),
|
||||
nameof(AdvToken_srgb),
|
||||
nameof(AdvToken_studio),
|
||||
nameof(AdvToken_total),
|
||||
nameof(AdvToken_ulmb),
|
||||
nameof(AdvToken_usable_now),
|
||||
nameof(AdvToken_user_set),
|
||||
nameof(AdvToken_variable_refresh),
|
||||
nameof(Agent_Banner_Missing_Body),
|
||||
nameof(Agent_Banner_Offline_Body),
|
||||
nameof(Agent_Banner_Offline_Title),
|
||||
@@ -1094,7 +801,6 @@ public static class Strings
|
||||
nameof(Menu_Tools_OpenDataFolder),
|
||||
nameof(Menu_Tools_UpdateRules),
|
||||
nameof(Menu_Tools_VulkanLayer),
|
||||
nameof(Nav_Advanced),
|
||||
nameof(Nav_Compare),
|
||||
nameof(Nav_Dashboard),
|
||||
nameof(Nav_Games),
|
||||
@@ -1236,8 +942,6 @@ public static class Strings
|
||||
nameof(Sessions_GameRamWs_Cell_Format),
|
||||
nameof(Sessions_GameRamWs_Tooltip_Format),
|
||||
nameof(Sessions_GameVram_Tooltip_Format),
|
||||
nameof(Settings_Advanced_Body),
|
||||
nameof(Settings_Advanced_Label),
|
||||
nameof(Settings_Agent_Elevated),
|
||||
nameof(Settings_Agent_Elevation_Body),
|
||||
nameof(Settings_Agent_Elevation_Label),
|
||||
@@ -1358,7 +1062,6 @@ public static class Strings
|
||||
nameof(Store_Gog_Format),
|
||||
nameof(Store_Steam_Format),
|
||||
nameof(Store_Xbox_Format),
|
||||
nameof(Summary_Advanced_Button),
|
||||
nameof(Summary_Annotations_Header),
|
||||
nameof(Summary_Crash_Body),
|
||||
nameof(Summary_Crash_Title),
|
||||
@@ -1562,18 +1265,12 @@ public static class Strings
|
||||
nameof(Viewer_ChangesThisPc_Off),
|
||||
];
|
||||
|
||||
public static string A11y_Advanced_Metric => ResourceManager.GetString(nameof(A11y_Advanced_Metric), Culture) ?? nameof(A11y_Advanced_Metric);
|
||||
|
||||
public static string A11y_Advanced_Session => ResourceManager.GetString(nameof(A11y_Advanced_Session), Culture) ?? nameof(A11y_Advanced_Session);
|
||||
|
||||
public static string A11y_Agent_Connected => ResourceManager.GetString(nameof(A11y_Agent_Connected), Culture) ?? nameof(A11y_Agent_Connected);
|
||||
|
||||
public static string A11y_Change_Format => ResourceManager.GetString(nameof(A11y_Change_Format), Culture) ?? nameof(A11y_Change_Format);
|
||||
|
||||
public static string A11y_ChangeMarker_Format => ResourceManager.GetString(nameof(A11y_ChangeMarker_Format), Culture) ?? nameof(A11y_ChangeMarker_Format);
|
||||
|
||||
public static string A11y_Chart_Advanced => ResourceManager.GetString(nameof(A11y_Chart_Advanced), Culture) ?? nameof(A11y_Chart_Advanced);
|
||||
|
||||
public static string A11y_Chart_Clocks => ResourceManager.GetString(nameof(A11y_Chart_Clocks), Culture) ?? nameof(A11y_Chart_Clocks);
|
||||
|
||||
public static string A11y_Chart_Compare => ResourceManager.GetString(nameof(A11y_Chart_Compare), Culture) ?? nameof(A11y_Chart_Compare);
|
||||
@@ -1600,8 +1297,6 @@ public static class Strings
|
||||
|
||||
public static string A11y_Chart_Vram => ResourceManager.GetString(nameof(A11y_Chart_Vram), Culture) ?? nameof(A11y_Chart_Vram);
|
||||
|
||||
public static string A11y_ChartData_Advanced => ResourceManager.GetString(nameof(A11y_ChartData_Advanced), Culture) ?? nameof(A11y_ChartData_Advanced);
|
||||
|
||||
public static string A11y_ChartData_Compare => ResourceManager.GetString(nameof(A11y_ChartData_Compare), Culture) ?? nameof(A11y_ChartData_Compare);
|
||||
|
||||
public static string A11y_ChartData_Latency => ResourceManager.GetString(nameof(A11y_ChartData_Latency), Culture) ?? nameof(A11y_ChartData_Latency);
|
||||
@@ -1716,584 +1411,6 @@ public static class Strings
|
||||
|
||||
public static string AddGame_Filter => ResourceManager.GetString(nameof(AddGame_Filter), Culture) ?? nameof(AddGame_Filter);
|
||||
|
||||
public static string Adv_ffx_framegen_config => ResourceManager.GetString(nameof(Adv_ffx_framegen_config), Culture) ?? nameof(Adv_ffx_framegen_config);
|
||||
|
||||
public static string Adv_ffx_memory_usage => ResourceManager.GetString(nameof(Adv_ffx_memory_usage), Culture) ?? nameof(Adv_ffx_memory_usage);
|
||||
|
||||
public static string Adv_ffx_upscale_depth => ResourceManager.GetString(nameof(Adv_ffx_upscale_depth), Culture) ?? nameof(Adv_ffx_upscale_depth);
|
||||
|
||||
public static string Adv_ffx_upscale_exposure => ResourceManager.GetString(nameof(Adv_ffx_upscale_exposure), Culture) ?? nameof(Adv_ffx_upscale_exposure);
|
||||
|
||||
public static string Adv_ffx_upscale_flags => ResourceManager.GetString(nameof(Adv_ffx_upscale_flags), Culture) ?? nameof(Adv_ffx_upscale_flags);
|
||||
|
||||
public static string Adv_ffx_upscale_frame_time_delta => ResourceManager.GetString(nameof(Adv_ffx_upscale_frame_time_delta), Culture) ?? nameof(Adv_ffx_upscale_frame_time_delta);
|
||||
|
||||
public static string Adv_ffx_upscale_jitter => ResourceManager.GetString(nameof(Adv_ffx_upscale_jitter), Culture) ?? nameof(Adv_ffx_upscale_jitter);
|
||||
|
||||
public static string Adv_ffx_upscale_sharpening => ResourceManager.GetString(nameof(Adv_ffx_upscale_sharpening), Culture) ?? nameof(Adv_ffx_upscale_sharpening);
|
||||
|
||||
public static string Adv_lhm_battery => ResourceManager.GetString(nameof(Adv_lhm_battery), Culture) ?? nameof(Adv_lhm_battery);
|
||||
|
||||
public static string Adv_lhm_board_fan => ResourceManager.GetString(nameof(Adv_lhm_board_fan), Culture) ?? nameof(Adv_lhm_board_fan);
|
||||
|
||||
public static string Adv_lhm_board_fan_control => ResourceManager.GetString(nameof(Adv_lhm_board_fan_control), Culture) ?? nameof(Adv_lhm_board_fan_control);
|
||||
|
||||
public static string Adv_lhm_board_model => ResourceManager.GetString(nameof(Adv_lhm_board_model), Culture) ?? nameof(Adv_lhm_board_model);
|
||||
|
||||
public static string Adv_lhm_board_sensor_chip => ResourceManager.GetString(nameof(Adv_lhm_board_sensor_chip), Culture) ?? nameof(Adv_lhm_board_sensor_chip);
|
||||
|
||||
public static string Adv_lhm_board_temperature => ResourceManager.GetString(nameof(Adv_lhm_board_temperature), Culture) ?? nameof(Adv_lhm_board_temperature);
|
||||
|
||||
public static string Adv_lhm_board_voltage => ResourceManager.GetString(nameof(Adv_lhm_board_voltage), Culture) ?? nameof(Adv_lhm_board_voltage);
|
||||
|
||||
public static string Adv_lhm_controller => ResourceManager.GetString(nameof(Adv_lhm_controller), Culture) ?? nameof(Adv_lhm_controller);
|
||||
|
||||
public static string Adv_lhm_cpu_clock => ResourceManager.GetString(nameof(Adv_lhm_cpu_clock), Culture) ?? nameof(Adv_lhm_cpu_clock);
|
||||
|
||||
public static string Adv_lhm_cpu_load => ResourceManager.GetString(nameof(Adv_lhm_cpu_load), Culture) ?? nameof(Adv_lhm_cpu_load);
|
||||
|
||||
public static string Adv_lhm_cpu_power => ResourceManager.GetString(nameof(Adv_lhm_cpu_power), Culture) ?? nameof(Adv_lhm_cpu_power);
|
||||
|
||||
public static string Adv_lhm_cpu_temperature => ResourceManager.GetString(nameof(Adv_lhm_cpu_temperature), Culture) ?? nameof(Adv_lhm_cpu_temperature);
|
||||
|
||||
public static string Adv_lhm_cpu_voltage => ResourceManager.GetString(nameof(Adv_lhm_cpu_voltage), Culture) ?? nameof(Adv_lhm_cpu_voltage);
|
||||
|
||||
public static string Adv_lhm_gpu_clock => ResourceManager.GetString(nameof(Adv_lhm_gpu_clock), Culture) ?? nameof(Adv_lhm_gpu_clock);
|
||||
|
||||
public static string Adv_lhm_gpu_current => ResourceManager.GetString(nameof(Adv_lhm_gpu_current), Culture) ?? nameof(Adv_lhm_gpu_current);
|
||||
|
||||
public static string Adv_lhm_gpu_fan => ResourceManager.GetString(nameof(Adv_lhm_gpu_fan), Culture) ?? nameof(Adv_lhm_gpu_fan);
|
||||
|
||||
public static string Adv_lhm_gpu_fan_control => ResourceManager.GetString(nameof(Adv_lhm_gpu_fan_control), Culture) ?? nameof(Adv_lhm_gpu_fan_control);
|
||||
|
||||
public static string Adv_lhm_gpu_load => ResourceManager.GetString(nameof(Adv_lhm_gpu_load), Culture) ?? nameof(Adv_lhm_gpu_load);
|
||||
|
||||
public static string Adv_lhm_gpu_memory => ResourceManager.GetString(nameof(Adv_lhm_gpu_memory), Culture) ?? nameof(Adv_lhm_gpu_memory);
|
||||
|
||||
public static string Adv_lhm_gpu_power => ResourceManager.GetString(nameof(Adv_lhm_gpu_power), Culture) ?? nameof(Adv_lhm_gpu_power);
|
||||
|
||||
public static string Adv_lhm_gpu_temperature => ResourceManager.GetString(nameof(Adv_lhm_gpu_temperature), Culture) ?? nameof(Adv_lhm_gpu_temperature);
|
||||
|
||||
public static string Adv_lhm_gpu_throughput => ResourceManager.GetString(nameof(Adv_lhm_gpu_throughput), Culture) ?? nameof(Adv_lhm_gpu_throughput);
|
||||
|
||||
public static string Adv_lhm_gpu_voltage => ResourceManager.GetString(nameof(Adv_lhm_gpu_voltage), Culture) ?? nameof(Adv_lhm_gpu_voltage);
|
||||
|
||||
public static string Adv_lhm_memory_load => ResourceManager.GetString(nameof(Adv_lhm_memory_load), Culture) ?? nameof(Adv_lhm_memory_load);
|
||||
|
||||
public static string Adv_lhm_memory_modules => ResourceManager.GetString(nameof(Adv_lhm_memory_modules), Culture) ?? nameof(Adv_lhm_memory_modules);
|
||||
|
||||
public static string Adv_lhm_memory_temperature => ResourceManager.GetString(nameof(Adv_lhm_memory_temperature), Culture) ?? nameof(Adv_lhm_memory_temperature);
|
||||
|
||||
public static string Adv_lhm_psu => ResourceManager.GetString(nameof(Adv_lhm_psu), Culture) ?? nameof(Adv_lhm_psu);
|
||||
|
||||
public static string Adv_lhm_storage_models => ResourceManager.GetString(nameof(Adv_lhm_storage_models), Culture) ?? nameof(Adv_lhm_storage_models);
|
||||
|
||||
public static string Adv_lhm_storage_temperature => ResourceManager.GetString(nameof(Adv_lhm_storage_temperature), Culture) ?? nameof(Adv_lhm_storage_temperature);
|
||||
|
||||
public static string Adv_ngx_parameters => ResourceManager.GetString(nameof(Adv_ngx_parameters), Culture) ?? nameof(Adv_ngx_parameters);
|
||||
|
||||
public static string Adv_nvapi_clock_video => ResourceManager.GetString(nameof(Adv_nvapi_clock_video), Culture) ?? nameof(Adv_nvapi_clock_video);
|
||||
|
||||
public static string Adv_nvapi_display_adaptive_sync_off => ResourceManager.GetString(nameof(Adv_nvapi_display_adaptive_sync_off), Culture) ?? nameof(Adv_nvapi_display_adaptive_sync_off);
|
||||
|
||||
public static string Adv_nvapi_display_edid => ResourceManager.GetString(nameof(Adv_nvapi_display_edid), Culture) ?? nameof(Adv_nvapi_display_edid);
|
||||
|
||||
public static string Adv_nvapi_display_hdr_formats => ResourceManager.GetString(nameof(Adv_nvapi_display_hdr_formats), Culture) ?? nameof(Adv_nvapi_display_hdr_formats);
|
||||
|
||||
public static string Adv_nvapi_display_luminance_max => ResourceManager.GetString(nameof(Adv_nvapi_display_luminance_max), Culture) ?? nameof(Adv_nvapi_display_luminance_max);
|
||||
|
||||
public static string Adv_nvapi_display_luminance_max_frame_average => ResourceManager.GetString(nameof(Adv_nvapi_display_luminance_max_frame_average), Culture) ?? nameof(Adv_nvapi_display_luminance_max_frame_average);
|
||||
|
||||
public static string Adv_nvapi_display_luminance_min => ResourceManager.GetString(nameof(Adv_nvapi_display_luminance_min), Culture) ?? nameof(Adv_nvapi_display_luminance_min);
|
||||
|
||||
public static string Adv_nvapi_display_max_frame_interval => ResourceManager.GetString(nameof(Adv_nvapi_display_max_frame_interval), Culture) ?? nameof(Adv_nvapi_display_max_frame_interval);
|
||||
|
||||
public static string Adv_nvapi_display_vrr_support => ResourceManager.GetString(nameof(Adv_nvapi_display_vrr_support), Culture) ?? nameof(Adv_nvapi_display_vrr_support);
|
||||
|
||||
public static string Adv_nvapi_driver_base_branch => ResourceManager.GetString(nameof(Adv_nvapi_driver_base_branch), Culture) ?? nameof(Adv_nvapi_driver_base_branch);
|
||||
|
||||
public static string Adv_nvapi_driver_chipset => ResourceManager.GetString(nameof(Adv_nvapi_driver_chipset), Culture) ?? nameof(Adv_nvapi_driver_chipset);
|
||||
|
||||
public static string Adv_nvapi_driver_dch => ResourceManager.GetString(nameof(Adv_nvapi_driver_dch), Culture) ?? nameof(Adv_nvapi_driver_dch);
|
||||
|
||||
public static string Adv_nvapi_driver_global_profile => ResourceManager.GetString(nameof(Adv_nvapi_driver_global_profile), Culture) ?? nameof(Adv_nvapi_driver_global_profile);
|
||||
|
||||
public static string Adv_nvapi_driver_interface_version => ResourceManager.GetString(nameof(Adv_nvapi_driver_interface_version), Culture) ?? nameof(Adv_nvapi_driver_interface_version);
|
||||
|
||||
public static string Adv_nvapi_driver_package => ResourceManager.GetString(nameof(Adv_nvapi_driver_package), Culture) ?? nameof(Adv_nvapi_driver_package);
|
||||
|
||||
public static string Adv_nvapi_encoder_fps => ResourceManager.GetString(nameof(Adv_nvapi_encoder_fps), Culture) ?? nameof(Adv_nvapi_encoder_fps);
|
||||
|
||||
public static string Adv_nvapi_encoder_latency => ResourceManager.GetString(nameof(Adv_nvapi_encoder_latency), Culture) ?? nameof(Adv_nvapi_encoder_latency);
|
||||
|
||||
public static string Adv_nvapi_encoder_session_processes => ResourceManager.GetString(nameof(Adv_nvapi_encoder_session_processes), Culture) ?? nameof(Adv_nvapi_encoder_session_processes);
|
||||
|
||||
public static string Adv_nvapi_encoder_sessions => ResourceManager.GetString(nameof(Adv_nvapi_encoder_sessions), Culture) ?? nameof(Adv_nvapi_encoder_sessions);
|
||||
|
||||
public static string Adv_nvapi_gpu_architecture => ResourceManager.GetString(nameof(Adv_nvapi_gpu_architecture), Culture) ?? nameof(Adv_nvapi_gpu_architecture);
|
||||
|
||||
public static string Adv_nvapi_gpu_board_serial => ResourceManager.GetString(nameof(Adv_nvapi_gpu_board_serial), Culture) ?? nameof(Adv_nvapi_gpu_board_serial);
|
||||
|
||||
public static string Adv_nvapi_gpu_bus_type => ResourceManager.GetString(nameof(Adv_nvapi_gpu_bus_type), Culture) ?? nameof(Adv_nvapi_gpu_bus_type);
|
||||
|
||||
public static string Adv_nvapi_gpu_clock_base_core => ResourceManager.GetString(nameof(Adv_nvapi_gpu_clock_base_core), Culture) ?? nameof(Adv_nvapi_gpu_clock_base_core);
|
||||
|
||||
public static string Adv_nvapi_gpu_clock_base_memory => ResourceManager.GetString(nameof(Adv_nvapi_gpu_clock_base_memory), Culture) ?? nameof(Adv_nvapi_gpu_clock_base_memory);
|
||||
|
||||
public static string Adv_nvapi_gpu_clock_boost_core => ResourceManager.GetString(nameof(Adv_nvapi_gpu_clock_boost_core), Culture) ?? nameof(Adv_nvapi_gpu_clock_boost_core);
|
||||
|
||||
public static string Adv_nvapi_gpu_clock_boost_memory => ResourceManager.GetString(nameof(Adv_nvapi_gpu_clock_boost_memory), Culture) ?? nameof(Adv_nvapi_gpu_clock_boost_memory);
|
||||
|
||||
public static string Adv_nvapi_gpu_core_count => ResourceManager.GetString(nameof(Adv_nvapi_gpu_core_count), Culture) ?? nameof(Adv_nvapi_gpu_core_count);
|
||||
|
||||
public static string Adv_nvapi_gpu_external => ResourceManager.GetString(nameof(Adv_nvapi_gpu_external), Culture) ?? nameof(Adv_nvapi_gpu_external);
|
||||
|
||||
public static string Adv_nvapi_gpu_fan_duty => ResourceManager.GetString(nameof(Adv_nvapi_gpu_fan_duty), Culture) ?? nameof(Adv_nvapi_gpu_fan_duty);
|
||||
|
||||
public static string Adv_nvapi_gpu_pci_ids => ResourceManager.GetString(nameof(Adv_nvapi_gpu_pci_ids), Culture) ?? nameof(Adv_nvapi_gpu_pci_ids);
|
||||
|
||||
public static string Adv_nvapi_gpu_power => ResourceManager.GetString(nameof(Adv_nvapi_gpu_power), Culture) ?? nameof(Adv_nvapi_gpu_power);
|
||||
|
||||
public static string Adv_nvapi_gpu_ram_bus_width => ResourceManager.GetString(nameof(Adv_nvapi_gpu_ram_bus_width), Culture) ?? nameof(Adv_nvapi_gpu_ram_bus_width);
|
||||
|
||||
public static string Adv_nvapi_gpu_ram_type => ResourceManager.GetString(nameof(Adv_nvapi_gpu_ram_type), Culture) ?? nameof(Adv_nvapi_gpu_ram_type);
|
||||
|
||||
public static string Adv_nvapi_gpu_rt_cores => ResourceManager.GetString(nameof(Adv_nvapi_gpu_rt_cores), Culture) ?? nameof(Adv_nvapi_gpu_rt_cores);
|
||||
|
||||
public static string Adv_nvapi_gpu_system_type => ResourceManager.GetString(nameof(Adv_nvapi_gpu_system_type), Culture) ?? nameof(Adv_nvapi_gpu_system_type);
|
||||
|
||||
public static string Adv_nvapi_gpu_temp_default_max => ResourceManager.GetString(nameof(Adv_nvapi_gpu_temp_default_max), Culture) ?? nameof(Adv_nvapi_gpu_temp_default_max);
|
||||
|
||||
public static string Adv_nvapi_gpu_tensor_cores => ResourceManager.GetString(nameof(Adv_nvapi_gpu_tensor_cores), Culture) ?? nameof(Adv_nvapi_gpu_tensor_cores);
|
||||
|
||||
public static string Adv_nvapi_gpu_type => ResourceManager.GetString(nameof(Adv_nvapi_gpu_type), Culture) ?? nameof(Adv_nvapi_gpu_type);
|
||||
|
||||
public static string Adv_nvapi_gpu_uuid => ResourceManager.GetString(nameof(Adv_nvapi_gpu_uuid), Culture) ?? nameof(Adv_nvapi_gpu_uuid);
|
||||
|
||||
public static string Adv_nvapi_gpu_vbios_version => ResourceManager.GetString(nameof(Adv_nvapi_gpu_vbios_version), Culture) ?? nameof(Adv_nvapi_gpu_vbios_version);
|
||||
|
||||
public static string Adv_nvapi_gpu_voltage => ResourceManager.GetString(nameof(Adv_nvapi_gpu_voltage), Culture) ?? nameof(Adv_nvapi_gpu_voltage);
|
||||
|
||||
public static string Adv_nvapi_limit_ac_battery => ResourceManager.GetString(nameof(Adv_nvapi_limit_ac_battery), Culture) ?? nameof(Adv_nvapi_limit_ac_battery);
|
||||
|
||||
public static string Adv_nvapi_limit_api => ResourceManager.GetString(nameof(Adv_nvapi_limit_api), Culture) ?? nameof(Adv_nvapi_limit_api);
|
||||
|
||||
public static string Adv_nvapi_limit_insufficient_power => ResourceManager.GetString(nameof(Adv_nvapi_limit_insufficient_power), Culture) ?? nameof(Adv_nvapi_limit_insufficient_power);
|
||||
|
||||
public static string Adv_nvapi_load_bus => ResourceManager.GetString(nameof(Adv_nvapi_load_bus), Culture) ?? nameof(Adv_nvapi_load_bus);
|
||||
|
||||
public static string Adv_nvapi_load_framebuffer => ResourceManager.GetString(nameof(Adv_nvapi_load_framebuffer), Culture) ?? nameof(Adv_nvapi_load_framebuffer);
|
||||
|
||||
public static string Adv_nvapi_load_video => ResourceManager.GetString(nameof(Adv_nvapi_load_video), Culture) ?? nameof(Adv_nvapi_load_video);
|
||||
|
||||
public static string Adv_nvapi_pstate => ResourceManager.GetString(nameof(Adv_nvapi_pstate), Culture) ?? nameof(Adv_nvapi_pstate);
|
||||
|
||||
public static string Adv_nvapi_reflex_frame_report => ResourceManager.GetString(nameof(Adv_nvapi_reflex_frame_report), Culture) ?? nameof(Adv_nvapi_reflex_frame_report);
|
||||
|
||||
public static string Adv_nvapi_reflex_gpu_times => ResourceManager.GetString(nameof(Adv_nvapi_reflex_gpu_times), Culture) ?? nameof(Adv_nvapi_reflex_gpu_times);
|
||||
|
||||
public static string Adv_nvapi_reflex_mode => ResourceManager.GetString(nameof(Adv_nvapi_reflex_mode), Culture) ?? nameof(Adv_nvapi_reflex_mode);
|
||||
|
||||
public static string Adv_nvapi_reflex_sleep_status => ResourceManager.GetString(nameof(Adv_nvapi_reflex_sleep_status), Culture) ?? nameof(Adv_nvapi_reflex_sleep_status);
|
||||
|
||||
public static string Adv_nvapi_session_driver_profile => ResourceManager.GetString(nameof(Adv_nvapi_session_driver_profile), Culture) ?? nameof(Adv_nvapi_session_driver_profile);
|
||||
|
||||
public static string Adv_nvapi_session_source_colorspace => ResourceManager.GetString(nameof(Adv_nvapi_session_source_colorspace), Culture) ?? nameof(Adv_nvapi_session_source_colorspace);
|
||||
|
||||
public static string Adv_nvapi_session_vrr_display_mode => ResourceManager.GetString(nameof(Adv_nvapi_session_vrr_display_mode), Culture) ?? nameof(Adv_nvapi_session_vrr_display_mode);
|
||||
|
||||
public static string Adv_nvapi_session_vrr_enabled => ResourceManager.GetString(nameof(Adv_nvapi_session_vrr_enabled), Culture) ?? nameof(Adv_nvapi_session_vrr_enabled);
|
||||
|
||||
public static string Adv_nvapi_session_vrr_possible => ResourceManager.GetString(nameof(Adv_nvapi_session_vrr_possible), Culture) ?? nameof(Adv_nvapi_session_vrr_possible);
|
||||
|
||||
public static string Adv_nvapi_session_vrr_requested => ResourceManager.GetString(nameof(Adv_nvapi_session_vrr_requested), Culture) ?? nameof(Adv_nvapi_session_vrr_requested);
|
||||
|
||||
public static string Adv_nvapi_temp_board => ResourceManager.GetString(nameof(Adv_nvapi_temp_board), Culture) ?? nameof(Adv_nvapi_temp_board);
|
||||
|
||||
public static string Adv_nvapi_temp_power_supply => ResourceManager.GetString(nameof(Adv_nvapi_temp_power_supply), Culture) ?? nameof(Adv_nvapi_temp_power_supply);
|
||||
|
||||
public static string Adv_nvapi_vram_available => ResourceManager.GetString(nameof(Adv_nvapi_vram_available), Culture) ?? nameof(Adv_nvapi_vram_available);
|
||||
|
||||
public static string Adv_nvapi_vram_dedicated => ResourceManager.GetString(nameof(Adv_nvapi_vram_dedicated), Culture) ?? nameof(Adv_nvapi_vram_dedicated);
|
||||
|
||||
public static string Adv_nvapi_vram_dedicated_available => ResourceManager.GetString(nameof(Adv_nvapi_vram_dedicated_available), Culture) ?? nameof(Adv_nvapi_vram_dedicated_available);
|
||||
|
||||
public static string Adv_nvapi_vram_eviction_count => ResourceManager.GetString(nameof(Adv_nvapi_vram_eviction_count), Culture) ?? nameof(Adv_nvapi_vram_eviction_count);
|
||||
|
||||
public static string Adv_nvapi_vram_evictions_size => ResourceManager.GetString(nameof(Adv_nvapi_vram_evictions_size), Culture) ?? nameof(Adv_nvapi_vram_evictions_size);
|
||||
|
||||
public static string Adv_nvapi_vram_framebuffer_physical => ResourceManager.GetString(nameof(Adv_nvapi_vram_framebuffer_physical), Culture) ?? nameof(Adv_nvapi_vram_framebuffer_physical);
|
||||
|
||||
public static string Adv_nvapi_vram_framebuffer_virtual => ResourceManager.GetString(nameof(Adv_nvapi_vram_framebuffer_virtual), Culture) ?? nameof(Adv_nvapi_vram_framebuffer_virtual);
|
||||
|
||||
public static string Adv_nvapi_vram_in_use => ResourceManager.GetString(nameof(Adv_nvapi_vram_in_use), Culture) ?? nameof(Adv_nvapi_vram_in_use);
|
||||
|
||||
public static string Adv_nvapi_vram_promotion_count => ResourceManager.GetString(nameof(Adv_nvapi_vram_promotion_count), Culture) ?? nameof(Adv_nvapi_vram_promotion_count);
|
||||
|
||||
public static string Adv_nvapi_vram_promotions_size => ResourceManager.GetString(nameof(Adv_nvapi_vram_promotions_size), Culture) ?? nameof(Adv_nvapi_vram_promotions_size);
|
||||
|
||||
public static string Adv_nvapi_vram_shared => ResourceManager.GetString(nameof(Adv_nvapi_vram_shared), Culture) ?? nameof(Adv_nvapi_vram_shared);
|
||||
|
||||
public static string Adv_nvapi_vram_system => ResourceManager.GetString(nameof(Adv_nvapi_vram_system), Culture) ?? nameof(Adv_nvapi_vram_system);
|
||||
|
||||
public static string Adv_sl_constants_camera => ResourceManager.GetString(nameof(Adv_sl_constants_camera), Culture) ?? nameof(Adv_sl_constants_camera);
|
||||
|
||||
public static string Adv_sl_constants_depth => ResourceManager.GetString(nameof(Adv_sl_constants_depth), Culture) ?? nameof(Adv_sl_constants_depth);
|
||||
|
||||
public static string Adv_sl_constants_jitter => ResourceManager.GetString(nameof(Adv_sl_constants_jitter), Culture) ?? nameof(Adv_sl_constants_jitter);
|
||||
|
||||
public static string Adv_sl_constants_motion_vectors => ResourceManager.GetString(nameof(Adv_sl_constants_motion_vectors), Culture) ?? nameof(Adv_sl_constants_motion_vectors);
|
||||
|
||||
public static string Adv_sl_constants_projection => ResourceManager.GetString(nameof(Adv_sl_constants_projection), Culture) ?? nameof(Adv_sl_constants_projection);
|
||||
|
||||
public static string Adv_sl_constants_resets => ResourceManager.GetString(nameof(Adv_sl_constants_resets), Culture) ?? nameof(Adv_sl_constants_resets);
|
||||
|
||||
public static string Adv_sl_deepdvc_options => ResourceManager.GetString(nameof(Adv_sl_deepdvc_options), Culture) ?? nameof(Adv_sl_deepdvc_options);
|
||||
|
||||
public static string Adv_sl_dlss_alpha_upscaling => ResourceManager.GetString(nameof(Adv_sl_dlss_alpha_upscaling), Culture) ?? nameof(Adv_sl_dlss_alpha_upscaling);
|
||||
|
||||
public static string Adv_sl_dlss_auto_exposure => ResourceManager.GetString(nameof(Adv_sl_dlss_auto_exposure), Culture) ?? nameof(Adv_sl_dlss_auto_exposure);
|
||||
|
||||
public static string Adv_sl_dlss_exposure => ResourceManager.GetString(nameof(Adv_sl_dlss_exposure), Culture) ?? nameof(Adv_sl_dlss_exposure);
|
||||
|
||||
public static string Adv_sl_dlss_hdr_input => ResourceManager.GetString(nameof(Adv_sl_dlss_hdr_input), Culture) ?? nameof(Adv_sl_dlss_hdr_input);
|
||||
|
||||
public static string Adv_sl_dlss_optimal_settings => ResourceManager.GetString(nameof(Adv_sl_dlss_optimal_settings), Culture) ?? nameof(Adv_sl_dlss_optimal_settings);
|
||||
|
||||
public static string Adv_sl_dlss_output_size => ResourceManager.GetString(nameof(Adv_sl_dlss_output_size), Culture) ?? nameof(Adv_sl_dlss_output_size);
|
||||
|
||||
public static string Adv_sl_dlss_presets => ResourceManager.GetString(nameof(Adv_sl_dlss_presets), Culture) ?? nameof(Adv_sl_dlss_presets);
|
||||
|
||||
public static string Adv_sl_dlss_vram_estimate => ResourceManager.GetString(nameof(Adv_sl_dlss_vram_estimate), Culture) ?? nameof(Adv_sl_dlss_vram_estimate);
|
||||
|
||||
public static string Adv_sl_dlssd_options => ResourceManager.GetString(nameof(Adv_sl_dlssd_options), Culture) ?? nameof(Adv_sl_dlssd_options);
|
||||
|
||||
public static string Adv_sl_dlssg_frames_presented => ResourceManager.GetString(nameof(Adv_sl_dlssg_frames_presented), Culture) ?? nameof(Adv_sl_dlssg_frames_presented);
|
||||
|
||||
public static string Adv_sl_dlssg_options => ResourceManager.GetString(nameof(Adv_sl_dlssg_options), Culture) ?? nameof(Adv_sl_dlssg_options);
|
||||
|
||||
public static string Adv_sl_dlssg_state => ResourceManager.GetString(nameof(Adv_sl_dlssg_state), Culture) ?? nameof(Adv_sl_dlssg_state);
|
||||
|
||||
public static string Adv_sl_dlssg_vram_estimate => ResourceManager.GetString(nameof(Adv_sl_dlssg_vram_estimate), Culture) ?? nameof(Adv_sl_dlssg_vram_estimate);
|
||||
|
||||
public static string Adv_sl_feature_lifecycle => ResourceManager.GetString(nameof(Adv_sl_feature_lifecycle), Culture) ?? nameof(Adv_sl_feature_lifecycle);
|
||||
|
||||
public static string Adv_sl_feature_requirements => ResourceManager.GetString(nameof(Adv_sl_feature_requirements), Culture) ?? nameof(Adv_sl_feature_requirements);
|
||||
|
||||
public static string Adv_sl_feature_support => ResourceManager.GetString(nameof(Adv_sl_feature_support), Culture) ?? nameof(Adv_sl_feature_support);
|
||||
|
||||
public static string Adv_sl_feature_versions => ResourceManager.GetString(nameof(Adv_sl_feature_versions), Culture) ?? nameof(Adv_sl_feature_versions);
|
||||
|
||||
public static string Adv_sl_init_preferences => ResourceManager.GetString(nameof(Adv_sl_init_preferences), Culture) ?? nameof(Adv_sl_init_preferences);
|
||||
|
||||
public static string Adv_sl_nis_options => ResourceManager.GetString(nameof(Adv_sl_nis_options), Culture) ?? nameof(Adv_sl_nis_options);
|
||||
|
||||
public static string Adv_sl_nvperf => ResourceManager.GetString(nameof(Adv_sl_nvperf), Culture) ?? nameof(Adv_sl_nvperf);
|
||||
|
||||
public static string Adv_sl_pcl_markers => ResourceManager.GetString(nameof(Adv_sl_pcl_markers), Culture) ?? nameof(Adv_sl_pcl_markers);
|
||||
|
||||
public static string Adv_sl_reflex_state => ResourceManager.GetString(nameof(Adv_sl_reflex_state), Culture) ?? nameof(Adv_sl_reflex_state);
|
||||
|
||||
public static string Adv_xess_options => ResourceManager.GetString(nameof(Adv_xess_options), Culture) ?? nameof(Adv_xess_options);
|
||||
|
||||
public static string Advanced_Chart_Band => ResourceManager.GetString(nameof(Advanced_Chart_Band), Culture) ?? nameof(Advanced_Chart_Band);
|
||||
|
||||
public static string Advanced_Chart_Empty => ResourceManager.GetString(nameof(Advanced_Chart_Empty), Culture) ?? nameof(Advanced_Chart_Empty);
|
||||
|
||||
public static string Advanced_Chart_Header => ResourceManager.GetString(nameof(Advanced_Chart_Header), Culture) ?? nameof(Advanced_Chart_Header);
|
||||
|
||||
public static string Advanced_Chart_LiveNote => ResourceManager.GetString(nameof(Advanced_Chart_LiveNote), Culture) ?? nameof(Advanced_Chart_LiveNote);
|
||||
|
||||
public static string Advanced_Chart_Metric => ResourceManager.GetString(nameof(Advanced_Chart_Metric), Culture) ?? nameof(Advanced_Chart_Metric);
|
||||
|
||||
public static string Advanced_Chart_Seconds => ResourceManager.GetString(nameof(Advanced_Chart_Seconds), Culture) ?? nameof(Advanced_Chart_Seconds);
|
||||
|
||||
public static string Advanced_Chart_Time => ResourceManager.GetString(nameof(Advanced_Chart_Time), Culture) ?? nameof(Advanced_Chart_Time);
|
||||
|
||||
public static string Advanced_Col_Name => ResourceManager.GetString(nameof(Advanced_Col_Name), Culture) ?? nameof(Advanced_Col_Name);
|
||||
|
||||
public static string Advanced_Col_ReadAt => ResourceManager.GetString(nameof(Advanced_Col_ReadAt), Culture) ?? nameof(Advanced_Col_ReadAt);
|
||||
|
||||
public static string Advanced_Col_Samples => ResourceManager.GetString(nameof(Advanced_Col_Samples), Culture) ?? nameof(Advanced_Col_Samples);
|
||||
|
||||
public static string Advanced_Col_Scope => ResourceManager.GetString(nameof(Advanced_Col_Scope), Culture) ?? nameof(Advanced_Col_Scope);
|
||||
|
||||
public static string Advanced_Col_Source => ResourceManager.GetString(nameof(Advanced_Col_Source), Culture) ?? nameof(Advanced_Col_Source);
|
||||
|
||||
public static string Advanced_Col_Status => ResourceManager.GetString(nameof(Advanced_Col_Status), Culture) ?? nameof(Advanced_Col_Status);
|
||||
|
||||
public static string Advanced_Col_Value => ResourceManager.GetString(nameof(Advanced_Col_Value), Culture) ?? nameof(Advanced_Col_Value);
|
||||
|
||||
public static string Advanced_Elevation_Hint => ResourceManager.GetString(nameof(Advanced_Elevation_Hint), Culture) ?? nameof(Advanced_Elevation_Hint);
|
||||
|
||||
public static string Advanced_Facts_Header => ResourceManager.GetString(nameof(Advanced_Facts_Header), Culture) ?? nameof(Advanced_Facts_Header);
|
||||
|
||||
public static string Advanced_Header => ResourceManager.GetString(nameof(Advanced_Header), Culture) ?? nameof(Advanced_Header);
|
||||
|
||||
public static string Advanced_InGameCallsLine => ResourceManager.GetString(nameof(Advanced_InGameCallsLine), Culture) ?? nameof(Advanced_InGameCallsLine);
|
||||
|
||||
public static string Advanced_InGameDriverLine => ResourceManager.GetString(nameof(Advanced_InGameDriverLine), Culture) ?? nameof(Advanced_InGameDriverLine);
|
||||
|
||||
public static string Advanced_InGameFeatureCallsLine => ResourceManager.GetString(nameof(Advanced_InGameFeatureCallsLine), Culture) ?? nameof(Advanced_InGameFeatureCallsLine);
|
||||
|
||||
public static string Advanced_InGameLine => ResourceManager.GetString(nameof(Advanced_InGameLine), Culture) ?? nameof(Advanced_InGameLine);
|
||||
|
||||
public static string Advanced_InGameMoreCallsLine => ResourceManager.GetString(nameof(Advanced_InGameMoreCallsLine), Culture) ?? nameof(Advanced_InGameMoreCallsLine);
|
||||
|
||||
public static string Advanced_Machine_Intro => ResourceManager.GetString(nameof(Advanced_Machine_Intro), Culture) ?? nameof(Advanced_Machine_Intro);
|
||||
|
||||
public static string Advanced_Max => ResourceManager.GetString(nameof(Advanced_Max), Culture) ?? nameof(Advanced_Max);
|
||||
|
||||
public static string Advanced_Mean => ResourceManager.GetString(nameof(Advanced_Mean), Culture) ?? nameof(Advanced_Mean);
|
||||
|
||||
public static string Advanced_Min => ResourceManager.GetString(nameof(Advanced_Min), Culture) ?? nameof(Advanced_Min);
|
||||
|
||||
public static string Advanced_Now_Header => ResourceManager.GetString(nameof(Advanced_Now_Header), Culture) ?? nameof(Advanced_Now_Header);
|
||||
|
||||
public static string Advanced_Session_Empty => ResourceManager.GetString(nameof(Advanced_Session_Empty), Culture) ?? nameof(Advanced_Session_Empty);
|
||||
|
||||
public static string Advanced_Session_Facts => ResourceManager.GetString(nameof(Advanced_Session_Facts), Culture) ?? nameof(Advanced_Session_Facts);
|
||||
|
||||
public static string Advanced_Session_NoSeries => ResourceManager.GetString(nameof(Advanced_Session_NoSeries), Culture) ?? nameof(Advanced_Session_NoSeries);
|
||||
|
||||
public static string Advanced_Session_NoStats => ResourceManager.GetString(nameof(Advanced_Session_NoStats), Culture) ?? nameof(Advanced_Session_NoStats);
|
||||
|
||||
public static string Advanced_Session_Pick => ResourceManager.GetString(nameof(Advanced_Session_Pick), Culture) ?? nameof(Advanced_Session_Pick);
|
||||
|
||||
public static string Advanced_Session_Stats => ResourceManager.GetString(nameof(Advanced_Session_Stats), Culture) ?? nameof(Advanced_Session_Stats);
|
||||
|
||||
public static string Advanced_Sources_Intro => ResourceManager.GetString(nameof(Advanced_Sources_Intro), Culture) ?? nameof(Advanced_Sources_Intro);
|
||||
|
||||
public static string Advanced_SourcesLine => ResourceManager.GetString(nameof(Advanced_SourcesLine), Culture) ?? nameof(Advanced_SourcesLine);
|
||||
|
||||
public static string Advanced_State_Live => ResourceManager.GetString(nameof(Advanced_State_Live), Culture) ?? nameof(Advanced_State_Live);
|
||||
|
||||
public static string Advanced_State_NoAgent => ResourceManager.GetString(nameof(Advanced_State_NoAgent), Culture) ?? nameof(Advanced_State_NoAgent);
|
||||
|
||||
public static string Advanced_State_Off => ResourceManager.GetString(nameof(Advanced_State_Off), Culture) ?? nameof(Advanced_State_Off);
|
||||
|
||||
public static string Advanced_State_OlderAgent => ResourceManager.GetString(nameof(Advanced_State_OlderAgent), Culture) ?? nameof(Advanced_State_OlderAgent);
|
||||
|
||||
public static string Advanced_State_Viewer => ResourceManager.GetString(nameof(Advanced_State_Viewer), Culture) ?? nameof(Advanced_State_Viewer);
|
||||
|
||||
public static string Advanced_State_Waiting => ResourceManager.GetString(nameof(Advanced_State_Waiting), Culture) ?? nameof(Advanced_State_Waiting);
|
||||
|
||||
public static string Advanced_Status_InGame => ResourceManager.GetString(nameof(Advanced_Status_InGame), Culture) ?? nameof(Advanced_Status_InGame);
|
||||
|
||||
public static string Advanced_Status_InGameDriver => ResourceManager.GetString(nameof(Advanced_Status_InGameDriver), Culture) ?? nameof(Advanced_Status_InGameDriver);
|
||||
|
||||
public static string Advanced_Status_Read => ResourceManager.GetString(nameof(Advanced_Status_Read), Culture) ?? nameof(Advanced_Status_Read);
|
||||
|
||||
public static string Advanced_Status_Readable => ResourceManager.GetString(nameof(Advanced_Status_Readable), Culture) ?? nameof(Advanced_Status_Readable);
|
||||
|
||||
public static string Advanced_Status_SourceSilent => ResourceManager.GetString(nameof(Advanced_Status_SourceSilent), Culture) ?? nameof(Advanced_Status_SourceSilent);
|
||||
|
||||
public static string Advanced_Tab_Machine => ResourceManager.GetString(nameof(Advanced_Tab_Machine), Culture) ?? nameof(Advanced_Tab_Machine);
|
||||
|
||||
public static string Advanced_Tab_Session => ResourceManager.GetString(nameof(Advanced_Tab_Session), Culture) ?? nameof(Advanced_Tab_Session);
|
||||
|
||||
public static string Advanced_Tab_Sources => ResourceManager.GetString(nameof(Advanced_Tab_Sources), Culture) ?? nameof(Advanced_Tab_Sources);
|
||||
|
||||
public static string AdvDriverRead_Error => ResourceManager.GetString(nameof(AdvDriverRead_Error), Culture) ?? nameof(AdvDriverRead_Error);
|
||||
|
||||
public static string AdvDriverRead_Faulted => ResourceManager.GetString(nameof(AdvDriverRead_Faulted), Culture) ?? nameof(AdvDriverRead_Faulted);
|
||||
|
||||
public static string AdvDriverRead_NoDirect3D12 => ResourceManager.GetString(nameof(AdvDriverRead_NoDirect3D12), Culture) ?? nameof(AdvDriverRead_NoDirect3D12);
|
||||
|
||||
public static string AdvDriverRead_NoGetter => ResourceManager.GetString(nameof(AdvDriverRead_NoGetter), Culture) ?? nameof(AdvDriverRead_NoGetter);
|
||||
|
||||
public static string AdvDriverRead_NoModule => ResourceManager.GetString(nameof(AdvDriverRead_NoModule), Culture) ?? nameof(AdvDriverRead_NoModule);
|
||||
|
||||
public static string AdvDriverRead_NothingReported => ResourceManager.GetString(nameof(AdvDriverRead_NothingReported), Culture) ?? nameof(AdvDriverRead_NothingReported);
|
||||
|
||||
public static string AdvDriverRead_Read => ResourceManager.GetString(nameof(AdvDriverRead_Read), Culture) ?? nameof(AdvDriverRead_Read);
|
||||
|
||||
public static string AdvDriverRead_Refused => ResourceManager.GetString(nameof(AdvDriverRead_Refused), Culture) ?? nameof(AdvDriverRead_Refused);
|
||||
|
||||
public static string AdvDriverRead_Slow => ResourceManager.GetString(nameof(AdvDriverRead_Slow), Culture) ?? nameof(AdvDriverRead_Slow);
|
||||
|
||||
public static string AdvDriverRead_Stalled => ResourceManager.GetString(nameof(AdvDriverRead_Stalled), Culture) ?? nameof(AdvDriverRead_Stalled);
|
||||
|
||||
public static string AdvDriverRead_Unknown => ResourceManager.GetString(nameof(AdvDriverRead_Unknown), Culture) ?? nameof(AdvDriverRead_Unknown);
|
||||
|
||||
public static string AdvGroup_Board => ResourceManager.GetString(nameof(AdvGroup_Board), Culture) ?? nameof(AdvGroup_Board);
|
||||
|
||||
public static string AdvGroup_Cpu => ResourceManager.GetString(nameof(AdvGroup_Cpu), Culture) ?? nameof(AdvGroup_Cpu);
|
||||
|
||||
public static string AdvGroup_Display => ResourceManager.GetString(nameof(AdvGroup_Display), Culture) ?? nameof(AdvGroup_Display);
|
||||
|
||||
public static string AdvGroup_Driver => ResourceManager.GetString(nameof(AdvGroup_Driver), Culture) ?? nameof(AdvGroup_Driver);
|
||||
|
||||
public static string AdvGroup_FrameGeneration => ResourceManager.GetString(nameof(AdvGroup_FrameGeneration), Culture) ?? nameof(AdvGroup_FrameGeneration);
|
||||
|
||||
public static string AdvGroup_Gpu => ResourceManager.GetString(nameof(AdvGroup_Gpu), Culture) ?? nameof(AdvGroup_Gpu);
|
||||
|
||||
public static string AdvGroup_GpuMemory => ResourceManager.GetString(nameof(AdvGroup_GpuMemory), Culture) ?? nameof(AdvGroup_GpuMemory);
|
||||
|
||||
public static string AdvGroup_Latency => ResourceManager.GetString(nameof(AdvGroup_Latency), Culture) ?? nameof(AdvGroup_Latency);
|
||||
|
||||
public static string AdvGroup_Memory => ResourceManager.GetString(nameof(AdvGroup_Memory), Culture) ?? nameof(AdvGroup_Memory);
|
||||
|
||||
public static string AdvGroup_Storage => ResourceManager.GetString(nameof(AdvGroup_Storage), Culture) ?? nameof(AdvGroup_Storage);
|
||||
|
||||
public static string AdvGroup_Upscaling => ResourceManager.GetString(nameof(AdvGroup_Upscaling), Culture) ?? nameof(AdvGroup_Upscaling);
|
||||
|
||||
public static string AdvInGame_NothingSeen => ResourceManager.GetString(nameof(AdvInGame_NothingSeen), Culture) ?? nameof(AdvInGame_NothingSeen);
|
||||
|
||||
public static string AdvInGame_NotHooked => ResourceManager.GetString(nameof(AdvInGame_NotHooked), Culture) ?? nameof(AdvInGame_NotHooked);
|
||||
|
||||
public static string AdvInGame_Reading => ResourceManager.GetString(nameof(AdvInGame_Reading), Culture) ?? nameof(AdvInGame_Reading);
|
||||
|
||||
public static string AdvInGame_Unknown => ResourceManager.GetString(nameof(AdvInGame_Unknown), Culture) ?? nameof(AdvInGame_Unknown);
|
||||
|
||||
public static string AdvInGameCall_NeverCalled => ResourceManager.GetString(nameof(AdvInGameCall_NeverCalled), Culture) ?? nameof(AdvInGameCall_NeverCalled);
|
||||
|
||||
public static string AdvInGameCall_NotAskedAgain => ResourceManager.GetString(nameof(AdvInGameCall_NotAskedAgain), Culture) ?? nameof(AdvInGameCall_NotAskedAgain);
|
||||
|
||||
public static string AdvInGameCall_NotHooked => ResourceManager.GetString(nameof(AdvInGameCall_NotHooked), Culture) ?? nameof(AdvInGameCall_NotHooked);
|
||||
|
||||
public static string AdvInGameCall_Read => ResourceManager.GetString(nameof(AdvInGameCall_Read), Culture) ?? nameof(AdvInGameCall_Read);
|
||||
|
||||
public static string AdvInGameCall_Unknown => ResourceManager.GetString(nameof(AdvInGameCall_Unknown), Culture) ?? nameof(AdvInGameCall_Unknown);
|
||||
|
||||
public static string AdvReach_BeforeAttach => ResourceManager.GetString(nameof(AdvReach_BeforeAttach), Culture) ?? nameof(AdvReach_BeforeAttach);
|
||||
|
||||
public static string AdvReach_Deferred => ResourceManager.GetString(nameof(AdvReach_Deferred), Culture) ?? nameof(AdvReach_Deferred);
|
||||
|
||||
public static string AdvReach_Game => ResourceManager.GetString(nameof(AdvReach_Game), Culture) ?? nameof(AdvReach_Game);
|
||||
|
||||
public static string AdvReach_HookedCall => ResourceManager.GetString(nameof(AdvReach_HookedCall), Culture) ?? nameof(AdvReach_HookedCall);
|
||||
|
||||
public static string AdvReach_Identifier => ResourceManager.GetString(nameof(AdvReach_Identifier), Culture) ?? nameof(AdvReach_Identifier);
|
||||
|
||||
public static string AdvReach_Licence => ResourceManager.GetString(nameof(AdvReach_Licence), Culture) ?? nameof(AdvReach_Licence);
|
||||
|
||||
public static string AdvReach_NewHook => ResourceManager.GetString(nameof(AdvReach_NewHook), Culture) ?? nameof(AdvReach_NewHook);
|
||||
|
||||
public static string AdvReach_NotInHeaders => ResourceManager.GetString(nameof(AdvReach_NotInHeaders), Culture) ?? nameof(AdvReach_NotInHeaders);
|
||||
|
||||
public static string AdvReach_PlayerState => ResourceManager.GetString(nameof(AdvReach_PlayerState), Culture) ?? nameof(AdvReach_PlayerState);
|
||||
|
||||
public static string AdvReach_Refused => ResourceManager.GetString(nameof(AdvReach_Refused), Culture) ?? nameof(AdvReach_Refused);
|
||||
|
||||
public static string AdvReach_RefusedRoute => ResourceManager.GetString(nameof(AdvReach_RefusedRoute), Culture) ?? nameof(AdvReach_RefusedRoute);
|
||||
|
||||
public static string AdvReach_Spike => ResourceManager.GetString(nameof(AdvReach_Spike), Culture) ?? nameof(AdvReach_Spike);
|
||||
|
||||
public static string AdvScope_MachineFact => ResourceManager.GetString(nameof(AdvScope_MachineFact), Culture) ?? nameof(AdvScope_MachineFact);
|
||||
|
||||
public static string AdvScope_Series => ResourceManager.GetString(nameof(AdvScope_Series), Culture) ?? nameof(AdvScope_Series);
|
||||
|
||||
public static string AdvScope_SessionFact => ResourceManager.GetString(nameof(AdvScope_SessionFact), Culture) ?? nameof(AdvScope_SessionFact);
|
||||
|
||||
public static string AdvSource_Faulted => ResourceManager.GetString(nameof(AdvSource_Faulted), Culture) ?? nameof(AdvSource_Faulted);
|
||||
|
||||
public static string AdvSource_NotElevated => ResourceManager.GetString(nameof(AdvSource_NotElevated), Culture) ?? nameof(AdvSource_NotElevated);
|
||||
|
||||
public static string AdvSource_NotPresent => ResourceManager.GetString(nameof(AdvSource_NotPresent), Culture) ?? nameof(AdvSource_NotPresent);
|
||||
|
||||
public static string AdvSource_PawnIoMissing => ResourceManager.GetString(nameof(AdvSource_PawnIoMissing), Culture) ?? nameof(AdvSource_PawnIoMissing);
|
||||
|
||||
public static string AdvSource_Reading => ResourceManager.GetString(nameof(AdvSource_Reading), Culture) ?? nameof(AdvSource_Reading);
|
||||
|
||||
public static string AdvSource_Unknown => ResourceManager.GetString(nameof(AdvSource_Unknown), Culture) ?? nameof(AdvSource_Unknown);
|
||||
|
||||
public static string AdvToken_active_render => ResourceManager.GetString(nameof(AdvToken_active_render), Culture) ?? nameof(AdvToken_active_render);
|
||||
|
||||
public static string AdvToken_adaptive_sync => ResourceManager.GetString(nameof(AdvToken_adaptive_sync), Culture) ?? nameof(AdvToken_adaptive_sync);
|
||||
|
||||
public static string AdvToken_agp => ResourceManager.GetString(nameof(AdvToken_agp), Culture) ?? nameof(AdvToken_agp);
|
||||
|
||||
public static string AdvToken_axi => ResourceManager.GetString(nameof(AdvToken_axi), Culture) ?? nameof(AdvToken_axi);
|
||||
|
||||
public static string AdvToken_bt2100_pq => ResourceManager.GetString(nameof(AdvToken_bt2100_pq), Culture) ?? nameof(AdvToken_bt2100_pq);
|
||||
|
||||
public static string AdvToken_desktop => ResourceManager.GetString(nameof(AdvToken_desktop), Culture) ?? nameof(AdvToken_desktop);
|
||||
|
||||
public static string AdvToken_discrete => ResourceManager.GetString(nameof(AdvToken_discrete), Culture) ?? nameof(AdvToken_discrete);
|
||||
|
||||
public static string AdvToken_dolby_vision => ResourceManager.GetString(nameof(AdvToken_dolby_vision), Culture) ?? nameof(AdvToken_dolby_vision);
|
||||
|
||||
public static string AdvToken_draw_debug_view => ResourceManager.GetString(nameof(AdvToken_draw_debug_view), Culture) ?? nameof(AdvToken_draw_debug_view);
|
||||
|
||||
public static string AdvToken_driver => ResourceManager.GetString(nameof(AdvToken_driver), Culture) ?? nameof(AdvToken_driver);
|
||||
|
||||
public static string AdvToken_driver_default => ResourceManager.GetString(nameof(AdvToken_driver_default), Culture) ?? nameof(AdvToken_driver_default);
|
||||
|
||||
public static string AdvToken_edr => ResourceManager.GetString(nameof(AdvToken_edr), Culture) ?? nameof(AdvToken_edr);
|
||||
|
||||
public static string AdvToken_fpci => ResourceManager.GetString(nameof(AdvToken_fpci), Culture) ?? nameof(AdvToken_fpci);
|
||||
|
||||
public static string AdvToken_frame_time => ResourceManager.GetString(nameof(AdvToken_frame_time), Culture) ?? nameof(AdvToken_frame_time);
|
||||
|
||||
public static string AdvToken_game_ready => ResourceManager.GetString(nameof(AdvToken_game_ready), Culture) ?? nameof(AdvToken_game_ready);
|
||||
|
||||
public static string AdvToken_gpu_render => ResourceManager.GetString(nameof(AdvToken_gpu_render), Culture) ?? nameof(AdvToken_gpu_render);
|
||||
|
||||
public static string AdvToken_gsync_module => ResourceManager.GetString(nameof(AdvToken_gsync_module), Culture) ?? nameof(AdvToken_gsync_module);
|
||||
|
||||
public static string AdvToken_hdr10 => ResourceManager.GetString(nameof(AdvToken_hdr10), Culture) ?? nameof(AdvToken_hdr10);
|
||||
|
||||
public static string AdvToken_hdr10_plus => ResourceManager.GetString(nameof(AdvToken_hdr10_plus), Culture) ?? nameof(AdvToken_hdr10_plus);
|
||||
|
||||
public static string AdvToken_hdr10_plus_gaming => ResourceManager.GetString(nameof(AdvToken_hdr10_plus_gaming), Culture) ?? nameof(AdvToken_hdr10_plus_gaming);
|
||||
|
||||
public static string AdvToken_integrated => ResourceManager.GetString(nameof(AdvToken_integrated), Culture) ?? nameof(AdvToken_integrated);
|
||||
|
||||
public static string AdvToken_laptop => ResourceManager.GetString(nameof(AdvToken_laptop), Culture) ?? nameof(AdvToken_laptop);
|
||||
|
||||
public static string AdvToken_no_profile_for_game => ResourceManager.GetString(nameof(AdvToken_no_profile_for_game), Culture) ?? nameof(AdvToken_no_profile_for_game);
|
||||
|
||||
public static string AdvToken_non_linear_color_pq => ResourceManager.GetString(nameof(AdvToken_non_linear_color_pq), Culture) ?? nameof(AdvToken_non_linear_color_pq);
|
||||
|
||||
public static string AdvToken_non_linear_color_srgb => ResourceManager.GetString(nameof(AdvToken_non_linear_color_srgb), Culture) ?? nameof(AdvToken_non_linear_color_srgb);
|
||||
|
||||
public static string AdvToken_none => ResourceManager.GetString(nameof(AdvToken_none), Culture) ?? nameof(AdvToken_none);
|
||||
|
||||
public static string AdvToken_not_a_number => ResourceManager.GetString(nameof(AdvToken_not_a_number), Culture) ?? nameof(AdvToken_not_a_number);
|
||||
|
||||
public static string AdvToken_not_radians => ResourceManager.GetString(nameof(AdvToken_not_radians), Culture) ?? nameof(AdvToken_not_radians);
|
||||
|
||||
public static string AdvToken_not_supported => ResourceManager.GetString(nameof(AdvToken_not_supported), Culture) ?? nameof(AdvToken_not_supported);
|
||||
|
||||
public static string AdvToken_off => ResourceManager.GetString(nameof(AdvToken_off), Culture) ?? nameof(AdvToken_off);
|
||||
|
||||
public static string AdvToken_on => ResourceManager.GetString(nameof(AdvToken_on), Culture) ?? nameof(AdvToken_on);
|
||||
|
||||
public static string AdvToken_on_and_off => ResourceManager.GetString(nameof(AdvToken_on_and_off), Culture) ?? nameof(AdvToken_on_and_off);
|
||||
|
||||
public static string AdvToken_os_queue => ResourceManager.GetString(nameof(AdvToken_os_queue), Culture) ?? nameof(AdvToken_os_queue);
|
||||
|
||||
public static string AdvToken_pci => ResourceManager.GetString(nameof(AdvToken_pci), Culture) ?? nameof(AdvToken_pci);
|
||||
|
||||
public static string AdvToken_pci_express => ResourceManager.GetString(nameof(AdvToken_pci_express), Culture) ?? nameof(AdvToken_pci_express);
|
||||
|
||||
public static string AdvToken_present => ResourceManager.GetString(nameof(AdvToken_present), Culture) ?? nameof(AdvToken_present);
|
||||
|
||||
public static string AdvToken_render_submit => ResourceManager.GetString(nameof(AdvToken_render_submit), Culture) ?? nameof(AdvToken_render_submit);
|
||||
|
||||
public static string AdvToken_rtx_new_feature => ResourceManager.GetString(nameof(AdvToken_rtx_new_feature), Culture) ?? nameof(AdvToken_rtx_new_feature);
|
||||
|
||||
public static string AdvToken_rtx_production => ResourceManager.GetString(nameof(AdvToken_rtx_production), Culture) ?? nameof(AdvToken_rtx_production);
|
||||
|
||||
public static string AdvToken_scrgb_linear => ResourceManager.GetString(nameof(AdvToken_scrgb_linear), Culture) ?? nameof(AdvToken_scrgb_linear);
|
||||
|
||||
public static string AdvToken_simulation => ResourceManager.GetString(nameof(AdvToken_simulation), Culture) ?? nameof(AdvToken_simulation);
|
||||
|
||||
public static string AdvToken_srgb => ResourceManager.GetString(nameof(AdvToken_srgb), Culture) ?? nameof(AdvToken_srgb);
|
||||
|
||||
public static string AdvToken_studio => ResourceManager.GetString(nameof(AdvToken_studio), Culture) ?? nameof(AdvToken_studio);
|
||||
|
||||
public static string AdvToken_total => ResourceManager.GetString(nameof(AdvToken_total), Culture) ?? nameof(AdvToken_total);
|
||||
|
||||
public static string AdvToken_ulmb => ResourceManager.GetString(nameof(AdvToken_ulmb), Culture) ?? nameof(AdvToken_ulmb);
|
||||
|
||||
public static string AdvToken_usable_now => ResourceManager.GetString(nameof(AdvToken_usable_now), Culture) ?? nameof(AdvToken_usable_now);
|
||||
|
||||
public static string AdvToken_user_set => ResourceManager.GetString(nameof(AdvToken_user_set), Culture) ?? nameof(AdvToken_user_set);
|
||||
|
||||
public static string AdvToken_variable_refresh => ResourceManager.GetString(nameof(AdvToken_variable_refresh), Culture) ?? nameof(AdvToken_variable_refresh);
|
||||
|
||||
public static string Agent_Banner_Missing_Body => ResourceManager.GetString(nameof(Agent_Banner_Missing_Body), Culture) ?? nameof(Agent_Banner_Missing_Body);
|
||||
|
||||
public static string Agent_Banner_Offline_Body => ResourceManager.GetString(nameof(Agent_Banner_Offline_Body), Culture) ?? nameof(Agent_Banner_Offline_Body);
|
||||
@@ -3692,8 +2809,6 @@ public static class Strings
|
||||
|
||||
public static string Menu_Tools_VulkanLayer => ResourceManager.GetString(nameof(Menu_Tools_VulkanLayer), Culture) ?? nameof(Menu_Tools_VulkanLayer);
|
||||
|
||||
public static string Nav_Advanced => ResourceManager.GetString(nameof(Nav_Advanced), Culture) ?? nameof(Nav_Advanced);
|
||||
|
||||
public static string Nav_Compare => ResourceManager.GetString(nameof(Nav_Compare), Culture) ?? nameof(Nav_Compare);
|
||||
|
||||
public static string Nav_Dashboard => ResourceManager.GetString(nameof(Nav_Dashboard), Culture) ?? nameof(Nav_Dashboard);
|
||||
@@ -3976,10 +3091,6 @@ public static class Strings
|
||||
|
||||
public static string Sessions_GameVram_Tooltip_Format => ResourceManager.GetString(nameof(Sessions_GameVram_Tooltip_Format), Culture) ?? nameof(Sessions_GameVram_Tooltip_Format);
|
||||
|
||||
public static string Settings_Advanced_Body => ResourceManager.GetString(nameof(Settings_Advanced_Body), Culture) ?? nameof(Settings_Advanced_Body);
|
||||
|
||||
public static string Settings_Advanced_Label => ResourceManager.GetString(nameof(Settings_Advanced_Label), Culture) ?? nameof(Settings_Advanced_Label);
|
||||
|
||||
public static string Settings_Agent_Elevated => ResourceManager.GetString(nameof(Settings_Agent_Elevated), Culture) ?? nameof(Settings_Agent_Elevated);
|
||||
|
||||
public static string Settings_Agent_Elevation_Body => ResourceManager.GetString(nameof(Settings_Agent_Elevation_Body), Culture) ?? nameof(Settings_Agent_Elevation_Body);
|
||||
@@ -4220,8 +3331,6 @@ public static class Strings
|
||||
|
||||
public static string Store_Xbox_Format => ResourceManager.GetString(nameof(Store_Xbox_Format), Culture) ?? nameof(Store_Xbox_Format);
|
||||
|
||||
public static string Summary_Advanced_Button => ResourceManager.GetString(nameof(Summary_Advanced_Button), Culture) ?? nameof(Summary_Advanced_Button);
|
||||
|
||||
public static string Summary_Annotations_Header => ResourceManager.GetString(nameof(Summary_Annotations_Header), Culture) ?? nameof(Summary_Annotations_Header);
|
||||
|
||||
public static string Summary_Crash_Body => ResourceManager.GetString(nameof(Summary_Crash_Body), Culture) ?? nameof(Summary_Crash_Body);
|
||||
|
||||
File diff suppressed because it is too large.
Load diff
@@ -18,888 +18,9 @@
|
||||
<resheader name="writer">
|
||||
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
|
||||
</resheader>
|
||||
<data name="A11y_Advanced_Metric" xml:space="preserve">
|
||||
<value>Reading to chart</value>
|
||||
</data>
|
||||
<data name="A11y_Advanced_Session" xml:space="preserve">
|
||||
<value>Session to show</value>
|
||||
</data>
|
||||
<data name="A11y_Chart_Advanced" xml:space="preserve">
|
||||
<value>Advanced reading over time</value>
|
||||
</data>
|
||||
<data name="A11y_ChartData_Advanced" xml:space="preserve">
|
||||
<value>Each line is one reading. The table beside the chart lists the same readings.</value>
|
||||
</data>
|
||||
<data name="About_Title" xml:space="preserve">
|
||||
<value>About FrameLedger</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_framegen_config" xml:space="preserve">
|
||||
<value>The game's FSR frame-generation configuration</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_memory_usage" xml:space="preserve">
|
||||
<value>FSR's own video memory, when the game asks it</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_depth" xml:space="preserve">
|
||||
<value>Near and far planes and the range of the field of view given to FSR</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_exposure" xml:space="preserve">
|
||||
<value>Pre-exposure given to FSR</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_flags" xml:space="preserve">
|
||||
<value>The flags of the game's FSR dispatch</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_frame_time_delta" xml:space="preserve">
|
||||
<value>The frame time the game reported to FSR</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_jitter" xml:space="preserve">
|
||||
<value>The largest jitter offset the game gave FSR</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_sharpening" xml:space="preserve">
|
||||
<value>FSR sharpening: on or off, and its strength</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_battery" xml:space="preserve">
|
||||
<value>Battery sensors</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_fan" xml:space="preserve">
|
||||
<value>Each fan header's speed</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_fan_control" xml:space="preserve">
|
||||
<value>Each fan header's duty</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_model" xml:space="preserve">
|
||||
<value>The motherboard's maker and model</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_sensor_chip" xml:space="preserve">
|
||||
<value>The board's sensor chip</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_temperature" xml:space="preserve">
|
||||
<value>The board's temperature sensors</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_voltage" xml:space="preserve">
|
||||
<value>The board's voltage rails</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_controller" xml:space="preserve">
|
||||
<value>Fan-controller sensors: the same search of USB devices</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_cpu_clock" xml:space="preserve">
|
||||
<value>Each core's clock, and the bus clock</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_cpu_load" xml:space="preserve">
|
||||
<value>Processor load: the total and each core</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_cpu_power" xml:space="preserve">
|
||||
<value>Processor power: the package, the cores</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_cpu_temperature" xml:space="preserve">
|
||||
<value>Processor temperatures: the package and each core</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_cpu_voltage" xml:space="preserve">
|
||||
<value>Processor voltages</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_clock" xml:space="preserve">
|
||||
<value>Every clock of the card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_current" xml:space="preserve">
|
||||
<value>Every current of the card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_fan" xml:space="preserve">
|
||||
<value>Every fan of the card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_fan_control" xml:space="preserve">
|
||||
<value>Each fan's duty</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_load" xml:space="preserve">
|
||||
<value>Every load of the card: its engines, its bus, its memory controller</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_memory" xml:space="preserve">
|
||||
<value>The card's memory counters: total, free, used, Direct3D dedicated and shared</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_power" xml:space="preserve">
|
||||
<value>Every power reading of the card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_temperature" xml:space="preserve">
|
||||
<value>Every temperature sensor of the card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_throughput" xml:space="preserve">
|
||||
<value>PCI Express traffic to and from the card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_voltage" xml:space="preserve">
|
||||
<value>Every voltage of the card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_memory_load" xml:space="preserve">
|
||||
<value>Memory in use: physical and virtual</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_memory_modules" xml:space="preserve">
|
||||
<value>The memory modules: size, speed, maker's part name - never a serial number</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_memory_temperature" xml:space="preserve">
|
||||
<value>Each memory module's temperature, where it has a sensor</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_psu" xml:space="preserve">
|
||||
<value>Power-supply sensors: reading them makes the library search every USB device</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_storage_models" xml:space="preserve">
|
||||
<value>The drives' model names: the library cannot list drives without touching removable ones</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_storage_temperature" xml:space="preserve">
|
||||
<value>Each drive's temperature: the same, so the storage group is not opened</value>
|
||||
</data>
|
||||
<data name="Adv_ngx_parameters" xml:space="preserve">
|
||||
<value>NGX parameters: the quality value, the DLSS hints</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_clock_video" xml:space="preserve">
|
||||
<value>Video clock</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_adaptive_sync_off" xml:space="preserve">
|
||||
<value>Adaptive sync is switched off on the display</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_edid" xml:space="preserve">
|
||||
<value>A display's EDID block, which carries its serial number</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_hdr_formats" xml:space="preserve">
|
||||
<value>HDR formats a display accepts: HDR10, HDR10+, HDR10+ Gaming, Dolby Vision, EDR</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_luminance_max" xml:space="preserve">
|
||||
<value>A display's maximum luminance for HDR content</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_luminance_max_frame_average" xml:space="preserve">
|
||||
<value>Its maximum frame-average light level</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_luminance_min" xml:space="preserve">
|
||||
<value>Its minimum luminance</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_max_frame_interval" xml:space="preserve">
|
||||
<value>The longest frame interval adaptive sync is set to hold</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_vrr_support" xml:space="preserve">
|
||||
<value>Variable refresh: supported, G-SYNC module or adaptive sync, ULMB, usable at the current mode</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_base_branch" xml:space="preserve">
|
||||
<value>The driver's base branch</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_chipset" xml:space="preserve">
|
||||
<value>Chipset vendor and name, as the driver reports them</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_dch" xml:space="preserve">
|
||||
<value>The driver is a DCH package</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_global_profile" xml:space="preserve">
|
||||
<value>Every setting of the driver's global profile, read-only</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_interface_version" xml:space="preserve">
|
||||
<value>NVAPI's own interface version</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_package" xml:space="preserve">
|
||||
<value>Game Ready, Studio or an RTX enterprise branch</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_encoder_fps" xml:space="preserve">
|
||||
<value>Average encoding rate of the active sessions</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_encoder_latency" xml:space="preserve">
|
||||
<value>Average encoding latency</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_encoder_session_processes" xml:space="preserve">
|
||||
<value>Which programs are encoding</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_encoder_sessions" xml:space="preserve">
|
||||
<value>Active hardware-encoder sessions, all programs</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_architecture" xml:space="preserve">
|
||||
<value>Chip architecture, implementation and revision</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_board_serial" xml:space="preserve">
|
||||
<value>The card's board serial number</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_bus_type" xml:space="preserve">
|
||||
<value>The bus the card sits on</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_clock_base_core" xml:space="preserve">
|
||||
<value>Base core clock</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_clock_base_memory" xml:space="preserve">
|
||||
<value>Base memory clock</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_clock_boost_core" xml:space="preserve">
|
||||
<value>Boost core clock</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_clock_boost_memory" xml:space="preserve">
|
||||
<value>Boost memory clock</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_core_count" xml:space="preserve">
|
||||
<value>Graphics cores</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_external" xml:space="preserve">
|
||||
<value>The card is an external one</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_fan_duty" xml:space="preserve">
|
||||
<value>Fan duty through NVAPI (LibreHardwareMonitor reads it)</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_pci_ids" xml:space="preserve">
|
||||
<value>PCI device, subsystem and revision ids - the model, not the unit</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_power" xml:space="preserve">
|
||||
<value>Card power through NVAPI (LibreHardwareMonitor reads it)</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_ram_bus_width" xml:space="preserve">
|
||||
<value>Width of the card's memory bus</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_ram_type" xml:space="preserve">
|
||||
<value>The card's memory type</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_rt_cores" xml:space="preserve">
|
||||
<value>Ray-tracing cores</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_system_type" xml:space="preserve">
|
||||
<value>Laptop or desktop, as the driver sees the PC</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_temp_default_max" xml:space="preserve">
|
||||
<value>The core sensor's default maximum temperature</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_tensor_cores" xml:space="preserve">
|
||||
<value>Tensor cores</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_type" xml:space="preserve">
|
||||
<value>Integrated or discrete graphics</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_uuid" xml:space="preserve">
|
||||
<value>The card's unique id</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_vbios_version" xml:space="preserve">
|
||||
<value>Video BIOS version</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_voltage" xml:space="preserve">
|
||||
<value>Card voltage through NVAPI (LibreHardwareMonitor reads it)</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_limit_ac_battery" xml:space="preserve">
|
||||
<value>Held back by a switch to battery on the tick: 100 or 0</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_limit_api" xml:space="preserve">
|
||||
<value>Held back at a program's request on the tick: 100 or 0</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_limit_insufficient_power" xml:space="preserve">
|
||||
<value>Held back by a missing power connector on the tick: 100 or 0</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_load_bus" xml:space="preserve">
|
||||
<value>Bus-interface utilisation</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_load_framebuffer" xml:space="preserve">
|
||||
<value>Frame-buffer (memory controller) utilisation</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_load_video" xml:space="preserve">
|
||||
<value>Video-engine utilisation</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_pstate" xml:space="preserve">
|
||||
<value>The card's current performance state (P-state id)</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_reflex_frame_report" xml:space="preserve">
|
||||
<value>Latency per frame: simulation, render submit, present, driver, OS queue, GPU render</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_reflex_gpu_times" xml:space="preserve">
|
||||
<value>The graphics card's time per frame, as the driver works it out: active render, frame to frame</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_reflex_mode" xml:space="preserve">
|
||||
<value>Reflex: low-latency mode, boost, the frame-rate limit</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_reflex_sleep_status" xml:space="preserve">
|
||||
<value>What the driver's low-latency state is</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_driver_profile" xml:space="preserve">
|
||||
<value>The settings the driver's profile for this game sets itself, read-only</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_source_colorspace" xml:space="preserve">
|
||||
<value>The colour space the game presented in, as the driver reports it for the process</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_vrr_display_mode" xml:space="preserve">
|
||||
<value>The display itself was in variable-refresh mode</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_vrr_enabled" xml:space="preserve">
|
||||
<value>Variable refresh was active on the game's display</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_vrr_possible" xml:space="preserve">
|
||||
<value>Variable refresh was possible on it</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_vrr_requested" xml:space="preserve">
|
||||
<value>Variable refresh was requested for it</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_temp_board" xml:space="preserve">
|
||||
<value>Board ambient temperature, where the card has the sensor</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_temp_power_supply" xml:space="preserve">
|
||||
<value>The card's power-supply temperature, where it has the sensor</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_available" xml:space="preserve">
|
||||
<value>Dedicated video memory available now, all programs</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_dedicated" xml:space="preserve">
|
||||
<value>Dedicated video memory on the card</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_dedicated_available" xml:space="preserve">
|
||||
<value>Dedicated video memory available for surfaces</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_eviction_count" xml:space="preserve">
|
||||
<value>Evictions from dedicated video memory since the driver loaded</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_evictions_size" xml:space="preserve">
|
||||
<value>Memory released by evictions since the driver loaded</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_framebuffer_physical" xml:space="preserve">
|
||||
<value>Physical frame buffer size</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_framebuffer_virtual" xml:space="preserve">
|
||||
<value>Virtual frame buffer size</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_in_use" xml:space="preserve">
|
||||
<value>Dedicated video memory in use now, all programs: available for surfaces less available now</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_promotion_count" xml:space="preserve">
|
||||
<value>Promotions into dedicated video memory since the driver loaded</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_promotions_size" xml:space="preserve">
|
||||
<value>Memory moved in by promotions since the driver loaded</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_shared" xml:space="preserve">
|
||||
<value>Shared system memory the driver may commit</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_system" xml:space="preserve">
|
||||
<value>System memory the driver reserved at load</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_camera" xml:space="preserve">
|
||||
<value>Camera position, axes and matrices</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_depth" xml:space="preserve">
|
||||
<value>Near and far planes, and whether depth is inverted</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_jitter" xml:space="preserve">
|
||||
<value>The jitter offsets the game gave Streamline</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_motion_vectors" xml:space="preserve">
|
||||
<value>Motion-vector scale, and whether they are 3D, dilated, jittered</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_projection" xml:space="preserve">
|
||||
<value>Field of view, aspect ratio, orthographic or not</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_resets" xml:space="preserve">
|
||||
<value>How often the game reset the upscaler's history</value>
|
||||
</data>
|
||||
<data name="Adv_sl_deepdvc_options" xml:space="preserve">
|
||||
<value>RTX Dynamic Vibrance's options</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_alpha_upscaling" xml:space="preserve">
|
||||
<value>DLSS upscales the alpha channel</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_auto_exposure" xml:space="preserve">
|
||||
<value>DLSS auto-exposure</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_exposure" xml:space="preserve">
|
||||
<value>Pre-exposure and exposure scale given to DLSS</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_hdr_input" xml:space="preserve">
|
||||
<value>The game told DLSS its colour buffers are HDR</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_optimal_settings" xml:space="preserve">
|
||||
<value>The render size and sharpness DLSS recommends</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_output_size" xml:space="preserve">
|
||||
<value>The output size the game gave DLSS</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_presets" xml:space="preserve">
|
||||
<value>The DLSS model preset per quality mode</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_vram_estimate" xml:space="preserve">
|
||||
<value>DLSS's own estimate of its video memory</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlssd_options" xml:space="preserve">
|
||||
<value>Ray reconstruction's options</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlssg_frames_presented" xml:space="preserve">
|
||||
<value>Frames DLSS frame generation presented, by its own count</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlssg_options" xml:space="preserve">
|
||||
<value>DLSS frame generation: mode, frames to generate</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlssg_state" xml:space="preserve">
|
||||
<value>DLSS frame generation: status, the most frames it can generate</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlssg_vram_estimate" xml:space="preserve">
|
||||
<value>DLSS frame generation's estimate of its video memory</value>
|
||||
</data>
|
||||
<data name="Adv_sl_feature_requirements" xml:space="preserve">
|
||||
<value>What each Streamline feature requires: operating system, driver, buffers</value>
|
||||
</data>
|
||||
<data name="Adv_sl_feature_lifecycle" xml:space="preserve">
|
||||
<value>Each feature switched on or off, its resources allocated and freed, Streamline shut down</value>
|
||||
</data>
|
||||
<data name="Adv_sl_feature_support" xml:space="preserve">
|
||||
<value>Whether Streamline says each feature is supported, and loaded</value>
|
||||
</data>
|
||||
<data name="Adv_sl_feature_versions" xml:space="preserve">
|
||||
<value>Each Streamline feature's version and its NGX model version</value>
|
||||
</data>
|
||||
<data name="Adv_sl_init_preferences" xml:space="preserve">
|
||||
<value>The preferences the game started Streamline with</value>
|
||||
</data>
|
||||
<data name="Adv_sl_nis_options" xml:space="preserve">
|
||||
<value>NVIDIA Image Scaling's options</value>
|
||||
</data>
|
||||
<data name="Adv_sl_nvperf" xml:space="preserve">
|
||||
<value>Streamline's performance counters (NSight Perf SDK licence)</value>
|
||||
</data>
|
||||
<data name="Adv_sl_pcl_markers" xml:space="preserve">
|
||||
<value>PC-latency markers the game sets</value>
|
||||
</data>
|
||||
<data name="Adv_sl_reflex_state" xml:space="preserve">
|
||||
<value>Reflex through Streamline: availability and its frame reports</value>
|
||||
</data>
|
||||
<data name="Adv_xess_options" xml:space="preserve">
|
||||
<value>XeSS's options</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Band" xml:space="preserve">
|
||||
<value>More than eight series: the lowest, the average and the highest of them are drawn. The table lists each one.</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Empty" xml:space="preserve">
|
||||
<value>Nothing to draw yet.</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Header" xml:space="preserve">
|
||||
<value>Over time</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_LiveNote" xml:space="preserve">
|
||||
<value>The last five minutes, kept in memory only.</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Metric" xml:space="preserve">
|
||||
<value>Show</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Seconds" xml:space="preserve">
|
||||
<value>Seconds from the session's start</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Time" xml:space="preserve">
|
||||
<value>Time</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Name" xml:space="preserve">
|
||||
<value>Reading</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_ReadAt" xml:space="preserve">
|
||||
<value>Read at</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Samples" xml:space="preserve">
|
||||
<value>Readings</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Scope" xml:space="preserve">
|
||||
<value>Belongs to</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Source" xml:space="preserve">
|
||||
<value>Source</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Status" xml:space="preserve">
|
||||
<value>Status</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Value" xml:space="preserve">
|
||||
<value>Value</value>
|
||||
</data>
|
||||
<data name="Advanced_Elevation_Hint" xml:space="preserve">
|
||||
<value>The processor, the memory and the motherboard are read only when the capture agent runs as administrator with PawnIO installed (Settings ▸ Capture agent).</value>
|
||||
</data>
|
||||
<data name="Advanced_Facts_Header" xml:space="preserve">
|
||||
<value>About this PC</value>
|
||||
</data>
|
||||
<data name="Advanced_Header" xml:space="preserve">
|
||||
<value>Advanced metrics</value>
|
||||
</data>
|
||||
<data name="Advanced_InGameCallsLine" xml:space="preserve">
|
||||
<value>What the game tells Streamline each frame: {0}. How it configures FSR frame generation: {1}.</value>
|
||||
</data>
|
||||
<data name="Advanced_InGameDriverLine" xml:space="preserve">
|
||||
<value>NVIDIA's latency report, which FrameLedger asks the graphics driver for inside the game: {0}.</value>
|
||||
</data>
|
||||
<data name="Advanced_InGameFeatureCallsLine" xml:space="preserve">
|
||||
<value>Which version each Streamline feature is: {0}. What each requires: {1}.</value>
|
||||
</data>
|
||||
<data name="Advanced_InGameMoreCallsLine" xml:space="preserve">
|
||||
<value>Streamline's other calls - read: {0}; hooked, the game did not make the call: {1}; not hooked: {2}.</value>
|
||||
</data>
|
||||
<data name="Advanced_InGameLine" xml:space="preserve">
|
||||
<value>Inside the game: {0}.</value>
|
||||
</data>
|
||||
<data name="Advanced_Machine_Intro" xml:space="preserve">
|
||||
<value>What the graphics driver and the hardware sensors say about this PC right now. It is read only while this page is open or a game is being recorded, and nothing shown here is stored.</value>
|
||||
</data>
|
||||
<data name="Advanced_Max" xml:space="preserve">
|
||||
<value>Highest</value>
|
||||
</data>
|
||||
<data name="Advanced_Mean" xml:space="preserve">
|
||||
<value>Average</value>
|
||||
</data>
|
||||
<data name="Advanced_Min" xml:space="preserve">
|
||||
<value>Lowest</value>
|
||||
</data>
|
||||
<data name="Advanced_Now_Header" xml:space="preserve">
|
||||
<value>Right now</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_Empty" xml:space="preserve">
|
||||
<value>No session has been recorded with Advanced metrics on yet. A session recorded while it was off is not filled in later.</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_Facts" xml:space="preserve">
|
||||
<value>The PC and the session</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_NoSeries" xml:space="preserve">
|
||||
<value>This session's per-second series are no longer kept (Settings ▸ Recording ▸ Raw series kept per game); its statistics are.</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_NoStats" xml:space="preserve">
|
||||
<value>No reading was stored for this session.</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_Pick" xml:space="preserve">
|
||||
<value>Session</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_Stats" xml:space="preserve">
|
||||
<value>Statistics of the session</value>
|
||||
</data>
|
||||
<data name="Advanced_Sources_Intro" xml:space="preserve">
|
||||
<value>Everything FrameLedger knows how to read, and everything it does not read, with the reason.</value>
|
||||
</data>
|
||||
<data name="Advanced_SourcesLine" xml:space="preserve">
|
||||
<value>NVIDIA driver: {0}. Graphics-card sensors: {1}. Processor, memory and motherboard sensors: {2}.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_Live" xml:space="preserve">
|
||||
<value>Read by the capture agent at {0}. NVIDIA's figures are read every second, the sensors every five.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_NoAgent" xml:space="preserve">
|
||||
<value>The capture agent is not answering. What is shown below is as old as its time says.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_Off" xml:space="preserve">
|
||||
<value>Advanced metrics is off, so nothing is read. Turn it on in Settings ▸ Recording.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_OlderAgent" xml:space="preserve">
|
||||
<value>The capture agent that is running is an older version and cannot answer this. Restart FrameLedger.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_Viewer" xml:space="preserve">
|
||||
<value>This is a copy of a ledger: nothing is read from this PC. The sessions stored in the copy are under Session.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_Waiting" xml:space="preserve">
|
||||
<value>The capture agent is opening its sources…</value>
|
||||
</data>
|
||||
<data name="Advanced_Status_InGame" xml:space="preserve">
|
||||
<value>Read inside a game FrameLedger measures, when the game makes the call</value>
|
||||
</data>
|
||||
<data name="Advanced_Status_InGameDriver" xml:space="preserve">
|
||||
<value>Read inside a game FrameLedger measures, from the graphics driver: FrameLedger asks for it about once a second</value>
|
||||
</data>
|
||||
<data name="Advanced_Status_Read" xml:space="preserve">
|
||||
<value>Read</value>
|
||||
</data>
|
||||
<data name="Advanced_Status_Readable" xml:space="preserve">
|
||||
<value>Read when a session or this page asks</value>
|
||||
</data>
|
||||
<data name="Advanced_Status_SourceSilent" xml:space="preserve">
|
||||
<value>Not read now: {0}</value>
|
||||
</data>
|
||||
<data name="Advanced_Tab_Machine" xml:space="preserve">
|
||||
<value>This PC</value>
|
||||
</data>
|
||||
<data name="Advanced_Tab_Session" xml:space="preserve">
|
||||
<value>Session</value>
|
||||
</data>
|
||||
<data name="Advanced_Tab_Sources" xml:space="preserve">
|
||||
<value>Sources</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Error" xml:space="preserve">
|
||||
<value>the driver answered with an error</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Faulted" xml:space="preserve">
|
||||
<value>stopped until the game closed - a call into the driver faulted</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_NoDirect3D12" xml:space="preserve">
|
||||
<value>not read - the game does not present through Direct3D 12</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_NoGetter" xml:space="preserve">
|
||||
<value>not read - the library did not answer for the two functions</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_NoModule" xml:space="preserve">
|
||||
<value>not read - the game has not loaded NVIDIA's nvapi64.dll, and FrameLedger never loads it</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_NothingReported" xml:space="preserve">
|
||||
<value>asked, and the driver reported no frame - the game does not use NVIDIA Reflex</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Read" xml:space="preserve">
|
||||
<value>read</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Refused" xml:space="preserve">
|
||||
<value>not read - the nvapi64.dll in the game is in the game's own folder, not the driver's</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Slow" xml:space="preserve">
|
||||
<value>stopped until the game closed - a call into the driver took {0:N0} µs, and one of 2,000 µs or more is the last</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Stalled" xml:space="preserve">
|
||||
<value>stopped - a call into the driver did not return</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Unknown" xml:space="preserve">
|
||||
<value>not stated</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Board" xml:space="preserve">
|
||||
<value>Motherboard</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Cpu" xml:space="preserve">
|
||||
<value>Processor</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Display" xml:space="preserve">
|
||||
<value>Displays</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Driver" xml:space="preserve">
|
||||
<value>Graphics driver</value>
|
||||
</data>
|
||||
<data name="AdvGroup_FrameGeneration" xml:space="preserve">
|
||||
<value>Frame generation</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Gpu" xml:space="preserve">
|
||||
<value>Graphics card</value>
|
||||
</data>
|
||||
<data name="AdvGroup_GpuMemory" xml:space="preserve">
|
||||
<value>Graphics card memory</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Latency" xml:space="preserve">
|
||||
<value>Latency</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Memory" xml:space="preserve">
|
||||
<value>Memory</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Storage" xml:space="preserve">
|
||||
<value>Storage</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Upscaling" xml:space="preserve">
|
||||
<value>Upscaling</value>
|
||||
</data>
|
||||
<data name="AdvInGame_NotHooked" xml:space="preserve">
|
||||
<value>the session was not measured inside the game</value>
|
||||
</data>
|
||||
<data name="AdvInGame_NothingSeen" xml:space="preserve">
|
||||
<value>the game made none of the calls these are read from</value>
|
||||
</data>
|
||||
<data name="AdvInGame_Reading" xml:space="preserve">
|
||||
<value>read from the game's own calls</value>
|
||||
</data>
|
||||
<data name="AdvInGame_Unknown" xml:space="preserve">
|
||||
<value>not known</value>
|
||||
</data>
|
||||
<data name="AdvInGameCall_NeverCalled" xml:space="preserve">
|
||||
<value>hooked - the game did not make the call</value>
|
||||
</data>
|
||||
<data name="AdvInGameCall_NotAskedAgain" xml:space="preserve">
|
||||
<value>hooked - the game asks this while it starts, and did not ask again after FrameLedger attached</value>
|
||||
</data>
|
||||
<data name="AdvInGameCall_NotHooked" xml:space="preserve">
|
||||
<value>not hooked - the game did not load the library that has the call</value>
|
||||
</data>
|
||||
<data name="AdvInGameCall_Read" xml:space="preserve">
|
||||
<value>read</value>
|
||||
</data>
|
||||
<data name="AdvInGameCall_Unknown" xml:space="preserve">
|
||||
<value>not known</value>
|
||||
</data>
|
||||
<data name="AdvReach_Deferred" xml:space="preserve">
|
||||
<value>Not read in this release</value>
|
||||
</data>
|
||||
<data name="AdvReach_Game" xml:space="preserve">
|
||||
<value>Inside a game FrameLedger measures</value>
|
||||
</data>
|
||||
<data name="AdvReach_HookedCall" xml:space="preserve">
|
||||
<value>Inside the game - comes with a later release</value>
|
||||
</data>
|
||||
<data name="AdvReach_Identifier" xml:space="preserve">
|
||||
<value>Never read: it identifies this PC, a display or another program</value>
|
||||
</data>
|
||||
<data name="AdvReach_Licence" xml:space="preserve">
|
||||
<value>Not read: the vendor's licence does not allow it</value>
|
||||
</data>
|
||||
<data name="AdvReach_NewHook" xml:space="preserve">
|
||||
<value>Inside the game, with a new hook - comes with a later release</value>
|
||||
</data>
|
||||
<data name="AdvReach_BeforeAttach" xml:space="preserve">
|
||||
<value>Not read: the game makes this call once, before FrameLedger is inside it</value>
|
||||
</data>
|
||||
<data name="AdvReach_NotInHeaders" xml:space="preserve">
|
||||
<value>Not offered by this interface</value>
|
||||
</data>
|
||||
<data name="AdvReach_PlayerState" xml:space="preserve">
|
||||
<value>Never read: it is the player's state in the game</value>
|
||||
</data>
|
||||
<data name="AdvReach_Refused" xml:space="preserve">
|
||||
<value>Not read: it would make the sensor library search every USB device</value>
|
||||
</data>
|
||||
<data name="AdvReach_RefusedRoute" xml:space="preserve">
|
||||
<value>Not read: it would take a patch at an address found while the game runs, a function of FrameLedger's handed to the game in place of the vendor's, or a call the vendor forbids from outside the game's own threads - all refused</value>
|
||||
</data>
|
||||
<data name="AdvReach_Spike" xml:space="preserve">
|
||||
<value>Being studied; not decided</value>
|
||||
</data>
|
||||
<data name="AdvScope_MachineFact" xml:space="preserve">
|
||||
<value>This PC</value>
|
||||
</data>
|
||||
<data name="AdvScope_Series" xml:space="preserve">
|
||||
<value>A session, over time</value>
|
||||
</data>
|
||||
<data name="AdvScope_SessionFact" xml:space="preserve">
|
||||
<value>A session</value>
|
||||
</data>
|
||||
<data name="AdvSource_Faulted" xml:space="preserve">
|
||||
<value>failed while reading</value>
|
||||
</data>
|
||||
<data name="AdvSource_NotElevated" xml:space="preserve">
|
||||
<value>the capture agent is not running as administrator</value>
|
||||
</data>
|
||||
<data name="AdvSource_NotPresent" xml:space="preserve">
|
||||
<value>not present on this PC</value>
|
||||
</data>
|
||||
<data name="AdvSource_PawnIoMissing" xml:space="preserve">
|
||||
<value>PawnIO is not installed</value>
|
||||
</data>
|
||||
<data name="AdvSource_Reading" xml:space="preserve">
|
||||
<value>answering</value>
|
||||
</data>
|
||||
<data name="AdvSource_Unknown" xml:space="preserve">
|
||||
<value>not asked yet</value>
|
||||
</data>
|
||||
<data name="AdvToken_adaptive_sync" xml:space="preserve">
|
||||
<value>Adaptive sync</value>
|
||||
</data>
|
||||
<data name="AdvToken_agp" xml:space="preserve">
|
||||
<value>AGP</value>
|
||||
</data>
|
||||
<data name="AdvToken_axi" xml:space="preserve">
|
||||
<value>AXI</value>
|
||||
</data>
|
||||
<data name="AdvToken_bt2100_pq" xml:space="preserve">
|
||||
<value>BT.2100 PQ (HDR10)</value>
|
||||
</data>
|
||||
<data name="AdvToken_desktop" xml:space="preserve">
|
||||
<value>Desktop</value>
|
||||
</data>
|
||||
<data name="AdvToken_discrete" xml:space="preserve">
|
||||
<value>Discrete</value>
|
||||
</data>
|
||||
<data name="AdvToken_dolby_vision" xml:space="preserve">
|
||||
<value>Dolby Vision</value>
|
||||
</data>
|
||||
<data name="AdvToken_driver" xml:space="preserve">
|
||||
<value>driver</value>
|
||||
</data>
|
||||
<data name="AdvToken_driver_default" xml:space="preserve">
|
||||
<value>Driver default</value>
|
||||
</data>
|
||||
<data name="AdvToken_draw_debug_view" xml:space="preserve">
|
||||
<value>Debug view</value>
|
||||
</data>
|
||||
<data name="AdvToken_edr" xml:space="preserve">
|
||||
<value>EDR</value>
|
||||
</data>
|
||||
<data name="AdvToken_fpci" xml:space="preserve">
|
||||
<value>FPCI</value>
|
||||
</data>
|
||||
<data name="AdvToken_game_ready" xml:space="preserve">
|
||||
<value>Game Ready</value>
|
||||
</data>
|
||||
<data name="AdvToken_active_render" xml:space="preserve">
|
||||
<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 (between the driver's start and end marks)</value>
|
||||
</data>
|
||||
<data name="AdvToken_gsync_module" xml:space="preserve">
|
||||
<value>G-SYNC module</value>
|
||||
</data>
|
||||
<data name="AdvToken_hdr10" xml:space="preserve">
|
||||
<value>HDR10</value>
|
||||
</data>
|
||||
<data name="AdvToken_hdr10_plus" xml:space="preserve">
|
||||
<value>HDR10+</value>
|
||||
</data>
|
||||
<data name="AdvToken_hdr10_plus_gaming" xml:space="preserve">
|
||||
<value>HDR10+ Gaming</value>
|
||||
</data>
|
||||
<data name="AdvToken_integrated" xml:space="preserve">
|
||||
<value>Integrated</value>
|
||||
</data>
|
||||
<data name="AdvToken_laptop" xml:space="preserve">
|
||||
<value>Laptop</value>
|
||||
</data>
|
||||
<data name="AdvToken_no_profile_for_game" xml:space="preserve">
|
||||
<value>The driver has no profile for this game</value>
|
||||
</data>
|
||||
<data name="AdvToken_non_linear_color_pq" xml:space="preserve">
|
||||
<value>Non-linear colour, PQ</value>
|
||||
</data>
|
||||
<data name="AdvToken_non_linear_color_srgb" xml:space="preserve">
|
||||
<value>Non-linear colour, sRGB</value>
|
||||
</data>
|
||||
<data name="AdvToken_none" xml:space="preserve">
|
||||
<value>None</value>
|
||||
</data>
|
||||
<data name="AdvToken_not_a_number" xml:space="preserve">
|
||||
<value>Not a number</value>
|
||||
</data>
|
||||
<data name="AdvToken_not_radians" xml:space="preserve">
|
||||
<value>Not radians: the value is larger than π. The game probably gives degrees.</value>
|
||||
</data>
|
||||
<data name="AdvToken_not_supported" xml:space="preserve">
|
||||
<value>Not supported</value>
|
||||
</data>
|
||||
<data name="AdvToken_off" xml:space="preserve">
|
||||
<value>Off</value>
|
||||
</data>
|
||||
<data name="AdvToken_on" xml:space="preserve">
|
||||
<value>On</value>
|
||||
</data>
|
||||
<data name="AdvToken_on_and_off" xml:space="preserve">
|
||||
<value>On at times, off at others</value>
|
||||
</data>
|
||||
<data name="AdvToken_os_queue" xml:space="preserve">
|
||||
<value>operating system's render queue</value>
|
||||
</data>
|
||||
<data name="AdvToken_pci" xml:space="preserve">
|
||||
<value>PCI</value>
|
||||
</data>
|
||||
<data name="AdvToken_pci_express" xml:space="preserve">
|
||||
<value>PCI Express</value>
|
||||
</data>
|
||||
<data name="AdvToken_present" xml:space="preserve">
|
||||
<value>present</value>
|
||||
</data>
|
||||
<data name="AdvToken_render_submit" xml:space="preserve">
|
||||
<value>render submit</value>
|
||||
</data>
|
||||
<data name="AdvToken_rtx_new_feature" xml:space="preserve">
|
||||
<value>RTX new-feature branch</value>
|
||||
</data>
|
||||
<data name="AdvToken_rtx_production" xml:space="preserve">
|
||||
<value>RTX production branch</value>
|
||||
</data>
|
||||
<data name="AdvToken_scrgb_linear" xml:space="preserve">
|
||||
<value>scRGB (linear)</value>
|
||||
</data>
|
||||
<data name="AdvToken_simulation" xml:space="preserve">
|
||||
<value>simulation</value>
|
||||
</data>
|
||||
<data name="AdvToken_srgb" xml:space="preserve">
|
||||
<value>sRGB</value>
|
||||
</data>
|
||||
<data name="AdvToken_studio" xml:space="preserve">
|
||||
<value>Studio</value>
|
||||
</data>
|
||||
<data name="AdvToken_total" xml:space="preserve">
|
||||
<value>total, simulation start to GPU render end</value>
|
||||
</data>
|
||||
<data name="AdvToken_ulmb" xml:space="preserve">
|
||||
<value>ULMB</value>
|
||||
</data>
|
||||
<data name="AdvToken_usable_now" xml:space="preserve">
|
||||
<value>Usable at the current mode</value>
|
||||
</data>
|
||||
<data name="AdvToken_user_set" xml:space="preserve">
|
||||
<value>Set by the user</value>
|
||||
</data>
|
||||
<data name="AdvToken_variable_refresh" xml:space="preserve">
|
||||
<value>Variable refresh</value>
|
||||
</data>
|
||||
<data name="Agent_Banner_Missing_Body" xml:space="preserve">
|
||||
<value>FrameLedger.Agent.exe was not found beside this application. Sessions are still readable; live status and capture control are not.</value>
|
||||
</data>
|
||||
@@ -1161,9 +282,6 @@
|
||||
<data name="Menu_Tools_VulkanLayer" xml:space="preserve">
|
||||
<value>Vulkan layer registration…</value>
|
||||
</data>
|
||||
<data name="Nav_Advanced" xml:space="preserve">
|
||||
<value>Advanced</value>
|
||||
</data>
|
||||
<data name="Nav_Compare" xml:space="preserve">
|
||||
<value>Compare</value>
|
||||
</data>
|
||||
@@ -1191,12 +309,6 @@
|
||||
<data name="Rules_Update_Failed" xml:space="preserve">
|
||||
<value>The agent did not answer the rules update.</value>
|
||||
</data>
|
||||
<data name="Settings_Advanced_Body" xml:space="preserve">
|
||||
<value>Read more from the graphics driver and the hardware sensors during a session - the graphics card's memory and load in detail, each fan and voltage, what your display can do, the driver's settings for the game - and, in a game FrameLedger measures from inside, what the game tells DLSS, Streamline and FSR (sizes, presets, sharpening, exposure, the depth range, how frame generation is configured - never where the camera is). On an NVIDIA card, in a Direct3D 12 game that uses NVIDIA's own library, FrameLedger also asks the graphics driver about once a second, from inside the game, how long each stage of a frame took - a call it makes itself on the thread that shows the game's frames. All of it is stored with the session. Off: nothing more is read or stored, inside a game either. It applies from the next session, and a session recorded while it was off is not filled in later.</value>
|
||||
</data>
|
||||
<data name="Settings_Advanced_Label" xml:space="preserve">
|
||||
<value>Advanced metrics</value>
|
||||
</data>
|
||||
<data name="Settings_Appearance_Header" xml:space="preserve">
|
||||
<value>Appearance</value>
|
||||
</data>
|
||||
@@ -1842,9 +954,6 @@
|
||||
<data name="Sessions_Col_Tier" xml:space="preserve">
|
||||
<value>Tier</value>
|
||||
</data>
|
||||
<data name="Summary_Advanced_Button" xml:space="preserve">
|
||||
<value>Advanced metrics…</value>
|
||||
</data>
|
||||
<data name="Tier_Dash_Tooltip" xml:space="preserve">
|
||||
<value>—: frame generation was measured as none, so there is no displayed rate distinct from the native one</value>
|
||||
</data>
|
||||
@@ -2383,7 +1492,7 @@
|
||||
<value>Running elevated.</value>
|
||||
</data>
|
||||
<data name="Settings_Agent_Elevation_Body" xml:space="preserve">
|
||||
<value>Elevation is not required by any capture tier. It optionally unlocks CPU temperature and, with Advanced metrics on, the processor's, the memory's and the motherboard's sensors (both through PawnIO), and attaching to games that run elevated themselves. Everything else — hooking, measuring, recording — works without it.</value>
|
||||
<value>Elevation is not required by any capture tier. It optionally unlocks CPU temperature (through PawnIO) and attaching to games that run elevated themselves. Everything else — hooking, measuring, recording — works without it.</value>
|
||||
</data>
|
||||
<data name="Settings_Agent_Elevation_Label" xml:space="preserve">
|
||||
<value>Elevation</value>
|
||||
@@ -2650,7 +1759,7 @@
|
||||
<value>Accept</value>
|
||||
</data>
|
||||
<data name="FirstRun_Agent_Body" xml:space="preserve">
|
||||
<value>FrameLedger starts a small capture agent beside itself, as a standard user — not elevated. Elevation is optional and is not required by any capture tier: it only unlocks CPU temperature and, with Advanced metrics on, the processor's, the memory's and the motherboard's sensors (both through PawnIO), and attaching to games that run elevated themselves. Below is what the agent reports about this machine.</value>
|
||||
<value>FrameLedger starts a small capture agent beside itself, as a standard user — not elevated. Elevation is optional and is not required by any capture tier: it only unlocks CPU temperature (through PawnIO) and attaching to games that run elevated themselves. Below is what the agent reports about this machine.</value>
|
||||
</data>
|
||||
<data name="FirstRun_Agent_Header" xml:space="preserve">
|
||||
<value>The capture agent</value>
|
||||
|
||||
@@ -13,888 +13,9 @@
|
||||
<resheader name="writer">
|
||||
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
|
||||
</resheader>
|
||||
<data name="A11y_Advanced_Metric" xml:space="preserve">
|
||||
<value>Chỉ số để vẽ biểu đồ</value>
|
||||
</data>
|
||||
<data name="A11y_Advanced_Session" xml:space="preserve">
|
||||
<value>Phiên để hiển thị</value>
|
||||
</data>
|
||||
<data name="A11y_Chart_Advanced" xml:space="preserve">
|
||||
<value>Chỉ số nâng cao theo thời gian</value>
|
||||
</data>
|
||||
<data name="A11y_ChartData_Advanced" xml:space="preserve">
|
||||
<value>Mỗi đường là một chỉ số. Bảng cạnh biểu đồ liệt kê cùng các chỉ số đó.</value>
|
||||
</data>
|
||||
<data name="About_Title" xml:space="preserve">
|
||||
<value>Giới thiệu FrameLedger</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_framegen_config" xml:space="preserve">
|
||||
<value>Cấu hình tạo khung hình FSR của game</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_memory_usage" xml:space="preserve">
|
||||
<value>Bộ nhớ video của riêng FSR, khi game hỏi</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_depth" xml:space="preserve">
|
||||
<value>Mặt phẳng gần, xa và khoảng góc nhìn đưa cho FSR</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_exposure" xml:space="preserve">
|
||||
<value>Tiền phơi sáng đưa cho FSR</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_flags" xml:space="preserve">
|
||||
<value>Các cờ trong lệnh dispatch FSR của game</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_frame_time_delta" xml:space="preserve">
|
||||
<value>Thời gian khung hình game báo cho FSR</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_jitter" xml:space="preserve">
|
||||
<value>Độ lệch jitter lớn nhất game đưa cho FSR</value>
|
||||
</data>
|
||||
<data name="Adv_ffx_upscale_sharpening" xml:space="preserve">
|
||||
<value>Làm nét của FSR: bật hay tắt, và cường độ</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_battery" xml:space="preserve">
|
||||
<value>Cảm biến pin</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_fan" xml:space="preserve">
|
||||
<value>Tốc độ của từng chân cắm quạt</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_fan_control" xml:space="preserve">
|
||||
<value>Mức điều khiển của từng chân cắm quạt</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_model" xml:space="preserve">
|
||||
<value>Hãng và model bo mạch chủ</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_sensor_chip" xml:space="preserve">
|
||||
<value>Chip cảm biến của bo mạch</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_temperature" xml:space="preserve">
|
||||
<value>Các cảm biến nhiệt độ của bo mạch</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_board_voltage" xml:space="preserve">
|
||||
<value>Các đường điện áp của bo mạch</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_controller" xml:space="preserve">
|
||||
<value>Cảm biến bộ điều khiển quạt: cũng phải dò thiết bị USB như vậy</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_cpu_clock" xml:space="preserve">
|
||||
<value>Xung của từng nhân, và xung bus</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_cpu_load" xml:space="preserve">
|
||||
<value>Tải bộ xử lý: tổng và từng nhân</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_cpu_power" xml:space="preserve">
|
||||
<value>Công suất bộ xử lý: cả gói, các nhân</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_cpu_temperature" xml:space="preserve">
|
||||
<value>Nhiệt độ bộ xử lý: cả gói và từng nhân</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_cpu_voltage" xml:space="preserve">
|
||||
<value>Các điện áp của bộ xử lý</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_clock" xml:space="preserve">
|
||||
<value>Mọi xung nhịp của card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_current" xml:space="preserve">
|
||||
<value>Mọi dòng điện của card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_fan" xml:space="preserve">
|
||||
<value>Mọi quạt của card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_fan_control" xml:space="preserve">
|
||||
<value>Mức điều khiển của từng quạt</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_load" xml:space="preserve">
|
||||
<value>Mọi mức tải của card: các bộ xử lý, bus, bộ điều khiển bộ nhớ</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_memory" xml:space="preserve">
|
||||
<value>Các bộ đếm bộ nhớ của card: tổng, trống, đã dùng, Direct3D chuyên dụng và dùng chung</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_power" xml:space="preserve">
|
||||
<value>Mọi số đo công suất của card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_temperature" xml:space="preserve">
|
||||
<value>Mọi cảm biến nhiệt độ của card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_throughput" xml:space="preserve">
|
||||
<value>Lưu lượng PCI Express đến và đi từ card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_gpu_voltage" xml:space="preserve">
|
||||
<value>Mọi điện áp của card</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_memory_load" xml:space="preserve">
|
||||
<value>Bộ nhớ đang dùng: vật lý và ảo</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_memory_modules" xml:space="preserve">
|
||||
<value>Các thanh nhớ: dung lượng, tốc độ, tên linh kiện của hãng - không bao giờ có số sê-ri</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_memory_temperature" xml:space="preserve">
|
||||
<value>Nhiệt độ từng thanh nhớ, nếu có cảm biến</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_psu" xml:space="preserve">
|
||||
<value>Cảm biến bộ nguồn: đọc chúng khiến thư viện dò mọi thiết bị USB</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_storage_models" xml:space="preserve">
|
||||
<value>Tên model các ổ đĩa: thư viện không liệt kê được ổ mà không chạm vào ổ tháo rời</value>
|
||||
</data>
|
||||
<data name="Adv_lhm_storage_temperature" xml:space="preserve">
|
||||
<value>Nhiệt độ từng ổ đĩa: cùng lý do, nên nhóm lưu trữ không được mở</value>
|
||||
</data>
|
||||
<data name="Adv_ngx_parameters" xml:space="preserve">
|
||||
<value>Tham số NGX: giá trị chất lượng, các gợi ý DLSS</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_clock_video" xml:space="preserve">
|
||||
<value>Xung video</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_adaptive_sync_off" xml:space="preserve">
|
||||
<value>Adaptive sync đang tắt trên màn hình</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_edid" xml:space="preserve">
|
||||
<value>Khối EDID của màn hình, có chứa số sê-ri của nó</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_hdr_formats" xml:space="preserve">
|
||||
<value>Định dạng HDR màn hình nhận: HDR10, HDR10+, HDR10+ Gaming, Dolby Vision, EDR</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_luminance_max" xml:space="preserve">
|
||||
<value>Độ chói tối đa của màn hình cho nội dung HDR</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_luminance_max_frame_average" xml:space="preserve">
|
||||
<value>Mức sáng trung bình khung hình tối đa của màn hình</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_luminance_min" xml:space="preserve">
|
||||
<value>Độ chói tối thiểu của màn hình</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_max_frame_interval" xml:space="preserve">
|
||||
<value>Khoảng khung hình dài nhất mà adaptive sync được đặt để giữ</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_display_vrr_support" xml:space="preserve">
|
||||
<value>Tần số quét biến thiên: có hỗ trợ, mô-đun G-SYNC hay adaptive sync, ULMB, dùng được ở chế độ hiện tại</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_base_branch" xml:space="preserve">
|
||||
<value>Nhánh gốc của driver</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_chipset" xml:space="preserve">
|
||||
<value>Hãng và tên chipset, theo driver báo</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_dch" xml:space="preserve">
|
||||
<value>Driver là gói DCH</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_global_profile" xml:space="preserve">
|
||||
<value>Mọi thiết lập trong profile toàn cục của driver, chỉ đọc</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_interface_version" xml:space="preserve">
|
||||
<value>Phiên bản giao diện của chính NVAPI</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_driver_package" xml:space="preserve">
|
||||
<value>Game Ready, Studio hay một nhánh RTX doanh nghiệp</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_encoder_fps" xml:space="preserve">
|
||||
<value>Tốc độ mã hoá trung bình của các phiên đang chạy</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_encoder_latency" xml:space="preserve">
|
||||
<value>Độ trễ mã hoá trung bình</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_encoder_session_processes" xml:space="preserve">
|
||||
<value>Những chương trình nào đang mã hoá</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_encoder_sessions" xml:space="preserve">
|
||||
<value>Số phiên mã hoá phần cứng đang chạy, mọi chương trình</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_architecture" xml:space="preserve">
|
||||
<value>Kiến trúc chip, bản triển khai và phiên bản</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_board_serial" xml:space="preserve">
|
||||
<value>Số sê-ri bo mạch của card</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_bus_type" xml:space="preserve">
|
||||
<value>Bus mà card cắm vào</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_clock_base_core" xml:space="preserve">
|
||||
<value>Xung nhân cơ sở</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_clock_base_memory" xml:space="preserve">
|
||||
<value>Xung bộ nhớ cơ sở</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_clock_boost_core" xml:space="preserve">
|
||||
<value>Xung nhân tăng tốc</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_clock_boost_memory" xml:space="preserve">
|
||||
<value>Xung bộ nhớ tăng tốc</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_core_count" xml:space="preserve">
|
||||
<value>Số nhân đồ hoạ</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_external" xml:space="preserve">
|
||||
<value>Card là card gắn ngoài</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_fan_duty" xml:space="preserve">
|
||||
<value>Mức điều khiển quạt qua NVAPI (LibreHardwareMonitor đọc số này)</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_pci_ids" xml:space="preserve">
|
||||
<value>Mã PCI của thiết bị, hệ con và phiên bản - là model, không phải từng chiếc</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_power" xml:space="preserve">
|
||||
<value>Công suất card qua NVAPI (LibreHardwareMonitor đọc số này)</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_ram_bus_width" xml:space="preserve">
|
||||
<value>Độ rộng bus bộ nhớ của card</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_ram_type" xml:space="preserve">
|
||||
<value>Loại bộ nhớ của card</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_rt_cores" xml:space="preserve">
|
||||
<value>Số nhân dò tia</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_system_type" xml:space="preserve">
|
||||
<value>Laptop hay máy bàn, theo cách driver nhìn máy</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_temp_default_max" xml:space="preserve">
|
||||
<value>Nhiệt độ tối đa mặc định của cảm biến nhân</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_tensor_cores" xml:space="preserve">
|
||||
<value>Số nhân tensor</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_type" xml:space="preserve">
|
||||
<value>Đồ hoạ tích hợp hay rời</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_uuid" xml:space="preserve">
|
||||
<value>Mã định danh duy nhất của card</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_vbios_version" xml:space="preserve">
|
||||
<value>Phiên bản Video BIOS</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_gpu_voltage" xml:space="preserve">
|
||||
<value>Điện áp card qua NVAPI (LibreHardwareMonitor đọc số này)</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_limit_ac_battery" xml:space="preserve">
|
||||
<value>Bị kìm do chuyển sang pin ở lần đọc: 100 hoặc 0</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_limit_api" xml:space="preserve">
|
||||
<value>Bị kìm theo yêu cầu của một chương trình ở lần đọc: 100 hoặc 0</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_limit_insufficient_power" xml:space="preserve">
|
||||
<value>Bị kìm do thiếu đầu cấp nguồn ở lần đọc: 100 hoặc 0</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_load_bus" xml:space="preserve">
|
||||
<value>Mức dùng giao tiếp bus</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_load_framebuffer" xml:space="preserve">
|
||||
<value>Mức dùng frame buffer (bộ điều khiển bộ nhớ)</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_load_video" xml:space="preserve">
|
||||
<value>Mức dùng bộ xử lý video</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_pstate" xml:space="preserve">
|
||||
<value>Trạng thái hiệu năng hiện tại của card (mã P-state)</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_reflex_frame_report" xml:space="preserve">
|
||||
<value>Độ trễ từng khung hình: mô phỏng, gửi lệnh dựng hình, present, driver, hàng đợi hệ điều hành, GPU dựng hình</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_reflex_gpu_times" xml:space="preserve">
|
||||
<value>Thời gian của card đồ hoạ cho mỗi khung hình, do driver tự tính: lúc thực sự vẽ, và từ khung này sang khung kế</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_reflex_mode" xml:space="preserve">
|
||||
<value>Reflex: chế độ độ trễ thấp, boost, giới hạn tốc độ khung hình</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_reflex_sleep_status" xml:space="preserve">
|
||||
<value>Trạng thái độ trễ thấp của driver</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_driver_profile" xml:space="preserve">
|
||||
<value>Các thiết lập mà profile của driver cho game này tự đặt, chỉ đọc</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_source_colorspace" xml:space="preserve">
|
||||
<value>Không gian màu game xuất ra, theo driver báo cho tiến trình</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_vrr_display_mode" xml:space="preserve">
|
||||
<value>Chính màn hình đã ở chế độ tần số quét biến thiên</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_vrr_enabled" xml:space="preserve">
|
||||
<value>Tần số quét biến thiên đã hoạt động trên màn hình của game</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_vrr_possible" xml:space="preserve">
|
||||
<value>Tần số quét biến thiên khả dụng trên màn hình đó</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_session_vrr_requested" xml:space="preserve">
|
||||
<value>Tần số quét biến thiên đã được yêu cầu cho màn hình đó</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_temp_board" xml:space="preserve">
|
||||
<value>Nhiệt độ môi trường trên bo của card, nếu card có cảm biến</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_temp_power_supply" xml:space="preserve">
|
||||
<value>Nhiệt độ khối cấp nguồn của card, nếu card có cảm biến</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_available" xml:space="preserve">
|
||||
<value>Bộ nhớ video chuyên dụng còn trống lúc này, mọi chương trình</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_dedicated" xml:space="preserve">
|
||||
<value>Bộ nhớ video chuyên dụng trên card</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_dedicated_available" xml:space="preserve">
|
||||
<value>Bộ nhớ video chuyên dụng dùng được cho bề mặt</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_eviction_count" xml:space="preserve">
|
||||
<value>Số lần bị đẩy khỏi bộ nhớ video chuyên dụng, tính từ lúc driver nạp</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_evictions_size" xml:space="preserve">
|
||||
<value>Bộ nhớ được giải phóng do bị đẩy ra, tính từ lúc driver nạp</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_framebuffer_physical" xml:space="preserve">
|
||||
<value>Kích thước frame buffer vật lý</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_framebuffer_virtual" xml:space="preserve">
|
||||
<value>Kích thước frame buffer ảo</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_in_use" xml:space="preserve">
|
||||
<value>Bộ nhớ video chuyên dụng đang dùng lúc này, mọi chương trình: phần dùng được cho bề mặt trừ phần còn trống</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_promotion_count" xml:space="preserve">
|
||||
<value>Số lần thăng cấp vào bộ nhớ video chuyên dụng, tính từ lúc driver nạp</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_promotions_size" xml:space="preserve">
|
||||
<value>Bộ nhớ được đưa vào do thăng cấp, tính từ lúc driver nạp</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_shared" xml:space="preserve">
|
||||
<value>Bộ nhớ hệ thống dùng chung driver có thể cấp</value>
|
||||
</data>
|
||||
<data name="Adv_nvapi_vram_system" xml:space="preserve">
|
||||
<value>Bộ nhớ hệ thống driver giữ lúc nạp</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_camera" xml:space="preserve">
|
||||
<value>Vị trí, các trục và ma trận của camera</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_depth" xml:space="preserve">
|
||||
<value>Mặt phẳng gần và xa, và độ sâu có bị đảo hay không</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_jitter" xml:space="preserve">
|
||||
<value>Độ lệch jitter game đưa cho Streamline</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_motion_vectors" xml:space="preserve">
|
||||
<value>Tỉ lệ vector chuyển động, và chúng có là 3D, giãn nở, có jitter hay không</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_projection" xml:space="preserve">
|
||||
<value>Góc nhìn, tỉ lệ khung, phép chiếu trực giao hay không</value>
|
||||
</data>
|
||||
<data name="Adv_sl_constants_resets" xml:space="preserve">
|
||||
<value>Số lần game đặt lại lịch sử của bộ nâng cấp</value>
|
||||
</data>
|
||||
<data name="Adv_sl_deepdvc_options" xml:space="preserve">
|
||||
<value>Các tuỳ chọn của RTX Dynamic Vibrance</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_alpha_upscaling" xml:space="preserve">
|
||||
<value>DLSS nâng cấp cả kênh alpha</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_auto_exposure" xml:space="preserve">
|
||||
<value>Tự động phơi sáng của DLSS</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_exposure" xml:space="preserve">
|
||||
<value>Tiền phơi sáng và hệ số phơi sáng đưa cho DLSS</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_hdr_input" xml:space="preserve">
|
||||
<value>Game báo cho DLSS rằng bộ đệm màu là HDR</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_optimal_settings" xml:space="preserve">
|
||||
<value>Kích thước dựng hình và độ nét DLSS khuyến nghị</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_output_size" xml:space="preserve">
|
||||
<value>Kích thước đầu ra game đưa cho DLSS</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_presets" xml:space="preserve">
|
||||
<value>Preset mô hình DLSS theo từng chế độ chất lượng</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlss_vram_estimate" xml:space="preserve">
|
||||
<value>Ước tính của chính DLSS về bộ nhớ video nó dùng</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlssd_options" xml:space="preserve">
|
||||
<value>Các tuỳ chọn của Ray Reconstruction</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlssg_frames_presented" xml:space="preserve">
|
||||
<value>Số khung tạo khung hình DLSS đã hiển thị, theo bộ đếm của chính nó</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlssg_options" xml:space="preserve">
|
||||
<value>Tạo khung hình DLSS: chế độ, số khung cần tạo</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlssg_state" xml:space="preserve">
|
||||
<value>Tạo khung hình DLSS: trạng thái, số khung tối đa có thể tạo</value>
|
||||
</data>
|
||||
<data name="Adv_sl_dlssg_vram_estimate" xml:space="preserve">
|
||||
<value>Ước tính của tạo khung hình DLSS về bộ nhớ video nó dùng</value>
|
||||
</data>
|
||||
<data name="Adv_sl_feature_requirements" xml:space="preserve">
|
||||
<value>Yêu cầu của từng tính năng Streamline: hệ điều hành, driver, bộ đệm</value>
|
||||
</data>
|
||||
<data name="Adv_sl_feature_lifecycle" xml:space="preserve">
|
||||
<value>Từng tính năng được bật hay tắt, tài nguyên được cấp và giải phóng, Streamline bị đóng</value>
|
||||
</data>
|
||||
<data name="Adv_sl_feature_support" xml:space="preserve">
|
||||
<value>Streamline nói từng tính năng có được hỗ trợ không, và có đang nạp không</value>
|
||||
</data>
|
||||
<data name="Adv_sl_feature_versions" xml:space="preserve">
|
||||
<value>Phiên bản từng tính năng Streamline và phiên bản mô hình NGX của nó</value>
|
||||
</data>
|
||||
<data name="Adv_sl_init_preferences" xml:space="preserve">
|
||||
<value>Các tuỳ chọn game dùng khi khởi động Streamline</value>
|
||||
</data>
|
||||
<data name="Adv_sl_nis_options" xml:space="preserve">
|
||||
<value>Các tuỳ chọn của NVIDIA Image Scaling</value>
|
||||
</data>
|
||||
<data name="Adv_sl_nvperf" xml:space="preserve">
|
||||
<value>Bộ đếm hiệu năng của Streamline (giấy phép NSight Perf SDK)</value>
|
||||
</data>
|
||||
<data name="Adv_sl_pcl_markers" xml:space="preserve">
|
||||
<value>Các mốc PC-latency game đặt</value>
|
||||
</data>
|
||||
<data name="Adv_sl_reflex_state" xml:space="preserve">
|
||||
<value>Reflex qua Streamline: có khả dụng không và các báo cáo khung hình của nó</value>
|
||||
</data>
|
||||
<data name="Adv_xess_options" xml:space="preserve">
|
||||
<value>Các tuỳ chọn của XeSS</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Band" xml:space="preserve">
|
||||
<value>Hơn tám chuỗi: biểu đồ vẽ giá trị thấp nhất, trung bình và cao nhất của chúng. Bảng liệt kê từng chuỗi.</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Empty" xml:space="preserve">
|
||||
<value>Chưa có gì để vẽ.</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Header" xml:space="preserve">
|
||||
<value>Theo thời gian</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_LiveNote" xml:space="preserve">
|
||||
<value>Năm phút gần nhất, chỉ giữ trong bộ nhớ.</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Metric" xml:space="preserve">
|
||||
<value>Hiển thị</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Seconds" xml:space="preserve">
|
||||
<value>Giây tính từ đầu phiên</value>
|
||||
</data>
|
||||
<data name="Advanced_Chart_Time" xml:space="preserve">
|
||||
<value>Thời gian</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Name" xml:space="preserve">
|
||||
<value>Chỉ số</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_ReadAt" xml:space="preserve">
|
||||
<value>Đọc lúc</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Samples" xml:space="preserve">
|
||||
<value>Số lần đọc</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Scope" xml:space="preserve">
|
||||
<value>Thuộc về</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Source" xml:space="preserve">
|
||||
<value>Nguồn</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Status" xml:space="preserve">
|
||||
<value>Trạng thái</value>
|
||||
</data>
|
||||
<data name="Advanced_Col_Value" xml:space="preserve">
|
||||
<value>Giá trị</value>
|
||||
</data>
|
||||
<data name="Advanced_Elevation_Hint" xml:space="preserve">
|
||||
<value>Bộ xử lý, bộ nhớ và bo mạch chỉ được đọc khi capture agent chạy quyền quản trị và máy đã cài PawnIO (Cài đặt ▸ Capture agent).</value>
|
||||
</data>
|
||||
<data name="Advanced_Facts_Header" xml:space="preserve">
|
||||
<value>Về máy này</value>
|
||||
</data>
|
||||
<data name="Advanced_Header" xml:space="preserve">
|
||||
<value>Thông số nâng cao</value>
|
||||
</data>
|
||||
<data name="Advanced_InGameCallsLine" xml:space="preserve">
|
||||
<value>Những gì game báo cho Streamline mỗi khung hình: {0}. Cách game cấu hình frame generation của FSR: {1}.</value>
|
||||
</data>
|
||||
<data name="Advanced_InGameDriverLine" xml:space="preserve">
|
||||
<value>Báo cáo độ trễ của NVIDIA, do FrameLedger hỏi driver đồ họa ngay bên trong game: {0}.</value>
|
||||
</data>
|
||||
<data name="Advanced_InGameFeatureCallsLine" xml:space="preserve">
|
||||
<value>Mỗi tính năng Streamline là phiên bản nào: {0}. Mỗi tính năng cần gì: {1}.</value>
|
||||
</data>
|
||||
<data name="Advanced_InGameMoreCallsLine" xml:space="preserve">
|
||||
<value>Các lời gọi khác của Streamline - đã đọc: {0}; đã hook, game không gọi: {1}; chưa hook: {2}.</value>
|
||||
</data>
|
||||
<data name="Advanced_InGameLine" xml:space="preserve">
|
||||
<value>Bên trong game: {0}.</value>
|
||||
</data>
|
||||
<data name="Advanced_Machine_Intro" xml:space="preserve">
|
||||
<value>Những gì driver đồ hoạ và các cảm biến phần cứng cho biết về máy này lúc này. Chỉ được đọc khi trang này đang mở hoặc đang ghi một game, và những gì hiện ở đây không được lưu.</value>
|
||||
</data>
|
||||
<data name="Advanced_Max" xml:space="preserve">
|
||||
<value>Cao nhất</value>
|
||||
</data>
|
||||
<data name="Advanced_Mean" xml:space="preserve">
|
||||
<value>Trung bình</value>
|
||||
</data>
|
||||
<data name="Advanced_Min" xml:space="preserve">
|
||||
<value>Thấp nhất</value>
|
||||
</data>
|
||||
<data name="Advanced_Now_Header" xml:space="preserve">
|
||||
<value>Lúc này</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_Empty" xml:space="preserve">
|
||||
<value>Chưa có phiên nào được ghi khi Thông số nâng cao đang bật. Phiên ghi lúc tắt sẽ không được bổ sung về sau.</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_Facts" xml:space="preserve">
|
||||
<value>Máy và phiên</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_NoSeries" xml:space="preserve">
|
||||
<value>Chuỗi theo giây của phiên này không còn được giữ (Cài đặt ▸ Ghi phiên ▸ Số chuỗi thô giữ lại mỗi game); thống kê thì vẫn còn.</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_NoStats" xml:space="preserve">
|
||||
<value>Phiên này không lưu số đo nào.</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_Pick" xml:space="preserve">
|
||||
<value>Phiên</value>
|
||||
</data>
|
||||
<data name="Advanced_Session_Stats" xml:space="preserve">
|
||||
<value>Thống kê của phiên</value>
|
||||
</data>
|
||||
<data name="Advanced_Sources_Intro" xml:space="preserve">
|
||||
<value>Mọi thứ FrameLedger biết cách đọc, và mọi thứ nó không đọc, kèm lý do.</value>
|
||||
</data>
|
||||
<data name="Advanced_SourcesLine" xml:space="preserve">
|
||||
<value>Driver NVIDIA: {0}. Cảm biến card đồ hoạ: {1}. Cảm biến bộ xử lý, bộ nhớ và bo mạch: {2}.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_Live" xml:space="preserve">
|
||||
<value>Capture agent đọc lúc {0}. Số liệu của NVIDIA được đọc mỗi giây, các cảm biến mỗi năm giây.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_NoAgent" xml:space="preserve">
|
||||
<value>Capture agent không trả lời. Những gì hiện bên dưới cũ đúng như thời điểm ghi kèm.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_Off" xml:space="preserve">
|
||||
<value>Thông số nâng cao đang tắt nên không đọc gì cả. Bật ở Cài đặt ▸ Ghi phiên.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_OlderAgent" xml:space="preserve">
|
||||
<value>Capture agent đang chạy là bản cũ hơn và không trả lời được yêu cầu này. Hãy khởi động lại FrameLedger.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_Viewer" xml:space="preserve">
|
||||
<value>Đây là bản sao của một sổ ghi: không đọc gì từ máy này. Các phiên lưu trong bản sao nằm ở thẻ Phiên.</value>
|
||||
</data>
|
||||
<data name="Advanced_State_Waiting" xml:space="preserve">
|
||||
<value>Capture agent đang mở các nguồn đọc…</value>
|
||||
</data>
|
||||
<data name="Advanced_Status_InGame" xml:space="preserve">
|
||||
<value>Được đọc bên trong game mà FrameLedger đo, khi game thực hiện lời gọi đó</value>
|
||||
</data>
|
||||
<data name="Advanced_Status_InGameDriver" xml:space="preserve">
|
||||
<value>Được đọc bên trong game mà FrameLedger đo, từ driver đồ họa: FrameLedger hỏi khoảng mỗi giây một lần</value>
|
||||
</data>
|
||||
<data name="Advanced_Status_Read" xml:space="preserve">
|
||||
<value>Đang đọc</value>
|
||||
</data>
|
||||
<data name="Advanced_Status_Readable" xml:space="preserve">
|
||||
<value>Được đọc khi một phiên hoặc trang này yêu cầu</value>
|
||||
</data>
|
||||
<data name="Advanced_Status_SourceSilent" xml:space="preserve">
|
||||
<value>Hiện không đọc được: {0}</value>
|
||||
</data>
|
||||
<data name="Advanced_Tab_Machine" xml:space="preserve">
|
||||
<value>Máy này</value>
|
||||
</data>
|
||||
<data name="Advanced_Tab_Session" xml:space="preserve">
|
||||
<value>Phiên</value>
|
||||
</data>
|
||||
<data name="Advanced_Tab_Sources" xml:space="preserve">
|
||||
<value>Nguồn</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Error" xml:space="preserve">
|
||||
<value>driver trả về lỗi</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Faulted" xml:space="preserve">
|
||||
<value>đã dừng cho tới khi đóng game - một lời gọi vào driver gặp lỗi (fault)</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_NoDirect3D12" xml:space="preserve">
|
||||
<value>không đọc - game không hiển thị qua Direct3D 12</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_NoGetter" xml:space="preserve">
|
||||
<value>không đọc - thư viện không trả về hai hàm cần gọi</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_NoModule" xml:space="preserve">
|
||||
<value>không đọc - game chưa nạp nvapi64.dll của NVIDIA, và FrameLedger không bao giờ nạp nó</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_NothingReported" xml:space="preserve">
|
||||
<value>đã hỏi, driver không báo khung hình nào - game không dùng NVIDIA Reflex</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Read" xml:space="preserve">
|
||||
<value>đã đọc</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Refused" xml:space="preserve">
|
||||
<value>không đọc - nvapi64.dll trong game nằm ở chính thư mục của game, không phải của driver</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Slow" xml:space="preserve">
|
||||
<value>đã dừng cho tới khi đóng game - một lời gọi vào driver mất {0:N0} µs, và lời gọi từ 2.000 µs trở lên là lời gọi cuối</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Stalled" xml:space="preserve">
|
||||
<value>đã dừng - một lời gọi vào driver không trả về</value>
|
||||
</data>
|
||||
<data name="AdvDriverRead_Unknown" xml:space="preserve">
|
||||
<value>không được ghi</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Board" xml:space="preserve">
|
||||
<value>Bo mạch chủ</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Cpu" xml:space="preserve">
|
||||
<value>Bộ xử lý</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Display" xml:space="preserve">
|
||||
<value>Màn hình</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Driver" xml:space="preserve">
|
||||
<value>Driver đồ hoạ</value>
|
||||
</data>
|
||||
<data name="AdvGroup_FrameGeneration" xml:space="preserve">
|
||||
<value>Tạo khung hình</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Gpu" xml:space="preserve">
|
||||
<value>Card đồ hoạ</value>
|
||||
</data>
|
||||
<data name="AdvGroup_GpuMemory" xml:space="preserve">
|
||||
<value>Bộ nhớ card đồ hoạ</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Latency" xml:space="preserve">
|
||||
<value>Độ trễ</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Memory" xml:space="preserve">
|
||||
<value>Bộ nhớ</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Storage" xml:space="preserve">
|
||||
<value>Lưu trữ</value>
|
||||
</data>
|
||||
<data name="AdvGroup_Upscaling" xml:space="preserve">
|
||||
<value>Nâng cấp hình ảnh</value>
|
||||
</data>
|
||||
<data name="AdvInGame_NotHooked" xml:space="preserve">
|
||||
<value>phiên này không được đo bên trong game</value>
|
||||
</data>
|
||||
<data name="AdvInGame_NothingSeen" xml:space="preserve">
|
||||
<value>game không thực hiện lời gọi nào để đọc các mục này</value>
|
||||
</data>
|
||||
<data name="AdvInGame_Reading" xml:space="preserve">
|
||||
<value>đã đọc từ chính các lời gọi của game</value>
|
||||
</data>
|
||||
<data name="AdvInGame_Unknown" xml:space="preserve">
|
||||
<value>không rõ</value>
|
||||
</data>
|
||||
<data name="AdvInGameCall_NeverCalled" xml:space="preserve">
|
||||
<value>đã hook - game không thực hiện lời gọi</value>
|
||||
</data>
|
||||
<data name="AdvInGameCall_NotAskedAgain" xml:space="preserve">
|
||||
<value>đã hook - game hỏi điều này lúc khởi động và không hỏi lại sau khi FrameLedger gắn vào</value>
|
||||
</data>
|
||||
<data name="AdvInGameCall_NotHooked" xml:space="preserve">
|
||||
<value>chưa hook - game không nạp thư viện chứa lời gọi này</value>
|
||||
</data>
|
||||
<data name="AdvInGameCall_Read" xml:space="preserve">
|
||||
<value>đã đọc</value>
|
||||
</data>
|
||||
<data name="AdvInGameCall_Unknown" xml:space="preserve">
|
||||
<value>không rõ</value>
|
||||
</data>
|
||||
<data name="AdvReach_Deferred" xml:space="preserve">
|
||||
<value>Không đọc trong bản phát hành này</value>
|
||||
</data>
|
||||
<data name="AdvReach_Game" xml:space="preserve">
|
||||
<value>Bên trong game mà FrameLedger đo</value>
|
||||
</data>
|
||||
<data name="AdvReach_HookedCall" xml:space="preserve">
|
||||
<value>Bên trong game - sẽ có ở bản phát hành sau</value>
|
||||
</data>
|
||||
<data name="AdvReach_Identifier" xml:space="preserve">
|
||||
<value>Không bao giờ đọc: nó định danh máy này, một màn hình hoặc chương trình khác</value>
|
||||
</data>
|
||||
<data name="AdvReach_Licence" xml:space="preserve">
|
||||
<value>Không đọc: giấy phép của hãng không cho phép</value>
|
||||
</data>
|
||||
<data name="AdvReach_NewHook" xml:space="preserve">
|
||||
<value>Bên trong game, cần hook mới - sẽ có ở bản phát hành sau</value>
|
||||
</data>
|
||||
<data name="AdvReach_BeforeAttach" xml:space="preserve">
|
||||
<value>Không đọc: game gọi lời gọi này một lần, trước khi FrameLedger vào trong game</value>
|
||||
</data>
|
||||
<data name="AdvReach_NotInHeaders" xml:space="preserve">
|
||||
<value>Giao diện này không cung cấp</value>
|
||||
</data>
|
||||
<data name="AdvReach_PlayerState" xml:space="preserve">
|
||||
<value>Không bao giờ đọc: đó là trạng thái của người chơi trong game</value>
|
||||
</data>
|
||||
<data name="AdvReach_Refused" xml:space="preserve">
|
||||
<value>Không đọc: việc này khiến thư viện cảm biến dò mọi thiết bị USB</value>
|
||||
</data>
|
||||
<data name="AdvReach_RefusedRoute" xml:space="preserve">
|
||||
<value>Không đọc: việc đó cần vá mã tại một địa chỉ chỉ tìm được khi game đang chạy, hoặc đưa cho game một hàm của FrameLedger thay cho hàm của nhà cung cấp, hoặc một lời gọi mà nhà cung cấp cấm thực hiện từ ngoài luồng của game - tất cả đều bị từ chối</value>
|
||||
</data>
|
||||
<data name="AdvReach_Spike" xml:space="preserve">
|
||||
<value>Đang nghiên cứu; chưa quyết định</value>
|
||||
</data>
|
||||
<data name="AdvScope_MachineFact" xml:space="preserve">
|
||||
<value>Máy này</value>
|
||||
</data>
|
||||
<data name="AdvScope_Series" xml:space="preserve">
|
||||
<value>Một phiên, theo thời gian</value>
|
||||
</data>
|
||||
<data name="AdvScope_SessionFact" xml:space="preserve">
|
||||
<value>Một phiên</value>
|
||||
</data>
|
||||
<data name="AdvSource_Faulted" xml:space="preserve">
|
||||
<value>gặp lỗi khi đọc</value>
|
||||
</data>
|
||||
<data name="AdvSource_NotElevated" xml:space="preserve">
|
||||
<value>capture agent không chạy quyền quản trị</value>
|
||||
</data>
|
||||
<data name="AdvSource_NotPresent" xml:space="preserve">
|
||||
<value>không có trên máy này</value>
|
||||
</data>
|
||||
<data name="AdvSource_PawnIoMissing" xml:space="preserve">
|
||||
<value>chưa cài PawnIO</value>
|
||||
</data>
|
||||
<data name="AdvSource_Reading" xml:space="preserve">
|
||||
<value>đang trả lời</value>
|
||||
</data>
|
||||
<data name="AdvSource_Unknown" xml:space="preserve">
|
||||
<value>chưa được hỏi</value>
|
||||
</data>
|
||||
<data name="AdvToken_adaptive_sync" xml:space="preserve">
|
||||
<value>Adaptive sync</value>
|
||||
</data>
|
||||
<data name="AdvToken_agp" xml:space="preserve">
|
||||
<value>AGP</value>
|
||||
</data>
|
||||
<data name="AdvToken_axi" xml:space="preserve">
|
||||
<value>AXI</value>
|
||||
</data>
|
||||
<data name="AdvToken_bt2100_pq" xml:space="preserve">
|
||||
<value>BT.2100 PQ (HDR10)</value>
|
||||
</data>
|
||||
<data name="AdvToken_desktop" xml:space="preserve">
|
||||
<value>Máy bàn</value>
|
||||
</data>
|
||||
<data name="AdvToken_discrete" xml:space="preserve">
|
||||
<value>Rời</value>
|
||||
</data>
|
||||
<data name="AdvToken_dolby_vision" xml:space="preserve">
|
||||
<value>Dolby Vision</value>
|
||||
</data>
|
||||
<data name="AdvToken_driver" xml:space="preserve">
|
||||
<value>driver</value>
|
||||
</data>
|
||||
<data name="AdvToken_driver_default" xml:space="preserve">
|
||||
<value>Mặc định của driver</value>
|
||||
</data>
|
||||
<data name="AdvToken_draw_debug_view" xml:space="preserve">
|
||||
<value>Chế độ xem gỡ lỗi</value>
|
||||
</data>
|
||||
<data name="AdvToken_edr" xml:space="preserve">
|
||||
<value>EDR</value>
|
||||
</data>
|
||||
<data name="AdvToken_fpci" xml:space="preserve">
|
||||
<value>FPCI</value>
|
||||
</data>
|
||||
<data name="AdvToken_game_ready" xml:space="preserve">
|
||||
<value>Game Ready</value>
|
||||
</data>
|
||||
<data name="AdvToken_active_render" xml:space="preserve">
|
||||
<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ẽ (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>
|
||||
</data>
|
||||
<data name="AdvToken_hdr10" xml:space="preserve">
|
||||
<value>HDR10</value>
|
||||
</data>
|
||||
<data name="AdvToken_hdr10_plus" xml:space="preserve">
|
||||
<value>HDR10+</value>
|
||||
</data>
|
||||
<data name="AdvToken_hdr10_plus_gaming" xml:space="preserve">
|
||||
<value>HDR10+ Gaming</value>
|
||||
</data>
|
||||
<data name="AdvToken_integrated" xml:space="preserve">
|
||||
<value>Tích hợp</value>
|
||||
</data>
|
||||
<data name="AdvToken_laptop" xml:space="preserve">
|
||||
<value>Laptop</value>
|
||||
</data>
|
||||
<data name="AdvToken_no_profile_for_game" xml:space="preserve">
|
||||
<value>Driver không có profile cho game này</value>
|
||||
</data>
|
||||
<data name="AdvToken_non_linear_color_pq" xml:space="preserve">
|
||||
<value>Màu phi tuyến, PQ</value>
|
||||
</data>
|
||||
<data name="AdvToken_non_linear_color_srgb" xml:space="preserve">
|
||||
<value>Màu phi tuyến, sRGB</value>
|
||||
</data>
|
||||
<data name="AdvToken_none" xml:space="preserve">
|
||||
<value>Không có</value>
|
||||
</data>
|
||||
<data name="AdvToken_not_a_number" xml:space="preserve">
|
||||
<value>Không phải số</value>
|
||||
</data>
|
||||
<data name="AdvToken_not_radians" xml:space="preserve">
|
||||
<value>Không phải radian: giá trị lớn hơn π. Có lẽ game đưa giá trị bằng độ.</value>
|
||||
</data>
|
||||
<data name="AdvToken_not_supported" xml:space="preserve">
|
||||
<value>Không hỗ trợ</value>
|
||||
</data>
|
||||
<data name="AdvToken_off" xml:space="preserve">
|
||||
<value>Tắt</value>
|
||||
</data>
|
||||
<data name="AdvToken_on" xml:space="preserve">
|
||||
<value>Bật</value>
|
||||
</data>
|
||||
<data name="AdvToken_on_and_off" xml:space="preserve">
|
||||
<value>Lúc bật, lúc tắt</value>
|
||||
</data>
|
||||
<data name="AdvToken_os_queue" xml:space="preserve">
|
||||
<value>hàng đợi vẽ của hệ điều hành</value>
|
||||
</data>
|
||||
<data name="AdvToken_pci" xml:space="preserve">
|
||||
<value>PCI</value>
|
||||
</data>
|
||||
<data name="AdvToken_pci_express" xml:space="preserve">
|
||||
<value>PCI Express</value>
|
||||
</data>
|
||||
<data name="AdvToken_present" xml:space="preserve">
|
||||
<value>present</value>
|
||||
</data>
|
||||
<data name="AdvToken_render_submit" xml:space="preserve">
|
||||
<value>gửi lệnh vẽ</value>
|
||||
</data>
|
||||
<data name="AdvToken_rtx_new_feature" xml:space="preserve">
|
||||
<value>Nhánh RTX tính năng mới</value>
|
||||
</data>
|
||||
<data name="AdvToken_rtx_production" xml:space="preserve">
|
||||
<value>Nhánh RTX production</value>
|
||||
</data>
|
||||
<data name="AdvToken_scrgb_linear" xml:space="preserve">
|
||||
<value>scRGB (tuyến tính)</value>
|
||||
</data>
|
||||
<data name="AdvToken_simulation" xml:space="preserve">
|
||||
<value>mô phỏng</value>
|
||||
</data>
|
||||
<data name="AdvToken_srgb" xml:space="preserve">
|
||||
<value>sRGB</value>
|
||||
</data>
|
||||
<data name="AdvToken_studio" xml:space="preserve">
|
||||
<value>Studio</value>
|
||||
</data>
|
||||
<data name="AdvToken_total" xml:space="preserve">
|
||||
<value>tổng, từ đầu mô phỏng tới khi GPU vẽ xong</value>
|
||||
</data>
|
||||
<data name="AdvToken_ulmb" xml:space="preserve">
|
||||
<value>ULMB</value>
|
||||
</data>
|
||||
<data name="AdvToken_usable_now" xml:space="preserve">
|
||||
<value>Dùng được ở chế độ hiện tại</value>
|
||||
</data>
|
||||
<data name="AdvToken_user_set" xml:space="preserve">
|
||||
<value>Do người dùng đặt</value>
|
||||
</data>
|
||||
<data name="AdvToken_variable_refresh" xml:space="preserve">
|
||||
<value>Tần số quét biến thiên</value>
|
||||
</data>
|
||||
<data name="Agent_Banner_Missing_Body" xml:space="preserve">
|
||||
<value>Không tìm thấy FrameLedger.Agent.exe cạnh ứng dụng. Vẫn đọc được các phiên chơi; trạng thái trực tiếp và điều khiển thu thập thì không.</value>
|
||||
</data>
|
||||
@@ -1156,9 +277,6 @@
|
||||
<data name="Menu_Tools_VulkanLayer" xml:space="preserve">
|
||||
<value>Đăng ký Vulkan layer…</value>
|
||||
</data>
|
||||
<data name="Nav_Advanced" xml:space="preserve">
|
||||
<value>Nâng cao</value>
|
||||
</data>
|
||||
<data name="Nav_Compare" xml:space="preserve">
|
||||
<value>So sánh</value>
|
||||
</data>
|
||||
@@ -1186,12 +304,6 @@
|
||||
<data name="Rules_Update_Failed" xml:space="preserve">
|
||||
<value>Agent không phản hồi yêu cầu cập nhật quy tắc.</value>
|
||||
</data>
|
||||
<data name="Settings_Advanced_Body" xml:space="preserve">
|
||||
<value>Đọc thêm từ driver đồ hoạ và các cảm biến phần cứng trong lúc ghi phiên - bộ nhớ và tải của card đồ hoạ ở mức chi tiết, từng quạt và điện áp, khả năng của màn hình, thiết lập của driver cho game - và, với game mà FrameLedger đo từ bên trong, những gì game đưa cho DLSS, Streamline và FSR (kích thước, preset, làm nét, phơi sáng, khoảng độ sâu, cách cấu hình frame generation - không bao giờ là vị trí camera). Với card NVIDIA, trong game Direct3D 12 có dùng thư viện của NVIDIA, FrameLedger còn hỏi driver đồ hoạ khoảng mỗi giây một lần, ngay bên trong game, xem từng chặng của một khung hình mất bao lâu - đây là lời gọi do chính FrameLedger thực hiện trên luồng hiển thị khung hình của game. Tất cả được lưu cùng phiên. Tắt: không đọc và không lưu thêm gì, kể cả bên trong game. Áp dụng từ phiên kế tiếp; phiên đã ghi lúc tắt sẽ không được bổ sung về sau.</value>
|
||||
</data>
|
||||
<data name="Settings_Advanced_Label" xml:space="preserve">
|
||||
<value>Thông số nâng cao</value>
|
||||
</data>
|
||||
<data name="Settings_Appearance_Header" xml:space="preserve">
|
||||
<value>Giao diện</value>
|
||||
</data>
|
||||
@@ -1837,9 +949,6 @@
|
||||
<data name="Sessions_Col_Tier" xml:space="preserve">
|
||||
<value>Tier</value>
|
||||
</data>
|
||||
<data name="Summary_Advanced_Button" xml:space="preserve">
|
||||
<value>Thông số nâng cao…</value>
|
||||
</data>
|
||||
<data name="Tier_Dash_Tooltip" xml:space="preserve">
|
||||
<value>—: đã đo là không có frame generation, nên không có FPS hiển thị khác với FPS gốc</value>
|
||||
</data>
|
||||
@@ -2378,7 +1487,7 @@
|
||||
<value>Đang chạy với quyền quản trị.</value>
|
||||
</data>
|
||||
<data name="Settings_Agent_Elevation_Body" xml:space="preserve">
|
||||
<value>Không tier nào cần quyền quản trị. Nó chỉ tuỳ chọn mở khoá nhiệt độ CPU và, khi bật Thông số nâng cao, cảm biến của bộ xử lý, bộ nhớ và bo mạch (đều qua PawnIO), cùng việc gắn vào game tự chạy với quyền quản trị. Mọi thứ khác — hook, đo, ghi — đều chạy không cần.</value>
|
||||
<value>Không tier nào cần quyền quản trị. Nó chỉ tuỳ chọn mở khoá nhiệt độ CPU (qua PawnIO) và gắn vào game tự chạy với quyền quản trị. Mọi thứ khác — hook, đo, ghi — đều chạy không cần.</value>
|
||||
</data>
|
||||
<data name="Settings_Agent_Elevation_Label" xml:space="preserve">
|
||||
<value>Quyền quản trị</value>
|
||||
@@ -2645,7 +1754,7 @@
|
||||
<value>Chấp nhận</value>
|
||||
</data>
|
||||
<data name="FirstRun_Agent_Body" xml:space="preserve">
|
||||
<value>FrameLedger khởi động một capture agent nhỏ bên cạnh nó, với quyền người dùng thường — không nâng quyền. Nâng quyền là tuỳ chọn và không tier thu thập nào yêu cầu: nó chỉ mở khoá nhiệt độ CPU và, khi bật Thông số nâng cao, cảm biến của bộ xử lý, bộ nhớ và bo mạch (đều qua PawnIO), cùng việc gắn vào game tự chạy với quyền quản trị. Bên dưới là những gì agent báo cáo về máy này.</value>
|
||||
<value>FrameLedger khởi động một capture agent nhỏ bên cạnh nó, với quyền người dùng thường — không nâng quyền. Nâng quyền là tuỳ chọn và không tier thu thập nào yêu cầu: nó chỉ mở khoá nhiệt độ CPU (qua PawnIO) và gắn vào game tự chạy với quyền quản trị. Bên dưới là những gì agent báo cáo về máy này.</value>
|
||||
</data>
|
||||
<data name="FirstRun_Agent_Header" xml:space="preserve">
|
||||
<value>Capture agent</value>
|
||||
|
||||
@@ -1,13 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
namespace FrameLedger.App.ViewModels;
|
||||
|
||||
/// <summary>One row under a table-valued fact of the Advanced page: a driver setting, a memory module.</summary>
|
||||
/// <param name="Name">What the row is, in the words it was stored with.</param>
|
||||
/// <param name="Value">Its value, a token of it in this language.</param>
|
||||
public sealed record AdvancedDetailRow(string Name, string Value)
|
||||
{
|
||||
/// <summary>What a screen reader says for the row: its name and its value.</summary>
|
||||
public override string ToString() => Name + ": " + Value;
|
||||
}
|
||||
@@ -1,13 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
namespace FrameLedger.App.ViewModels;
|
||||
|
||||
/// <summary>The facts of one group of the catalog - the graphics card, the displays - under its heading.</summary>
|
||||
/// <param name="Title">The group in this language.</param>
|
||||
/// <param name="Rows">Its facts, in the catalog's order.</param>
|
||||
public sealed record AdvancedFactGroup(string Title, IReadOnlyList<AdvancedFactRow> Rows)
|
||||
{
|
||||
/// <summary>What a screen reader says for the group: its title.</summary>
|
||||
public override string ToString() => Title;
|
||||
}
|
||||
@@ -1,17 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
namespace FrameLedger.App.ViewModels;
|
||||
|
||||
/// <summary>One fact of the Advanced page: what it is, its value in one line, and the rows of a table-valued one.</summary>
|
||||
/// <param name="Label">The catalog entry in this language, with the display or device it is about.</param>
|
||||
/// <param name="Value">The value in its unit; for a table, how many rows it has.</param>
|
||||
/// <param name="Details">The rows of a table-valued fact; empty for every other.</param>
|
||||
public sealed record AdvancedFactRow(string Label, string Value, IReadOnlyList<AdvancedDetailRow> Details)
|
||||
{
|
||||
/// <summary>Whether there are rows to unfold.</summary>
|
||||
public bool HasDetails => Details.Count > 0;
|
||||
|
||||
/// <summary>What a screen reader says for the row: its label and its value.</summary>
|
||||
public override string ToString() => Label + ": " + Value;
|
||||
}
|
||||
@@ -1,165 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
using System.Globalization;
|
||||
using FrameLedger.Application.Advanced;
|
||||
|
||||
namespace FrameLedger.App.ViewModels;
|
||||
|
||||
/// <summary>
|
||||
/// The words of the Advanced page (owner decision D101): a catalog entry's label, a group's, a token's, a source's
|
||||
/// state — each a key of <c>Strings.resx</c> made from the thing's own name — and a value in its unit.
|
||||
/// </summary>
|
||||
/// <remarks>
|
||||
/// A key that is not there reads as the thing's own name, never as nothing: a ledger written by a newer build can
|
||||
/// hold a token this build has no word for, and the page shows what was stored.
|
||||
/// </remarks>
|
||||
public static class AdvancedLabels
|
||||
{
|
||||
/// <summary>A catalog entry's label; its English summary where no string names it.</summary>
|
||||
public static string Of(AdvancedMetric metric)
|
||||
{
|
||||
ArgumentNullException.ThrowIfNull(metric);
|
||||
return Lookup(metric.LabelKey) ?? metric.Summary;
|
||||
}
|
||||
|
||||
/// <summary>A member of a family: the family's label and what the hardware calls the member.</summary>
|
||||
public static string Member(string family, string? member) => string.IsNullOrWhiteSpace(member) ? family : family + " — " + member;
|
||||
|
||||
public static string Group(AdvancedGroup group) => Lookup("AdvGroup_" + group) ?? group.ToString();
|
||||
|
||||
public static string Scope(AdvancedScope scope) => Lookup("AdvScope_" + scope) ?? scope.ToString();
|
||||
|
||||
/// <summary>A source's name. These are the vendors' own names and are the same in every language.</summary>
|
||||
public static string Source(AdvancedSource source) => source switch
|
||||
{
|
||||
AdvancedSource.Nvapi => "NVAPI",
|
||||
AdvancedSource.Lhm => "LibreHardwareMonitor",
|
||||
AdvancedSource.Streamline => "Streamline",
|
||||
AdvancedSource.FidelityFx => "FidelityFX",
|
||||
AdvancedSource.Ngx => "NGX",
|
||||
AdvancedSource.Xess => "XeSS",
|
||||
_ => source.ToString(),
|
||||
};
|
||||
|
||||
/// <summary>Why an entry that is not read is not.</summary>
|
||||
public static string Reach(AdvancedReach reach) => Lookup("AdvReach_" + reach) ?? reach.ToString();
|
||||
|
||||
public static string Status(AdvancedSourceStatus status) => Lookup("AdvSource_" + status) ?? status.ToString();
|
||||
|
||||
/// <summary>What became, in one session, of the entries read inside the game (0.1.0-beta.40).</summary>
|
||||
public static string InGame(AdvancedInGameStatus status) => Lookup("AdvInGame_" + status) ?? status.ToString();
|
||||
|
||||
/// <summary>What became of one call hooked only for Advanced metrics, in a session (0.1.0-beta.43).</summary>
|
||||
public static string InGameCall(AdvancedInGameCall call) => Lookup("AdvInGameCall_" + call) ?? call.ToString();
|
||||
|
||||
/// <summary>
|
||||
/// The same for a call a game makes while it starts (0.1.0-beta.44): hooked and not seen is then "the game did not
|
||||
/// ask again after FrameLedger attached" - the usual case, and not a finding about the game.
|
||||
/// </summary>
|
||||
public static string InGameStartupCall(AdvancedInGameCall call) =>
|
||||
call == AdvancedInGameCall.NeverCalled ? Strings.AdvInGameCall_NotAskedAgain : InGameCall(call);
|
||||
|
||||
/// <summary>A token the driver's answer was mapped to; the token itself where this build has no word for it.</summary>
|
||||
public static string Token(string token) => Lookup("AdvToken_" + token) ?? token;
|
||||
|
||||
/// <summary>
|
||||
/// What became of the driver's latency report in a session, in words. A read stopped for being slow says how
|
||||
/// slow: <paramref name="slowestUs"/> is the session's slowest call into the driver, in microseconds.
|
||||
/// </summary>
|
||||
public static string DriverRead(AdvancedDriverRead read, int? slowestUs)
|
||||
{
|
||||
string text = Lookup("AdvDriverRead_" + read) ?? read.ToString();
|
||||
return read == AdvancedDriverRead.Slow ? string.Format(CultureInfo.CurrentCulture, text, slowestUs ?? 0) : text;
|
||||
}
|
||||
|
||||
/// <summary>A number in its unit. A flag is yes or no; a count has no unit.</summary>
|
||||
public static string Number(double value, AdvancedUnit unit)
|
||||
{
|
||||
CultureInfo c = CultureInfo.CurrentCulture;
|
||||
return unit switch
|
||||
{
|
||||
AdvancedUnit.Flag => value != 0 ? Strings.Common_Yes : Strings.Common_No,
|
||||
AdvancedUnit.Celsius => value.ToString("0.#", c) + " °C",
|
||||
AdvancedUnit.Percent => value.ToString("0.#", c) + " %",
|
||||
AdvancedUnit.Megahertz => value.ToString("0.#", c) + " MHz",
|
||||
AdvancedUnit.Mebibytes => value.ToString("N0", c) + " MiB",
|
||||
AdvancedUnit.Watts => value.ToString("0.#", c) + " W",
|
||||
AdvancedUnit.Volts => value.ToString("0.###", c) + " V",
|
||||
AdvancedUnit.Amperes => value.ToString("0.##", c) + " A",
|
||||
AdvancedUnit.Rpm => value.ToString("N0", c) + " RPM",
|
||||
AdvancedUnit.Microseconds => value.ToString("N0", c) + " µs",
|
||||
AdvancedUnit.Milliseconds => value.ToString("0.##", c) + " ms",
|
||||
AdvancedUnit.Nits => value.ToString("0.####", c) + " cd/m²",
|
||||
AdvancedUnit.FramesPerSecond => value.ToString("0.#", c) + " FPS",
|
||||
AdvancedUnit.BytesPerSecond => Rate(value, c),
|
||||
AdvancedUnit.Bits => value.ToString("N0", c) + " bit",
|
||||
_ => value.ToString("0.###", c),
|
||||
};
|
||||
}
|
||||
|
||||
/// <summary>The unit's symbol for a chart's axis; empty where the value has none.</summary>
|
||||
public static string Unit(AdvancedUnit unit) => unit switch
|
||||
{
|
||||
AdvancedUnit.Celsius => "°C",
|
||||
AdvancedUnit.Percent => "%",
|
||||
AdvancedUnit.Megahertz => "MHz",
|
||||
AdvancedUnit.Mebibytes => "MiB",
|
||||
AdvancedUnit.Watts => "W",
|
||||
AdvancedUnit.Volts => "V",
|
||||
AdvancedUnit.Amperes => "A",
|
||||
AdvancedUnit.Rpm => "RPM",
|
||||
AdvancedUnit.Microseconds => "µs",
|
||||
AdvancedUnit.Milliseconds => "ms",
|
||||
AdvancedUnit.Nits => "cd/m²",
|
||||
AdvancedUnit.FramesPerSecond => "FPS",
|
||||
AdvancedUnit.BytesPerSecond => "B/s",
|
||||
AdvancedUnit.Bits => "bit",
|
||||
_ => string.Empty,
|
||||
};
|
||||
|
||||
/// <summary>
|
||||
/// A fact's value in one line: a number in its unit, a text as it is, tokens in this language. A table has no one
|
||||
/// line — its rows are shown under it — so it reads as how many rows it has.
|
||||
/// </summary>
|
||||
public static string Value(AdvancedValue value, AdvancedUnit unit)
|
||||
{
|
||||
ArgumentNullException.ThrowIfNull(value);
|
||||
if (value.Number is double number)
|
||||
{
|
||||
return Number(number, unit);
|
||||
}
|
||||
|
||||
if (value.Tokens is { } tokens)
|
||||
{
|
||||
return tokens.Count == 0 ? Strings.Common_NotAvailable : string.Join(", ", tokens.Select(Token));
|
||||
}
|
||||
|
||||
if (value.Rows is { } rows)
|
||||
{
|
||||
return rows.Count.ToString(CultureInfo.CurrentCulture);
|
||||
}
|
||||
|
||||
return string.IsNullOrEmpty(value.Text) ? Strings.Common_NotAvailable : value.Text;
|
||||
}
|
||||
|
||||
/// <summary>One row of a table-valued fact: its token in this language where it has one, else what was stored.</summary>
|
||||
public static string RowValue(AdvancedRow row)
|
||||
{
|
||||
ArgumentNullException.ThrowIfNull(row);
|
||||
return row.Token is { Length: > 0 } token ? Token(token) : row.Value;
|
||||
}
|
||||
|
||||
private static string Rate(double bytesPerSecond, CultureInfo c) => Math.Abs(bytesPerSecond) switch
|
||||
{
|
||||
>= 1024 * 1024 => (bytesPerSecond / (1024 * 1024)).ToString("0.#", c) + " MiB/s",
|
||||
>= 1024 => (bytesPerSecond / 1024).ToString("0.#", c) + " KiB/s",
|
||||
_ => bytesPerSecond.ToString("0", c) + " B/s",
|
||||
};
|
||||
|
||||
private static string? Lookup(string key)
|
||||
{
|
||||
string? found = Strings.ResourceManager.GetString(key, Strings.Culture);
|
||||
return string.IsNullOrEmpty(found) ? null : found;
|
||||
}
|
||||
}
|
||||
@@ -1,14 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
namespace FrameLedger.App.ViewModels;
|
||||
|
||||
/// <summary>One series as it reads now: its label, its last value in its unit, and when that value was read.</summary>
|
||||
/// <param name="Label">The catalog entry in this language, with the hardware's name for a member of a family.</param>
|
||||
/// <param name="Value">The last value read.</param>
|
||||
/// <param name="ReadAt">The time it was read at - a sensor read every fifth second is as old as this says.</param>
|
||||
public sealed record AdvancedLiveRow(string Label, string Value, string ReadAt)
|
||||
{
|
||||
/// <summary>What a screen reader says for the row: its label and its value.</summary>
|
||||
public override string ToString() => Label + ": " + Value;
|
||||
}
|
||||
@@ -1,10 +0,0 @@
|
||||
// SPDX-License-Identifier: GPL-3.0-only
|
||||
// Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE
|
||||
|
||||
namespace FrameLedger.App.ViewModels;
|
||||
|
||||
/// <summary>A catalog entry the chart can draw, in the selector: its id and its label in this language.</summary>
|
||||
public sealed record AdvancedMetricOption(string Id, string Label)
|
||||
{
|
||||
public override string ToString() => Label;
|
||||
}
|
||||
Loaded 100 of 366 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user