Session Capture records poses and inputs in VRS and allows automatic replay. Understand how to use the feature in regression and continuous integration.

Direct answer

Meta XR Simulator's Session Capture records head movements and user inputs to a VRS file and then plays back the same sequence. The September 3, 2026 documentation also describes automatic replay by persistent_data.json for standalone applications, with initial delay, termination at the end and output file. The feature improves repeatability in regression, but does not alone confirm that the interface responded correctly; the test needs to collect logs, images, or state assertions.

Replay turns gesture into fixture

A critical sequence can be recorded once and repeated after each build, reducing human variation in navigation and interaction testing.

Repeated entry is not verified result

The file reproduces poses and actions; approval depends on comparing expected status, messages, screenshots or telemetry.

Version and scenario must accompany the file

Layout or physics changes may render a recording invalid. Each fixture must register build, synthetic environment and device profile.

CI requires isolation and evidence

Automatic replay must terminate with clear code, preserve logs, and separate failure from actual regression infrastructure to avoid false alarms.

Nexus Reading

Recorded sessions create a practical QA foundation for VR. The biggest gain comes when each replay is linked to a requirement, verifiable evidence, and an update policy.

FAQ

What does the VRS file record?

The documentation describes the inputs given to the application, including head movement and controls used in the session.

Can the replay play automatically?

Yes, standalone applications can configure playback and termination via persistent_data.json.

Does it work in Unity's Play Mode?

The replay automation described by Meta works with standalone applications, not Play Mode.

Essential guides to delve deeper into the decision

Primary sources and references

This editorial analysis was produced by Nexus from the official sources below, consulted on September 20, 2026. The text is original and interprets practical implications for companies.

Date reported by main source: documentation updated on September 3, 2026.