Fix: Unity Physics.OverlapSphere Misses Rigidbodies

Here is how to fix Unity OverlapSphere returning empty arrays or missing specific Rigidbodies you can clearly see inside the radius. Three things commonly cause this: trigger exclusion, wrong layer mask, and stale physics state from un-synced transforms.

The Symptom

Calling Physics.OverlapSphere(pos, radius) returns fewer Colliders than visible inside the sphere. Toggle the gizmo wireframe; the sphere overlaps obvious targets that the array does not contain.

What Causes This

Triggers excluded. Default behavior depends on project setting Queries Hit Triggers. If false, triggers are not returned. Always pass interaction explicitly.

Layer mask too narrow. The default mask of -1 (Everything) sometimes gets overridden by a script. A mask of 0 returns nothing.

Transform not synced. If you moved a collider this frame and Auto Sync Transforms is off, the broadphase has stale data.

The Fix

Step 1: Pass interaction and mask explicitly.

int mask = LayerMask.GetMask("Enemies", "Pickups");
Collider[] hits = Physics.OverlapSphere(transform.position, 5f, mask, QueryTriggerInteraction.Collide);
Debug.Log($"Hit {hits.Length} colliders");

Step 2: Sync transforms before the query.

// If you teleported or moved Rigidbodies this frame:
Physics.SyncTransforms();
Collider[] hits = Physics.OverlapSphere(pos, radius);

Step 3: Use the non-allocating variant for hot paths.

private static Collider[] buffer = new Collider[32];

int count = Physics.OverlapSphereNonAlloc(pos, radius, buffer, mask, QueryTriggerInteraction.Collide);
for (int i = 0; i < count; i++)
{
    // process buffer[i]
}

Avoids per-frame allocation that Unity GC charges for the array.

Step 4: Verify with Debug.DrawWireSphere.

void OnDrawGizmos()
{
    Gizmos.color = Color.red;
    Gizmos.DrawWireSphere(transform.position, queryRadius);
}

Visual confirmation lets you see whether the sphere actually overlaps what you think it does.

Step 5: For 2D, use Physics2D.OverlapCircle. 3D OverlapSphere does not see 2D colliders. Mixing pipelines requires querying each separately.

Performance Note

OverlapSphere is fast but allocates an array per call. NonAlloc avoids GC pressure. For per-frame queries on many actors, NonAlloc is mandatory; otherwise allocations dominate.

Understanding the issue

Physics simulations rely on deterministic, frame-by-frame integration of forces and constraints. When a single step misbehaves, the consequences cascade through subsequent frames - velocities accumulate error, contacts re-solve, and what should have been a clean interaction becomes visible jitter or unbounded motion.

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

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

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

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

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.

“Layer mask + trigger interaction + synced transforms. Three knobs that fix most empty-result OverlapSpheres.”

Related Issues

For physics overlap returning stale results, see OverlapBox Stale Results. For trigger detection, see Trigger Collider Not Detecting.

Mask, interaction, sync, NonAlloc. Four habits, every overlap query.