Fix X-Plane 11 crashes or freezes while loading: read Log.txt, isolate plug-ins and scenery, reset preferences, and repair damaged files.
X-Plane 11 usually crashes or stops responding while loading because a third-party plug-in, aircraft or scenery package is incompatible, a preference or shader cache is corrupt, or the system runs out of memory. Check the fresh Log.txt, then test a clean, default flight before repairing or reinstalling anything.
Is X-Plane 11 frozen or just loading slowly?
An operating-system “Not Responding” message does not prove X-Plane 11 has crashed. The simulator's main thread can become unresponsive while it reads large scenery packages, builds shaders or loads a complex aircraft.
Watch whether CPU or disk activity continues and whether Log.txt is still changing. If both continue, let the load finish. A genuine hang shows no progress for a prolonged period; a crash closes X-Plane or produces an error or crash report.
Large orthophoto scenery, a newly rebuilt shader cache and the first load after installing scenery can all take longer than an ordinary flight. Repeatedly force-closing X-Plane during these operations can make diagnosis harder.
How do I find what makes X-Plane 11 crash?
The quickest reliable method is to read the latest log and remove third-party components until X-Plane loads normally.
- Preserve the latest log. After the crash, open
Log.txtin the main X-Plane 11 folder before launching the simulator again. Each new run replaces the useful evidence from the previous session. - Read the final section carefully. Look for a named plug-in, aircraft, scenery package, graphics API error or memory warning. The last line is a clue rather than proof: a native plug-in or graphics driver can terminate X-Plane before the real cause is written to the log.
- Try a stock flight. Select an aircraft supplied with X-Plane 11 and an airport using default scenery. If this works, the failure belongs to the aircraft, livery, airport scenery or related dependency used by the original flight.
- Disable third-party plug-ins. Move user-installed plug-in folders and files out of
X-Plane 11/Resources/plugins, leaving X-Plane's own components untouched. Aircraft can also contain private plug-ins inside their aircraft folder, so a stock-aircraft test matters. - Remove user-added scenery temporarily. Move only packages you installed out of
Custom Scenery, including their extra libraries, and test a default airport. Deletingscenery_packs.inialone does not disable a defective package; it merely makes X-Plane rebuild the load order. Our guide to correct add-on folder structure and dependency checks explains the common installation mistakes. - Reset the preferences. With X-Plane closed, rename
Output/preferencesto a backup name. X-Plane will create clean preferences at the next start. This resets graphics, controls and other settings, so retain the backup until the fault is confirmed. - Rebuild the shader cache. Rename or remove
Output/shadercachewhile X-Plane is closed. The next load may be slower while the cache is regenerated. - Add components back in batches. Restore half the disabled packages, test, and repeat with progressively smaller groups. This is much faster than reinstalling everything or testing dozens of add-ons individually from the start.
A mistake we see constantly is changing plug-ins, scenery, drivers and preferences simultaneously. Make one category of change at a time, or a successful launch will not reveal which action fixed it.
What does the loading stage reveal?
The loading phase usually identifies which part of X-Plane 11 needs to be isolated next.
| Where loading stops | Likely cause | Best next test |
|---|---|---|
| Before the main menu while plug-ins initialise | Global plug-in, damaged preference or security software blocking a plug-in file | Remove third-party files from Resources/plugins and reset preferences |
| While loading one aircraft | Aircraft-specific plug-in, incompatible aircraft version, livery texture or missing dependency | Load a stock aircraft at the same airport |
| While reading or initialising scenery | Broken scenery, generated scenery, missing library, mesh conflict or exhausted memory | Test a default airport after removing user-added scenery |
| While preparing shaders or the world | Corrupt shader cache, graphics driver problem, Vulkan or Metal issue, or unstable GPU settings | Rebuild the shader cache and test the OpenGL renderer where available |
| After an out-of-memory message | Insufficient RAM, virtual memory or VRAM for the selected aircraft and scenery | Close other applications, restore system-managed virtual memory and reduce texture or scenery demands |
Missing scenery-library warnings do not automatically explain a hard crash; they often produce absent objects instead. Give more weight to the package loaded immediately before the failure, explicit memory errors and repeated plug-in faults.
If the problem began after installing generated map scenery, check its helper plug-ins, cache and scenery packages using our generated-scenery installation and troubleshooting steps.
What if X-Plane 11 still crashes without add-ons?
If a stock aircraft, default scenery and an empty third-party plug-in set still fail, the likely causes are damaged simulator files, graphics software, memory pressure or an operating-system restriction.
- Repair the simulator files: use the standalone X-Plane installer or updater to scan the installation, or the game client's file-verification function for a managed installation. Do not assume this checks third-party content.
- Check the graphics driver: install a suitable stable driver, or roll back if crashes started directly after a driver change. On macOS, graphics components are supplied through operating-system updates.
- Test another renderer: if the log mentions Vulkan, Metal, device loss or shader compilation, temporarily use OpenGL where X-Plane 11 offers it. Also remove GPU or CPU overclocks during testing.
- Check memory and storage: retain adequate free disk space, allow the operating system to manage virtual memory, and close memory-heavy applications. Detailed orthophotos and high-resolution aircraft textures can exhaust RAM or VRAM during loading.
- Review permissions and security software: a protected installation folder or quarantined plug-in file can prevent loading. Restore only files you recognise and trust; do not disable security protection permanently.
Will reinstalling X-Plane 11 fix the loading crash?
Reinstalling into the same folder often does not fix the problem because preferences, plug-ins, aircraft and custom scenery can survive or be copied straight back. Repair the core files first.
If repair fails, install a clean copy in a separate writable folder and run it with only stock content. Follow the correct X-Plane 11 installer and folder setup, then test before adding anything. If the clean copy works, restore add-ons in small batches; if it also crashes, concentrate on the graphics driver, operating system, memory and hardware stability rather than scenery load order.