* build: the main line on .NET 11 - SDK 11.0.100, net11.0, the three runtime-serviced packages at 11.0.0; Windows 10 stated as untested and unsupported (D94, D95) (beta.37 PR-1) The owner moved the main line to .NET 11 the day after it shipped (D94), setting aside condition (a) of 20_OPEN_QUESTIONS section G's table - two alphas on the released runtime. This is the alpha branch's switch applied to main at released versions, and what follows from it. - global.json 11.0.100 (allowPrerelease false), TFM net11.0-windows10.0.22621.0, Microsoft.Extensions.Hosting, Microsoft.Data.Sqlite and System.Diagnostics.EventLog 11.0.0; legal/licenses/nuget regenerated (78 packages -> 69). - Two CA1307 sites the released SDK raised in tests written after the last alpha was cut take the (char, StringComparison) overload. - IHost.RunAsync rethrows a failed BackgroundService on .NET 11: the Agent's --serve leaves through its crash report where it exited 0. Accepted, not wrapped; HostBackgroundFailureTests holds the runtime's behaviour, which nothing had observed. - release.yml installs a .NET 10 runtime for vpk 1.2.161; Qodana's container installs the .NET 11 SDK first (interim, until the Ultimate linter); Dependabot's and the workflows' comments follow. - Windows 10 22H2 is not blocked, and is stated as untested and unsupported (D95): NFR-8, LIMITATIONS, README, the guide, the wiki. A processor needs SSE4.2 and POPCNT. - docs: 12_BUILD (the main line's .NET; the alpha line rests after alpha.4, D98), 13_CI_CD, 20_OPEN_QUESTIONS row closed, 10_LOGGING, spike-notes section 28, CLAUDE.md, the decisions index (D94-D96, D98). Gate on the dev box: all passed in 338 s on SDK 11.0.100 (native 32/32, 2,561 tests, coverage floors held). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> * build: what this pull request's runs measured on .NET 11 - CodeQL reads net11.0 whole, the delta from beta.36, Qodana's one finding fixed - HostBackgroundFailureTests: the message is kept rather than the exception, so no `!` is needed - the one problem Qodana's interim run reported (run 42916491047, InspectCode 2026.2.3.1 on SDK 11.0.100). - 13_CI_CD: what analyze (csharp, none) read of net11.0 (CodeQL 2.27.4, "scanned 1220 out of 1220 C# files", 363 references resolved, none unresolved), and the rule for C# 15 constructs (D96); the interim's first run. - spike-notes section 28: the table of this pull request's runs - check, CodeQL, SonarCloud, Qodana, and the release rehearsal with the first delta across two runtime majors (72.6 MB, 372 of 443 files patched). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
3.4 KiB
Install and first start
What you need
- Windows 11, 64-bit. FrameLedger may also run on Windows 10 (22H2), but it has not been tested there and nobody supports it: it is built on .NET 11, which Microsoft supports on Windows 11.
- A processor Windows 11 accepts. On an older one, without the SSE4.2 and POPCNT instructions, FrameLedger does not start.
- Games FrameLedger can measure: 64-bit DirectX 11, DirectX 12 and OpenGL games. Other games — 32-bit games, DirectX 9 games, and Vulkan games you start yourself — are still recorded (how long you played, your PC's sensors, the game's memory use), but not measured. Limitations has the full list.
Download and install
- Download
FrameLedger.App-win-Setup.exefrom the project's Releases page on GitHub. - Check the file. Each release publishes SHA-256 checksums in
SHA256SUMS.txt. In PowerShell:Get-FileHash .\FrameLedger.App-win-Setup.exe— the result must match the line for that file. - Run it. FrameLedger is free software and is not code-signed, so Windows SmartScreen may warn about an unknown publisher. Once the checksum matches, choose More info ▸ Run anyway.
FrameLedger installs into %LOCALAPPDATA%\FrameLedger.App and needs no administrator rights. Your recordings are kept
separately, in %LOCALAPPDATA%\FrameLedger.
The first start
The first window walks you through four short steps:
- Before you start — the documents. You accept three: the End User License Agreement, the Disclaimer and the Privacy Policy. The GNU GPL v3 is shown too: it is your licence to FrameLedger and needs no acceptance. A short summary sits above them, and The terms, in plain words explains them, but the documents are the terms. Declining closes FrameLedger.
- The capture agent — the background program that notices when one of your games starts and records it. It runs as you, without administrator rights.
- What hooking means — the difference between a game that is recorded and a game that is measured. Read Anti-cheat and safety before you switch hooking on for any game.
- Your game library — where to import it from. Nothing is measured until you choose to.
Updates
A few seconds after it starts, FrameLedger asks GitHub whether a newer version exists. A new version downloads in the background and is installed only when you restart FrameLedger — never while a game is being measured, and not while a game it measured earlier is still running. You can switch the check off in Settings ▸ Updates ▸ Check for updates at startup, and check by hand with Help ▸ Check for updates.
Settings ▸ Updates ▸ Channel is Automatic unless you choose: a test version (a pre-release, like every version so far) looks for test versions, a release looks for releases. Choose Stable or Beta to decide yourself. Before 0.1.0-beta.14 the channel was Stable by default and found no version at all — on an older copy, choose Beta to update.
An alpha — an experimental build on a new .NET — updates only to newer alphas, and its channel is locked; a beta never updates to an alpha. Installing one, and going back: Alpha builds.
Uninstall
Uninstall FrameLedger from Windows Settings ▸ Apps. It asks before it deletes your recordings folder.