Hello everyone, I’ve been facing this problem for a long time: the HighlightLayer starts to overexpose and behave very strangely when it interacts with certain other functions. For example, in this case, I reproduced the moment when objects intersect with each other while two HighlightLayers are enabled simultaneously—one blue and one red.
This also happens with text.
Because of this, in my main project, I have to somehow work around it or completely disable the HighlightLayer (but I really like it and want to use it).
Is there any solution to this problem (other than simply disabling the other color)?
Or, for example, when we see text, I had to completely disable the HighlightLayer, otherwise the same bug would happen—the object would start glowing very brightly.
has a compatibility bug with WebGPU — there is a problem with sampler binding at the engine level, and it cannot be worked around.
I tried to run it, but it didn’t work.
Does it only work on WebGL?
The problem is that SelectionOutlineLayer has a compatibility bug with WebGPU — it incorrectly sets up the sampler binding (Filtering sampler incompatible with non-filtering sampler binding), which breaks the entire render pipeline. Neither forceGLSL nor disabling MSAA helps — this is a bug at the Babylon.js engine level.
The problem has been solved, I found your correspondence on the forum 4 days ago, and decided to update the version to the latest, and indeed the problem has been solved.
