Ghostmode aka Transparency is not consistent

[pstowasser01]

Describe the bug 📝

Im trying to get transparency working with the ghostmode to better visualize specific elements in my scene.

Im currently colorizing my elements based on a status with the highlighter and adding styles based on the hex color and coloring a modelidmap with one of those styles. (there might be a better solution on coloring but this works quiet well and the styles can be reused)

Now i followed the ghostmode tutorial and also added the highlighterstyle materials next to the core.models.materials list to get affected by transparency!

Now in the viewer I hover over my elements (using the hoverer object) and the Transparency is not consistent based on where the camera is looking from like shown in following images:

From one angle its correctly colored behind my other transparent element, but from my second angle its custom hex highlighter material is showing when behind another element instead of the hoverer material.

Tested on v3.4.0

Reproduction ▶️

No response

Steps to reproduce 🔢

• Import a model
• add highlighter styles with a color
• enable ghostmode (or maybe only setting transparency is sufficient)
• use the hoverer to hover over elements in the scene
• hover over an element that has another (transparent) element in front of it

System Info 💻

System:
    OS: Windows 11 10.0.26100
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i7-13700H
    Memory: 10.39 GB / 31.59 GB
  Binaries:
    Node: 24.14.1 - C:\Program Files\nodejs\node.EXE
    npm: 11.5.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 147.0.7727.101
    Edge: Chromium (140.0.3485.54)
    Firefox: 149.0.2 - C:\Program Files\Mozilla Firefox\firefox.exe
    Internet Explorer: 11.0.26100.8115

Used Package Manager 📦

npm

Error Trace/Logs 📃

No response

Validations ✅

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
• Check that this is a concrete bug. For Q&A join our Community.
• The provided reproduction is a minimal reproducible example of the bug.