The problem you're having is that the ball is not hitting the collision shape in the way you want it to? Did you carefully assign specific shapes to each tile?

    Erich_L the problem is the balls dont collide you would expect they change the direction without a reason. In the reddit post you can see in the video what i mean.

      Ah I had to watch the video a few more times. It's always nice if you describe the problem with text too. I have never seen anything like this but have only done similar work in 3.5. In my work the collisions work as expected.
      All I can say for sure is you shouldn't need to use continuous detection for this.

        Erich_L Yea makes sense will keep it in mind.

        The only workaround for now is to do this merge yourself with scripts. E.g. disable the TileMap collision and parse the polygons from the used cells and TileSet then merge them together with the Geometry2D class and set them on a StaticBody2D / NavigationRegion2D node.

        Do you maybe know a way how to achieve this ?

            Galla I would definitely avoid doing that. Instead I'd opt to figure out to use the tool as it's intended and accept the possibility that b/c we're early in 4.0 there might be unresolved issues and missing functionality.