Luxar Viewer API Documentation - v2026.9.22
    Preparing search index...

    Function runInitPipeline

    • Build the complete viewer subsystem graph (scene manager, animation controller, panels, input handler, etc.), wire context-loss / device-loss listeners, and kick the animation loop. Returns the constructed components so the orchestrator can store them on its fields. The order of construction is part of observable behaviour (e.g. PerformanceMonitor depends on the bus the animation controller emits each frame), so the helper keeps the steps strictly in their original order.

      Parameters

      • ports: InitPipelinePorts
      • partial: Partial<InitPipelineResult>

        Mutable accumulator the pipeline fills as each subsystem is constructed. The caller pre-allocates and passes it in so partial state survives an exception: if sceneManager.init throws, partial.sceneManager is still set and LuxarApp.dispose can clean it up. The pipeline ALSO returns the same object cast to the full result type — on the happy path the caller can use either reference.

      Returns Promise<InitPipelineResult>