What causes shader sampler limit errors in Unity?

The shader declares more texture samplers than the target profile allows — big uber-shaders, terrain with many layers, or stacked keywords each adding samplers push past the 16-sampler D3D limit.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix “Shader error: maximum ps_5_0 sampler register index exceeded” and Sampler Limits in Unity

Quick answer: Reduce distinct samplers: share sampler states across textures, use texture arrays or atlases, and split the uber-shader so no variant exceeds the profile's limit.

Shaders compile per-variant, and the variant that exceeds sampler registers fails — sometimes only for one keyword combination you rarely test. Here is how to get back under the limit.

How to fix it

1. Share sampler states

In HLSL, declare textures with SAMPLER(sampler_linear_repeat)-style shared samplers instead of one sampler per texture — the limit is on samplers, not textures.

2. Collapse textures into arrays or atlases

Terrain and layered materials benefit most: a Texture2DArray uses one sampler for all layers and removes per-layer branches.

3. Prune keyword explosions

Multiply your shader_feature combinations: the worst-case variant is what must fit. Strip unused keywords and split rarely co-used features into separate passes or shaders.

4. Compile the worst case in CI

Force-compile all variants (or at least the maximal keyword set) during builds so the failing combination surfaces before a player's material hits it.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.