Fix: Godot 4 Physics Interpolation Jitter on Camera Follow

Player runs across the screen. On a 60 Hz display: smooth. On a 144 Hz display: stuttering. The character is stepping at 60 Hz physics; the camera renders at 144. Interpolation is the bridge between the two rates.

The Symptom

On a high-refresh display, the player’s sprite shows obvious stutter even though FPS is high. Camera follows perfectly — both move together but both look jittery. On a 60 Hz display the issue disappears.

What Causes This

By default, Godot runs physics at 60 Hz. CharacterBody/RigidBody update positions on the physics tick. Render frames between ticks (e.g. 1.4 frames per tick at 84 Hz vs 60 Hz physics) show the character at the same position twice, then jump. Without interpolation, the camera following the character also locks to the 60 Hz cadence.

The Fix

Step 1: Enable physics interpolation. Project Settings → Physics → Common → Physics Interpolation. On. Restart the project.

This makes Godot interpolate Node2D/Node3D positions of physics-driven nodes between physics ticks for rendering.

Step 2: Camera in _process, not _physics_process.

extends Camera2D

@export var target: Node2D
@export var follow_speed := 8.0

func _process(delta: float) -> void:
    if target == null: return
    var target_pos = target.global_position
    global_position = global_position.lerp(target_pos, follow_speed * delta)

Reading target.global_position in _process with interpolation enabled returns the interpolated value, sampled at the current render frame’s temporal position. Smooth at any refresh rate.

Step 3: Disable interpolation per-node where unwanted. For nodes that should snap (a teleporting boss, a respawning player), call node.reset_physics_interpolation() right after the snap to skip the interpolation for one frame.

RigidBody Caveat

RigidBody2D/3D respect physics interpolation automatically. CharacterBody also does. Custom Node2D nodes you move manually in _physics_process need explicit interpolation control via the physics_interpolation_mode property.

Determinism

Physics interpolation is purely visual; the simulation is unchanged. Networked games still tick deterministically at the configured rate; only the rendered transform interpolates.

Verifying

Run on a high-refresh monitor (or set V-Sync off and watch FPS > 60). Move the player. The sprite should glide; the camera should glide. Without interpolation: visible stair-stepping.

Or temporarily set physics/common/physics_ticks_per_second = 30. With interpolation, the game still looks smooth at 144 Hz. Without, it looks like stop-motion.

Understanding the issue

Physics simulations rely on deterministic, frame-by-frame integration of forces and constraints. When a single step misbehaves, the consequences cascade through subsequent frames - velocities accumulate error, contacts re-solve, and what should have been a clean interaction becomes visible jitter or unbounded motion.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Godot. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Godot-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

Within Godot, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Interpolation on. Camera in _process. Read interpolated transforms. The high-refresh stutter goes away.”

Related Issues

For Godot frame pacing, see frame pacing. For camera shake jitter, see camera shake.

Interpolation. _process for camera. Smooth at 144Hz.