Interpolation Algorithms for Smooth VR Avatars in Networked Games

Why Standard Interpolation Doesn't Work for VR Avatars

In a typical networked shooter, interpolating a character's position with 50–80 ms latency is unnoticeable: the model lags slightly, but it's within normal perception. In VR, this breaks. Another player's head and hands must move without jitter — otherwise, the brain perceives it as unnatural and the sense of presence collapses. Meanwhile, the HMD sends tracking data at 72–120 Hz, and the network delivers packets irregularly. We solve this by combining multiple interpolation algorithms and an adaptive buffer.

The typical mistake is applying the same methods used for gameplay objects to VR avatars. Vector3.Lerp between two received positions with a fixed t=0.1 produces a rubbery lag, especially noticeable on hands: the hand continues moving toward the old target even after a new position arrives. The root cause is the frequency mismatch: VR scene rendering at 90 Hz (11 ms per frame) versus network updates at 20–30 packets per second (33–50 ms per packet). Between two network snapshots, we need to generate 3–4 intermediate states, and jitter (packet delay variation) can reach 20–30 ms even on a good connection.

Adapting Interpolation for High Jitter

Dead Reckoning with Correction (Predictive Interpolation)

We store a buffer of the last N states (position + orientation + velocity + time). At render time, we compute a predicted position based on the last known velocity: predictedPos = lastKnownPos + velocity * deltaTime. When a new network packet arrives, we smoothly correct to the real position over 3–5 frames. Velocity is computed as (currentPos - prevPos) / packetDeltaTime and smoothed via EMA (Exponential Moving Average) with α=0.3. This approach works well for the head, where movement is inertial. For hands, it's worse: a hand can instantly stop or sharply change direction.

Hermite Spline Interpolation — 6× More Accurate on Sharp Turns

For smooth curvilinear motion, we use Hermite Spline. We build a spline through the last 4 tracking points with tangents (derivatives). Implemented as HermiteInterpolate(p0, p1, m0, m1, t) where m0/m1 are the tangents at the points. Comparison: linear interpolation yields up to 30% error on sharp hand turns; Hermite — less than 5%. This makes the avatar look more natural and users experience less discomfort.

Jitter Buffer: Configuration and Adaptation

A Jitter Buffer is mandatory. We maintain a buffer of incoming packets for 2–3 network frames (60–100 ms). We always render from the buffer, not from the last packet. This adds latency but removes jitter from irregular packet arrival. The buffer size is adapted dynamically: if jitter increases (determined via standard deviation of interpacket interval over the last 10 packets), we increase the buffer; if it stabilizes, we decrease it. An adaptive buffer outperforms a fixed one: on a stable network, it reduces latency by 20%; during spikes, it prevents packet loss.

Why Quaternion Slerp Over Lerp?

Quaternion.Lerp produces non-linear rotation speed at large angles. Quaternion.Slerp is the correct choice for head tracking. For the wrist IK solver when recovering from motion data, it's also important to normalize the quaternion after interpolation — accumulated float errors over several frames cause artifacts in FK. Learn more about Slerp.

Inverse Kinematics for the Avatar Body

HMD + two controllers provide 3 tracking points. From these, we need to recover poses for shoulders, elbows, and spine. For this, we use an IK solver. In Unity — Animation Rigging (package com.unity.animation.rigging) with TwoBoneIK Constraint for arms and ChainIKConstraint for the spine. Configuring hint objects for elbows is critical: without them, arms bend into unnatural positions. We compute the hint position analytically from the controller position and direction toward the body. For more complex bodies and Full Body IK — FinalIK or a custom FABRIK solver. FABRIK (Forward and Backward Reaching IK) converges iteratively in 5–10 iterations, sufficient for real-time.

How to Set Up an Adaptive Jitter Buffer: Step-by-Step

1. Define base parameters: window size for statistics (default 10 packets).
2. Compute the standard deviation of interpacket intervals.
3. Set a target confidence level (e.g., 95%).
4. Calculate the required buffer size as mean + 2*stddev.
5. Limit the maximum size (e.g., 150 ms) to avoid exceeding the latency budget.
6. On each new packet, update statistics and adjust the buffer.
7. Profile: average latency and percentage of dropped frames.

Interpolation Algorithm Comparison for VR

What's Included in the Work

• Architectural documentation and algorithm selection per your requirements
• Implementation of NetworkAvatarController with isolated interpolation logic
• IK tuning for target anthropometries and testing at extreme values
• Integration into your project (Unity, Unreal Engine, Godot)
• Team training on the system
• Technical support for 2 months after delivery

Example Savings

On one project, the client saved over 40% of debugging time for network code thanks to our system — instead of manually tuning buffers and algorithms, they received a ready-made solution that adapts to real network traffic.

Work Stages

We take a systematic approach: profile the network, select algorithms for your conditions, implement, calibrate IK, and test under degradation. For simulation, we use tc netem (Linux) or Clumsy (Windows) with parameters: latency up to 200 ms, packet loss 10%, jitter 50 ms. Below are estimated timelines.

public class AdaptiveJitterBuffer : MonoBehaviour
{
    private Queue<StateSnapshot> buffer = new Queue<StateSnapshot>();
    private float targetDelay = 0.1f; // 100 ms
    
    void Update()
    {
        // Adaptation based on jitter
        float jitter = CalculateJitter();
        targetDelay = Mathf.Clamp(0.05f + jitter * 2f, 0.05f, 0.15f);
    }
}

We have specialized in VR/AR development for over 5 years and have delivered 30+ projects for PC, consoles, and mobile platforms. We guarantee that the final system will pass your network degradation tests. Contact us to evaluate your project — we'll discuss details and choose the optimal solution. Order algorithm development today: get an engineer consultation within 24 hours.

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.