What causes baked foliage going black or flat from self-shadowing?

Dense foliage cards overlap heavily and occlude each other in the GI bake, so layered leaves accumulate self-shadow and the canopy bakes to near-black with no internal light.

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 Baked Foliage Going Black or Flat from Self-Shadowing

Quick answer: Reduce foliage GI contribution or exclude it from the bake, enable two-sided/translucent shadowing, add subsurface or a fill term, and lean on realtime lighting for foliage.

Stacked foliage cards shade each other in a bake until the interior goes black. Foliage usually wants light to pass through it, so excluding it from heavy baking or enabling translucent shadows keeps it readable.

How to fix it

1. Exclude dense foliage from baking

Mark thick foliage as not contributing to GI (or as dynamic) so it is lit by realtime light and probes instead of accumulating self-shadow in the lightmap.

2. Enable two-sided/translucent shadows

Set the foliage material to two-sided foliage shading with translucency so light passes through leaves rather than each card fully occluding the one behind it.

3. Add a subsurface or fill term

Give leaves subsurface/translucency or a small ambient fill so the canopy interior is not pure black where direct light cannot reach.

4. Bake at higher samples if needed

If you must bake foliage, raise indirect samples and denoise so the overlapping cards resolve to soft shade rather than crushed black, then verify in-engine.

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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.