Set visibility = false but still effected by hover effect

[andersskeiefocus]

Describe the bug 📝

First I select a wall icon

then I set visibility upon that ifcElement to be false

then it is hidden

but the hidden element is effected by the hover effect

This worked in version
"@thatopen/components": "^3.3.0",
"@thatopen/components-front": "^3.3.0",
"@thatopen/fragments": "^3.3.6",
"@thatopen/ui": "^3.3.0",
"@thatopen/ui-obc": "^3.3.0",

but fails in
"@thatopen/components": "3.4.5",
"@thatopen/components-front": "3.4.3",
"@thatopen/fragments": "3.4.5",
"@thatopen/ui": "3.4.1",
"@thatopen/ui-obc": "3.4.2",

AI pinpointed it to
The bug is in step 1: child.material = this._idMaterial (single material) causes the ID render to ignore geometry.groups — so hidden faces still write their item ID into the buffer. The picker then incorrectly reports a hidden item is under the cursor. Once that wrong answer reaches step 4, your hoverer material dutifully displays it.

Let me know if you need more info

Reproduction ▶️

No response

Steps to reproduce 🔢

No response

System Info 💻

windows

    "@thatopen/components": "3.4.5",
    "@thatopen/components-front": "3.4.3",
    "@thatopen/fragments": "3.4.5",
    "@thatopen/ui": "3.4.1",
    "@thatopen/ui-obc": "3.4.2",

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.