VR Render Tuning for Different FOV: From Lenses to Performance

Adapting Game Graphics for Lenses with Different Field of View (FOV)

In our practice, the difference in lens FOV between VR headsets is one of the most common causes of complaints about image quality. Valve Index gives ~130° horizontally, Meta Quest 3 about 110°, Pico 4 — 105°, PSVR2 — 110°. The same scene looks different on them — not only due to the viewing angle, but also due to lens geometry, barrel/pincushion distortion, chromatic aberration, and sweet spot. Without adaptation, users see either blurry edges, artifacts, or constant discomfort. Additionally, different FOV affects performance: a wide angle requires rendering more pixels, which directly impacts the GPU budget. We solve this problem by configuring rendering for each device's specific optics.

We guarantee stable performance across all platforms thanks to years of experience: 5+ years adapting VR projects, over 20 successful releases. Instead of a universal setting for one headset, we create a configuration that accounts for the lens physics of each device — and saves up to 30% time on subsequent optimization.

Why FOV for VR Design Is Not Just a Number

A wide FOV (Index) lets you see peripherals — objects that on Quest 3 would be outside the field of view. If a scene is designed for Index FOV, on Quest 3 the player will turn their head more often to see what should be "on the periphery." The opposite: a scene designed for 105° — on Index, rendering artifacts (incomplete skybox, visible level boundaries) appear at the edges that were not visible on the target headset.

Specific case: a game interface with elements positioned 40° from center. On Quest 3 they are in good viewing zone. On Index — still in frame, but beyond the lens sweet spot, where image quality degrades due to distortion. The user sees blurry UI edges and thinks it's a bug. Solution: adaptive UI that moves closer to center when a wide-angle headset is detected.

How to Configure the Camera for Different FOVs

In Unity via OpenXR or OVR SDK, FOV is set automatically based on the headset configuration — manual adjustment is not needed and not recommended. According to the OpenXR specification, FOV is hardware-defined. But there are a few things to consider:

1. Near clip plane. The wider the FOV, the more critical the correct near clip plane. On Meta Quest, a value of 0.1 (10 cm) is standard. On headsets with smaller IPD (users with IPD <60 mm exist), objects may "pass through" the near clip when approaching the face. A value of 0.05 (5 cm) is a safer minimum for widely supported headsets.

2. Foveated rendering — rendering at lower resolution at the edges of the frame. On Quest 2/3, it's implemented via Fixed Foveated Rendering (FFR) levels 1–4. On PSVR2 and Meta Quest Pro — via Eye Tracked Foveated Rendering (ETFR). At high FOV (Index), FFR with the central zone set for standard Quest parameters will look different: with a wide FOV, the peripheral resolution reduction area falls into the zone that Index users see normally. FFR level configuration must account for target devices. Comparison: FFR level 3 gives up to 30% performance gain over level 1, while quality loss at edges is imperceptible. The choice of level depends on the available GPU budget: for mobile Snapdragon XR2 chips, level 3-4 is optimal; for discrete GPUs (Index), level 1-2.

3. Barrel distortion mesh. Each headset's compositor applies distortion correction to the final image. But if content with sharp geometric patterns (grids, stripes, clear straight lines) is rendered, on headsets with high lens distortion the edges of these patterns will appear curved. There is no software fix — it's lens physics. Design solution: avoid such patterns at the edges of the scene or use organic shapes.

How to Adapt Render Resolution for Different Headsets

Render scale is a critical parameter. Quest 3 recommends an eye render target of 1832×1920 pixels per eye. Index via SteamVR automatically computes a recommended resolution multiplier based on GPU and headset. With incorrect render scale: too low — blurry image, slipping text, blurred UI; too high — GPU can't cope, frame drops, reprojection.

In Unity through XR Management: XRSettings.eyeTextureResolutionScale — runtime scale changes. Recommended is a dynamic adapter that lowers scale when fps drops below 72/90/120 (depending on headset target rate). Dynamic render scale is 15-20% more stable than fixed in terms of standard deviation of frame time.

For multi-platform projects: a table of default render scales by platform, configurable via ScriptableObject and loaded at XR initialization.

What Is Included in Graphics Adaptation for FOV

The work is done turnkey and includes:

• Documentation of render configuration for each target headset.
• Recommendations for FFR/ETFR settings considering FOV and performance.
• Optimized render pipeline with dynamic render scale.
• Support during integration — we check builds on real devices.
• Team training — we transfer knowledge on adapting to new headsets.

Timeline: audit of an existing project for 2-3 headsets — 2-5 working days. Full implementation of multi-platform render configuration with dynamic scale — 1-2 weeks.

Cost is calculated individually after analyzing target platforms and the current state of the project's render configuration. We'll assess your project for free.

Contact us to evaluate your project. Order adaptation for your target headsets — we'll select the optimal rendering configuration and eliminate image problems on any devices.

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.