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 Unity Shader Variant Count Bloating Build Size and First Load

Q: What causes Unity shader variant count bloating build size and first load?

Shaders declare many multi_compile keywords whose combinations multiply into thousands of variants, all of which Unity compiles, ships, and warms up.

Quick answer: Strip unused variants via Graphics Settings and shader stripping, prefer shader_feature over multi_compile where possible, and prewarm only the variants you actually use with a ShaderVariantCollection.

Each keyword combination is a separate compiled shader. Liberal multi_compile keywords explode the variant count, inflating the build and causing long hitches the first time each variant is used. Stripping and variant collections bring it under control.

How to fix it

1. Measure the variant count

Check the build log or use the Shader inspector's variant count. Numbers in the tens of thousands usually mean keywords you do not need are being kept.

2. Strip unused keywords

In Project Settings > Graphics enable shader stripping options (lightmap modes, fog, instancing) you do not use, and convert optional keywords from multi_compile to shader_feature so unused ones are dropped.

3. Prewarm only what you use

Record a ShaderVariantCollection from actual gameplay and warm it at load so you ship and compile only the variants the game needs.

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.

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.