TourSubsystem

​

When to use

​

Role

• Loads / unloads tour areas (often additive scenes)
• Teleports between spots
• SharedString home scene for returning to lobby
• Optional keep-loaded radius when leaving an area (reduces reload churn)

​

Runtime flow (simplified)

​

Code

using Molca;
using MolcaSDK.VR.Scenario.Tour;

public static class TourApi
{
    public static TourSubsystem Subsystem => RuntimeManager.GetSubsystem<TourSubsystem>();

    public static async Awaitable<bool> GoToArea(TourScenarioData data) =>
        await Subsystem.TransitionToAreaAsync(data);

    public static void Jump(TourSpotController spot) => Subsystem.TeleportToSpot(spot);

    public static async Awaitable<bool> ExitToLobby() => await Subsystem.EndTourAndGoHomeAsync();
}

​

Troubleshooting

• Transition fails — TourScenarioData null or Addressables / scene name mismatch; check OnError and console for [TourSubsystem] messages.
• Teleport does nothing — TourSpotController needs TeleportationAnchor; ensure XRI teleport provider is active.
• Home scene wrong — Set SharedString on the subsystem so value matches a Build Settings scene name (or your loader contract).
• Memory / load churn — Tune maxDistanceToKeepAreaLoaded or call UnloadDistantInactiveAreaScenesAsync after teleports if you manage areas manually.

​

Related

• VR content hierarchy — tour vs simulation trees
• Tour area and spots
• Scenario mode drivers — tour driver
• VR player manager — ground position for distance checks
• Session authentication — ScenarioSessionManager for tour posts

​

Unity Editor

RuntimeManager prefab → TourSubsystem with home SharedString and distance fields.