Tile Map collisions on wrong tiles (when tile map is too large ?) (DEF-3687)


Hey everyone,

I got some weird collision issues today while I was working on a new Tile Map.

There is one plain blue tile I selected as an obstacle within the collision group (painted as red on the editor) of the associated Tile Source.

Now my character is colliding with every tiles (the ground itself, anything…) unless I move this blue tile outside of the collision group !

It might be something related to Tile Map layers, as no collision works for any tile in the lowest layer…

Do someone knows if there might be an issue with the collision group ?

Thank you!


How strange… are you able to zip the project up and share it here? Hard to diagnose otherwise.


As it is a very big multiplayer project, I just created a new Defold project with a few tiles but the same tilemap layout to reproduce it, but I didn’t had the issue.

I told myself the issue could only happen because of the tilemap… so I recreated the map from scratch on Tiled (I use it and then export maps to .tilemaps with the Tiled Defold plugin), and exported it again.

I no longer have the issue now. Maybe I messed up with tilesources or something, I don’t know…

Sorry for that !

EDIT: This is no longer relevant, I managed to reproduce the issue, please check the answer below.


Hey, I’m back and I managed to reproduce the issue!
It looks like to happen when the Tile Map is very large or the tile is widely used.

You can test it by loading the attached project. Right from starting the game, the character collides with a tile that it should not collide with.
If you just remove the blue tile from the blocker collision on the Tile Source, it’s not colliding anymore.
(note: Moving the character is possible with the arrow keys.)

I had to modify a tutorial project to test it quicky, but it is enough to see the issue (I printed a message on collision):
RPG map sample.zip (3.4 MB)


I’ll take a look and get back to you.


Yup, that does indeed look like a bug. Created DEF-3687 and added it to our sprint planning session today. I can’t promise that this will be included in the current sprint though.


Thanks for the heads up!