How do Physics2D effectors work?

An effector applies forces to rigidbodies whose colliders overlap a paired trigger collider on the same GameObject. The trigger must have isTrigger = true and usedByEffector = true, the effector component must be present, and the affected rigidbody must be Dynamic (not Kinematic).

What's the usedByEffector flag?

A bool on Collider2D. When true, the collider becomes the effector’s area-of-effect. Default is false — effector won’t work even with a collider present. Easy to miss the first time you set up an effector.

Why does BuoyancyEffector2D push my body but not buoy it?

The body is Kinematic or has gravityScale = 0. Buoyancy works by countering gravity; if gravity isn’t pulling the body down, buoyancy can’t lift it. Set Body Type = Dynamic and Gravity Scale > 0.

Fix: Unity Physics2D Effector Area Overlap Missed

Quick answer: Check Used By Effector on the trigger collider (default is off!). The effector and collider must be on the same GameObject. The affected Rigidbody2D must be Dynamic.

You add a BuoyancyEffector2D to a water area to make rigidbodies float. The collider is a Box2D, set to Is Trigger. Run play; objects fall straight through. The effector is configured; the water is set up; nothing happens.

Effector Setup Checklist

For a Physics2D effector to work, four things must be true:

The effector component (BuoyancyEffector2D, PointEffector2D, etc.) is on the GameObject.
A Collider2D on the same GameObject has Is Trigger = true.
That collider has Used By Effector = true.
The body being affected has Rigidbody2D.bodyType = Dynamic.

Miss any one and the effector silently no-ops. The most commonly missed: step 3.

The Fix

Select the water GameObject. In the Inspector:

BoxCollider2D
  Is Trigger: true
  Used By Effector: true   // THIS
BuoyancyEffector2D
  Density: 2
  Surface Level: 0
  Linear Drag: 1
  Angular Drag: 1

Save. The collider area now acts as the effector’s zone of influence.

Dynamic Body Type

For buoyancy, the affected body must respond to gravity (which the effector counters). Check:

Rigidbody2D
  Body Type: Dynamic
  Gravity Scale: 1.0

Kinematic and Static bodies don’t respond to forces, so effectors do nothing to them. Switch to Dynamic if you intended physics interaction.

Effector Layers

Each effector has a Collider Mask field. By default it’s Everything. If your project sets it to a specific layer, only colliders on that layer get affected. Check the affected body’s layer is in the mask.

Diagnosing

Enable physics gizmos. The effector’s area should be highlighted with its visualization (e.g., wavy lines for buoyancy, arrow for point). Drop a rigidbody into the area — it should react. If gizmos don’t show, the collider isn’t marked as “used by effector”.

Verifying

Drop a Dynamic Rigidbody2D into the water. It should bob to the surface and float. If it falls through, recheck the four-step list. If it bobs but oscillates wildly, increase Linear Drag for damping.

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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

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

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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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

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.

“Used By Effector is the property everyone forgets. Check it first when any effector misbehaves.”

Build a tiny EffectorAuditor editor script that lists every effector + collider pair and flags missing Used By Effector flags.