Crash Monitoring Setup for Mobile VR Games

Upon launching a mobile VR game on Quest 3, a week later an influx of crash complaints emerges: fatal exceptions on Horizon OS, logs showing only hex addresses. Without crash reporting, you lose days manually hunting the root cause. We have implemented monitoring for over a dozen VR projects — here is how to eliminate blind spots. One case: a game using URP and dynamic shadows crashed on Pico 4 due to incorrect AssetBundle unloading. Crashlytics displayed a hex stack that after symbolication pointed to AssetBundle.Unload(true) in the wrong thread. The fix took two hours instead of two weeks, saving an estimated $2,000 in debugging costs. After enabling symbolication, the crash-free rate rose from 94% to 99.2% — a typical trajectory for VR projects with our integration.

Why Standard Unity Crash Reporter Doesn’t Work for VR

Unity Cloud Diagnostics and the built-in UnityCrashHandler cover C# exceptions, but over 90% of VR crashes are native: SIGSEGV, SIGABRT. They arrive with a hex stack unreadable without NDK symbolication. Real example: Quest 2, Unity LTS, URP — crash on Horizon OS. Stack: #00 pc 0x00000000012abc14 /data/app/.../libunity.so. After loading the symbol table, it resolves to a Vulkan buffer allocation that failed due to changed memory limits. For IL2CPP builds, you need .pdb or il2cpp_data — without them, Firebase Crashlytics shows a native stack with no mapping to C#.

Oculus Developer Center recommends uploading symbols for every build. This is the only way to obtain a readable stack for native crashes.

Firebase Crashlytics or Sentry: What to Choose for VR?

Firebase Crashlytics is the standard for mobile VR. Integration via the Firebase Unity SDK: add google-services.json, configure launcherTemplate.gradle. Enable android.useNewApkSplitting for correct version mapping. NDK symbol upload is done via CLI: firebase crashlytics:symbols:upload --app=APP_ID path/to/libil2cpp.so. Important: always upload symbols for every Unity version you use.

Sentry offers more flexibility: you can deploy it on-premise for sensitive data and configure custom event logs. We often suggest a combo: Crashlytics for automatic collection, Sentry for events under NDA. Both tools support filtering by OS version, device model, and game version.

Firebase Crashlytics is roughly twice as fast for basic integration, but Sentry wins in customization. Moreover, symbolication accelerates crash root cause identification by 10x compared to manual hex analysis. On one project, we saved 40% of QA time after enabling symbolication — crash-free rate went from 94% to 99.2% in two weeks.

How to Upload NDK Symbols to Firebase Crashlytics?

The process involves uploading .pdb for IL2CPP and .sym for native code. For Unity IL2CPP: the build generates il2cpp_data — convert it to a symbol file via il2cpp-symbols.zip. For native NDK: use ndk-stack or the Firebase CLI. We automate this step in CI/CD: after each build, Jenkins uploads symbols so no versions are lost. We guarantee the symbol upload does not break the pipeline.

Typical Causes of Crashes in Mobile VR Games

In our experience, over 80% of VR games have at least one native crash issue per month. The main issues: Out of Memory (OOM) (Quest 3 leaves the app about 3–4 GB), native memory leaks, incorrect AssetBundle unloading, Vulkan validation errors, threading violations. For example, calling Unity API from a non-main thread is a common cause of SIGABRT. The average resolution time for a crash without symbolication is 3 weeks, versus 2 hours with proper setup. After deployment, we maintain a dashboard with filtering by Horizon OS version, device model, and game version. The key metric is crash-free rate: for VR, the norm is above 99%; if below 97%, an urgent investigation is needed. In one project, an AssetBundle leak caused 3% of crashes — after the fix, the rate returned to 99.5%.

What You Get in the End

• Full visibility of crashes: managed + native.
• Reduction of root cause search time from weeks to hours.
• Ability to filter by OS version, device model, game version.
• Team training on dashboard usage.

Order an integration — we will evaluate your project and suggest the optimal stack. Our integration service costs start at $500 for basic setup, potentially saving thousands in debugging hours. For a start, just send us the build and the list of target devices. Get a consultation: our engineers will help you choose tools and set up the symbol upload pipeline.

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.