Should you enable HAGS for Microsoft Flight Simulator VR? See when it helps, when it causes stutter, and how to run a reliable VR A/B test.
Enable Hardware-Accelerated GPU Scheduling (HAGS) for Microsoft Flight Simulator VR only after an A/B test. It can improve frame pacing on some modern Windows PCs and is needed by some flat-screen frame-generation modes, but it can also add stutter. For native VR rendering, there is no universally faster setting.
This applies to Microsoft Flight Simulator 2020 and 2024 on Windows. HAGS is an operating-system setting rather than an MSFS option, so it affects other GPU-accelerated applications as well. Console users do not have this Windows control.
Which HAGS setting should I use for MSFS VR?
For a fresh installation on a modern PC, we recommend starting with HAGS enabled and keeping it only if repeated VR tests are as smooth or smoother. Do not change a stable setup solely because another simmer reports a higher frame rate.
| Situation | Starting choice | Reason |
|---|---|---|
| Modern Windows PC with a supported GPU and stable driver | On, then test | HAGS may reduce some CPU scheduling overhead, but the result depends on the driver, headset runtime and workload. |
| VR is already smooth and reliable | Leave it unchanged | A theoretical improvement is not worth introducing new frame-pacing problems. |
| Periodic hitching, dropped compositor frames or crashes appeared after an update | Test off | HAGS can interact badly with particular driver, overlay or compositor combinations. |
| You use supported frame generation on the flat-screen render path | On if required | Some frame-generation modes require HAGS, but that does not prove it benefits native VR. |
Changing HAGS in Windows
HAGS is a global Windows setting and requires a restart before the comparison is reliable.
- Close MSFS and the headset software. Also close recording, monitoring and overlay applications so they do not distort the first test.
- Open Windows graphics settings. In Windows 11, the control is normally under
Settings > System > Display > Graphics > Change default graphics settings. Windows 10 places it in the Display graphics settings area. - Change Hardware-accelerated GPU scheduling. Turn it on or off without altering Variable Refresh Rate or other graphics controls.
- Restart the PC. Merely reopening Microsoft Flight Simulator is not enough for a clean HAGS comparison.
- Launch VR in the usual order. Use the same headset runtime, connection method and background applications for both tests.
There is no per-game HAGS switch for MSFS. Avoid registry workarounds if Windows does not expose the setting.
How should I test HAGS in Microsoft Flight Simulator VR?
A controlled comparison should measure headset smoothness and frame time, not just the frame-rate figure shown on the desktop mirror.
First establish a practical MSFS VR settings baseline. Changing HAGS while also adjusting render scale, OpenXR, clouds or traffic makes the result meaningless.
- Use a repeatable flight. Load the same aircraft, cockpit position, airport, weather, time and traffic conditions. A saved flight near a demanding airport is useful.
- Lock the VR variables. Keep headset refresh rate, OpenXR runtime, render scale, anti-aliasing or upscaling mode, motion reprojection and connection method unchanged.
- Let the scene settle. Loading, scenery streaming and the first cockpit view can create hitches unrelated to HAGS.
- Observe frame time and head movement. Where available, compare GPU time, main-thread time, missed compositor frames and reprojection stability. Slowly turn your head across the instrument panel and outside scenery.
- Repeat each state. Run several comparable passes with HAGS on, restart, then repeat with it off. One unusually smooth circuit is not evidence.
- Keep the reproducibly better state. Prefer steadier frame delivery and fewer visible hitches over a tiny increase in average FPS.
A mistake we see constantly is judging HAGS from one cockpit pan immediately after a reboot. VR exposes irregular frame delivery far more clearly than a desktop FPS counter does.
CPU, GPU and frame-generation limits
HAGS does not remove Microsoft Flight Simulator's main-thread, GPU or VRAM bottlenecks. It changes how Windows schedules supported GPU work; it does not create extra rendering capacity.
- Limited by MainThread: reduce terrain and object level of detail, AI traffic and other CPU-heavy activity. HAGS may make a small scheduling difference, but it will not cure a heavily constrained main thread.
- Limited by GPU: reduce the MSFS or OpenXR render scale, expensive cloud settings and other GPU-heavy options. Watch frame time rather than VRAM allocation alone.
- Near the VRAM limit: lower texture pressure or resolution. HAGS cannot compensate for exhausted video memory and the resulting data movement.
- Unstable reprojection: aim for a consistent native frame time beneath the compositor's chosen threshold. HAGS is not a replacement for OpenXR motion reprojection, ASW or an equivalent headset feature.
Is HAGS required for DLSS in VR?
No. DLSS Super Resolution and DLSS Frame Generation are separate features. DLSS upscaling in VR does not itself require HAGS; a supported frame-generation mode used on the flat-screen render path may require it.
Frame generation is also different from headset motion reprojection. A larger frame-rate number on the monitor does not establish that the headset is receiving smoother native VR frames.
When should I disable HAGS for MSFS VR?
Disable HAGS when the same repeatable test produces more hitching, missed compositor frames, black frames, display-driver resets or crashes with it enabled. Confirm the behaviour after a restart before blaming the setting.
If the desktop mirror looks smooth but the headset does not, check the VR path before changing MSFS repeatedly. Verifying the active OpenXR runtime and headset connection can expose a runtime mismatch that resembles a HAGS problem.
Quest headsets add USB or wireless transport, video encoding and compositor behaviour to the chain. Keep those variables fixed during the comparison, and separate Quest Link and compositor tuning from the HAGS test.
If both settings perform identically, leave HAGS in the state that keeps the rest of the PC stable. Enable it when another feature explicitly requires it; otherwise there is no MSFS VR penalty for choosing the demonstrably smoother state.
Missing HAGS setting
If Hardware-Accelerated GPU Scheduling is absent, Windows, the graphics driver or the GPU is not exposing the feature. Install an appropriate stable driver, apply supported Windows updates and restart before checking again.
If the switch remains unavailable, do not force it through the registry. Microsoft Flight Simulator VR works without HAGS, and conventional frame-time optimisation will matter far more than an unsupported scheduler override.