FPS, mouse & performance tools
Start with the setting you want to understand. These tools explain their formulas and assumptions; they do not measure your game’s FPS.
12
- Mouse sensitivity: eDPI, cm/360 and DPI changes
- Horizontal and vertical FOV for a game display
- FPS and frame time budget
- Analyze a game frametime sample
- Summarize gaming ping samples
- Gaming packet loss from sent and received counts
- How much space will a gameplay recording use?
- Game download time from size and bandwidth
- Radial controller deadzone preview
- Crosshair gap and line preview
- Game render scale and pixel workload
- Will a 180-degree turn fit on your mousepad?
Names are source identifiers, not official translations.
Where to start
FPS, mouse & performance tools has 12 entries in this collection, including Mouse sensitivity: eDPI, cm/360 and DPI changes, Horizontal and vertical FOV for a game display, and FPS and frame time budget. Search for the item or character you already know, then open its page to check the recorded variants. The result count is the number of references, not a ranking of recommendations.
Before you choose
At 60 FPS, a frame lasts about 16.67 ms; at 120 FPS, about 8.33 ms; at 144 FPS, about 6.94 ms. Doubling frame rate halves the time available for a frame. The improvement from adding 30 FPS therefore depends on your starting point.
Try your current rate and your target separately, then compare their millisecond budgets. These are steady-rate equivalents. A game can average the target FPS and still have noticeable long frames; use the frametime-sample tool when you have a log.
Sources and scope
Public source snapshot; changes after this version may differ. 2026-11-03