Why does X-Plane crash after installing scenery?

X-Plane, especially X-Plane 12, usually crashes after new scenery is installed because the package is corrupt or incompatible, a required library is missing, a bundled plug-in fails, or the added mesh and textures exceed available RAM or VRAM. Remove the package, reproduce the same load, then inspect the fresh Log.txt.

We use X-Plane 12 terminology below, but the same isolation process applies to X-Plane 11. Airports, libraries and compiled plug-ins must still be compatible with the X-Plane generation and operating system on which they run.

What kind of X-Plane crash are you seeing?

A desktop crash, a stalled scenery scan, a loading warning and an aircraft collision are different faults, even though simmers often describe all four as a crash.

A localised operating-system message such as è crashato only means that the application exited unexpectedly. It does not establish that scenery caused the failure; the controlled removal test and Log.txt provide that evidence.

How do I find which scenery is crashing X-Plane 12?

The quickest reliable test is to move the complete new package outside Custom Scenery and repeat the same flight. Do not reinstall X-Plane first: reinstalling the simulator while retaining the faulty add-on usually changes nothing.

1. Preserve the failed session's log. Before opening X-Plane again, copy Log.txt from the simulator's root folder to another location. X-Plane rewrites this file on the next launch.
2. Record a repeatable test. Note the airport, runway and point at which the failure occurs. Use a default aircraft for subsequent tests so an aircraft plug-in does not become a second variable.
3. Quarantine every supplied folder. Move all folders installed with the new scenery completely outside Custom Scenery. A download may contain separate airport, overlay, mesh and library folders. Merely adding disabled text to a folder name is unreliable because X-Plane can still scan it.
4. Repeat the same load. If the location now opens normally, the removed package or the extra memory it demanded caused the failure. If it still crashes, test a different location and continue to the clean-baseline checks below.
5. Inspect the folder structure. The directory containing the actual package files must be directly inside Custom Scenery. An extra wrapper such as Custom Scenery/My Airport/My Airport/Earth nav data prevents normal discovery. Our guide to checking an X-Plane 12 scenery installation and its folder layout covers the correct structure.
6. Install complete dependencies. Read the package documentation and confirm that every required object library is present, extracted and enabled. Do not copy individual objects out of libraries or merge unrelated library folders. Use our library installation and missing-resource checks when the log names an unresolved object, facade or texture.
7. Test components separately. Restore the airport, overlay and mesh one folder at a time, restarting X-Plane after each change. The component that restores the crash is the useful finding; adding everything back together proves nothing.
8. Replace damaged files cleanly. If the log names a DSF, terrain, object or texture inside the package, remove the old copy before extracting a complete replacement. Extracting over an incomplete installation can leave obsolete or corrupt files behind.

A mistake we see constantly is treating a missing library warning as proof of the desktop crash. X-Plane can often continue with buildings or objects absent. A corrupt DSF, invalid asset, memory failure or compiled plug-in is more likely to terminate the process.

Some airport packages include a plugins folder for animated systems or other local features. Temporarily move that folder outside the scenery package and retest. If the crash stops, the binary may be incompatible with the operating system or X-Plane version; the airport may load without it, but its plug-in-driven features will not work.

Why is X-Plane 12 stuck on reading new scenery files?

X-Plane 12 can remain on Reading new scenery files while indexing a large or newly changed Custom Scenery folder, but a repeatable stall usually points to the newest package, inaccessible storage or a scenery index it cannot finish updating.

1. Allow one genuine first scan to finish. Adding many packages on slow storage can take longer than an ordinary start. Continuing disk activity suggests that the scan is still working rather than frozen.
2. Remove the newest folders. Once the application is clearly unresponsive, close it, preserve Log.txt, and move the latest additions outside Custom Scenery. Relaunch before changing anything else.
3. Check that the download was extracted. Do not place a ZIP, 7z archive or cloud-only placeholder in Custom Scenery. Confirm that external storage is connected and that any linked folder resolves to a real, readable location.
4. Check write access and free space. X-Plane must be able to update files in its installation, including scenery_packs.ini. A full disk, read-only folder or interrupted extraction can leave the scan incomplete.
5. Rebuild the index only as a diagnostic. Back up Custom Scenery/scenery_packs.ini, remove the original and start X-Plane with the suspect package still quarantined. X-Plane will generate another file, but deliberate scenery ordering must then be restored.

Repeatedly deleting scenery_packs.ini is not a cure for a damaged package. If the stall returns as soon as one folder is restored, keep that folder out and inspect or replace it.

What should I check in X-Plane Log.txt?

