Skip to main content

Known Issues

🟠 Varjo Base v4.4+ Overlay Issues​

  • Overlays may appear in the wrong location or be completely invisible.
  • Head-locked overlays (edit instructions) are not affected.
  • Workaround: If you experience this issue, downgrade to Varjo Base v4.3.

🔴 Somnium VR1 Not Supported​

  • Due to limitations in Somnium VR1's runtime, the headset is not compatible.
  • Attempting to use it may cause game crashes.
user report

According to a user report, Somnium VR1 works just fine on SteamVR

🟡 Pimax & AMD Graphics Card Issues​

  • Pimax headsets using AMD graphics cards may suffer from performance issues and flickering.
  • Possible workaround: Users may experience better performance when using SteamVR as their OpenXR runtime.

🔴 iRacing + Meta Quest: Overlays Hidden Behind Cockpit​

Since a recent iRacing season update, VR overlays may appear behind the cockpit geometry (dashboard, rollbars, etc.) on Meta Quest headsets running via Meta Link / Air Link. Overlays can only be placed very close to the driver or through windows, making them almost unusable.

Cause: This is a Meta Link runtime bug. Per the OpenXR specification, composition layers (overlays) must always be drawn on top of the game, regardless of depth. iRacing appears to have started submitting depth information to the runtime, and Meta Link incorrectly uses that depth data to occlude overlays behind the game geometry. iRacing itself is not at fault — it is conformant behavior that the runtime may use depth info, but Meta Link's handling of it is broken.

Workaround: Disable the OpenXR depth layer extension in iRacing:

  1. Close iRacing.
  2. Open the file rendererDX11OpenXR.ini in your iRacing config folder (typically Documents\iRacing\).
  3. Under the [OpenXR] section, set: 
    DepthLayerExtensionEnabled=0
  4. Save and restart iRacing.
note

Disabling this extension may slightly reduce reprojection / ASW quality, but it restores overlay visibility. The setting is OpenXR-only — if you use OpenVR in iRacing, this fix does not apply.

warning

A small number of users have reported a BSOD (IRQL_NOT_LESS_OR_EQUAL) when toggling this setting. This appears to be an unrelated GPU/driver issue. Make sure your GPU drivers are up to date before changing the setting.