Why does X-Plane 11 crash on Steam, and how do I fix it?

X-Plane 11 on Steam usually crashes because a plugin, aircraft or scenery package is incompatible, its preferences or game files are damaged, or the graphics driver loses the Vulkan/OpenGL device. Save Log.txt, verify files in Steam, test without add-ons, reset preferences, then diagnose the GPU if a clean stock flight still fails.

Fix X-Plane 11 Steam crashes in the right order

The fastest reliable fix is to establish a clean X-Plane 11 baseline before changing drivers or reinstalling the simulator.

1. Preserve the evidence: before opening X-Plane again, copy Log.txt from the top-level X-Plane 11 folder to another location. The next launch overwrites it. If you cannot find the correct copy, use our guide to locate the Steam installation folder and its Log.txt file.
2. Deal with any Steam error first: if the message specifically says Steam subsystem failure, make sure the Steam client is running and signed in, then launch X-Plane 11 from the Steam Library rather than directly from its executable.
3. Verify the official files: open X-Plane 11’s Steam Properties, select Installed Files and run Verify integrity of game files. Steam will replace missing or modified files it owns, but it will not normally remove extra plugins or scenery you installed yourself.
4. Remove launch variables: use the standard Steam branch, clear custom launch options and temporarily disable the Steam Overlay, recording tools, frame-rate displays and graphics injectors. Restore each item if disabling it makes no difference.
5. Test without third-party content: move third-party folders out of Resources/plugins, disable add-on scripts and move third-party scenery out of Custom Scenery. Do not remove official scenery. Select a default aircraft rather than an aircraft with its own plugin.
6. Reset preferences safely: rename Output/preferences to preferences.backup. X-Plane will build a fresh folder, so expect to configure graphics, joystick assignments and other preferences again.
7. Run one controlled flight: load the default Cessna 172 at a stock airport with ordinary weather and modest graphics settings. If that works, restore one category of add-ons at a time until the fault returns.

A stock flight that works proves the core simulator and basic graphics path can run. A stock flight that still crashes shifts attention towards the graphics driver, Steam integration, operating-system permissions, security software or unstable hardware.

What does Steam subsystem failure mean in X-Plane 11?

Steam subsystem failure means X-Plane 11 could not initialise Steam’s client or ownership services; it is unrelated to an aircraft’s steam, pneumatic or environmental systems.

• Restart both programs: close X-Plane and exit Steam fully, reopen Steam, sign into the account that owns X-Plane 11 and test while online.
• Launch from the Library: starting the executable directly can expose a Steam initialisation problem that does not occur when Steam launches it.
• Match permissions: do not force X-Plane to run as administrator while Steam runs normally, or vice versa. Remove unnecessary compatibility settings from the executable.
• Verify files: this restores damaged or missing Steam integration components without disturbing most user-installed extras.
• Check security actions: review whether security software quarantined an official X-Plane or Steam component. Verify the installation after correcting the action, but do not whitelist an unknown third-party plugin merely to make the warning disappear.
• Reboot the computer: a stuck Steam process or pending client update can survive closing the visible window.

If other Steam games also fail to initialise their Steam services, the fault is probably in the Steam client or account session rather than X-Plane’s aircraft, scenery or preferences.

What does X-Plane 11 Log.txt reveal?

Log.txt records the most recent startup and flight session, and the lines near the end often identify the failing plugin, aircraft, scenery package or graphics subsystem.

Do not treat every warning as the cause. A missing scenery object may explain an incomplete airport without crashing the simulator. Give more weight to an explicitly named plugin, a fatal graphics message and errors written immediately before logging stops.

How do I find which X-Plane add-on is crashing?

The quickest method is to remove add-ons by category and restore half of the suspect group at a time.

• Start with global plugins in Resources/plugins, because they can affect every aircraft and location.
• Disable scripts loaded by plugin-based script engines; changing aircraft does not stop a global script.
• Use a default aircraft before investigating aircraft-specific plugins.
• If the crash occurs only in one area, disable that airport and its required third-party libraries before removing unrelated scenery.
• Restore half the suspect packages, test, then halve the failing group again. This is much faster than testing a large collection one item at a time.

Update or repair a supported aircraft rather than mixing files from different releases; our instructions explain how to repair compatible add-ons with SkunkCrafts Updater. Confirm that each plugin supports X-Plane 11, your operating system and the graphics API you selected.

A mistake we see constantly is copying an entire old Resources, Output or Custom Scenery folder into a repaired installation. That restores the original fault along with the add-ons. Bring back aircraft, plugins, scenery and preferences separately.

Is Vulkan causing an X-Plane GPU crash or graphic error?

A clean X-Plane 11 installation that works in OpenGL but crashes in Vulkan usually has a graphics-driver, VRAM, overlay or GPU-stability problem rather than damaged Steam files.

