Learn the correct Prepar3D mesh and photoreal scenery order, why install sequence rarely matters, and how to fix elevation conflicts.
In Prepar3D, the file-copy sequence usually does not matter: install mesh and photoreal scenery in separate folders, then place broad-area mesh below the photoreal package in scenery priority. Keep airports and other local scenery above both. Follow the add-on’s instructions if it supplies its own mesh or elevation files.
Does the installation order matter?
No—the order in which you copy mesh and photoreal files normally makes no difference when each product has its own folder and scenery entry. Installing mesh first is a tidy convention, but installing it afterwards will not put it visually on top of the imagery.
The exception is an installer that replaces or merges existing files. Do not combine unrelated packages in one Scenery folder or approve an overwrite without checking the documentation. Separate folders make conflicts much easier to diagnose and let you disable one package without disturbing another.
Where should mesh sit in the Prepar3D Scenery Library?
Broad regional or global mesh should normally have lower priority than photoreal scenery, airports and other local add-ons. In the traditional Scenery Library, entries nearer the top have higher priority, so the usual order is:
- Airports and local scenery — keep airport objects, flattens and elevation corrections at the priority specified by their developer.
- Photoreal or orthophoto scenery — place the imagery package below airports but above broad terrain packages.
- Regional or global terrain mesh — position general-purpose mesh below the more geographically specific scenery.
- Default scenery — leave Prepar3D’s supplied terrain at its normal base priority.
Our Prepar3D scenery installation and layering guidance covers the registration process in more detail. Add-ons installed through add-on.xml may manage their own layers; use the package’s supported priority method rather than moving its files manually.
Why can lower-priority mesh still affect the terrain?
Prepar3D’s terrain selection is strongly influenced by mesh resolution, not just Scenery Library order. The simulator will generally use the finest available mesh for a location, so a detailed global mesh can still affect an area even when its library entry sits below a coarser local mesh.
Photoreal imagery does not replace terrain elevation. It is draped over whichever mesh Prepar3D selects, which means changing the imagery priority may not fix hills, cliffs or airport elevation problems.
| Symptom | Likely cause | What to check |
|---|---|---|
| Photoreal textures appear, but the terrain shape is wrong | An unintended mesh is being selected | Disable overlapping mesh packages one at a time and reload the area. |
| An airport is sunken or on a plateau | An airport flatten or elevation correction conflicts with the active mesh | Keep the complete airport package above broad scenery and restore its supplied elevation files. |
| The new mesh makes no visible difference | It is inactive, lacks coverage there or is no finer than the existing terrain | Confirm its scenery entry, coverage and package compatibility. |
| The ground imagery is blurred or missing | This is usually an imagery installation or loading problem, not mesh order | Check the photoreal folders and activation using our orthophoto installation procedure. |
Does photoreal scenery need a separate mesh?
No, photoreal scenery can use Prepar3D’s default terrain mesh. A higher-detail mesh changes the shape of mountains, valleys and coastlines beneath the photograph; it does not increase the imagery resolution.
A broad package such as the FreeMeshX terrain mesh download and installation notes shows the usual relationship between global mesh, photoreal coverage and airport scenery. Check compatibility with your Prepar3D version, and give any mesh bundled specifically with the photoreal package precedence according to that package’s instructions.