Fix slow FS2004 loading by isolating scenery, aircraft and AI add-ons, stopping repeated scenery rebuilds, and choosing upgrades that help.
FS2004 (FS9) usually loads slowly because it is scanning too many add-on aircraft, AI traffic files or scenery layers, waiting for a missing drive, or rebuilding scenery indexes it cannot save. Test a default flight, disable add-ons in halves, fix invalid paths and permissions, then move the complete installation to an SSD.
What makes FS2004 take so long to load?
The stage at which FS2004 pauses is the best clue to what is causing the delay.
| Where FS2004 slows down | Likely cause | First test |
|---|---|---|
| Before the opening screen | A large aircraft collection, startup module, external utility, antivirus scan or slow storage | Temporarily remove recently added aircraft and disable known third-party startup components |
| While creating every flight | Scenery, AI traffic, weather, a saved-flight dependency or storage bottleneck | Load a default aircraft and airport with simple weather and AI traffic disabled |
| Only at one airport | Faulty or excessively detailed local scenery, duplicate airport files or dense local AI traffic | Disable that airport's add-on scenery and load the default version |
| Only with one aircraft | Missing gauges, broken panel or sound aliases, large textures or a faulty aircraft configuration | Load the same flight with a default aircraft |
| Rebuilding scenery on every launch | An invalid path, unwritable configuration or index files being deleted | Check scenery paths, permissions and file-cleaning software |
| After the cockpit appears | Terrain and texture throughput rather than programme startup | Test a default area and reduce demanding scenery settings |
A single scenery-database rebuild after installing, removing or reordering scenery is normal. Rebuilding it after every clean shutdown is not.
How long should FS2004 take to load?
There is no useful universal loading time because an installation with hundreds of aircraft and scenery layers has far more files to inspect than a default installation.
Consistency is the better test. An unchanged second launch should not rebuild the scenery database, and a default flight should load markedly faster than one using a complex aircraft, detailed airport and extensive AI traffic. Measure programme startup separately from flight creation so that you know which stage improved.
How do I find the add-on causing slow loading?
The fastest reliable method is to establish a default-content baseline, then restore add-ons in groups until the delay returns.
- Back up the active configuration. With FS2004 closed, copy
%APPDATA%\Microsoft\FS9\FS9.cfg, the activescenery.cfgand any files you intend to move. On modern Windows, file virtualisation can leave more than one apparent configuration file, so use modification dates to identify the copy FS9 actually updates. - Test a simple default flight. Select a default aircraft, default airport, fair weather and no AI traffic. If FS9 opens directly into a saved flight, replace it temporarily; saved flights can reference removed aircraft, scenery or weather components.
- Disable add-on scenery by halves. In the Scenery Library, disable roughly half the non-default layers, close FS2004 and restart it. A library change can trigger one legitimate rebuild, so judge the following unchanged launch. Repeat with the slow half until the offending layer is isolated. Missing network drives, disconnected external disks and folders added at the wrong level are common causes; use our checks for invalid scenery paths, library conflicts and folder structure if a layer will not load correctly.
- Isolate add-on aircraft. Move complete third-party aircraft folders out of
Aircraftand into a temporary folder outside FS2004, testing half the collection at a time. Do not move default aircraft or individual panel, model and texture subfolders. If one aircraft is responsible, check its panel gauges and sound or texture aliases before replacing the whole installation. - Test AI traffic files separately. Setting AI traffic to zero reduces generated traffic, but it does not remove suspect traffic files from the scenery scan. Move only recognised third-party traffic
.bglfiles into a holding folder, then restore them by package. These files are often underScenery\World\scenery, although an add-on may use its own scenery layer. - Disconnect third-party utilities. Weather programs, traffic injectors and other tools configured to connect when FS9 starts can wait for unavailable network services. Disable them through their own settings first. Test known third-party modules individually rather than deleting unfamiliar files from the
Modulesfolder. - Regenerate FS9.cfg last. Close FS2004 and rename
FS9.cfgtoFS9.cfg.old. FS9 will generate a clean file on its next launch. This resets display options, controls and other preferences, so retain the old file until testing is complete. When rebuilding it, follow our guidance on conservative FS9.cfg changes and their loading trade-offs.
A mistake we see often is changing scenery, aircraft, AI traffic and configuration settings simultaneously. That may make the symptom disappear, but it does not identify the faulty package and makes the simulator harder to restore.
Why does FS2004 rebuild the scenery database every time?
Repeated scenery rebuilding means FS9 detects a change on every launch or cannot retain the generated scenery indexes.
- Confirm that every enabled Scenery Library path exists and that any required network or removable drive is connected before FS9 starts.
- Remove obsolete and duplicate entries through the Scenery Library instead of editing unrelated configuration files.
- Check that the active configuration and per-user index locations are not read-only and are not being deleted by antivirus, synchronisation or cleanup software.
- Use the same Windows account and privilege level each time. Alternating between ordinary and administrator launches can make an old application use different real or virtualised configuration files.
- Allow one rebuild to finish, close FS2004 normally and test another unchanged launch. A crash or forced shutdown can prevent the new database from being retained.
Legacy installations under a protected Windows system folder are particularly prone to split configuration files and permissions trouble. If this remains the confirmed cause, a clean installation in a dedicated folder outside the protected system directories is safer than repeatedly running FS9 as administrator.
Do not delete the scenery indexes before every flight. That guarantees another slow rebuild and hides the invalid path or write-permission problem that needs fixing.
Will an SSD, more RAM or lower settings speed up FS2004 loading?
An SSD usually provides the most useful hardware improvement, but no upgrade can repair a missing scenery path, damaged add-on or configuration that cannot be saved.
| Change | What it can improve | Limitation |
|---|---|---|
| SSD | Reading thousands of small scenery, texture, gauge and aircraft files | Scenery left on a slow or unavailable drive remains a bottleneck |
| More RAM | Helps when Windows is paging heavily to disk | FS2004 is a 32-bit application and will not scale proportionally with large amounts of memory |
| Faster CPU | Flight creation and other processor-heavy FS9 work | Extra cores and raised process priority do not fix faulty files or inaccessible storage |
| Lower simulator settings | Flight creation, frame rate and pauses once flying | Usually has little effect on a delay before the opening screen |
| Antivirus exclusion | Can reduce repeated scanning of trusted FS9 files | Use only narrow exclusions for folders you have already scanned; never disable protection globally |
If moving FS2004 to an SSD, include the simulator, active add-on scenery and other frequently accessed content. Reinstalling or cloning while preserving paths is safer than casually dragging the folder because older add-on installers and scenery entries may contain absolute locations.
AI traffic, autogen, scenery complexity, clouds and complex aircraft can all increase flight-creation time. Our practical FS2004 performance settings show which sliders to reduce first instead of sacrificing every visual option.
Why is scenery still loading after the cockpit appears?
Slow or blurry terrain after entering the flight is a texture-streaming problem, not necessarily the same fault as slow programme startup.
Excessive scenery radius settings, uncapped frame rates, dense autogen and a slow drive can leave FS9 too little time to load terrain. If the opening screens are normal but ground textures sharpen slowly, follow our terrain-loading checks for frame limits, scenery demand and storage rather than deleting scenery indexes or reinstalling aircraft.
When should I reinstall FS2004?
Reinstall only when a default flight remains abnormally slow after third-party content is isolated, FS9.cfg has been regenerated, scenery paths are valid and the storage drive is healthy.
Back up add-ons and configuration files first, but do not copy everything straight into the new installation. Confirm that the clean simulator loads correctly, then restore aircraft, scenery, AI traffic and utilities in separate batches. Otherwise, the same faulty package will simply recreate the delay.