What KDFW scenery add-ons are available for Prepar3D?

For Prepar3D, our library offers three freeware KDFW options: a full Dallas/Fort Worth scenery replacement, a lighter ADE airport-layout update, and an AFCAD focused on ILS alignment for runways 18R/36L. Install only one airport-layout package at a time unless its documentation explicitly says the files are designed to work together.

Which KDFW scenery add-on should I choose?

Choose according to the problem you want to solve rather than installing all three packages.

The ADE and AFCAD labels overlap more than their names suggest. Both can contain airport-facility records covering runways, taxiways, parking, AI routing or navaids, so combining them with another KDFW replacement can produce conflicts.

Will these KDFW add-ons work in every Prepar3D version?

The full scenery package is presented for FSX and Prepar3D, but that does not guarantee every component will behave identically in every Prepar3D release.

Airport-layout BGL files tend to transfer between simulator generations more successfully than executable modules. Custom models, effects, animated jetways and old installers are more version-sensitive. Check the included documentation for its stated simulator target, and test the package before adding other scenery around KDFW.

If an old installer recognises only FSX, do not point it blindly at Prepar3D's core directory. Extract the package manually when its format permits, preserve its folder structure and activate it as a separate scenery area.

How do I install KDFW scenery without duplicate airports?

Keep one active KDFW airport package and install it outside Prepar3D's protected stock scenery folders.

1. Read the included instructions. They take priority if the package requires a particular folder structure or activation method.
2. Disable existing KDFW add-ons. Do not delete Prepar3D's stock airport files; remove or deactivate only third-party KDFW scenery.
3. Preserve the folders. Legacy packages commonly use separate Scenery and Texture directories. An accidental extra folder level can leave the airport visible but its textures missing.
4. Register the package once. Use either the Scenery Library or its supplied add-on package method, not both. Our Prepar3D scenery installation walkthrough covers both approaches.
5. Set sensible priority. Place the airport above broad regional scenery and other packages that modify KDFW, then restart Prepar3D and test with no second KDFW enhancement active.

Why are the ILS, AI traffic or jetways still wrong?

Most KDFW faults come from conflicting airport-facility files rather than a failed installation.

• Double terminals, markings or taxiway signs: two KDFW airport files are active. Disable every third-party KDFW package except the one being tested.
• AI aircraft use incorrect gates or taxi routes: an older AFCAD may be overriding the chosen scenery. Parking and taxi-path data must come from the same airport layout.
• ILS remains offset: use the focused AFCAD only if another KDFW package is not already supplying the airport and navaid records. A third-party aircraft's FMS navigation database is separate, so an AFCAD cannot update its procedures or cycle data.
• Jetways do not move: confirm that the selected stand has an animated jetway, park on the stand correctly and use Prepar3D's configured jetway command. A visible jetway is not necessarily animated.
• Missing or black textures: check that the package's Texture folder was copied and that the scenery path does not contain an unintended nested directory. Persistent missing models can indicate a compatibility problem with that Prepar3D release.
• Airport sits on a plateau or below the ground: disable competing KDFW elevation corrections and regional airport files one at a time until the conflicting layer is identified.