Skip to main content
Source root: Assets/_MolcaDT/Code/Scripts/Managers/

​
When to use

Use this page when bootstrapping a DT scene/template and deciding manager initialization order (preload, auth, hierarchy, menu/panel flow).

​
Typical manager chain

_MolcaDT does not use VR ScenarioManager; startup is manager-driven: Exact scene wiring varies by project, but this reflects the common _MolcaDT/Managers responsibilities.

​
Inspector setup checklist

  • Add one active instance per manager type (RootManager, MachineHierarchyManager, InterfaceManager, etc.).
  • Verify singleton/static access patterns in scripts that expose instance (many managers are singleton-like).
  • Confirm required object references (panel roots, prefabs, TMP labels, button hooks).
  • Validate preload/login transitions before opening machine-level panels.

​
Code reference

RootManager is one concrete anchor for scene-driven setup: 
// Assets/_MolcaDT/Code/Scripts/Managers/RootManager.cs
void Awake()
{
    instance = this;
}

public void SetupRootMachinePanel()
{
    if (rootMachinePanel == null || !usingRootMachinePanel) return;
    // Build root machine buttons and click handlers
}

​
Troubleshooting

  • Panel opens with empty root machine list: verify hierarchy data has loaded before SetupRootMachinePanel.
  • Duplicate manager behavior: check for multiple manager instances in loaded additive scenes.
  • Buttons do nothing: recheck prefab/button references and listener setup in manager scripts.