VR Locomotion System Design: Teleportation & Comfort

Motion sickness is the leading cause of VR game returns. According to research, up to 60% of users abandon games with poor locomotion. We design VR movement systems: teleportation, smooth movement, snap turn, and their combinations. This article explains why proper locomotion is key to player retention and how to avoid common design pitfalls. Our experience spans over 20 successful projects for PC VR and mobile headsets.

Why Smooth Movement Causes Nausea

Motion sickness in VR arises from vection—the illusion of movement when there is none in reality. The visual system tells the brain "we are moving," the vestibular system says "we are still." This conflict causes nausea in 40–60% of first-time users. Smooth stick movement is the strongest trigger for vection, but it can be used with mitigation mechanics. Comparison: a vignette reduces nausea by 50% compared to no dimming.

The primary tool is the locomotion vignette. When moving, peripheral vision (outside 40–50° from center) is darkened via a tinted overlay. The brain perceives movement only in the central zone, reducing vection. In Unity, this is implemented through a post-processing Vignette effect with dynamic intensity tied to speed via RTPC, or using the specialized TunnelingVignette component in XRIT 3.x.

Parameters for a starting vignette: easeInTime = 0.15 s, easeOutTime = 0.3 s, featheringEffect = 0.3, vignetteIntensity = 0.6. All parameters are exposed in Comfort Settings—different players have different sensitivity thresholds. We can tune comfort profiles for your audience—contact us for a consultation.

Teleportation: More Than "Move Position"

Teleportation seems simple, but details separate "works" from "works well." Arc visualization—a parabola from controller to landing point. In XRIT, this is done via XRRayInteractor in Projectile Curve mode plus TeleportationProvider. Parabola parameters: velocity = 8–12, acceleration = -9.8. The hit point is determined by raycasting against Teleportation Area/Anchor colliders with a Layer Mask.

Validity: players must not teleport into air or walls. TeleportationArea only checks colliders, not NavMesh. If validation is needed, create a custom TeleportationArea with an override of ValidateTeleportation that calls NavMesh.SamplePosition.

Orientation after teleport: best practice is letting the player aim their gaze via stick rotation. TeleportationProvider supports MatchOrientation = TargetUpAndForward.

Transition animation: fade to black in 0.2–0.3 s eliminates the abrupt camera jump. Implementation via ScreenFadeProvider that intercepts the teleportRequest.

Tuning Comfort Parameters for Different Players

Most modern VR games use a hybrid system: teleportation + smooth movement + snap turn. The Locomotion System architecture in XRIT supports registering multiple LocomotionProvider instances simultaneously. Important: ContinuousMoveProvider and TeleportationProvider can conflict on simultaneous input. LocomotionSystem has an exclusivityMode—when one provider activates, others are blocked. Priority: teleportation should interrupt smooth movement.

For rotations: snap turn (instant rotation of 45°) causes no discomfort. Smooth turn is continuous, acceptable up to 60–90°/s. Comparison: snap turn reduces discomfort by 70% compared to smooth turn for sensitive players. For action games, a hybrid with 22.5° steps is optimal.

// Example script for dynamic vignette in XRIT
public class SpeedBasedVignette : MonoBehaviour
{
    public TunnelingVignette vignette;
    public ContinuousMoveProvider moveProvider;
    
    void Update()
    {
        float speed = moveProvider.moveSpeed; // current speed
        vignette.vignetteParameters.intensity = Mathf.Lerp(0.2f, 0.9f, speed / 5f);
    }
}

Which Locomotion System for Your VR Game?

The choice depends on genre and audience. For quest and action games, best practice is a hybrid with teleportation priority. For walking simulators, smooth movement with a tunable vignette works. Comparison of locomotion types:

What's Included in the Work

• Analysis of target platforms and audience
• Design of the locomotion system (teleportation, smooth, snap, comfort profiles)
• Implementation in Unity (XRIT) with custom elements (NavMesh, animations, vignette)
• Configuration of Comfort Settings (vignette, speed, rotation angles)
• Testing on target devices, bug fixing
• Documentation on settings and integration
• Post-release support (2 weeks free)

This reduces rework costs by 30% and lowers the testing budget by preventing errors. Order turnkey development—we evaluate your project in 1–2 days.

Design and Implementation Timeline

Cost is calculated after analyzing game requirements and target platforms. Get a consultation—contact us to discuss your project.

