Installing and Managing Scenery

Lesson Overview

Welcome to Module 15 of the Flight Sim Mastery Academy.

Scenery add-ons can transform Microsoft Flight Simulator by replacing basic airports and generic environments with:

  • Custom terminals.
  • Accurate runways and taxiways.
  • Airline-specific stands.
  • Custom jetways.
  • Detailed ground textures.
  • Hand-built landmarks.
  • Terminal interiors.
  • Static aircraft.
  • Airport vehicles and workers.
  • Regional terrain and city enhancements.

However, scenery is also one of the most common causes of:

  • Low FPS.
  • MainThread limitations.
  • High VRAM usage.
  • Long loading times.
  • Duplicate buildings.
  • Terrain spikes.
  • Floating objects.
  • Broken runways.
  • Jetway problems.
  • CTDs after simulator updates.

This lesson teaches students how to install scenery correctly, configure only the features they need, organise large scenery libraries and measure the true performance cost of each airport.

Students will learn how to manage scenery purchased from:

  • The Microsoft Flight Simulator Marketplace.
  • Developer stores.
  • External retailers.
  • Freeware websites.
  • Product managers.
  • Manually downloaded packages.

They will also learn how scenery management differs between MSFS 2020 and MSFS 2024.

In MSFS 2024, Marketplace and installed content can be reviewed through Marketplace → My Library, where packages can be downloaded, enabled or disabled. Community Folder items can also be checked from the Community section of My Library.  

Lesson Objectives

By the end of this module, students will be able to:

Distinguish Marketplace, external-store and manual scenery installations.

Identify the correct MSFS 2020 and MSFS 2024 package.

Install airports through official product managers.

Install manual Community Folder packages safely.

Understand scenery object libraries and dependencies.

Remove outdated versions correctly.

Detect duplicate airports.

Configure static aircraft and terminal interiors.

Configure jetways, ground vehicles and airport clutter.

Install and test GSX airport profiles.

Understand scenery package priority.

Build Add-ons Linker profiles.

Create regional scenery groups.

Compare default and third-party airport performance.

Measure FPS, 1% lows, MainThread, GPU load and VRAM.

Diagnose terrain and photogrammetry conflicts.

Test CTDs and Sim Update compatibility.

The Three-Step Structure

Step 1 – Installation

Students will learn how scenery packages enter the simulator and how to avoid installing the wrong version or creating duplicates.

Step 2 – Configuration and Management

Students will configure airport features, organise libraries and create profiles for different types of flying.

Step 3 – Performance and Compatibility Testing

Students will benchmark scenery and isolate conflicts involving terrain, photogrammetry, traffic, jetways and simulator updates.

STEP 1 – INSTALLATION AND UPDATES

Estimated Time: 12–15 Minutes

1. Understanding Scenery Package Types

Scenery can be divided into several categories.

Airport Scenery

Replaces or improves one airport.

Examples include:

  • Heathrow.
  • Frankfurt.
  • JFK.
  • Innsbruck.
  • Palma.
  • Small regional airports.

City Scenery

Adds:

  • Custom buildings.
  • Bridges.
  • Stadiums.
  • Skylines.
  • Harbours.
  • Landmarks.

Regional Scenery

May modify:

  • Terrain.
  • Coastlines.
  • Vegetation.
  • Roads.
  • Mesh.
  • Buildings.
  • Points of interest.

Object Libraries

Contain reusable assets required by other scenery packages.

Examples may include:

  • Vehicles.
  • People.
  • Hangars.
  • Signs.
  • Fences.
  • Lighting.
  • Animated objects.

Enhancement Packages

Modify an existing airport or region rather than replacing it completely.

Examples:

  • Removal of static aircraft.
  • Additional stands.
  • Improved taxi signs.
  • Custom jetways.
  • Better lighting.
  • GSX profiles.

Understanding the package type helps students determine whether two add-ons can coexist.

2. Marketplace Scenery

Marketplace scenery is purchased and managed inside Microsoft Flight Simulator.

Advantages include:

  • Centralised ownership.
  • Simple installation.
  • Automatic account association.
  • Easy access from the simulator library.
  • No need to locate the Community Folder manually.

Possible disadvantages include:

  • Updates may appear later than direct-store versions.
  • Package files may be protected or less accessible.
  • Developer configuration tools may be limited.
  • Troubleshooting can be harder when package contents cannot be inspected directly.

In MSFS 2024, owned content is managed through Marketplace → My Library, where individual packages can be downloaded, enabled or disabled.  

