Modular VR Game Architecture: Design for Performance & Scalability

In our practice, a VR game built without a well-thought-out architecture turns into an untouched minefield by the third month of development. Every class knows about every other class: XR Origin directly calls GameManager, which pokes AudioManager, which for some reason holds a reference to the Player — and when you try to add support for a second platform, the whole construct requires a complete rewrite. Our 10 years of experience in game development show that proper architecture pays off already during porting or adding new mechanics.

VR adds specific architectural challenges beyond the ordinary: multiple input sources (left controller, right controller, hand tracking, gaze), platform-dependent APIs (OpenXR vs OVR vs SteamVR), strict framerate requirements (90 fps — 11 ms budget), and the need to isolate platform code from game logic.

Why Input Abstraction Is Critical for VR

The first and most important architectural decision is abstraction over XR input. If game logic directly uses OVRInput.Get(OVRInput.Button.PrimaryIndexTrigger), porting to another platform requires changing every place that handles input. The correct approach: input abstraction layer — an interface IXRInputProvider with methods like GetGripAxis(), GetTriggerAxis(), GetPrimary2DAxis(), and separate implementations per platform/SDK. Game logic only knows about the interface. In Unity, this is natively supported via OpenXR + Input System: InputActionAsset with bindings for different devices, InputAction with callbacks. One InputActionAsset with two binding paths (<XRController>{LeftHand}/trigger and <OculusTouchController>/trigger) works on any OpenXR-compatible platform without extra code.

The Interaction System is the second key layer. XR Interaction Toolkit provides IXRInteractable and IXRInteractor interfaces, but for complex projects it’s not enough. You need a custom event system: InteractionEventBus with typed events (GrabStarted, GrabEnded, HoverEntered, ActivatePerformed) and subscription without direct dependencies between objects.

A State Machine for player state is mandatory in VR due to specific states: Grounded, Teleporting, InMenu, GrabbingObject, UsingTool. Without an explicit state machine, these states scatter across bool flags in different components and start conflicting.

How to Design a Modular Architecture for Multi-Platform Support

Follow these steps to design a modular architecture for a Unity VR project:

1. Core — platform-independent interfaces: IXRInputProvider, ILocomotionController, IHapticController, IHandTrackingProvider. No dependencies on Unity-specific or XR-specific classes, only C# interfaces.
2. Platform — implementations of Core interfaces: OculusInputProvider, OpenXRInputProvider, SteamVRInputProvider. Platform code is concentrated here and only here. A Bootstrap component at scene start detects the active platform and registers the needed implementations via Dependency Injection (Zenject or custom IoC container).
3. XR — interaction logic: XRInteractionManager, HandPresenceController, GrabSystem, LocomotionSystem. Works through Core interfaces, knows nothing about specific platforms.
4. Gameplay — game logic: mechanics, progression, AI, saves. Works through events from the XR layer, does not know about XR directly.
5. UI — all game interfaces via World Space Canvas + UGUI or custom spatial UI. Does not access Gameplay directly — only through events or the ViewModel pattern.

This separation allows testing Gameplay logic with Unity Test Framework without starting an XR session — using mock implementations of Core interfaces.

public interface IXRInputProvider
{
    float GetTriggerAxis(XRHand hand);
    Vector2 GetPrimary2DAxis(XRHand hand);
    bool GetGripPressed(XRHand hand);
    event Action<XRHand> OnTriggerPressed;
    event Action<XRHand> OnTriggerReleased;
}

Performance as an Architectural Constraint

In VR, every architectural decision is evaluated through the lens of performance. 90 fps means an 11 ms frame budget. Patterns that are painless in regular games kill framerate in VR:

• FindObjectOfType<T>() in Update — full scene scan every frame. In a VR scene with 500+ objects, that’s easily 2–3 ms. Using cached references instead is 200x faster.
• C# allocations in hot path — GC pauses are physically noticeable in VR because a dropped frame is not just “stuttering”; it triggers motion sickness instantly. In Update/FixedUpdate — zero allocations, everything via object pool and struct-based events. Object pooling reduces GC pauses by 80%.
• Synchronous operations on the main thread — resource loading, network requests. In VR everything is async: AddressableAssets.LoadAssetAsync, async/await with correct synchronization context.

Job System and DOTS for VR projects with many physics objects or NPCs are not just an optimization — they are an architectural requirement. IJobParallelFor for calculations that can be vectorized (collision checks, proximity queries for grab system) offloads the main thread by 30–50% in typical scenarios — 2–3 times more efficient than the classic approach.

What Our VR Game Architecture Design Service Includes

We deliver a comprehensive set of deliverables to guarantee quality at every stage:

• Documentation: architectural diagrams (UML), module descriptions, interfaces, and dependencies.
• Proof-of-concept: implementation of critical modules (e.g., input abstraction or interaction system).
• Performance report: profiling results, budget analysis, and optimization recommendations.
• Integration support: assistance during integration and code review of your team.
• Training session: a 1-hour session to familiarize your team with the architecture.
• Repository access: full access to the project repository with GitHub integration.

OpenXR guarantees compatibility. We assess your project in 1–2 days — contact us to discuss the details. Our architecture design starts at $2,500 for a single-platform MVP — a proven approach that saves up to $10,000 in porting costs for multi-platform projects.

Estimated Timelines for Architecture Design

Design includes documentation, dependency diagrams, and proof-of-concept implementation of critical modules. Pricing is determined after analysis of requirements and target platforms.

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.