Compare two freeware KMCO scenery add-ons for Prepar3D, with compatibility advice, installation steps and fixes for common airport conflicts.
For Prepar3D, two useful freeware KMCO options are available in our library: a broader Orlando International Airport makeover and a more focused AFCAD airport-layout update. The full scenery changes taxiways, parking and ground details; the AFCAD concentrates on stands, airport objects and vehicle roads. Install only one airport definition at a time.
Available freeware KMCO scenery for Prepar3D
The two downloads target different parts of Orlando International Airport, so the better choice depends on the detail you want and your Prepar3D version.
| KMCO add-on | What it changes | Compatibility caveat |
|---|---|---|
| Broader freeware KMCO airport makeover | Updates taxiways, parking and roads, with fuel-truck details and a helipad. | The listing explicitly identifies it for FSX and Prepar3D, although individual P3D releases should still be tested. |
| Detailed KMCO AFCAD layout package | Adds airline-coded parking, extra stands and revised vehicle roads. Airport objects and terrain are supplied as separate BGL components. | This is a legacy airport-definition package, so compatibility is more dependent on the P3D version and other installed scenery. |
AFCAD is the long-standing community term for an airport-definition BGL. It can alter runways, taxiways, parking and AI routing, but the term alone does not imply a fully modelled terminal or photoreal ground textures.
Which Orlando scenery should I choose?
Choose the broader makeover for a general upgrade to the default KMCO, or the AFCAD package when parking allocation and ground layout matter most.
- For visual flying and general operations: start with the broader FSX/P3D makeover because it updates several parts of the airport in one package.
- For airline AI traffic: the AFCAD package is the more relevant option because it includes airline-coded parking and additional stands.
- For an existing regional scenery setup: use whichever package causes fewer elevation and object conflicts with your mesh, landclass or airport collection.
Do not activate both packages together. Each may contain a KMCO airport definition, and stacking them can produce duplicated objects, conflicting parking positions, broken taxi routing or elevation artefacts.
Will these KMCO add-ons work in Prepar3D v4, v5 and v6?
The broader makeover is explicitly offered for Prepar3D, but neither download should be assumed to work perfectly in every P3D generation without testing.
Simple airport BGLs often transfer more successfully than scenery relying on old object models, effects or installers. Later Prepar3D releases also use different default terrain and airport data, which can expose plateaus, sunken runways or duplicated buildings that were not visible against an earlier simulator base.
Load KMCO in a clean test scenario before adding AI traffic or complex weather. Check runway elevation, taxiway surfaces, terminal objects, night lighting and parking positions. If a package fails, disable its scenery entry rather than deleting stock Prepar3D files.
How do I install KMCO scenery in Prepar3D?
Install the selected KMCO package in its own folder, preserve its internal structure and register it through Prepar3D rather than scattering BGL files through global scenery directories.
- Remove competing KMCO add-ons. Disable any other Orlando airport package while testing the new one.
- Read the included instructions. Some legacy packages require a Scenery Library entry, while newer packaging may use
add-on.xml. - Preserve the folders. Keep the package's
SceneryandTexturedirectories together. Do not flatten or rename them unless its documentation requires that. - Register the scenery. Our Prepar3D scenery installation walkthrough covers Scenery Library registration and missing-scenery checks. P3D v5 users should follow the version-specific installation methods for legacy and add-on.xml scenery.
- Set sensible priority. Give the airport package higher priority than broad regional or base scenery, while following any ordering instructions included with the download.
- Restart and inspect KMCO. Test the airport before enabling another Orlando package or making permanent changes.
Why is the KMCO scenery missing or displaying incorrectly?
Missing or damaged KMCO scenery usually means the library points at the wrong folder, another airport BGL is overriding it, or an incompatible terrain component is active.
- No visible change: check that the registered path leads to the package folder containing
Scenery, not to an extra nested folder or the BGL directory itself. - Duplicate terminals or parking: disable other airport packages one at a time. Do not remove Prepar3D's default airport files.
- Sunken runways or plateaus: look for a competing KMCO elevation correction, terrain BGL or regional mesh. The AFCAD package's separate terrain component can help isolate this kind of conflict.
- Missing objects or textures: restore the original folder structure and confirm that the complete download was extracted. A working airport layout does not prove that every object format is supported by that P3D release.
- AI ignores airline-coded stands: parking codes do not create traffic. The AI aircraft and flight plans must use matching codes, and each stand must have a sufficient parking radius.
- Runway or taxiway data disagrees with navigation data: the scenery may represent a different airport revision. Layer priority cannot reconcile an older airport BGL with newer navigation data.