Fix Godot Shader Depth Buffer Access Flipped

Depth-based effects — water, fog, soft particles, SSAO — break in strange ways if the depth sample is wrong. The most common failure modes are an upside-down read (your fog appears at the top of the screen instead of the horizon) and a depth value that seems to saturate to 1.0 everywhere. Both stem from mishandling the depth buffer’s coordinate system and its non-linear encoding.

Pick the right UV

In a Godot 4 spatial or canvas_item shader you have two ways to compute the screen UV for a depth sample:

// Option A: the built-in SCREEN_UV
float depth_raw = texture(DEPTH_TEXTURE, SCREEN_UV).r;

// Option B: compute from FRAGCOORD
vec2 uv = FRAGCOORD.xy / VIEWPORT_SIZE;
float depth_raw = texture(DEPTH_TEXTURE, uv).r;

On Vulkan, SCREEN_UV in a post-process pass is sometimes inverted relative to a user’s expectation coming from GLES. If your effect renders correctly on the top half of the screen and not the bottom, flip the Y: uv.y = 1.0 - uv.y. Test on both Vulkan Forward+ and the Compatibility renderer before shipping.

Linearize the depth value

The value you read is not a linear distance. It is the post-perspective-divide Z in [0, 1] for a standard depth-24 buffer, which is heavily biased toward the near plane. Using it directly produces fog that sits entirely in the first meter of the scene. Convert it to view-space Z:

float linearize_depth(float d, mat4 inv_proj) {
    vec4 ndc = vec4(0.0, 0.0, d * 2.0 - 1.0, 1.0);
    vec4 view = inv_proj * ndc;
    return -view.z / view.w;
}

void fragment() {
    float raw = texture(DEPTH_TEXTURE, SCREEN_UV).r;
    float z = linearize_depth(raw, INV_PROJECTION_MATRIX);
}

In Godot 4, depth in the shader is already in [0, 1] (not [-1, 1]), so whether you multiply by two and subtract one depends on which SDK version you are targeting. If your fog is inverted at mid range, flip the sign of z; if it is always zero, drop the NDC remap step.

Do not forget the perspective divide

If you want world-space position from depth, you need to reconstruct the full clip-space vector and divide by w after multiplying by the inverse view-projection matrix. Forgetting the divide is the most common subtle bug — the result looks “almost right” at the center of the screen and diverges toward the edges:

vec4 clip = vec4(SCREEN_UV * 2.0 - 1.0, depth_raw, 1.0);
vec4 world = INV_VIEW_MATRIX * INV_PROJECTION_MATRIX * clip;
vec3 pos = world.xyz / world.w; // divide is essential

Check renderer differences

Godot supports Forward+, Mobile, and Compatibility renderers, and they handle the depth texture slightly differently. Compatibility (GLES3) inverts Y compared to Vulkan, so the flip that fixes one breaks the other. Keep a small uniform toggle:

uniform bool flip_y = false;
// Set from GDScript based on RenderingServer.get_rendering_method()

Canvas_item shaders and depth

Canvas_item shaders on a 2D viewport cannot read 3D depth — the viewport did not write one. If you are trying to implement a 2D fake-depth effect, attach your post-process shader to a SubViewport with Use 3D enabled, or pipe a separate depth render texture through a uniform sampler.

Understanding the issue

Shader bugs manifest visually but trace to invisible state. Triage requires understanding the runtime context as much as the source.

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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

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

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.

“Depth sampling has three independent bugs: wrong UV, wrong linearization, missing perspective divide. Fix them in that order.”

Related Issues

If depth is fine but lighting still looks wrong, see Fix Godot 3D models inside out invisible. For another Godot rendering quirk with viewports, Fix Godot viewport stretch mode black bars unexpected walks through related coordinate-system confusion.

Tip: visualize depth as grayscale first — if the gradient is black near the camera and white far away you have the right orientation.