Learn how to add AI traffic in FSX without a major FPS drop using efficient models, selective schedules, sensible sliders and repeatable testing.
You cannot add AI traffic to FSX with literally zero performance cost, but you can keep the hit small by using purpose-built low-detail AI aircraft, installing only the airlines and schedules you need, avoiding duplicate traffic files, and starting with conservative airline and general aviation traffic sliders.
How should I install AI traffic with minimal FPS loss?
The most efficient setup uses dedicated AI models and a selective schedule rather than high-detail flyable aircraft or every available airline. The same method applies to boxed FSX and FSX: Steam Edition; only their installation paths differ.
- Record a baseline. Save a flight at a demanding airport with fixed weather, time, aircraft and cockpit view. Use FSX's frame-rate display and note both FPS and stuttering with airline and general aviation traffic disabled.
- Choose aircraft built specifically for AI. Proper AI models use simpler geometry, multiple levels of detail and lighter textures. Avoid assigning complex flyable add-ons as traffic aircraft: their detailed exterior models, virtual cockpits, gauges and large textures can make even a modest schedule expensive.
- Install only the traffic you will see. A practical package-based approach is to use an installer that places World of AI files into FSX, then add only the selected airline traffic packages needed for your usual regions and airports.
- Remove overlapping schedules. Running default traffic and replacement plans for the same routes can produce duplicate departures and crowded parking. Disable an obsolete traffic BGL rather than deleting it, restart FSX, and test one change at a time.
- Start with conservative density settings. Around 10–20% is a sensible testing range for airline traffic, with general aviation set lower at large hubs. Increase each slider in small steps; there is no universal percentage that guarantees a particular FPS.
- Repeat the same test. Compare the saved flight from the same view after AI has spawned. Testing while cruising over an empty area will not reveal the cost of taxiing aircraft, airport scenery and ground vehicles at a busy hub.
Which AI traffic setup is easiest on FPS?
Purpose-built AI aircraft with a small, relevant timetable offer the best balance between airport activity and performance.
| Traffic method | Best use | Likely performance effect |
|---|---|---|
| Dedicated AI models | Normal airline and general aviation traffic | Lowest cost for a given number of visible aircraft |
| Targeted custom schedules | A few favourite airlines, bases or routes | Easy to control because unnecessary flights are excluded |
| Large package collection | Broad worldwide coverage | Greater risk of duplicate routes and excessive hub traffic |
| Flyable add-ons used as AI | Only when no suitable AI model exists | Usually the heaviest option and best avoided at busy airports |
If packaged timetables add far more movements than you need, our instructions for building small, targeted AI schedules explain how to compile a traffic BGL containing only the routes you want.
Which FSX traffic settings affect FPS most?
The airline and general aviation sliders control how many scheduled aircraft are eligible to appear, while airport and road vehicles add separate CPU and rendering loads.
- Airline traffic density: Reduce this first when performance falls mainly at large commercial hubs.
- General aviation traffic density: Keep it low if you mostly fly airliners, particularly where an add-on schedule already supplies regional or business traffic.
- Airport vehicle density: Service vehicles can be disproportionately expensive at complex airports with many stands.
- Road vehicle density: This does not control aircraft, but it can consume enough resources to worsen an AI-related slowdown near cities.
- Ships and ferries: Lower them when they are not relevant to the flight rather than sacrificing visible aircraft first.
The traffic percentage does not make each AI model cheaper; it only limits which scheduled flights appear. Ten complex flyable aircraft can therefore perform worse than many well-optimised AI models. Detailed airport scenery, aircraft shadows and several taxiing aircraft can also combine into a larger loss than any one setting causes alone.
Can FSX AI traffic have no FPS impact at all?
No: every active AI aircraft requires flight simulation, ATC handling and rendering, so some processing cost remains. FSX is often constrained by its main simulation thread, which is why a busy airport can stutter even when the graphics card is not fully occupied.
A frame-rate limit can hide the cost while the computer has spare capacity. For example, the displayed FPS may remain fixed, but reduced headroom appears later as uneven frame delivery when traffic, clouds and detailed scenery coincide. Judge smoothness as well as the displayed average.
Why is the installed AI traffic missing?
Missing traffic usually points to an installation or schedule problem rather than an FPS setting. Confirm that the installer targeted the correct FSX installation, the airline or general aviation slider is above zero, the aircraft exists under SimObjects\Airplanes, and the traffic BGL sits inside an active scenery folder.
Check the scheduled day and time, available parking and complete model and texture entries as well. A common FSX trap is mixing traffic-file formats: a single enabled legacy FS9-format traffic BGL can suppress FSX-format traffic plans. Temporarily rename suspect BGL files with a non-BGL extension, restart the simulator and test them individually; never delete the originals while diagnosing the problem.
If traffic is only one part of a wider slowdown, use our broader FSX frame-rate tuning steps to balance scenery, weather and vehicle settings without cutting AI more than necessary.