FSX scenery does not install directly in MSFS 2020 or 2024. Learn what can be converted, what must be rebuilt, and why copying BGL files fails.
No. FSX scenery is not directly compatible with Microsoft Flight Simulator 2020 or 2024. Copying an FSX scenery folder or its BGL files into the MSFS Community folder will not install it. The airport must be rebuilt or converted into a valid MSFS package, and some assets may need replacing.
Why does FSX scenery not work in MSFS?
FSX and modern Microsoft Flight Simulator use different scenery engines, asset formats and packaging systems. Both may contain files with the .bgl extension, but that shared extension does not mean the compiled data inside is interchangeable.
MSFS expects an add-on package containing files such as manifest.json and layout.json, with assets prepared through the MSFS development tools. FSX scenery-library registration and a folder of legacy BGL and texture files do not meet those requirements.
| FSX scenery element | What is required for MSFS |
|---|---|
| Runways, taxiways and aprons | Rebuild or convert the airport layout, then compile it with the MSFS SDK. |
| Custom MDL objects in BGL files | Convert from suitable source files into supported MSFS models, with materials, levels of detail and collision data checked. |
| BMP or legacy DDS textures | Convert or recreate the textures and configure modern material properties. |
| Landclass, vector and terrain BGLs | Rebuild them using MSFS terrain, polygon, exclusion and elevation tools. |
| FSX effects and animations | Recreate them using features supported by the MSFS SDK. |
Can FSX scenery be converted to Microsoft Flight Simulator?
Some FSX scenery can be converted, but conversion is a development job rather than an installation shortcut. A basic airport made from runways, aprons and stock objects is a much better candidate than a complex product containing custom models, animations, terrain work and legacy effects.
Access to the original project and model source files makes a major difference. With only compiled BGL files, extraction may be incomplete, materials can break and some data may have to be recreated manually. Our guide to which legacy scenery elements can be converted or must be rebuilt explains those limits in more detail.
Copyright also applies. Owning an FSX scenery package does not automatically grant permission to extract its models or distribute a converted version. Check the original licence and obtain the author's permission before sharing any conversion.
What happens if I copy an FSX BGL into the Community folder?
Usually, the scenery simply fails to appear. A loose FSX BGL is not a complete MSFS package, and putting it inside a folder does not convert its airport records, models or textures.
Partially converted or incorrectly packaged scenery can produce other faults:
- missing buildings, textures or ground markings;
- floating or sunken runways caused by different elevation data;
- duplicate taxiways, aprons or buildings where the default airport remains active;
- objects appearing with incorrect scale, materials or placement;
- package-loading errors and conflicts with another airport add-on.
Do not place legacy files in the simulator's protected official-content folders. Remove the failed package and use the normal Community-package system described in our MSFS scenery installation and management guidance.
What is the safest way to move an FSX airport to MSFS?
- Look for a native MSFS edition. A purpose-built package will normally be cleaner and more reliable than an automated conversion. Our MSFS freeware library is a useful place to check for an existing replacement.
- Confirm the licence and source files. Make sure you have permission to convert the scenery and access to the original models and textures where possible.
- Assess the complexity. Airport layouts may provide a usable starting point, while custom objects, terrain, effects and animations often need substantial manual work.
- Build a valid MSFS project. Use the simulator's SDK to recreate the airport and compile a proper package. The full workflow is covered in our guide to building custom scenery with the MSFS SDK.
- Test without unrelated add-ons. Disable other Community scenery temporarily, then inspect runway alignment, elevations, parking positions, lighting, textures and night appearance.
- Check for conflicts. Re-enable other packages one at a time and remove duplicate versions of the same airport.
Does this apply to both MSFS 2020 and MSFS 2024?
Yes. Neither Microsoft Flight Simulator 2020 nor Microsoft Flight Simulator 2024 directly accepts original FSX scenery. A converted package should be tested in the specific modern simulator for which it is intended, even if an MSFS 2020 version appears to load in MSFS 2024.
Manual conversion and Community-folder installation are PC workflows. Xbox Series X|S and PlayStation 5 users cannot copy ordinary FSX scenery folders into the simulator; console scenery must be supplied through the platform's supported in-simulator distribution system.