Module Review & Preparing For Optimisation

Estimated Lesson Length: 20–25 Minutes

Welcome To The Final Lesson

Congratulations.

You’ve reached the end of Module 1 of the Performance Academy.

Before we begin changing settings in Module 2, we’re going to review everything you’ve learnt so far.

This module has been entirely focused on understanding how Microsoft Flight Simulator works.

Many people skip this stage.

They immediately start changing graphics settings, installing optimisation software or copying settings from YouTube.

The problem is…

Without understanding how the simulator actually works…

You’ll never know why something improved or why something made performance worse.

Now you do.

And that puts you in a much stronger position than most users.

Why Module 1 Matters

Think of building a house.

You wouldn’t start building the roof before laying the foundations.

The same applies here.

Before optimising Microsoft Flight Simulator…

You first needed to understand:

How your computer works.

How the simulator uses your hardware.

What causes performance problems.

How to identify bottlenecks.

How to measure improvements.

Everything we’ve learnt in this module becomes the foundation for every optimisation we’ll make later in the course.

Review 1 – Understanding The CPU

Let’s begin with the CPU.

Throughout this module, you’ve learnt that the CPU is responsible for performing the simulator’s calculations.

Rather than drawing graphics…

The CPU is responsible for thinking.

Every second it calculates:

Aircraft physics.

Navigation.

Weather.

AI traffic.

Ground vehicles.

Autopilot.

Glass cockpit displays.

Terrain loading.

Airport systems.

Flight calculations.

Without these calculations…

Nothing would happen inside the simulator.

Remember…

The GPU cannot begin drawing the next frame until the CPU has finished preparing it.

Key Takeaway

The CPU calculates the world.

Review 2 – Understanding The GPU

The GPU has a very different role.

Instead of calculating the simulation…

It creates everything you actually see.

The GPU renders:

Clouds.

Buildings.

Aircraft.

Cockpit lighting.

Shadows.

Textures.

Reflections.

Runways.

Weather effects.

Every single frame shown on your monitor has first been rendered by the graphics card.

The higher your graphics settings…

The harder your GPU works.

Key Takeaway

The GPU draws the world.

CPU Vs GPU

One of the easiest ways to remember the difference is this.

Imagine building a house.

The architect designs everything.

The builders actually construct it.

The CPU is the architect.

The GPU is the builder.

Both are essential.

If either one becomes overloaded…

Performance suffers.

Review 3 – Understanding FPS

We also explored Frames Per Second.

Remember…

FPS simply tells us how many individual images your computer creates every second.

However…

One of the biggest lessons from this module is that FPS alone doesn’t tell the full story.

Higher FPS doesn’t automatically mean smoother flying.

Consistency matters far more.

Stable FPS

Imagine driving on a motorway.

Maintaining a constant 60 mph feels comfortable.

Now imagine repeatedly accelerating and braking.

Even if your average speed is still 60 mph…

The journey feels much rougher.

Frame delivery works exactly the same way.

Consistent FPS creates smooth flying.

Unstable FPS creates a rough experience.

Key Takeaway

Smooth and consistent FPS is more important than chasing the highest number.

Review 4 – Frame Times

Frame time tells us how long each individual frame takes to create.

Unlike FPS…

Frame time allows us to understand how consistently the simulator is running.

Low and stable frame times create smooth motion.

Large fluctuations usually indicate performance problems.

Experienced simmers often monitor frame times alongside FPS because they provide a clearer picture of overall smoothness.

Key Takeaway

Consistent frame times create a consistent flying experience.

Review 5 – Stutters

One of the biggest complaints in Microsoft Flight Simulator is stuttering.

You’ve now learnt that stutters can have many different causes.

Examples include:

CPU spikes.

GPU spikes.

Scenery streaming.

Photogrammetry.

Large airports.

AI traffic.

Ground traffic.

Add-ons.

Insufficient RAM.

Thermal throttling.

Driver issues.

Rather than assuming the graphics card is always to blame…

You now understand how to investigate the real cause.

Key Takeaway

