AR Tracking Stability Testing Under Different Lighting Conditions

A user places a virtual object on a table, but it floats in the air — this isn't a bug, it's tracking loss due to lighting. We encounter this on nearly every second project. Sunlight at a 15° angle, 100 Hz fluorescent flicker, dark room with spot LED — each scenario breaks tracking in its own way. With over 30 projects involving positional tracking, we can predict these scenarios and eliminate them before release. Contact us for a detailed audit of your project.

Causes of Tracking Loss Under Poor Lighting

Visual inertial odometry (VIO) algorithms, which power ARCore and ARKit, rely on feature points — distinct points in the frame — to estimate camera position. Below approximately 50 lux, the number of reliable feature points drops sharply, and the system compensates using IMU data. This works until IMU drift accumulates. In practice, after 3–4 seconds in poor light, the anchor drifts by 5–8 cm. In gaming, this is catastrophic: the object appears to hover instead of sitting on the surface.

Overexposure is also critical: direct sunlight creates zones with saturated pixels where feature extraction fails. ARKit reports this via ARCamera.TrackingState with reason .insufficientFeatures, ARCore via TrackingFailureReason.INSUFFICIENT_LIGHT. The thresholds differ, but both allow showing a user warning.

Fluorescent lamps are a separate pain point. At 50/60 Hz, they create flicker that the sensor registers as periodic exposure variations. Visually it's almost imperceptible, but the algorithm sees feature points "breathing" between frames and interprets this as camera movement. According to Apple documentation, ARKit uses VIO and detects insufficient lighting via ARCamera.TrackingState.

How We Test Different Lighting Types

Our standard test matrix covers three axes:

• Light level: dark room (~10-30 lux), office (~300-500 lux), cloudy outdoor (~1000-5000 lux), direct sunlight (>50,000 lux).
• Light source type: point (LED), linear (fluorescent tube), diffuse (clouds), mixed (window + ceiling).
• Dynamics: static, moving shadows, day/night transition, flickering light.

For each scenario, we record: time to tracking loss, maximum ARAnchor drift over 60 seconds, number of .limited events, recovery time.

Tools: custom overlay in Unity AR Foundation displaying session state in real time, recording via ReplayKit (iOS) or MediaProjection (Android).

Comparison of ARCore and ARKit Under Low Light

At a lighting level of 30 lux — typical for a dimly lit room — we tested both platforms. After 4 seconds of tracking, ARKit reported .limited with .insufficientFeatures, while ARCore continued tracking for 8 seconds before also going limited, but with notable anchor drift. This means ARKit enters limited state 1.7x faster than ARCore under low light. In our projects, we use these differences to tailor the user experience and fallback logic.

Handling Tracking Loss in Sunlight

When tracking is unstable in a specific lighting range, it's a UX task. A few techniques:

• Enabling ARWorldTrackingConfiguration.environmentTexturing helps ARKit better understand the environment but increases memory usage. On iPhone 12 and newer, it's justified.
• For poor light — force plane detection with ARPlaneDetectionMode and anchor to planes instead of feature points. More stable.
• On Android — setting Config.FocusMode.FIXED reduces blurred frames during fast motion in low light.

Improper illumination assessment can cost extra weeks of QA and up to 20% of budget for rework. With our testing, you can save up to 40% of budget on the optimization phase — typically $5,000 for a single platform.

How to Conduct AR Tracking Testing: Step-by-Step Plan

1. Define requirements: target platforms, OS versions, device models, typical usage conditions, acceptable anchor drift.
2. Set up test environment: adjustable lights, curtains, set of targets with different textures.
3. Run the scenario matrix, recording metrics: time to tracking loss, ARAnchor drift, .limited events.
4. Analyze results: determine critical lighting thresholds for each platform.
5. Adjust AR session configuration and UX state handling accordingly.

Deliverables

Our deliverables include:

• Documentation: Test results with drift graphs and threshold tables.
• Access: Custom Unity overlay for real-time tracking state monitoring.
• Training: Team training on best practices and code review.
• Support: Ongoing support for up to 30 days after handover.

All deliverables are tailored to your platform (iOS/Android) and device set. Our certified Unity developers (over 5 years of experience) guarantee tracking stability improvements. Pricing starts at $2,000 for a single platform and $3,500 for dual platform.

Our Process

We start by collecting requirements: target platforms, OS versions, device models, typical usage conditions, acceptable anchor drift. We then set up the test environment: adjustable lights, curtains, textured targets. We run the scenario matrix, capture metrics, and produce a report with thresholds and recommendations. If needed, we adjust AR session configuration or add UX handling for critical states.

Timelines: from 2-3 days for a single platform to 2-3 weeks for full coverage with iterations. Cost is determined after analysis — request a consultation and we will evaluate your project within one day. Full-cycle service.

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.