Seams on tilemaps

Hello everybody, I am trying to load and display simple orthogonal timlemap, the problem is there are seams between same tiles. Picture below illustrates the problem
And here is minimalistic sample
As you can see in sample, those seams desappear and appear again, when you move camera (with wsad). It looks like texture coordinates are moving a bit when you moving camera.
So, I’d like to know, why does this happen and how can I avoid it? One obvious solution is to add 1px border to each tile with the same color as tile, but this looks like hack, and probably won’t fix the problem fundamentally.

This doesn’t work? :wink:

I’d look at the map and tiles, but I’m not creating a Google account to download a file.

1 Like

Unfortunately, no, this makes no effect. I tried setting different filtering and address modes, they don’t seem to effect too.

Huh? Dropbox doesn’t require you to have google account, just press “No thanks” button at the bottom.

1 Like

If sprite vertices are aligned and texture is good, there shan’t be any seams between. I saw similar problems in sample games, will investigate it later.

Thanks. Also, i forgot to mention - if camera zoom is integer, those seams seem to be constant, moving camera does not affect them.

I’ve done some research, and first off, Modanung was right. Changing filtering to nearest really fixed the problem on that map. My apologies, I should’ve tested it before.

But I’ve got similar problem on another map, and here it does not helps. More correct, it helps a bit, those seams appear quite rarely, but they are. This is what it looks like:


Also, I’ve updated dropbox archive with new map.

I tried to place sprites on the scene by hand without TileMap, like this:

Node@ spritesNode = scene_.CreateChild();
Texture2D@ texture = cache.GetResource("Texture2D", "grass9.png");
Sprite2D@ sprite = Sprite2D();
sprite.texture = texture;
sprite.rectangle = IntRect(32, 32, 64, 64);
Sprite2D@ sprite2 = Sprite2D();
sprite2.texture = texture;
sprite2.rectangle = IntRect(128, 32, 160, 64);

for (int r = 0; r< 50; ++r) {
    for (int i = 0; i< 50; ++i) {
        Node@ spriteNode = spritesNode.CreateChild("StaticSprite2D");
        spriteNode.position2D = Vector2(i * 32 * PIXEL_SIZE, r * 32 * PIXEL_SIZE);

        StaticSprite2D@ staticSprite = spriteNode.CreateComponent("StaticSprite2D");
        staticSprite.sprite = (r+i)%6 < 3 ? sprite : sprite2;

and problem stayed, so I believe, vertices are aligned and texture is OK.

Is there anything I should try?

This looks like bad texture. You just have dirty brown tile data.
Are these seams 100% visible?

Can you elaborate, please? What do you mean at bad texture - a broken texture?
And what do you mean at 100% visible, you mean they are not transparent?

I mean that this “seam” isn’t program defect. It’s the defect of sprite data. The leftmost column of pixels of brown sprite is grass.

I mean you always see these seams regardless of camera position, resolution and so on.

The leftmost column of pixels of brown sprite is grass.

No, the brown sprite size is exactly 32x32 pixels, grass belongs to another tile. In Tiled tilemap looks OK.

I mean you always see these seams regardless of camera position, resolution and so on.

No, they appear sometimes, rather infrequently, when you move camera.

That sucks…
If you have fixed and valid sprite texture coords, it must look the same regardless of camera position. Could you scale it e.g. twice? To ensure that all texels are shown as 2x2 pixels.

The line glitches stay visible here after dividing the camera’s ortho size by two, doubling it’s zoom or scaling the map’s node.
To me they do seem part of the neighbouring tiles (in the set) though. Using the -tf 0 option, btw.

Do you see Cannot get rid of lines around StaticSprite2D ?
Perhaps it is the same problem and solution.

I inveestigated your issue.
Sprite2D has tune parameter edgeOffset_ that is used to avoid edge bleeding.
Tile map doesn’t use it in any way, but it definetely should.
Unfortunatelly, Sprite2D is resource and TmxFile2D that creates it is resource too.
So you couldn’t just add new paramter to some component.


  • Hard-code constant in TmxFile2D
  • Put some extra data into TmxFile2D
  • Add an ability to change the constant at the level of StaticSprite2D and so expose it into TileMap2D

Wow! Works perfectly, big thanks!
I’ve googled a bit about texture bleeding, and as I can see, edgeOffset of 0.5 is perfect. So, my temporary workaround is:

void SetTextureEdgeOffsetRecursively(Node@ n) {
    Node@[]@ children = n.GetChildren();
    for (uint i=0; i < children.length; ++i) {
        if (children[i].HasComponent("StaticSprite2D")) {
            StaticSprite2D@ staticSprite = children[i].GetComponent("StaticSprite2D");
            staticSprite.sprite.textureEdgeOffset = 0.5;

I think, I’ll put extra data into TmxFile2D an make a PR

1 Like