Stutters are symptoms—not the problem itself. The goal is to identify the root cause.

Review 6 – Bottlenecks

Throughout this module we’ve discussed bottlenecks several times.

Let’s recap.

CPU Bottleneck

The processor cannot complete its calculations quickly enough.

The GPU waits.

FPS decreases.

Developer Mode often reports:

MainThread Limited.

GPU Bottleneck

The graphics card is fully occupied rendering the image.

GPU utilisation approaches 100%.

Reducing graphical settings often improves performance.

Neither bottleneck is “bad.”

They simply tell you which component is currently limiting performance.

Knowing which component is limiting your simulator allows you to make the right optimisation decisions later.

Key Takeaway

Always identify the bottleneck before changing settings.

Review 7 – Your Performance Baseline

Perhaps the most important lesson in this module was creating your Performance Baseline.

Many users begin changing settings immediately.

Professional troubleshooting works differently.

You measure first.

Optimise second.

Measure again.

Compare the results.

Your baseline includes:

Airport.

Aircraft.

Weather.

Graphics settings.

Resolution.

Average FPS.

Lowest FPS.

Highest FPS.

MainThread or GPU Limited.

Personal observations.

This document becomes your reference point throughout the rest of the Performance Academy.

Key Takeaway

If you don’t measure your starting point, you’ll never know whether you’ve actually improved.

How Everything Connects

Let’s bring everything together.

Your CPU prepares the simulation.

↓

Your GPU renders the image.

↓

Frames are created.

↓

Frame times determine smoothness.

↓

Smooth frame pacing creates a better flying experience.

↓

Stutters occur when something interrupts this process.

↓

Your Performance Baseline allows you to measure improvements objectively.

Understanding this chain is the foundation of effective optimisation.

Knowledge Check

Before continuing to Module 2, answer the following questions.

Question 1

Which component performs the majority of Microsoft Flight Simulator’s simulation calculations?

A) GPU

B) CPU

C) RAM

D) SSD

Correct Answer: B) CPU

Question 2

What is the primary role of the GPU?

A) Download scenery

B) Render graphics and images

C) Store flight plans

D) Calculate aircraft physics

Correct Answer: B) Render graphics and images

Question 3

Why is stable frame pacing often more important than a high FPS number?

A) It reduces download speeds

B) It creates smoother, more consistent motion and reduces visible judder

C) It increases VRAM

D) It improves internet performance

Correct Answer: B)

Question 4

What is a CPU bottleneck?

A) The graphics card has run out of VRAM

B) The processor cannot prepare frames quickly enough, causing the GPU to wait

C) Windows needs updating

D) Your SSD is full

Correct Answer: B)

Question 5

Why should every benchmark use the same airport, aircraft and weather?

A) To make testing quicker

B) To ensure results are consistent and directly comparable

C) To improve FPS automatically

D) To reduce VRAM usage

Correct Answer: B)

Practical Assignment

Before moving on to Module 2, complete and save your Performance Baseline Report.

Your report should include:

• CPU model
• GPU model
• Installed RAM
• Storage type (HDD, SSD or NVMe SSD)
• Airport used for testing
• Aircraft used
• Weather preset
• Graphics preset
• Display resolution
• Average FPS
• Lowest FPS
• Highest FPS
• Main Thread or GPU limited
• Notes on frame pacing and any stutters observed

Store this report somewhere safe. It will be your benchmark throughout the rest of the Performance Academy.

Looking Ahead To Module 2

Congratulations—you’ve completed Module 1.

You now understand how Microsoft Flight Simulator uses your hardware, what causes bottlenecks and stutters, why frame pacing matters and how to measure performance properly.

In Module 2 – Preparing Your PC for Optimisation, we’ll put this knowledge into practice. We’ll begin by optimising Windows, updating drivers correctly, configuring power settings, reducing unnecessary background activity and preparing your system so it delivers the best possible performance before we even touch the simulator’s graphics settings.

By the end of Module 2, your PC will be ready for the detailed optimisation work that follows later in the academy.