sorry for triple posting, but I actually found the solution. When right clicking on a Tileset (not Tilemap) an option called “Condition Tile Sheet Texture” appears, which apparently creates some sort of buffer around tiles, which completely eliminates the problem! 
Hope this helps someone in the future.
3 Likes
version 4.15
The problem still exists
Does anyone have any ideas? In motion the same problems…
- If use AA, problems are solved in
part. - If use Condition Tile Sheet
Texture, this is resolved exist
problem. But this is not convenient
for debugging, you lose the ability
to re-export the texture.
Help pls 
I think, I found a solution, you just need to manually add indentation in the source texture (2px/2px + 2px/2px padding).
See this - Unreal Engine 4: TileSets and TileMaps! - Saucy.se part TileMap tearing.
In this case, you can save the ability to re-export the textures
for example:
and that is WORK!!! for if you don’t have use tile map… or for fast re-export…
36x36 = source dimension, and rendering size 32x32(padding = 4) and other settings…
The tile flickering issue has two solutions.
If you can re-author the spritesheet you’re using for the Tile Map, add a pixel extrusion (meaning, add a single extra pixel along the edges of the sprite, so that the sprite has 1 extra pixel repeated along the entire edge). Adding the extra pixel covers up the tearing in between tiles.
If you can’t re-author the spritesheet (i.e., you’ve already made a great level and can’t change where sprites are located on the sheet). Then you can Condition the Tile Map’s spritesheet by right-clicking on the Tile Set for the Tile Map and selecting “Condition Tile Sheet Texture”, which makes a new Texture using the original spritesheet, but adding the extruded pixels for you. (Source for this fix: http://saucy.se/blog/gamedev/curse-of-undeath/unreal-engine-4-tilesets-and-tilemaps/ Thanks to [aleksvander for posting the link in this thread).
After using the Condition Tile Sheet Texture method, my game didn’t have any tearing while running in the Editor or after running packaged on Android.
1 Like
Confirmed that adding an extra 1 pixel border around each of the sprites in question resolves the issue. I had attempted a bunch of camera things but flickering was still occurring. I am not using a tilemap but am manually constructing terrain pieces from sprites.
In 4.22 this issue has once again returned, however this time showing up on sprite sheets that HAVE the pixel padding.
In 4.21 did not observe this problem. But in 4.21 bad speed loading new sprite tiles at the edges of the camera.
If anyone still challenging with this problem; just add edges in photoshop around the sprites, and the problem will gone… Sprite bound should remain same in the engine, but just add for example 2 pixel stroke in photoshop, than overwrite the file…
helped me a lot! thanks.