Fix FS2004 stuttering while taxiing by checking AI traffic, scenery, clouds, add-ons, frame limits and texture-loading bottlenecks in order.
FS2004 usually stutters while taxiing because ground level makes it process nearby airport scenery, autogen and AI aircraft while also running the selected aircraft's gauges. Texture or scenery files may also be loading as the aircraft moves. Reduce traffic and scenery first, cap the frame rate, then isolate aircraft and scenery add-ons.
Why is FS2004 slower on the ground than in the air?
Airports concentrate far more work into a small area than cruise flight does. FS2004 must draw buildings, taxiway markings, autogen and parked or moving AI aircraft, while calculating traffic and loading scenery as you cross into new areas.
The simulator's main workload is heavily dependent on one processor thread. Total CPU utilisation can therefore look low even when the thread running FS2004 is at its limit, and a faster graphics card alone may not solve the problem. Taxiway edges and buildings also make uneven frame delivery much easier to see than it is against open sky.
Is it low FPS or a scenery-loading stutter?
The pattern of the slowdown usually identifies the cause more reliably than the average frame rate. Press Shift+Z to cycle FS2004's information display until the frame rate appears, then watch what happens during the pause.
| Symptom | Most likely cause | Useful test |
|---|---|---|
| Continuously low FPS | AI traffic, autogen, airport complexity, clouds or a demanding aircraft | Set traffic to zero and use a default aircraft |
| Brief pauses every few seconds | Scenery or texture loading, background file access or an add-on conflict | Repeat the flight at a default airport with default scenery |
| Slow only at major airports | Dense airport scenery and concentrated AI traffic | Compare the same aircraft at a small stock airport |
| Slow only in one cockpit or aircraft | Complex gauges, virtual cockpit geometry or large aircraft textures | Change aircraft and compare cockpit and external views |
| Blurry ground followed by a pause | Texture loading cannot keep pace | Use our checks for late-loading FS2004 textures |
Which FS2004 settings should you change first?
Change one group of settings at a time so that the result identifies the actual bottleneck. We recommend this order:
- Create a clean baseline. Load a default aircraft at a small stock airport, select simple clear weather and set AI traffic to zero. If this runs smoothly, the core installation is probably not the problem.
- Set a finite frame-rate target. Start with 25 or 30 FPS rather than Unlimited. Choose a target the computer can maintain; an unstable 30 FPS target may feel worse than a steady 25 FPS.
- Test AI traffic separately. Keep all airline and general aviation traffic at zero, then restore them gradually. Large AI schedules and detailed AI models hit hardest around hubs, precisely when taxiing.
- Reduce nearby scenery load. Turn off ground-scenery shadows first, then lower autogen density and scenery complexity one step. Do not immediately reduce every graphics option to minimum.
- Simplify the weather. Detailed three-dimensional clouds can consume resources even when the slowdown appears to be airport-related. Compare identical taxi tests in clear and cloudy conditions.
- Change aircraft and view. A large improvement in an external view points towards panel or virtual-cockpit gauges. A different aircraft running smoothly points towards the original add-on rather than the airport.
- Disable add-ons individually. Deactivate the suspect airport or regional scenery through the Scenery Library and reload or restart FS2004 as prompted. Do not delete packages while diagnosing them.
Our balanced settings for steadier FS2004 frame rates explain which detail controls affect the processor, graphics card and scenery loading. A mistake we see constantly is reducing resolution or anti-aliasing first when AI and nearby scenery are actually exhausting the main processor thread.
Can an SSD stop taxiing stutters?
An SSD helps only when the pauses come from reading scenery and texture files. It can shorten loading and reduce some file-access delays, but it will not cure continuously low FPS caused by AI traffic, autogen, clouds or complex gauges.
If textures appear late as you taxi, check that the drive has free space and that backup, indexing or security software is not repeatedly scanning the FS2004 directory. Do not disable security protection permanently. Our explanation of what an external SSD can and cannot improve in FS2004 covers the storage trade-offs.
What if the stuttering began after installing scenery?
If the slowdown started immediately after a scenery change, that package should be the first suspect. Dense custom airports, broad landclass coverage, detailed mesh and large ground textures can overlap, increasing both terrain processing and file access.
Disable the newest scenery area and repeat the exact taxi route. If performance returns, re-enable related packages individually and check their Scenery Library order. At an airport affected by multiple packages, also look for duplicate airport layouts rather than assuming the newest airport is faulty.
When mesh or replacement ground textures are involved, verify their folders and activation order using our FS2004 terrain mesh and ground-texture installation guidance. Reinstalling the whole simulator is unnecessary unless default scenery also stutters under the clean baseline test.
Should you edit FS9.cfg?
Do not begin with copied FS9.cfg tweaks. Many old tuning recommendations target different hardware, and combining them can make frame pacing or texture loading worse.
If default aircraft and scenery still stutter after resetting the display options, close FS2004, back up the configuration file and rename it so the simulator creates a clean one at the next launch. This resets preferences, so record important settings first. If the fresh configuration changes nothing, restore the backup rather than adding speculative tweaks.
What does the test result mean?
- Smooth at a small airport but slow at a hub: reduce AI traffic or the hub's scenery complexity.
- Smooth in a default aircraft only: simplify or replace the add-on aircraft, panel or gauges.
- Pauses accompanied by blurry or popping textures: investigate storage access, texture size and scenery packages.
- Low FPS everywhere near the ground: lower autogen, scenery complexity, shadows and clouds, then use a sustainable frame-rate cap.
- Only one geographic area is affected: isolate scenery, mesh, landclass and duplicate airport files covering that location.