What causes a double-sided shader lighting backfaces wrong?

With backface culling off, both sides share the same vertex normal, so the back faces are lit as if they faced the same direction as the front and appear dark or inside-out.

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 a Double-Sided Shader Lighting Backfaces Incorrectly in Unity

Quick answer: Detect the triangle facing with the VFACE semantic (or SV_IsFrontFace) and flip the normal for back faces before lighting.

Turning off culling with Cull Off draws both sides of a surface, but the geometry only carries one normal per vertex. Without flipping the normal on the reverse side, lighting on back faces is wrong. Here is how to fix it.

How to fix it

1. Read the facing in the fragment

Add a facing input to the fragment stage with float facing : VFACE (Built-in) or FRONT_FACE_SEMANTIC in HLSL, where positive means front-facing.

2. Flip the normal for backfaces

Multiply the interpolated normal by the sign of the facing value (normal *= facing > 0 ? 1 : -1) before feeding it into your lighting so the lit side matches the visible side.

3. Keep Cull Off intentional

Confirm Cull Off is actually needed; if you only want the front, Cull Back avoids overdraw and the normal problem entirely.

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.

A crash you can name from its stack trace is a crash you can usually fix in minutes.