Skip to content

XoL: Running X-Plane on Linux

This documentation covers setup and optimization of X-Plane 12 (Laminar Research) under Linux. It is aimed at experienced Linux users — a working installation is assumed. The examples are based on Debian but transfer to other distributions with minor adjustments.

Where to Start

  • Why Linux? Introduction explains what makes X-Plane on Linux different.
  • New to X-Plane on Linux? Getting Started covers system requirements, installation, and first launch.
  • X-Plane already running? Performance explains the three load dimensions (CPU, I/O, network) before diving into System Tuning.

About This Documentation

The core focus is on Linux system tuning — kernel parameters, CPU governor, GPU drivers, display server selection, and filesystem optimization — complemented by performance analysis using both X-Plane's built-in tools and Linux monitoring utilities. Additional sections cover scenery management with orthophoto streaming, flight operations including ATC procedures, and a reference catalog of Linux-compatible addons and plugins. The guides are modular — individual topics can be implemented independently or combined as needed.

Contributing

This documentation is an open project. Improvements or additions can be contributed via GitHub:

  • Create issues for bugs or suggestions
  • Submit pull requests for changes
  • Share experiences in the discussions in the footer of this website (e.g., via the Discord link)

All Videos →

Recent Changes

2026-02-27

  • Swap & Memory Management, System Tuning, and Tuning Case Study revised: Updated zram recommendations — swappiness=180 + watermark_scale_factor=125 instead of watermark_boost_factor=15000, based on 14 measurement runs. Separate configuration blocks for zram and disk swap, new field notes on dirty ratio tuning and vfs_cache_pressure

2026-02-24

  • Tuning Case Study expanded: New Step 5 — Watermark optimization with measured results (97% IO latency reduction, 58% fewer render-thread reclaim events)
  • Swap & Memory Management corrected: watermark_boost_factor=15000 replaces previous recommendation of 0, based on measurement data

2026-02-22

  • New page Tuning Case Study — Five measured tuning steps from micro-stutters to stable frame times: memory pressure, IO latency, zram swap, swap readahead, and watermark tuning