Use our X-Plane 12 troubleshooting process to diagnose crashes, failed starts, plugins, scenery, controls, stutters and Vulkan errors.
Troubleshoot X-Plane 12 by first reproducing the fault with a default aircraft at a default airport, then inspect Log.txt immediately after closing the simulator. Temporarily remove third-party plugins and scenery, reset suspect preferences, repair the installation, and restore add-ons one at a time until the problem returns.
What should I do first when X-Plane 12 has a problem?
Start by separating a simulator-wide fault from an aircraft-, airport- or add-on-specific fault. Changing several things at once may hide the cause without proving which change fixed it.
- Preserve the evidence: close X-Plane and copy
Log.txtsomewhere safe before launching it again. The file is replaced on the next run. - Define a repeatable test: record the aircraft, airport, weather, flight phase and action that triggers the problem. Check whether it happens everywhere or only in one location or aircraft.
- Load a clean scenario: use a default Laminar Research aircraft at an airport covered by the standard scenery. Avoid saved situations because they can retain aircraft, weather and systems states that confuse the test.
- Remove third-party plugins: move their folders out of
Resources/pluginsto a temporary folder outside X-Plane. Do not remove built-in components. Moving a plugin is a stronger test than disabling it after its binary has already loaded. - Test fresh preferences: back up and rename
Output/preferences, then let X-Plane create a new preferences folder. This resets graphics, controls and other settings, so restore the backup if it makes no difference. - Repair the core installation: use the X-Plane installer or the platform's file-verification function. This replaces missing or modified simulator files without requiring an immediate full reinstall.
- Restore add-ons gradually: add plugins, aircraft and scenery back in small groups. If the fault returns, divide the last group and test again until one package is identified.
Keep related components together during testing. An aircraft may require its bundled plugin, while scenery may depend on a separate library; removing only half of such a package can create a new error unrelated to the original fault.
Where is X-Plane 12 Log.txt, and what does it show?
X-Plane 12 writes Log.txt in the main simulator folder beside the executable. Read it immediately after the failed session and work upwards from the final lines, but do not assume the last named add-on caused the crash.
Look for a repeated plugin or scenery path, a missing file or library, an aircraft loading failure, memory pressure, or a Vulkan device-loss message. Ordinary warnings can appear in otherwise successful sessions, so compare the failing log with one from a clean test rather than treating every warning as fatal.
If the simulator crashes before updating Log.txt, verify the installation and graphics driver first. A log whose modification time has not changed suggests that X-Plane failed before its normal logging process started.
Which fix matches the X-Plane 12 symptom?
The fastest fix depends on whether the problem follows the entire simulator, one add-on, one aircraft or one location.
| Symptom | Likely scope | Best first test |
|---|---|---|
| Fails before reaching the main menu | Plugin, preferences, graphics driver or damaged core file | Move third-party plugins, reset preferences and verify files |
| Only one aircraft fails | Aircraft package, bundled plugin or compatibility issue | Load a default aircraft in the same conditions |
| Only one airport or region fails | Custom scenery, missing library or package order | Remove the affected scenery and repeat the flight |
| Black plugin window or missing plugin menu | Incorrect installation, incompatible binary or graphics bridge issue | Check the plugin folder structure and X-Plane 12 compatibility |
| Low frame rate everywhere | Graphics settings, complex aircraft, plugins or hardware limit | Compare a default aircraft and reduce one setting at a time |
| Controls move by themselves | Duplicate assignments, calibration or axis noise | Disconnect extra devices and test a fresh control profile |
Crashes and failed starts
A crash that remains with a default aircraft, standard scenery and no third-party plugins points towards preferences, the graphics driver, the base installation or hardware stability. A crash that disappears under that baseline is almost always tied to an add-on or its interaction with another add-on.
Do not copy every add-on straight back after reinstalling; that simply recreates the same test environment. For persistent failures, follow our detailed crash diagnosis using Log.txt and controlled add-on isolation.
Missing or broken plugins
A plugin that does not appear is usually installed one folder too deep, built for an incompatible operating system or simulator version, or missing a required dependency. Aircraft-specific plugins may live inside the aircraft package rather than in the global Resources/plugins folder.
Blank windows and crashes on opening a plugin can also indicate graphics compatibility rather than a bad menu installation. Our plugin folder, dependency and compatibility checks cover these cases without requiring every plugin to be removed permanently.
Aircraft loading errors
If only one aircraft is affected, leave global preferences and scenery alone until the aircraft itself has been tested. Confirm that the package supports X-Plane 12, install a clean copy without overwriting the default aircraft, and retain any bundled folders in their supplied structure.
An older aircraft may load with visual or systems faults even when X-Plane accepts its aircraft file. Missing cockpit displays or non-functional systems often come from an incompatible aircraft plugin rather than the flight model itself.
Missing scenery and airport errors
Scenery that fails at one airport usually has a nested folder, absent library, incomplete multi-folder installation or incorrect scenery_packs.ini order. Test the same airport after moving only the suspect package outside Custom Scenery; do not delete the standard Global Airports content.
If the default airport returns, the base simulator is working. Use our scenery folder and priority troubleshooting to check package structure, libraries and ordering.
Low frame rate, stutters and Vulkan errors
Performance problems should be measured with the same aircraft, airport, weather and camera view after each change. Enable X-Plane's frame-rate data output: the larger CPU or GPU frame time identifies which side is limiting performance.
- GPU-limited: reduce resolution, antialiasing, shadows or other graphics-heavy effects. Lower texture quality if VRAM is exhausted or textures become blurred after loading complex scenery.
- CPU-limited: reduce object density, traffic and plugin workload, then compare a default aircraft against the complex aircraft that showed the problem.
- Intermittent stutters: test without streaming scenery, complex custom airports and background plugins. Shader rebuilding after a driver change can also make the first sessions less representative.
For device-loss messages, black rendering or driver-related crashes, use our Vulkan, VRAM and graphics-driver checks before changing unrelated scenery or control settings.
Unresponsive or erratic controls
Control faults usually come from calibration, a noisy axis or the same command being assigned to multiple devices. Disconnect all but the main controller, recalibrate it, check every connected device for duplicate pitch, roll, yaw, throttle and trim assignments, and confirm that the intended aircraft control profile is active.
If a fresh preferences folder fixes the problem, restore the old folder and rebuild only the affected control profile where practical. Replacing every setting is unnecessary when one device profile is corrupt.
When should I reinstall X-Plane 12?
Reinstall X-Plane 12 only when file verification cannot repair missing or damaged core files, or when a clean baseline still fails after preferences, drivers and add-ons have been ruled out. Back up aircraft, scenery, plugins, control profiles and licence information before removing anything.
A reinstall is not a reliable fix for an add-on conflict. Test the newly installed simulator before restoring user content, then return each add-on category gradually so the original problem cannot slip back unnoticed.