X-Plane 11 crashing on Steam? Use Log.txt, verify files, isolate plugins and scenery, reset preferences, and diagnose Vulkan or driver faults.
X-Plane 11 on Steam usually crashes because a plugin, aircraft or scenery package is incompatible, preferences or game files are damaged, or the graphics driver loses the Vulkan, Metal or OpenGL device. Save Log.txt first, verify Steam files, test a stock flight without add-ons, reset preferences, then investigate the GPU.
Fix X-Plane 11 Steam crashes in this order
Use one controlled sequence so that each test either eliminates a cause or identifies it.
- Save the crash log before relaunching: copy
Log.txtfrom the main X-Plane 11 directory to another location. X-Plane replaces this log during the next launch. If you cannot find it, follow our instructions for finding the Steam installation folder and Log.txt. - Restart Steam and the computer: exit both X-Plane and Steam fully, reboot, sign into the Steam account that owns X-Plane 11, and launch it from the Steam Library. This clears stuck client processes and pending updates.
- Verify the official files: open X-Plane 11 in the Steam Library, select Properties, then Installed Files, and run Verify integrity of game files. Steam replaces missing or modified files it manages, but usually leaves untracked plugins, scenery and scripts in place.
- Remove launch-time interference: clear custom Steam launch options and temporarily disable the Steam Overlay, recording tools, frame-rate displays, post-processing injectors and hardware monitoring overlays. Remove forced administrator and compatibility settings so Steam and X-Plane run at the same permission level.
- Test without third-party content: move third-party plugins out of
Resources/plugins, disable scripts loaded by scripting plugins, and move third-party packages out ofCustom Scenery. Leave official scenery and built-in plugins alone. Select a default aircraft. - Reset preferences safely: rename
Output/preferencestopreferences.backup. X-Plane will create clean preferences at startup, so graphics options, controller assignments and other settings will need configuring again. - Run a repeatable stock flight: use the default Cessna 172 at a stock airport with ordinary weather and moderate graphics settings. Avoid changing several settings between tests.
- Restore content gradually: if the stock flight works, restore one category at a time. For a large plugin or scenery collection, restore half the suspect group, test, and keep halving the group that causes the crash.
A successful stock flight shows that the core simulator and basic graphics path can run. If the clean test still crashes, concentrate on Steam integration, the graphics driver, security software, permissions or system stability rather than reinstalling every add-on.
Did Steam crash on startup, or did X-Plane 11 crash?
If Steam closes or will not open before X-Plane starts, Steam is crashing on startup; if Steam remains open while the simulator closes, the fault is usually inside X-Plane or one of its add-ons.
| What happens | Likely fault | Next action |
|---|---|---|
| The Steam client closes, hangs or never opens | Steam client files, cache, GPU acceleration or security software | Repair Steam before changing X-Plane |
| Steam stays open but X-Plane closes | X-Plane plugin, aircraft, scenery, preferences or graphics failure | Inspect Log.txt and run the stock test |
X-Plane reports Steam subsystem failure | X-Plane could not initialise Steam ownership services | Restart Steam, sign in and launch through the Library |
| The entire computer freezes or restarts | Driver, temperature, power, memory or hardware instability | Return hardware to standard settings and diagnose the system |
When Steam itself is crashing, reinstalling X-Plane will not repair the client. Our separate Steam startup and client-crash checks cover damaged client files, cache problems, overlays and GPU acceleration.
What does Steam subsystem failure mean?
Steam subsystem failure means X-Plane 11 could not communicate with the running Steam client or confirm the installation correctly.
- Exit Steam completely, reboot, then sign into the account that owns X-Plane 11.
- Launch the simulator from the Steam Library rather than opening its executable directly.
- Test online once, even if you normally use Steam's offline mode.
- Remove forced administrator or compatibility settings from both applications.
- Verify X-Plane's files and check whether security software quarantined an official component.
Do not whitelist an unknown plugin merely to suppress a security warning. Remove the plugin and confirm its source and compatibility first.
What does X-Plane 11 Log.txt reveal after a crash?
Log.txt records the most recent startup and flight session, and its final section can identify the aircraft, plugin, scenery package or graphics subsystem involved.
| Evidence | Probable cause | Best test |
|---|---|---|
A plugin or .xpl module is named immediately before the crash | Plugin failure or incompatibility | Remove that plugin and repeat the same flight |
| Only one aircraft crashes | Aircraft plugin, sound bank, model or configuration | Load a default aircraft at the same airport |
| Only one airport or region crashes | Airport, scenery library, orthophoto or mesh conflict | Disable the affected third-party scenery |
| Vulkan device loss, allocation or memory errors appear | Driver reset, VRAM pressure, overlay or unstable GPU settings | Reduce GPU demand and test another graphics API |
| The log ends abruptly without identifying a component | Native plugin, graphics driver or wider system failure | Test without add-ons, overlays, overclocks or undervolts |
| No new log is created | X-Plane did not start far enough to initialise logging | Check Steam, permissions and security software |
The last warning is not automatically the cause. Missing scenery objects may produce warnings without closing the simulator. Give more weight to a fatal graphics message, an explicit plugin-crash statement, or a component repeatedly named immediately before logging stops.
How do I find the add-on that crashed my game?
Remove third-party content by category, establish that stock X-Plane works, then restore the suspect group in batches.
- Start with global plugins in
Resources/plugins, because they load regardless of the selected aircraft or airport. - Disable scripts as well as plugin folders. Changing aircraft does not stop a global script from running.
- If only one aircraft fails, test a default aircraft before changing unrelated scenery.
- If only one location fails, disable its airport, required libraries, orthophotos and local mesh before removing global content.
- Check that every restored add-on supports X-Plane 11, your operating system and the selected graphics API.
A mistake we see constantly is copying an old Resources, Output or Custom Scenery folder wholesale into a repaired installation. That restores the original fault. Bring back plugins, aircraft, scenery and preferences separately.
Can a virtual airline client cause an X-Plane crash?
Yes. A virtual airline client can crash X-Plane if it loads an incompatible simulator plugin, script or data-connection module.
Disable both the X-Plane-side module and its companion client during the stock test. If X-Plane works without them, install a version explicitly compatible with X-Plane 11 and avoid combining duplicate tracking or data-export plugins. A disconnected virtual airline session should not normally crash an otherwise stock simulator.
Is Vulkan causing the X-Plane 11 crash?
A stock installation that works with OpenGL but crashes with Vulkan usually has a driver, VRAM, overlay or GPU-stability problem rather than damaged Steam files.
- Update or roll back the driver: use the correct package for the active GPU. If the crashes began immediately after a driver change, returning to the previous stable driver is a valid test. Our flight-simulator graphics driver guide explains the safe update process. On macOS, graphics drivers are supplied through operating-system updates.
- Remove unstable tuning: return the CPU, GPU and memory to standard clock and voltage settings while testing.
- Reduce VRAM demand: lower texture quality and anti-aliasing first, especially when the crash occurs after loading detailed aircraft or dense scenery.
- Disable injected software: turn off overlays, recording tools, monitoring displays and post-processing injectors.
- Rebuild generated shaders: close X-Plane and rename
Output/shadercache. The simulator will recreate it at the next launch. - Test another graphics API: OpenGL is a useful diagnostic fallback in X-Plane 11. Vulkan applies to supported Windows and Linux systems, while macOS uses Metal where supported.
A Vulkan device-loss message does not prove that the graphics card is defective. If other applications also show corruption, the computer restarts, or the display driver repeatedly resets, investigate temperatures, power delivery, memory and hardware stability.
What should I do if X-Plane uses Intel graphics?
First confirm the active graphics device near the beginning of Log.txt, because an Intel processor may be paired with a separate NVIDIA or AMD GPU.
On a laptop with two GPUs, assign X-Plane to the high-performance GPU through the operating system's graphics settings. If integrated Intel graphics is the only option, install the appropriate driver, lower textures and anti-aliasing, and test OpenGL. Shared system memory is not equivalent to dedicated VRAM, particularly with detailed aircraft and scenery.
What if X-Plane 11 still crashes immediately or does not run?
The point at which X-Plane stops determines what to test next when the earlier fixes do not work.
| Failure point | Concentrate on |
|---|---|
No X-Plane window and no updated Log.txt | Steam initialisation, executable permissions, security quarantine or missing official files |
| Crash at the splash screen before the menu | Global plugins, preferences, graphics API and driver initialisation |
| Crash while loading an aircraft | Aircraft plugins, sounds, scripts, memory use and texture demand |
| Crash while loading one airport or area | Scenery packages, libraries, mesh conflicts and VRAM pressure |
| Crash after several minutes of flight | Plugin activity, driver resets, memory exhaustion, temperatures or unstable hardware tuning |
Record the exact on-screen message, where loading stopped, the aircraft and airport, the selected graphics API, and the active GPU named in Log.txt. If X-Plane simply closes, also preserve the operating system's crash report where available. A report that only says it crashed cannot distinguish a Steam failure from a plugin or graphics fault.
When should I reinstall X-Plane 11 from Steam?
Reinstall only after file verification, clean preferences and an add-on-free stock test have all failed.
A normal Steam uninstall may leave untracked plugins, scripts, scenery, generated caches and preferences behind. Back up only files you genuinely need, uninstall the simulator, then remove or rename the remaining X-Plane 11 directory by following our clean X-Plane uninstall procedure.
Launch the untouched installation with a default aircraft before restoring anything. If a clean copy still crashes, do not copy the old folders back: the remaining suspects are the graphics driver, security software, storage, permissions or system stability.