Why does my game judder even at a high frame rate?

Because frame pacing is about consistency, not average frame rate. A game can average 60 FPS while frames arrive at uneven intervals, some taking longer than others, and that unevenness produces judder even though the average looks fine. The causes are inconsistent frame times from spikes, presentation or VSync timing problems, or a frame rate that doesn't align with the display. Average FPS hides this; measuring frame-time consistency reveals it so you can smooth the unevenness.

Should I cap my frame rate to improve pacing?

Often yes. If your hardware can't reliably hold a high frame rate, capping to one it can sustain prevents the jarring bounce between an unholdable high and a jarring low, so frames arrive at steady intervals. A reliably-held cap frequently feels smoother than an uncapped rate that constantly fluctuates, because pacing consistency is what players perceive as smooth, not the peak. Field data showing what each device can sustain helps you choose a cap that holds steadily.

Tips for Improving Frame Pacing

Q: How do I improve frame pacing?

Target consistency over peak frame rate: measure frame-time variance (not average FPS, which hides unevenness), find and smooth the spikes causing uneven frame times (asset loads, GC pauses, bursts), address presentation and VSync timing, and consider capping to a frame rate the hardware can steadily sustain. Players feel evenness more than a high average, so steady frame delivery, not peak FPS, is the goal. Making frames arrive at even intervals is what improves pacing.

Quick answer: Target consistency over peak: measure frame-time variance (not average FPS), find and smooth the spikes causing uneven frames, address presentation and VSync timing, and consider capping to a steadily-sustainable rate.

Frame pacing is how evenly your frames are delivered, and good pacing makes a game feel smooth even at a modest frame rate. Players feel the dips, not the peaks. Here are practical tips for improving frame pacing.

Target Consistency, Not Peak Frame Rate

The core tip: target consistency over peak. Evenly-spaced frames matter more to perceived smoothness than a high average, a game averaging 60 FPS but spiking every second feels worse than a steady 40. So measure frame-time variance, not average FPS, which hides the unevenness.

Bugnet's performance snapshots capture frame-time data from real sessions, so you can see the variance and worst frames behind pacing problems. Measuring consistency is the foundation of improving frame pacing.

Smooth the Spikes Causing Uneven Frames

The tip: find and smooth the spikes that cause uneven frame times, asset loads, garbage-collection pauses, bursts, the same work behind frame drops, and address presentation and VSync timing. Smoothing these makes frames arrive at even intervals, which is what good pacing is.

Bugnet captures frame-time spikes and what caused them, so you can target the unevenness. Eliminating the spikes that disrupt the cadence is the core of better frame pacing.

Consider Capping for Steadiness

The final tip: consider capping to a frame rate the hardware can reliably sustain, so you never bounce between an unholdable high and a jarring low. A reliably-held cap can feel better than an uncapped rate that constantly fluctuates, because the steadiness is what players perceive as smooth.

Bugnet shows what frame rate each device can sustain, so you can choose a cap that holds. So improve frame pacing by targeting consistency, smoothing the spikes, and capping for steadiness, making frames arrive evenly, which is what makes a game feel reliably smooth.

Target consistency over peak: measure frame-time variance (not average FPS), smooth the spikes causing uneven frames, address presentation/VSync timing, and consider capping to a steadily-sustainable rate. Players feel evenness, not peaks.