Best RTX 5090 VR settings for MSFS 2024, with clear starting values for DLSS, TAA, resolution, LOD, traffic and motion reprojection.
For Microsoft Flight Simulator 2024 VR on an RTX 5090, start with headset/OpenXR resolution at 100%, DLSS Quality, High clouds, Ultra textures, Terrain LOD 150–200, Object LOD 150, moderate traffic and motion reprojection off. Choose TAA at 100% instead when cockpit text matters more than maximum frame-rate headroom.
The RTX 5090 has ample GPU performance and VRAM, but MSFS 2024 can still be limited by the CPU, traffic simulation, scenery streaming or an extremely high-resolution headset. Treat this as a strong baseline rather than an instruction to set every option to Ultra.
Recommended MSFS 2024 RTX 5090 VR settings
These settings balance cockpit clarity, scenery quality and consistent frame times across most modern VR headsets.
| Setting | Recommended starting point | When to change it |
|---|---|---|
| Headset or OpenXR resolution | 100% or the runtime's recommended resolution | Raise it gradually only after confirming GPU headroom; do not supersample in several places at once |
| Headset refresh rate | 80 or 90 Hz where supported | Use 72 Hz or the nearest lower supported rate for demanding airliners, large hubs or very high-resolution headsets |
| Anti-aliasing | DLSS Quality | Use TAA with 100% render scaling for sharper instruments; use DLSS Balanced only when genuinely GPU-limited |
| Terrain Level of Detail | 150–200 | Reduce to 100–150 when the main thread struggles at large airports |
| Objects Level of Detail | 150 | Lower before reducing texture quality when dense scenery causes CPU-limited stutter |
| Texture Resolution | Ultra | Reduce only if VRAM use, add-on scenery or unusually high headset scaling causes instability |
| Anisotropic Filtering | 16x | Leave enabled; its cost is small on this GPU |
| Off-screen Terrain Pre-caching | Ultra | Lower only when troubleshooting memory pressure; Ultra helps prevent scenery appearing during head movement |
| Volumetric Clouds | High | Try Ultra only with spare GPU frame time; High is the better VR trade-off in poor weather |
| Buildings, Trees, Grass and Bushes | High | Reduce vegetation first when flying low over dense photogrammetry |
| Shadow Maps and Contact Shadows | High | Use Medium if the GPU frame time rises sharply inside complex cockpits |
| Ray-traced Shadows | Off | The extra cost is difficult to justify in VR, even on an RTX 5090 |
| Ambient Occlusion | High | Reduce to Medium if looking around the cockpit produces GPU spikes |
| Cubemap Reflections | Medium | Raise to High only after clouds, resolution and frame timing are stable |
| Water Waves and Windshield Effects | High | Medium is sufficient when recovering performance in storms or over water |
| Glass Cockpit Refresh Rate | High | Use Medium in avionics-heavy airliners when limited by the main thread |
| Aircraft, road and airport traffic | Low to moderate | Traffic is often CPU-limited; reduce it before sacrificing image resolution |
| Motion Blur | Off | Leave it off in VR |
| V-Sync | Off | Let the headset runtime control display timing |
| NVIDIA Reflex | On, if offered in the VR profile | Use the normal On mode before trying any boost option |
| Frame Generation | Off or unavailable in VR | Desktop Multi Frame Generation results do not represent VR performance |
| Motion reprojection | Off initially | Enable a stable half-rate mode if native refresh cannot be maintained |
Headset runtimes do not all define 100% resolution identically, so copying another user's pixel dimensions can produce very different results. Our headset resolution and OpenXR baseline explains the settings that sit outside the simulator.
Should you use DLSS Quality or TAA in VR?
Use DLSS Quality for the best overall balance, but switch to TAA at 100% when small glass-cockpit text and distant runway markings need to look as crisp as possible.
- DLSS Quality: Best starting option for high-resolution headsets, weather-heavy flying and complex airliners. It creates useful GPU headroom but can soften displays or leave trails behind moving objects.
- TAA at 100%: Usually produces clearer avionics and fewer reconstruction artefacts, although it demands more raw rendering performance.
- DLSS Balanced: Reserve it for exceptionally high headset resolutions or situations where Quality cannot meet the required frame time.
- DLSS Performance: Generally too soft for cockpit use and should be a last resort rather than an RTX 5090 default.
- DLAA: If available, it offers high-quality native-resolution antialiasing but no upscaling headroom. Use it only after the simulator is already holding the desired refresh target.
Do not combine aggressive headset supersampling with TAA render scaling above 100%. That renders far more pixels than expected and can make even an RTX 5090 appear inadequate. If DLSS produces smearing around displays, propellers or airframe edges, use our targeted VR ghosting, flicker and freeze fixes before dropping every graphics setting.
Should motion reprojection be enabled?
Leave motion reprojection off when MSFS 2024 can sustain the headset's native refresh rate; otherwise, use a stable half-rate target rather than allowing frame rate to fluctuate constantly.
- At 90 Hz, a consistent 45 frames per second with reprojection can feel better than movement between 55 and 80 frames per second.
- At 80 Hz, the equivalent half-rate target is 40 frames per second.
- Automatic modes can work well, but repeated switching between native and reprojected output may cause visible judder.
- Reprojection can distort propellers, wing edges and moving glass-cockpit symbology. TAA often behaves better than DLSS when these artefacts are prominent.
Set the reprojection mode through the headset software or active OpenXR runtime, not through in-game V-Sync. The names vary between headset platforms, but the principle is the same: hold one repeatable timing target.
Why can MSFS 2024 still stutter on an RTX 5090?
An RTX 5090 cannot eliminate stutter caused by the main thread, traffic, scenery compilation, data streaming or an overloaded headset runtime.
- Start from one repeatable test. Use the same aircraft, airport, weather and camera position after every change.
- Check the limiting component. If the GPU is limiting performance, reduce headset resolution, switch from TAA to DLSS Quality, or lower clouds and shadows.
- Fix a main-thread limit separately. Reduce aircraft traffic, airport activity, Terrain LOD, Objects LOD and glass-cockpit refresh rate. Lowering textures will rarely cure a CPU bottleneck.
- Test without reprojection. Establish the simulator's true frame time before choosing native refresh or a fixed half-rate mode.
- Add complexity gradually. Reintroduce live traffic, demanding weather and scenery add-ons one at a time.
Our CPU-versus-GPU VR tuning process shows how to interpret frame times instead of guessing from average FPS.
What common RTX 5090 VR mistakes should you avoid?
The most common mistake is increasing every setting because the graphics card is powerful, then overlooking the CPU-bound options that actually cause the poor frame pacing.
- Do not run maximum scaling in both places. Choose the headset runtime as the primary resolution control, then use DLSS mode or TAA render scaling inside MSFS 2024.
- Do not set Terrain LOD to the maximum automatically. Dense airports, traffic and complex avionics can become main-thread limited long before the RTX 5090 reaches full load.
- Do not tune only over empty countryside. A preset that is smooth in a light aircraft may fail at a detailed hub in an airliner.
- Do not alter the flat-screen profile by mistake. Confirm that changes are being made to the simulator's VR graphics settings.
- Do not force driver antialiasing or V-Sync. Leave those application-controlled and use a clean per-program profile; our recommended NVIDIA profile and override guidance covers the few settings that are useful.
- Do not judge VR by desktop Frame Generation figures. Generated desktop frames do not solve headset tracking latency or VR frame-time requirements.
These starting values assume a desktop RTX 5090 paired with a suitably fast processor. An RTX 5090 laptop GPU has different power and thermal limits, so begin with lower LOD, High rather than Ultra secondary effects, and a conservative headset refresh rate.