Compare KDFW scenery add-ons for X-Plane: Gateway, payware, freeware and Texas ortho, with clear X-Plane 12 compatibility and layering advice.
X-Plane users have four practical KDFW scenery choices: the included Scenery Gateway airport, Aerosoft’s dedicated Dallas/Fort Worth International payware for X-Plane 11, community-built freeware revisions, and Texas orthophoto scenery for the surrounding metroplex. In X-Plane 12, verify native compatibility rather than assuming an X-Plane 11 airport will work unchanged.
Which KDFW scenery options are available?
The right option depends on whether you want dependable X-Plane 12 operation, detailed airport buildings or better terrain around Dallas and Fort Worth.
| Option | What it adds | Compatibility considerations |
|---|---|---|
| Gateway KDFW | Runways, taxiways, ramps and library-based airport buildings | Included through X-Plane’s Global Airports scenery and matched to the simulator version in which it ships |
| Aerosoft Dallas/Fort Worth International | Custom terminals, textures and airport-specific detail | The established package originated as an X-Plane 11 product; use it in X-Plane 12 only when that specific release explicitly states support |
| Community freeware KDFW | Custom buildings, revised layouts or enhancements to the stock airport | Quality, required object libraries and X-Plane 12 compatibility vary by revision |
| Texas orthophoto scenery | Photographic ground textures across the wider Dallas–Fort Worth region | Complements an airport package but does not provide detailed KDFW terminals or airport objects |
The Gateway airport is the safest baseline. A dedicated commercial package is the stronger choice when bespoke terminal modelling matters, while freeware can work well if its library requirements and supported X-Plane version are documented. Our advice on combining airports, overlays and terrain in X-Plane 12 explains how these scenery types fit together.
Check layout accuracy as well as visual quality. KDFW’s taxiways, stands and terminal areas change over time, so a detailed package with old airport data may be less useful for online flying than a newer Gateway revision.
Which KDFW option should X-Plane 12 users choose?
For X-Plane 12, use the supplied Gateway KDFW unless a custom package explicitly supports X-Plane 12 or has a verified update for it.
An X-Plane 11 airport may load in X-Plane 12, but that does not establish full compatibility. Common trouble spots include lighting, materials, vegetation, animated jetways, external plugin dependencies and terrain alignment. Keep the default airport available so you can remove the custom package and revert without reinstalling X-Plane.
- Choose Gateway KDFW for reliability, straightforward updates and no extra dependencies.
- Choose dedicated payware for airport-specific terminals and apron detail, provided your simulator version is supported.
- Choose freeware when its screenshots, documentation, library list and airport revision meet your needs.
- Add orthophoto scenery when realistic Dallas–Fort Worth approaches matter more than extra terminal detail.
Does Texas orthophoto scenery replace KDFW airport scenery?
No. Orthophoto scenery replaces the regional ground imagery beneath KDFW, while the airport package supplies runways, taxiways, buildings, signs and other objects.
You can download complete Texas orthophoto coverage to improve views around the Metroplex and on approach. Before installing a large regional package, read our guide to free satellite and Ortho4XP scenery for X-Plane 12 for storage, overlay and visual-quality considerations.
Base meshes do not blend simply because both are installed. If a KDFW package includes its own mesh, whichever mesh has priority for that tile can suppress the Texas orthophoto tile. Follow the airport package’s ordering instructions rather than merging folders.
How should KDFW scenery be installed?
Install one custom KDFW airport above Global Airports, with overlays above orthophoto or mesh scenery.
- Remove competing KDFW packages. Two active airport definitions can produce duplicate terminals, overlapping signs and doubled taxiway objects.
- Extract the complete package. Place each intended scenery folder directly inside
Custom Scenery; avoid leaving it inside an extra wrapper folder created by the archive. - Install required libraries. If the documentation lists object libraries or a jetway plugin, missing dependencies will usually cause an incomplete airport or a scenery-loading warning.
- Check scenery priority. In
scenery_packs.ini, place the custom KDFW airport aboveGlobal Airports. Put overlays above orthophoto and mesh entries, which normally belong near the bottom. - Load KDFW and inspect the log. If X-Plane reports an error, search
Log.txtfor the KDFW folder name and messages about missing objects, libraries or scenery files.
Why are buildings duplicated or the ortho tile missing?
Duplicated buildings normally mean two KDFW airport packages are active or a custom package has been ordered below another airport definition. A missing orthophoto tile usually means another base mesh has higher priority; unlike airport objects and overlays, two meshes covering the same tile are not combined.