Repository navigation
User guide
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.
- Install and first start
- Record a game
- Read your results
- Anti-cheat and safety — read this before you switch hooking on for any game
- Your data
- Questions and answers
- The screens — what each page, menu and button does
- Every setting
- When something goes wrong
- Words FrameLedger uses
- 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.
This wiki is generated from the repository at v0.1.0-beta.23. Edit wiki/ or guide/ there: a change made here is overwritten when the next release is published.
Use FrameLedger
- User guide
- Install and first start
- Record a game
- Read your results
- Anti-cheat and safety
- Your data
- Questions and answers
- The screens
- Every setting
- When something goes wrong
- Words FrameLedger uses
- The terms, in plain words
- Limitations
Build or change FrameLedger