More about vection on Wikipedia

VR and AR Development

When we first launch a project in a VR headset, most teams face the same thing: technically everything works, but in the headset either motion sickness occurs, or hands 'float' with a delay, or the scene looks jerky at the periphery. These are not bugs in the usual sense — they are a consequence of the fact that VR/AR development requires a different approach to render architecture, interaction, and UX from the very beginning of the project. Our experience: over 7 years in game dev, 15+ completed VR/AR projects for Meta Quest, SteamVR, PSVR2, HoloLens. We work with teams that need not just a prototype but a production‑ready application with a stable frame rate.

Platforms and SDKs

We work with all relevant stacks. We use OpenXR as the base layer wherever possible — it provides cross‑platform compatibility between Meta, Valve Index, HP Reverb and other PC VR devices. On top of OpenXR, we build on the XR Interaction Toolkit (Unity) or VR Expansion Plugin (Unreal). Contact us for a stack assessment tailored to your project.

How to minimize motion sickness in VR locomotion?

Locomotion — the main source of motion sickness for inexperienced VR users. According to research, about 70% of users experience discomfort with improper movement settings Oculus Developer Guidelines. Teleportation — standard navigation method when smooth movement is undesirable.

Components from XR Interaction Toolkit: TeleportationArea, TeleportationAnchor, TeleportationProvider. Basic implementation works out of the box, but for production we refine it in four steps:

1. Setting up XRRayInteractor with a curved ray (Bend Ray) — the teleportation arc looks more natural than a straight ray and is perceived better by users.
2. Adding a valid landing zone — a visual indicator changes color when hovering over an obstacle (red/green).
3. Implementing fade transition — smooth screen fade (black fade) before teleportation reduces disorientation.
4. Rotation snapping — after teleportation we offer snap rotation by 45° or 90° instead of smooth, reducing motion sickness risk.

For projects requiring smooth locomotion (action games, simulators), we use comfort settings: vignetting during movement, reducing FOV during acceleration. Settings are available to the user in the menu — different people have different sensitivity thresholds. The difference between kinematic and physics‑based movement: kinematic gives instant hand following but lets objects pass through walls; physics‑based via Joint provides realistic collisions but requires velocity damping and max joint force tuning. We choose based on the type of interaction.

How to make object grabbing in VR physically realistic?

This is the most underestimated part of VR development. Clients often perceive it as 'just hand animation', but in practice it is a complex system where physical correctness, responsiveness, and comfort conflict.

Grab (grabbing)

XR Interaction Toolkit provides three types of Interactable for grabbing:

• XRGrabInteractable — standard grab, object follows controller via physics joint or direct position/rotation
• XRSimpleInteractable — for objects without physical movement (buttons, levers)
• Custom Interactable by inheriting from XRBaseInteractable

Attach Transform — a frequently ignored detail. Each Interactable must have a properly configured Attach Transform (the point where the hand 'attaches'). Without it, the pistol grip will be at the center of the mesh, not where it is held.

For weapons and tools with two‑handed grab — a separate TwoHandGrab system: leading hand determines position, the second — orientation. XR Interaction Toolkit supports this via XRTwoHandGrabInteractable or custom logic with two Attach Points.

Throw (throwing)

Velocity smoothing is critical for realistic throwing because the Rigidbody.velocity at the moment of controller release reflects instantaneous speed, often incorrect due to tracking discretization. The user makes a quick wrist movement — but the object flies half as fast.

Solution: velocity smoothing over the last N frames (typically 5–10 frames, ~80–160 ms at 60 Hz) before release. XR Interaction Toolkit does this via VelocityEstimator. Additionally, we apply a velocity scaling multiplier — a small speed increase (1.2–1.5×) makes throws subjectively more satisfying. Angular velocity (for objects that should spin in flight) is also averaged similarly.

AR: Plane Tracking and Environment Interaction

AR adds a different class of problems — working with real, unpredictable environment. AR Foundation — a cross‑platform layer on top of ARKit and ARCore. Most basic features (plane detection, raycasting, image tracking, face tracking) are available through a unified API.

Plane Detection

ARPlaneManager detects horizontal and vertical planes. Practical nuances:

