Develop

Meta XR Simulator Logs

Updated: Sep 3, 2026

Overview

Meta XR Simulator writes diagnostic output on disk: a runtime event log, a crash dump, and the frontend logs that the simulator keeps for itself. The runtime event log also streams live into the Console tab while the simulator runs. Read the Console tab to watch activity as it happens. Collect the on-disk files when you need a complete record.
For an introduction to the simulator, see Meta XR Simulator.

Log locations (Windows)

Log typeLocation
Runtime event log (directory)
%AppData%\MetaXR\MetaXrSimulator\logs
Crash dump
%LocalAppData%\Oculus\MetaXRSimulator\crashes

Log locations (macOS)

Log typeLocation
Runtime event log (directory)
~/Library/Application Support/MetaXR/MetaXrSimulator/logs
Crash dump
~/Library/Logs/DiagnosticReports/Oculus/MetaXRSimulator

Log files and retention

The runtime writes one event log file per runtime process. Filenames follow this pattern:
meta_xrsim_<YYYY-MM-DD>_<pid>.log
<YYYY-MM-DD> is the date the process ran. <pid> is the process ID.
Each time the runtime starts, it deletes every file in the runtime log directory that matches meta_xrsim_*.log and is older than 7 days. The runtime does not rotate log files by size.

Console

The Console tab sits in the bottom tray. It streams runtime log entries while the simulator runs.
The entry table has three columns: Time, Service, and Message. Each severity filter carries a live count badge.
The Console holds 5000 entries in memory. When the buffer overflows, it halves.
Controls in the Console tab:
  • Pause log stream stops the live stream. The control then reads Start log stream, which resumes it.
  • Keyword search filters entries by text. The search activates at two or more characters.
  • Clear filters removes the active filters.
  • Reset logs empties the entry list.
  • Toggle detail panel opens and closes the detail panel.
  • Copy logs copies the buffered entries to the clipboard.
  • Download logs writes the buffered entries to a file.
Download logs opens a save dialog titled Save Console Logs. The default filename is console_logs_<timestamp> with the extension .log. Each line in the exported file has this format:
[HH:MM:SS] [LEVEL] [tag] message
When no runtime is connected, the Console tab displays this text: “To see your app logs here, enable the XR Simulator runtime toggle and press Play in your editor (Unity, Unreal, etc.).”

Collect logs for a bug report

Copy logs and Download logs export the Console in-memory buffer only, and they apply the active filters. Always attach the on-disk files.
  1. Reproduce the problem with the simulator runtime running.
  2. Open the runtime event log directory for your operating system, listed in the tables above.
  3. Collect every meta_xrsim_*.log file that covers the reproduction. Collect them before the next runtime start deletes the files older than 7 days.
  4. If the simulator crashed, collect the crash dump from the crash dump location for your operating system. The crash dump is a separate artifact from the runtime event log.
  5. Submit the runtime event logs through Report a bug, which attaches them for you. Add a Console export as extra context.
Report a bug cannot submit crash dumps. It offers only the log files it discovers, so keep the crash dump you collected in step 4 locally and provide it when someone investigating the report asks for it.

Report a bug

Use Report a bug to send a report with the log files attached for you.
  1. In the left nav, select Report a bug.
  2. Enter a Title and a Details description. Submit stays disabled until both fields hold text.
  3. Review the Include logs section. Every discovered log file is checked by default. Clear the checkbox next to any file you want to leave out.
  4. Keep personal information out of the Title and Details fields. The report attaches device and system details for you.
  5. Select Submit. The dialog closes and a notification reports Issue successfully reported.
By default the available attachments are the frontend logs, every *.log file in the runtime log directory, and the Unity Editor.log where one exists. Crash dumps are not offered.

Increase log verbosity

Runtime verbosity comes from the log_level key in the core configuration JSON file. The META_XRSIM_CONFIG_JSON environment variable points at that file. Set the variable in the shell you start the application or editor from, so the runtime inherits it:
Windows (Command Prompt)
set META_XRSIM_CONFIG_JSON=C:\path\to\your\config.json
macOS
export META_XRSIM_CONFIG_JSON=/path/to/your/config.json
Set log_level in that JSON file to one of these values:
  • none
  • error
  • warning
  • info
  • verbose
The shipped configuration leaves log_level unset. An unset key yields error, warning, and info entries. The Console tab has no verbosity setting.
Nav Logo
English (US)
© 2026 Meta