What frame rate should I set in FS2004?

In FS2004 (FS9), set Target frame rate to 30 FPS for most flights. If a detailed airport, complex aircraft, heavy clouds or AI traffic pulls it down repeatedly, use 25 FPS. Choose Unlimited only for diagnosis: a stable cap usually gives smoother pacing and leaves processing time for scenery and gauges.

Recommended FS2004 frame-rate settings

For most FS2004 installations, 30 FPS is the best starting point, while 25 FPS is a sensible fallback for demanding aircraft and scenery.

The selected target is a ceiling, not a promised frame rate. A 30 FPS setting stops FS2004 trying to render significantly faster than 30; it cannot make a flight already running at 18 FPS reach 30.

FS2004 is often limited by its main CPU workload rather than the graphics card. AI traffic, panel gauges, autogen and scenery calculations can therefore hold back a modern computer even when GPU usage appears low.

How do I find the best target frame rate?

Test 30 FPS in the most demanding conditions you regularly use, then lower it to 25 only if performance cannot remain reasonably close to the target.

1. Build a realistic test flight. Load the aircraft, airport, weather and approximate AI level you normally use. An empty rural flight in a default aircraft will give a misleading result if you usually fly airliners from detailed hubs.
2. Let the flight finish loading. Wait for the initial scenery and textures to settle before judging performance.
3. Display the frame rate. Press Shift+Z until the red information text includes the FPS reading.
4. Set the initial limit. Open Options > Settings > Display > Hardware and move the Target frame rate slider to 30.
5. Test the demanding parts. Taxi around the airport, pan the virtual cockpit or 2D panel, change views and fly through cloud. Watch for prolonged drops, pauses and ground textures that stay blurred—not just the highest number displayed.
6. Change one setting at a time. If 30 remains broadly stable, keep it. If the simulator spends much of the test in the low twenties, try 25 and reduce the workload responsible for the drop.

Do not expect the counter to remain fixed on exactly 30. Brief dips while changing view or loading new scenery are normal; sustained low performance and repeated stutters matter more. Our guide to the FS2004 sliders that recover FPS with the least visual loss explains what to reduce before lowering image quality across the simulator.

Why is Unlimited usually worse in FS2004?

Unlimited is usually worse because FS2004 may devote too much processing time to drawing extra frames instead of loading scenery, updating gauges and managing AI traffic.

The displayed average can rise while the actual experience becomes less consistent. Typical symptoms include uneven cockpit panning, short pauses and terrain textures that remain blurry longer than expected. A mistake we see repeatedly is selecting Unlimited simply because the computer is much newer than FS2004; the simulator’s old engine behaviour still applies.

Unlimited remains useful as a temporary diagnostic setting. It can show whether a flight is capable of exceeding the intended cap, but compare smoothness and texture loading as well as the FPS counter before keeping it.

If blurred ground textures persist with a sensible limit, our explanation of FS9.cfg changes, frame limits and texture loading covers the next checks. Back up FS9.cfg before editing it, and avoid applying several copied tweaks at once.

Why does FS2004 fall below the selected target?

FS2004 falls below its target when the aircraft, scenery, weather or traffic requires more processing time than the computer can provide for each frame.

The most common causes are:

• Dense AI aircraft at a major airport
• Complex add-on panels and gauge code
• Detailed airport scenery
• High autogen or scenery-complexity settings
• Dense 3-D cloud coverage and multiple cloud layers
• Extra undocked views or multiple monitors
• Background programs interrupting the simulator
• Conflicting internal, driver-level or third-party frame limiters

Reduce the workload causing the problem rather than repeatedly lowering the target. At an airport, temporarily reducing AI traffic is a useful first test. During general flying, clouds and autogen are more likely candidates. Our broader FS2004 performance troubleshooting answers cover stutters, add-ons and other bottlenecks.

What if FS2004 runs at only 1 FPS?

A persistent 1 FPS is a fault rather than a frame-limit choice, so changing the target from 30 to 25 will not solve it.

Check whether the problem affects every aircraft and location, then test without recently installed aircraft, scenery or weather add-ons. Graphics-driver overrides and a damaged configuration can also produce extreme slowdowns. Follow our step-by-step checks for an FS2004 installation stuck at 1 FPS before changing normal display settings.

Is 60 FPS better in FS2004?

Sixty FPS is better only when FS2004 can sustain it without stutters, blurred scenery or cuts to the visual settings that matter to you.

A high-refresh monitor does not make 60 FPS necessary. FS2004 remains comfortable at a steady 25–30 FPS, particularly for normal cockpit flying, and 30 FPS often leaves useful processing headroom for scenery and gauges. Once 30 is dependable, increase visual detail gradually before deciding that a higher frame-rate target offers a worthwhile improvement.

Forced vertical synchronisation or an external limiter can change frame pacing, but avoid running several caps together. Establish a baseline with FS2004’s own limiter first. For most installations, the dependable setting remains 30 FPS, falling back to 25 FPS when demanding flights cannot hold 30.