A game can report 100 FPS and still feel uneven. The reason is that average FPS hides frame-time spikes: the delay between displayed frames. At 60 FPS, each frame takes about 16.7 ms; at 120 FPS, about 8.3 ms. Smooth play depends on keeping those times consistent, not just pushing the average higher.
1. Measure before changing settings
Pick a repeatable scene—an in-game benchmark, a saved replay, or the same location and camera movement. Record:
Use one monitoring tool at a time, such as the game’s built-in overlay or a trusted performance monitor. Run the test for a few minutes; a quick glance at the FPS counter is not a diagnosis.
A useful rough guide:
A mostly flat frame-time graph is generally better than a high average FPS with frequent sharp spikes.
2. Find the bottleneck
Check GPU usage while playing a demanding scene:
Overall CPU usage can be misleading: one busy game thread may limit performance even if the total CPU percentage looks modest.
3. Tune settings in the right order
Start with the settings that usually have the biggest performance impact:
1. Lower ray tracing or disable it for testing.
2. Reduce resolution scale or use the game’s supported upscaling option.
3. Lower volumetric lighting, shadows, and reflections.
4. Reduce texture quality only if VRAM is close to its limit.
5. Change one setting at a time and repeat the same test.
Texture quality often affects video memory more than raw frame rate. If VRAM is full, however, the game may stream textures more aggressively and produce hitching. Don’t lower every setting to “Low” by default; that can make a game uglier without fixing the actual bottleneck.
4. Set a sensible frame-rate limit
An unlimited frame rate can keep the GPU at full load and cause noisy frame pacing or extra heat. Try a cap that your system can hold steadily. For a 144 Hz display, for example, a stable 120 FPS may feel better than fluctuating between 90 and 160.
With a variable-refresh-rate display, enable the relevant display and driver features, then use the game’s frame limiter if it behaves well. If it doesn’t, try the GPU driver’s limiter or a reputable external limiter. Avoid stacking several limiters at once: the game, driver, and overlay can end up arguing over who controls the frames.
5. Check the basics
After each change, compare results in the same scene. If the frame-time graph improves and the game feels smoother, keep the change. If not, revert it and test the next likely cause.
1. Measure before changing settings
Pick a repeatable scene—an in-game benchmark, a saved replay, or the same location and camera movement. Record:
- Average FPS
- 1% low FPS, if your overlay provides it
- Frame-time graph
- GPU usage, CPU usage, temperatures, and clock speeds
Use one monitoring tool at a time, such as the game’s built-in overlay or a trusted performance monitor. Run the test for a few minutes; a quick glance at the FPS counter is not a diagnosis.
A useful rough guide:
Код:
60 FPS = 16.7 ms per frame
90 FPS = 11.1 ms per frame
120 FPS = 8.3 ms per frame
144 FPS = 6.9 ms per frameA mostly flat frame-time graph is generally better than a high average FPS with frequent sharp spikes.
2. Find the bottleneck
Check GPU usage while playing a demanding scene:
- GPU near full usage: Lower GPU-heavy settings first—ray tracing, resolution scale, shadows, volumetric effects, and anti-aliasing.
- GPU usage often low, with uneven performance: The CPU, game engine, background tasks, or asset streaming may be limiting performance.
- Performance drops as the session continues: Check temperatures and clock speeds. Thermal or power limits can reduce performance.
- Stutters when entering new areas: The game may be compiling shaders or loading assets. A faster SSD can help with loading, but it cannot eliminate every engine-related hitch.
Overall CPU usage can be misleading: one busy game thread may limit performance even if the total CPU percentage looks modest.
3. Tune settings in the right order
Start with the settings that usually have the biggest performance impact:
1. Lower ray tracing or disable it for testing.
2. Reduce resolution scale or use the game’s supported upscaling option.
3. Lower volumetric lighting, shadows, and reflections.
4. Reduce texture quality only if VRAM is close to its limit.
5. Change one setting at a time and repeat the same test.
Texture quality often affects video memory more than raw frame rate. If VRAM is full, however, the game may stream textures more aggressively and produce hitching. Don’t lower every setting to “Low” by default; that can make a game uglier without fixing the actual bottleneck.
4. Set a sensible frame-rate limit
An unlimited frame rate can keep the GPU at full load and cause noisy frame pacing or extra heat. Try a cap that your system can hold steadily. For a 144 Hz display, for example, a stable 120 FPS may feel better than fluctuating between 90 and 160.
With a variable-refresh-rate display, enable the relevant display and driver features, then use the game’s frame limiter if it behaves well. If it doesn’t, try the GPU driver’s limiter or a reputable external limiter. Avoid stacking several limiters at once: the game, driver, and overlay can end up arguing over who controls the frames.
5. Check the basics
- Install the latest stable graphics driver, especially when troubleshooting a new game. If a problem began immediately after an update, testing the previous driver can be reasonable.
- Confirm the display is actually set to its intended refresh rate in operating-system display settings.
- Close unnecessary background recording, browser, and launcher overlays for testing.
- Keep the game on an SSD when possible, and leave enough free disk space for updates and temporary files.
- Don’t disable security features or download “FPS booster” scripts from random sites. Most are placebo; some are a memorable way to reinstall Windows.
After each change, compare results in the same scene. If the frame-time graph improves and the game feels smoother, keep the change. If not, revert it and test the next likely cause.
