Why does X-Plane 12 crash or fail to start?
X-Plane 12 usually crashes or refuses to start because of an incompatible plug-in, damaged preference or installation files, a graphics-driver/Vulkan/Metal problem, insufficient RAM or VRAM, or broken scenery. Start it with all third-party content removed, inspect the fresh Log.txt, reset preferences, then repair the installation before considering a full reinstall.
What should I do when X-Plane 12 will not start?
Use a clean-start test to separate an X-Plane problem from an add-on or system problem.
- Preserve the log. Copy
Log.txtfrom the main X-Plane 12 folder immediately after the crash. X-Plane rewrites this file on the next launch, so do not run repeated tests before saving the useful copy. - Remove third-party plug-ins. Move only the plug-in folders you installed from
Resources/pluginsto a temporary folder outside X-Plane. Do not remove Laminar-supplied components. Aircraft may contain their own plug-ins, so use a default aircraft when the menu becomes available. Our guidance on correct X-Plane add-on folders and dependencies covers the nesting mistakes and incompatible files we see most often. - Reset preferences safely. Rename or move
Output/preferencesrather than deleting it. X-Plane will create fresh preferences at launch. If that works, rebuild settings and control assignments instead of restoring the entire old folder. - Repair the simulator files. Use the standalone installer’s update or repair function, or the file-verification option supplied by your installation platform. Back up user content first; our X-Plane 12 installation and repair steps explain when a clean installation is justified.
- Check the graphics path. Install a stable driver suitable for the GPU, disable overlays and graphics injectors, and return any GPU or CPU overclock or undervolt to standard settings. X-Plane 12 uses Vulkan on Windows and Linux and Metal on macOS, so a driver or device-initialisation failure can stop it before the main menu appears.
- Run a simple default flight. Select a Laminar aircraft, a default airport, clear weather and modest graphics settings. This removes complex aircraft, scenery and high rendering load from the test.
- Restore content in batches. Add plug-ins, aircraft and scenery back one category at a time. If a category causes the crash, test half its packages at a time until the specific add-on is identified.
Plug-ins are the first suspect when X-Plane crashes before reaching the menu. Custom scenery is more likely to matter after a flight starts loading, although scenery-management utilities and other global plug-ins can run earlier.
How do I read X-Plane 12 Log.txt after a crash?
Log.txt records what X-Plane loaded, which makes the crash timing more useful than a generic operating-system error.
Read upwards from the bottom and look for a named plug-in, aircraft, scenery package, graphics-device error or memory warning. The final line is only a clue: a component named there may have loaded successfully just before a different component failed.
| Crash timing or log clue | Most likely area to test |
|---|---|
No window and no useful Log.txt | Damaged executable, permissions, security software or graphics initialisation |
| Stops while loading plug-ins | Third-party plug-in, missing dependency or incompatible binary |
| Crashes with one aircraft only | Aircraft files, scripts or an aircraft-specific plug-in |
| Crashes at one airport or region | Custom scenery, a missing library or corrupted orthophoto data |
| Mentions device loss, Vulkan, Metal or memory | GPU driver, VRAM/RAM pressure, overclock or rendering settings |
| Random crashes in every scenario | Global plug-in, driver, overheating, unstable hardware or system memory |
Can an X-Plane 11 add-on crash X-Plane 12?
Yes. An aircraft, plug-in or script made for X-Plane 11 is not automatically compatible with X-Plane 12, even if its files appear in the menus.
Native plug-ins must also match the operating system and processor architecture. On a Mac, for example, an older plug-in may lack a compatible Apple silicon build; on any platform, an outdated plug-in can call simulator functions that have changed. Confirm explicit X-Plane 12 support rather than treating a successful installation as proof of compatibility.
Why does X-Plane 12 crash while loading scenery?
A location-specific crash usually points to a damaged scenery package, incorrect folder nesting, a missing dependency or excessive memory use.
Test the same aircraft and weather at a default airport. If that works, remove the suspect airport, mesh or orthophoto package and inspect its entries in Log.txt. Missing library objects often produce a scenery-loading error rather than a complete application crash, but they still need correcting; see our explanation of scenery-library placement and OpenSceneryX errors.
Large orthophoto areas, detailed airports, high-resolution textures and complex weather can exhaust system memory or place heavy pressure on VRAM. Lower settings temporarily and close memory-heavy applications. If that prevents the crash, adjust the settings that control graphics quality and VRAM load instead of reinstalling the simulator.
Should I reinstall X-Plane 12?
Repair the existing installation first; reinstalling is not the best first response to an X-Plane 12 startup crash.
A reinstall into the same folder may leave the faulty plug-in, scenery and preferences untouched, producing exactly the same failure. If repair and clean-start tests do not work, install or test an untouched copy in a separate folder where your installation channel permits it. Launch that copy before adding any aircraft, scenery, plug-ins or old preferences.
What if a clean X-Plane 12 installation still crashes?
If an untouched installation crashes with a default aircraft and scenery, concentrate on the graphics driver, operating-system permissions and hardware stability.
- Make sure a laptop is using its dedicated GPU rather than a low-power integrated adapter.
- Disable overlays, recording hooks, reshading tools and hardware-monitoring injectors.
- Return overclocked or undervolted components to their standard configuration.
- Check free disk space, system memory and cooling, especially if other demanding applications also fail.
- On macOS, review security prompts for blocked components; on Linux, check the log for missing system libraries or permissions.
If the clean default test remains reproducible, retain the complete Log.txt and any crash-report files X-Plane generated. A useful developer report includes the operating system, CPU, GPU, driver, RAM, exact aircraft and airport, and the shortest sequence that reproduces the crash. Report a third-party-only failure to that add-on’s developer; report a clean default-simulator failure through X-Plane’s official bug-report channel.