What is physics interpolation in Godot 4?

Physics interpolation smooths the visual position of objects between fixed physics timesteps, eliminating jitter caused by the mismatch between physics and render frame rates.

How do I fix pixel art camera jitter in Godot?

Use viewport stretch mode, enable Camera2D position smoothing, and snap the camera position to whole pixels using global_position.round() in _physics_process.

Fix: Camera2D Jittering When Following Player in Godot

Quick answer: Camera jitter happens when the camera and player update at different rates. Enable Position Smoothing on Camera2D and Physics Interpolation in project settings to fix it.

Here is how to fix Camera2D jittering following player Godot. Your Camera2D follows the player, but the entire screen shakes or stutters with every frame. Characters jitter, tiles flicker, and the game looks broken even though the logic is correct. Camera jitter in 2D games is almost always a timing mismatch between physics and rendering.

The Symptom

The game view shakes subtly but noticeably as the camera tracks the player. Tiles may appear to vibrate, and pixel art can show sub-pixel rendering artifacts. The jitter is most visible at consistent movement speeds and may disappear when the player stops.

What Causes This

Camera jitter occurs when the camera position updates at a different rate than the player position. If the player moves in _physics_process (fixed timestep) but the camera updates in _process (variable timestep), the camera position on screen lags or leads the player by a fraction of a pixel each frame.

Other causes include:

Position Smoothing disabled — The camera snaps instantly to the player each frame instead of interpolating.
Camera not set as Current — The viewport uses a default camera that does not have smoothing.
Pixel snap conflicts — The rendering snaps to integer pixels but the camera position is fractional.

The Fix

Step 1: Enable Position Smoothing on Camera2D. Select your Camera2D node, and in the inspector enable Position Smoothing > Enabled. Set the speed to around 5-10 for a smooth follow.

# Enable smoothing via code
extends Camera2D

func _ready():
    position_smoothing_enabled = true
    position_smoothing_speed = 8.0

Step 2: Enable Physics Interpolation. In Project Settings, go to Physics > Common and enable Physics Interpolation. This smooths the visual position of physics objects between fixed timesteps.

# project.godot setting:
# [physics]
# common/physics_interpolation = true

Step 3: For pixel art, snap the camera to whole pixels. If you use viewport stretch mode, the camera position should be rounded to avoid sub-pixel jitter.

func _physics_process(delta):
    # Snap camera to pixel grid
    global_position = global_position.round()

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Godot Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

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.

Smoothing on, physics interpolation, pixel snap.