Fix FS2004 low FPS at airports and on runways by testing AI traffic, scenery, weather, shadows and add-on airport conflicts in the right order.
FS2004 usually loses FPS at airports because FS9 must process concentrated AI traffic, terminal scenery, autogen, shadows, lights and weather at once. The runway itself is rarely the fault. First disable AI traffic, then test scenery complexity, autogen, clouds and shadows; if only one airport is slow, suspect its add-on scenery.
Why are airports so demanding in FS2004?
Airports concentrate more CPU and graphics work into one view than most areas of FS2004. At a major hub, FS9 may be calculating dozens of AI aircraft while drawing terminals, jetways, static aircraft, ground polygons, nearby autogen and several layers of cloud.
- AI traffic: Airline and general aviation traffic consume CPU time for flight models, taxi routing, lights and sound. The impact rises sharply at hubs where many schedules overlap.
- Scenery complexity: Detailed terminals, custom objects and static aircraft create far more draw calls than an open countryside scene.
- Autogen: Buildings and trees surrounding an airport remain visible from the runway, particularly with a long visibility range.
- Weather: Multiple cloud layers and poor-weather visibility effects can turn an acceptable airport into a slow one.
- Shadows and lights: Aircraft shadows, scenery shadows, landing lights and illuminated airport objects add work near the ground.
- Add-on aircraft: Complex panels, gauges, sounds and lighting effects continue running while FS9 is also handling the airport.
FS2004 is heavily dependent on single-thread CPU performance. A modern graphics card may therefore show low utilisation while the simulator still struggles at a busy airport.
How do I find the exact cause of low airport FPS?
A controlled, one-change-at-a-time test will identify the bottleneck faster than applying several configuration tweaks together.
- Create a repeatable test. Save a flight at the affected airport in daylight, using a default aircraft. Cycle
Shift+Zuntil the frame-rate display appears, then use the same cockpit view for every test. - Set AI traffic to zero. Reduce both airline and general aviation traffic, then reload the flight. A large improvement means traffic density is the main constraint.
- Use clear weather. Remove cloud layers temporarily. If performance returns, reduce cloud detail or weather visibility before changing airport scenery.
- Lower scenery complexity. Move it down one level and reload the flight. Test autogen separately so that you know which setting matters.
- Disable shadows. Test the aircraft and scenery shadow options independently, especially if FPS falls only when the aircraft is on the ground.
- Compare the default airport. Disable the airport's third-party Scenery Library entry, restart FS2004 and repeat the test. Do not delete the package while diagnosing it.
- Compare a default aircraft. If only one add-on aircraft is slow, its gauges, virtual cockpit, lighting or sound package is contributing to the problem.
| Test result | Most likely cause | Best next action |
|---|---|---|
| FPS rises with traffic at zero | AI aircraft and airport activity | Use a lower traffic percentage at large hubs |
| FPS rises in clear weather | Cloud layers or visibility effects | Reduce cloud detail before reducing scenery |
| Only one airport is slow | Add-on scenery or a scenery conflict | Test that package and check for duplicate airport files |
| Only one aircraft is slow | Panel, gauges, virtual cockpit or effects | Reduce aircraft-specific options where available |
| There are brief pauses rather than sustained low FPS | Scenery and texture loading | Check storage performance and scenery configuration |
Which FS2004 settings should I lower first?
Lower AI traffic first, followed by scenery complexity, autogen, clouds and shadows. Texture quality and screen resolution are lower priorities unless the graphics card is demonstrably the limiting component.
- AI traffic: Avoid using maximum traffic at major hubs. Choose the highest percentage that remains stable at your most demanding airport.
- Scenery complexity: Lower this when terminals or static scenery are the cause. Some add-on airports require a particular level to display essential buildings, so check the package documentation.
- Autogen density: Reduce this when airports surrounded by cities are slower than isolated airports.
- Cloud detail: Reduce it when clear-weather performance is good but overcast approaches are slow.
- Shadows: Disable these when the loss occurs near the ground or when using aircraft with unusual transparency effects.
- Target frame rate: Use a finite target the computer can maintain, commonly somewhere around 20–30 FPS in FS9 rather than Unlimited. A limiter cannot raise the true minimum, but it can improve consistency and leave time for scenery loading.
Our balanced FS2004 display-setting recommendations explain the visual and performance cost of each major slider. A mistake we see constantly is lowering every option at once, obtaining better FPS and never discovering that AI traffic alone caused the slowdown.
What if only one add-on airport has low FPS?
If one airport is slow while comparable default airports run well, the add-on package or a conflict with another scenery layer is the likely cause.
Disable the airport through the Scenery Library and restart FS2004. If that fixes the problem, restore the package and check for optional static aircraft, dense surrounding scenery, custom ground polygons and multiple active airport-layout or AFCAD files for the same ICAO code.
Duplicate airport files can create overlapping layouts, misplaced objects and abnormal AI behaviour. Move only suspect third-party files, keep backups and never remove stock FS2004 scenery files merely because they contain the same airport. Scenery Library priority should also follow the add-on developer's instructions.
Why does FPS drop after touchdown or at night?
A touchdown or night-time slowdown usually exposes lighting, shadow or close-range scenery costs that were less visible during the approach.
Test the same airport in daylight, with clear weather and aircraft shadows disabled. If night performance alone is poor, examine runway lighting, AI aircraft lights and the add-on aircraft's landing-light effects. A momentary hitch on approach is normally scenery loading; a low frame rate that persists at the gate points to traffic or rendering workload.
Will an SSD, more RAM or a faster GPU fix it?
An SSD can shorten loading pauses, but it normally will not cure sustained low FPS caused by AI traffic or complex airport scenery. More RAM helps only when Windows is paging heavily, while a faster GPU mainly helps at high resolutions or with demanding anti-aliasing.
Because FS9 is predominantly limited by one CPU thread, airport performance often depends more on CPU speed and per-core efficiency than the total number of processor cores. This is why changing traffic and scenery settings can produce a larger gain than upgrading the graphics card.
Should I use FS9.cfg tweaks or performance utilities?
Configuration edits and utilities are secondary measures, not substitutes for identifying the airport bottleneck. Back up FS9.cfg and any file an utility will modify before testing it.
Our guide to safe FS9.cfg and graphics modifications covers configuration changes that can help texture loading or accidentally make airport stutters worse. Change one value at a time and retain a route back to the original file.
The downloadable FS2004 autogen frame-rate modification reduces scenery overhead by changing autogen data. It is most relevant when autogen is the confirmed cause, affects scenery beyond airports and may conflict with other modified autogen files, so keep the originals rather than installing it as a first response.