Adding a Texture loads out parts without textures

[Coney133 (Coney)]

You’ll notice that adding a texture to a part in studio will load out parts without textures once you go away from it. This bugs started happening about a month ago. My studio graphics quality level is at 21. This bug also occurs in-game as well.

Steps to reproduce:
Adda texture to a part, and do not add a texture to the overlapping part such as:

Here’s a video which should do a better job explaining the bug.

I’m not 100% sure if this is a bug, so feel free to correct me if I’m wrong.

[PeZsmistic]

This is a duplicate of any of the many threads about texture z-sorting being imperfect. The issue is the texture on the middle rectangular part is sorted incorrectly and covers up the parts that are in front of it.

You can see they still exist as evident by the black pixels on top of the wall here:

Opaque textures render over thin parts

When a thin part is placed on top of a part with a texture on top, the texture can render through the thin part. This happens when you zoom out and/or find some special camera angle. The zoom level and angle required is related to the size of the part underneath (something something texture origin something camera z-plane?). [image] Gross.rbxl (15.5 KB) I am using a GTX 1070. This is an old bug, this issue seems related and lots of discussion about similar layering issues has al…

[Coney133 (Coney)]

Sorry, didn’t see your post when I tried searching for the bug.

[OuterspaceNemo (Nemooo)]

Thanks for the report! We’ve filed a ticket to our internal database and we’ll follow up when we have an update for you.

[Coney133 (Coney)]

Hi, I was wondering if there’s any update on this since it’s been about 2 months.

Thanks!

[hyperhumanist]

TL;DR: Not a bug - but generally expected limitation of the system. Could be improved, but would require very complicated changes to the system, not likely to happen soon.

Explanation in detail:

The issue that you are experiencing is called z-fighting: two parallel, but not identical, polygons at same (or very similar) distance will generate non-identical depth buffer values in each pixel so they will sort wrong.
What happens here in particular is that the Texture renders on top of its parent part. In order to prevent z-fighting of the Texture with its own parent part, we apply what is known as “depth-bias”: the polygon rendered on top is “moved a bit towards the camera”.
So, when you put another part that is also near-parallel, then that Texture will render a bit over this other part, due to numeric imprecision. As you go further away, the imprecision increases thus the problem is more likely to occur.
There’s nothing much that can be done to fix this in general unless we were to completely change how Textures work, which will probably not happen in the near future.

One workaround that would function, but may be not applicable for you, or too complicated, would be to use a mesh part for the entire thing. Alternatively, make the overlaid part a bit thicker, which will push the problem a bit further away.