Fix: Unity TilemapCollider2D Edges Jagged Catching Players

Players ice-skating across your tilemap floor and randomly stopping mid-stride? The problem is not your movement code. It is the tilemap collider, which is producing one tiny collider per tile and the player’s capsule is catching on the seams between them.

The Symptom

Player walks across a flat row of tiles. Sometimes movement halts. Sometimes a jump fails because the velocity gets eaten by an invisible vertical edge between two tiles. Raycasts down to check “is grounded” flicker between true and false at tile boundaries.

What Causes This

TilemapCollider2D, by default, generates a separate Box-shaped collider for every solid tile. Two adjacent tiles share an edge in screen space but do not share collider geometry. A CapsuleCollider2D (or any non-zero-radius collider) crossing that edge is briefly in contact with both colliders, and Box2D resolves the contact by pushing the player back along the seam normal — which points up out of the tilemap and stops horizontal motion.

The Fix

Step 1: Add the components. On the GameObject that holds the Tilemap and TilemapCollider2D, add:

Tilemap GameObject:
  - Tilemap
  - TilemapRenderer
  - TilemapCollider2D
  - CompositeCollider2D     // added
  - Rigidbody2D             // auto-added by Composite, set Body Type = Static

Step 2: Wire the TilemapCollider2D to the composite. On the TilemapCollider2D component, check Used By Composite. The per-tile shapes are now consumed by the composite and do not produce contacts directly.

Step 3: Geometry Type = Polygons. On the CompositeCollider2D, set Geometry Type to Polygons. This produces one closed polygon per connected region, which is exactly what a floor or wall should be. Outlines is for hollow shapes and is the wrong choice for solid terrain.

Step 4: Regenerate when the tilemap changes. If you place or remove tiles at runtime, call compositeCollider.GenerateGeometry() after the change. The composite does not auto-rebuild on every SetTile.

Verifying It Worked

Enable the Physics 2D gizmos (Window → Analysis → Physics Debugger). The collider should appear as a single thick outline around the entire floor, not a grid of cells. Walk the player across the floor; the snag is gone.

One Gotcha: Slopes

Polygons mode merges into convex pieces. Pure 45° slope tiles work fine; mixing slopes with steps can produce unexpected polygon splits. If your level has complex slope geometry, a custom EdgeCollider2D path drawn over the relevant region is more predictable than relying on the tilemap collider.

Understanding the issue

Tilemaps are dense data structures. A single tile change touches several other systems: rendering, collision, possibly navigation. Bugs at the intersection often look like 'I changed one tile, why did three other things break'.

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

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.

“Composite the tilemap. Polygons geometry. Static rigidbody. The seams disappear and the player walks straight.”

Related Issues

For player getting stuck on slopes, see 2D character on slopes. For ground-check raycast flicker, see isGrounded flicker.

Composite. Polygons. Used By Composite. The player glides.