Marketplace Installation Procedure

  1. Launch the correct simulator.
  2. Open the Marketplace.
  3. Search for the airport or scenery.
  4. Confirm the product is for MSFS 2020 or MSFS 2024.
  5. Confirm the airport ICAO code.
  6. Review the product description.
  7. Complete the purchase.
  8. Open My Library or Content Manager.
  9. Download or enable the scenery.
  10. Restart the simulator where required.
  11. Load the airport using a default aircraft.
  12. Confirm that the scenery appears correctly.

Do not assume that every MSFS 2020 Marketplace product is a fully native MSFS 2024 product.

Always review the compatibility label.

3. External-Store Scenery

External scenery may be purchased from:

  • The developer’s own store.
  • iniBuilds.
  • Orbx.
  • Contrail-supported stores.
  • Aerosoft.
  • simMarket.
  • Just Flight.
  • Flight1.
  • Other authorised retailers.

External purchases may provide:

  • Faster updates.
  • Developer configuration tools.
  • Optional texture packs.
  • Static-aircraft controls.
  • Interior-detail options.
  • Better access to support.
  • Manual package visibility.

The installation method depends on the store and developer.

4. Product Managers

Many scenery developers use dedicated product managers.

Examples can include:

  • iniManager.
  • Orbx Central.
  • Aerosoft One.
  • Contrail.
  • Developer-specific installers.

A product manager may handle:

  • Installation.
  • Updates.
  • Simulator selection.
  • Optional features.
  • Libraries.
  • Liveries.
  • Repair.
  • Uninstallation.

Product Manager Installation Procedure

  1. Close MSFS.
  2. Download the official product manager.
  3. Sign into the account used for purchase.
  4. Allow it to detect installed simulators.
  5. Confirm whether MSFS 2020 or MSFS 2024 is selected.
  6. Confirm the installation path.
  7. Locate the scenery.
  8. Select Install.
  9. Install required libraries.
  10. Wait for completion.
  11. Record the installed version.
  12. Launch the simulator and test.

Never select a folder simply because it contains the word Community.

Confirm that it belongs to the correct simulator.

5. Manual Community Folder Installation

Some scenery arrives as a compressed ZIP or RAR archive.

The package usually contains a folder with files such as:

 

manifest.json
layout.json
scenery


 

 

The folder containing manifest.json and layout.json is normally the package folder that must be placed in the Community Folder.

Correct Manual Installation

  1. Close MSFS.
  2. Download the scenery from a trusted source.
  3. Scan the archive.
  4. Extract it to a temporary folder.
  5. Open the extracted folder.
  6. Locate the actual package folder.
  7. Confirm manifest.json and layout.json are directly inside it.
  8. Copy the package folder into the correct Community Folder.
  9. Launch the simulator.
  10. Confirm the package appears.

Incorrect Folder Nesting

Community
└── HeathrowScenery-v2
└── HeathrowScenery-v2
├── manifest.json
└── layout.json


 

 

Correct


Community
└── HeathrowScenery-v2
├── manifest.json
└── layout.json


 

 

Nested folders are a common reason manually installed scenery does not appear.

6. MSFS 2020 Community Folder

The default location depends on whether MSFS 2020 was installed through:

  • Microsoft Store or Xbox.
  • Steam.
  • Retail disc.
  • A custom package path.

Microsoft’s support documentation lists different default Community Folder locations for these installation types, although users may also choose a custom Packages location.  

The safest way to confirm the active folder is to inspect the simulator’s package path rather than relying entirely on a copied path from a tutorial.

7. MSFS 2024 Community Folder

MSFS 2024 uses its own Community Folder.

Do not treat it as the same folder as MSFS 2020.

To confirm a manually installed MSFS 2024 add-on:

  1. Launch MSFS 2024.
  2. Open Marketplace.
  3. Open My Library.
  4. Select the Community category.
  5. Search for the installed package.

Microsoft’s support guidance states that correctly detected Community Folder content should appear in this section.  

8. MSFS 2020 vs MSFS 2024 Packages

Some developers provide:

  • One MSFS 2020 package.
  • A compatible MSFS 2024 package.
  • A separate native MSFS 2024 edition.
  • One installer that selects the appropriate version.

Do not manually copy MSFS 2020 scenery into MSFS 2024 unless the developer confirms compatibility.

Possible problems include:

  • Missing buildings.
  • Floating objects.
  • Incorrect terrain.
  • Broken materials.
  • Jetway errors.
  • Performance problems.
  • CTDs.
  • Incorrect package priority.

Always read the product documentation.

9. Object Libraries