• Initialization takes time — the user must look around the room while the system builds a map. An explicit onboarding with instruction 'slowly move the camera across surfaces' is needed.
• Planes are unstable — their boundaries and position are updated as data accumulates. Objects placed on a plane need to be attached via parent to ARPlane, not to world coordinates.
• Plane merging — two detected floor segments may merge into one, moving the anchor. For critical anchors, use ARAnchor instead of direct attachment to the plane.

Image tracking (via ARTrackedImageManager) quality directly depends on the quality of reference images. Images with high detail frequency and contrasting edges (like a QR code but stylish) track more reliably than smooth logos. ARCore Geospatial API — for outdoor AR with real‑world coordinate binding (accuracy up to 10 cm in well‑mapped areas).

Optimization for VR: Frame Rate and Comfort

VR requires stable high frame rate. About 60% of development time in mobile VR goes to optimization, not functionality — retrofit costs twice as much as proper architecture from the first sprint.

Single Pass Instanced Rendering

The main render optimization in VR. Without it, the scene is rendered twice (once per eye), doubling draw calls. Single Pass Instanced renders both eyes in one pass via instancing: geometry is processed once, the shader gets two view/projection matrices through GPU instancing. Enabled in Unity via XR Plug-in Management > Rendering Mode: Single Pass Instanced. Important: custom shaders must support SPI — standard URP/HDRP shaders support it, custom HLSL requires modifications (UNITY_SETUP_STEREO_EYE_INDEX_POST_VERTEX and related macros). Applying this technique reduces draw calls by 40–50%, making it twice as efficient as naive double rendering.

Foveated Rendering

On Meta Quest, Fixed Foveated Rendering (FFR) is available — reducing resolution at the periphery where visual acuity is lower. Configured via OVRManager or Meta XR SDK:

OVRManager.fixedFoveatedRenderingLevel = OVRManager.FixedFoveatedRenderingLevel.High;
OVRManager.useDynamicFixedFoveatedRendering = true;

Dynamic FFR automatically increases the level when frame rate drops — more convenient than fixed in scenes with variable load.

IPD and Comfort Settings

IPD (Inter‑Pupillary Distance) — affects depth perception. At the programmable level on most devices, only reading IPD is available (OVRPlugin.GetSystemDisplayFrequency), physical adjustment is on the headset. For applications requiring precise positioning (medical simulators, training), we account for IPD in scene scale calculations.

Haptics

Haptic feedback — an underestimated tool. Even a simple vibration response when grabbing an object or hitting significantly increases the sense of presence. On average, integrating haptic patterns takes 30–80 hours per project.

XR Haptics via OpenXR:

var hapticImpulse = new UnityEngine.XR.HapticCapabilities();
InputDevice device = InputDevices.GetDeviceAtXRNode(XRNode.RightHand);
device.SendHapticImpulse(0, amplitude: 0.5f, duration: 0.1f);

For complex patterns (tactile 'texture' of a surface when touched, increasing vibration when drawing a bowstring) we use Meta Haptics Studio — allows designing haptic clips visually. This can reduce time spent on manual haptic tuning by about 30%.

What does VR/AR application development include?

When ordering a turnkey project, we provide the following deliverables:

• Architectural document with stack description, render logic, and interaction system
• Working prototype (MVP) for testing on target device
• Integration of necessary SDKs (Meta XR, OpenXR, AR Foundation, etc.)
• Optimization for target frequencies 72/90/120 Hz with draw call and FPS profiling
• Testing on physical hardware (Quest, SteamVR, HoloLens) with user involvement
• Full documentation for build, deployment, and support
• Training for the client's team (workshop on XR Toolkit)
• Warranty support for 1 month after delivery

What affects cost and timeline?

VR/AR projects are more expensive than regular games of similar scope. Iterations are slower — each fix must be tested in the headset, an emulator does not convey the real experience. Motion sickness forces reworking some conceptual decisions after the first playtest. Optimization takes a significant portion of time — for mobile VR (Quest) up to 60–70% of the cycle. For Quest projects, we start optimization from the first sprint. The cost of basic SDK integration (XR Interaction Toolkit) varies depending on the scope of custom Interactable. Typical budgets for a full Quest project range from $25,000 to $80,000 depending on complexity, number of custom interactions, and depth of optimization. Proper architectural planning from sprint one typically saves 40% on later rework compared to fixing performance bottlenecks retroactively.

Get a consultation on your project — we will assess the task, stack, and timelines. Order turnkey VR/AR application development with a guaranteed stable frame rate.