The most useful evidence is normally in the final few dozen lines of the Log.txt produced by the failed session. Read upwards from the end and look for a package name, DSF tile, resource path, scenery plug-in or graphics-memory message.

The last package named is not automatically guilty. It may simply be the last item X-Plane loaded successfully before another component or the graphics driver failed. The removal-and-reproduction test is stronger evidence than one isolated log line.

Why does X-Plane 12 report a GPU crash after installing scenery?

An X-Plane 12 GPU crash after adding scenery can be caused by VRAM pressure, but it can also be a graphics-driver or hardware-stability fault exposed by the heavier load. High-resolution orthophotos, dense objects, a complex aircraft and large displays all compete for graphics memory.

• Choose an asset diagnosis when the crash occurs with one package or tile even at reduced settings, and disappears whenever that package is removed.
• Choose a memory diagnosis when several dense airports fail, lowering texture quality prevents the crash, or a default aircraft succeeds where a complex add-on aircraft does not.
• Choose a broader graphics diagnosis when stock scenery and a default aircraft also produce graphics-device errors. Check the normal graphics-driver installation, remove GPU overclocks and disable third-party graphics overlays before testing again.

Change one setting at a time and restart before the next comparison. Lower texture quality first for suspected VRAM pressure; reduce object density and rendering resolution if the entire scene is unusually heavy. These changes are diagnostic: if only one package remains unstable at conservative settings, replacing or removing that package is better than permanently degrading every flight.

Can scenery_packs.ini order make X-Plane crash?

Incorrect scenery_packs.ini order usually causes missing airports, duplicate buildings, misplaced overlays or absent orthophotos rather than a desktop crash. Airports and overlays generally need higher priority than orthophoto and base-mesh packages, and X-Plane uses the highest-priority base mesh available for a tile rather than combining several meshes.

Reordering can appear to fix a crash when it stops the defective package from being selected, but the underlying package remains bad. Keep a backup before editing the file, and use our explanation of airport, overlay and mesh priority in X-Plane 12 when scenery layers are competing.

Why does X-Plane crash only near one airport?

A crash limited to one airport or geographical area usually indicates a damaged DSF tile, invalid terrain reference, scenery plug-in or memory spike as X-Plane loads that region. A bad tile can remain hidden until departure, arrival or the moment the aircraft crosses a tile boundary.

• Remove the airport and any orthophoto or mesh package covering that tile, then repeat the route.
• Look for the tile or package name near the end of Log.txt.
• Test a default aircraft and temporarily lower texture quality to distinguish a defective file from total memory demand.
• Confirm that every terrain file and texture finished extracting and that the storage device has sufficient free space.
• Restore the airport, overlay and mesh separately rather than treating them as one package.

If only one orthophoto tile fails after a clean extraction, leave that tile disabled. Moving overlays above orthophotos can fix missing roads or buildings, but it cannot repair a corrupt texture or terrain definition.

Is this an X-Plane 12 crash physics problem?

If the application stays open but the aircraft hits terrain, bounces on a runway or resets after impact, the problem is not an X-Plane software crash. New scenery can introduce a conflicting mesh, runway-elevation mismatch or hard surface that causes a physical collision.

Retest the airport without the add-on and check for duplicate airport or mesh packages covering the same area. If the aircraft behaves normally with stock scenery, isolate the airport, overlay and mesh components just as you would for a desktop crash.

That is different from a dedicated plane crash simulator. X-Plane is a flight simulator that represents impacts and aircraft failures, but it is not a detailed plane crash sim with comprehensive structural deformation. Installing scenery does not normally alter global crash physics, although a bundled plug-in or incorrectly authored hard surface can affect behaviour at that location.

What if X-Plane still crashes after the scenery is removed?

If the same failure continues with the new package completely outside Custom Scenery, the installation may only have exposed an unrelated aircraft plug-in, global plug-in, graphics or stock-file problem.

1. Test a clean combination. Use a default aircraft at a stock airport in a different region.
2. Remove other third-party add-ons temporarily. Check global plug-ins separately from scenery plug-ins. Leave stock global scenery and other simulator-supplied packages in place.
3. Verify the simulator files. Use the installation platform's repair or verification process before attempting a complete reinstall.
4. Capture another fresh log. Compare it with the scenery-related failure rather than relying on a log from a different test.

If stock scenery and a default aircraft still fail, follow our structured X-Plane 12 crash-isolation process to separate plug-ins, preferences, graphics settings, memory and damaged simulator files. Reinstalling over an existing Custom Scenery folder should be a last resort because it can preserve the original fault.