Fix: Unity Shader Graph Vertex Position Not Updating

Here is how to fix Unity Shader Graph vertex shaders where the math is correct but the mesh visually does not deform. You add a Sample Texture, multiply by the normal, and feed it back somewhere on the master node, but the geometry sits there unmoved. Two pins look similar at the top of the master node: only one of them actually displaces.

The Symptom

Shader Graph vertex math runs (you can see it in graph preview), but the rendered mesh does not deform. Or it deforms in the asset preview but not on the GameObject in scene.

What Causes This

Connected to Position Predisplacement. This pin is the input value, useful for reading the original position. Modifying it does nothing because the vertex stage uses the lower Position pin output.

Frustum culling. Even with displacement working, the renderer culls based on the original mesh bounds. If the original bounds are off-screen but the displaced geometry would be visible, the mesh disappears entirely.

Inactive vertex stage. Some Shader Graph templates lock the vertex stage. Confirm the master node has a Vertex output expanded.

SRP mismatch. A URP-targeted graph used on an HDRP material (or vice versa) compiles a fallback that may strip vertex modification.

The Fix

Step 1: Connect to Position, not Position Predisplacement. In the master output (URP Lit / HDRP Lit), expand Vertex and find Position. Drag your displaced Vector3 into that pin. The Predisplacement pin is for reading the input.

Step 2: Inflate mesh bounds for displaced meshes.

using UnityEngine;

[RequireComponent(typeof(MeshFilter))]
public class InflateBounds : MonoBehaviour
{
    [SerializeField] private float displacementMargin = 2f;

    void Start()
    {
        var mf = GetComponent<MeshFilter>();
        var mesh = mf.mesh;
        var b = mesh.bounds;
        b.Expand(displacementMargin * 2f);
        mesh.bounds = b;
    }
}

Inflated bounds keep the renderer in the frustum even when displaced.

Step 3: Verify SRP target. Open the Shader Graph asset. Top-left, the Master Stack header shows the target (URP/HDRP). Match this to your project’s SRP. Otherwise you are compiling for the wrong pipeline.

Step 4: Test with a known-good displacement.

// Simple test: oscillate Y
Position.y += sin(_Time.y) * 0.5;

If this oscillates the mesh, the pipeline works. Build up to your real displacement from there.

Step 5: Use Custom Function for advanced math. If your displacement needs noise or matrix transforms not in graph nodes, drop a Custom Function node and write HLSL inline. Make sure to declare it for the vertex stage if needed:

// Custom Function: VertexDisplace.hlsl
void VertexDisplace_float(float3 position, float time, out float3 result)
{
    result = position + float3(sin(position.x + time), 0, 0);
}

Shadow Cast Considerations

By default, the shadow caster pass uses the same vertex displacement only if Shader Graph’s Override Vertex Position For Shadow is configured correctly. Without it, your displaced mesh casts shadows from the original silhouette — producing visible shadow-mesh mismatch. See related issues for fixing this.

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 Unity. 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

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

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

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

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Unity-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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, 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

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

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.

“Position pin moves the mesh. Predisplacement pin reads the input. Inflate bounds so culling does not undo your art.”

Related Issues

For Shader Graph time issues, see Shader Graph Time Build. For shadow displacement mismatch, see Vertex Displacement Shadow.

Position pin (lower). Inflate bounds. Match SRP target. The mesh moves.