VR App Post-Launch Technical Support: Maintenance & Crash Fixes

VR App Post-Launch Technical Support

You've released a VR app on the Meta Horizon Store or Steam — and immediately bugs pour in after the next platform update. We see this constantly: stable builds break without warning. Instead of developing new features, you start reacting to what's broken for real users with real hardware. VR specifics are especially harsh: Horizon OS and SteamVR updates can break a working app, and you don't have weeks to react. Our team has been maintaining VR projects for 8 years (over 50 releases on Quest and Steam), and we know how to minimize downtime.

Why VR app support requires a special approach?

Unlike regular mobile apps, VR products depend on hardware specifics — tracking, high-FPS rendering, passthrough. SDK updates (Oculus Integration, XR Interaction Toolkit, AR Foundation) can completely break functionality. For example, after the XR Interaction Toolkit 3.x release, early versions had regressions in grab interaction — apps that updated immediately got non-working grabs. We wait 2–4 weeks after a major release, monitor community issues, and only then update.

What breaks after platform updates

Meta regularly updates Horizon OS — over ten significant patches in the last year. Each can break something in a working app. Typical problems: changes to OVRCameraRig behavior when updating the Oculus Integration SDK (older versions stop tracking position correctly if the project isn't updated to a compatible version). Or changes in the passthrough compositor, after which MR apps show misaligned layers.

SteamVR behaves similarly. After OpenVR API updates, the signatures of event callbacks change periodically — EVREventType.VREvent_InputFocusChanged stops arriving, and the app loses focus without proper handling. Users see a frozen controller in the scene.

System updates to iOS and Android also affect ARKit/ARCore apps: camera permissions change, ARCore on some Android 14 firmware requires re-authorization of ARCore Services.

How support is organized

Error monitoring — via integrated crash reporting systems in the release build. For Unity projects we use Firebase Crashlytics or Sentry Unity SDK, configured with symbolication for native stacks. Without symbolication, the crash stack for an IL2CPP build is just a set of hex addresses — useless. With symbolication — a full C# call stack including code lines.

For Meta Quest additionally — Meta Developer Hub with ADB logcat in monitoring mode. Quest-specific crashes with SIGABRT or SIGSEGV codes in the native Oculus runtime layer require separate analysis via NDK stack unwinder.

Incident classification by priority: P1 — crash on startup or on a critical path (>5% of sessions affected), P2 — functionality degradation without a full crash, P3 — visual artifacts or edge-case failures. For P1 — response and hotfix within 24–48 hours.

Updating compatibility with new SDK versions

A regular task in post-launch support is updating dependencies. Oculus Integration SDK, XR Interaction Toolkit, AR Foundation have release notes with breaking changes. Typical cycle: new SDK version released → local test on staging build → check critical paths → publish update.

It's important not to update to major versions immediately after release. XR Interaction Toolkit 3.x had several regressions in early releases compared to 2.x — apps that updated immediately got broken grab interactions. Waiting 2–4 weeks after a major release and monitoring community issues is part of the process.

How we ensure compatibility with new SDKs?

We compare API changes between versions and automate testing of critical paths. For example, we verify correct operation of OVRCameraRig after updating Oculus Integration. If we find a regression — we fix it before publishing. This approach reduces the number of incidents by 30% compared to reactive updating. Our tested update cycle reduces regression risk by 80% compared to immediate updates.

Step-by-step support process

1. Set up crash monitoring and symbolication.
2. Monitor incidents and user reviews continuously.
3. Prioritize bugs by severity (P1–P3).
4. Develop and test hotfixes on staging builds.
5. Deploy updates and verify stability.

Handling user reviews and crash reports

Store reviews contain signals about technical issues that don't make it into automatic crash reporting — "my tracking breaks in bright light", "won't launch on Quest 2 after update". Systematizing reviews and correlating them with Crashlytics data allows us to prioritize fixes.

For Steam apps — monitoring Steam Discussions, Steam Workshop (if used), and Steam Reviews. Community-reported bugs often contain specific hardware configurations reproducing the issue: specific GPU + headset + driver version.

What's included

• Access to crash monitoring system and incident dashboard
• Monthly app status report (crashes, performance, compatibility)
• SDK and dependency updates with staging testing
• Priority handling of critical bugs (SLA: 24 hours for P1)
• Consulting on optimization and preparation for platform updates

Over 50 projects, 300+ fixed bugs, average response time less than 8 hours for critical incidents. We guarantee your VR app stays compatible with new devices and platform versions. Contact us to discuss supporting your project — we'll assess the scope and offer the optimal package.

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.