User guide - poli0981/frameledger GitHub Wiki

FrameLedger records how your games run on this PC — frame rate, frame times, the settings a game is really rendering 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 four are there to look things up.

  1. Install and first start
  2. Record a game
  3. Read your results
  4. Anti-cheat and safety — read this before you switch hooking on for any game
  5. Your data
  6. Questions and answers
  7. The screens — what each page, menu and button does
  8. Every setting
  9. When something goes wrong
  10. Words FrameLedger uses
  11. The terms, in plain words

What FrameLedger cannot do is listed on its own page: Limitations (in the app: Help ▸ Limitations).

FrameLedger is beta software. It certainly still has bugs. If something goes wrong, Help ▸ Report a bug… builds a report on your PC that you can look at before you decide to share it.

This guide is part of FrameLedger and describes the version it came with. It is also in the project's repository on GitHub, in the guide folder, and on the project's wiki, which shows the newest release.