General

Can I use Ortho4XP and simHeaven?

Yes. Ortho4XP provides an updated bash mesh (the 3-dimension surface) and texture layer (the orthophotos you see) and simHeaven provides an updated objects (buildings, trees, etc.) as an overlay. In fact, it's ideal to run both together since the simHeaven object placement is based on real world data so it should mostly match the orthophoto imagery.

Issues

When I try to launch Ortho4XP, I get a popup message with the error ""Python.framework" is damaged and can't be opened. You should move it to the Trash."

This is likely due to a permissions issue with macOS. Make sure you performed the additional steps for macOS on the installation page.

When building a tile, an error in the console asserts, "ERROR : could not rename DSF file, tile is not active."

Make sure the custom_overlay_source is set to your X-Plane 12 Global Scenery directory (e.g., ../X-Plane 12/Global Scenery/X-Plane 12 Global Scenery).

When building a tile, an error in the console asserts, "ERROR: Triangle4XP really couldn't make it !"

Try adjusting the min_angle for the tile configuration to a value in the 0-5 range.

Why does there appear to be a gap or shadow between the land and water?

This happens if custom_overlay_src is not set to the X-Plane 12 Global Scenery directory or if it set, the tile with the issue is likely in an area where the Earth nav data is in the X-Plane 12 Demo Areas directory. In the latter case, the custom_overlay_src_alternate can be set to the X-Plane 12 Demo Areas such that if the Earth nav data is not found in the custom_overlay_src directory, the custom_overlay_src_alternate directory is searched.

Why are there some "bumpy" runways?

This is likely caused by an issue with the OSM data resulting in the airfield not being appropriately flattened. To fix this, encode its boundary as a closed way on OSM (don’t forget to add the tag ”aeroway”=”aerodrome”, then (optional but recommended) one tag for its name and one for its ICAO code). Pay attention to reuse as much as possible existing OSM nodes, and to close the way.

Why is one of the tiles completely filled with water?

There is likely an incorrectly tagged feature in OSM as a coastline in an area where it does not exist. To fix this, you can manually open the OSM coastline file in the JOSM application, delete the incorrectly placed coastline and re-build the tile. The OSM coastline file is located in Ortho4XP/OSM_data/tile_folder/specific_tile/*_coastline.osm.bz2. To prevent issues for future users, you should also submit a change to OSM.

Why do some of my orthophotos have white squares?

This is due to a server issue of the orthophoto provider. This version of Ortho4XP will automatically delete orthophoto .jpeg and .dds files with white squares and attempt to redownload and reconvert the orthophoto. This only occurs once and there is a chance on this second attempt, there's still server issues. If that's the case, a summary should be provided at the end of the build process with which orthophotos still have white squares. You can attempt to redownload and rebuild them again by searching for the specific orthophoto name, both the .jpeg and .dds file, deleting them, and running the tile build process again.

When using custom DEM files, Viewfinderpanorama tiles are downloading and overriding the custom dem.

When using custom DEM files, first, make sure the custom_dem setting is blank in the Tile Config. You also need to have all of the custom DEM files that surround the tile you're trying to build or else Viewfinderpanorama DEM files will be downloaded and override your custom DEM files.

When I build a tile, only a single (or a couple) orthophotos seem to be created.

There is likely an incorrectly marked coastline in the OSM data. For example, if the tile at +50+006 is having this issue, open the coastline OSM file in the OSM_data/+50+000/+51+006 titled +51+006_coastline.osm.bz2 using an application such as JOSM. Look for a coastline that is incorrectly marked (e.g., water feature inland that is marked as a coastline) and either rename or delete it. Save the file and rebuild the tile. It's also recommended to update this in OpenStreetMaps so the issue is fixed for other users.