VRPlayerManager

​

When to use

• Read player ground position (GetGroundPosition — head XZ with XR Origin Y).
• Enable or disable all XR Interaction Toolkit locomotion providers together (teleport, move, snap turn, etc.), e.g. during precision Grab step work.
• Access left/right VRControllerVisual from static properties for haptics or visuals.

​

Inspector setup

​

Code

using MolcaSDK.VR;
using UnityEngine;

public class LocomotionGate : MonoBehaviour
{
    private VRPlayerManager player;

    private void Awake()
    {
        player = GetComponent<VRPlayerManager>();
        if (player == null)
            player = VRPlayerManager.Instance;
    }

    public void DisableMovement() => player.SetLocomotionEnabled(false);
    public void EnableMovement() => player.SetLocomotionEnabled(true);
    public void ToggleMovement() => player.ToggleLocomotion();
}

​

API (key members)

​

Troubleshooting

• “Instance not found” / null static access — Only one VRPlayerManager should exist on the active rig; Awake assigns Instance. Ensure the rig is active before calling static helpers from arbitrary objects.
• Locomotion toggle does nothing — Confirm LocomotionProvider components live under the same GameObject hierarchy (auto-discover) or are assigned in manual list. Check the Console for “No locomotion providers” warnings.
• VRSubsystem not found — RuntimeManager prefab must include VRSubsystem; wait until after subsystem init (manager waits in Start).
• Wrong ground height — GetGroundPosition uses xROrigin.transform.position.y; verify XROrigin reference and floor / tracking setup.

​

Related

• Scenario activity — broader scenario / VR flow
• RuntimeManager — initialization and GetSubsystem
• Grab step — typical reason to disable locomotion
• EventDispatcher — locomotion state events

​

Unity Editor

XR Origin root with VRPlayerManager + locomotion components.