Some airports depend on shared object libraries.

A library may be required for:

  • Terminal furniture.
  • People.
  • Ground vehicles.
  • Hangars.
  • Signs.
  • Lighting.
  • Static aircraft.
  • Vegetation.

If a required library is missing, scenery may show:

  • Empty areas.
  • Missing buildings.
  • Pink or blank textures.
  • Missing vehicles.
  • Error messages.
  • CTDs in severe cases.

Library Management Rules

  • Install only the current version.
  • Do not keep several copies.
  • Do not rename the library package.
  • Do not remove it while dependent scenery remains active.
  • Record which airports use it.
  • Update it through the same manager used for installation.

A large shared library is usually better than several duplicated copies of the same objects.

10. Installing Updates

Before updating scenery:

  1. Close MSFS.
  2. Open the store or product manager.
  3. Record the current version.
  4. Read the changelog.
  5. Check for simulator-version requirements.
  6. Remove the older version if instructed.
  7. Install the new version.
  8. Check optional settings.
  9. Restart the product manager.
  10. Test the airport with default conditions.

Updates may change:

  • Package names.
  • Jetways.
  • GSX compatibility.
  • Static aircraft.
  • Terrain.
  • Textures.
  • Terminal interiors.
  • Performance.

11. Removing Older Versions

Do not simply place the new package beside the old one.

Old versions may have names such as:

egll-airport
egll-airport-v2
egll-airport-old
egll-airport-backup


 

 

If all remain inside the Community Folder, the simulator may load more than one version.

Correct Update Workflow

  1. Close MSFS.
  2. Identify the old package.
  3. Remove or disable it.
  4. Install the new package.
  5. Check for a renamed folder.
  6. Check required libraries.
  7. Clear only the scenery-specific cache if the developer recommends it.
  8. Launch the simulator.
  9. Inspect the airport.

Do not keep backup folders inside the active Community Folder.

Store backups elsewhere.

12. Avoiding Duplicate Airports

Duplicate scenery occurs when two packages modify the same airport.

Common causes include:

  • Marketplace version plus external-store version.
  • Old version plus updated version.
  • Freeware airport plus payware airport.
  • World Update airport plus third-party airport.
  • MSFS 2020 compatibility package plus native 2024 package.
  • Airport enhancement plus full airport replacement.
  • Two regional packages covering the same location.

Duplicate Scenery Symptoms

  • Double terminals.
  • Multiple control towers.
  • Duplicate jetways.
  • Flickering surfaces.
  • Floating buildings.
  • Uneven runways.
  • Duplicate taxi signs.
  • Severe MainThread load.
  • CTDs while loading.

Duplicate Check

For each airport, record:

ICAO:

Developer:

Store:

Version:

Simulator:

Package folder:

World Update version active: Yes / No

Enhancement packages active:

Only one full replacement should normally be active.

13. First Airport Test

After installation, use:

  • Default aircraft.
  • Clear Skies.
  • Daytime.
  • No traffic.
  • No GSX.
  • No external weather.
  • Default livery.

Inspect:

  • Runways.
  • Taxiways.
  • Jetways.
  • Terminal buildings.
  • Terrain.
  • Night lighting where relevant.
  • Windsocks.
  • Signs.
  • Stand positions.
  • FPS and frame pacing.

Do not combine the first test with a complex aircraft and maximum traffic.

STEP 2 – CONFIGURATION AND SCENERY MANAGEMENT

Estimated Time: 18–20 Minutes

14. Airport Configuration Tools

Many scenery packages include a configuration application.

Possible options include:

  • Static aircraft.
  • Terminal interiors.
  • High-resolution textures.
  • Animated people.
  • Ground clutter.
  • Landside traffic.
  • Custom jetways.
  • VDGS.
  • Seasonal textures.
  • Optional city landmarks.
  • Satellite imagery.

Configure the airport before launching MSFS where required.

15. Build a Default Airport Profile

For the initial test, use a balanced profile.

Recommended starting point:

  • Static aircraft off.
  • Terminal interiors reduced or off.
  • Standard textures.
  • Animated people reduced.
  • Ground clutter medium.
  • Custom jetways on.
  • Essential objects on.
  • Optional city scenery off initially.

This establishes the core airport performance before optional features are added.

16. Static Aircraft

Static aircraft improve visual atmosphere but can create several problems.

They may:

  • Use CPU draw calls.
  • Use GPU resources.
  • Use VRAM.
  • Block gates.
  • Duplicate injected traffic.
  • Interfere with GSX.
  • Display incorrect airlines.
  • Make busy airports appear overcrowded.

