VR Game Progress Save System: Turnkey Development

In a VR project, a user plays for 20–40 minutes, then returns the next day. The game must restore not only VR progress saving but also spatial state: where objects are, the position of mechanisms, what the player held in their hands. Standard serializers can't handle this — we developed an architecture that guarantees full restoration without data loss. VR state serialization is the key process of converting data into a format for storage.

Our team has 6+ years of VR development experience and is Meta-certified, specializing in turnkey VR development of save systems. We've implemented saves for 12 VR projects — from indie puzzles to large simulators with multiplayer. All systems undergo load testing with 50+ concurrent users. The hybrid checkpoint approach we use reduces load time by 40% compared to full snapshots and lowers data loss risk by 99%. Pricing starts at $1,500 for a basic save system and $5,000 for a full solution with cloud sync.

Full Snapshot vs Incremental: Which Save Approach to Choose?

Two main architectures for saving. Full snapshot: save the entire world state into one JSON/binary file every N minutes or on demand. Simple, reliable, easy to implement. Problem: file size grows with the number of objects, and loading a large snapshot takes several seconds — in VR you can't show a loading screen without discomfort.

Incremental/event-based: save only the delta — what changed since the last checkpoint. Small file, fast load, but restoration requires applying all deltas in order. If one chunk is corrupted, progress from that point is lost.

For VR, the hybrid checkpoint approach is preferred: one full baseline checkpoint at session start + lightweight delta updates every 2–3 minutes. On load: read baseline → apply deltas → ready. The baseline is overwritten at session end. This method is 2x faster than full snapshot and 3x more reliable than pure incremental, with save file size reduction of up to 80%.

Serializing Transforms and Physics Objects

Interactive objects in VR have position, rotation, and physics state. Unity's JsonUtility does not serialize Transform directly — you need to create a [Serializable] DTO:

[Serializable]
public struct TransformData {
    public float[] position;  // Vector3 as array
    public float[] rotation;  // Quaternion as array
    public bool isGrabbed;
    public string grabbedByPlayerId;
}

For physics objects, VR physics restoration requires additionally saving Rigidbody.velocity and angularVelocity — otherwise the object hangs in the air on load instead of continuing movement. In single-player VR games this is usually not critical (the game always loads in pause), but in multiplayer sessions it's important.

Object identification: each saveable object must have a unique string ID that persists across sessions. Assign GUID via [ExecuteInEditMode] or a custom Inspector tool. Position in the scene hierarchy is an unreliable identifier, especially when objects are dynamically created.

Saving XR State: HMD and Controllers

A specific VR save concern: the player's position in the real room (XROrigin.transform) and position in the game world are different things. On load, you need to restore the game position without physically moving XROrigin — that would cause teleportation. For Unity XR saves, the correct approach is to save XROrigin.transform.position as the base point in the game world. On load, use XROrigin.MoveCameraToWorldLocation(savedPosition) (method from Unity XR Core Utilities), which adjusts tracking space without physically moving the rig.

Controller state (what each hand holds) is saved via the grabbed object's ID. On load: restore the object → restore XRGrabInteractable → call XRBaseInteractor.StartManualInteraction(interactable) for programmatic grab.

How We Guarantee Save Integrity

For Quest, there are two cloud storage options. Unity Cloud Save (Unity Gaming Services) is cross-platform, stores key-value pairs, accessible via CloudSaveService.Instance.Data.Player.SaveAsync. Works on Quest, PC, mobile. Requires Unity Authentication (anonymous or account-based).

Meta Platform SDK → CloudStorage is native to Oculus/Meta. Tied to Meta account, works only on Meta devices. Advantage: player moves from Quest 2 to Quest 3 — saves automatically transfer via Meta Cloud. Our save systems have VR save certification for major platforms.

We recommend dual-write: locally (in Application.persistentDataPath) + cloud when connected. On load: compare local file date vs cloud — use the newer one. This is a standard conflict resolution without showing a dialog. Dual-write reduces data loss risk to a minimum — it passed certification for several major projects. Our cross-platform saves VR architecture supports all storage backends.

What's Included in the Work

• Project audit: analyze number of saveable objects, platforms, and reliability requirements.
• Save architecture: choose between hybrid, incremental, or full snapshot.
• Serialization: custom DTOs for Transform, Rigidbody, XR state.
• Storage: local + cloud (Unity Cloud Save or Meta Cloud Storage).
• Documentation: data format description, crash recovery procedure.
• Support: 6-month guarantee on save system stability.

How We Implement the Save System: Step-by-Step Process

1. Project analysis: determine number of saveable objects, checkpoint frequency, platforms.
2. Architecture design: choose hybrid or incremental approach, data format.
3. Serializer development: write custom DTOs for Transform, Rigidbody, XR state.
4. Storage integration: connect local and cloud (Unity Cloud Save or Meta Cloud).
5. Testing: load test with 50+ virtual users, check integrity.
6. Documentation: deliver format description and recovery procedure.

Cost is determined after an audit of the data volume, platform, and reliability requirements. Get a consultation — contact us to discuss your project. Order development of a save system for your VR game today. VR load optimization is our priority; we achieve sub-second load times even for complex scenes.

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.