Fix MSFS 2024 blurry ground textures and tune Terrain LOD, texture resolution and VRAM use while protecting flight-simulator FPS.
Flight simulator scenery settings control terrain detail, ground-texture sharpness, building and vegetation density, draw distance, shadows, water and airport clutter. Raising them improves low-level realism, but can reduce FPS by increasing CPU work, GPU load, VRAM use and scenery-streaming demand. Lower the setting tied to the actual bottleneck.
The simulator scope here is General: these principles apply to Microsoft Flight Simulator, X-Plane, FSX, Prepar3D and similar simulators. We give extra attention to Microsoft Flight Simulator 2024 because its streamed scenery, Terrain Level of Detail and Texture Resolution controls are frequent sources of confusion.
What does each flight sim scenery setting change?
Each scenery control changes a different part of the image, so lowering the wrong one may harm graphics without improving frame times.
| Setting type | What it changes | Usual first pressure | Symptom when set too high |
|---|---|---|---|
| Terrain LOD, mesh detail or detail radius | Terrain shape and the distance over which finer ground data is used | CPU, RAM and scenery streaming | Main-thread slowdown, terrain transitions or stutters while moving |
| Objects LOD or object draw distance | How far buildings, trees and airport objects remain visible and detailed | CPU draw calls, then GPU load | Low FPS over cities and at detailed airports |
| Scenery complexity, autogen or world-object density | The number of buildings, vegetation and placed objects | CPU and GPU | Uneven frame times during approach or low-level flight |
| Texture Resolution | The maximum detail available from terrain, aircraft, building and airport textures | VRAM and memory bandwidth | Stutters, texture swapping or sudden loss of sharpness when memory is exhausted |
| Anisotropic filtering | Texture clarity when runways and ground surfaces are viewed at a shallow angle | GPU, usually with a modest cost on modern hardware | Runways look sharp nearby but blur rapidly into the distance when set too low |
| Shadows, reflections and water effects | Lighting depth, reflected scenery and water appearance | GPU | High GPU utilisation and a substantial FPS loss at high display resolutions |
| Grass, vegetation and airport clutter | Close-range detail around airports and during low flight | Mixed CPU and GPU load | Poor ground performance despite smooth cruise flight |
| Photogrammetry or streamed scenery | Real-world aerial imagery and three-dimensional urban data | Network, storage, CPU and VRAM | Late loading, soft ground imagery, “melted” buildings or intermittent stutters |
The labels and slider scales are not interchangeable. MSFS 2020 and 2024 use Terrain Level of Detail and Objects Level of Detail; FSX and Prepar3D expose controls such as Mesh Complexity, Scenery Complexity, Autogen Density and Texture Resolution; X-Plane uses its own world-object, vegetation and texture controls. The final part of a slider often adds a heavy workload for a small improvement visible only in particular conditions.
Why are MSFS 2024 ground textures blurry?
In MSFS 2024, blurry ground textures usually come from render scaling, texture filtering, VRAM pressure, scenery streaming or low-resolution source imagery—not simply from a low Terrain LOD value.
| What you see | Likely cause | What to check |
|---|---|---|
| The cockpit, menus and outside view all look soft | Output resolution, render scaling, anti-aliasing or temporal upscaling | Use the display's native resolution and check render scaling before changing scenery settings |
| Nearby ground is acceptable but runways blur at an angle | Low anisotropic filtering | Raise anisotropic filtering if GPU headroom permits |
| Ground starts blurry and becomes sharper after several seconds | Streaming, cache, storage or asset-loading delay | Check online data, bandwidth limits, cache operation and storage activity |
| Textures become soft after loading a large airport or turning the camera | VRAM pressure | Lower Texture Resolution or remove memory-heavy add-ons and retest |
| Distant terrain loses definition or changes visibly as you approach | Terrain LOD or terrain-data delivery | Raise Terrain LOD gradually, watching main-thread performance |
| Buildings appear suddenly but the ground remains sharp | Objects LOD | Increase Objects LOD if the CPU has enough headroom |
| Only one tile or airport remains blurry | Source imagery, an add-on or stale cached data | Compare another location and temporarily disable the affected package |
MSFS cannot invent detail missing from its aerial imagery or an add-on's texture files. If the same small area remains blurry after it has fully loaded while surrounding terrain is sharp, raising every global slider will waste performance. A confirmed stale cache can be cleared through the simulator's data controls, but doing so forces scenery to download again and may initially make loading slower.
Does Terrain Level of Detail make ground textures sharper?
Terrain Level of Detail can improve distant ground definition, terrain shape and the radius over which finer data is retained, but it is not a universal texture-sharpening control.
Raise MSFS 2024 Terrain LOD when hills, coastlines or distant terrain simplify too early, or when higher-detail ground data arrives noticeably late. Reduce it when frame times deteriorate while flying towards a city or when the simulator reports a main-thread limit. It will not fix a soft cockpit, low render scaling, poor anisotropic filtering or low-resolution source imagery.
Objects LOD is separate. It controls buildings, trees and placed objects rather than the underlying terrain, and it is often the more effective setting to reduce at a large airport.
What does Texture Resolution do, and what is the texture VRAM limit?
Texture Resolution caps the detail of loaded textures, while the VRAM limit is the graphics-memory budget shared by scenery, the aircraft, cockpit displays, airport assets and rendering buffers.
There is no universal texture VRAM limit or safe Texture Resolution setting. Available VRAM, output resolution, aircraft complexity and add-on airports all change the result. Higher display resolutions also consume more VRAM for rendering buffers even when Texture Resolution stays unchanged.
Once the working set exceeds the available budget, a PC may move assets through slower shared memory or repeatedly evict and reload textures. Typical signs are camera-turn stutters, textures that begin sharp and then soften, or a sudden performance collapse at a detailed hub. Lower Texture Resolution one step and repeat the same flight; reload or restart only if the simulator requests it.
Do not lower Texture Resolution merely because distant terrain lacks shape. That points to Terrain LOD or mesh data. Persistent blur confined to one scenery tile is more likely to be a source-data or package problem than a VRAM limit.
What are sensible MSFS 2024 graphics settings in 2026?
For Microsoft Flight Simulator 2024 under Sim Update 5 from April 2026, the best scenery settings still depend on whether the limiting resource is the CPU, GPU, VRAM or scenery connection; no single maximum-quality preset suits every route.
| Situation | Lower first | Try to preserve |
|---|---|---|
| Main-thread limited at a large airport | Objects LOD, world-object density, airport vehicles and traffic, then Terrain LOD | Texture Resolution unless VRAM is also full |
| GPU limited at high resolution | Scenery shadows, reflections, water effects and dense vegetation | Terrain detail if CPU headroom remains |
| VRAM exhausted after loading detailed scenery | Texture Resolution and high-resolution add-on content | Objects LOD if CPU performance is stable |
| Blurry scenery that sharpens late | Reduce streaming demand only after checking online data, cache and storage | Image resolution and filtering |
| Low-level VFR or helicopter flying | Reflections, shadows and non-essential airport clutter | Terrain LOD, Objects LOD and ground filtering |
| Airliner operations at major hubs | Objects LOD, traffic and airport clutter | Readable cockpit resolution and stable frame times |
Start with the simulator's hardware-appropriate preset rather than maximum settings, then adjust one category at a time. Our practical MSFS starting values for Terrain LOD, Objects LOD, textures and other graphics controls provide a baseline that can then be tuned for the aircraft and airports you use.
MSFS 2024 runs on PC, Xbox Series X|S and PlayStation 5/PS5 Pro. PC exposes the most granular graphics controls; console editions manage more of the scenery and memory budget automatically, so a missing PC slider cannot be unlocked through another menu. Guides mentioning PlayStation apply to MSFS 2024, not MSFS 2020, which remains a PC and Xbox release.
How can I identify the scenery setting limiting FPS?
Use a repeatable worst-case test and change one setting group at a time; otherwise several bottlenecks can hide one another.
- Choose a demanding test: use the same aircraft, airport, runway view, weather and time of day. A quiet rural cruise is not a useful test for hub performance.
- Allow scenery to load: wait for initial streaming and compilation activity to settle before recording the result.
- Establish a baseline: note FPS and frame-time behaviour while stationary, during taxi and after turning the camera towards the terminal or city.
- Test the CPU group: reduce Objects LOD, object density, traffic and airport clutter. A clear improvement points towards main-thread or draw-call pressure.
- Test the GPU group: reduce shadows, reflections and display resolution or render scaling. A clear improvement indicates GPU pressure.
- Test the memory group: reduce Texture Resolution and disable the most detailed scenery package. Improvement after a camera turn or airport load suggests VRAM pressure.
- Retest the route: check departure, approach and the busiest cockpit view. A setting that works only at altitude is not stable.
An FPS cap or vertical synchronisation can leave GPU utilisation below its maximum even when performance is healthy, so low GPU utilisation alone does not prove a CPU bottleneck. Where available, use the simulator's frame-time display and compare CPU and GPU frame times. Our systematic CPU, GPU, VRAM and streaming diagnosis method covers the wider performance checks without requiring every slider to be lowered.
Which scenery settings should I lower first?
Lower Objects LOD and object density first for a CPU-bound airport, shadows and reflections for a GPU limit, and Texture Resolution only when the evidence points to VRAM pressure.
- For busy airports: reduce object draw distance, airport clutter, vehicles and traffic before sacrificing nearby ground clarity.
- For city approaches: balance Terrain LOD against Objects LOD; very high values for both can overload the main thread.
- For low-level VFR: retain terrain, ground filtering and nearby objects, then save performance through shadows, reflections and non-essential traffic.
- For high-altitude IFR: lower distant object density and airport clutter because much of it is hidden by altitude, haze or the cockpit.
- For blurred streamed scenery: diagnose the connection, data settings and cache before cutting visual quality. Lowering settings cannot repair unavailable source data.
A mistake we see constantly is raising worldwide Terrain LOD to compensate for one bad airport or imagery tile. That slows every flight while leaving the defective source untouched.
Can SimScenery or another add-on scenery package cause blur or low FPS?
Yes. If the affected add-on is listed as SimScenery, treat it like any third-party airport, terrain mesh or photoreal package: it may supply its own textures, geometry and object density while still competing for the simulator's global CPU, GPU and memory budgets.
Test the same camera position with the package disabled through the simulator's normal content-management method. On an MSFS PC installation, this can also mean temporarily moving the suspect package out of the Community folder while the simulator is closed. Check for duplicate airports, overlapping terrain meshes and multiple packages covering the same area.
If disabling one package restores sharp textures or stable frame times, global settings are not the sole cause. Our explanation of how scenery add-ons increase CPU, GPU, memory and storage demands helps identify which part of the package is expensive. For imagery-specific differences, see how photoreal and default scenery use different source data; Texture Resolution cannot restore detail that the underlying package never contained.