Virtual Reality (VR) Optimisation
Estimated Lesson Time: 60–75 Minutes
Lesson Overview
Throughout the Performance Academy, we’ve focused on extracting the maximum possible performance from Microsoft Flight Simulator through careful optimisation, benchmarking and understanding how the simulator uses your hardware.
This lesson takes everything you’ve learned and applies it to one of the most demanding ways to experience the simulator:
Virtual Reality.
Flying in VR is unlike anything possible on a traditional monitor.
Instead of viewing the simulator through a screen, you are placed directly inside the cockpit, allowing you to naturally judge height, distance, depth and spatial awareness.
For many simmers, VR is the closest experience to flying a real aircraft.
However, achieving smooth VR performance is significantly more challenging.
Unlike desktop flying, VR requires your computer to produce two high-resolution images—one for each eye—while maintaining extremely consistent frame timing. Even small performance fluctuations that might go unnoticed on a monitor can feel uncomfortable in VR.
This masterclass explains how VR works, why it is so demanding and how to optimise your hardware to create the smoothest possible experience.
Lesson Objectives
By the end of this lesson you will understand:
Why VR is significantly more demanding than desktop flying.
The different roles of the CPU and GPU in VR.
Motion Reprojection.
OpenXR.
SteamVR.
Meta/Oculus software.
Resolution scaling.
DLSS in VR.
Foveated Rendering.
VRAM requirements.
Refresh rates.
Headset optimisation.
Frame timing.
Common VR stutters.
Monitoring VR performance.
Recommended settings for different GPUs.
Motion sickness reduction techniques.
Why VR Is So Demanding
On a normal monitor your graphics card renders a single image every frame.
VR is completely different.
The simulator must render:
• One complete image for your left eye.
• One complete image for your right eye.
Each image is rendered from a slightly different viewpoint.
Your brain combines both images together to create realistic depth perception.
This instantly increases GPU workload.
Modern VR headsets also have extremely high display resolutions.
Many headsets exceed 4K total rendered resolution.
That means the GPU is processing millions more pixels every second than it would on a standard monitor.
This is why VR can require two to three times the graphics performance of desktop flying.
CPU vs GPU in VR
Both components become extremely important.
CPU Responsibilities
The CPU still performs exactly the same simulation calculations as desktop mode:
• Flight model
• Aircraft systems
• Glass cockpit refresh
• Terrain calculations
• AI traffic
• Ground vehicles
• Weather simulation
• Navigation systems
• Physics
If the CPU becomes overloaded, the headset cannot receive frames consistently.
This results in judder and poor smoothness.
GPU Responsibilities
The GPU renders:
• Two images every frame
• Cockpit textures
• Volumetric clouds
• Terrain
• Shadows
• Lighting
• Reflections
• Water
• Anti-aliasing
The GPU usually becomes the limiting component first in VR.
Motion Reprojection
One of the most important VR technologies.
Motion Reprojection attempts to create additional frames whenever your GPU cannot maintain the headset’s native refresh rate.
Example:
Headset:
90Hz
PC renders:
45 FPS
Motion Reprojection creates additional frames to maintain perceived smoothness.
Benefits:
• Smoother head movement
• Reduced judder
• Better immersion
Potential disadvantages:
• Distorted propellers
• Visual artefacts
• Ghosting around moving aircraft
• Slight increase in latency
Not every headset implements Motion Reprojection in exactly the same way, so results may vary.
OpenXR
OpenXR is the modern standard that allows Microsoft Flight Simulator to communicate with VR headsets through a common interface.
Benefits include:
• Better compatibility.
• Easier optimisation.
• More consistent updates.
Most modern VR users should ensure that OpenXR is configured correctly before attempting any simulator optimisation.
SteamVR
SteamVR acts as the runtime for many PC VR headsets.
It provides:
• Headset configuration
• Resolution adjustment
• Motion smoothing
• Performance overlays
• Controller management
SteamVR settings should complement your in-simulator settings rather than duplicate scaling unnecessarily.
Oculus / Meta Software
Meta Quest headsets use Meta Quest Link (formerly Oculus Link) software.
Within the Meta software you can adjust:
• Render resolution
• Refresh rate
• Link quality
• Runtime configuration
These settings directly influence GPU workload before the simulator even launches.
Resolution Scaling
Resolution scaling determines how many pixels are rendered internally before the final image reaches the headset.
Higher values provide:
• Sharper cockpit instruments
• Better distant scenery
• Clearer text
Lower values reduce GPU workload but also reduce image clarity.
Finding the right balance is essential.
DLSS in VR
DLSS works similarly in VR as it does on desktop.
The simulator renders internally at a lower resolution before AI reconstructs the final image.
Advantages:
• Higher performance
• Lower GPU workload
Potential disadvantages:
• Softer instruments
• Slight shimmering
• Reduced text clarity depending on the preset
Always compare image quality against performance rather than assuming one mode is universally best.
Foveated Rendering
Foveated Rendering reduces GPU workload by rendering the centre of your vision in high detail while reducing quality in your peripheral vision.
Benefits include:
• Improved FPS
• Reduced GPU usage
• Better frame timing
Support depends on your headset and software platform.
VRAM Requirements
VR uses considerably more VRAM than desktop mode because it renders:
• Two high-resolution images
• Larger textures
• Additional buffers
• More rendering data
Running out of VRAM may result in:
• Stuttering
• Texture pop-in
• Performance degradation
Monitor VRAM usage carefully when configuring VR settings.
Refresh Rates
Most headsets support multiple refresh rates.
Higher refresh rates improve motion clarity but require significantly more rendering performance.
Choose a refresh rate that your hardware can maintain consistently rather than simply selecting the highest available option.
Headset Optimisation
Before launching Microsoft Flight Simulator:
Ensure:
• Latest headset firmware.
• Latest graphics drivers.
• Correct OpenXR runtime.
• Appropriate refresh rate.
• Comfortable render resolution.
Small improvements outside the simulator often have a noticeable impact on the final VR experience.
Frame Timing
Unlike desktop gaming, average FPS is not the most important metric in VR.
Stable frame timing is critical.
Inconsistent frame delivery may cause:
• Judder
• Head movement stutter
• Motion sickness
Smooth frame delivery should always take priority over maximum FPS.
Common VR Stutters
Typical causes include:
• CPU bottlenecks
• GPU overload
• Running out of VRAM
• Heavy AI traffic
• Dense airports
• High Terrain LOD
• Excessive Object LOD
• Complex weather
• Background applications
Use the same benchmarking principles learned throughout the Performance Academy to isolate the true cause.
Monitoring VR Performance
Recommended tools include:
• OpenXR Toolkit (where supported)
• SteamVR Performance Graph
• MSI Afterburner
• HWiNFO
• NVIDIA App Overlay
Monitor:
• GPU utilisation
• VRAM usage
• CPU temperatures
• GPU temperatures
• Frame timing
• Reprojection status
Recommended Hardware Profiles
RTX 4070
Ideal for:
• Medium–High settings
• DLSS Quality
• Moderate Terrain LOD
• Balanced AI traffic
Prioritise stable frame timing over maximum visual settings.
RTX 4080
Allows:
• Higher render resolution
• Larger airports
• Higher texture quality
• Increased Terrain LOD
Continue monitoring VRAM usage during complex flights.
RTX 5080
Suitable for:
• High–Ultra settings
• Premium airports
• Advanced aircraft
• Dense photogrammetry
Maintain sensible AI traffic and LOD values to avoid unnecessary CPU bottlenecks.
RTX 5090
Offers the greatest performance headroom currently available.
Suitable for:
• Very high render resolutions
• Extensive photogrammetry
• Complex weather
• High-fidelity aircraft
Even with this level of hardware, CPU limitations can still occur at demanding airports.
AMD Equivalent Recommendations
Comparable AMD GPUs include:
• RX 7800 XT
• RX 7900 XT
• RX 7900 XTX
The same optimisation principles apply:
• Balance resolution.
• Monitor VRAM.
• Optimise CPU-heavy settings.
• Prioritise smooth frame timing.
Motion Sickness Considerations
Motion sickness affects users differently.
Common contributing factors include:
• Low frame rates
• Uneven frame pacing
• High latency
• Rapid head movement
• Long sessions without breaks
Reducing these issues often improves comfort significantly.
If you’re new to VR, begin with shorter flights and gradually increase session length as you become accustomed to the experience.
Common Mistakes
Using desktop graphics settings unchanged.
Chasing maximum FPS.
Ignoring frame timing.
Running excessive Terrain LOD.
Forgetting to monitor VRAM.
Using an unsuitable refresh rate
Ignoring CPU bottlenecks.
Student Exercise
If you own a VR headset:
Step 1
Create a dedicated VR graphics profile.
Record:
• Render resolution
• Refresh rate
• DLSS mode
• Terrain LOD
• Object LOD
• AI traffic
Step 2
Run your permanent benchmark flight.
Record:
• Average FPS
• Frame timing
• GPU utilisation
• VRAM usage
• CPU temperature
• GPU temperature
Step 3
Compare these results with your desktop profile.
Identify:
• Which settings required adjustment.
• Whether Motion Reprojection improved smoothness.
• Which component became the primary bottleneck.
• Which configuration offered the best balance between image quality, smoothness and comfort.
If you do not own a VR headset, review this lesson to understand how VR fundamentally changes optimisation priorities.
Student Checklist
Dedicated VR profile created (if applicable).
Headset software reviewed.
OpenXR or SteamVR configured.
Benchmark completed.
GPU and VRAM monitored.
Desktop and VR results compared.
Performance Profile updated.
Lesson Summary
Congratulations.
You have completed the optional Virtual Reality Optimisation Masterclass.
You now understand that VR optimisation is not simply about increasing FPS—it is about delivering a consistently smooth and comfortable experience. Stable frame timing, balanced graphics settings and careful monitoring of CPU, GPU and VRAM usage are far more important than pushing every option to its maximum.
The same optimisation principles you’ve learned throughout the Performance Academy still apply, but VR demands even greater attention to detail because the performance margin is much smaller.
Whether you fly occasionally in VR or spend every flight wearing a headset, you now have the knowledge to build a dedicated VR profile that matches your hardware and provides the best possible balance between realism, smoothness and immersion.
Knowledge Check
- Why is VR significantly more demanding than desktop mode?
- Which component typically becomes the primary bottleneck in VR?
- What is Motion Reprojection and when should it be used?
- Why is stable frame timing more important than peak FPS in VR?
- How does DLSS affect both image quality and performance in VR?
- What is Foveated Rendering and how can it improve efficiency?
- Why should VR graphics settings be configured separately from desktop settings?
- Based on your own testing, what changes produced the best balance between image quality, performance and comfort?