Learn which scenery settings hit CPU, GPU, VRAM and streaming, what each changes visually, and which to lower first for smoother flight simulator FPS.
In flight simulators, scenery detail settings control terrain shape and sharpness, building and vegetation density, object draw distance, shadows, water and airport clutter. Raising them improves low-altitude realism, but can reduce FPS through extra CPU work, GPU load, VRAM use and scenery streaming; the exact bottleneck depends on the setting.
Across Microsoft Flight Simulator, X-Plane, FSX, Prepar3D and DCS, the labels differ but the workload is similar. Microsoft Flight Simulator uses controls such as Terrain Level of Detail and Objects Level of Detail, while FSX and Prepar3D expose Scenery Complexity, Autogen Density, Mesh Complexity and Texture Resolution. Our recommended starting points for MSFS scenery and graphics controls cover that simulator's specific sliders.
Console editions generally expose fewer controls, with some scenery budgets managed automatically. On PC, add-on airports and scenery can also exceed the performance cost implied by the global slider because their object density, textures and scripts vary considerably.
What does each scenery setting change?
Each scenery control affects a different part of the image, so lowering the wrong one can damage graphics quality without fixing the actual performance problem.
| Setting type | Visible effect | Usual first pressure | Typical symptom when set too high |
|---|---|---|---|
| Terrain mesh, Terrain LOD or detail radius | Shape and detail of hills, coastlines and distant ground | CPU, RAM and streaming; GPU and VRAM at extreme distances | Main-thread slowdown, delayed terrain loading or stutters while moving |
| Object LOD or draw distance | How far buildings, trees and airport objects remain detailed and visible | CPU draw calls, followed by GPU load | Low FPS in cities and large airports |
| Scenery complexity, autogen or world-object density | Number of buildings, vegetation and placed objects | CPU and GPU | Uneven frame times, especially close to the ground |
| Texture resolution and anisotropic filtering | Sharpness of terrain, buildings and runway surfaces | VRAM and memory bandwidth | Texture swapping, pauses or sudden blurring when memory is exhausted |
| Scenery shadows, reflections and water effects | Lighting depth, reflected scenery and water appearance | GPU | High GPU utilisation and a large FPS drop at higher resolutions |
| Grass, ground clutter and airport vehicles | Close-range detail around airports and at low altitude | Mixed CPU and GPU load | Poor performance on the ground despite smooth cruise flight |
| Photogrammetry or streamed scenery, where supported | Detailed real-world terrain and three-dimensional urban data | Network, storage, CPU and VRAM | Late loading, melted-looking structures or intermittent stutters |
Slider scales are not interchangeable between simulators. Doubling a displayed LOD value does not necessarily double the visible distance or performance cost, and the final part of a slider often produces the smallest visual improvement for the largest workload.
How can I tell which scenery setting is limiting performance?
The correct setting to lower depends on whether the simulator is limited by the CPU, GPU, VRAM or scenery delivery.
- CPU or main-thread limit: FPS falls sharply at complex airports or over dense cities, while the GPU is not consistently fully occupied. Reduce Object LOD, scenery complexity, autogen, airport vehicles and then Terrain LOD. MSFS 2024 users can follow our method for diagnosing and reducing a main-thread bottleneck.
- GPU limit: performance improves clearly when display resolution or render scaling is reduced. Lower scenery shadows, reflections, water effects, vegetation detail and other GPU-heavy effects before sacrificing terrain definition.
- VRAM limit: the simulator may run well until a detailed airport loads, then develop severe stutters or blurred textures. Lower texture resolution and memory-heavy scenery options, particularly with high-resolution add-ons.
- Streaming or storage limit: ground textures and buildings load late even though FPS may remain acceptable. Reduce the terrain radius or streamed-scenery demand and check that the simulator's data and cache features are operating normally.
A frame-rate cap or vertical synchronisation can hide performance gains, so do not use GPU utilisation alone as proof of a CPU bottleneck. Built-in frame-time displays are more useful where the simulator provides them.
Which scenery settings should I lower first?
Lower Object LOD or object density first for a CPU-bound busy airport, shadows and reflections for a GPU-bound system, and texture resolution only when VRAM is genuinely under pressure.
- Create a repeatable test: use the same aircraft, airport, weather, camera position and time of day. Test a demanding location rather than an empty rural area.
- Change one group at a time: adjust either LOD, object density, GPU effects or textures. Moving every slider together makes the result impossible to diagnose.
- For a CPU limit: reduce object draw distance and scenery density in small steps, then lower Terrain LOD if frame times remain poor.
- For a GPU limit: reduce scenery shadows, reflections, water and dense vegetation before lowering the resolution of every texture.
- For memory or streaming problems: reduce texture resolution, terrain radius and streamed detail. Allow scenery time to load before judging the result.
- Retest the worst case: check the cockpit view at a large airport, during approach and after changing camera direction. A setting that works only at altitude is not a stable configuration.
Protect the detail that matters for the type of flying. Low-level VFR and helicopter flying benefit strongly from terrain and object detail, so shadows and reflections are often better sacrifices. Airliner users should tune around dense hubs, where object density, airport clutter and traffic combine to create the hardest CPU load.
Maximum settings are not automatically the most realistic choice. Excessive autogen can look unnaturally dense, while a very high draw distance may consume substantial performance for objects hidden by haze or the cockpit. The practical target is the highest useful detail that remains smooth in demanding conditions.
Why is scenery blurry even with high detail settings?
Blurry scenery often comes from render scaling, texture resolution, filtering, VRAM pressure or streaming rather than from the scenery complexity slider.
- The entire image is soft: check render scaling, anti-aliasing or temporal upscaling rather than Terrain LOD.
- Nearby ground is sharp but distant surfaces blur: texture filtering, texture resolution or source imagery is the likely cause.
- Buildings suddenly appear: increase Object LOD or draw distance if performance allows.
- Ground starts blurred and sharpens later: investigate streaming, cache, storage speed or VRAM use.
- Hills and coastlines lack shape: terrain mesh quality or Terrain LOD is more relevant than texture resolution.
For Microsoft Flight Simulator, our breakdown of blurry textures, LOD and render scaling separates these commonly confused causes.
If only one airport or scenery tile looks wrong while other locations are sharp, suspect the scenery package, data source or an add-on conflict before raising global settings. A mistake we see constantly is using extreme worldwide LOD settings to compensate for one defective area, slowing every flight without repairing the underlying scenery.