RaceLab in VR – overview
RaceLab VR lets you bring your favourite overlays directly into the headset so you can see
timing, fuel, gaps and inputs while staying fully immersed in the car. VR support is part of
RaceLab Pro and requires the separate RaceLabVR installer in
addition to the main RaceLab app.[1]
This page explains what you need, which sims and VR APIs are supported, and the basic workflow
for running RaceLab in VR safely and smoothly.
Example: RaceLab timing and relative overlays in a VR cockpit.
What you need before starting
To use RaceLab in VR you must have:
- An active RaceLab Pro subscription (VR is not available on the free tier).[1]
- The normal RaceLab app installed and logged in.
- The separate RaceLabVR v3 component installed on the same PC.[1]
- A compatible VR runtime: OpenXR (recommended) or OpenVR / SteamVR on supported sims.[1]
- A supported sim (for example iRacing, ACC, AMS2, rFactor 2, F1 2024, Le Mans Ultimate).[2]
OpenXR is the modern cross-platform VR standard used by most current headsets and runtimes,
and it is the preferred option for RaceLab VR where available.[4]
Supported sims and VR runtimes (summary)
RaceLabVR v3 supports multiple sims and VR APIs. The table below is a simplified version of
the official compatibility matrix; always check the Garage documentation for the latest details.[2]
| Sim |
OpenXR |
OpenVR / SteamVR |
Notes |
| iRacing |
✅ Recommended |
✅ Supported |
Native OpenXR works very well with RaceLab VR.[2] |
| Le Mans Ultimate |
✅ via built-in OpenComposite |
✅ Supported |
Game always uses its built-in OpenComposite layer.[2] |
| F1 2024 |
➖ |
✅ OpenVR only |
OpenComposite is not compatible; use OpenVR.[2] |
| ACC / AC / rF2 |
✅ Supported |
✅ Supported |
Both OpenXR and OpenVR are available depending on your launcher and runtime.[2] |
| AMS2 |
⚠️ Limited |
⚠️ Issues with OpenComposite |
Known issues when using OpenComposite; SteamVR is strongly recommended.[2] |
This list is a simplified snapshot. Always confirm current support in the official Garage
compatibility docs before changing runtimes or tools.[2]
Basic RaceLab VR workflow
The exact steps vary slightly between sims, but the overall workflow is similar:
-
Install and update everything. Install the latest RaceLab app and the
RaceLabVR component, then sign in and let them update fully.[1]
-
Set your VR runtime. For most headsets, select OpenXR as your
active runtime where the sim supports it. On some titles (for example F1 2024) you must use
OpenVR / SteamVR instead.[2]
-
Start the sim in VR. Launch your sim in VR mode first, then join a test or
practice session.
-
Start RaceLab VR. Launch the RaceLabVR app and make sure it detects the sim.
On supported setups the overlays can now be enabled inside the headset without needing SteamVR
as a separate step.[3]
-
Create overlay sets. On the VR Settings page in RaceLab, create one or more
overlay sets (for example “Racing”, “Qualifying”, “Endurance”). Add the overlays you want to
see in VR and assign hotkeys to cycle sets.[3]
-
Re-center before editing. Always re-center your VR view in the sim before
moving or resizing overlays. This keeps your layout consistent between sessions.[3]
-
Use edit mode for fine positioning. Enter VR overlay edit mode (for example
using TAB or a bound key), then use the mouse to drag and resize overlays until they are
comfortable and readable.[3]
-
Save your layout. Once you are happy with the positions, save the overlay set
so it loads the same way next time.
Using VR overlays together with OpenKneeboard
Many sim racers combine RaceLab overlays with OpenKneeboard so they can also
see browser windows, notes or other tools inside the headset. OpenKneeboard is a free tool
that uses OpenXR or SteamVR to show a virtual “kneeboard” overlay in VR.[5]
This is especially useful if you want to keep an eye on Twitch chat, crew chief messages or
extra telemetry dashboards while driving. If you do this, keep an eye on overall performance
– every extra overlay or app in VR adds to GPU load.[5]
Comfort and performance tips
VR is far more demanding than a single monitor, so a few small changes can make a big difference:
-
Keep overlays simple. Use only the overlays you really need in VR. Turn off
extra widgets during races to reduce clutter and GPU load.
-
Use high-contrast colours. Make sure texts and backgrounds are easy to read
against the track and cockpit. Avoid tiny fonts or very thin lines.
-
Check your refresh rate. Run the headset at a refresh rate your GPU can
maintain consistently; smooth frame-times are more important than raw resolution.
-
Avoid running tools as Administrator unless needed. Keep RaceLab, VR tools
and your sim at the same privilege level to avoid hotkey and input problems.
If you experience stuttering or motion sickness, start by reducing the number of overlays and
lowering the sim’s graphics settings until the frame-rate is stable.
Sources & references
-
RaceLab Garage – VR Installation & Requirements (RacelabVR v3, Pro membership, supported APIs).
-
RaceLab Garage – VR Compatibility (supported games and VR runtimes, OpenXR / OpenVR / OpenComposite notes).
-
RaceLab Garage – VR Usage (overlay sets, positioning, key bindings and recentering advice).
-
Khronos Group – OpenXR 1.1 specification and overview (open standard VR/AR API).
-
OpenKneeboard – Getting started and VR usage with OpenXR and SteamVR.