Expected behavior
The mountain in the image should not be highlighting, as its the player only that should be highlighted.
A private message is associated with this bug report
Highlighting is not correctly determining what should be highlighted, and adding too many highlights
2 Likes
Highlighters have a property called “DepthMode” and by default its set to always on top which makes it so it overlaps other objects like in the picture you sent. To fix this set depthmode to occluded.
It’s possible that the highlight glitched out and now shows on top of everything even if it’s occluded, I had that happen, it’s mostly because of quality settings render distance or content streaming. It’s better to use highlights only when needed and destroy the unused ones (disabled still counts), still wishing they just added a render distance for them instead of a limit
1 Like
From the looks of the image, it seems like this is a separate Highlight instance given that the one on the mountain has a FillColor while the one on the player does not? Could this be a different Highlight that actually exists; being enabled randomly, mapping incorrectly, or staying alive past it’s life-time? It’s still a bug in all 3 of these cases, but it’s possibly a different issue to triage.
1 Like
This i know, but its showing on things that never have highlights, and aren’t intended to have a highlight object parented to them
No,
As seen from this image, theres no way a stray highlight could occur.
The script is the only script that highlights.
1 Like
No instances of highlight also exist.
@Abcreator
@LvieReal
Theres no highlights that are applying to top.
1 Like
I told you that it’s a glitch and even though it’s set to occluded it still renders on top because of it