Fix X-Plane 11 crashing on Steam by verifying files, isolating add-ons, resetting preferences and reading Log.txt to identify the cause.
X-Plane 11 on Steam usually keeps crashing because of a third-party plugin, aircraft or scenery package, damaged Steam files, corrupted preferences, or a graphics-driver/Vulkan problem. Verify the installation first, then test a clean add-on-free setup and use X-Plane’s Log.txt to identify the component that failed.
Steam crash checks in the right order
Work through these checks in order so that each test changes only one part of the simulator.
- Preserve the crash log: before launching X-Plane again, copy
Log.txtfrom the top-level X-Plane 11 folder to another location. X-Plane replaces it on the next start. - Verify the Steam installation: in the Steam Library, open X-Plane 11’s Properties, select Installed Files and run Verify integrity of game files. This repairs missing or modified official files.
- Remove Steam variables: leave the Betas setting on the standard branch, clear any launch options and temporarily disable the Steam Overlay. Re-enable the overlay if it makes no difference.
- Disable third-party content: move third-party folders out of
Resources/plugins, disable add-on scripts and remove third-party scenery fromCustom Scenery. Move files rather than deleting them. - Reset X-Plane’s preferences: rename
Output/preferencesto something such aspreferences.backup. X-Plane will create clean preferences, but graphics settings and control assignments will need configuring again. - Run a controlled test: load the default Cessna 172 at a stock airport with ordinary weather. If that works, test the aircraft, airport or plugin that was active when the crash occurred.
Steam verification does not normally remove extra files that Steam did not install. An incompatible plugin can therefore survive verification and even a normal uninstall. Our X-Plane add-on folder and Log.txt guide explains where aircraft, scenery, plugins and scripts are stored.
What does X-Plane 11 Log.txt reveal?
Log.txt records the simulator’s latest startup and flight session, and its final lines often identify the plugin, aircraft, scenery tile or graphics subsystem involved.
| Evidence or symptom | Likely cause | Best test |
|---|---|---|
The final lines name a plugin or .xpl module | Plugin failure or incompatibility | Remove that plugin and test again |
| Crash occurs only with one aircraft | Aircraft plugin, model or configuration | Load a default aircraft under identical conditions |
| Crash occurs only near one airport | Airport, scenery library or mesh conflict | Use a stock airport, then disable the affected scenery |
| Vulkan device loss or memory errors appear | Graphics driver, VRAM pressure or injected graphics software | Test OpenGL and lower texture demand |
| The log ends abruptly without naming a cause | Driver failure, native plugin crash or system instability | Test without add-ons, overlays or manual overclocks |
Not every warning is fatal. Missing scenery objects and library warnings may explain incomplete scenery without being the actual crash trigger. Give the most weight to an explicitly named plugin and to errors written immediately before the log stops.
How do I find which X-Plane add-on is crashing?
The quickest isolation method is to remove add-ons by category and then restore them in small batches.
- Start with global plugins in
Resources/plugins, because they can affect every aircraft and airport. - Check scripts loaded through plugin-based script engines; removing an aircraft does not disable a global script.
- Test a default aircraft before investigating aircraft-specific plugins.
- If the crash is tied to one location, remove that airport and its required scenery libraries before disabling unrelated packages.
- Restore half of the suspect add-ons at a time. Repeatedly halving the group finds the offender faster than testing a large collection individually.
A mistake we see constantly is copying an entire old Resources or Custom Scenery folder into a repaired installation. That immediately restores the fault. Reintroduce each category separately, checking that every plugin supports X-Plane 11, your operating system and the selected graphics API.
Is Vulkan causing X-Plane 11 to crash?
If X-Plane 11 works under OpenGL but crashes with Vulkan enabled, the likely problem is the graphics driver, VRAM usage, an overlay or an injected graphics modification rather than Steam itself.
- Install a stable graphics driver suitable for the GPU, then reboot before testing.
- Return manual CPU, GPU and memory overclocks or undervolts to standard settings.
- Disable recording overlays, frame-rate displays and graphics injectors while diagnosing the crash.
- Reduce texture quality if the log reports memory exhaustion or the crash happens after loading dense scenery.
- On a laptop, make sure the operating system assigns X-Plane to the dedicated GPU rather than the integrated graphics processor.
Switching to OpenGL is a useful diagnostic and a workable fallback, but it does not repair an unstable Vulkan driver. If both APIs crash in a clean setup, investigate preferences, system software and hardware stability instead.
When should I reinstall X-Plane 11 from Steam?
Reinstall only after verification, clean preferences and an add-on-free test have failed, because an ordinary Steam reinstall may leave the offending third-party files behind.
For a genuinely clean test, back up only material you need, uninstall X-Plane 11, rename or remove the remaining installation folder, and let Steam install a fresh copy. Our Steam installation walkthrough for X-Plane 11 covers the normal installation process. Launch the untouched simulator before restoring any aircraft, scenery, plugins or preferences.
If leftover files must be removed as well, follow our full-removal procedure for X-Plane installations. A clean copy that still crashes with default content points away from Steam files and towards the graphics driver, security software, operating-system permissions, unstable hardware or insufficient free storage.