Why is FS2004 FPS low at airports and on runways?

FS2004 (FS9) loses FPS at airports because busy hubs combine AI traffic, detailed scenery, autogen, clouds, lights and shadows in one view, while the simulator relies heavily on a single CPU thread. Set AI traffic to zero first; if only one airport remains slow, test its add-on scenery and duplicate airport files.

Why are airports so demanding in FS2004?

Airports produce FS2004's heaviest combination of simulation and rendering work, so the runway surface itself is rarely the cause.

• AI traffic: FS9 calculates aircraft positions, taxi routes, lights and sounds. The cost rises at hubs where many airline and general aviation schedules overlap.
• Airport scenery: Terminals, jetways, static aircraft, ground polygons and other custom objects create much more work than open countryside.
• Autogen: Trees and buildings around an urban airport remain visible from the runway, especially when visibility is high.
• Weather: Several cloud layers can turn an acceptable clear-weather frame rate into a poor overcast approach.
• Shadows and lighting: Ground scenery shadows, aircraft shadows, landing lights and illuminated airport objects add work close to the ground.
• The aircraft: Complex gauges, virtual cockpits, sounds and effects continue running while FS9 processes the airport.

FS2004 depends heavily on main-thread CPU performance. A modern graphics card can therefore show modest utilisation while AI traffic or scenery work holds back the frame rate.

How do I identify the exact airport FPS bottleneck?

A repeatable, one-change-at-a-time test is the quickest way to find the setting or add-on responsible.

1. Create a baseline. Save a daylight flight at the affected airport with clear weather and a default aircraft. Use the same cockpit view and cycle Shift+Z until the frame-rate display appears.
2. Set both AI sliders to zero. Turn off airline and general aviation traffic, then reload the flight so the comparison starts cleanly. A large gain identifies traffic as the main constraint; our reversible FS2004 traffic-isolation procedure explains how to perform this test without removing traffic files.
3. Test clear weather. If removing clouds restores performance, reduce cloud detail or the number of layers before sacrificing airport scenery.
4. Separate scenery from autogen. Lower scenery complexity by one step, reload and record the result. Restore it before testing autogen density, otherwise the useful setting remains hidden.
5. Disable shadows independently. Start with ground scenery shadows, then test aircraft shadows. Do not assume both options have the same cost.
6. Remove the add-on airport from the test. Disable all Scenery Library entries belonging to that package, restart FS2004 and compare the stock airport. Keep the package installed while diagnosing it.
7. Compare a default aircraft. If the slowdown occurs only with one add-on aircraft, its panel, gauges, virtual cockpit, lighting or sound package is contributing to the load.

Which FS2004 settings should I lower first?

Lower AI traffic first, then ground scenery shadows, scenery complexity, autogen and cloud detail; reduce resolution or texture quality only when the graphics card is the confirmed limit.

• AI traffic: Choose a percentage that remains stable at the busiest airport you regularly use. Maximum traffic is rarely sensible at a large hub.
• Ground scenery shadows: Disable these early in the test because they can be disproportionately expensive near detailed buildings.
• Scenery complexity: Lower this when terminals or static scenery are responsible. Some add-on airports use this setting to control essential buildings, so check that the airport has not become incomplete.
• Autogen density: Reduce it when city airports are much slower than isolated fields.
• Cloud detail: Adjust it when clear-weather FPS is good but overcast arrivals are slow.
• Resolution and anti-aliasing: Lower these when FPS changes substantially with display resolution. Little or no change usually points back to a CPU-side limit.

Our balanced FS2004 display-setting guidance covers the trade-offs between the major sliders. A common mistake is to lower everything at once, gain FPS and never discover that one traffic setting caused most of the loss.

Is it low FPS or scenery-loading stutter?

Sustained low FPS and short loading pauses need different fixes, even though both feel rough while taxiing.

If the Shift+Z counter remains low for several seconds, the simulator is continuously overloaded by traffic, scenery, weather or the aircraft. If the displayed rate is otherwise acceptable but the picture freezes briefly at particular taxiway points or during turns, FS9 is probably loading textures and scenery.

An SSD can reduce those pauses, but it will not remove a CPU bottleneck that holds the simulator at a low frame rate. Our guidance on distinguishing taxiing stutters from an airport FPS limit covers storage and scenery-loading checks without confusing them with the sustained slowdown discussed here.

What if only one add-on airport has low FPS?

If comparable default airports run well, the affected airport package or a conflict with another scenery layer is the likely cause.

Disable every Scenery Library area installed by that package and restart FS2004. If the stock airport performs normally, restore the package and check its documentation for optional static aircraft, surrounding city scenery, high-detail objects or alternative texture sets. Static aircraft built into scenery are not removed by setting AI traffic to zero.

Also check third-party scenery for multiple airport-layout or AFCAD .bgl files covering the same ICAO code. Duplicates can produce overlapping layouts, misplaced objects and abnormal AI behaviour. Do not delete stock FS2004 scenery files, and do not judge a file solely by its name; move only confirmed third-party duplicates to a backup location.

Scenery priority matters when a package includes separate airport, mesh or landclass entries. Follow the package's intended ordering rather than repeatedly moving the airport to the top and creating a different conflict.

Why does FPS drop after touchdown or at night?

A touchdown or night-time drop usually reveals close-range scenery, shadow and lighting costs that were less prominent during the approach.

Test the same saved flight in daylight with clear weather, ground scenery shadows disabled and the aircraft's landing lights off. Poor performance only at night points towards airport lighting, AI aircraft lights, night textures or aircraft lighting effects. A brief touchdown hitch may be an effect or scenery load; a low rate that continues to the gate is a sustained workload problem.

Direction is another useful clue. If FPS improves when looking away from the terminal, concentrate on airport scenery. If every direction is equally slow, test AI traffic, weather and the aircraft panel before blaming the runway.

Will an SSD, more RAM, a faster GPU or the frame limiter fix it?

Hardware upgrades help only when they match the bottleneck, and FS2004's frame-rate limiter cannot raise a true airport minimum.

• SSD: Helps scenery and texture loading pauses more than sustained FPS.
• More RAM: Helps if Windows is paging heavily, but FS9 remains a 32-bit application and does not turn spare memory into extra frame rate.
• Faster GPU: Helps at high resolutions and demanding anti-aliasing settings. It does little for CPU-bound AI calculations.
• Faster CPU: Better per-core performance usually matters more to FS9 than a high total core count.

A finite target around 25–30 FPS is often smoother than Unlimited if the computer can maintain it. Setting the limit below an unstable peak can leave processing time for scenery loading, but it cannot convert a 15 FPS airport into 30 FPS. See our advice on choosing a realistic FS2004 frame-rate target before treating the limiter as a performance fix.

Should I edit FS9.cfg to improve airport FPS?

Use FS9.cfg edits only after a controlled test has identified the bottleneck.

Back up the existing file before changing anything, alter one value at a time and keep notes. If configuration corruption is suspected, rename the file and let FS2004 create a fresh one; expect simulator preferences to return to defaults, and retain the original until the test is complete.

Avoid copying large collections of unexplained tweaks. They make comparisons unreliable and can trade low FPS for blurred textures or extra loading pauses. An autogen modification is sensible only when the earlier tests prove that autogen—not AI traffic, clouds or one airport package—is the limiting factor.