What causes lightmap memory wasted on hidden surfaces?

The baker allocates lightmap texels to every static surface including faces the player never sees, so undersides, hidden interiors, and tiny props consume atlas space that visible hero surfaces need.

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 Lightmap Memory Wasted on Hidden or Back-Facing Surfaces

Quick answer: Lower lightmap scale on unseen meshes, remove hidden geometry from the bake, and reallocate the freed texels to visible surfaces, then rebake to shrink atlas count.

Lightmap memory is finite, and spending it on faces nobody sees starves the surfaces that matter. Cutting density on hidden geometry frees texels for visible hero surfaces and reduces atlas count.

How to fix it

1. Lower scale on unseen meshes

Reduce Scale In Lightmap (or per-object resolution) on undersides, ceilings, and back faces the camera never frames, so they use minimal texels.

2. Exclude truly hidden geometry

Mark surfaces the player can never see as not contributing GI (or remove them) so the baker stops allocating atlas space to them entirely.

3. Reinvest in visible surfaces

Spend the reclaimed texel budget on floors, walls, and props near the camera, raising their density where the player actually inspects detail.

4. Rebake and check atlas count

Rebake and watch the lightmap count/size; fewer or smaller atlases with the same visible quality confirms the memory was reallocated well.

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.

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.