Collect Logs

Gather diagnostic logs for Vrex support

When troubleshooting issues, our support team often needs log files. This guide shows you where to find them.

Windows Desktop Logs

Log File Locations

Vrex stores logs in your user profile:

%USERPROFILE%\AppData\LocalLow\Vrex\Vrex\

Key files:

FileContent
Player.logCurrent session log
Player-prev.logPrevious session log

Launcher logs:

%USERPROFILE%\AppData\Local\Programs\VrexLauncher2.0\Vrex_launcher.txt

Quick Access

  1. Press Win + R to open Run
  2. Paste: %USERPROFILE%\AppData\LocalLow\Vrex\Vrex\
  3. Press Enter

What to Send

For most issues, send:

  1. Player.log (current session)
  2. Player-prev.log (if the issue occurred in a previous session)
  3. Vrex_launcher.txt (if the launcher fails to start Vrex)

How to Collect

Method 1: File Explorer

  1. Navigate to the log folder (see paths above)
  2. Copy the relevant .log files
  3. Attach them to your support email

Method 2: PowerShell

Run this command to copy logs to your Desktop:

$logPath = "$env:USERPROFILE\AppData\LocalLow\Vrex\Vrex"
$dest = "$env:USERPROFILE\Desktop\vrex-logs"
New-Item -ItemType Directory -Force -Path $dest
Copy-Item "$logPath\Player*.log" -Destination $dest
Write-Host "Logs copied to: $dest"

VR Headset Logs

Meta Quest (Streaming)

When using Vrex via streaming, logs are on the streaming server, not the headset. The relevant logs are still the Windows logs from the cloud instance.

Contact support for streaming-specific diagnostics.

Meta Quest (Vrex Go)

For standalone Vrex Go:

  1. Connect your Quest to a PC via USB
  2. Enable developer mode on the headset
  3. Use adb logcat to capture logs
  4. Or contact support for remote diagnostics

What to Include in Your Support Request

When emailing logs to support@vrex.no, include:

  • Description of the issue
  • Steps to reproduce
  • When it started happening
  • Your Vrex version (shown in launcher)
  • Your organization/workspace name
  • Attached log files

Log Privacy

Logs may contain:

  • Your Windows username
  • File paths on your system
  • Project names and model identifiers
  • Network addresses

They do not contain passwords or model geometry.