• Install an appropriate stable driver: use a driver intended for the active GPU and reboot after installation. On macOS, graphics drivers arrive through operating-system updates rather than separate driver packages.
• Return hardware to standard settings: remove manual CPU, GPU and memory overclocks or undervolts while testing.
• Disable injected software: turn off recording overlays, monitoring displays, post-processing injectors and similar tools.
• Reduce GPU demand: lower texture quality and anti-aliasing first if crashes occur after loading detailed aircraft or dense scenery.
• Rebuild generated shaders: with X-Plane closed, rename the generated Output/shadercache folder. X-Plane will recreate it on the next launch, which may take longer than usual.
• Test the other graphics API: OpenGL is a useful diagnostic fallback in X-Plane 11. Vulkan applies on supported Windows and Linux systems; macOS uses Metal instead.

A Vulkan device-loss message does not by itself prove that the graphics card is defective. If the whole computer restarts, freezes outside X-Plane or shows display corruption in other applications, investigate driver stability, temperatures, power delivery and hardware rather than repeatedly reinstalling the simulator.

I have Intel graphics — what should I do?

Having an Intel processor does not necessarily mean X-Plane is using Intel graphics; many systems pair an Intel CPU with a separate NVIDIA or AMD GPU.

Check the active GPU named near the beginning of Log.txt. Intel Arc is discrete graphics, while Intel UHD and Iris models are commonly integrated and use shared system memory. On a laptop with two GPUs, assign X-Plane to the high-performance GPU in the operating system’s graphics settings.

If Intel integrated graphics is the only option, install the appropriate driver, reduce textures and anti-aliasing, and test OpenGL. Older Intel graphics may lack the Vulkan features or resources X-Plane needs. Shared system memory should not be treated as equivalent to dedicated VRAM, particularly with detailed scenery and aircraft.

What does “an incompatible version of this game is installed on your device — uninstall the Steam version” mean?

This message normally indicates an installation-channel conflict, such as a standalone installer or updater being pointed at a Steam-managed copy of X-Plane 11; it is not a GPU crash.

“Uninstall the Steam version” means uninstall the X-Plane 11 application, not the entire Steam client. Our installer-channel, permissions and repair checks cover problems encountered after choosing the correct edition.

If the exact message came from another game or launcher, X-Plane folder changes will not fix it. Identify which application produced the warning before uninstalling anything.

What does “script editor read only due to an unstable connection” mean?

A script editor becoming read-only because of an unstable connection is a warning from an external editor or add-on service, not a standard X-Plane 11 or Steam crash message.

The editor has usually disabled saving to avoid conflicts while its connection is unreliable. Copy any unsaved text locally if possible, restore the connection or session, then save through the editor’s normal process. X-Plane’s Log.txt is a local file and should not become read-only for this reason.

If the affected script belongs to an X-Plane plugin, disable that script or its script-engine plugin during the clean test. Do not edit several scripts while diagnosing a crash, because that changes more than one variable at once.

When should I reinstall X-Plane 11 from Steam?

Reinstall only after Steam verification, clean preferences and an add-on-free stock flight have all failed.

A normal Steam uninstall may leave files Steam did not install, including plugins, scripts, scenery, preferences and generated caches. Back up only material you need, uninstall X-Plane 11, then rename or remove the remaining installation folder before downloading a fresh copy. Follow our procedure to remove leftover X-Plane files that Steam does not track.

Launch the untouched simulator with a default aircraft before restoring anything. If that fresh copy still crashes, the evidence points away from add-ons and damaged game files and towards the graphics driver, security software, storage, permissions or system stability.

Is “-4 + x = -11” an X-Plane error?

-4 + x = -11 is an algebra equation, not an X-Plane 11, Steam or GPU error code. Add 4 to both sides and the answer is x = -7. If the expression appeared inside an add-on script, preserve the surrounding error message because the script language and line number determine whether it is valid there.

What should I record if X-Plane simply did not run?

Record the exact message, the point at which startup stopped and a copy of Log.txt; a vague report cannot distinguish a Steam failure from a graphics or add-on crash.

Short searches such as não rodou (“it did not run”), bune şimdi or bu ne şimdi? (“what is this now?”), and что делать (“what should I do?”) all need the same extra evidence:

• the exact on-screen error, copied without paraphrasing;
• whether X-Plane reached the menu, aircraft-loading screen or cockpit;
• the active GPU named in Log.txt rather than only “I have Intel”;
• whether Vulkan, Metal or OpenGL was selected;
• the aircraft and airport used, and whether they were stock or third-party;
• whether Steam launched X-Plane and updated Log.txt at all.

If no new log is created, concentrate on Steam initialisation, permissions and security software. If the log names a component, isolate that component. If the entire computer resets, treat it as a driver, power, thermal or hardware-stability problem rather than an ordinary X-Plane crash.