Achieving Smooth VR Across Refresh Rates: Graphics Optimization

A missed frame in VR isn't just a visual glitch—it's a vestibular conflict: the visual system says “you're still,” while the vestibular system says “you're moving.” With regular frame drops, nausea sets in. We specialize in VR development and optimizing VR graphics for 72/90/120 Hz. Our experience: after VR profiling and rendering optimization, we stabilize the stable VR framerate to a consistent 90 fps even on projects that originally struggled to hit 72. The budget savings from a proper audit are direct: typical GPU time reduction is 30% or more, saving thousands in development costs. Get a consultation for your project.

Why Missed Frames Are Critical in VR

At 72 Hz VR, the frame budget is 13.9 ms. At 90 Hz VR—11.1 ms. At 120 Hz VR—8.3 ms. Every millisecond counts, and standard game optimization approaches don't work here. The Meta Quest 3 defaults to 72 Hz—the developer must explicitly request 90 or 120 through OVRManager.display.displayFrequency (see OVRManager documentation). But requesting isn't enough: you must ensure the render budget can maintain frames at the chosen frequency.

How to Measure Performance Loss

No data means no optimization. The first step is always profiling using OVR Metrics Tool (for Quest) or Unity Profiler connected to the device. We focus on GPU time per frame, not FPS—FPS can appear stable thanks to Asynchronous SpaceWarp (ASW), which synthesizes intermediate frames on drops. After VR profiling, we use Frame Debugger to analyze draw call sequences and RenderDoc VR for detailed GPU captures.

Where Milliseconds Are Actually Lost

The most common cause of frame drops is overdraw from transparent materials. VR renders both eyes, so every semi-transparent object is drawn twice. RenderDoc VR can measure overdraw precisely: in Overdraw Heatmap mode, you can immediately see where pixels are redrawn 8–12 times.

The second issue is draw calls. On the Quest 3 (Snapdragon XR2 Gen 2), the GPU isn't as problematic as CPU overhead from a high number of calls. 300 draw calls with inefficient batching can cost 3–4 ms on the CPU side alone. GPU Instancing works well for identical meshes, Static Batching for static geometry. Dynamic Batching should be disabled in VR and replaced with manual DrawMeshInstanced for dynamic objects.

The third is shadows. Real-time shadows are a luxury in VR. The standard approach: bake shadows into lightmaps for static geometry and use Blob Shadow Projectors or pseudo-shadows for dynamic objects.

What Is Fixed Foveated Rendering and How to Use It

How Optimization Works in Practice

Typical result: Quest 3 optimization, action game, start—68 fps at 72 Hz. After optimization: stable 90 fps with 2–3 ms headroom. Our experience confirms: FFR High plus disabling real-time shadows yields the main gain. Using our method, you can achieve 2x faster framerate stabilization compared to manual trial-and-error.

What's Included in the Work

• Profiling audit with a detailed report (identifies all bottlenecks).
• Recommendations for render and batching optimization, including shader and LOD adjustments.
• Code changes (FFR, shaders, LOD, batching).
• Testing on target platform with metrics (GPU/CPU time, frame timing).
• Documentation: settings guide, optimization checklist, and ongoing support options.
• Deliverables: source code changes, configuration files, and a summary report.

Why Choose Us

With 7+ years of VR development experience and over 50 optimized projects, we bring proven expertise. Our team includes Oculus-certified developers who guarantee a stable framerate with at least 20% GPU headroom after optimization. We provide cost-effective solutions: our full optimization audit starts from $1500, and typical savings from a proper audit are direct—often reducing GPU time by 30% or more. That is 3x more efficient than standard profiling.

For VR graphics optimization targeting a stable VR framerate at 72 Hz VR, 90 Hz VR, or 120 Hz VR, efficient profiling and rendering techniques are essential. Contact us for a consultation—we'll evaluate your project and propose an optimal plan.

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.