Developing VR Multiplayer Modules for Shared Experiences

Imagine two players in Quest 3 headsets grabbing the same virtual cube simultaneously. Without proper networking synchronization, one sees a snap, the other a position mismatch, and joint interaction becomes chaos. We've been solving this for over 5 years, with dozens of commercial VR multiplayer projects under our belt. Reach out to discuss your scenario in detail.

We engineer custom multiplayer modules for shared VR experiences. Synchronizing two hands, head, grabs, and physics objects with a latency of 50–80 ms is our specialty. On Quest's mobile hardware with limited bandwidth, we maintain stable 72 FPS even with 4–8 players. A typical budget for such a module ranges from $10,000 to $25,000, including load testing.

Off-the-shelf networking solutions—Photon Fusion, Photon PUN2, Mirror, Netcode for GameObjects (NGO)—each have their trade-offs for VR. We select the stack for your project: Mirror for small indie titles, Photon Fusion in Server Mode for larger ones. We assess your project free of charge and propose the optimal architecture.

Why Server Mode is Better than Shared Mode for VR

Photon Fusion offers two modes: Shared (peer-to-peer with one host) and Server (dedicated Photon server). For VR, Server Mode is preferable even for smaller projects.

In Shared Mode, one player acts as host, routing all traffic. In VR this means: if the host moves their hands (which happens 72–90 times per second), their own data is processed locally, while other players receive it with the host's RTT. With an unstable host connection, the entire session suffers. Server Mode eliminates this single point of failure—Photon Cloud handles relay and authoritative state management.

A concrete setup: NetworkRunner with GameMode.Server, FixedUpdateNetwork instead of Update for deterministic physics. For hand transforms, we use NetworkTransform with InterpolationDataSource.Predicted—client-side prediction reduces perceived latency.

According to Photon documentation, Server Mode provides the lowest latency for real-time shared experiences.

How to Synchronize Avatars with Minimal Bandwidth

The core technical challenge of VR avatars in multiplayer is that remote players have a full-body avatar with animation, while the local player sees only hands in first person. We need to sync head and two hand positions, then reconstruct the body pose for others.

Our solution is Full Body IK with a limited number of control points. In Unity, we use the Animation Rigging package with TwoBoneIKConstraint for arms and MultiParentConstraint for the torso. The head (HMD position) drives the torso via a heuristic downward offset (~0.3 m), then arms via IK to controller positions. This is not physically precise but looks convincing under normal motion.

Network traffic: three transforms (head + two hands) × 7 floats (pos + rot) × 90 fps = ~7.5 KB/s per player uncompressed. With NetworkTransform and quantization in Photon Fusion, it drops to 1.5–2 KB/s. With 4–8 players, bandwidth remains manageable.

How to Implement Pickup Interaction in Multiplayer: Step-by-Step

1. Create a NetworkObject with Rigidbody and NetworkTransform.
2. On the client, subscribe to the pickup event (e.g., OnTriggerEnter).
3. Request StateAuthority via RequestStateAuthority for that object.
4. Simulate movement on the authoritative side; other players interpolate the position.
5. On release, return StateAuthority to the server.

Synchronizing Physics Objects

Grabbable items, throwable objects, doors—all are physics rigidbodies. The fundamental problem: two clients simulate physics independently, and results diverge. One player throws a cube at a wall—it bounces right on their side, left on another's.

Approach 1: Authoritative physics on the server. All Rigidbody are simulated only on the StateAuthority (in Photon Fusion terms, the one who grabbed the object). Other players interpolate the position. When grabbed, the object 'transfers' to the new holder via RequestStateAuthority. Downside: a slight teleportation is visible on transfer if positions have drifted.

Approach 2: Client-side physics with reconciliation. Each client simulates physics locally; the server periodically broadcasts authoritative state. If discrepancy exceeds a threshold, a soft Lerp moves the object toward the authoritative position. This looks better but is harder to implement without artifacts.

In practice, VR games with physical interactions use approach 1, augmented with a 'ghost' object—a thin semi-transparent copy showing the authoritative position while the main mesh interpolates. Our optimizations reduce cloud server costs by 30–40%.

What's Included in the Work

• Network logic architecture and stack selection
• Basic transform and avatar synchronization with IK
• Physics object synchronization (grabbable, throwable)
• Traffic optimization (quantization, avatar LOD)
• Load testing (up to 8 players)
• Documentation and team training

Development Process

A multiplayer module is a separate task best designed into the architecture from the start, rather than retrofitted into a finished single-player game. Retrofitting multiplayer into an existing single-player VR project typically adds 50–70% more effort compared to initial design with multiplayer in mind.

Stages: networking stack and architecture selection → basic transform synchronization → avatars with IK → physics object sync → game logic (scores, states, rounds) → load testing → traffic optimization.

Pricing is determined after requirements analysis: number of players, interaction type, platform (Quest standalone, PCVR, cross-platform). Contact us to discuss details and timelines for your project. Request development of a module—we will assess your project free of charge.

We have been developing VR multiplayer for over 5 years, with more than 10 commercial projects for Quest and PCVR.

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.