Skip to content
X-Plane 9 min read 1.2k views

Why does X-Plane 12 crash on startup or fail to start?

Adam McEnroe
In short

Fix X-Plane 12 crashes on startup, GPU device-loss errors, plug-in and scenery faults, plus aircraft engines that will not start.

“X-Plane 12 will not start” means the simulator application crashes or never opens; “the aircraft engine will not start” is a cockpit-procedure issue. For an application startup crash, save Log.txt, remove third-party plug-ins, reset preferences, repair the installation, then test a Laminar aircraft with default scenery and conservative graphics settings.

X-Plane 12 crashes on startup: use this clean-start order

A clean-start test separates a damaged simulator or system problem from an incompatible add-on.

  1. Preserve the failed launch log. Copy Log.txt from the main X-Plane 12 folder immediately after the crash. X-Plane rewrites it on the next launch, so repeated attempts can erase the useful evidence.
  2. Identify the loading stage. Read upwards from the bottom of the log and note whether it stopped during graphics initialisation, plug-in loading, aircraft loading or scenery loading. The final named component is a clue, not proof that it caused the crash.
  3. Disable third-party plug-ins. Move the plug-in folders you installed from Resources/plugins to a temporary folder outside X-Plane. Leave Laminar-supplied components in place. Aircraft can also contain plug-ins inside their own folders; our folder-layout and dependency checks for X-Plane add-ons cover the nesting errors we see regularly.
  4. Reset preferences safely. Rename or move Output/preferences rather than deleting it. X-Plane will generate clean preferences, and you can keep the old folder as a backup. If this fixes the launch, rebuild graphics, controls and other settings instead of copying the whole faulty folder back.
  5. Remove user scenery from the test. Temporarily move only the packages you added from Custom Scenery. Do not remove Laminar content. This matters when the log reaches scenery loading or the failure occurs only at one airport.
  6. Repair the core files. Use the installer’s update or repair function, or the verification facility supplied by the installation platform. Repair before reinstalling because it replaces missing or altered simulator files without deliberately retaining a damaged executable.
  7. Run a minimal flight. Choose a Laminar aircraft, default airport, standard weather and modest graphics settings. If that works, the base simulator and graphics path can at least run that controlled scenario.
  8. Restore add-ons in batches. Add plug-ins, aircraft and scenery back one category at a time. When the crash returns, test half of that batch at a time until one package or combination is isolated.

What do the crash timing and Log.txt evidence mean?

The last completed loading stage in Log.txt determines which part of X-Plane 12 should be tested next.

No X-Plane window appears

A failure before any window appears usually points to the executable, permissions, security software or graphics-device initialisation rather than scenery.

If no new Log.txt is created, X-Plane probably failed before its normal logging started. Repair the installation, check whether security software quarantined a file, review operating-system permission prompts and try launching without overlays or injectors. A short log ending around Vulkan, Metal, an adapter or renderer initialisation leads to the GPU sequence below.

It crashes during plug-in loading

A stop while loading plug-ins makes third-party code, a missing dependency or an incompatible native binary the leading suspect.

Look near the bottom for repeated references to a particular plug-in or its binary, but do not assume the last Loaded: line names the offender; that component may have finished successfully. Remove all user-installed plug-ins for the baseline test, not just the one that appears last. If the menu then opens but one custom aircraft crashes, also inspect that aircraft’s internal plug-in folder.

It crashes during scenery loading

A reproducible crash at one airport or region usually points to custom scenery, malformed mesh or orthophoto data, a missing library, storage trouble or memory pressure.

References to a named package, .dsf file, library object or scenery path in Log.txt identify what to remove first. Test the same aircraft and weather at a default airport. If X-Plane hangs at Reading new scenery files rather than closing, follow our checks for scenery indexing, package structure and storage delays.

It reaches the menu, then crashes or fails mid-flight

A crash after reaching the menu means basic application startup succeeded, so the loaded aircraft, location, weather, plug-ins and rendering load become more relevant.

Reproduce the flight with a Laminar aircraft and default airport. A failure tied to one aircraft suggests its scripts or plug-ins; one location suggests scenery. Random mid-flight failures across unrelated routes are more consistent with a global plug-in, GPU device loss, exhausted memory, overheating or unstable clocks. A crash only after a long flight can also expose accumulated RAM or VRAM pressure that a short startup test misses.

How do I fix an X-Plane 12 GPU crash?

An X-Plane 12 GPU crash is recognised by Vulkan, Metal, device-loss, graphics-memory or driver-initialisation messages near the end of Log.txt.

