Graphics Optimization Specifications for Mobile VR Headsets

We develop graphics optimization specifications for mobile VR headsets. For example, Quest 3 renders two images at 2064×2208 pixels each on a Snapdragon XR2 Gen 2 chip at a target frame rate of 72–90 fps — without any headroom for drops. Every frame below the target either results in an ATW artifact (Asynchronous TimeWarp pulls an old frame) or real latency causing discomfort for the player. Our years of experience optimizing for Meta Quest and other headsets ensures the specification will be workable immediately after implementation. Average savings on rework amount to $5,000–$10,000 thanks to early problem detection — this is confirmed by 50+ completed projects. Our specification package is typically priced at $1,500, providing a 3x return on investment by preventing costly later-stage fixes.

Graphics Optimization Specification for Mobile VR Headsets

Without numerical constraints, the team risks exceeding the GPU budget, leading to dropped frames or ATW artifacts. The specification cements limits in advance, saving time and money. Typical projects with our specifications show a 40% reduction in rework.

How do we determine the GPU budget for a mobile VR headset?

The main metric for Quest is GPU time per eye frame. At 72 fps, each eye has roughly 6.9 ms. At 90 fps — 5.5 ms. Anything that doesn't fit results in either ATW or a drop.

A typical budget is broken down by category:

Draw calls. On Adreno 740 (Quest 3), the comfortable ceiling is 100–150 draw calls per eye with static batches. Without batching, 300 objects in a scene easily produce 300+ draw calls and drop the frame. The specification prescribes batching rules: which objects go into Static Batching, which into GPU Instancing, which require manual Mesh Combining.

Texture budget. VRAM on Quest 3 is shared with RAM. Standard: no more than 512 MB for scene textures. For VR on mobile, the only sensible format is ASTC (Adaptive Scalable Texture Compression): ASTC 6×6 for diffuse/albedo, ASTC 8×8 for roughness/metallic-packed maps. PNG or uncompressed RGBA in the build is an immediate red flag during audit. ASTC is 4x better than RGBA in memory usage — critical for VR with limited VRAM.

Polygon budget. For a scene in general — usually no more than 200–300k triangles for comfortable rendering. But distribution matters more: foreground character up to 15k, background NPCs 3–5k, environmental props from 50 to 2000 depending on size and position.

Shaders. For mobile VR, the only reasonable choice is URP Lit or a custom shader based on URP. HDRP does not work on Quest. Every custom shader must be profiled: how many instructions, whether discard is used in the fragment stage (kills early-z), whether there are dependent texture samples. URP is 2–3 times better than HDRP on mobile VR. Shaders with more than 50 instructions or using discard cause GPU-bound bottlenecks.

What tools are used for performance auditing?

To measure target metrics, we use Snapdragon Profiler and OVR Metrics Tool. RenderDoc allows step-by-step frame inspection, and Unity Profiler provides an overall CPU/GPU load picture. These tools are the standard set for any VR optimization engineer.

Texture Format Comparison — Specification Development

Specification Deliverables

• Budget table by category (draw call limit, poly count, texture memory, shader complexity)
• Naming and grouping rules for batching
• Checklist for each asset type: character, environment, prop, UI
• Unity Quality Settings (shadow distance, shadow cascades = 1 or off, pixel light count, anti-aliasing — MSAA 2x or 4x, Fixed Foveated Rendering level)
• LOD requirements: at least 3 levels for large objects, switch distances
• Occlusion Culling rules: marking Static/Dynamic occluders
• Example compliant scene that meets all constraints
• Multi-View rendering specification with exceptions for shaders and components

Commercial Deliverables

Our specification package includes:

• Documentation: a detailed PDF with all constraints, rules, and examples.
• Access to the example Unity scene that fully complies with the specification.
• Training: a 1-hour online session for your team explaining how to use the specification.
• Support: 2 weeks of email support after delivery for any questions.

What are common mistakes in VR optimization?

Novices often forget to enable Multi-View, use HDRP instead of URP, or fail to check texture format — all of which are immediately identified during audit. Our specifications eliminate these errors at the design stage.

Specification Development Process

1. Platform audit. Determine headset, SDK (Meta OpenXR SDK, OpenXR via Unity XR Plugin Management), target frame rate, content type (action with many objects vs. narrative with few).
2. Asset analysis. If the project is in progress — audit existing models, textures, shaders. For a new project — derive constraints from scratch based on typical scenarios.
3. Verification. Build a test scene, measure metrics, adjust limits.
4. Delivery. Hand over the final document with an example scene and checklist. The team gets a reference for all asset reviews.

Timeline: 3–7 working days for a new specification; 1–3 days for auditing and adapting an existing one. Cost is calculated individually — contact us for a preliminary estimate. Order a specification development, and your team will get clear numerical targets for stable FPS.

Trust and Experience

With 5+ years on the market and 50+ completed projects, our team has proven expertise in mobile VR optimization. We guarantee that our specifications are based on real measurements and will work immediately. We’ve helped top VR studios reduce rework by 40% and saved clients an average of $8,000 per project. Our experiences ensure your project avoids costly rework and delivers a smooth VR experience.

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.