What's the difference between stutter and frame drops?

Frame drops are specific, measurable events, individual frames that took too long and missed their time budget (a momentary dip in frame rate). Stutter is the perceived choppiness or hitching players feel when frame delivery is inconsistent, which frame drops cause. So frame drops are the measurable cause, and stutter is the felt symptom; you fix the stutter by eliminating the frame drops behind it.

Why does my game stutter even at 60 FPS?

Because stutter is about consistency (frame pacing), not average frame rate. A game can average 60 FPS while individual frames arrive unevenly, some taking much longer than others, and those frame drops produce the stutter you feel. The average hides the variance. To find the cause, look at frame-time spikes and worst frames rather than average FPS, which reveals the dropped frames behind the perceived stutter.

How do I fix stutter in my game?

Eliminate the frame drops causing it. Find the work that spikes above your frame budget, commonly asset loads, garbage-collection pauses, or bursts of entities or effects, using frame-time data from real sessions, then smooth that work (stream loads, reduce allocations, spread bursts across frames) so frames are delivered consistently. Since stutter is the felt symptom of frame drops, fixing the drops removes the stutter.

Stutter vs Frame Drops: What's the Difference?

Quick answer: Frame drops are individual frames that miss the budget, brief dips; stutter is the perceived choppiness from inconsistent frame pacing, often caused by frame drops. Frame drops are the cause; stutter is the felt symptom.

Stutter and frame drops are closely related performance problems, so close that they're often used interchangeably, but there's a useful distinction between the measurable cause and the felt symptom. Here's how they differ.

What Frame Drops Are

A frame drop is a specific, measurable event: an individual frame that took too long to render, missing its time budget. If your game targets 60 FPS (about 16ms per frame) and a frame takes 40ms, that's a dropped frame, a momentary dip in delivered frame rate. Frame drops are countable spikes in frame time.

Frame drops come from work spiking above the frame budget, an asset load, a garbage-collection pause, a burst of entities. Bugnet's performance snapshots capture frame-time data from real sessions, so you can see the drops, the specific frames that overran, rather than just an average.

What Stutter Is

Stutter is the perceived experience: the choppiness, hitching, or jerkiness players feel when frame delivery is inconsistent. It's a symptom, the felt result of frames being delivered unevenly, which frame drops cause. A player doesn't see 'a frame took 40ms'; they feel a stutter.

Stutter is fundamentally about consistency, frame pacing, more than average frame rate. A game can average 60 FPS and still stutter badly if frames arrive unevenly. Bugnet's frame-time data lets you see the variance and worst frames behind the stutter, not just the flattering average.

How They Relate

The relationship: frame drops are the measurable cause, and stutter is the felt symptom. You fix stutter by eliminating the frame drops behind it, finding the work that spikes above the frame budget (loads, GC, bursts) and smoothing it so frames are delivered consistently.

Bugnet captures frame-time spikes and what the game was doing when they happened, so you can target the drops causing the stutter. So treat frame drops as the diagnosable events and stutter as the experience they produce: measure and fix the frame drops, and the stutter goes away.

Frame drops are measurable events, individual frames missing the budget; stutter is the felt choppiness they cause. Frame drops are the cause, stutter the symptom. Fix the drops and the stutter goes away.