How to Fix a Two-Sided Material Casting No Shadow on Its Backface When Baked

A flat two-sided object only blocks light from one side unless you tell the baker its backface also casts shadow. Enabling two-sided shadow casting makes it occlude light regardless of view side.

How to fix it

1. Enable two-sided shadow casting

On the static mesh or material, turn on Cast Shadow As Two Sided (Unreal) or two-sided GI/shadows so the backface is treated as a shadow caster in the bake.

2. Use a two-sided material

Ensure the material itself is two-sided so both faces render and occlude; a single-sided material has no backface to cast from.

3. Avoid degenerate single planes for occluders

If the object must reliably block light, consider giving it thickness; a single plane is inherently fragile as a baked occluder.

4. Rebake and check both sides

Re-run the lighting bake and inspect the shadow from both viewing sides to confirm the backface now casts a correct shadow.

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 Unreal Engine 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.