Find the best FSX scenery settings for balanced visuals and FPS, with practical slider values plus fixes for stutters, missing objects and OOM errors.
For the best balance in FSX and FSX: Steam Edition, start with the level-of-detail radius towards Large, 70–100% mesh complexity, 10 m mesh resolution, 1 m texture resolution, Low 2.x water, Dense scenery, Normal-to-Dense autogen, ground shadows off, and medium-to-high special effects. Adjust autogen first when frame rate falls.
Recommended balanced FSX scenery settings
These settings provide a sensible starting point for default scenery and most add-ons without pushing every slider to its maximum.
| FSX setting | Balanced starting point | When to change it |
|---|---|---|
| Level-of-detail radius | Towards Large, within the menu range | Reduce it if terrain loading causes stutters or memory errors. |
| Mesh complexity | 70–100% | Use 100% for detailed terrain mesh if performance remains stable. |
| Mesh resolution | 10 m | Match the resolution specified by an installed terrain-mesh package. |
| Texture resolution | 1 m | Select a finer value only for photoreal scenery designed to use it. |
| Water effects | Low 2.x | Drop to a 1.x setting if reflective water noticeably reduces FPS. |
| Scenery complexity | Dense | Raise it when an add-on requires Very Dense or Extremely Dense to show every object. |
| Autogen density | Normal or Dense | Lower this first over large cities; raise it in rural areas if spare performance is available. |
| Ground scenery shadows | Off | Enable only if the visual improvement justifies the performance cost. |
| Special effects detail | Middle to high | Reduce it when smoke, spray or other effects cause local slowdowns. |
These are starting values rather than mandatory settings. Our detailed explanation of the FSX scenery sliders covers what each control changes if you need to fine-tune a particular area.
Which FSX scenery settings affect FPS most?
Autogen density is usually the first scenery control to reduce when FSX becomes CPU-limited over a city. It governs large numbers of generated buildings and trees, so moving from Dense to Normal can help without removing the hand-placed terminals and landmarks controlled by Scenery Complexity.
Water effects can also be expensive, particularly the 2.x modes with reflections. Scenery Complexity matters most around detailed airports and cities, while the level-of-detail radius, high-resolution ground textures and dense add-ons often show their cost as loading stutters or memory pressure rather than a simple reduction in average FPS.
If changing scenery sliders produces little improvement, AI traffic, complex aircraft, clouds or display settings may be the real bottleneck. Use our broader FSX performance troubleshooting order rather than reducing scenery quality blindly.
How should mesh and texture resolution be configured?
Set mesh and texture resolution according to the source scenery; selecting a finer value cannot create detail that the add-on does not contain.
Mesh resolution controls the smallest terrain grid FSX may display, while Mesh Complexity controls how much of that elevation data is retained. A 10 m mesh setting does not turn coarse default terrain into 10 m terrain, and setting 1 m for a 10 m mesh adds no genuine elevation detail.
Use the resolution recommended by the mesh developer, or the next finer menu value if there is no exact match. Our guide to matching terrain-mesh resolution and library priority explains the relationship in more detail.
Texture Resolution concerns ground imagery rather than terrain shape. Keep it at 1 m for general flying, then use the stated native resolution for photoreal scenery. Very fine imagery consumes more memory and increases loading work, so there is little reason to select the finest value globally when most of the route cannot use it.
How do I tune FSX scenery without chasing the wrong slider?
Use one repeatable test flight and change one group of settings at a time.
- Choose a demanding test location. Load the same aircraft, airport, weather, time and viewpoint for every comparison.
- Apply the balanced settings. Leave traffic and weather unchanged so they do not mask the effect of a scenery adjustment.
- Test autogen first. Fly over the busiest nearby city and compare Normal with Dense.
- Check the add-on airport. Adjust Scenery Complexity separately, watching for missing terminals, vehicles, vegetation or other placed objects.
- Test terrain loading. Fly fast enough to cross several scenery tiles. Reduce the level-of-detail radius or texture resolution if pauses appear as new terrain loads.
- Run a complete flight. A short airport test may look smooth but will not expose the memory pressure accumulated along a long route.
A mistake we see constantly is changing autogen, traffic, clouds, water and aircraft simultaneously. That may improve performance, but it gives no indication which setting solved the problem or which visual feature can safely be restored.
Why do scenery objects disappear at lower settings?
Scenery Complexity can deliberately hide objects whose developers assigned them to higher detail levels.
If an add-on airport loses terminals, hangars or smaller decorations, raise Scenery Complexity one step and reload the area. Some packages require Very Dense or Extremely Dense for their complete object set; in that case, retain the required complexity and recover performance by reducing autogen instead.
If objects remain missing at the maximum setting, the cause is probably outside the scenery sliders. Check that the add-on is enabled, its library files are present and its scenery-library position is correct.
How do I prevent scenery stutters and OOM errors?
Reduce the level-of-detail radius, ground texture resolution and overall scenery density when terrain loading causes persistent stutters or an Out of memory error.
Both boxed FSX and FSX: Steam Edition remain 32-bit applications. Detailed airports, high-resolution photoreal scenery, aircraft textures and AI can therefore exhaust FSX’s limited virtual address space even when the computer still has free physical RAM.
Avoid forcing the level-of-detail radius beyond the simulator menu’s normal maximum through fsx.cfg. That popular tweak can increase distant detail, but it also loads more terrain and often makes long-flight stutters and memory failures worse. Use the menu settings first, keep a backup before editing the configuration file, and relaunch FSX after a memory failure before testing again.