Why is my terrain grass missing on Android/iOS but visible in editor?

The default Grass shader is desktop-only. Mobile builds need a mobile-compatible material on the detail prototype, the prototype set to GPU Instancing, and Detail Distance / Density tuned to fit mobile memory.

What's the cheapest grass for mobile?

Texture-based detail prototypes with Billboard mode and Render Mode = Grass on a single-quad mesh. Avoid Detail Mesh prototypes (full meshes) on mobile unless density is very low. URP's Lit Particle / Mobile Particle shaders work as a base.

Should I use Terrain Detail or scattered prefabs?

For mobile, scattered prefabs with GPU instancing often perform better than the Terrain Detail system because they let you batch and cull at the prefab level. The Terrain Detail system is convenient but its mobile path has more constraints.

Fix: Unity Terrain Detail Painting Not Rendering on Mobile

Quick answer: Replace the default Grass shader with a mobile-friendly one on each Detail Prototype, enable GPU Instancing on the prototype, lower Detail Distance to ~30m and Detail Density to 0.5 or less. Editor uses desktop fallbacks; mobile builds need explicit setup.

Editor view: lush grass everywhere. Build to Android: bare dirt. The Terrain Detail system has a mobile-specific configuration path that is easy to skip.

The Symptom

Terrain Detail brushes visible in editor (and even the Game window when targeting Standalone) but missing on Android, iOS, or in URP mobile builds. Trees may render fine; only Detail Meshes / Detail Textures vanish.

What Causes This

Two things differ between editor and mobile:

The default Grass shader doesn’t compile on GLES 3 or has variants stripped during build.
Without GPU Instancing on the prototype, instancing falls back to per-instance draw calls, which are too expensive and the system silently culls.

The Fix

Step 1: Mobile-friendly material per prototype. Open the Terrain → Paint Details. Edit the Detail Prototype. For Detail Texture (single-quad billboard) replace the default Material with a custom one based on URP’s Universal Render Pipeline / Particles / Lit Unlit or a Shader Graph that respects the Terrain Engine path.

For Detail Mesh (a full mesh per blade), the Material on the mesh must have Enable GPU Instancing checked.

Step 2: Tune density and distance.

Terrain Settings → Mesh Resolution / Heightmap:
  Detail Distance:           30     // 30m, default 80
  Detail Density:            0.5
  Detail Resolution Per Patch: 8

Detail Prototype:
  Render Mode:               Grass      // for billboards
  Use GPU Instancing:        true
  Min/Max Width/Height:      modest range
  Healthy Color:             desaturated green

Step 3: Strip-safe shader variants. Edit Project Settings → Graphics → Always-Included Shaders. Add the grass material’s shader explicitly. This prevents the build process from stripping it as “not directly referenced.”

Verifying on Device

Build to a development build with Autoconnect Profiler. In Frame Debugger, look for Draw Mesh Instanced calls naming your detail prototype. If absent, the prototype isn’t rendering at all (material/shader issue). If present but visually missing, density or culling is too aggressive.

Alternatives Worth Considering

For mobile, consider replacing Terrain Details entirely with:

Scattered prefabs placed by an editor tool, instanced via Graphics.DrawMeshInstanced.
Static batched meshes with vertex-color wind animation in the shader.
Impostor cards rather than meshes for distant grass.

Each gives more control over draw call counts and shader paths than the Terrain Detail system on mobile.

Understanding the issue

Render pipelines have ordering: which pass runs when, what state is bound, which targets are written. Bugs at this layer are often invisible in code review and only manifest at runtime.

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

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

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

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

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

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.

“Mobile shader. GPU instancing. Lower density and distance. Always-included shaders. Grass appears.”

Related Issues

For shader stripping, see shader stripping. For mobile draw call counts, see mobile draw calls.

Mobile shader. Instancing. Trim density. Grass blooms on device.