What Is Photogrammetry and Why It Matters for X‑Plane Scenery

Photogrammetry is the science of extracting three‑dimensional measurements and models from two‑dimensional photographs. By stitching together hundreds or thousands of overlapping images taken from different angles, photogrammetry software builds a dense point cloud that is then converted into a textured mesh. In flight simulation, this technique provides an unprecedented level of real‑world accuracy—capturing not just the shape of the terrain but the actual appearance of buildings, vegetation, roads, and natural landmarks.

For X‑Plane users, integrating photogrammetry data means moving beyond generic, algorithm‑generated scenery into a world that mirrors the real environment down to the roofline of a specific building or the curve of a riverbank. The result is a dramatic improvement in visual fidelity and pilot immersion. Whether you are flying VFR (visual flight rules) routes over familiar cities or practicing approaches into remote airports, photogrammetry‑enhanced scenery makes every flight feel grounded in reality.

Benefits of Using Photogrammetry in X‑Plane

Integrating photogrammetry into your X‑Plane scenery projects offers several concrete advantages:

  • Sub‑meter accuracy – High‑resolution orthophotos combined with 3D meshes produce terrain and structures that align precisely with real‑world coordinates.
  • Rich visual detail – Natural features such as trees, rock formations, and shoreline contours are captured as actual geometry rather than flat textures.
  • Improved depth perception – Because buildings and terrain have real relief, pilots can judge altitude, distance, and approach angles more intuitively.
  • Reduced reliance on generic autogen – Photogrammetry replaces blocky, repetitive autogen buildings with authentic, location‑specific models.
  • Consistency with real‑world navigation – VFR checkpoints like water towers, stadiums, or unique hillsides become immediately recognizable in the sim.

Gathering Source Data

The quality of your photogrammetry output depends almost entirely on the quality of your input images. For X‑Plane scenery, you typically need aerial imagery, drone footage, or satellite photos. Here are the most common sources and their trade‑offs:

Aerial Photography (Manned Aircraft)

Helicopter or fixed‑wing surveys can capture extremely high‑resolution images (under 2 cm per pixel) over large areas. This method is ideal for covering an entire airport or city district. The main drawback is cost and the need to coordinate with pilots and local aviation authorities.

Drone Surveys

Consumer‑grade drones such as the DJI Phantom or Mavic series can produce excellent results for smaller zones (a few square kilometers). Plan your flight path with 70–80% forward overlap and 60–70% side overlap. Consistent lighting—ideally a bright, overcast day—reduces shadows and makes texture stitching easier.

Public Satellite and Orthoimagery

If custom flights are impractical, you can download free or low‑cost orthophotos from sources like the USGS EarthExplorer, Maxar Open Data, or Google Earth (for reference only—check licensing for derivative 3D models). While satellite imagery typically has lower resolution (30–50 cm per pixel), it is sufficient for regional terrain enhancements.

Important: Always respect copyright and data‑use licenses. If you plan to distribute your scenery publicly, use only imagery with permissive licenses or your own capture.

Processing Photogrammetry Data into 3D Models

Once you have your image set, you need photogrammetry software to convert the photos into a 3D mesh and texture atlas. Several options are available, ranging from free open‑source tools to professional suites:

  • Meshroom (AliceVision) – Free, open‑source. Good for small to medium projects. Exports OBJ and glTF.
  • Agisoft Metashape – Industry‑standard toolbox. Produces high‑accuracy models and supports georeferencing with GPS data. (Paid, with educational licensing.)
  • RealityCapture – Very fast processing, excellent for large datasets. (Paid per‑model or subscription.)
  • WebODM – Open‑source, web‑based. Best for orthomosaic and point cloud generation; can export 3D meshes.

Workflow Overview

  1. Import and align photos – The software detects common points across images and calculates camera positions.
  2. Build dense point cloud – Millions of 3D points are generated from the image matches.
  3. Generate mesh – The point cloud is triangulated into a surface. For X‑Plane, aim for a mesh that captures major geometry (buildings, hills) but isn’t overly dense.
  4. Create texture – The software projects the original photos onto the mesh to produce a seamless texture map.
  5. Export – Export as OBJ or COLLADA (.dae) with the texture image. X‑Plane’s native format is OBJ, so that is often the safest choice.

During processing, pay attention to the coordinate system. If your images contain GPS data (e.g., from a drone), the model will be georeferenced automatically. Otherwise, you will need to manually align it later in WED (World Editor).

Preparing Models for X‑Plane

Raw photogrammetry meshes can be extremely heavy—millions of polygons for a single block. Running such models directly in X‑Plane will kill frame rates. To make them usable, you must optimize:

Decimation (Reducing Polygon Count)

Use tools like MeshLab, Blender, or instant meshes to decimate the mesh. For ground terrain, you can often reduce to 200,000–500,000 triangles per square kilometer without losing visible detail. For isolated buildings, aim for 5,000–20,000 triangles per structure.

Texture Atlasing and Compression

Photogrammetry textures are often large (8K or 16K). Resize them to 2K or 4K for X‑Plane, or use DDS compression (with mipmaps) to save VRAM. You can combine multiple texture files into a single atlas to reduce draw calls.

Level of Detail (LOD)

