Fix: Unity Shader Graph Master Stack Vertex Output Ignored

A wind-sway shader displaces vertex positions to make grass wave. In the Shader Graph preview the grass sways beautifully. Applied to grass meshes in scene view, it sways. In game view, the grass is static.

Active Targets

Graph Settings declares which render pipelines and passes the graph compiles for. If “Universal Forward” isn’t active but you’re running URP, the runtime pass is the fallback (no vertex displacement). Open Graph Settings → Active Targets and ensure your pipeline is listed.

Block Space

Master stack blocks have a Space dropdown. The default for Position is Absolute World in some Shader Graph versions. For vertex displacement you want Object Space:

1. Click the Vertex Position block in the master stack.
2. Inspector → Space → Object.
3. Reconnect your Position output, computed in object space.

Mixing spaces silently produces zero displacement when world-position input maps to zero object-position offset.

Verify the Connection

Look at the master stack node. If the Vertex Position block’s input is gray (unconnected), you broke the wire during editing. Reconnect from your final Position output to the block.

Material Render Queue

If the shader is set to Opaque but the material is assigned to a Transparent renderer queue, some pipelines short-circuit the vertex pass for transparent passes. Check material → Render Queue. Match it to the shader’s SurfaceType setting.

GPU Instancing and _Time

If you use _Time for animation and the material has GPU Instancing enabled, all instances share _Time — identical motion, which can read as “static” for a regular pattern. Add a per-instance hash:

// inside Custom Function or via Object position in object space
float hash = frac(dot(WorldPosition, float3(12.9898, 78.233, 37.719)));
float phase = _Time.y + hash * 6.28;

Each instance picks a different phase, breaking the synchronized look.

Diagnosing

Open Window → Analysis → Frame Debugger. Capture a frame while game view is active. Click your grass renderer entry — the shader name and pass should be the one with vertex displacement. If a fallback shader is bound, the active target setup is wrong.

Verifying

Build and run. Grass should sway identically to the editor preview. If still static in builds, switch the URP Renderer asset to one with the same passes active, and confirm Shader Stripping isn’t culling the variant.

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

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

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

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

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.

“Active Targets, Position Space, and runtime pass selection — all three must agree, or vertex displacement preview-works but ship-fails.”

Build a tiny vertex-shake test scene as a smoke test for new graphs — reveals active-target misconfig instantly.