Use AutoOrtho with SimHeaven X-World in X-Plane 12. Get the correct scenery order and fixes for duplicate roads, missing objects and blank tiles.
Yes. In X-Plane 12, AutoOrtho and SimHeaven X-World are complementary: AutoOrtho supplies streamed photographic ground textures and base mesh, while X-World adds roads, buildings, forests and landmarks. Install them separately, put airports above X-World, keep X-World above AutoOrtho, and start AutoOrtho before launching the simulator.
How AutoOrtho and X-World work together
AutoOrtho and X-World perform different jobs, so one does not replace the other. AutoOrtho changes the terrain beneath the aircraft; X-World is primarily an overlay placed on top of that terrain.
- AutoOrtho: photographic ground imagery, terrain mesh and streamed texture data.
- SimHeaven X-World: buildings, roads, forests, power lines, regional details and other objects derived from geographic data.
- Airport scenery: runways, terminals, taxiways and airport-specific objects, which normally take the highest priority.
The installed regions must cover the area where you fly. An AutoOrtho region can work without the matching X-World region, and vice versa, but you will only receive the features supplied by the scenery that covers that location.
How do I configure AutoOrtho with X-World?
- Install and test AutoOrtho first. Confirm that its selected region mounts correctly and appears in X-Plane before adding another variable. Our AutoOrtho mounting and cache instructions cover the platform-specific setup.
- Install the matching X-World region. Extract its component folders directly into
X-Plane 12/Custom Scenery. Install the required vegetation library as well; our X-World folder and library checklist explains the expected layout. - Check for nested folders. Each scenery folder should contain its configuration and scenery files directly. A path such as
Custom Scenery/X-World/X-World-region-folderis usually one level too deep. - Start AutoOrtho before X-Plane. Wait until its virtual scenery mount is ready, then launch X-Plane 12. Starting the simulator first can leave the AutoOrtho entries unavailable.
- Let X-Plane register the packages. Reach the main menu, close the simulator, then open
Custom Scenery/scenery_packs.iniin a plain-text editor. - Reorder the scenery entries. Keep airports at the top, X-World in the middle and AutoOrtho's base-mesh entries near the bottom.
Do not merge AutoOrtho and X-World folders. They must remain separate so X-Plane can apply their scenery priorities correctly and so each package can be updated without damaging the other.
Which scenery_packs.ini order should I use?
X-Plane gives entries near the top of scenery_packs.ini higher priority than entries below them. A practical order is:
| Priority | Scenery type | Placement |
|---|---|---|
| Highest | Custom airports and *GLOBAL_AIRPORTS* | Above regional overlays |
| High | SimHeaven X-World component folders | Below airports, above AutoOrtho |
| Medium | Optional AutoOrtho overlay, often named yAutoOrtho_Overlays | Below every X-World layer |
| Low | AutoOrtho photographic base-mesh or mount entries | Near the bottom |
| Lowest | Other custom meshes that AutoOrtho should override | Below AutoOrtho |
Keep the X-World component folders in the order supplied with the package. They are normally arranged numerically from the -1-vfr layer near the top through to the network layer lower down. Do not reverse them or scatter unrelated scenery between the components.
AutoOrtho folder names vary by region and release, so identify them by the folders created or mounted by AutoOrtho rather than renaming them. X-Plane may put newly discovered packages at the top automatically, which is why the file should be checked after installing or mounting a region.
Should yAutoOrtho_Overlays remain enabled?
The optional AutoOrtho overlay can remain enabled if it sits below all X-World entries. X-World's higher-priority exclusions should replace much of the lower autogen within its coverage, while the AutoOrtho overlay can still provide objects outside that coverage.
If you see two sets of roads, overlapping buildings or unusually dense forests, disable the AutoOrtho overlay temporarily by changing its line to SCENERY_PACK_DISABLED. Keep the AutoOrtho base-mesh entries enabled; disabling the overlay does not disable the photographic ground textures.
Why are buildings, roads or photographic tiles missing?
| Symptom | Likely cause | Fix |
|---|---|---|
| Default ground textures appear | AutoOrtho was not mounted before X-Plane started | Close X-Plane, start AutoOrtho, confirm the mount and relaunch. Use our AutoOrtho mount troubleshooting steps if the mount never becomes available. |
| No X-World buildings | Nested folders, disabled entries or missing regional coverage | Check the folder depth and confirm every required X-World layer is enabled above AutoOrtho. |
| Missing-library warning | The X-World vegetation library is absent or incorrectly extracted | Install the required library and inspect Log.txt for the exact missing path. |
| Duplicate roads or buildings | An additional overlay is above X-World | Move that overlay below X-World or disable it for a comparison flight. |
| One tile loses photographic imagery | A custom airport includes its own base mesh | Use an airport package without mesh when available, or accept that the airport mesh replaces AutoOrtho for that tile. |
Only one base mesh can control a given tile. Raising AutoOrtho above an airport mesh restores the photographic terrain but may remove airport-specific terrain shaping, so this is a choice rather than a simple priority error.
How does this combination affect performance?
AutoOrtho and X-World stress different parts of the system. Pauses while approaching a new tile usually point to AutoOrtho downloading, cache or storage performance; a frame-rate loss over dense cities is more likely caused by X-World object density.
For city performance problems, reduce X-Plane's object-density setting before removing X-World layers. For delayed or blank photographic tiles, check AutoOrtho's mount, available cache space and connection rather than lowering object density.