Skip to content
X-Plane 6 min read

How do I troubleshoot common X-Plane 11 problems?

Adam McEnroe
In short

Fix common X-Plane 11 problems with a clear checklist for crashes, missing scenery, add-on faults, low FPS, controls and corrupt files.

To troubleshoot common X-Plane 11 problems, reproduce the fault with a default aircraft, default scenery and all third-party plug-ins disabled. Then inspect the fresh Log.txt, reset preferences if needed, verify the simulator files, and restore add-ons one at a time until the problem returns.

Where should I start troubleshooting X-Plane 11?

Start by reducing X-Plane 11 to the simplest configuration that can reproduce the fault. Changing several settings or add-ons together makes the cause harder to identify.

  1. Preserve the failed session's log. Copy Log.txt from the main X-Plane 11 folder before launching the simulator again, because every launch replaces it.
  2. Use a default aircraft and airport. Select a Laminar Research aircraft, default scenery, clear weather and no AI aircraft. This separates a simulator fault from an aircraft, scenery or weather problem.
  3. Disable third-party plug-ins. Move their folders out of Resources/plugins into a temporary folder outside X-Plane. Aircraft-specific plug-ins are excluded automatically when you test a default aircraft.
  4. Reset preferences safely. Back up Output/preferences, move it out of the simulator and let X-Plane create fresh preferences. This resets graphics, controls and other saved settings.
  5. Repair the installation. Use the X-Plane installer to scan a standalone installation, or verify the game files through Steam. Do not assume reinstalling add-ons will repair damaged simulator files.
  6. Restore items gradually. Add plug-ins, scenery and preferences back separately. If there are many plug-ins, test them in groups and then narrow down the failing group one item at a time.
SymptomBest first testLikely area
Crash before the main screenFresh preferences and no global plug-insPreferences, graphics driver or plug-in
Crash with one aircraftLoad a default aircraft at the same airportAircraft files, scripts or aircraft plug-in
Crash at one airportUse the same aircraft at a default airportCustom scenery, library or mesh
Failure only when onlineDisable weather and multiplayer clients separatelyNetwork plug-in, firewall or downloaded data
Stutter or crash after a long flightMonitor memory and temperatures with add-ons disabledVRAM pressure, system memory, heat or unstable overclock

How do I use X-Plane 11 Log.txt?

Log.txt is X-Plane 11's main diagnostic record and should be read immediately after the failure. It sits beside the X-Plane executable in the simulator's main folder.

Check the opening lines to confirm which X-Plane copy actually ran; keeping multiple installations is a common source of confusion. Then search for terms such as error, failed, missing and could not, along with the name of the aircraft, scenery package or plug-in involved.

The last line is not always the cause. It may simply identify the operation X-Plane was performing when another component failed, so inspect the preceding section for library errors, plug-in messages or repeated warnings.

Why does X-Plane 11 crash or freeze?

Repeatable X-Plane 11 crashes are most often traced to a third-party plug-in, aircraft, scenery package, damaged preference file or graphics problem. The point at which the crash occurs usually identifies which component to test first.

  • During start-up: remove global plug-ins and reset preferences.
  • While loading an aircraft: test a default aircraft, then check that add-on's plug-ins and dependencies.
  • While loading scenery: remove the packages used around that airport and inspect the log for missing objects or libraries.
  • After enabling Vulkan or Metal: test the OpenGL renderer once. If that works, remove overlays and overclocks, update the graphics driver and retest the accelerated renderer.
  • Only with online services: disable real-world weather, multiplayer and network clients individually rather than disconnecting everything at once.

Our step-by-step crash and loading diagnosis covers slow loading, memory pressure, corrupt caches and the point at which X-Plane stops responding.

How can I identify a faulty plug-in?

A faulty plug-in is confirmed when the problem disappears without it and returns when it is restored under the same test conditions. Moving only its visible menu entry or configuration file is not enough; remove the complete plug-in folder from Resources/plugins.

Old binaries, missing dependencies and installing into the wrong X-Plane copy are common causes. Our guide to correct X-Plane add-on paths and dependencies explains the folder structures that prevent many plug-in and aircraft failures.

Why is my X-Plane 11 scenery missing?

Missing X-Plane 11 scenery usually results from an extra folder level, incorrect scenery_packs.ini priority, an absent object library or a missing global scenery tile. Third-party scenery normally belongs in Custom Scenery, not inside Global Scenery.

Open the package folder and check that its scenery files are directly inside it rather than buried under a duplicate wrapper folder. Airports should normally load above overlays, orthophoto packages and base meshes; a mesh placed too high can suppress scenery beneath it.

Use our missing scenery and scenery_packs.ini checklist for package ordering and library errors. If entire regions show water, blank terrain or default terrain files are absent, follow the procedure for repairing X-Plane global scenery.

How do I fix low FPS and stuttering?

Fix low X-Plane 11 frame rates by determining whether the CPU or GPU has the longer frame time, then lowering settings that affect that component. Testing every slider at once can reduce image quality without addressing the actual bottleneck.

  • CPU-limited: reduce world objects, reflections, AI aircraft and CPU-heavy scripts or traffic plug-ins.
  • GPU-limited: reduce resolution, antialiasing and graphics effects.
  • VRAM-limited: lower texture quality and remove oversized aircraft or scenery textures. VRAM pressure often appears as severe stuttering when the view changes.
  • Sudden performance loss: test without weather add-ons, recording software, overlays and background programs, then check temperatures and available disk space.

Compare performance with the same aircraft, airport, weather and view after each change. A complex airliner at a detailed custom airport is not a useful baseline for diagnosing the simulator itself.

Why are my controls behaving incorrectly?

Incorrect control behaviour is usually caused by failed calibration, duplicate axis assignments or the wrong aircraft control profile. Calibrate every connected device, check each axis through its full travel and remove duplicate throttle, pitch, roll or yaw assignments.

Test with calm weather and a default aircraft before treating a pull to one side as a controller fault; propeller torque and crosswind can produce genuine yaw. If axes or commands still activate by themselves, create fresh preferences and rebuild the control profile rather than copying the suspect files back.

Should I reinstall X-Plane 11?

Reinstall X-Plane 11 only after a clean add-on test, fresh preferences and file verification have failed. Reinstalling into the same folder while retaining faulty plug-ins, scenery or preferences often reproduces the problem immediately.

Before reinstalling, back up downloaded aircraft, custom scenery and control profiles separately. Test the repaired or clean simulator before restoring anything, then return add-ons in small groups so the original fault cannot hide inside the rebuilt installation.

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