Disable static aircraft when using:

  • FSLTL.
  • BeyondATC traffic.
  • VATSIM.
  • AIG.
  • MSFS Live Traffic.
  • Another traffic injector.

Keep them only when flying offline without injected traffic and when the performance cost is acceptable.

17. Terminal Interiors

Detailed terminal interiors may include:

  • Seating.
  • Shops.
  • Signs.
  • People.
  • Furniture.
  • Lighting.
  • Glass.
  • Interior textures.

These can increase:

  • Draw calls.
  • VRAM use.
  • GPU load.
  • Loading time.
  • Night-lighting cost.

Ask:

Can the interior actually be seen from the cockpit?

If not, disabling it may offer a worthwhile performance saving with little visual loss.

18. High-Resolution Textures

Some scenery offers:

  • Standard textures.
  • 4K textures.
  • 8K textures.
  • Performance textures.

Higher-resolution textures improve close-up detail but increase:

  • Download size.
  • Storage use.
  • VRAM.
  • Loading time.
  • Texture-streaming pressure.

Recommended approach:

8 GB VRAM

Use standard or lower-resolution textures.

12–16 GB VRAM

Use high-resolution textures selectively.

20 GB or More

Higher-resolution packages may be suitable, but still test them with complex aircraft and traffic.

The airport, aircraft, livery and weather all compete for VRAM.

19. Custom Jetways

Custom jetways improve realism but can introduce:

  • Misalignment.
  • Incorrect door connection.
  • Animation problems.
  • Duplicate jetways.
  • GSX conflicts.
  • Additional object load.

Test:

  1. Default aircraft.
  2. Complex airliner.
  3. Native jetway operation.
  4. GSX jetway operation.
  5. Passenger boarding.
  6. Pushback.

If two jetway systems are active, disable one where required.

20. GSX Profiles

A GSX airport profile may configure:

  • Stand positions.
  • Stop points.
  • Jetway doors.
  • Passenger paths.
  • Pushback routes.
  • Handling operators.
  • Catering operators.
  • Bus positions.
  • Vehicle locations.

GSX Profile Installation

  1. Confirm the profile is designed for the exact scenery developer.
  2. Confirm the scenery version.
  3. Check the airport ICAO.
  4. Follow the profile creator’s installation instructions.
  5. Remove older versions.
  6. Start MSFS.
  7. Load at the correct stand.
  8. Reposition the aircraft if required.
  9. Test boarding and pushback.

A profile made for the default airport may not work with a third-party version.

21. Ground Vehicles

Airport scenery may contain its own:

  • Buses.
  • Baggage carts.
  • Fuel trucks.
  • Catering vehicles.
  • Service cars.
  • Animated workers.

MSFS and GSX may also create vehicles.

Using all systems together can cause:

  • Duplicate vehicles.
  • Clipping.
  • Blocked taxiways.
  • MainThread load.
  • Stuttering.

Choose one primary source of detailed ground services.

22. Worker Density

Animated workers add movement but increase CPU workload.

Test:

  • Workers off.
  • Workers low.
  • Workers medium.
  • Workers high.

Observe:

  • FPS.
  • 1% lows.
  • MainThread.
  • Taxi smoothness.

At busy hubs, reducing workers can improve performance without significantly changing the cockpit experience.

23. Scenery Priority

When several packages modify the same area, the simulator’s package loading order determines which package takes priority.

The MSFS SDK documentation describes package priority as a mount order running from lower to higher priority. Some packages may be locked and cannot be reordered.  

Priority may matter for:

  • Airport replacements.
  • Terrain corrections.
  • Static-aircraft removal packages.
  • Jetway modifications.
  • Navigation-data packages.
  • Regional scenery.
  • Compatibility patches.

Do not change package order randomly.

Change it only when:

  • The developer instructs you.
  • A compatibility patch requires higher priority.
  • Two packages clearly conflict.
  • Testing proves the order matters.

24. Package Reorder Tool

The Package Reorder Tool can be accessed through Developer Mode tools.

It shows:

  • Active packages.
  • Package priority.
  • Locked packages.
  • Custom priority values.
  • Mount order.

The SDK documentation notes that priorities can use negative values and that packages mount from the lowest to highest priority.  

Safe Reorder Workflow

  1. Record the existing order.
  2. Identify the exact conflicting packages.
  3. Read developer instructions.
  4. Change one priority.
  5. Restart MSFS.
  6. Test the airport.
  7. Reverse the change if it does not help.

Do not reorder hundreds of packages based on an old forum screenshot.

