Skip to main content
You create most contributions in the browser. You only need the simulator when you perform the final in-simulator test.

​
Before you start

Sign in to your BARS account before opening the contribution flow.
Have these ready:
  • The four-character ICAO code for the airport.
  • The exact scenery package you want to support.
  • MSFS 2020, MSFS 2024, or X-Plane installed with that scenery.
  • The BARS Pilot Client installed for the in-simulator test.
  • A desktop browser that can select a local folder.
Use the same scenery package when you create, edit, and test the draft. If you reconnect a different package, the editor warns that the scenery no longer matches the draft source.

​
Check the airport

The airport’s division must have supplied lighting data and enabled contributions. The review page shows a clear message when either requirement is missing. You can contribute another scenery package for an airport that already has approved contributions. Each scenery and simulator combination has its own submission.

​
Start from the dashboard

Open the Contribution Dashboard. It has two views:
  • All Contributions lists approved airport and scenery combinations. You can search by airport, scenery, or simulator and download an approved XML file.
  • Your Contributions shows your approved, pending, and rejected submissions. It also shows a status summary.
The leaderboard lists the community’s top contributors.
BARS Contribution Dashboard with the All Contributions and Your Contributions tabs, search field, leaderboard, and Contribute New Airport button

Use Contribute New Airport to begin. Your Contributions shows the status of submissions made from your account.

1

Select Contribute New Airport

The button is available after you sign in.
2

Enter the airport ICAO

Enter the airport’s four-character ICAO code.
3

Select Review airport

BARS loads the airport layout and contribution policy.
Start a contribution page with the Airport ICAO field, Review airport button, and contribution progress tracker

Enter an ICAO to begin the six-step contribution flow.

Selecting a scenery folder does not upload the package. BARS only uploads the contribution XML when you test and submit it.

​
Legacy MSFS workflow

You can still build an MSFS contribution with the simulator’s developer tools and upload the resulting XML at the test step. Use this route when the experimental MSFS browser editor cannot render your scenery correctly.
1

Enable Developer Mode

Start MSFS and enable Developer Mode:
Open Options > General Options > Developers, then turn Developer Mode on.
Start a flight at the airport you are mapping before opening the Scenery Editor.
2

Create a scenery project

Open the Project Editor:
Select Tools > Project Editor, then Project > New Project.
Name the project BARS Maps and choose where to save it. MSFS 2024 may display the name as BARS-Maps because it replaces spaces with hyphens.In the package wizard:
  1. Choose Package, then Custom.
  2. Use bars-maps as the package name and BARS Maps as its display name.
  3. Set Content-Type to SCENERY.
  4. Continue to the asset group screen.
3

Set up the asset group

Name the asset group using the airport and scenery:
For example, use EGLL-iniBuilds for the iniBuilds scenery at Heathrow.
Create a separate asset group for every airport and scenery package you map.
Set Asset Type to BGL, create the group, then select Load In Editor. Save the project before placing polygons.
4

Create the BARS object polygons

For each object on the BARS airport review map:
  1. Copy its BARS ID.
  2. In the Scenery Editor’s Objects panel, select Polygon, then Add.
  3. Hold Control and left-click to place each point.
  4. Press Enter to finish the polygon.
  5. In Properties, set Display Name to the exact BARS ID, such as BARS_0GHSI.
Shape the polygon along the stop bar, lead-on lights, or other object it represents. Repeat this for every object you want to include.
5

Add removal polygons

Draw polygons around default MSFS lights that BARS will replace. Set the display name of each removal polygon to remove.Only cover the lights that need to disappear. Do not place removal polygons over runway or scenery lights that should remain visible.
6

Save and test the XML

Select Save Scenery and save the XML inside the BGL asset group’s Asset Directory, usually its scenery folder under PackageSources. You can use Control + S for later saves.Return to the airport review page, select Skip to test, and upload the saved scenery XML.Check the browser preview before opening the contribution in the BARS Pilot Client. If an object is missing, confirm that its polygon uses the exact BARS ID. If a removal is missing, confirm that its polygon is named remove.

Review the airport

Check the division layout and BARS IDs before creating a draft.