Enable Quad Views in MSFS 2024 VR: set OpenXR and eye tracking correctly, verify foveation, and fix blur, crashes or no performance gain.
To enable Quad Views in Microsoft Flight Simulator 2024 VR on PC, select a compatible OpenXR runtime, turn on and calibrate headset eye tracking, then install or enable a single compatible Quad Views OpenXR layer. Start the headset software before MSFS 2024 and enter VR normally; the simulator has no universal Quad Views switch.
What does Quad Views require in MSFS 2024?
Quad Views works only when the PC headset, its active OpenXR runtime and the rendering layer all support the same quad-view path. Eye tracking is required for dynamic, gaze-controlled foveation but not necessarily for a fixed central focus region.
The technique renders two detailed focus views and two lower-resolution context views, one pair for each eye. Reducing peripheral detail can lower GPU load while preserving sharp instruments where the user is looking.
| Mode | Requirement | Best use |
|---|---|---|
| Eye-tracked Quad Views | Compatible eye tracker, gaze data exposed through OpenXR and a supported Quad Views provider | Cockpit scanning and the best balance of clarity and GPU savings |
| Fixed Quad Views | A provider that supports a fixed focus region | Headsets without eye tracking or troubleshooting unstable gaze tracking |
| Standard stereo | Any supported VR headset | Fallback when the runtime cannot provide Quad Views |
An eye-tracked headset is not automatically compatible. If its gaze data is unavailable to the active OpenXR runtime, MSFS 2024 cannot use it for dynamic foveation. These instructions apply to PC; console VR paths do not use PC OpenXR API layers.
How do I set up Quad Views in MSFS 2024?
- Close MSFS and every VR application. OpenXR runtime and API-layer changes are normally detected only when a new VR session starts.
- Select the correct OpenXR runtime. Use the headset's native runtime when its Quad Views implementation requires that path. Use SteamVR only if the headset and Quad Views provider explicitly support it. Follow our steps for selecting and checking the active OpenXR runtime if more than one is installed.
- Enable and calibrate eye tracking. Perform calibration in the headset software, confirm that gaze tracking works there, and repeat calibration after changing the headset's physical position.
- Install or enable one Quad Views provider. This may be an option built into the headset runtime or a compatible OpenXR API layer such as Quad-Views-Foveated. It is not an MSFS Community-folder add-on. Quad-Views Companion is only a settings editor for the rendering layer; installing the companion application alone does not enable Quad Views.
- Disable competing foveation features for the first test. Do not run vendor fixed foveation, another Quad Views injector and similar OpenXR processing at the same time. Temporarily disable non-essential OpenXR overlays and OpenXR Toolkit features as well, then add them back individually after Quad Views works.
- Start the headset software, launch MSFS 2024 and enter VR. When the runtime and provider negotiate quad-view rendering correctly, it activates automatically. Our MSFS VR entry and recentering instructions cover the normal VR controls if the headset is not detected or the cockpit position is wrong.
- Test the default profile first. Avoid changing peripheral resolution, focus size, MSFS render scale and upscaling simultaneously. Establish that the standard configuration works before tuning one variable at a time.
How can I tell whether Quad Views is working?
The most reliable confirmation is the status or log produced by the Quad Views provider. It should report a quad-view session and, for dynamic mode, active gaze tracking rather than a fixed focus point or stereo fallback.
Visual inspection alone can be misleading. In eye-tracked mode the detailed region follows the eyes, so trying to look directly at its boundary makes the boundary move. Compare GPU frame time in the same aircraft, location, weather and view, first with Quad Views enabled and then disabled.
A performance increase is most likely when the flight is GPU-limited. Busy airports, high traffic and large terrain-detail settings can leave MSFS limited by the main thread, in which case reducing peripheral pixels will have little effect on the frame rate.
Which Quad Views settings should I adjust first?
Start with eye-tracking accuracy and focus-region size, then lower peripheral resolution gradually. Cockpit displays, small labels and scenery around the point of gaze should remain stable and readable.
- Blurry instruments under your gaze: recalibrate eye tracking and enlarge the focus region before increasing the whole VR render scale.
- Peripheral shimmering: raise peripheral resolution slightly or use a less aggressive peripheral multiplier.
- Little GPU improvement: reduce peripheral quality in small steps and check that an external runtime scale is not adding excessive supersampling.
- Sharp image but poor frame rate: check MSFS clouds, render scale and antialiasing. Terrain detail, object detail and traffic can remain CPU-bound regardless of Quad Views.
- Focus region lags behind your eyes: repeat eye calibration, improve tracking conditions or switch to fixed foveation or standard stereo.
Once Quad Views itself is stable, use our focused MSFS 2024 VR optimisation guidance to balance render scale, terrain detail, clouds and traffic without masking the benefit.
Why does Quad Views fail or make no difference?
The usual cause is a runtime mismatch rather than an MSFS graphics setting. A mistake we see constantly is changing the preferred OpenXR runtime while the simulator or a VR service is still running, so the old runtime remains active for that session.
- No Quad Views detected: restart every VR process, verify the active runtime and confirm that the chosen provider supports both MSFS 2024 and that runtime.
- Eye tracking works outside MSFS but not inside it: the active runtime may not be exposing gaze data, or the provider may have fallen back to fixed foveation.
- Black eye, doubled image or crash on entering VR: disable all optional OpenXR layers, overlays and duplicate foveation systems. Test standard stereo, then enable only the Quad Views provider.
- No measurable improvement: the flight may be CPU-limited, the focus area may be too large, or peripheral resolution may still be close to full resolution.
- Cockpit text becomes unstable: the peripheral reduction is too aggressive, gaze calibration is poor, or upscaling and foveation are combining to remove too much detail.
If MSFS also fails in ordinary stereo VR, work through our OpenXR and headset troubleshooting checklist before reinstalling the Quad Views layer.
How do I disable Quad Views safely?
Disable the provider in its runtime or configuration utility, or uninstall its OpenXR API layer, then restart the headset software and MSFS 2024. Do not delete unrelated files from the MSFS Community folder: Quad Views normally operates at the OpenXR level, outside the simulator's add-on system.