Fix: Unity Physics.Overlap Returning Stale Results

Here is how to fix Unity Physics.Overlap returning stale results. You teleport an enemy to a new position, then immediately run Physics.OverlapSphere to check what is nearby — and it returns colliders that were near the enemy’s old position, not the new one. Or you move a trigger zone and the overlap query thinks nothing is inside it yet. The physics world is out of sync with your transforms.

The Symptom

Physics.OverlapSphere, Physics.OverlapBox, Physics.OverlapCapsule, and their non-allocating variants (OverlapSphereNonAlloc, etc.) return colliders based on positions from the previous physics step. Objects you just moved appear to be in their old locations. Raycasts exhibit the same problem — they hit colliders at their previous positions.

This is most noticeable when you move objects in Update and then immediately query. In FixedUpdate the problem is less apparent because physics has just simulated.

What Causes This

The physics world is separate from Transform state. PhysX (Unity’s physics engine) maintains its own copy of collider positions and orientations. When you set transform.position, only the Transform component updates immediately. The physics world updates during the next FixedUpdate simulation step or when explicitly synced.

Physics.autoSyncTransforms is false. Since Unity 2018.3, autoSyncTransforms defaults to false in new projects for performance. The old behavior (automatically syncing before every query) was expensive because it forced a full broadphase rebuild on every overlap check. With it disabled, you gain performance but must manage sync timing yourself.

Querying in Update after moving in Update. If you move a collider in Update frame N and query in the same Update frame N, the physics world still has frame N-1 positions (or whatever the last FixedUpdate left).

The Fix

Step 1: Call Physics.SyncTransforms() when needed. After moving objects outside of physics simulation and before querying, sync the physics world explicitly.

// Teleport then immediately query
enemy.transform.position = newPosition;

// Sync physics world to match new Transform positions
Physics.SyncTransforms();

// Now overlap queries see the updated position
Collider[] nearby = Physics.OverlapSphere(newPosition, 5f);
Debug.Log("Nearby count: " + nearby.Length);

Step 2: Prefer querying in FixedUpdate. If your game logic allows it, perform overlap queries in FixedUpdate rather than Update. The physics simulation runs at the start of FixedUpdate, so collider positions are current by the time your code executes.

void FixedUpdate()
{
    // Physics just simulated — collider positions are current
    int count = Physics.OverlapSphereNonAlloc(
        transform.position, detectionRadius, results, enemyMask);

    for (int i = 0; i < count; i++)
    {
        ProcessTarget(results[i]);
    }
}

Step 3: Use Rigidbody.MovePosition for physics-driven movement. If you move objects with Rigidbody.MovePosition instead of setting transform.position directly, the physics engine integrates the movement during simulation and collider positions stay consistent with queries in the same FixedUpdate.

// Kinematic Rigidbody movement — physics stays in sync
private Rigidbody rb;

void FixedUpdate()
{
    rb.MovePosition(targetPosition);
    // Overlap queries after this in the same FixedUpdate see the new position
}

Step 4: Do not enable autoSyncTransforms globally. While setting Physics.autoSyncTransforms = true in Project Settings > Physics fixes the problem, it re-introduces the performance cost for every query in your entire project. Use targeted SyncTransforms() calls instead.

Performance Considerations

Physics.SyncTransforms() iterates over every transform that has moved since the last sync and updates the physics broadphase. If you have thousands of moving objects, calling it multiple times per frame is expensive. Batch your queries: move everything, sync once, then run all your overlap checks.

// Batch pattern: move all, sync once, query all
foreach (var unit in units)
    unit.transform.position = unit.targetPos;

Physics.SyncTransforms(); // One sync for all moves

foreach (var unit in units)
    unit.RunOverlapQuery();

Understanding the issue

Game physics is a contract between authoring (the body, mass, collision shapes you set) and the solver (how the engine integrates them per tick). Bugs at this boundary usually surface as 'the values look right but the behavior is wrong' - a sign that one side of the contract isn't honoring the other.

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

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

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

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

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

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.

“The physics world is a parallel universe. It only learns about Transform changes when you tell it to sync — or when FixedUpdate runs.”

2D Physics Too

The same issue applies to Physics2D.OverlapCircle and related 2D queries. Use Physics2D.SyncTransforms() for 2D physics. The setting is separate: Physics2D.autoSyncTransforms in Project Settings > Physics 2D.

SyncTransforms is not expensive for a few objects. It is expensive when you have thousands. Move, sync once, then query — do not sync between every move.