How to Fix Two-Sided Foliage Self-Shadowing Too Dark

Dark two-sided foliage is back faces lit with front-facing normals plus aggressive self-shadow. Two-sided lighting and softened shadow bias restore even, translucent-looking leaves.

How to fix it

1. Enable two-sided lighting

Turn on two-sided lighting (or a foliage/two-sided shading model) so the renderer flips the normal for back faces and lights both sides of each leaf correctly.

2. Add subsurface or translucency

Use a translucency/subsurface term so light passes through thin leaves, which removes the flat black look on faces turned away from the sun.

3. Soften self-shadow bias

Reduce shadow and contact-shadow bias on foliage so dense leaf clusters do not self-shadow into solid black where geometry overlaps.

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