Find MSFS 2020 SDK sample projects, open them in Project Editor, build packages correctly, and fix missing samples or failed builds.
MSFS 2020 SDK sample projects are normally installed in the Samples folder inside the SDK location you selected, commonly C:\MSFS SDK\Samples. Copy a sample to a writable work folder, enable Developer Mode, open its top-level project XML in Project Editor, then use Build All to compile and test its package.
Where are the MSFS 2020 SDK samples installed?
The samples belong to the separate SDK installation, not the simulator's Community folder. Look inside the SDK destination selected during installation for directories such as Samples, Documentation and Tools; the exact drive and parent folder can differ.
If the SDK is not installed, obtain its installer from the Developer Mode Help menu. Our SDK installation and first-project walkthrough covers the installer, documentation and basic build process.
If the SDK exists but Samples does not, check that you are looking at the active installation rather than an older SDK folder. Run the installer offered by your installed copy of MSFS 2020 and use its repair or reinstall option if necessary.
How do I open and build a sample project?
- Copy the entire sample folder. Put it in a writable development directory. Do not copy only the project XML because its relative links to
PackageDefinitions,PackageSourcesand other assets will break. - Read the included notes. A scenery sample may specify coordinates, while code and gauge samples can require additional compilers or tools.
- Enable Developer Mode. If its menu bar is missing, follow our explanation of the Developer Mode controls and project tools.
- Open Project Editor. In MSFS 2020, select
Tools, thenProject Editor, chooseOpen Projectand open the top-level XML file in the sample's root folder. Do not select an XML file buried insidePackageDefinitions. - Build the package. Select the project or package and use
Build All. Watch the Developer Mode console for the first error rather than relying only on the final build status. - Test the result. Keep editor-based projects loaded while inspecting them in the simulator. Scenery must be viewed at the coordinates stated by the sample; our practical Scenery Editor workflow explains how to load, place, build and check scenery assets.
Built packages normally appear beneath the project's Packages directory. For a consumer-style test, use the resulting package folder containing manifest.json and layout.json. Do not put the source project XML, PackageDefinitions or unbuilt PackageSources in the Community folder.
Which sample project should I start with?
Choose the smallest sample that uses the same asset and build process as the add-on you intend to create.
| Sample type | How it is used | Best for |
|---|---|---|
| Scenery package | Open the root project XML in Project Editor, then work with its scenery asset group | Airports, objects and local scenery |
| Aircraft or model package | Build through Package Builder after exporting the required model assets | Aircraft, cockpit and animated model work |
| Gauge or WASM sample | Prepare its required compiler toolchain before building the package | Custom systems, gauges and compiled modules |
| SimConnect sample | Open its source or solution in the appropriate development environment rather than Project Editor | External applications communicating with MSFS 2020 |
Model-based samples are not complete until their source assets have been exported into the expected package structure. Our guide to configuring the MSFS Blender exporter and ModelLib workflow covers that extra stage.
Why will an SDK sample not build or appear?
Most sample failures come from opening the wrong XML, breaking relative paths or testing an unbuilt source folder.
- Project Editor opens nothing: select the XML at the sample project's root, not a package-definition or asset XML.
- Access denied or files are read-only: work from a writable copy instead of modifying the SDK installation directory.
- Models or textures are missing: copy the complete sample tree and confirm that any required exporter has generated its output under
PackageSources. - The build succeeds but nothing is visible: check the sample's coordinates, load the correct flight area and examine the Developer Mode console for asset-loading errors.
- Old content appears instead of the edited sample: remove any earlier package with the same identity from
Community, rebuild, then reload or restart the simulator. - Compiler or schema errors appear: use the SDK supplied through the same MSFS 2020 installation. An old SDK copy can contain tools or definitions that no longer match the simulator build.
Can I use an SDK sample as my own add-on template?
Yes, but first copy it, rename its project and package identifiers, and change its output paths so it cannot overwrite or conflict with the original sample. Retain only the components your add-on needs; unused asset groups make build errors harder to diagnose.
Before distributing anything derived from a sample, read its included licence and documentation. The presence of source files in the SDK does not automatically make every model, texture, name or third-party component redistributable.