25. Add-ons Linker

MSFS Addons Linker is a community utility that stores add-ons outside the Community Folder and creates links to activate selected packages.

Its listed functions include:

  • Custom storage folders.
  • Enabling and disabling groups.
  • Saved presets.
  • Package organisation.
  • Separate add-on locations.  

It is not an official Microsoft tool.

Students should test it carefully, particularly when using both MSFS 2020 and MSFS 2024.

Example Add-on Library

D:\MSFS Add-ons
├── Airports
│ ├── United Kingdom
│ ├── Europe
│ ├── North America
│ └── Islands
├── City Scenery
├── Object Libraries
├── Aircraft
├── Liveries
├── Utilities
└── Disabled


 

 

26. Add-ons Linker Profiles

Create profiles for different flight types.

European Airline Profile

Enable:

  • European airports.
  • Required object libraries.
  • GSX profiles.
  • Airline aircraft.
  • Relevant utilities.

UK Domestic Profile

Enable:

  • UK airports.
  • UK landmarks.
  • UK regional enhancements.
  • Required libraries.

North America Profile

Enable:

  • US and Canadian airports.
  • Relevant city packs.
  • Required libraries.

VFR Profile

Enable:

  • Regional terrain.
  • Landmarks.
  • Small airports.
  • Vegetation enhancements.

Troubleshooting Profile

Enable only:

  • One aircraft.
  • One airport.
  • Required libraries.

27. Avoid Linking Every Add-on

The purpose of Add-ons Linker is not to activate everything permanently.

Activating thousands of packages may still increase:

  • Package scanning.
  • Loading times.
  • Conflict risk.
  • Troubleshooting difficulty.

Enable only what the planned flight needs.

28. Regional Scenery Setups

A regional profile should contain scenery relevant to the route.

Example

EGLL to LEPA


 

 

Enable:

  • Heathrow.
  • Palma.
  • Relevant UK and Spanish landmarks.
  • Required libraries.
  • GSX profiles.
  • Optional en-route scenery only when useful.

Disable:

  • North American airports.
  • Asian airport packs.
  • Unrelated city packs.
  • Unused liveries and utilities.

This reduces the active variables during troubleshooting.

29. Airport-Specific Profiles

Very demanding airports may need their own configuration.

Example Heathrow profile:

  • Static aircraft off.
  • Terminal interiors off.
  • Standard textures.
  • Workers low.
  • Ground vehicles low.
  • AI traffic reduced.
  • Object LOD lowered.
  • GSX profile enabled.
  • Nearby city enhancement tested separately.

Example Innsbruck profile:

  • Terrain LOD higher.
  • Airport interiors optional.
  • Photogrammetry tested.
  • Mountain mesh enabled.
  • Traffic kept low.

The best configuration depends on the airport workload.

30. Scenery Documentation Sheet

Record each airport 

 

 

Field

Information

Airport ICAO

Developer

Store

Simulator

Version

Package folder

Required libraries

Static aircraft

On / Off

Interiors

On / Off

Texture package

GSX profile

Known conflicts

Normal Fps 

Normal VRAM


 


 

This becomes the student’s scenery database.

STEP 3 – PERFORMANCE AND COMPATIBILITY TESTING

Estimated Time: 12–15 Minutes

31. Default vs Add-On Airport Benchmark

A fair scenery test requires identical conditions.

Use:

  • Same aircraft.
  • Same parking stand or location.
  • Same weather.
  • Same time.
  • Same camera angle.
  • Same graphics settings.
  • Same traffic.
  • Same simulator version.

Test:

  1. Default airport.
  2. Third-party airport.
  3. Third-party airport with optional features reduced.
  4. Third-party airport with full features.

32. Record the Correct Metrics

Measure:

  • Average FPS.
  • Minimum FPS.
  • 1% lows.
  • Frame times.
  • MainThread status.
  • GPU utilisation.
  • VRAM usage.
  • RAM usage.
  • Loading time.
  • Stutter locations.

Do not judge an airport using maximum FPS alone.

33. FPS Comparison

Example

Configuration

Average FPS

Default airport

70

Add-on airport full

43

Add-on airport optimised

55

The result shows both:

  • The cost of the scenery.
  • The performance recovered through configuration.

34. 1% Lows

1% lows reveal how the airport feels during demanding moments.

Test while:

  • Panning across the terminal.
  • Taxiing near parked aircraft.
  • Passing jetways.
  • Using GSX.
  • Approaching the runway.
  • Looking towards the city.

An airport may average 50 FPS but still feel poor if its 1% lows fall to 20 FPS.

