Comfort QA Testing for VR Games

Motion Sickness in VR is not a subjective feeling. It is a physiological response to specific patterns in movement, rendering, and interactions. We conduct systematic Comfort QA testing to identify and eliminate these patterns before release. Our protocol reduces discomfort complaints by 70% and ensures passing Meta's review without an 'Intense' rating. Without Comfort QA, an app reaches a limited audience or gets rejected. We offer a turnkey service: from audit to final testing. Contact us to evaluate your project—we'll select the optimal test plan.

Why Comfort QA Is Critical for Your VR Project

Meta requires compliance with Comfort guidelines for placement in the Quest Store. Our team has over 5 years of experience in VR development and testing, and we know how to meet these requirements. Our protocol detects twice as many triggers as standard testing, confirmed by results from 50+ projects.

How Vestibular Conflict Affects Comfort

The root cause of VR motion sickness is a mismatch between what the eyes see and what the vestibular system feels. If the in-game camera moves while the user stands still—conflict arises. Not all users react the same way, but design must account for sensitive individuals.

Most common triggers:

• Acceleration/deceleration. Smooth camera movement at constant speed is significantly better tolerated than movement with acceleration and braking. Teleportation (instant transition without intermediate motion) is a standard alternative for locomotion-sensitive users.
• Horizon roll. When the camera tilts on the Z-axis (roll) without corresponding physical head tilt—a strong trigger. For airplane tilt in a flight simulator: either limit roll angle to 15–20° or provide a 'stabilized horizon' option.
• Field of View during movement. Dynamic FOV reduction during acceleration (Vignette effect) reduces peripheral motion perception and lessens motion sickness. In Unity, implement via Post Processing Volume with dynamic Vignette.intensity parameter tied to character speed.
• Framerate drops. A frame drop at 90 Hz introduces 11 ms delay. Regular drops to 60 fps when targeting 90 ms cause perceived judder. For sensitive users, 10–15 minutes at 60 fps instead of 90 is enough to trigger discomfort.

Comfort QA Testing Methodology

Comfort QA is not 'played and okay'. It is a documented protocol.

Physical testers. You need people with varying VR sensitivity: from 'iron stomach' to those who get sick from any locomotion. Minimum 3–5 people, including at least one with high sensitivity. This parameter cannot be artificially simulated.

Simulator sickness is assessed using the Simulator Sickness Questionnaire (SSQ), developed by NASA, consisting of 16 items. Filled before and after each session. We calculate normalized scores on three scales: Nausea, Oculomotor, Disorientation. For Comfort QA, we record SSQ after every test session—this reveals trends across iterations.

Session protocol. 15 minutes of continuous active gameplay (active—static experience does not reveal locomotion triggers). Then SSQ. 30-minute break. Repeat session if needed. A tester who experiences discomfort stops immediately—continuing worsens the condition and yields no additional data.

Technical Checks in Comfort QA

Beyond subjective testing, we perform automated technical checks:

• Latency to photons. Motion-to-photon latency must be below 20 ms. Measured via OVR Metrics Tool (mode Motion-to-Photon Latency). Above 20 ms—visible lag of image behind head movement, a direct discomfort trigger.
• Frame time consistency. Not just average fps, but standard deviation of frame time. Unstable 90 fps with spikes to 30 ms is worse than stable 72 fps. Frame time measured via OVR Metrics Tool in recording mode—we look at histogram, not average.
• Head movement tracking fidelity. We verify that Camera.main.transform follows the HMD precisely without software smoothing. Any Lerp or SmoothDamp on the camera transform is an immediate trigger. XROrigin must update via XRInputSubsystem, without additional 'improvement' scripts.
• Stroboscopic effects. List of flashing elements in the scene checked against Meta's 3 Hz limit. Particularly relevant for particle effects and shader animations.

Comparison of Locomotion Methods and Their Impact on Comfort

Comfortable vs Uncomfortable Patterns

What's Included in Our Comfort QA Service

• Audit of current scene and project configurations
• Conduct SSQ testing with a panel of respondents (3–5 people)
• Technical analysis of latency, frame time, tracking fidelity
• Report with prioritized issues and recommendations
• Retesting after fixes (up to 3 iterations)
• Final documentation for passing Meta Comfort Guidelines

Timeline and Cost

Comfort QA timeline: from one week (audit + basic protocol) to 3–4 weeks for a full cycle with iterations. Cost is determined after reviewing the project and defining the scope of testing. Get a consultation—we'll design the 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.