How to Fix a Light Cookie or Gobo Not Projecting Its Pattern in Unity

A cookie or gobo breaks a light into a pattern like window blinds or leaves. If the spotlight is just a plain cone, the cookie is not importing or the pipeline is ignoring it. Fixing the import and pipeline flag projects the pattern.

How to fix it

1. Import the cookie correctly

Set the texture's import type so it is usable as a cookie, use Clamp wrap mode (so it does not tile across the cone), and keep an alpha channel that defines the cutout pattern.

2. Assign it to the light's cookie slot

On the Light component, drag the texture into the Cookie field. For a spotlight the cookie maps onto the cone; for a directional light it projects across the world.

3. Enable cookies in the pipeline asset

In the URP/HDRP Renderer/Asset settings, ensure Light Cookies are enabled and the cookie atlas resolution is high enough; if disabled, the engine silently drops the cookie.

4. Check cookie size and falloff

Adjust the cookie's scale/tiling so the pattern fits the cone. An oversized cookie can push the visible pattern outside the lit area.

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.