Professional AR Hand Gesture Recognition Setup for Unity and Unreal

Professional AR Hand Gesture Recognition Setup for Unity and Unreal

False positive gestures are the scourge of AR games. The hand shakes, pinch triggers accidentally, a fist is recognized as an open palm. In a Meta Quest project, we spent two weeks just filtering the noise from 26 joint positions from the Meta Hand Tracking SDK. Here is how we solved this problem without overcomplicating things.

What the Platform Provides and What You Need to Build Yourself

Meta Quest (via Meta Hand Tracking SDK or OpenXR Hand Interaction Extension) provides 26 joint positions of the fingers and wrist in world coordinates, updated at 30–60 Hz. These are raw data—bone positions. ARKit (iOS, via AR Foundation) with Vision framework gives a similar set of hand landmarks through ARHandTrackingConfiguration, available since iOS 18. On Android, ARCore does not have a direct Hand Tracking API—third-party solutions are used (MediaPipe via ML Kit) or Google ARCore Geospatial + a custom ML model. Out of the box, you get data, but not gestures. Gesture recognition is your task.

How to Build a Gesture Recognizer

Each gesture is a set of conditions on joint positions:

• Pinch: Euclidean distance between ThumbTip and IndexTip < threshold (usually 2–3 cm in world units). Plus an additional check: MiddleTip, RingTip, PinkyTip are far from the thumb (open). Without the second condition, a fist is falsely recognized as a pinch.
• Open Palm: all fingertip joints are at a significant distance from the Palm joint. We check Vector3.Distance(fingertip, palm) > openThreshold for all five fingers. Additionally, the palm normal (vector from Palm to Middle Metacarpal) should roughly face the camera, otherwise an open palm from behind will also trigger.
• Point: IndexTip extended (large distance from IndexMetacarpal), other fingers curled (small distance tip→metacarpal). Plus the angle between the IndexProximal → IndexTip vector and the palm vector.

Why Debounce and Confidence Filters Are Important

The hand naturally trembles—ThumbTip and IndexTip can randomly get close and move apart faster than 1 frame. Without debounce, a pinch fires 5 times per second when trying to perform it once. Standard technique: a state machine with a time threshold. A gesture is considered active only if the condition has been met continuously for at least N frames (or T seconds). Values: 3–5 frames for quick gestures, 10–15 frames (≈ 0.2 s at 60 Hz) for static poses like Open Palm. Additionally, a confidence filter. The Meta Hand Tracking SDK provides OVRHand.HandConfidence—when tracking confidence is low (hand partially out of view, poor lighting), gestures are not processed. This is critical for AR on smartphones where shooting conditions are unpredictable.

How to Integrate Gestures into AR Foundation?

In AR Foundation (Unity), Hand Tracking is connected via XRHandSubsystem (package com.unity.xr.hands). XRHandJoint for each joint provides TryGetPose()—position and rotation in space. The gesture recognizer subscribes to the XRHandSubsystem.handsUpdated event and processes data in the callback. It is important not to do heavy computation in this callback—it may be called off the main thread. Either buffer the data and process in Update, or use the Job System with IJobParallelFor for multi-hand recognition. For MediaPipe on Android—separate integration via Native Plugin or ready-made wrappers (mediapipe-unity-plugin), data arrives via callback with ML results.

We apply Kalman filtering for joint smoothing and quaternion angle checks for orientation-based gestures. This eliminates jitter and ensures robust detection.

Typical Gestures and Their Thresholds

What's Included in Gesture Recognition Setup?

Timeline and Budget

Timeline: from 3–5 working days for a basic prototype to 2–3 weeks for a full system with 10+ gestures, debounce, and confidence filters. The project budget is calculated individually, but typical costs range from $500 for a basic prototype to $5,000 for a comprehensive system with full testing and documentation. We guarantee reliable performance based on 7+ years of experience and provide a 30-day warranty on integration.

How to Proceed

1. Contact us with your requirements and target platform.
2. We analyze your project and propose a solution within 1-2 business days.
3. We deliver a prototype for testing and feedback.
4. After approval, we finalize integration and provide documentation.

Experience and Trust

With over 7 years of expertise and 15+ successful projects on Meta Quest and iOS, we have a proven track record in hand gesture recognition for AR. Our clients include gaming studios and enterprise AR developers. We provide a reliable, production-ready system backed by a warranty.

Learn more about Meta Hand Tracking SDK and OpenXR Hand Interaction. Contact us to get a consultation from an engineer.

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.