Functional Testing of VR Controllers Across Headset Models

Introduction: Typical VR Controller Compatibility Issues

We have encountered situations where an application that works perfectly on Quest 2 loses functionality on Quest Pro. The cause is different Input Binding Profiles and haptic APIs. Without functional testing of controllers for each headset model, such a bug is guaranteed to make it into release. Our team has conducted over 50 VR testing projects, including shuttle checks on 8 headset models. We perform end-to-end testing—from test bench setup to final report. Bug fix budget savings can reach up to 40% compared to post-release patches.

How to Properly Configure Input Mapping for All Controllers

OpenXR standardizes input via OpenXR Input Binding Profiles. In Unity with XR Interaction Toolkit and OpenXR Plugin, all controller actions are mapped through an InputActionAsset with multiple binding profiles: Oculus Touch Controller Profile, Valve Index Controller Profile, HTC Vive Controller Profile, Windows Mixed Reality Controller Profile.

A common issue: binding is set for only one profile. A developer adds <XRInputBinding path="/user/hand/right/input/trigger/value"> without specifying a profile—the binding applies to the "default" controller and does not work on Index Knuckles or WMR controllers. We recommend using multi-profile bindings: for each action in the InputActionAsset, add bindings for all supported profiles. XR Interaction Toolkit provides a Default Input Actions asset with preconfigured multi-profile bindings—a good starting point, but requires auditing for the specific project.

Specific to Meta Quest Pro: Touch Pro controllers have additional sensors (stylus pointer, face buttons capacitive touch). If the application uses OVRInput directly instead of OpenXR Actions, you must explicitly handle OVRInput.Controller.TouchPro as a separate type—otherwise some buttons return incorrect values. OpenXR Actions are better than OVRInput for cross-platform compatibility: they automatically adapt to the profile, reducing the risk of bugs.

Hand Tracking: An Alternative Input Often Overlooked

Quest 2, 3, and Pro support Hand Tracking without controllers. If the application claims to support hand tracking, it must be tested separately—Hand Tracking has a different input pipeline and different limitations.

The XR Hands Package (com.unity.xr.hands) provides XRHandSubsystem with data on 26 joints per hand. Gestures are implemented via XRHandGesture components or custom logic. The problem: the pinch gesture, the primary interaction method without a controller, suffers from latency and false activations during fast finger movements. In our tests, false pinch activation rates during normal finger activity can reach 15%, which is unacceptable for gaming scenarios. Response latency can be 30–50 ms, critical for rhythm games.

Test cases for Hand Tracking differ from controller ones: we check detection accuracy in low-light conditions (below 100 lux), with hand occlusion, and during fast gestures. We record false activation rates and provide recommendations for sensitivity threshold tuning. Getting a consultation on Hand Tracking setup can significantly reduce debugging time.

Why Haptic Testing Is Critical

Touch Pro and Touch Plus have the TruTouch haptic system—more precise vibration with amplitude and frequency support. Touch on Quest 2 provides basic vibration with a single intensity parameter. The APIs differ: OVRHaptics for native Meta, XRBaseController.SendHapticImpulse(amplitude, duration) for OpenXR. On Touch Pro via Meta XR SDK, OVRInput.SetControllerVibration offers extended parameters. If only the basic OpenXR haptic API is used, TruTouch on Pro controllers will work like ordinary vibration, not leveraging the hardware advantage. As a result, the user loses immersive experience, and the team spends time on post-release fixes.

Test: compare haptics on Quest 2 and Quest 3/Pro for the same game events. Sword strike—different intensity? Expected. Haptics completely missing on one device—bug, we log it.

Test Matrix: What Is Included in the Work

Functional testing is conducted using a matrix: devices × test cases. Minimum matrix for a Quest-first project:

Each cell: Pass / Fail / Not Applicable + description on Fail. This is a living document updated with each build. The deliverable is a test matrix with documented Fail cases, priorities, and fix recommendations. Scope includes: Input Mapping audit, haptic and Hand Tracking checks, stress testing of edge conditions.

Timelines and Work Format

Functional controller testing requires physical access to devices. If the client does not have test headsets, we discuss using our devices or rental.

The deliverable is a test matrix with documented Fail cases, priorities, and fix recommendations. The cost is calculated after receiving the list of supported devices and functionality scope. Get a consultation—we will estimate the scope and timeline for your project.

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.