Technical Limitations Analysis for AR Gaming Devices

Developing an AR game without evaluating the technical limitations of target devices means designing blindly. What works perfectly on HoloLens 2 may deliver 15 FPS on a Meta Quest 3 in passthrough mode, and may not run at all on a budget Android smartphone with ARCore. Analysis of AR device limitations is the first document that should appear in the project, before any architecture. Contact us to get an assessment of your project.

Why is analysis of technical limitations of AR devices necessary?

At first glance, all AR devices display virtual content over the real world. In practice, they do it in fundamentally different ways, and these differences dictate capabilities at the physics level.

Optical see-through (OST) — HoloLens 2, Magic Leap 2. Lenses are transparent, augmented reality is overlaid optically. Consequence: it is impossible to display opaque content, colors are perceived differently (dark shades are almost invisible), field of view is limited (HoloLens 2 — about 52°). For games this means: all content must be bright and contrasty, mechanics cannot rely on occlusion of real objects.

Video see-through (VST) — Meta Quest 3, PICO 4, mobile AR. A camera captures the real world and renders it together with virtual content. Advantage: full control over compositing, occlusion possible. Limitation: latency between the real world and its video image (on Quest 3 about 12-15 ms), color artifacts on object edges, passthrough quality depends on the camera.

Mobile AR (iOS ARKit, Android ARCore) — VST through the main camera. Limitations: lack of depth (no stereoscopic vision), tracking only via SLAM on a single camera, object placement accuracy ~1-2 cm, no controller-level haptic feedback. ARKit with LiDAR provides occlusion 5-10 times more accurate than ARCore without depth sensor, where the error reaches 5-10 cm. Meta Quest 3 offers 2x the field of view of HoloLens 2, enabling more immersive AR experiences.

Which key parameters of AR devices need to be analyzed?

What to know about tracking? — analysis of technical limitations

Determine what the device supports out of the box: plane detection, image tracking, object tracking, face tracking, hand tracking, spatial anchors, scene understanding (mesh reconstruction). ARKit on iPhone 12+ supports LiDAR scanning, giving a mesh of the real world and allowing virtual objects to "hide" behind real surfaces via occlusion. ARCore lacks a depth sensor on most devices and uses monocular depth estimation — significantly less accurate.

Compute budget

AR requires parallel work: camera + SLAM + rendering + game logic. On Snapdragon 888 this works with proper optimization. On Snapdragon 680 (budget segment), ARCore's SLAM algorithm takes 20-30% CPU, leaving less for game logic. Analysis should include specific CPU/GPU budgets for each platform.

Consider an example: on a project with dense geometry and PBR shaders on HoloLens 2, we measured 200k draw calls at 60 FPS — the limit. Increasing triangles beyond 1 million caused drops to 45 FPS. On Quest 3, a similar scene maintained 90 FPS at 300k draw calls thanks to a more powerful GPU. If you plan complex physics or simulations, allocate a separate core for them — otherwise stuttering will occur.

Memory constraints

Textures for AR games are often not compressed as aggressively as in regular games because they overlay the real world and compression artifacts are more noticeable. On devices with 2-3 GB RAM this creates pressure.

Display characteristics

FOV, refresh rate, pixel density — critical for OST devices. HoloLens 2 has ~60 Hz refresh rate and limited FOV, which affects what effects and animations are acceptable. Quest 3 with 110° FOV and 90 Hz offer broader possibilities.

How does the analysis of limitations save project budget?

Timely detection of incompatibilities at the specification stage prevents costly rework. As our technical director notes: Identifying incompatibilities at the specification stage prevents rework that is 10 times more expensive. If your project targets VST devices, you won't waste resources on complex visual effects for OST lenses. Savings at the prototyping stage — up to 40% of time. For a typical project, this translates to savings of $5,000-$15,000 in avoided rework costs. The cost of analysis ranges from $700 to $2,100 per device, a small fraction of the total budget. Get a consultation for your project — we'll assess platform risks and optimization opportunities.

What's included in the work?

The analysis delivers:

• Detailed documentation with benchmark results and capability matrices
• Access to raw data and test scenes for internal verification
• Training session for your team on device-specific optimizations
• Priority support for 2 weeks after delivery for clarification

How we conduct analysis of AR device limitations?

1. Collect specifications — study official documentation and performance profiles of target devices.
2. Benchmark tests — run test scenes on real hardware, measure FPS, batching, draw calls, memory usage.
3. Capability matrix — compile a table per device (tracking, rendering, memory) with noted limitations.
4. Form recommendations — determine minimum viable platform and optimization priorities.

Comparison table of popular AR devices

What is included in the final document?

• Capability matrix per device (hand tracking, plane detection, occlusion, spatial anchors) with statuses: supported/limited/not supported.
• List of constraints for architecture tied to SDK dependencies.
• Definition of minimum viable platform and premium experience.
• Documentation with benchmark results.
• Checklist of technical parameters: CPU/GPU performance, memory bandwidth, tracking latency (motion-to-photon), support for spatial anchors and their stability, compatibility with hand tracking SDKs (ARKit, MRTK, Oculus Interaction), rendering mode limitations (URP/HDRP).
• Each deliverable includes raw data, graphs, and actionable recommendations.

Our analysis covers key AR device constraints such as HoloLens 2 limitations, Meta Quest 3 AR capabilities, iPhone ARKit analysis, and ARCore constraints.

Estimated timelines

With over 5 years of AR development experience and a proven track record of 20+ projects, our analysis is trusted by industry leaders. We guarantee that our recommendations will reduce your technical risk. Order an analysis of your project — we'll evaluate platform risks and optimization opportunities.

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.