DT project layout

_MolcaDT/
└── Code/
    └── Scripts/
        ├── Managers/           # RootManager, PreloadManager, LoginManager, MainMenuManager, …
        ├── Network/            # NetworkManager, TokenRenewalManager, APIMapperInvoker*, SSE tooling
        ├── POI/                # POIManager, POIHandler, POIFollowTarget
        ├── Handler/            # Panel handlers, MachineInfo*, FunctionDataHandler, …
        ├── JsonMapping/        # JsonMappingAsset, JsonMappingEvaluator
        ├── UI/                 # SimpleImageUI, SearchButtonHandler, EventAlertButtonHandler, …
        ├── Scriptable Object/  # e.g. CameraConfiguration, DigitalTwinDynamicModule
        └── Editor/             # Inspectors, JsonMappingWindow, POI editors, …

​

Troubleshooting

• Script not found after clone — Ensure the molca-sdk-dt package/folder is under Assets/_MolcaDT (or your fork’s equivalent); asmdef / platform settings may hide scripts if the folder was moved outside Unity’s asset database.
• Wrong manager firing — Many types use instance singletons (NetworkManager**, POIManager, TokenRenewalManager); duplicate bootstrap objects cause Destroy or double requests—keep one DT root scene.
• Namespaces — Production code mixes MolcaDT.* with Molca.DigitalTwin (**DigitalTwinDynamicModule**); search both when tracing URLs and auth.
• Editor-only tooling — Editor/ scripts apply only in the Unity Editor; CI builds omit them—do not reference editor types from runtime assemblies without guards.
• Upgrade / merge conflicts — Handler/Panel Handler/ is deep; prefer adding new panels in a subfolder than editing stock handlers, to ease upstream merges.

​

Next pages

• DT startup flow
• DT network and mapping
• DT POI and panels

​

Unity Editor

Expand Code/Scripts/Managers and one Handler panel in Project.