Fix FS2004 stuttering while taxiing by testing AI traffic, airport scenery, aircraft gauges, texture loading and a stable frame-rate cap.
FS2004 usually stutters while taxiing because airports combine dense scenery, autogen, AI traffic, aircraft gauges and frequent texture loading on an engine largely limited by one CPU thread. Set a sustainable frame-rate cap, reduce traffic and airport detail, then test a default aircraft and stock airport to isolate add-ons.
Why is FS2004 slower on the ground than in the air?
Airports put FS2004's heaviest workloads into a small area. The simulator must draw buildings, taxiway markings, surrounding autogen and AI aircraft while calculating traffic movement and loading new scenery and textures as the aircraft crosses the airport.
FS2004 is predominantly limited by one processor thread. Overall CPU usage can therefore appear modest on a modern multicore computer even though the thread running the simulator has reached its limit. A faster graphics card will not necessarily fix that bottleneck.
Taxiway edges, lights and nearby buildings also make uneven frame delivery much easier to see than it is against open sky. Our explanation of the workloads that reduce FS2004 performance at airports covers the main ground-specific causes in more detail.
Is it low FPS, frame pacing or scenery loading?
The pattern of the slowdown is usually more revealing than the average frame rate. Press Shift+Z until FS2004 displays its frame-rate counter, then repeat the same taxi route and note when each hitch occurs.
| Symptom | Likely cause | Best first test |
|---|---|---|
| Continuously low FPS around the airport | AI traffic, dense scenery, autogen, clouds or a demanding aircraft | Set airline and general aviation traffic to zero and load a default aircraft |
| High displayed FPS but jerky movement | Uneven frame delivery, an unsustainable frame-rate target or periodic background work | Set a finite target such as 25 or 30 FPS and test again |
| Pause at the same place on every taxi run | A scenery boundary, airport object, texture or conflicting scenery file | Repeat the route with the add-on airport disabled |
| Blurry ground followed by sharpening and a pause | Terrain or texture loading cannot keep pace | Check storage activity and reduce excessive terrain or texture demands |
| Only one aircraft or cockpit is affected | Complex gauges, virtual-cockpit geometry, textures or aircraft code | Compare a default aircraft and several views |
| The aircraft heading jumps but the scenery remains smooth | A noisy or poorly calibrated rudder or tiller axis | Test without the controller and inspect its calibration |
Why can FS2004 stutter despite showing high frame rates?
A high average FPS figure does not show short frame-time spikes. FS2004 may render many frames quickly, pause to process scenery or AI, and then catch up; the counter still looks healthy while motion along the taxiway appears uneven.
Running with the frame-rate target set to Unlimited can make this worse by allowing rendering to consume processor time needed for scenery loading and simulation work. Choose a target the computer can maintain at the problem airport, not the highest number it can reach in cruise. A steady 25 FPS often looks better than a target of 30 that repeatedly falls below its limit.
If the counter remains high but the motion still pulses, follow our checks for FS2004 stuttering with a high FPS reading. Do not judge smoothness solely by the peak figure.
How do you fix FS2004 taxiing stutters?
The quickest reliable fix is to build a clean baseline and restore one workload at a time. Keep the aircraft, starting position, view, weather and taxi route identical between tests.
- Test the problem airport with a default aircraft. Select simple clear weather, set both airline and general aviation traffic to zero, and use a default aircraft. This separates the airport from a demanding aircraft or panel.
- Set a finite frame-rate target. Start at 25 or 30 FPS rather than Unlimited. If FS2004 cannot hold that target at the busiest part of the taxi route, lower it until frame delivery becomes steady.
- Compare a small stock airport. Use the same default aircraft and weather at an uncomplicated default airport. Smooth performance there points towards the original airport, regional scenery or concentrated traffic rather than the core simulator.
- Restore AI traffic gradually. Increase airline traffic first, then general aviation traffic. Large schedules and detailed AI models have their greatest effect at hubs because many aircraft, textures and taxi calculations become active together.
- Reduce nearby scenery load. Turn off ground-scenery shadows, then lower autogen density and scenery complexity one step at a time. These settings usually matter more during taxi than reducing screen resolution.
- Compare clear and cloudy weather. Detailed three-dimensional clouds can consume resources even when the stutter appears airport-related. Repeat the same route without changing any other condition.
- Compare cockpit and external views. A large improvement outside the cockpit is a strong clue that panel gauges or virtual-cockpit detail are involved, although some gauge code may continue running when the panel is not visible.
- Disable suspect scenery rather than deleting it. Deactivate the newest airport or regional package through the Scenery Library and restart or reload FS2004 when required. Test packages individually so the result identifies the actual conflict.
A mistake we see repeatedly is changing every slider at once. That may improve performance, but it does not reveal whether AI, scenery, clouds or the aircraft caused the problem. Our practical FS2004 graphics and frame-rate settings provide sensible starting points without forcing every option to minimum.
Can an SSD stop taxiing stutters?
An SSD can reduce pauses caused by reading scenery and texture files, but it cannot fix continuously low FPS from AI traffic, airport complexity, clouds or aircraft gauges. It is most likely to help when ground textures appear late, scenery objects pop in, or disk activity rises during each pause.
Keep adequate free space on the drive and check whether backup, indexing or security software is repeatedly scanning the FS2004 folders. Scheduled background work can be paused briefly for diagnosis, but security protection should not be disabled permanently.
If blurriness accompanies the hitching, use our guide to diagnosing slow or late FS2004 texture loading. Excessive terrain settings in FS9.cfg can overwhelm loading even when the simulator is installed on fast storage.
What if the stuttering started after installing airport scenery?
Scenery installed immediately before the problem began should be the first suspect. A detailed airport may add high-resolution ground textures, complex buildings, static aircraft, lighting and additional objects that remain demanding even with the AI traffic sliders at zero.
Disable the complete scenery package and repeat the exact taxi route. If the stutter disappears, restore related components individually where the package permits it. Moving scenery lower in the Scenery Library is not the same as disabling it and may not resolve duplicate airport files.
Also check for two airport layouts covering the same location, particularly after installing an airport alongside an older AFCAD-style package. Do not delete files during diagnosis; move or disable only the confirmed duplicate after keeping a backup.
Should you reset or edit FS9.cfg?
Reset FS9.cfg only after default aircraft and scenery still stutter under the clean baseline. Copied configuration tweaks can contain oversized terrain values or settings intended for completely different hardware, so adding more tweaks is a poor first response.
Close FS2004, back up the existing configuration file and rename it. FS2004 will create a fresh file when it next starts, after which display, sound and controller preferences must be set again. If the clean configuration makes no difference, restore the backup rather than continuing with speculative edits.
What does each test result tell you?
- Smooth at a small airport but slow at a hub: reduce AI traffic, airport detail, surrounding autogen or scenery shadows.
- Smooth only with a default aircraft: investigate the original aircraft's panel, gauges, virtual cockpit and texture sizes.
- Pauses always occur at the same taxiway: isolate airport scenery, regional scenery and duplicate airport files.
- Blurry textures precede each pause: investigate storage access and terrain-loading settings rather than chasing a higher average FPS.
- Stutter appears only in complex weather: reduce three-dimensional cloud demands while leaving airport settings unchanged.
- Everything stutters, including stock aircraft and airports: reset
FS9.cfg, check background processes and verify that the computer is not throttling under load. - The view is smooth but steering is erratic: calibrate the rudder or tiller axis and add a small null zone if the controller signal is noisy.