35. MainThread Testing

Airports can increase CPU workload through:

  • Draw calls.
  • Objects.
  • Jetways.
  • Vehicles.
  • Workers.
  • Static aircraft.
  • AI traffic.
  • Building density.
  • Animation.

Signs of a MainThread problem:

  • GPU utilisation falls.
  • FPS drops.
  • Developer Mode shows MainThread limitation.
  • Lowering resolution provides little improvement.

Test:

  • Static aircraft off.
  • Workers reduced.
  • Ground vehicles reduced.
  • Traffic reduced.
  • Object LOD lowered.
  • Terminal interiors disabled.

36. GPU Load Testing

Scenery can increase GPU load through:

  • High-resolution textures.
  • Glass.
  • Reflections.
  • Night lighting.
  • Shadows.
  • Terminal interiors.
  • Large city scenery.
  • High render resolution.

Signs of GPU limitation:

  • GPU utilisation reaches 95–100%.
  • Lowering resolution improves FPS.
  • VRAM use rises.
  • GPU frame time exceeds CPU frame time.

Test:

  • Texture Resolution.
  • Render Scaling.
  • Shadows.
  • Reflections.
  • High-resolution texture option.
  • Terminal interiors.
  • Night lighting.

37. VRAM Testing

Measure VRAM:

  • Default airport.
  • Add-on airport.
  • Default livery.
  • High-resolution livery.
  • Cockpit.
  • Exterior view.
  • Day.
  • Night.

Signs of VRAM pressure include:

  • Texture pop-in.
  • Blurry textures.
  • Panning stutters.
  • Long pauses.
  • Severe frame-time spikes.
  • Performance degradation during approach.

The scenery, aircraft and livery all contribute to the total.

38. Loading-Time Testing

Measure:

Simulator Startup

Launch to main menu.

Flight Loading

Press Fly to cockpit-ready.

Scenery Initialisation

Time until:

  • Objects appear.
  • Textures become sharp.
  • Jetways load.
  • Ground services respond.

Compare

Configuration

Loading Time

Default airport

Add-on airport

Add-on plus interiors

Add-on plus full library

39. Duplicate Scenery Test

If an airport behaves incorrectly:

  1. Search Marketplace My Library.
  2. Search the Community Folder.
  3. Search Add-ons Linker.
  4. Check product managers.
  5. Check World Updates.
  6. Check airport-enhancement packages.
  7. Disable every version.
  8. Enable only one airport package.
  9. Restart MSFS.
  10. Retest.

Symptoms that disappear after this process strongly suggest duplication.

40. Terrain Conflicts

Terrain conflicts may create:

  • Trenches.
  • Hills on runways.
  • Floating terminals.
  • Sunken roads.
  • Water climbing onto land.
  • Terrain spikes.
  • Uneven aprons.
  • Mismatched coastlines.

Possible causes include:

  • Airport terraforming.
  • Regional mesh.
  • City enhancement.
  • Photogrammetry.
  • World Update scenery.
  • Two airport versions.
  • Outdated compatibility patch.

Terrain Conflict Test

  1. Load the airport with all scenery active.
  2. Capture screenshots.
  3. Disable regional mesh.
  4. Retest.
  5. Disable photogrammetry.
  6. Retest.
  7. Disable World Update airport content if appropriate.
  8. Retest.
  9. Check package priority.
  10. Install the developer’s compatibility patch if available.

Change one variable at a time.

41. Photogrammetry Overlap

Photogrammetry may overlap with hand-built scenery.

Possible symptoms:

  • Melted buildings beside custom terminals.
  • Duplicate skylines.
  • Floating structures.
  • Incorrect terrain height.
  • Stutters as city data streams.
  • Poor visual transitions.

Test:

  1. Photogrammetry on.
  2. Photogrammetry off.
  3. City add-on on.
  4. City add-on off.
  5. Airport only.
  6. Airport plus city enhancement.

Choose the combination with the best visual and performance balance.

42. Night Performance

Night lighting can increase GPU workload.

Test:

  • Day.
  • Sunset.
  • Night.
  • Rain at night.

Monitor:

  • GPU utilisation.
  • VRAM.
  • Reflections.
  • Terminal glass.
  • Apron lighting.
  • Frame times.

An airport that performs well in daylight may be more demanding at night.

43. Traffic and Scenery Combined Test

Test the airport with:

  1. No traffic.
  2. Moderate traffic.
  3. Heavy traffic.
  4. GSX active.
  5. Static aircraft enabled.
  6. Injected traffic enabled.

