Learn how to remove trees from a runway in FSX using autogen checks, scenery-priority fixes and a safe local exclusion BGL.
To remove trees from a runway in FSX, first confirm that the intended airport scenery has priority, then place an autogen-exclusion polygon over the runway and approaches with Airport Design Editor. Compile it as a separate BGL in an active scenery area; do not delete or overwrite FSX's default scenery files.
The same method applies to boxed FSX and FSX: Steam Edition. Before changing anything, determine whether the trees are generated autogen, individually placed scenery objects or the result of conflicting airport scenery.
Are the runway trees autogen or scenery objects?
The Autogen density setting provides the quickest way to identify the source of the trees.
| What happens during the test | Likely cause | Correct fix |
|---|---|---|
| Trees disappear with Autogen density set to None | Terrain autogen vegetation | Create a local exclude-autogen terrain or CVX polygon |
| Trees remain with autogen disabled | Placed library objects or custom models | Use an object-exclusion rectangle or disable the responsible scenery |
| Runways, taxiways or buildings appear twice or are misaligned | Duplicate or mismatched airport scenery | Correct the Scenery Library priority and disable the obsolete airport file |
Open FSX's display and scenery settings, move Autogen density to None, then reload the airport. Restore the original setting after the test. Lowering Scenery complexity is less reliable because placed objects may use different complexity flags.
How do I remove trees from one FSX airport?
A local exclusion BGL is the cleanest fix because it clears the runway without removing vegetation from the rest of the simulator.
Our Airport Design Editor workflow for creating and compiling exclusions covers the editor setup in more detail. For runway vegetation, follow this sequence:
- Find the scenery responsible. Temporarily disable suspected airport add-ons one at a time in the Scenery Library. If the trees vanish, note which layer supplied them rather than deleting files at random.
- Open the correct airport. Load the stock airport or the active add-on airport in Airport Design Editor. Check that its runway position matches what FSX displays.
- Choose the correct exclusion type. For trees that disappear when autogen is disabled, use a terrain or CVX polygon configured to exclude autogen. An ordinary object-exclusion rectangle does not normally suppress terrain autogen. Use the object exclusion only when the trees are placed library objects.
- Cover the affected ground. Extend the polygon beyond the runway edges, thresholds and any affected approach lighting. Keep it as small as practical; an airport-wide exclusion can remove wanted vegetation and buildings.
- Compile for FSX. Save the generated BGL or BGLs in a separate active folder such as
Addon Scenery\RunwayTreeFix\scenery. Configure the editor for FSX rather than another simulator target. - Set the scenery priority. Place the correction above the airport or terrain package it is intended to override. Restart FSX or force a scenery-library reload, restore normal autogen density and inspect both runway ends.
Keep the editor project and a note of every generated file. That makes the correction easy to revise or remove without touching the simulator's default scenery.
Can a ready-made scenery package remove the trees?
A ready-made vegetation fix can save time when it covers the affected location, but it must still have the correct Scenery Library priority.
The ready-made FSX Lumberjack vegetation-removal scenery is designed to clear unwanted trees around supported runways. Read its coverage and installation notes before using it, and avoid stacking several vegetation fixes over the same airport.
Why does my exclusion BGL not remove the trees?
Most failed runway-tree fixes use the wrong exclusion class or load beneath the scenery that creates the vegetation.
- Wrong exclusion: object rectangles remove placed library objects; terrain autogen requires an exclude-autogen polygon or suitable airport-background/CVX definition.
- Wrong layer: move the correction above the offending airport, landclass or photoreal scenery area.
- Inactive folder: confirm that the parent scenery area is enabled and that the compiled BGL is inside its
scenerysubfolder. - Wrong airport version: an add-on may move the runway slightly, leaving an exclusion drawn around the stock coordinates ineffective.
- Duplicate airport files: old AFCAD-style files can produce overlapping layouts. Disable the obsolete file after making a backup; never remove the stock airport BGL.
- Custom tree models: some scenery packages place their own vegetation. Disable or patch the responsible package rather than deleting a shared tree library, which can break vegetation at other airports.
Can I remove every tree in FSX temporarily?
Setting Autogen density to None removes autogenerated trees globally and is useful for testing or low-performance systems.
It also removes autogen buildings, so it is not a good permanent solution for one obstructed runway. If trees remain after this setting is applied, they are almost certainly placed scenery objects or custom models and must be excluded or removed from the responsible add-on.