How do I fix Vulkan device loss in X-Plane 12?
A Vulkan device loss in X-Plane 12 usually means the graphics driver reset or the GPU stopped responding. Reboot, return the GPU to stock settings, install a stable driver, disable third-party plug-ins, lower VRAM-heavy graphics options, and test with default aircraft and scenery. Then inspect Log.txt for the failing component.
What does the Vulkan device loss error mean?
The message VK_ERROR_DEVICE_LOST means X-Plane lost access to the graphics device while rendering. It does not automatically mean the graphics card is faulty: driver crashes, unstable overclocks, excessive VRAM use, overlays and add-ons can all produce the same result.
X-Plane 12 uses Vulkan on Windows and Linux; there is no OpenGL fallback comparable to X-Plane 11. On macOS, X-Plane uses Metal instead, so a literal Vulkan error points to a Windows or Linux installation. The GPU and its driver must support Vulkan 1.3; our X-Plane 12 hardware and GPU guidance explains the relevant compatibility and VRAM considerations.
How do I fix X-Plane 12 Vulkan device loss?
Work through these checks in order and test after each major change, rather than changing everything at once.
- Preserve the log before relaunching. Copy
Log.txtfrom the mainX-Plane 12folder immediately after the crash. X-Plane replaces this file on the next launch. Near the end, look forVK_ERROR_DEVICE_LOST, memory warnings, the last aircraft or scenery loaded, and plug-in messages. The final line is a clue, not proof that the named component caused the crash. - Establish a clean baseline. Load a default aircraft at an airport unaffected by custom scenery, with simple weather and no external utilities. Temporarily move only third-party plug-in folders out of
Resources/plugins; do not remove files supplied with X-Plane. A default aircraft also excludes plug-ins embedded inside an add-on aircraft. Our clean-start and crash-diagnosis procedure covers this isolation process in more detail. - Repair or change the graphics driver. If the failures started immediately after a driver update, return to the previous stable release. Otherwise, install a suitable driver from the GPU manufacturer and use its clean-install option when available. A driver offered automatically by the operating system may be older or incomplete. On Linux, avoid mixing incompatible proprietary and Mesa driver components.
- Remove instability and injected overlays. Return GPU core and memory clocks to stock, remove undervolting, and temporarily disable CPU or RAM overclocks, including XMP or EXPO profiles. Close recording overlays, frame-rate limiters, graphics injectors and hardware-monitoring tools that hook into Vulkan. Stability in another game does not prove that an overclock is stable under X-Plane's workload.
- Reduce GPU and VRAM demand. Begin by lowering texture resolution, anti-aliasing and render resolution, especially at 4K or when using detailed aircraft and scenery. Reduce shadows, clouds and scenery density if the crash occurs at complex airports or in heavy weather. Restart X-Plane after changing texture-related options, then increase settings one at a time. Our GPU, VRAM and system-load tuning advice provides a practical order for reducing demand.
- Reset preferences and the shader cache. With X-Plane closed, rename
Output/preferencesto keep a backup, then let the simulator create fresh preferences. This resets graphics, controls and views, so do not delete the backup. IfOutput/shadercacheexists, rename that separately and allow X-Plane to rebuild it. Test between these changes so you know which one mattered. - Verify the installation. Use the X-Plane installer to update or repair a direct installation, or the platform's file-verification function for a managed installation. Verification replaces damaged core files but normally does not remove problematic third-party content. See our installation and file-repair instructions for the relevant method.
- Check the wider system. On a laptop, force X-Plane to use the dedicated GPU and connect mains power. Ensure there is adequate free disk space, leave virtual memory system-managed, and check GPU temperature and power stability. A black screen, driver-reset notification or similar crashes in other 3D applications points beyond X-Plane to the driver, power supply or graphics hardware.
What does the timing of the crash reveal?
Where and when the error appears usually identifies the most productive next test.
| Failure pattern | Likely area | Best next test |
|---|---|---|
| Crash during graphics initialisation | Driver, unsupported GPU, overlay or corrupted preferences | Install a clean driver, disable overlays and reset preferences |
| Crash after several minutes | Heat, unstable clocks, power or rising memory use | Use stock clocks, monitor temperatures and lower GPU load |
| Crash at one airport or viewpoint | Custom scenery, texture load or a scenery library | Test the same location with custom scenery disabled |
| Crash only with one aircraft | Aircraft plug-in, avionics or high-resolution textures | Repeat the flight with a default aircraft |
| Crash after a driver update | Driver regression or damaged installation | Clean-install or roll back the graphics driver |
How can I identify the faulty plug-in or scenery package?
If the clean default test works, restore add-ons gradually until the failure returns. Adding half the disabled plug-ins at a time is faster than testing a large collection individually; once the failing half is known, narrow it down one package at a time.
Repeat the same aircraft, airport, weather and camera position for every test. Aircraft-specific plug-ins live inside their aircraft packages and will not be disabled by cleaning only Resources/plugins. Likewise, scenery trouble may appear only when approaching a particular tile or airport.
Should I reinstall X-Plane 12?
A full reinstall is rarely the first or best fix for Vulkan device loss. File verification, fresh preferences and a clean add-on test provide the same diagnostic value with less disruption.
Reinstall only if verification repeatedly finds damaged files or a completely clean installation still fails. Installing over the existing folder can preserve the faulty plug-in, preference or scenery package, so it is not a meaningful clean test.
What should I do if the error still occurs?
A reproducible device loss with default aircraft, default scenery, stock clocks and fresh preferences needs evidence-based reporting. Preserve Log.txt, record the exact aircraft, airport, weather and graphics settings, note the GPU and driver version, and submit the simulator's crash report when offered.
Avoid registry tweaks that merely extend the graphics-driver timeout. They can turn a recoverable driver reset into a longer system freeze without fixing the underlying Vulkan hang.