Skip to main content
This page is a high-level map of Molca’s startup and configuration — the glue between Unity, Molca Core, and product code (VR, DT, shared UI). Use it before diving into Molca Project Settings or Scenario Data Config.

Startup chain

  1. MolcaProjectSettings (ScriptableObject) is resolved at load time (default asset path or Addressables key — see script).
  2. The assigned RuntimeManager prefab is instantiated and marked DontDestroyOnLoad (RuntimeManager).
  3. RuntimeSubsystem components on that prefab register with the runtime (tour, session, fade, etc.) (Runtime subsystem).
  4. GlobalSettings referenced from the same project settings asset exposes SettingModule entries — ScenarioDataConfig, optional media/modal modules, and product-specific pieces.
Important: Which subsystems and modules exist is determined by the prefab + GlobalSettings you assign in MolcaProjectSettings, not by implicit auto-discovery.

What lives where

ConceptTypical locationDoc entry
Root settings assetMolcaProjectSettingsMolca Project Settings
Living runtime singletonRuntimeManager (prefab instance)RuntimeManager
Pluggable services on runtimeRuntimeSubsystem subclassesRuntime subsystem
Named config bagGlobalSettingsSettingModule[]Global settings
VR scenario catalog & modesScenarioDataConfigScenario Data Config

VR-specific subsystems (examples)

Your RuntimeManager prefab in a VR template usually includes subsystems such as:
  • TourTourSubsystem for tour scenarios.
  • SessionScenarioSessionManager for connected auth, content fetch, and session lifecycle (session loading).
  • Presentation — fade, player, inventory managers as needed (VR presentation docs group).
Exact components depend on the prefab shipped with your repo; treat the prefab as the manifest of runtime capabilities.

Content vs runtime wiring

For the content tree (modules → scenario → activity/step vs tour), see VR content hierarchy.

Digital Twin note

The DT SDK (_MolcaDT) uses Molca Core patterns where linked, but not the VR scenario / tour stack above. Start from DT overview and DT project layout.