X-Plane uses Vulkan on Windows and Linux and Metal on macOS. Clues include VK_ERROR_DEVICE_LOST, VK_ERROR_OUT_OF_DEVICE_MEMORY, VK_ERROR_OUT_OF_HOST_MEMORY, a failed Vulkan-device or renderer initialisation, or Metal command-buffer and memory errors. Device loss does not by itself prove that the graphics card is defective; overlays, drivers, unstable tuning and VRAM pressure can produce the same result.

  1. Remove overlays and injectors. Disable recording overlays, performance overlays, reshading tools and monitoring utilities that hook into the graphics process. Test with them fully closed, not merely hidden.
  2. Reset hardware tuning. Return the GPU, CPU and system memory to standard clocks and voltage settings. Remove overclocks and undervolts, including factory profiles that have been manually altered.
  3. Install a stable graphics driver. Update the driver or perform a clean driver installation where the platform supports it. The newest release is not always the most reliable, so use a stable version if the crash began directly after a driver change. On macOS, Metal driver updates arrive with operating-system updates. Our flight-simulator graphics-driver procedure explains clean installation and rollback choices.
  4. Force the dedicated laptop GPU. Set X-Plane to use the high-performance discrete adapter in the operating system or GPU control panel. Confirm the selected adapter in Log.txt; do not assume the laptop chose it automatically.
  5. Reduce VRAM demand. Lower texture resolution, antialiasing and output resolution, then remove high-resolution scenery and complex aircraft from the test. Close other GPU-heavy applications. Out-of-host-memory errors also require checking system RAM and free virtual-memory or swap space.
  6. Retest a default flight. Use a Laminar aircraft, default scenery, standard weather and no third-party plug-ins. If this succeeds, restore one source of graphics load at a time.

For a repeatable VK_ERROR_DEVICE_LOST failure, use our more focused Vulkan device-loss isolation sequence. Keep the failed launch’s log because the same on-screen message can have different underlying causes.

Engine not starting in X-Plane 12

An aircraft engine that will not start is normally a fuel, electrical, ignition, control-binding or aircraft-specific procedure problem, not an X-Plane 12 application crash.

  1. Use the aircraft checklist. Piston, turboprop and jet engines have different start sequences. Custom aircraft may replace X-Plane’s standard commands with their own systems, so consult the supplied aircraft manual rather than applying a generic shortcut.
  2. Confirm usable fuel. Check actual fuel quantity, select a tank containing fuel and open any fuel selector or shut-off valve. A gauge showing fuel does not help if the selected tank is empty or the fuel cut-off remains closed.
  3. Set the mixture or condition lever. A piston aircraft normally needs an appropriate mixture and may require priming, while a turbine needs its condition or fuel-control lever moved at the correct point in the start. Check hardware axes because a noisy or reversed lever can continually command idle cut-off.
  4. Use the required fuel pumps. Turn on boost, auxiliary or electric pumps only as the checklist specifies. Some aircraft use them for priming; others require a particular pump arrangement throughout the start.
  5. Set electrical power and ignition. Turn on the battery and required master switches. Set piston magnetos to the prescribed position or enable turbine ignition and the start selector. The avionics master usually does not power the starter, and many piston procedures leave avionics off during cranking, so follow the aircraft’s checklist.
  6. Engage the starter correctly. Hold the starter command for the required period and watch for engine rotation. A key, switch or controller binding that immediately returns to another position can prevent engagement. Turbine starts also require the correct sequence between starter rotation, ignition and fuel introduction.
  7. Check interlocks and ground equipment. Some custom aircraft require the parking brake, external electrical power, an APU, pneumatic air or specific ground equipment before starting. These are aircraft dependencies, not universal X-Plane requirements; the aircraft manual should state them.
  8. Test a Laminar default aircraft. Reset active failures and try a Laminar-supplied aircraft using its checklist. If the default aircraft starts but the custom one does not, concentrate on that aircraft’s procedure, plug-ins and documentation. If neither starts, inspect control assignments, mixture or condition axes, fuel state and failure settings.
What the engine doesWhere to look first
Starter does not turn the engineBattery and master power, starter binding, start switch, interlock or required ground power
Engine turns but never firesFuel selection, mixture or condition lever, priming, pumps, magnetos or ignition
Engine fires and immediately stopsFuel cut-off, idle position, selected tank, pump state or a hardware axis overriding the cockpit lever
Only one custom aircraft will not startAircraft-specific checklist, custom systems, internal plug-in or unsupported shortcut command

Can an X-Plane 11 add-on cause an X-Plane 12 crash?

Yes. An aircraft, script or plug-in made for X-Plane 11 is not automatically compatible with X-Plane 12, even when it appears in the aircraft or plug-in menus.

Native plug-ins must also match the operating system and processor architecture. Older Mac plug-ins, for example, may lack a compatible Apple silicon binary, while an outdated plug-in on any platform may call simulator functions that changed. Confirm explicit X-Plane 12 support; successful file installation is not evidence of runtime compatibility.

Should I reinstall X-Plane 12 if it still crashes?

Repair the existing installation first because reinstalling into the same folder can leave the faulty plug-ins, scenery and preferences untouched.

If repair and every clean-start test fail, install or test an untouched copy in a separate folder where the installation channel permits it. Launch that copy before transferring Output/preferences, custom aircraft, scenery or plug-ins. If the clean copy also crashes, concentrate on drivers, permissions, available RAM and disk space, cooling and hardware stability.

Keep the complete Log.txt and any generated crash report. A useful report records the operating system, CPU, GPU, graphics driver, RAM, exact aircraft and airport, and the shortest sequence that reproduces the failure. Send an add-on-only fault to its developer; report a reproducible failure in an untouched simulator through X-Plane’s official bug-report channel.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members