What causes a shader that works in the editor but breaks on a device?

Mobile GPUs use lower default precision, different texture formats, and a smaller feature set than your desktop editor, so a shader that looks right on a PC produces artifacts or black output on the phone.

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 Debug a Shader That Renders Correctly in the Editor but Breaks on Device

Quick answer: Force the precision the device uses, check texture format and feature-level support, capture a frame on the actual device to inspect the real inputs, and test on the target hardware rather than the editor.

A shader that is perfect in the editor and wrong on a phone is rarely a code typo; it is a hardware difference. Mobile GPUs default to lower precision and support fewer features, so the editor was quietly forgiving something the device will not.

How to debug it

1. Match the device precision

Mobile defaults to half/mediump where the editor uses full precision. Force low precision in the editor (or explicitly declare precision) so the banding and overflow artifacts reproduce where you can iterate.

2. Check formats and feature support

Verify the textures and render targets use formats the device supports, and that any feature you use (derivatives, certain samplers, MRT) exists at the device's GL ES/Metal feature level. Unsupported features silently fail or fall back.

3. Capture a frame on the device

Use a device frame capture (Xcode GPU capture, Android GPU Inspector, or RenderDoc where supported) to inspect the actual bound textures and shader inputs on the real GPU, not a desktop approximation.

4. Test on the target hardware

Iterate on the device or an equivalent, not the editor. The only reliable confirmation that a mobile shader is correct is seeing it render correctly on the GPU it will ship to.

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