[REGRESSION]: Raycaster returning null

[ShaMan123]

Describe the bug 📝

I upgraded to latest version 3.4.5 along with:

    "@thatopen/components": "^3.4.5", // also "^3.4.6"
    "@thatopen/components-front": "^3.4.3",
    "@thatopen/fragments": "^3.4.5",
    "camera-controls": "^3.1.2",
    "three": "^0.184.0",

Using raycaster stopped working, it always returns null.

Reverting to previous version works.

   "@thatopen/components": "^3.3.3",
    "@thatopen/components-front": "^3.3.3",
    "@thatopen/fragments": "^3.3.7",
    "camera-controls": "^3.1.2",
    "three": "^0.182.0",

Reproduction ▶️

No response

Steps to reproduce 🔢

No response

System Info 💻

n/a

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.

[ShaMan123]

related #737?

[ShaMan123]

I can confirm that reverting to 77e3034 does not include this regerssion

[rihokirss]

We hit a related regression on @thatopen/components 3.4.4 → 3.4.5 in our project. Different surface symptom from raycaster-returning-null, but possibly the same underlying issue — flagging it here in case it's useful.

Setup
"@thatopen/components": "3.4.5",
"@thatopen/components-front": "^3.4.3",
"@thatopen/fragments": "3.4.5"

Symptoms — once we apply highlight styles to elements (e.g. our content-validation tool colours items by status, or our filter engine ghosts everything and colours a subset), the Highlighter.events.select picker breaks for the coloured items:

• Clicks on a highlighted element either select an element behind it, select nothing, or occasionally activate a random unrelated localId.
• Non-highlighted elements in the same model remain clickable as before.
• Clearing all highlight styles restores normal picking immediately.

Reproduces with both single-style highlight (one colour over plain materials) and multi-style setups (ghost + coloured subset).

Bisection — pinning only @thatopen/components back to 3.4.4 (keeping components-front 3.4.3 + fragments 3.4.5) restores correct picking. fragments and components-front versions don't affect the symptom. Likely related to the same commit OP narrowed down
(77e3034).

[rihokirss]

We hit a related regression on @thatopen/components 3.4.4 → 3.4.5 in our project. Different surface symptom from raycaster-returning-null, but possibly the same underlying issue — flagging it here in case it's useful.

ok I dicovered that 3.4.6 is available and fixed the problem!

[ShaMan123]

seems 3.4.6 does solve this issue
Highlighter remains in regression, maybe something changed about its config?

[Rocha442]

I have tested with multiple browsers and it seems that this issue still occurs when using either Firefox or Edge with the latest packages versions.

[Rocha442]

I believe i found a temporary fix (at least for me). It seems that using thatopen/components-front": "3.4.2" and up breaks the raycaster, so i reverted back to 3.4.1. All other packages are updated and are working as intended.