Tile Map Tilemap has tearing between tiles, even with pixel snap

Hey, I have a problem where my tiles have lines between them when moving around. I have tried pixel snap materials which just changes where and how frequently these occur.

Anyone have a solution to this issue?

 

You can round the camera's position to values that are not problematic, so relative offset of each pixel to camera is always the same. This will depend on your pixels per meter, so depending on that you need to find the rounding point at which the inaccuracies don't appear.

This is what I'm doing.

 

Makes sense. I'll give that a go then! thanks.

 

So I've tried all of these suggestions, but I still have this problem.

Even if my camera is at an integer value (no decimal place), My PPU is 16, and my ortho size is 8, so that should be a clean multiple at 1080p. In fact, no matter what I change the ortho size to the tearing stays. I'm at a loss!

*Edit* I hadn't done the sprite atlas thing actually, I am not familiar with that. I tried just making a sprite atlas and putting the spritesheet in there and it actually seems to have improved the situation somehow? I'm not certain but it seems that way. Why does putting this in an atlas help?

 

This is what fixed it for me as well. It's due to the fact that packing adds "padding" around each tile.

Spritesheets are traditionally densely packed (i.e. no padding between sprites), but this doesn't translate well to a 3D engine since it works by sampling textures coordinates (0-1), not pixels. The tearing comes from oversampling a tile by a tiny bit (i.e. 0.0001), and into an adjacent tile's content. Padding repeats the border pixels of a tile to ensure the effects of oversampling can't be seen, even though it's still happening.

It's the same reason we add padding around UV islands in textures.

 

Dear Johaness, what should be done to solve the problem if I want non pixel-perfect, for example need to zoom in and out!

 

I fixed this problem by unchecking the 'Allow MSAA' box in the camera component.

 

This is a different problem.

Anti aliasing gives you static lines that reposition when you move or zoom out. They appear as solid, black verticals and horizontals.

This camera problem is flickering lines when the camera moves.They appear to all be vertical in my experience.

 

Any luck solving this issue? I'm seeing the same thing. I got this asset from the store https://assetstore.unity.com/packages/2d/environments/2d-hand-painted-town-tileset-67346

It includes a sample scene that doesn't use the tilemap system, it just has hundreds of sprites manually laid out. I added a test character and follow cam and can move around and it has no issues. I made my own scene with a tilemap and a test map and I get vertical black lines quite frequently. I even copied my tilemap into their test scene so I know it's using same camera etc all the same. Looking at the frame debugger, their multiple sprites cause hundreds of drawcalls but no tearing. The tilemap only has a couple dozen but tears all over the place, it doesn't make any sense to me.

 

@furroy I'm the creator of that asset. What I did was just using this guide: https://blogs.unity3d.com/2015/06/19/pixel-perfect-2d/
So it should just be a matter of setting up the camera, make sure the sprite asset itself has correct import settings. Another thing (although maybe a stupid suggestion), make sure the game window when you run the game has correct dimensions and is 1x scale. I noticed it started tearing if you didn't have full resolution size in the game window.

The asset was created before the Unity 2D tools, but I don't think that should make a difference.
I hope it was of some help.

 

Maybe I wasn't clear in my post. I have two towns in the same scene in the same project side by side. Your original town renders flawless and the equivalent one I made in a tilemap gets vertical tears all over. They are using same anti-aliasing settings (none), same orthographic camera etc, so I don't see it is an issue with those things, I think there is something inherently goobered with the tilemap implementation.

Your assets are amazing! I'm making a thing to procedurally generate maps from them and having a lot of fun!

Here is tear even visible in the editor:

 

@furroy Ah ok, strange for sure. My latest tileset "Mines" I did the example level in the Unity tileset tool and it worked perfectly. So maybe there is something is up with the scene itself? Did it work better if you started a new from scratch?

 

i had some more time to poke at this. my camera is locked to follow the x&y of my character. the tearing is only ever vertical, never horizontal. the funny thing is, it reproduces only when my character (and hence camera) is at an exact integer X value. So it looks fine at 29.9 and 30.1, but camera at 30 shows tearing. This happens for every integer value of X.

 

I just updated to current unity version, but it looks like the problem i had on my project using mesh plane.
IIRC the fix was to disable anti aliasing Edit -> Project Settings -> Quality

But now that i'm using the current version it seems like it no longer does this issue with anti aliasing on.

My question to Unity is;
Does the Tilemap system uses quads/mesh to render texture?

 

Is current unity version is 2017.4.0f1 ?
I'm having this issue with tilemap / tiles too. Disabling anti aliasing helped a lot, but black lines still appear sometimes when moving.

 

@vovx
Make sure that the elements' size in your sprite atlas matches the grid size and/or maybe try Filter Mode: Point (no filter).

I was using unity 2016. I'm new to unity tilemap but the lack of information on what system it uses to render is bothering me, since I also want to make an in-game editor and want to know at least the basics of what's going on behind the scene.
So I don't have much experience with it and therefor did not encounter that problem using that system.

(current version is 2017.3.1f1)

 

I've done all that and like I said, another map made from same sprites manually laid out in the same scene doesn't have. If it was a projects settings or camera setting, both would have the issue. I had to upgrade to the 2018 beta because tilemaps don't even show up on iphone in 2017.x and still same issue

 

Turns out it does happen on horizontal as well, finally saw an instance of it.

 

is your game window scale 1?
sometimes when i choose a resolution larger that what fit (default behaviour) it scales it down and see lines
but change to small res like 800x600 that filts easy with no scale and problem solved?

 

yes scale is 1. thankfully it only does it while developing. once deployed on my iphone i never see it.

 

also I messed around with things a bit more. it doesn't seem to happen with tilemaps made using the built in tile palette. it's only doing it on my maps i procedurally generated w/ Tilemap.SetTile()

 

Hello,
Assigning a packing tag to my tile-set and let unity pack my tiles solved my problem.
Best regards,

 

Hello,

I experienced the same/a similar problem.

Setting:
Camera.projection == orthograhic
Camera.Size = 8


Observations:
- SpriteAtlases did not help me.
- Disable Camera's "Allow MSAA' reduces the problem, but it is still very visible
- Every time the problem occurs, the camera's position is (camera.position.x % 0.1f) == 0
- The problem does not occur on every one of these position (problem occurs on x = 5.5 and 5.3 but not on 5.4)

Solutions:
1. Force an offset on problematic positions: Add 0.01f to position.x, when the upper mentioned condition is met. (Only add when condition is true, otherwise x = 5.49 --> 5.5 --> Bug)
2. Change Size of Camera: When I change Camera.Size from 8 to 8.01, I dont experience any problems. If I set size to 7.01 I experience problems, but not on 7.

However, when I enable camera's "Allow MSAA' the game is screwed totally.

 

It seems I had same issue. I've solved it by disabling "allow HDR" on the camera
I'm on Unity 2017.4.17f1

 

Creating an atlas with padding of 8 seems to solve the issue for me. However, there's a related issue where the background sometimes gets shown between tiles.
One thing that seems to solve that for me is setting a tile gap of -0.001 (1/10th of a pixel). This does make the grid size slightly smaller, so you might want to compensate this by scaling the transform (the amount depends on your grid size... should be gridSize / (gridSize -0.001)).

EDIT : the colliders don't seem to be put in the correct spots when scaling the grid's transform, so this solution might not be ideal.