Learn what scenery exclusion zones remove, how to place and layer them in MSFS, X-Plane, FSX and P3D, and how to fix failed exclusions.
Across MSFS, X-Plane, FSX and Prepar3D, a scenery exclusion zone is a bounded area that suppresses selected default or lower-priority scenery—such as trees, buildings, roads or library objects—so replacement airport scenery displays cleanly. Draw the smallest possible zone, exclude only the required categories, export it, then test the package above conflicting scenery.
How do scenery exclusion zones work?
An exclusion is a scenery-layer instruction, not an eraser that permanently alters the simulator's base files. It tells the rendering engine to ignore specified classes of scenery inside a rectangle or other supported boundary while the package is active.
The available classes depend on the simulator and design tool. Typical choices include vegetation, autogen, forests, façades, roads, generic buildings and placed library objects. Exclusions do not normally change terrain height, replace aerial imagery or delete airport data such as runways, parking positions and taxiway links; those require separate controls.
How does the method differ by simulator?
The principle is shared, but each simulator uses different tools, category names and scenery-priority rules.
| Simulator | Typical method | Main limitation |
|---|---|---|
| MSFS 2020/2024 | Use exclusion rectangles and category flags in an SDK-compatible scenery editor. | Deleting stock airport elements and changing terrain require separate airport or terraforming controls. |
| X-Plane | WED provides category-specific exclusion zones for objects, façades, forests, roads and other scenery. Our guide covers setting targeted exclusions in WED. | The package must have sufficient priority in scenery_packs.ini. An airport boundary is not a universal immediate exclusion zone. |
| FSX and Prepar3D | Exclusion rectangles are compiled into a BGL. See our walkthrough of placing and compiling exclusions with Airport Design Editor. | Terrain vectors, autogen and scenery objects may require different exclusion types. |
How do I use an exclusion zone in airport design?
Identify the unwanted scenery, select its actual scenery class, enclose it tightly and test the compiled package in the simulator.
- Find the source of the conflict. Disable your project and inspect the stock airport. If the unwanted item disappears only when another add-on is disabled, you are making a compatibility exclusion rather than correcting default scenery.
- Choose the correct mechanism. A tree may be vegetation, forest autogen or a placed library object. A runway elevation problem is terrain, while a duplicate parking position belongs to the airport facility data.
- Draw a tight boundary. Cover the unwanted item and a small margin, but avoid surrounding terminals, roads or vegetation that should remain. Several small zones are usually safer than one airport-wide rectangle.
- Select only the required categories. Use an object exclusion for a stock hangar and a vegetation or forest exclusion for trees. Reserve an exclude-all setting for cases where the area genuinely must be cleared of every supported class.
- Export and check scenery priority. Compile or export the project using the tool's normal packaging process. The exclusion package generally needs higher priority than the scenery it is intended to suppress.
- Test the loaded package. Reload scenery or restart the simulator as required. Check from several viewpoints because a large model's visible geometry may extend well beyond its placement point.
Do not rely solely on the editor preview. The compiled package and the simulator's actual scenery order determine the result.
Which exclusion category should I choose?
Choose the category that matches how the unwanted feature was created, not merely how it looks on screen.
| Unwanted feature | First control to try | Common trap |
|---|---|---|
| Trees or generated vegetation | Vegetation, forest or autogen exclusion | Some trees are individually placed library objects. Our FSX runway-tree exclusion example explains the distinction. |
| Stock hangar, terminal or clutter object | Object or library-object exclusion | A whole terminal complex may be one combined model rather than several removable parts. |
| Road crossing an apron | Road, network or terrain-vector exclusion | A wide zone can also remove nearby roads and traffic. |
| Duplicate runway, taxiway, start or parking position | Airport delete or replacement controls | A normal object exclusion does not remove the underlying airport record. |
| Hill, trench or uneven runway | Terraforming, flattening or corrected mesh | Object exclusions do not change elevation data. |
| Wrong ground texture or aerial image | Apron, material, projected image or imagery-layer controls | Excluding objects will not remove the source ground imagery. |
Why is my scenery exclusion zone not working?
A failed exclusion usually means the wrong category was selected, the package has insufficient priority or the visible feature is controlled by a different scenery system.
- Wrong scenery class: try to establish whether the feature is autogen, a library object, an airport element or terrain data before enlarging the zone.
- Incorrect priority: move the patch above the scenery being corrected. FSX users should check the scenery-library priority rules and conflict checks.
- Reference point outside the zone: some engines test a model's placement origin rather than every visible polygon. Extend the boundary towards the likely origin instead of covering unrelated scenery.
- Old or duplicate output: remove obsolete compiled copies and confirm that the simulator is loading the package you just exported.
- Wrong mechanism: use airport-delete commands for duplicate airport data and terrain tools for elevation or vector problems.
- Higher-priority third-party scenery: an exclusion cannot reliably override a package that the simulator loads above it.
For diagnosis, begin with only the base simulator and your exclusion package enabled. Once it works against default scenery, restore other add-ons one at a time until the conflict returns.
Can exclusion zones remove third-party scenery?
Exclusion zones can suppress third-party scenery when the target uses a supported object class and your patch loads at higher priority. They cannot selectively cut geometry from a single combined model or override content that the simulator treats as part of a higher layer.
A compatibility patch normally contains the exclusion plus any replacement objects required to restore the intended airport layout. Keep that patch separate from the original add-on so it can be disabled easily when either airport package is updated.
How large should an exclusion zone be?
The best exclusion zone is the smallest boundary that consistently catches the unwanted feature. Start tight, test it, then extend only the affected edge if the object's reference point or generated vegetation lies outside the original area.
A mistake we see constantly is placing an exclude-all rectangle over the entire airport. It clears the immediate conflict but can also remove nearby buildings, forests, façades and road networks. Category-specific exclusions preserve more of the surrounding scenery and cause fewer conflicts with later add-ons.