Do not combine static aircraft and maximum injected traffic without testing.

Record how the combined workload changes MainThread and 1% lows.

44. CTD Testing

If the airport causes a CTD:

  1. Record the exact location.
  2. Record the aircraft.
  3. Record the scenery version.
  4. Check Reliability Monitor.
  5. Check Event Viewer.
  6. Test a default aircraft.
  7. Test with the default livery.
  8. Disable traffic.
  9. Disable GSX.
  10. Disable surrounding scenery.
  11. Test with only the airport and required libraries.
  12. Reinstall the airport only after controlled testing.

Microsoft’s Safe Mode disables third-party Marketplace content and Community Folder modifications temporarily, making it useful for determining whether third-party content is involved. Microsoft also recommends reactivating packages individually when isolating the cause.  

45. MSFS 2024 Vanilla Test

For MSFS 2024 troubleshooting, Microsoft recommends disabling third-party streamed packages through My Library and renaming the Community Folder temporarily to test a clean simulator state.  

Use this only as a controlled diagnostic test.

Do not permanently delete the Community Folder before confirming backups.

46. Sim Update Compatibility

After a Sim Update:

  1. Read the scenery developer’s compatibility notice.
  2. Update the airport.
  3. Update required libraries.
  4. Disable old compatibility patches.
  5. Test the default airport.
  6. Test the add-on airport alone.
  7. Check jetways.
  8. Check terrain.
  9. Check GSX.
  10. Run a benchmark.
  11. Re-enable surrounding scenery gradually.

Do not assume the simulator update caused permanent performance loss until scenery and libraries have been tested.

47. World Update Compatibility

World Updates can add or alter:

  • Airports.
  • Photogrammetry.
  • Terrain.
  • City scenery.
  • Landmarks.

After installing a World Update:

  • Check whether it includes the same airport.
  • Disable the default handcrafted airport when required.
  • Test terrain.
  • Test city overlap.
  • Review developer compatibility notes.
  • Check package priority.

48. Conflict Escalation Process

Level 1 – Configuration

Disable:

  • Static aircraft.
  • Interiors.
  • Workers.
  • High-resolution textures.

Level 2 – Surrounding Add-ons

Disable:

  • City scenery.
  • Mesh.
  • Photogrammetry enhancements.
  • Regional packs.

Level 3 – Traffic and Utilities

Disable:

  • GSX.
  • Traffic injectors.
  • Camera tools.
  • Weather tools.

Level 4 – Clean Scenery Profile

Enable only:

  • Airport.
  • Required libraries.
  • Default aircraft.

Level 5 – Repair

  • Reinstall the airport.
  • Reinstall libraries.
  • Reset package priority.
  • Contact the scenery developer.

Common Problems

Airport Does Not Appear

Check:

  • Correct simulator.
  • Correct Community Folder.
  • Folder nesting.
  • Product manager path.
  • Package enabled.
  • Required library.
  • Simulator restarted.

Default Airport Still Appears

Check:

  • Duplicate full airport.
  • Package priority.
  • Marketplace version.
  • World Update version.
  • Incorrect ICAO.
  • Add-on disabled.

Buildings Are Missing

Check:

  • Object libraries.
  • Package installation.
  • Correct simulator version.
  • Texture package.
  • Scenery update.

Double Jetways

Check:

  • Default airport still active.
  • Two scenery versions.
  • GSX replacement jetways.
  • Compatibility patch.
  • Package priority.

Aircraft Park Inside Buildings

Check:

  • GSX profile version.
  • Parking-position update.
  • World Map stand.
  • Airport scenery version.
  • Old profile.

Very Low FPS

Check:

  • Static aircraft.
  • Interiors.
  • AI traffic.
  • Workers.
  • Ground vehicles.
  • Object LOD.
  • High-resolution textures.
  • Premium aircraft.
  • VRAM.

Terrain Spikes or Trenches

Check:

  • Regional mesh.
  • Photogrammetry.
  • World Update.
  • Two airports.
  • Compatibility patch.
  • Package order.

Airport CTD

Test:

  • Default aircraft.
  • Default livery.
  • No traffic.
  • No GSX.
  • Only required scenery packages.
  • Current version.
  • Safe Mode.

Student Practical Assignment

Install, Configure and Benchmark One Airport

Choose one third-party airport.

Part 1 – Installation Record

Airport ICAO:

Developer:

Store:

Simulator: MSFS 2020 / MSFS 2024

Airport version:

Installation method:

Package folder:

Required libraries:

Marketplace version present: Yes / No

