IFCBEARING and IFCREFERENT elements not rendered in 3D view

[vovka236]

Describe the bug 📝

Environment

• @thatopen/components version: 3.3.2
• @thatopen/components-front version: 3.3.3
• @thatopen/fragments version: 3.3.6
• Browser: Chrome / Edge
• Model: IFC4x3 bridge model

When loading an IFC4x3 bridge model, IFCBEARING and IFCREFERENT elements are
not rendered in the 3D view, despite being present in the model.
Both element types are visible in BIMvision desktop 3.1.2.

Availability in API:

• IFCBEARING: returned by both model.getItemsOfCategories(SPATIAL_CATEGORIES)
  and model.getSpatialStructure()
• IFCREFERENT: returned by model.getItemsOfCategories(SPATIAL_CATEGORIES) only,
  absent from model.getSpatialStructure()

Neither type produces any visible geometry in the 3D viewport.

Reproduction ▶️

No response

Steps to reproduce 🔢

Viadotto Acerno.zip

1. Load an IFC4x3 bridge model containing IFCBEARING and IFCREFERENT elements
2. Observe the 3D view - neither element type is rendered
3. Confirm presence via:
   const spatialItems = await model.getItemsOfCategories(SPATIAL_CATEGORIES);
   const spatialStructure = await model.getSpatialStructure();
4. IFCBEARING appears in both; IFCREFERENT appears only in spatialItems

System Info 💻

System:
    OS: Windows 11 10.0.26200
    CPU: (24) x64 AMD Ryzen 9 7900X3D 12-Core Processor
    Memory: 10.47 GB / 31.12 GB
  Binaries:
    Node: 24.12.0 - C:\Program Files\nodejs\node.EXE
    npm: 11.12.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 148.0.7778.97
    Edge: Chromium (143.0.3650.75)
    Firefox: 145.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.