See how photoreal scenery uses imagery, tiles, mesh and overlays, with fixes for blurry MSFS 2024 ground and X-Plane 12 orthophotos.
Photoreal scenery works by draping georeferenced aerial or satellite images over a simulator’s elevation mesh. The engine divides the imagery into geographic tiles, loads suitable detail levels around the aircraft, and combines them with separate airports, roads, trees, buildings and lights. Tiles may be streamed online or installed locally.
This is a general flight-simulator explanation covering Microsoft Flight Simulator 2020 and 2024, X-Plane 12, FSX and Prepar3D. Their package formats and scenery-priority rules differ, but the underlying process is much the same.
How does an aerial image become flight-simulator scenery?
The source photograph must be positioned, corrected and converted before a simulator can use it as terrain.
- Obtain suitable imagery. Developers use aerial photography, satellite imagery or an existing orthophoto mosaic. The source needs enough genuine resolution for the intended flying altitude, and its licence must allow the planned use and redistribution.
- Orthorectify and georeference it. Camera perspective and terrain distortion are corrected so that roads, shorelines and buildings occupy their proper coordinates. Projection or datum mistakes can shift an otherwise sharp image away from the simulator’s airports and vector roads.
- Clean and colour-match the source. Clouds, aircraft, fixed shadows, colour casts and abrupt joins between surveys may need manual correction. Water and blend masks can separate animated simulator water from water photographed in the source.
- Divide it into tiles and detail levels. The imagery is cut into geographic sections and supplied at several resolutions. Close terrain receives detailed tiles, while distant terrain uses smaller mipmaps or lower levels of detail.
- Compile the scenery package. The tiles are converted into the target simulator’s texture and terrain formats. Depending on the simulator, the package may also contain mesh, masks, seasonal textures, night lighting or object placement data.
- Layer airports and objects above it. Functional runways, taxiways, roads, trees, buildings and lights are separate from the photograph. Their position, exclusions and scenery priority determine which components remain visible.
At runtime, the scenery engine requests the tiles intersecting the visible area and replaces them with finer or coarser versions as the view changes. Loading can therefore produce temporary blur or tile pop-in even when the source imagery itself is sharp.
The photography is a historical snapshot, not a live view. A road, runway or housing development may have changed since the survey was captured. For a concrete example of the older local-scenery workflow, our practical FSX imagery and texture-compilation tutorial shows how photographs are aligned and built into simulator scenery.
Is photoreal scenery the same as satellite scenery or photogrammetry?
No. Photoreal and satellite scenery normally describe a flat ground image, while photogrammetry is textured three-dimensional geometry reconstructed from overlapping photographs.
| Component | What it contains | What it controls | Common limitation |
|---|---|---|---|
| Photoreal or orthophoto scenery | Georeferenced 2D photography | Visible fields, roads, roofs, coastlines and ground markings | Buildings and trees photographed from above remain flat without another layer |
| Photogrammetry | Textured 3D geometry reconstructed from many images | The shape and appearance of city blocks, structures, trees and cliffs | Can produce melted shapes, visual noise and high streaming or storage demands |
| Elevation mesh | A grid or network of terrain heights | Mountains, valleys, slopes and the physical ground surface | A coarse mesh can flatten terrain even beneath detailed imagery |
| Overlay or autogen | Placed roads, lights, forests, buildings and other objects | Interactive and three-dimensional detail above the ground | May be shifted if it was made from a different source or date |
Satellite scenery is also a loose name: much of the sharp imagery seen around cities was captured from aircraft rather than satellites. A high tile zoom level does not prove that the underlying photograph has equally high resolution; enlarged source pixels remain enlarged pixels.
Microsoft Flight Simulator can display both flat aerial imagery and streamed 3D city data. Our explanation of how MSFS reconstructs photogrammetry from overlapping photographs covers that separate process.
How does a geo flight sim use real-world data?
A geo flight sim combines several geographic datasets rather than relying on one photograph. Aerial imagery supplies colour, elevation data supplies terrain shape, vector data defines features such as roads and water, airport data provides operational surfaces, and object systems add buildings, trees and lights.
Photoreal scenery is therefore only one part of geographic realism. It can make a town recognisable from the air while still leaving the terrain too flat, the airport outdated or the roads non-functional.
What are scenery tiles, general tiles and a sim overlay?
A scenery tile is an addressable geographic section that the simulator can load independently. Some engines use a hierarchy of progressively smaller tiles; X-Plane scenery is organised around geographic DSF areas, with textures subdivided further inside the package.
General tiles is not a universal flight-simulation file type. Some tools and libraries use General as a category for ordinary terrain tiles, but the term alone does not identify a format, resolution or compatible simulator. Check the package documentation for its coordinates, simulator version and included layers.
A sim overlay adds features above an underlying terrain or orthophoto package. Typical overlay content includes roads, railways, forests, power lines, lights and generated buildings. It does not normally replace the underlying photographic image.
Tile boundaries explain several familiar defects: square areas at the wrong resolution, abrupt colour changes, missing sections and straight-edged water. They do not all have the same cause. A seam baked into two photographs needs source editing, while a temporarily blurred square may only indicate that a higher-detail streamed tile has not arrived.
How does X-Plane 12 satellite scenery work?
X-Plane 12 does not provide a default worldwide satellite-imagery stream; custom orthophoto scenery is normally generated or installed as local scenery. The orthophoto package supplies terrain textures and usually a base mesh, while a separate overlay restores roads, forests, buildings and other objects.
Three priority rules prevent most X-Plane satellite scenery problems:
- Place the package in
Custom Scenery. Keep every folder at the level expected by the package rather than accidentally nesting it inside an extra directory. - Put airports and overlays above orthophotos. Higher entries in
scenery_packs.initake priority. Airport scenery and overlay packages should sit above the photographic base mesh they are intended to complement. - Avoid competing base meshes. X-Plane loads one base mesh for a given geographic tile. If two orthophoto or custom-mesh packages cover the same tile, the higher-priority one wins rather than blending with the other.
A mistake we see constantly is moving an overlay beneath the orthophoto because the user assumes the ground should load first. Scenery priority is not a drawing sequence; the overlay needs higher priority so its objects are not suppressed.
X-Plane photogrammetry is different again. It consists of custom 3D models packaged as scenery objects; installing satellite textures does not automatically reconstruct buildings. For package placement, dependencies and priority details, use the folder and scenery-order checks in our X-Plane 12 orthophoto walkthrough.
MSFS 2024 streamed vs installed scenery
In Microsoft Flight Simulator 2024, streamed and installed content can use the same authored assets; the main difference is whether package data is fetched when required or retained on local storage. This choice is separate from the simulator’s streamed world imagery and photogrammetry services.
| Content mode | Choose it when | What to expect |
|---|---|---|
| Streamed world data | You want broad aerial-imagery and photogrammetry coverage without storing entire regions | Quality and loading depend on online services, connection stability, bandwidth and cache behaviour |
| Streamed package | You use an aircraft or scenery package occasionally and want to conserve storage | Assets may need to download before they reach their intended detail |
| Installed package | You use the package regularly or need predictable access to its files | It consumes local storage but does not necessarily install the surrounding world imagery |
| Local cache | You repeatedly fly over the same streamed areas | It can reduce repeat downloads, but it is not a complete offline installation and may preserve stale or damaged tile data |
Installing an airport does not install all aerial imagery around that airport unless the package explicitly includes it. Equally, an installed package may still depend on online weather, world data or other simulator services. Where the content library offers both states, choose installed for frequently used aircraft and regions; leave occasional content streamed when storage matters more than repeat loading time.
Microsoft Flight Simulator 2020 follows the same broad streamed-world model, although package management differs. FSX and Prepar3D photoreal packages are normally compiled and stored locally, as are typical X-Plane orthophoto tiles.
How do I fix blurry ground textures in MSFS 2024?
Blurry MSFS 2024 ground textures usually result from delayed or disabled world-data streaming, cached low-detail tiles, limited source imagery, add-on conflicts or graphics settings that reduce texture clarity. Identify which type of blur you have before changing settings.
- Separate ground blur from photogrammetry problems. A flat but soft aerial image is a ground-texture issue. Melted buildings and lumpy trees are photogrammetry or 3D-data issues, even when the ground beneath them is sharp.
- Confirm that online world imagery is enabled. Check the simulator’s data and online settings, any bandwidth or data limits, and the connection itself. If the online imagery service is unavailable, the simulator may fall back to generic or lower-detail terrain.
- Wait for the detailed tile to load. Pause briefly over a known area. If the ground changes from soft to sharp, streaming throughput or package delivery is the problem rather than texture resolution.
- Test without add-ons. On PC, temporarily remove or rename the contents of
Community; on consoles, disable relevant airport and world-enhancement packages through content management. Restart the simulator before comparing. - Rebuild the local cache when the same tiles remain wrong. A stale or incomplete cache can repeatedly serve blurred or damaged imagery. Recreate it using the simulator’s cache controls rather than deleting unrelated package folders.
- Review graphics settings last. Texture resolution and anisotropic filtering can affect clarity, while terrain level of detail mainly affects how far detailed terrain is maintained. None of these settings can restore information missing from the source photograph.
- Compare another region. If only one location remains blurred after the streaming and cache checks, the available source image may simply be low-resolution, cloudy or poorly processed. A local aerial-imagery add-on is then the only user-side replacement.
Do not assume that switching a package from streamed to installed will fix the ground. It only helps if that package contains the affected aerial textures or if its own assets were failing to arrive.
What causes black squares with Real Taxiways in MSFS 2024?
Black squares around taxiway markings usually indicate a missing, damaged or incompatible material in an airport or taxiway-enhancement package, not a faulty satellite image. If Real Taxiways is the installed enhancement, disable that package first and test the stock airport.
- Black shapes follow painted lines or signs: update or reinstall the affected enhancement, remove older duplicate copies, and make sure the package was built for the simulator generation being used.
- The defect flickers with another surface underneath: two airport packages are probably drawing the same taxiway or apron. Disable duplicates and retain one version of the airport.
- A large black square follows a geographic tile boundary: suspect failed world-data delivery or cached terrain instead. Restart the data connection and rebuild the relevant cache.
- The problem remains with all add-ons disabled: repair or redownload the simulator-managed airport content where the platform provides that option.
Clearing the rolling cache is not the first fix for a black marking attached to a taxiway object. Cache changes affect streamed geographic data; they cannot restore a texture omitted from an add-on package.
Why does photoreal scenery look wrong?
Most photoreal scenery defects come from the source image, a missing companion layer or scenery loaded at the wrong priority.
| Symptom | Likely cause | Useful fix |
|---|---|---|
| Blurry ground close to the aircraft | Low-resolution source, unfinished streaming, reduced texture quality or a stale cache | Check the source resolution and online delivery before raising graphics settings |
| Sharp roofs painted flat on the ground | No overlay, autogen or photogrammetry layer | Install or enable the intended companion object layer above the orthophoto |
| Roads and buildings shifted sideways | Poor georeferencing or layers made from different datasets and dates | Use matching components; scenery priority cannot correct coordinates baked into a package |
| Square edges or abrupt colour changes | Adjacent surveys have different lighting, seasons or colour processing | Use a colour-corrected package or revised source textures |
| Clouds, aircraft or fixed shadows on the ground | The objects were present when the source was photographed | Edit or replace the source image; a display setting cannot remove baked details |
| Frozen water or harsh coastlines | The water remains in the photograph or the package lacks suitable masks | Use compatible water and blend masks, and disable conflicting shoreline scenery |
| Runways or taxiways appear twice | The photograph and airport layout come from different dates, or two airport packages overlap | Keep the functional airport above the photographic base and disable duplicate airports |
| Wrong winter or night appearance | The package contains only daylight imagery from one season | Use scenery that supplies seasonal or night variants; one daytime photograph cannot provide them accurately |
When is photoreal scenery the right choice?
Photoreal scenery is most valuable when recognisable real-world ground detail matters more than seasonal consistency or storage efficiency.
- Low-level VFR: real field boundaries, road junctions, quarries, industrial sites and coastlines make visual navigation easier.
- Distinctive regions: unusual geology, farmland and urban patterns are reproduced more faithfully than repeated generic textures.
- Airport approaches: surrounding roads and terrain features can resemble the visual references expected on arrival.
It is a weaker choice when you require convincing seasons, small downloads or fully three-dimensional cities. Halving the metres-per-pixel value creates roughly four times as many source pixels for the same area before compression, so high-resolution regional coverage grows quickly.
What should I check before installing photoreal scenery?
Check compatibility, coverage and included layers before judging a package by its screenshots or download size.
- Simulator and platform: packages compiled for FSX, Prepar3D, X-Plane or MSFS are not interchangeable. PC folder-based installation instructions also do not apply to console versions.
- Geographic coverage: confirm the exact boundary and whether adjacent tiles are required to avoid visible edges along the planned route.
- Real source resolution: metres per pixel is more useful than a tile zoom label, but even that cannot guarantee that every source photograph is equally sharp.
- Included components: determine whether the download contains imagery only or also mesh, overlays, autogen, water masks, landmarks and airports.
- Source date: older photography may show removed taxiways, previous runway layouts or undeveloped areas beneath newer scenery.
- Scenery priority: airports and object overlays generally belong above photographic terrain. In X-Plane, do not expect two competing base meshes to combine.
- Storage and extraction space: compressed scenery may need substantially more room after installation, plus temporary space while it is unpacked.
- Season and night support: verify that the package supplies the conditions you intend to use rather than assuming the simulator can derive them from one daylight image.