Anyone having issues with ZIndex Decals? Here's my issue

I was very excited to see the ZIndex property finally released for decals/textures, primarily for creating layered face decals. After toying with it for a little while I noticed one major issue and I’m curious if some of you may have run into this and what you may have done to resolve it?

In the below gif you will see that I have a decal for the eye colors and another for the eye shape and detailing. The pupils are ZIndex 0 and eyes ZIndex 1:

https://gyazo.com/4485e14ac3765127e1069b800f0064c4

The issue is at certain angles the layering is reverted. When the eyes are seen with correct layering, 0 is acting as the bottom layer and 1 as the top, and when it is seen incorrect the layering is 1 is the bottom and 0 is the top (I swapped the numbers to verify this).

The issue occurs randomly depending on the position of the layered decals and the angle of the player’s camera. It’s not consistent along one specific camera angle/axis.

This is of course in a humanoid player with a transparent fake head welded to the original head to preserve the face detail. At first I thought the mesh could be the culprit but even removing the mesh I would see this issue. Interestingly enough, if I placed these decals on a part separate from the player I could not find an angle at which the layering was incorrect.

Any help on this would be greatly appreciated. I’m not sure if I’m just using this incorrectly or if I have found a bug. Thanks in advance!

Romul

2 Likes

Adding onto this post, further investigation has shown that if I remove the head that displays the decal outside of the humanoid player the decal layering shows perfect. Could this be an issue with using this inside humanoids?

1 Like

I’m also having the same issue with ZIndex not working in my game as well. My decal part is not transparent, and parenting the decal part to a non-humanoid model fixes the overlapping, so it definitely has something to do with humanoids messing with a decals ZIndex. Hopefully, Roblox staff will fix this soon!