How to Fix an Area Light Looking Hard or Noisy When Baked

Area lights only look soft when they have real size and enough samples. A tiny rect light baked at low quality gives hard, noisy shadows. Enlarging it and raising samples produces the soft look you expect.

How to fix it

1. Give the light real dimensions

Set the area light's width and height to its physical size. A near-zero-size area light behaves like a point light and casts hard shadows with no penumbra.

2. Set the light to Baked or Mixed

Area lights contribute their soft area shadows only when baked. A Realtime area light is approximated and loses the soft falloff, so switch its mode to Baked or Mixed.

3. Raise per-light bake samples

Increase the bake sample count (Unity indirect samples, Lightmass quality, Godot bake quality) so the penumbra resolves smoothly instead of showing grain.

4. Add denoising and rebake

Enable the lightmapper's denoiser and rebake. The denoiser cleans residual noise in the soft shadow region without you pushing samples impractically high.

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.