Optimise HP Reverb G2 settings for MSFS 2024 with OpenXR scaling, TAA or DLSS, reprojection, stutter fixes and vital Windows WMR caveats.
To optimise Microsoft Flight Simulator 2024 for an HP Reverb G2, first confirm Windows Mixed Reality still works, select its OpenXR runtime, then tune one resolution scaler rather than two. Start near 70–80% OpenXR resolution, use TAA or DLSS Quality, reduce terrain LOD and traffic, and prioritise stable frame timing over maximum detail.
Does the HP Reverb G2 still work with MSFS 2024?
The Reverb G2 can run Microsoft Flight Simulator 2024 on PC, but it depends on the legacy Windows Mixed Reality stack. Windows 11 version 24H2 removed WMR, and installing SteamVR does not replace the missing headset driver and compositor.
A retained WMR-capable Windows installation may continue to operate, although it becomes an increasingly awkward and unsupported configuration. Check our explanation of Reverb G2 and Windows Mixed Reality compatibility before changing Windows versions or reinstalling the simulator.
Connect the headset's DisplayPort lead directly to the discrete graphics card. Use a stable USB port without a passive extension, and try another motherboard port if the headset disconnects, displays error messages or loses audio.
Set the correct OpenXR runtime first
MSFS 2024 should use the Windows Mixed Reality OpenXR runtime directly for the Reverb G2. The Steam edition of the simulator does not require SteamVR to be the active OpenXR runtime.
- Start Windows Mixed Reality: verify that the headset image and tracking work before opening the simulator.
- Check the active runtime: use OpenXR Tools for Windows Mixed Reality to make the Microsoft WMR runtime active.
- Remove conflicting layers: temporarily disable third-party OpenXR overlays, API layers and performance tools while establishing a clean baseline.
- Start MSFS 2024 in 2D: load the flight first, then enter VR. This makes runtime failures easier to distinguish from simulator loading problems.
If the simulator opens in the wrong headset software or stays in a flat theatre view, follow our OpenXR runtime setup and conflict checks before adjusting graphics settings.
Recommended HP Reverb G2 settings for MSFS 2024
A balanced Reverb G2 profile preserves cockpit readability while reducing the settings that produce the worst frame-time spikes. Treat these values as a starting point, not a universal preset.
| Setting | Starting point | When to change it |
|---|---|---|
| Headset refresh rate | 90 Hz | Try 60 Hz only if you tolerate visible flicker and need a lower performance target. |
| OpenXR resolution | 70–80% | Raise in 5% steps when GPU headroom remains; lower it if GPU frame time is unstable. |
| In-sim render scale | 100 with TAA | Avoid reducing both this and OpenXR resolution at the same time. |
| Anti-aliasing | TAA | Use DLSS Quality on an RTX card when GPU-limited and willing to accept softer displays. |
| Terrain Level of Detail | 80–100 | Lower it for main-thread spikes over cities and large airports. |
| Objects Level of Detail | 80–100 | Reduce it when dense airport buildings and city objects cause stutter. |
| Volumetric clouds | High | Use Medium when bad weather makes GPU frame time jump. |
| Textures | High | Lower them if VRAM fills and head turns cause pauses or texture swapping. |
| Shadows, reflections and ambient occlusion | Low to Medium | Raise these only after resolution, clouds and LOD are stable. |
| Aircraft, airport, road and boat traffic | Low | Increase cautiously; traffic is often limited by the main thread rather than the GPU. |
| Motion blur and depth of field | Off | They add little in a headset and can reduce clarity. |
The G2's 100% OpenXR setting is demanding because the compositor renders an eye buffer that includes lens-distortion allowance; it is not simply driving two 2160-by-2160 images. Our broader MSFS 2024 VR tuning workflow explains how to identify CPU, GPU and VRAM limits without changing several settings at once.
Should I use TAA or DLSS with the Reverb G2?
Use TAA when cockpit instruments and distant scenery clarity matter most; choose DLSS Quality when the GPU cannot maintain the required frame time. DLSS Balanced and Performance recover more performance but usually make glass-cockpit text, power lines and distant buildings noticeably softer in the G2.
With TAA, keep the in-sim render scale at 100 and tune OpenXR resolution first. With DLSS Quality, start with OpenXR at a clear, usable resolution and let DLSS provide the main reduction in internal rendering load. Stacking low OpenXR resolution, reduced render scale and aggressive DLSS is a common cause of unreadable instruments.
Should motion reprojection be enabled?
Motion reprojection is useful when the system can hold a steady fraction of the Reverb G2's refresh rate, but unstable reprojection often looks worse than a lower fixed workload. At 90 Hz, a consistent 45-frame-per-second reprojection target is more practical than repeatedly moving between performance bands.
- Use automatic reprojection when performance stays close to its target across most of the flight.
- Disable it for comparison if propellers, wing edges or glass displays bend and wobble.
- Consider 60 Hz mode only if you are not sensitive to flicker; it lowers the native and half-rate targets.
- Reduce traffic and Terrain LOD first when reprojection disengages at busy airports, because that usually indicates a main-thread limit.
Do not judge performance from an empty rural runway alone. Test the same complex aircraft, airport, weather and viewing direction after every change.
Why does the Reverb G2 still stutter after lowering graphics?
Stutter that survives a large resolution reduction is usually caused by the main thread, tracking, VRAM pressure, streaming or a conflicting OpenXR layer rather than raw shader load. The behaviour of the image helps identify which problem you have.
- The whole cockpit moves while your head is still: clean the tracking cameras, provide even room lighting and remove reflective surfaces or bright lights from their view.
- Stutter appears only at large airports: lower Terrain LOD, Objects LOD and traffic rather than texture resolution.
- Pauses occur when turning your head: check VRAM use, reduce textures or scenery detail, and close GPU-accelerated background applications.
- Scenery arrives late or pauses vary by flight: investigate network and streamed-world-content performance before sacrificing image quality.
- Performance changed after installing a VR utility: disable its OpenXR API layer and retest with the plain WMR runtime.
Our guide to diagnosing MSFS 2024 VR jitter and stuttering separates tracking faults from CPU, GPU and reprojection problems.
Final tuning order
The fastest route to a clear, stable Reverb G2 image is to change settings in the order that matches their likely bottleneck.
- Confirm WMR and OpenXR operation.
- Set 90 Hz, TAA, 70–80% OpenXR resolution and low traffic.
- Test one demanding, repeatable flight.
- Lower Terrain LOD and traffic if main-thread limited.
- Lower clouds, shadows or OpenXR resolution if GPU-limited.
- Raise OpenXR resolution in small steps once frame timing is stable.
- Enable reprojection last and check for cockpit or propeller artefacts.
A stable 45 fps with clean reprojection generally feels better than settings that occasionally reach a higher rate but collapse during head movement, weather changes or an approach into a detailed airport.