Create at least two LOD versions: a high‑detail model for close distances (0–200 m) and a low‑detail version for mid‑range (200–1500 m). For very large scenery, add a third LOD with simplified geometry and a single texture for far views. X‑Plane supports LOD by naming convention (e.g., mybuilding.obj, mybuilding_LOD1.obj).

Integrating into X‑Plane with WED (World Editor)

World Editor (WED) is the official tool for creating and editing X‑Plane scenery packs. Follow these steps to place your photogrammetry models:

  1. Create a new scenery package or open an existing one.
  2. Import your orthoimagery (GeoTIFF) as a background layer to help visually align your 3D models.
  3. Drag your OBJ model into the WED project. If the model has embedded GPS coordinates, it should appear in the correct location. Otherwise, move and rotate it to match the orthoimagery.
  4. Use the “Validate” function to check for errors (e.g., missing textures, incorrect heights).
  5. Export your scenery pack. WED generates a Earth nav data folder with DSF (X‑Plane’s terrain format) files.

For large terrain coverage, you may need to tile your mesh into smaller sections (e.g., 1×1 km tiles) to match X‑Plane’s DSF tile system. Tools like Ortho4XP can help automate the tiling of orthophotos and elevation data, but integrating custom 3D meshes requires manual placement.

Blending with Default Scenery and Orthophotos

A common mistake is to place photogrammetry models on top of default scenery without blending. The result looks like a floating island. To create a seamless transition:

  • Use a base orthophoto texture – Cover the entire scenery area with a high‑resolution orthophoto (GeoTIFF) so that the ground matches your model.
  • Adjust mesh elevation – In WED, you can set a “ground” height for your model. Ensure the base of your photogrammetry mesh aligns with the DSF terrain elevation (height can be fine‑tuned per vertex in the OBJ file).
  • Add exclusion zones – Use WED’s “forest,” “buildings,” and “facades” exclusions to remove default autogen objects that overlap your custom model.
  • Blend edges with grass/terrain textures – If your photogrammetry object has a hard boundary, create a translucent texture or add vertex‑based vegetation at the edges to soften the seam.

Performance Tuning

Even after decimation, multiple high‑detail models can tank your FPS. Here are strategies to keep the sim smooth:

  • Limit draw distance – In WED, you can set a “visibility range” for each object. Keep main photogrammetry objects visible within 2–3 km; distant views can use generic terrain.
  • Combine objects – Merge several small models into a single OBJ to reduce draw calls (but maintain separate LOD groups if needed).
  • Use instancing – For repeated objects like lampposts or trees, use X‑Plane’s instancing system (ATTR_instance) to render many copies with one draw call.
  • Monitor VRAM – Keep the total texture memory within your GPU’s limits. Use the X‑Plane data output (Shift+F1) to watch VRAM usage during flight.

Troubleshooting Common Issues

Even careful workflows can produce problems. Here are fixes for frequent pitfalls:

Model Appears Black or Missing Textures

Check that your texture file is in a format X‑Plane supports (PNG or DDS). Ensure the texture path in the OBJ file is relative to the scenery folder (e.g., TEXTURE ../textures/mytexture.png) and that the file exists.

Model Hovering Above Ground or Sinking

Adjust the Y‑offset in WED’s object properties, or edit the OBJ file’s vertex coordinates. For large terrains, consider baking the ground elevation into the mesh itself so that the bottom of the model matches the DSF height.

Seams Show Between Photo Texture and Default Terrain

Increase the orthophoto coverage area to overlap the default terrain by at least 200–300 meters. Use feathering in image editing software to blend the edges.

Low Frame Rate Only Near Your Scenery

Your model is likely too dense. Reduce polygon count further or split the area into LOD groups. Also check that you haven’t accidentally left the ultra‑high‑detail LOD active at long distances.

Advanced Techniques: Custom Mesh Terrain

For those willing to go even further, you can replace X‑Plane’s base terrain mesh entirely with a photogrammetry‑derived elevation mesh. This gives you exact real‑world slopes, ridges, and even road embankments. The process involves:

  • Exporting a DEM (digital elevation model) from photogrammetry software.
  • Converting the DEM into a 3D mesh triangle strip.
  • Using Ortho4XP’s “Custom DEM” option to insert your height data.

This technique requires more advanced GIS knowledge, but the results are stunning for areas with complex topography (e.g., mountain airstrips, river valleys).

Before uploading your photogrammetry scenery to the X‑Plane.org forum or other repositories, ensure you have the right to distribute the base imagery and derived 3D models. If you used public satellite imagery, check the license (many allow non‑commercial redistribution with attribution). For drone‑captured images, you own the copyright, but you must follow local privacy laws (do not capture identifiable people or private property without consent).

If you share your work, include a README with the source of your data, the software used, and any required libraries. This transparency helps other users trust and build upon your work.

Conclusion

Photogrammetry has the power to transform X‑Plane’s global scenery from a generic approximation into a precise digital twin of the real world. By carefully capturing source imagery, processing it into optimized 3D meshes, and integrating those models with the simulation’s terrain and autogen systems, you can create flying experiences that are not only visually stunning but also genuinely useful for VFR navigation, procedural training, and pure enjoyment. Start with a small, well‑defined area—such as your home airport or a nearby landmark—and iterate. Over time, the skills and techniques you develop will let you tackle entire regions, bringing the accuracy of photogrammetry to the entire X‑Plane community.