Learn which FSX scenery add-ons reduce FPS, which settings matter most, and how to recover smooth performance without removing your scenery.
Yes. Scenery add-ons can reduce FPS in FSX and FSX: Steam Edition, especially at object-heavy airports or in dense autogen areas. Limit the hit by testing the scenery alone, lowering scenery complexity and autogen first, disabling optional traffic or object layers, and avoiding overlapping airport packages.
FSX often becomes limited by main-thread processing when it must draw large numbers of buildings, trees, lights, vehicles and animated objects. A scenery package's download size is therefore a poor guide to performance: a small but object-dense airport can cost more FPS than a large collection of replacement ground textures.
Which FSX scenery add-ons have the greatest FPS impact?
Detailed airports, city scenery and dense autogen usually have the largest effect, while mesh alone is generally less demanding.
| Scenery type | Typical impact | Main causes | Settings or options to check |
|---|---|---|---|
| Detailed airports | High but localised | Buildings, ground polygons, lighting, animated objects and nearby AI | Scenery Complexity, Airport Vehicle Density, AI traffic and Ground Scenery Shadows |
| City or regional autogen | Medium to high | Large numbers of trees, buildings and road vehicles | Autogen Density, Scenery Complexity and Road Vehicles |
| Photoreal scenery | Usually low to medium | Texture loading, very high-resolution imagery and optional autogen | Optional autogen layers and Texture Resolution |
| Terrain mesh and landclass | Usually low by itself | Fine terrain resolution or additional autogen generated by landclass | Mesh Resolution, Mesh Complexity and Autogen Density |
| Custom traffic and animations | Variable, sometimes high | Road traffic, boats, airport vehicles or bundled AI schedules | Traffic sliders and the package's optional components |
The effect is normally strongest near the add-on. FSX loads scenery by geographic area, so an elaborate airport may run smoothly in cruise and then reduce FPS during the approach. Global mesh, landclass and texture replacements have a wider reach, but each individual area may be relatively inexpensive.
How can I reduce scenery FPS loss without uninstalling it?
- Create a repeatable test. Save a flight at the affected location and keep the aircraft, cockpit view, weather, time and traffic unchanged. Cycle
Shift+Zuntil the frame-rate display appears, then allow the scenery to finish loading before comparing results. - Establish a baseline. Untick the suspect scenery area in the FSX Scenery Library, restart when requested and repeat the flight. If performance does not change, another add-on, traffic file or simulator setting is probably responsible.
- Check for overlapping airports. Keep only one detailed version of an airport active. A regional package, an older airport add-on and a separate airport-layout file can coexist even when the library priority looks correct, producing duplicate buildings, conflicting runways and unnecessary processing.
- Lower the expensive settings first. Reduce Road Vehicles, Airport Vehicle Density and AI traffic before sacrificing the main airport buildings. Lower Autogen Density around cities and forested approaches; then reduce Scenery Complexity one step at a time. Some add-ons assign sensible complexity levels, while others show nearly every object at the same setting.
- Disable optional components selectively. Use the scenery's documented configuration options, if supplied, to remove features such as extra autogen, road traffic, static aircraft or animations. Do not delete shared object libraries or rename random
.bglfiles, because other scenery may depend on them. - Set a sustainable frame-rate target. FSX's frame-rate limiter does not create performance, but a target the computer can maintain often gives steadier frame pacing and leaves processing time for scenery loading. Compare the same approach rather than judging a single peak FPS reading.
If the whole simulator runs poorly rather than one scenery area, follow our ordered FSX performance-tuning process instead of stripping out scenery at random.
Should I lower mesh or texture resolution first?
Not for an object-heavy airport: traffic, autogen and scenery complexity are usually better first targets. Mesh Resolution controls terrain shape, while Texture Resolution affects ground-image sharpness and texture memory; neither directly removes the thousands of buildings and vehicles that commonly limit airport FPS.
For a mesh package, use a resolution appropriate to its source data rather than selecting the finest setting simply because it is available. Our explanation of global mesh resolution and regional scenery combinations covers this distinction. Photoreal scenery is different: lowering texture resolution may help texture-loading pressure, but it also removes the detail for which the package was installed.
Why does FPS fall only when several add-ons are active?
Scenery costs accumulate with the aircraft, weather, shadows and traffic already in use. A detailed airport that performs acceptably with a default aircraft may struggle when combined with a complex virtual cockpit, dense AI and heavy cloud coverage.
- Duplicate airport files can place more than one set of buildings or airport data in the same location.
- Bundled traffic files may be installed outside the scenery area's own folder, so unticking that area does not always disable its AI schedules.
- Regional autogen can add thousands of objects around an airport even when the airport package itself is efficient.
- Library priority resolves which scenery has precedence, but it does not make every lower overlapping file free to process.
Test one add-on or setting change at a time. Our comparison of FSX graphics upgrades and their performance costs can help when scenery is stacked with texture, lighting and autogen modifications.
Is it low FPS or scenery-loading stutter?
Persistent slow performance while the view is stationary is an FPS problem; brief pauses during an approach or when panning are more likely to be scenery-loading stutters. Faster storage can reduce loading pauses, but it will not solve the CPU draw-call load from a highly detailed airport.
Also distinguish poor FPS from an out-of-memory failure. FSX and FSX: Steam Edition are 32-bit applications, so several high-detail sceneries, large textures and a complex aircraft can exhaust virtual address space. An out-of-memory message requires reducing the active memory load; changing the frame-rate target alone will not fix it.