Fix: Unity ShadowCaster2D Not Blocking 2D Light

Here is how to fix Unity URP ShadowCaster2D components that fail to block their accompanying 2D Lights. You add a Light 2D for a torch, place ShadowCaster2D on the walls, and the light passes through the walls as if nothing was there. The 2D shadow system has three independent requirements that all must be true at once.

The Symptom

2D Lights illuminate the scene correctly. ShadowCaster2D components are present on walls or characters. But the lights pass through casters with no shadow effect. The Scene view’s gizmo for the caster shape is either invisible or shows a tiny red outline.

What Causes This

No generated shape. ShadowCaster2D needs a polygon to define its silhouette. Unity does not auto-generate one from sprites; you must click Generate Shape in the inspector or assign a shape from a Collider2D.

Shadow Strength is 0. Each Light 2D has a Shadow Strength slider. The default is 0, meaning shadows are not cast at all even when casters are present.

Sorting layers do not match. 2D Lights only affect (and receive shadows from) sprites in their Target Sorting Layers. If the caster is on layer Default but the light targets Foreground, no shadow is cast.

Composite caster setup wrong. If you have many small caster shapes under a parent, you may want a CompositeShadowCaster2D. Without it, each caster works alone, which can produce gaps.

The Fix

Step 1: Generate the caster shape. Select the GameObject with ShadowCaster2D. In the inspector click Generate Shape. The polygon should appear as a yellow outline in the Scene view. If the shape is wrong, edit it in the Sprite Editor or attach a PolygonCollider2D and toggle Use Renderer Silhouette.

Step 2: Raise Shadow Strength on the light. Select the Light 2D, find Shadow Strength in the inspector, and set it between 0.5 and 1.0. Values near 1 produce hard, fully opaque shadows; values below 0.5 are subtle.

Step 3: Add caster sorting layer to the light’s Target Sorting Layers. On the Light 2D inspector, expand Target Sorting Layers and ensure the layer your caster sits on is listed.

Step 4: Add a CompositeShadowCaster2D for grouped casters.

// Hierarchy:
// WallGroup (CompositeShadowCaster2D)
//   Wall1 (ShadowCaster2D)
//   Wall2 (ShadowCaster2D)
//   Wall3 (ShadowCaster2D)

The composite stitches child shapes into a single caster, eliminating gaps where adjacent casters meet.

Step 5: Enable Self Shadows for solid objects. On the caster, check Self Shadows if the object should appear darker on the side facing away from the light. Leave unchecked for thin objects where you want the silhouette without dimming the object itself.

Verifying the Setup

In the Scene view, drag a 2D Light around the caster. You should see the shadow polygon project away from the light source, with darkened cells where the shadow falls. If you see no projection at all, the issue is shape, strength, or layer — check those three first.

// Quick runtime check
using UnityEngine;
using UnityEngine.Rendering.Universal;

public class ValidateShadowSetup : MonoBehaviour
{
    void Start()
    {
        var caster = GetComponent<ShadowCaster2D>();
        if (caster == null || caster.shapePath.Length < 3)
            Debug.LogError("ShadowCaster2D missing valid polygon shape");
    }
}

Performance Considerations

Each caster contributes to per-light shadow geometry. Hundreds of small casters can hurt frame rate on mobile. Use CompositeShadowCaster2D to merge static groups, and disable shadow on lights where artistic intent does not require it.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Shape, strength, layer. Three boxes that must all be checked. The 2D shadow system is unforgiving when any one fails.”

Related Issues

For 2D Lights not lighting at all, see 2D Light Not Affecting Sprites. For URP rendering issues, see URP Shader Not Rendering in Build.

Generate Shape. Strength > 0. Sorting layer in target list. The shadow appears.