SDKs and repositories

Molca ships multiple Unity SDKs. This site is one documentation hub: use Molca Core and relevant product sections for your project.

Package map

SDK	Typical Unity path	Repository (example)	Doc section
Molca Core	`Packages/com.molca.core/`	Bundled with product templates	Molca Core
Shared Unity module	`Assets/_MolcaSDK/Code/`	Often next to VR in `molca-sdk-vr`	Shared module
Molca VR training SDK	`Assets/_MolcaSDK/_VR/`	e.g. `molca-sdk-vr`	Molca VR SDK — setup starts here
Molca Digital Twin SDK	`Assets/_MolcaDT/`	e.g. `molca-sdk-dt`	Digital Twin (DT)

Paths are conventions in Molca templates; your repo layout may differ slightly. For validation/version conventions across these SDKs, see Compatibility and validation.

What applies where

Core — RuntimeManager, DI, events, references, sequences, HTTP, modals, settings: any Molca-based Unity app that references com.molca.core.
Shared (_MolcaSDK/Code) — generic UI, preload, media helpers: commonly used with VR; optional for DT-only apps (confirm what your template imports).
VR (_MolcaSDK/_VR) — scenarios, session, XR steps, tour, scoring, Home UI: only VR training projects.
DT (_MolcaDT) — digital twin UI, network/mappers, POI, machine menus: DT projects (overview).

Reading order by product

You are building	Start with
VR training	Architecture → VR overview → VR architecture → Runtime and settings → VR setup
Desktop / twin	Architecture → DT overview → DT architecture → Runtime and settings
Shared library on Core only	Runtime and settings → Molca Core & project settings

Introduction Architecture

Overview

Common Tasks

Molca Core

Shared module (MolcaSDK)

Molca SDK - VR

Molca SDK - DT

Package map

What applies where

Reading order by product

​Package map

​What applies where

​Reading order by product

Package map

What applies where

Reading order by product