Selection, Orbiting & Raycasting isn't possible for "Clipped" Fragments Model

[NadaElnagar]

Describe the bug 📝

Hello,

First of all thank you guys for all the brilliance you created over the years and even more for allowing users to provide feedback.

Recenlty I've been trying things out with the engine and with Fragments, I think everything is going just fine until I faced this issue where I'm unable to select or pivot around objects (I'm using setOrbitPoint) when a clipping plan is in the way (above, before) of the target objects, here are 3 snaps to explain the issue:

1- No Clipping is Active ( you can see the sphere which indicates where the mouse is picking) :

2- Clipping is Active (I can't select or target an object to pivot around)

3- Clipping is Active but I'm after or below the section plan, I'm able to pick and pivot around

It's noticeable that this issue isn't there when I'm Using an IFC model, please refer to the next snap :

I appreciate your help on the matter.

Again, guys, thank you really for this amazing Repo.

Go Open BIM

Reproduction ▶️

No response

Steps to reproduce 🔢

No response

System Info 💻

System:
    OS: Windows 11 10.0.26200
    CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13900HX
    Memory: 11.40 GB / 31.69 GB
  Binaries:
    Node: 25.2.1 - C:\Program Files\nodejs\node.EXE
    npm: 11.6.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 144.0.7559.60
    Edge: Chromium (143.0.3650.139)
    Internet Explorer: 11.0.26100.7309

Used Package Manager 📦

npm

Error Trace/Logs 📃

[DEBUG] [Click] Click event started
Debug Log.js:44 Data: {clientX: 592, clientY: 418, isDragOperation: false, sectionsCount: 1}
Debug Log.js:42 [DEBUG] [Click] Mouse coordinates calculated
Debug Log.js:44 Data: {normalizedMouse: {…}, pixelMouse: {…}}
Debug Log.js:42 [DEBUG] [Raycast] Starting fragment raycast...
Debug Log.js:42 [DEBUG] [FragRaycast] raycastFragmentModels called
Debug Log.js:44 Data: {hasFragmentsRef: true, hasLoadedModelsRef: true, loadedModelsCount: 1, mouseCoords: {…}}
Debug Log.js:42 [DEBUG] [FragRaycast] Raycasting frag model
Debug Log.js:44 Data: {modelName: 'Duplex.frag', modelId: 'frag-1768649278604-0'}
Debug Log.js:42 [DEBUG] [FragRaycast] Raycast result for model
Debug Log.js:44 Data: {modelName: 'Duplex.frag', hasResult: true, resultType: 'object', resultKeys: Array(14), hasPoint: true, …}
Debug Log.js:42 [DEBUG] [FragRaycast] Hit point is clipped
Debug Log.js:44 Data: {sectionId: 1}
Debug Log.js:42 [DEBUG] [FragRaycast] All models raycasted
Debug Log.js:44 Data: {resultsCount: 0}
Debug Log.js:42 [DEBUG] [FragRaycast] No valid results, returning null
Debug Log.js:42 [DEBUG] [Raycast] Fragment raycast completed
Debug Log.js:44 Data: {hasResult: false, resultType: 'null', resultKeys: Array(0)}
Debug Log.js:42 [DEBUG] [Raycast] No fragment hit, falling back to Three.js raycast
Debug Log.js:42 [DEBUG] [Raycast] Valid objects for Three.js raycast
Debug Log.js:44 Data: {validObjectsCount: 13}
Debug Log.js:42 [DEBUG] [Raycast] Three.js raycast completed
Debug Log.js:44 Data: {totalIntersects: 0}
Debug Log.js:42 [DEBUG] [Raycast] No Three.js intersects, clicked on empty space

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.

[NadaElnagar]

I found the solution here for any one who's facing the same issue
https://people.thatopen.com/c/ask-the-community/active-clipper-does-not-pass-through-raycaster-latest-thatopen-packages