World Update airport present: Yes / No

Part 2 – Configuration

Static aircraft: On / Off

Terminal interiors: On / Off

Texture package:

Workers:

Ground vehicles:

Custom jetways: On / Off

GSX profile:

Regional scenery active:

Photogrammetry: On / Off


Part 3 – Benchmark

Measurement

Default Airport

Add-On Full

Add-On Optimised

Loading time

Average FPS

1% Low

MainThread status

GPU utilisation

VRAM usage

RAM usage

Night FPS

Approach smoothness

Part 4 – Conflict Tests

Confirm:

☐ Duplicate airport search completed.

☐ World Update content checked.

☐ Object libraries checked.

☐ Terrain mesh tested.

☐ Photogrammetry tested.

☐ Traffic tested.

☐ GSX tested.

☐ Package priority reviewed.

☐ Default scenery restored successfully.

Part 5 – Final Assessment

Answer:

  • Is the visual improvement worth the performance cost?
  • Which feature caused the largest FPS reduction?
  • Did static aircraft create duplicate traffic?
  • Did interiors create noticeable VRAM pressure?
  • Was the airport MainThread or GPU limited?
  • Did photogrammetry create conflicts?
  • Did the airport remain stable after restart?
  • Is the airport ready for normal flights?

Student Checklist

Marketplace installation understood.

External-store installation understood.

Community Folder package installed correctly.

Product manager configured.

MSFS 2020 and 2024 folders separated.

Object libraries installed.

Updates checked.

Old versions removed.

Duplicate airport search completed.

Airport configuration tool reviewed.

Static aircraft configured.

Terminal interiors tested.

Texture resolution selected.

Jetways tested.

GSX profile installed.

Ground vehicles tested.

Package priority understood.

Add-ons Linker profile created.

Regional profile created.

Default and add-on airports compared.

FPS measured.

1% lows measured.

MainThread monitored.

GPU load monitored.

VRAM measured.

Loading time measured.

Terrain conflicts tested.

Photogrammetry overlap tested.

CTD workflow understood.

Sim Update compatibility checked.

Lesson Summary

You have now learned how to install, configure, organise and test airport and world scenery in Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024.

Remember:

  • Install the version designed for your simulator.
  • Keep MSFS 2020 and MSFS 2024 Community Folders separate.
  • Marketplace, product-manager and manual installations require different management methods.
  • Remove old versions before installing major updates.
  • Do not keep backup scenery inside the active Community Folder.
  • Install required object libraries once and keep them updated.
  • Only one full replacement of an airport should normally be active.
  • Static aircraft should usually be disabled when using injected traffic.
  • Terminal interiors and high-resolution textures can increase GPU and VRAM load.
  • Airport workers, vehicles and objects can increase MainThread workload.
  • Use package priority only when a documented conflict requires it.
  • Add-ons Linker profiles are most useful when they activate only the scenery required for the planned flight.
  • Benchmark the default, full and optimised airport under identical conditions.
  • Measure 1% lows and frame times, not only average FPS.
  • Test terrain, photogrammetry, World Updates and city scenery independently.
  • Use Safe Mode or a temporary vanilla profile when third-party content is strongly suspected.
  • Reinstall the simulator only after the airport, libraries and surrounding scenery have been isolated.

Knowledge Check

  1. What are the three main ways scenery can be installed?
  2. How is MSFS 2024 Marketplace content enabled or disabled?
  3. Why must MSFS 2020 and 2024 packages remain separate?
  4. What files normally identify the root of a Community Folder package?
  5. Why can nested package folders prevent scenery loading?
  6. What is an object library?
  7. Why should old airport versions be removed?
  8. What are common symptoms of duplicate scenery?
  9. Why can static aircraft conflict with VATSIM or FSLTL?
  10. How can terminal interiors affect performance?
  11. Why may 8K textures create problems?
  12. What is the purpose of an airport configuration tool?
  13. What does a GSX profile configure?
  14. Why can several ground-service systems create duplicate vehicles?
  15. What is scenery package priority?
  16. Why should package order not be changed randomly?
  17. What is the purpose of Add-ons Linker profiles?
  18. How can regional profiles reduce troubleshooting complexity?
  19. What metrics should be recorded during an airport benchmark?
  20. What indicates a MainThread-limited airport?
  21. What indicates a GPU-limited airport?
  22. What are common signs of VRAM pressure?
  23. How can photogrammetry conflict with hand-built scenery?
  24. What should be tested after a World Update?
  25. When should Safe Mode be used?
1 2 3 4 5 6 7 ADD-ON Masterclass