2

Im using a tiled tmx map, and I created a class that adds bodies to each tile within a certain layer. This has been working great so far except for when a character or an enemy moves around on the screen, its body gets stuck on an edge between two tiles.

This seems to happen "sometimes" and in certain spots. Jumping makes u unstuck but its annoying when it happens, and i tried increasing the position iterations, but the problem keeps reoccurring.

Heres what my game looks like: https://i.stack.imgur.com/f5Igm.png I didnt render the tiles so that its easier to see what the tile's body looks like

user3712476
  • 118
  • 1
  • 11
  • For future questions, you may get a better response on [GameDev.SE](http://gamedev.stackexchange.com). – ashes999 Sep 17 '14 at 15:59
  • 1
    This has been reported many times over the life of Box2D. Your best solution is to use edge shapes instead of tiles. http://www.iforce2d.net/b2dtut/ghost-vertices – Colonel Thirty Two Sep 17 '14 at 16:30
  • Ahh i see that article was very informative. Im going to try to use edge shapes, if not im probably going to try to implement a way to detect if tiles next to each other so i can make one bigger body for that peice instead. This should totally be an answer instead of a comment – user3712476 Sep 17 '14 at 19:40

1 Answers1

0

What happens is that an upper dynamic body's "skin" can get embedded into the shapes below it. If the upper body is then moved across the lower shapes and encounters a corner of one of those shapes, then an impulse is generated by the physics engine that's in opposition to the direction of travel.

Boom! Upper body gets stuck.

Here's a zoomed in image showing this for an upper rectangle moving to the right:

enter image description here

The blue dots and lines extending from them are where the Box2D manifold calculation code has determined impulses need to be applied. Note the blue dots and lines that are on the right side of the reddish/brown rectangle. Those are opposing impulses.

A solution, as Colonel Thirty Two suggested in the comments, is to use the "ghost-vertices" mechanism in edge shapes for the lower shapes (or just use a chain shape that effectively calculates the edges for you).

As background, I have my own fork of Box2D that I've been developing and I just pushed out an alternative solution for this very problem that doesn't require the lower shapes to be edge (or chain) shapes. I've also done a write-up of this alternative.

Louis Langholtz
  • 2,913
  • 3
  • 17
  • 40