Set the Orbx insertion point in FSX or Prepar3D correctly, with the proper priority for airports, regions, openLC and third-party scenery.
Set the Orbx insertion point in Orbx Central so third-party airports and local scenery stay above Orbx Airports and Regions, then place Orbx Global openLC below the Orbx regions group. In FSX and Prepar3D, higher Scenery Library entries normally have priority, so this order protects detailed local add-ons from broader scenery layers.
Where should the Orbx insertion point be?
The safest general order is local airport scenery first, Orbx Airports and Regions beneath it, and Orbx Global openLC beneath the regional products.
| Priority | Scenery type | Reason |
|---|---|---|
| Highest | Airport-specific fixes and compatibility patches | These must override the scenery they are correcting. |
| High | Third-party airports, cities and local scenery | Detailed local files need priority over broader Orbx coverage. |
| Middle | Orbx Airports and Regions | Regional scenery supplies the surrounding terrain, objects and airport coverage. |
| Lower | Orbx Global openLC | General landclass should not override a full Orbx region. |
| Lowest | Broad terrain layers and default scenery | These provide the base beneath more specific scenery. |
“Above” means higher in the FSX or Prepar3D Scenery Library and therefore normally higher priority. Our guide to how FSX scenery priority and layer order work explains the wider ordering rules.
Compatibility files can require a very specific position. For example, this Portland scenery patch demonstrates why exclusions may need to sit above FTX_NA layers. Always follow explicit instructions supplied with an airport or patch.
How do I change the insertion point in Orbx Central?
Set both Orbx boundaries while FSX or Prepar3D is closed, then confirm the resulting order in the simulator's Scenery Library.
- Close the simulator. Do not edit scenery order while FSX or Prepar3D is running.
- Select the correct simulator in Orbx Central. Insertion-point settings are simulator-specific, so verify that you are changing FSX or the intended Prepar3D installation.
- Open the insertion-point settings. In Orbx Central, open Settings and find Insertion Point. Older FTX Central releases use a similarly named Scenery Library Configuration control; the menu wording differs, but the ordering principle is the same.
- Set Orbx Airports and Regions. Choose the lowest third-party airport or local scenery entry that must remain above Orbx. Central will place its Airports and Regions block below that boundary.
- Set Orbx Global openLC. Place openLC below the Orbx Airports and Regions group. Do not put openLC between a custom airport and its Orbx region.
- Apply the setting and let Central synchronise. Wait for any library update to finish before opening the simulator.
- Inspect the Scenery Library. Confirm that every local third-party airport is above the Orbx block and that openLC is below the Orbx regional layers.
A mistake we see constantly is selecting the highest third-party entry rather than the lowest one that needs protection. That can leave several custom airports underneath Orbx. Use the final non-Orbx airport or local scenery layer as the boundary.
If Orbx is the only add-on scenery installed, its default managed order is normally sufficient. Set a custom boundary after adding the first third-party airport or regional package.
What if the target scenery is missing from the list?
A scenery package must be active and registered before Orbx Central can use it as an insertion-point boundary.
For FSX, first check that the package appears and is enabled in the Scenery Library; our steps for registering and moving FSX scenery areas cover that process. Prepar3D users should verify the installation method against our Prepar3D scenery registration instructions.
Prepar3D add-on packages registered through add-on.xml may be managed outside the traditional scenery.cfg workflow or appear as non-editable entries. Do not register the same scenery folder manually a second time merely to make it movable. Duplicate registration can produce doubled objects, conflicting airport layouts and elevation problems.
Orbx Central controls the placement of the Orbx layers it manages; it does not rewrite the internal order of an unrelated add-on package. If that package's instructions specify a different priority, follow those instructions.
Why is scenery still wrong after changing the insertion point?
An insertion point fixes layer-priority conflicts only; it cannot repair missing files, incompatible airport data or every elevation problem.
- The wrong simulator was selected: repeat the change under the correct FSX or Prepar3D profile in Orbx Central.
- Orbx returned to the top: set and retain the Central insertion point instead of repeatedly dragging individual Orbx entries by hand.
- There are duplicate airport files: disable the older airport or duplicate registration rather than relying on priority alone.
- The airport is sunken or on a plateau: check for an elevation-adjustment file, legacy airport BGL or incompatible mesh. Older products may place adjustment files in
Scenery\World\scenery, where changing the visible library order may not solve the conflict. - Buildings remain missing: confirm that required object libraries are installed and active, then use Orbx Central's file-verification function for the affected Orbx product.
After correcting the order, restart the simulator and test at the affected airport. A correct result should show the custom airport and its exclusions, with the Orbx region supplying the surrounding scenery and openLC remaining underneath both.