Understanding CPU Bottlenecks
Lesson Duration: 20–30 Minutes
Lesson Overview
In this lesson, we’re going to explore one of the most misunderstood concepts in Microsoft Flight Simulator: the CPU bottleneck.
Many users upgrade to a powerful graphics card expecting a huge increase in FPS, only to discover that their performance barely changes. The reason is often not the graphics card at all—it’s the CPU.
By the end of this lesson, you’ll understand:
What a CPU bottleneck is
Why airports are so demanding
What the Main Thread is
How Terrain LOD affects performance
How AI and Ground Traffic increase CPU workload
Why glass cockpit aircraft require more processing power
How to identify CPU limitations using Developer Mode
What Is A CPU Bottleneck?
Definition
A CPU bottleneck occurs when your processor cannot complete all of the calculations required to generate the next frame quickly enough.
When this happens, the graphics card has nothing to render because it’s waiting for the CPU to finish its work.
As a result:
• FPS decreases
• Stutters become more noticeable
• GPU usage often drops
• Performance becomes inconsistent
Real-World Example
Imagine an airport baggage system.
The CPU is the baggage handlers loading suitcases.
The GPU is the aircraft waiting to depart.
If the baggage handlers are still loading luggage, the aircraft cannot leave.
The aircraft isn’t the problem.
It’s waiting for the loading process to finish.
The same happens inside Flight Simulator.
The GPU cannot begin rendering the next frame until the CPU has finished calculating everything that needs to happen.
How A Frame Is Created
Every frame you see on your monitor follows the same process.
Step 1
The CPU performs calculations.
These include:
Aircraft physics
Weather
Navigation
Traffic
Terrain
Autopilot
Flight systems
Cockpit displays
Step 2
Once the CPU has completed these calculations…
It sends instructions to the GPU.
Step 3
The GPU then renders the image.
Step 4
The completed frame appears on your monitor.
If Step 1 takes too long…
Everything waits.
This is a CPU bottleneck.
Why Airports Stress The CPU
Busy airports are one of the most demanding environments in Microsoft Flight Simulator.
Why?
Because the CPU suddenly has thousands of additional calculations to perform.
Instead of simply flying through empty skies…
The simulator now needs to calculate:
Hundreds of airport buildings
Taxiway lighting
Ground markings
Jetways
Airport vehicles
AI aircraft
Ground crew
Pushback operations
Passengers
Fuel trucks
Weather effects
Glass cockpit systems
Ground radar
ATC
Each of these systems updates continuously.
This dramatically increases CPU workload.
Example
Compare:
A small rural airfield
versus
London Heathrow
The scenery isn’t just larger.
The amount of simulation occurring is dramatically higher.
This explains why FPS often drops significantly at major airports.
Understanding The Main Thread
This is one of the most important concepts in Flight Simulator.
Microsoft Flight Simulator uses multiple CPU cores.
However…
One core performs the majority of the simulator’s most important work.
This core is called:
The Main Thread.
Think of the Main Thread as the project manager.
Many workers are helping.
But every important decision still passes through one person.
If that manager becomes overwhelmed…
Everyone else begins waiting.
The simulator slows down.
What Does The Main Thread Handle?
The Main Thread manages:
Aircraft systems
Physics calculations
Flight model
Terrain loading
Object placement
AI traffic
Ground traffic
Cockpit updates
Weather
Flight calculations
Every frame depends on the Main Thread finishing its work.
What Happens When The Main Thread Is Overloaded?
You’ll usually notice:
FPS dropping
GPU usage decreasing
Stutters
Long frame times
Developer Mode displaying:
MainThread Limited
This is one of the clearest signs of a CPU bottleneck.
Terrain Level Of Detail (Terrain LOD)
Terrain LOD controls how much scenery the simulator draws around you.
Higher values mean:
More buildings
More trees
More terrain detail
More distant scenery
Longer drawing distances
This looks fantastic.
However…
Every additional object must first be processed by the CPU.
The GPU cannot render an object until the CPU has told it where the object belongs.
Increasing Terrain LOD dramatically increases CPU workload.
Example
Terrain LOD 100
The simulator loads scenery within a moderate distance.
Terrain LOD 300
The simulator loads significantly more scenery over a much greater distance.
This requires far more calculations every frame.
AI Traffic
AI aircraft behave just like real aircraft.
Each aircraft requires the CPU to calculate:
Taxi routing
Take-off clearance
Flight path
Altitude
Heading
Speed
Navigation
Landing
Parking
Now imagine:
100 AI aircraft.
Every aircraft updates multiple times every second.
That’s thousands of additional calculations.
Reducing AI traffic often improves CPU performance.
Ground Traffic
Ground traffic includes:
Airport buses
Fuel trucks
Pushback vehicles
Baggage carts
Service vehicles
Marshaller animations
Passengers
Although individually small…
Together they create a significant CPU workload.
Every moving object must be updated continuously.
Glass Cockpit Refresh Rate
Modern aircraft contain multiple digital displays.
Examples include:
Primary Flight Display
Navigation Display
Engine Display
Electronic Flight Bag
Weather Radar
Traffic Displays
These displays constantly update.
Some aircraft refresh these displays:
Every frame.
Others refresh:
30 times per second
60 times per second
The faster they update…
The more work your CPU performs.
Many aircraft allow you to reduce Glass Cockpit Refresh Rate.
Lower refresh rates can reduce CPU usage while remaining perfectly usable.
Identifying CPU Bottlenecks Using Developer Mode
Fortunately, Microsoft Flight Simulator includes a built-in performance monitor.
Step 1
Launch Microsoft Flight Simulator.
Step 2
Open:
Options
↓
General Options
↓
Developers
↓
Developer Mode
Turn it ON.
A small developer toolbar will appear at the top of the simulator.
Step 3
Select:
Options
↓
Display FPS
A performance overlay will appear.
Understanding The FPS Overlay
You’ll notice several pieces of information.
The most important are:
MainThread
GPU
Frame Time
FPS
If MainThread is displayed in red and shows a higher frame time than the GPU…
Your CPU is limiting performance.
If GPU is higher than MainThread…
Your graphics card is the limiting factor.
Student Practical Exercise
Today we’re going to identify whether your simulator is CPU limited.
Step 1
Enable Developer Mode.
Step 2
Display the FPS Counter.
Step 3
Load into one of the following airports:
EGLL Heathrow
KJFK
KLAX
EDDF Frankfurt
LFPG Paris
Choose a complex aircraft if available.
Examples:
PMDG 737
Fenix A320
iniBuilds A350
Step 4
Remain stationary at the gate.
Observe:
MainThread
GPU
FPS
Frame Time
Step 5
Taxi around the airport.
Observe whether:
MainThread frame time increases.
GPU usage decreases.
FPS drops.
Step 6
Take off.
Notice how:
As the aircraft climbs away from the airport…
CPU workload often decreases.
FPS improves.
MainThread frame time reduces.
Lesson Summary
Congratulations.
You now understand one of the most important performance concepts in Microsoft Flight Simulator.
Remember:
The CPU performs the calculations.
The GPU draws the image.
Busy airports dramatically increase CPU workload.
Terrain LOD is one of the biggest CPU-intensive settings.
AI and Ground Traffic both increase CPU usage.
Glass cockpit aircraft require additional processing power.
The Developer Mode FPS Counter allows you to identify whether your CPU is limiting performance