Home - poli0981/frameledger GitHub Wiki

FrameLedger records how your games run on this PC — frame rate and frame times, the settings a game really renders with, ray tracing, temperatures, and the game's own memory — and keeps every session so you can compare them later. Everything stays on your PC: no account, no telemetry. It is free software under the GNU GPL v3, for 64-bit Windows 10 (22H2) and Windows 11, and it is in beta.

Download it from the Releases page.

Use FrameLedger

The user guide is the one FrameLedger shows under Help ▸ User guide.

1. Install and first start
2. Record a game
3. Read your results
4. Anti-cheat and safety — read it before you switch hooking on for any game
5. Your data
6. Questions and answers

To look something up: The screens, Every setting, When something goes wrong, Words FrameLedger uses, The terms, in plain words, and Limitations — what FrameLedger cannot do.

Build or change FrameLedger

Start at Developers. The developer pages are short; each says what a part is and links to its full document in docs/.

• Architecture — the processes, and how a frame travels from the game to the screen.
• Repository map — what is where.
• Build and test — the toolchain and the one gate.
• Contributor rules — the rules every change keeps, safety first.
• Capture pipeline, Metrics, Data and IPC, App UI development, Releasing, Developer glossary.

More

• A bug or a question: the project's issues. A game whose anti-cheat FrameLedger missed: the Safety gap form there.
• A vulnerability: SECURITY.md.
• The licence: LICENSE (GPL v3) and NOTICE; the name: legal/TRADEMARKS.md.