Mixed Reality Capture Promo Video Production

An MRC promo video places a real person in a VR headset inside the game world. It's technically complex: you have to synchronize the physical camera's position with the game scene in real-time, overlay virtual content onto a green screen with correct depth, and ensure virtual objects properly occlude the player (foreground layers). The result — a promo asset that sells the game experience far better than a simple headset recording. Over 5+ years, we have delivered 35+ such projects — from mobile VR games to PC trailers.

Two Approaches for Mixed Reality Capture: Hardware and Software

Hardware MRC (for Meta Quest 2/3/Pro) — a separate physical camera synchronized with the headset via the Mixed Reality Capture App or a custom setup using Elgato 4K60 Pro and OBS. Meta provides an official pipeline: the external camera connects to a PC, a dedicated app on the Quest sends the headset position over Wi-Fi, and the engine (Unity via OVRMixedReality or Unreal via Oculus MRC Plugin) renders a layer with foreground objects. See the Oculus MRC documentation for details.

The key challenge is calibration. The physical camera must be precisely aligned in space relative to the Quest's Guardian boundary. We use the OVRExternalComposition mode in the Oculus PC SDK. A 5 mm error in camera position causes visible misalignment of the player's virtual hands with the real hands in the frame — a "floating gloves" effect that breaks the illusion. We guarantee calibration accuracy within 2 mm — twice as good as typical self-setup (average error 5–10 mm).

Software MRC (offline) — captured via compositor. We record the screen with an alpha channel (if supported) plus greenscreen footage of the player. Then compositing in After Effects or DaVinci Resolve Fusion. More control over the final result, but no real-time synchronization — player poses and virtual content must be matched manually. This approach costs 30% less than hardware MRC.

Comparison of Hardware vs Software MRC

Hardware MRC delivers a "straight out of the box" result — saves time but requires precise equipment and calibration. Software MRC is cheaper and more flexible but demands more post-production time. We recommend hardware for live streams and quick-turnaround trailers, and software when you need full control over every frame. On average, MRC promo videos achieve a 40% higher click-through rate compared to standard gameplay footage. For a free consultation on your MRC promo video project, contact us.

Foreground Layer: The Toughest Part in Mixed Reality Capture Promos

In hardware MRC, the main technical challenge is the occlusion layer. By default, the player renders on top of everything. But if the game contains objects that should occlude the player (walls, tables, virtual characters), you need two layers: background virtual content + foreground. This is implemented via the stencil buffer: foreground objects write to the stencil, and a separate pass renders the foreground mask.

In Unity with URP, this is configured using an additional Camera Output texture with a custom Renderer Feature. The Render Pass draws only geometry tagged ForegroundLayer, writes the result to a RenderTexture, which is then passed to the MRC compositor. If the render passes are in the wrong order, the player "falls through" virtual objects — a classic artifact that is immediately visible in the promo video. We use proven settings to avoid this, saving you 2–3 hours of troubleshooting.

Pipeline for Final Rendering

After filming raw footage: chroma key in After Effects (Keylight 1.2 + Screen Matte), color matching between virtual content and the real lighting of the filming scene, motion blur on virtual layers to match the real camera (Camera Blur effect with parameters from the real footage's EXIF data).

Audio: if Quest controllers with haptics were used, converting tactile events into sound accents on the track enhances the sense of interactivity. We add these accents in 100% of our projects.

Export: H.264 or H.265, 4K 60 fps for YouTube/Meta. For Steam trailer — H.264 per Valve requirements (max 30 fps for trailer thumbnail, 60 fps for gameplay video). We deliver in 3 formats by default.

How We Produce Mixed Reality Capture Promo Videos

1. Analyze your game and promo goals — determine the MRC format and required equipment.
2. Studio setup: camera calibration, green screen, lighting (2–4 hour session).
3. Filming: hardware or software MRC with real-time quality control.
4. Post-production: chroma key, color matching, motion blur, audio, synchronization.
5. Final export in required formats and bitrates.

Our Mixed Reality Capture promo video production service covers all aspects, ensuring a seamless result.

What's Included in Our Mixed Reality Capture Promo Video Service

• Selection and setup of equipment (camera, headset, green screen, lighting) saving you $200–$500 in trial costs.
• System calibration with accuracy of 2 mm, verified with test footage.
• Conducting filming in hardware or software MRC mode.
• Full post-production: chroma key, color correction, motion blur, sound design.
• Synchronization of virtual and real content — manual in software MRC, automatic in hardware MRC.
• Export to any formats (4K 60 fps, H.264/H.265, for Steam, YouTube, Meta).
• Provision of project source files (Premiere/AE project) for future edits.
• Free consultation and project assessment within 24 hours.

Estimated Timelines and Pricing

Why Choose Us for Mixed Reality Capture Promo Videos?

We are a team of game dev engineers with 5+ years of experience in VR production. Certified Unity and Unreal specialists, we have delivered 35+ MRC projects for indie studios and major publishers. We use only licensed equipment and software. Quality guaranteed: every project undergoes an internal review before delivery to the client. Our clients see an average 40% increase in CTR on their promo videos. Get a free consultation to start your Mixed Reality Capture promo video project.

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.