Skip to main content
ARCHITECTURE / PIPELINE

A clear path from BIM to experience

Keep the pipeline legible. Each layer remains inspectable as the application grows.

  1. Open the model — read the Fragment 2.0 file and validate its metadata.
  2. Stream the right representation — load geometry in chunks and keep startup responsive.
  3. Preserve structure — retain ModelGuid, element IDs, relationships, properties, and materials.
  4. Process in chunks — create Unreal representations, prioritize shell geometry, and schedule work.
  5. Build the experience — stream the geometry you need while keeping BIM context available to the application.

What happens after load​

LoadFragmentAsync reads and validates the model and retains metadata, element lookup data, representations, samples, and materials. It does not by itself spawn the model into the world.

ProcessLoadedFragment consumes that loaded state, builds bucket roots, schedules chunked work, prioritizes shell geometry, creates meshes and HISM instances, and registers cells for distance-aware visibility.

Representation strategy​

  • LOD0 represents source elements through HISM instances and generated meshes.
  • LOD1 merges cell contents.
  • LOD2 provides whole-model proxy tiers.
  • Selection can promote a cell or activate a proxy before retrying the trace.