[SOLVED] Texture atlas has visible seams but it should not

[kruze]

Hello there fellow users!

I need your help and judgement with the following issue:

I have a 128x128 pixel texture. I have a mesh that is a flat quad but if you look at it in wireframe mode it consists of separate quads (like a minecraft terrain without greedy meshing). So each face is mapped to the texture (actually two triangles).
I use this texture on the mesh with a material and it looks perfect. The texture itself is seamless so it is easily tileable.
However, if I use a texture atlas, there are visible seams, it’s like the other textures I have added to the texture atlas are bleeding over just enough to be there visible seems.

Has anybody experienced this issue? How to resolve this?

Here is a picture of what I’m talking about. Color is different because the lighting is different (it’s two separate projects using the same set of textures).

Edit: typos and clarification

[pspeed]

You have one of two choices:

1. set the min and mag filters to “nearest” so that you get blocky pixelated style textures like minecraft.
2. create a border between all of the ‘cells’ to give gaps in between for the min/mag bleed to have proper color to sample.

[kruze]

Hey pspeed!

Thank you for replying. Gonna try these out. Questino about the second suggestion: what do you mean exactly to create a border? On the mesh itself? Or on the texture?

[kruze]

I tired your first suggestion, it worked beautifully! Still curious about what did you mean by the second suggestion.

[xuan]

I think he means to do this:

Picture shamelessly taken from google images.

[richtea]

Here is an example of my texture map (automatically generated). Here you can see the main textures and also the borders that prevent mipping problems highlighted in red. Those sections in general aren’t shown anywhere but when mipping causing bleeding it’s those borders that bleed in not the neighbouring texture

[pspeed]

For the borders, it’s also common to partially repeat the texture instead of stretching it… at least for repeating textures.

[kruze]

Thank you guys! Now I understand.

[JaRe]

Hi!

I learned here that TextureArray is very good alternative to Atlas / texture map.

Own map with "magic marking" over TextureArray

I’m tinkering with my own map. I still use basics, still no lighting effects. The exercises from the beginner’s documentation and here from the forum let me build a first presentable version. The most important hint from Paul was: Use TextureArray for this task! i’m still busy, the attempts without TextureArray to cut back. At this point I would like to thank Paul and other for the quick answers here in the forum. Video: [My Landscape with JME3] The heart of the marking is thi…

[oxplay2]

Yes, i also like TextureArray too, but it require same sizes and formats of textures, also GLSL 4+ as i remember. I seen some Atlas maps with different texture sizes.

There are probably more differences - so not everyone use it as alternative.

[JaRe]

1. TextureArrays are not available on older versions, nothing can be said about that. is a limitation.

2. In my example, I use square textures for the floor and oblong ones for the walls. You can use multiple arrays with different sizes.

3. For tiny accessories, theoretically, a texture of the array itself can still be a mini atlas.

4. With closed textures I can use repeatable mode: If the panel is e.g. 3 x 3 large for a area, then I do not define the TexCoord from 0f…1f but from 0f…3f in size. Finished. I don’t get closed textures in the atlas.