Fix X-Plane crashes after scenery installs by checking Log.txt, isolating the package, repairing libraries and testing mesh, plug-ins and memory.
X-Plane usually crashes after a scenery installation because the package contains corrupt or incompatible data, a required library is absent, a bundled plug-in fails, or high-resolution mesh and orthophotos exhaust memory. Remove the new package, restart at the same location, then inspect the fresh Log.txt to identify the exact fault.
How do I find which scenery is crashing X-Plane?
The quickest reliable method is to quarantine the new scenery and add its components back one at a time. Do not reinstall X-Plane before completing this test; a full reinstall rarely fixes a faulty package in Custom Scenery.
- Preserve the crash log. Before launching X-Plane again, copy
Log.txtfrom the simulator’s root directory to another location. X-Plane rewrites this file during the next session. - Move the new scenery out. Move every folder supplied by the package completely outside
Custom Scenery. Renaming a folder while leaving it there is less reliable because X-Plane may still detect it. - Repeat the same test. Load the same airport or geographical area, preferably with a default aircraft. If X-Plane now loads normally, the removed package or the extra memory it required caused the failure.
- Check the folder structure. The actual scenery package should sit directly inside
Custom Scenery. A mistake we see constantly is an extra wrapper folder, such asCustom Scenery/My Airport/My Airport/Earth nav data. Our guide to checking downloaded scenery folders and installation explains the expected package layout. - Install every dependency. Read the supplied documentation and confirm that each required object library is installed, extracted and enabled. Do not copy isolated objects between libraries; use the complete library package. See our scenery library installation and fault checks if the log reports missing resources.
- Test package components separately. If the download supplied an airport, overlay and mesh as separate folders, restore one at a time. Restart X-Plane after each change so the failing component is unambiguous.
- Replace suspect files. Re-extract or re-download the package if the log points to a DSF, texture or object inside it. Incomplete archives and interrupted extractions can leave files present but unreadable.
Some scenery includes its own plugins folder for animated features or airport systems. A compiled plug-in can cause a genuine desktop crash, especially if it was built for another operating system or simulator generation. Temporarily move that scenery’s plug-in folder outside the package and test again; this is a diagnostic step, and some airport functions will remain unavailable without it.
What should I check in X-Plane Log.txt?
The useful clue is normally near the end of the Log.txt created by the failed session. Read upwards from the final line and look for the new package’s folder name, a DSF tile, an unresolved library resource, a plug-in path or a memory warning.
| Log clue | Likely cause | Next action |
|---|---|---|
New scenery name or .dsf file immediately before the failure | Corrupt or incompatible scenery data | Remove that component, then obtain and extract a clean copy |
| Failed resource, object, facade or library reference | Missing, disabled or incorrectly nested library | Install the named dependency and verify its folder structure |
Path to a binary inside a scenery plugins folder | Faulty or incompatible scenery plug-in | Test without that plug-in and use a compatible replacement if available |
| Memory, allocation or graphics-memory warning | The combined aircraft, scenery and texture load is too high | Reduce texture and object settings, then test a default aircraft |
| Log ends abruptly without a scenery reference | Hard plug-in, graphics-driver or system-level failure | Repeat the test with all third-party scenery removed |
A missing object does not always mean X-Plane has crashed. The simulator may display a warning that scenery could not be loaded and continue running with missing buildings. A return to the desktop, frozen process or crash reporter indicates a deeper failure.
Can scenery_packs.ini order make X-Plane crash?
Incorrect scenery_packs.ini order usually causes missing airports, flattened buildings, overlapping terrain or absent orthophotos rather than a desktop crash. Airports and overlays normally need higher priority than base mesh and orthophoto packages, while only the highest-priority base mesh for a tile is used.
Reordering can appear to cure a crash if it prevents X-Plane from loading the defective package, but that package remains faulty. Do not repeatedly delete scenery_packs.ini as a general fix: X-Plane will regenerate it, but any deliberate ordering is lost. Keep a backup before making manual changes.
Why does orthophoto scenery crash only near one airport?
An orthophoto failure confined to one area usually points to a damaged tile, invalid terrain reference or a memory spike when X-Plane loads that region. X-Plane loads scenery around the aircraft, so a bad tile may remain hidden until departure, arrival or an in-flight boundary crossing.
- Remove the orthophoto package covering that tile and repeat the flight.
- Test with a default aircraft to reduce the plug-in and texture load.
- Lower texture quality and object density temporarily. If that prevents the crash, total memory demand is the likely trigger.
- Check that overlays sit above orthophoto or mesh packages in
scenery_packs.ini. - Confirm there is enough free storage and that every texture and terrain file finished extracting.
Large photo packages need the right folder structure, coverage and load order. Our orthophoto installation and troubleshooting steps cover those checks without duplicating them here.
What if X-Plane still crashes after the scenery is removed?
If X-Plane still crashes with the new scenery completely outside Custom Scenery, the installation may only have exposed an unrelated plug-in, graphics or memory problem. Test with a default aircraft, disable other third-party add-ons, verify the simulator’s stock files and reproduce the failure at a different airport.
Do not remove stock global scenery during this isolation process. If the crash persists in an otherwise clean installation, follow our structured X-Plane 12 crash-isolation process to separate scenery faults from plug-ins, preferences, graphics settings and damaged simulator files.