How to Fix Unity Lighting That's Too Dark After Building

A scene that is well-lit in the editor but murky in the build usually shipped without baked lighting, or with lighting that never finished baking. Here is how to get the build to match what you authored.

How to fix it

1. Bake lighting and turn off Auto Generate

In the Lighting window, disable Auto Generate and click Generate Lighting so lightmaps are baked and saved. Auto Generate can leave a build with incomplete or missing lightmap data.

2. Confirm lightmaps are included

Baked lightmaps live next to the scene and must be committed and included in the build. If they are missing, the scene loses its baked global illumination and goes dark.

3. Check ambient and reflection settings

Environment lighting, ambient colour or intensity, and reflection probes contribute much of a scene's brightness. Make sure these are set in the Lighting settings and not left at a near-black default.

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.