BaseScenarioData without digging through every setup doc first.
Related mental model: VR content hierarchy · Bootstrap: Runtime and settings.
Asset types (data)
Scenario assets usually live under something like
Scenario/Data/ or your content folder; the exact path is project-specific.
Scene types (Unity)
Rule of thumb: anything you
LoadScene by name (or Addressable key) must be included in the player build (or delivered as Addressables) and must match the string your code or data references.
Wiring checklist
- Register scenario assets in ScenarioDataConfig (or your org’s fetch path) so Home / runtime can resolve them.
- Add Preload, Auth, Home, and each scenario scene to File → Build Settings (or your Addressables groups) — Scenes and build settings.
- Reference scenario data on the ScenarioManager in the scenario scene (and align mode driver / data kind).
- For tour, confirm area scene names match TourScenarioData / subsystem expectations and that TourSubsystem
homeScenepoints at your Home scene’s SharedString.
Related
- New scenario quick start — asset to playable scene
- VR architecture — VR layers on Core
- Architecture — product-neutral stack
- Home UI — scenario selection entry