Gaming on Ubuntu: The Complete Guide to Proton, Drivers, and Native Play

Linux gaming has crossed a threshold that would have seemed implausible five years ago. According to data compiled by Boiling Steam from ProtonDB, close to 90% of Windows games on Steam now run on Linux via Proton, with the share of titles that will not launch at all -- the Borked category -- down to roughly 4% and still falling. The Steam Survey for December 2025 recorded Linux at 3.58% of active Steam users (a figure Valve revised upward from an initial 3.19% report), up from 2.29% the same month a year prior and less than 2% in December 2023. By March 2026, the Steam Hardware Survey placed Linux at 5.33% -- an all-time high for the platform.

Ubuntu sits at the center of this shift. It is the distribution against which many native Linux games are first tested, and it is the most common system reported in ProtonDB. If you have a desktop or laptop running Ubuntu 24.04 LTS and want to game on it -- seriously game on it, not just run a few lightweight indie titles -- this is the guide that tells you exactly what to do and why.

How Proton Works

Proton is a compatibility layer developed by Valve that ships inside the Steam client. It lets games built for Windows run on Linux by translating Windows system calls into ones the Linux kernel and graphics stack can understand. It is not an emulator -- no virtual Windows machine runs in the background. The game accesses your real GPU and RAM directly, which is why performance can approach and sometimes exceed native Windows numbers on the same hardware.

Canonical notes that Proton enables games to "fully leverage the benefits of your PC's hardware" rather than emulating Windows. (Canonical Ubuntu Blog) This is why performance under Proton can match or in some titles exceed native Windows benchmarks on identical hardware -- the game process runs on your real CPU and GPU with no virtualization layer in the call path.

Proton is built on top of Wine, a project that has been in active development for over 33 years. Valve adds its own components on top of Wine: DXVK translates Direct3D 8, 9, 10, and 11 calls to Vulkan; VKD3D-Proton handles Direct3D 12; and a set of runtime patches covers timing, controller input, and shader compilation. The result is what Valve calls Steam Play.

As of April 2026, the current stable release is Proton 10.0-4, released January 26, 2026 by Valve and CodeWeavers. According to Phoronix and the official GitHub changelog, this release enabled 19 previously Experimental-only games on the stable branch (including Metal Slug: Awakening, Summoners War: RUSH, Distant Worlds 2, and REACH), pulled in VKD3D-Proton 3.0b, Wine Mono 10.4.1, and SteamWorks SDK 1.63, and delivered a range of game-specific fixes including corrections for Far Cry 5, Assassin's Creed Shadows, DualSense haptic regressions, and video playback in multiple titles. A rolling Proton Experimental channel also exists for bleeding-edge support.

Installing Steam on Ubuntu

There are two supported installation paths: the Ubuntu multiverse repository and the official .deb from Valve. The multiverse package pulls in the 32-bit library dependencies automatically and integrates cleanly with apt for updates. The Valve installer is always the most current version but requires manual dependency resolution on minimal installs.

One important clarification: the steam-installer package from multiverse is a small bootstrapper, not the full Steam client. Its sole job is to run on first launch, pull the real Steam client binaries from Valve's servers, and install them under your home directory. This is why the apt download is only a few hundred kilobytes -- the actual client download (around 200MB or more) happens when you first launch Steam after installation. The advantage of this bootstrapper approach is that Steam updates itself independently of Ubuntu's package repositories, so you always get the latest client without waiting for an Ubuntu package update.

# Enable multiverse and update package index
$ sudo add-apt-repository multiverse
$ sudo apt update

# Install Steam (pulls in required i386 libraries automatically)
$ sudo apt install steam-installer

# Alternatively: download the .deb directly from Valve's official repository
$ wget https://repo.steampowered.com/steam/archive/precise/steam_latest.deb
$ sudo apt install ./steam_latest.deb

After installation, launch Steam, log into your account, and let the client update itself. On first run Steam downloads the Steam Linux Runtime -- a container environment that isolates game dependencies from your host system. The reason this exists is that many games were built against specific older versions of system libraries (glibc, libstdc++, SDL2, and others) that no longer ship in their expected versions on modern Ubuntu. Rather than requiring you to install dozens of legacy library packages system-wide -- which could break other software -- the Steam Runtime bundles those specific library versions inside a container that only the game process uses. This is why a game built in 2014 can still run reliably on Ubuntu 24.04 without touching your system libraries.

The Steam Linux Runtime comes in multiple "slots." Runtime 1.0 (Steam Runtime "scout") covers legacy games; Runtime 2.0 ("soldier") is the base for older Proton versions; Runtime 3.0 ("sniper") is what Proton 8.0 and later use. You do not need to manage these manually -- Steam selects the correct runtime per game automatically. However, if you delete a game and find that a runtime container still occupies gigabytes on disk, you can remove unused runtime slots in Steam's Download Cache settings. If a game fails to launch after a Steam update, verifying the game's files and checking that the Steam Linux Runtime containers are up to date (visible under Tools in your Steam library) fixes the problem in a large proportion of cases.

GPU Drivers: Getting This Right First

Your driver situation determines everything downstream. A misconfigured or outdated driver will cause game crashes, Vulkan failures, and frame drops that no amount of Proton tweaking can fix.

NVIDIA

NVIDIA's proprietary driver is required for any serious gaming. The open-source Nouveau driver does not implement the Vulkan features that DXVK and VKD3D need -- specifically, DXVK 2.7 requires VK_KHR_maintenance5 and other Vulkan 1.3 extensions that Nouveau does not expose. Nouveau is reverse-engineered without access to NVIDIA's firmware or hardware documentation, so its Vulkan implementation lags significantly behind the proprietary driver's feature set and will not reach parity in the foreseeable future. On Ubuntu 24.04 LTS, the recommended path is ubuntu-drivers:

# Let Ubuntu identify and install the recommended driver
$ sudo ubuntu-drivers autoinstall

# Or install the 580 series explicitly (580.142 is current recommended stable, March 2026)
$ sudo apt install nvidia-driver-580

# Reboot after installation -- the driver won't load until you do
$ sudo reboot

# Confirm the driver is loaded
$ nvidia-smi

Install Vulkan support alongside the driver. libvulkan1 is the Vulkan loader library that applications use to discover and interface with the Vulkan driver at runtime -- without it, Vulkan-using programs can't find the driver even if it is installed. vulkan-tools provides the vulkaninfo and vkcube diagnostics. Note: the package is named vulkan-tools on Ubuntu 22.04 and 24.04; on older Ubuntu releases it was named vulkan-utils.

AMD

AMD is the easier path on Ubuntu. The open-source AMDGPU kernel driver ships in the mainline kernel, and the Mesa graphics stack provides Vulkan support out of the box. Ubuntu 24.04 ships Mesa 24.x; for newer hardware or better performance on recent titles, the Kisak Mesa PPA provides builds that track Mesa releases closely:

# Install Mesa Vulkan drivers (standard Ubuntu repos)
$ sudo apt install mesa-vulkan-drivers vulkan-tools

# Optional: upgrade to the latest Mesa via Kisak PPA
# Note: this upgrades Mesa system-wide -- all GPU-accelerated apps use the new version
$ sudo add-apt-repository ppa:kisak/kisak-mesa
$ sudo apt update && sudo apt upgrade

# Verify Vulkan is functional -- you should see your GPU listed
$ vulkaninfo | grep "GPU id"

Intel

Intel Arc GPUs (Alchemist and Battlemage) use the open-source i915 and xe kernel drivers with the ANV Vulkan driver in Mesa. Support has improved substantially in the 2024--2026 Mesa development cycle. For Arc users on Ubuntu 24.04, the Kisak Mesa PPA is highly recommended -- the ANV driver shipped in Ubuntu's bundled Mesa 24.x is significantly older than what Arc cards benefit from. After installing updated Mesa, verify Vulkan support with vulkaninfo | grep "GPU id". MangoHud 0.8.0 added full Intel GPU temperature and load monitoring for both i915 and XE driver GPUs.

# Add the Kisak Mesa PPA for Intel Arc users (strongly recommended on 24.04)
$ sudo add-apt-repository ppa:kisak/kisak-mesa
$ sudo apt update && sudo apt upgrade

# Verify Intel Vulkan (ANV) is active
$ vulkaninfo | grep -E "GPU id|deviceName"

Proton GE: The Community Build

GE-Proton (formerly Proton-GE, maintained by the developer GloriousEggroll -- a Red Hat Software Maintenance Engineer who has maintained the project since well before Valve's own Proton matured) is a fork of Valve's Proton that pulls in patches faster than the official release cycle. It frequently includes codec fixes, media foundation patches, game-specific workarounds, and experimental DXVK and VKD3D builds before they reach the stable Valve version. The current series as of early 2026 is GE-Proton 10-x, tracking the Proton 10 base. It is not a replacement for Proton -- it is an alternative for specific titles that behave better under it. Both Heroic Games Launcher and Lutris have integrated umu-launcher as the backend when running GE-Proton outside of Steam, which eliminates the need for manual shell scripting.

The simplest way to install and manage GE-Proton versions is ProtonUp-Qt, a graphical tool available as a Flatpak:

# Install Flatpak if not already present
$ sudo apt install flatpak
$ flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

# Install ProtonUp-Qt
$ flatpak install flathub net.davidotek.pupgui2

# Launch it
$ flatpak run net.davidotek.pupgui2

Once inside ProtonUp-Qt, click "Add version," select the latest GE-Proton from the list, and click Install. Restart Steam afterward. To use GE-Proton for a specific game, right-click the game in your Steam library, open Properties, navigate to the Compatibility tab, check "Force the use of a specific Steam Play compatibility tool," and select the GE-Proton version from the dropdown.

Checking Compatibility Before You Buy

ProtonDB is a crowd-sourced database where players submit reports on how well individual games run under Proton. Ratings fall into five categories: Platinum (works perfectly out of the box), Gold (minor tweaks needed), Silver (playable with some issues), Bronze (significant problems), and Borked (will not launch). As of October 2025, the Boiling Steam analysis of ProtonDB data placed approximately 42% of new releases in the Platinum tier -- up from 29% the year before -- and the Borked category had fallen to around 3.8%.

Boiling Steam's October 2025 analysis of ProtonDB data found that "almost 90% of Windows games now run on Linux" -- with the Platinum tier (works out of the box) rising to roughly 42% of reported titles, up from 29% the prior year.

Before purchasing a title you intend to play on Ubuntu, search ProtonDB for it. Look at recent reports -- not just the aggregate medal -- because a game may have shipped a patch that broke Linux compatibility after a Gold rating was assigned. Pay attention to what GPU the top reporters are using. A Gold rating achieved entirely on NVIDIA hardware might mean a different experience on AMD, and vice versa.

GameMode and MangoHud: Performance That You Can Measure

Two tools from the open-source ecosystem are considered standard practice for Linux gaming: GameMode and MangoHud.

GameMode is a daemon developed by Feral Interactive -- the studio responsible for many native Linux game ports -- that tells the Linux kernel to prioritize a game process. When a game starts with GameMode active, it switches the CPU governor to performance, disables power-saving features that add latency, and boosts the I/O scheduler for the game's process tree. The result is lower frame-time spikes and, depending on how CPU-bound the title is, a 5--15% increase in average frame rate.

$ sudo apt install gamemode mangohud

# Verify GameMode daemon is running
$ systemctl --user status gamemoded

# Confirm gamemoderun is available
$ which gamemoderun

To enable both tools for a game in Steam, right-click the title, open Properties, and add the following to the Launch Options field:

MangoHud is an overlay for Vulkan and OpenGL (and by extension, DXVK and VKD3D) games that displays real-time metrics: frame rate, frame times, GPU load, CPU load, temperatures, and VRAM usage. It creates a visible feedback loop so you can see whether a driver update or launch option flag changed anything. The configuration file lives at ~/.config/MangoHud/MangoHud.conf and lets you customize precisely which metrics appear and where. MangoHud 0.8.2 is the current stable release; version 0.8.0 added full Intel GPU support (i915 and XE drivers) alongside multi-GPU display, which made the 0.8.x line the most complete version of the tool to date. MangoHud also powers the built-in performance overlay on the Steam Deck.

Non-Steam Games: Lutris and Heroic

Steam is not the only storefront, and some games do not exist on it at all. Lutris is an open-source game manager that handles Wine, Proton, and emulators under a single interface. It maintains community-maintained install scripts for thousands of titles, automating steps like downloading the game, configuring Wine, installing the required Visual C++ runtimes, and setting environment variables. For games from GOG, Epic Games Store, and Ubisoft Connect, Lutris is the standard tool.

Heroic Games Launcher is a focused alternative for Epic Games Store and GOG titles specifically. Its interface is cleaner and more similar to a conventional game launcher, which many players find more comfortable than Lutris's broader scope. Both tools support GE-Proton and allow per-game runner customization. Heroic has enabled umu-launcher by default when using GE-Proton, and Lutris uses umu as the default backend when GE-Proton (Latest) is selected -- this means non-Steam games now run in the same containerized Valve runtime environment that Steam itself uses, rather than through ad-hoc Wine configurations.

# Add the Lutris PPA for the most current version
$ sudo add-apt-repository ppa:lutris-team/lutris
$ sudo apt update
$ sudo apt install lutris

Heroic is available as a Flatpak, which keeps its dependencies isolated from your system and simplifies updates:

The Anti-Cheat Problem: Honest Assessment

This is the section where the honest answer is less comfortable. Anti-cheat software is the primary reason some games still do not run on Ubuntu, and it is important to understand why, because the technical reality is different from the policy reality.

Both Easy Anti-Cheat (EAC) and BattlEye have officially added support for Proton. Enabling that support is a simple configuration switch that game developers flip inside their anti-cheat SDK setup. The barrier is therefore not technical -- it is a business decision by the game's developer. EAC, which is owned by Epic Games, powers titles like Apex Legends, Fortnite, PUBG, and Rust, among many others. BattlEye is used by titles including Rainbow Six Siege and DayZ. Whether these games work on Linux through Proton depends entirely on whether the specific game's developers have opted into the Linux-compatible mode of those anti-cheat systems.

Grand Theft Auto V on Linux is a concrete example of how this plays out: Rockstar did not enable the Linux-compatible path for its anti-cheat configuration, which is why GTA V does not function under Proton despite the technical support existing at the anti-cheat SDK level. The block is a policy decision, not a technical limitation of Proton itself.

There are also kernel-level anti-cheat systems -- most notably Riot Games' Vanguard -- that require Windows kernel access and have no path to Linux compatibility regardless of developer intent. These represent a hard wall. Before committing to Ubuntu as your primary gaming OS, check GamingOnLinux's anti-cheat compatibility tracker at gamingonlinux.com/anticheat for the current status of any multiplayer title you care about.

Security Considerations for Linux Gamers

Linux has a well-earned reputation for security, but that reputation requires qualification for desktop gamers. The platform is not immune to threats, and the gaming context introduces several specific attack surfaces that are worth understanding clearly rather than dismissing.

The Proton and Wine Attack Surface

A persistent misconception is that running Windows games through Proton provides a security sandbox. It does not. Wine -- which Proton is built on -- explicitly states in its own FAQ that it is malware-compatible. The Wine prefix system provides file-system isolation in the sense that each game gets its own virtual C: drive, but the process running inside Wine has the same filesystem permissions as the user who launched it. A malicious Windows executable running through Proton can read, write, and delete files anywhere your user account has access -- including your home directory, browser credential stores, and SSH keys. Proton does not intercept or inspect the system calls a Windows binary makes; it translates them and passes them through.

The Flatpak installation of Steam adds a layer of meaningful restriction here. The Flatpak version runs inside a bubblewrap container that limits filesystem access by default, preventing the game process from reaching directories outside the declared sandbox without explicit Flatseal permissions. The .deb Steam installation does not provide this containment. This is one concrete case where the Flatpak path offers a genuine security advantage over the .deb, at the cost of the additional configuration overhead described in the installation section.

The FBI Steam Malware Investigation

In March 2026, the FBI's Seattle Division announced an active investigation into malware-laden games distributed through Steam between May 2024 and January 2026. The games identified in the investigation include BlockBlasters, Chemia, Dashverse (also known as DashFPS), Lampy, Lunara, PirateFi, and Tokenova. The attack pattern in several of these titles involved publishing a functional game that passed Steam's initial vetting, then delivering malware via a subsequent update -- a technique that bypasses platform checks that only run on initial submission.

The malware families deployed across these titles included Vidar (a Malware-as-a-Service infostealer that exfiltrates browser credentials, authentication cookies, and cryptocurrency wallet data), HijackLoader (a loader that establishes persistence and drops additional payloads), and Fickle Stealer. One of the most documented cases involved BlockBlasters, where a crypto-drainer was added after initial release. A streamer who downloaded and ran the game during a charity livestream lost over $32,000 from a cryptocurrency wallet. Blockchain investigators later estimated total losses from that title at approximately $150,000.

The Steam Workshop is a related vector. In February 2026, the People Playground developer temporarily shut down its Workshop after a mod called "FPS++" was found to contain worm malware. Workshop content for games running through Proton can execute code with the same user-level permissions as the game process itself. The People Playground incident appeared to primarily affect Windows users; whether the worm executed on Linux via Proton was not conclusively determined, but the principle applies -- Workshop content is executable code and should be treated accordingly.

If you installed any of the named titles during the relevant period, the FBI is actively seeking victim reports at ic3.gov and via a dedicated reporting form at forms.fbi.gov/victims/Steam_Malware.

Steam Account Security

Steam Guard is Valve's two-factor authentication system. Two modes exist: email verification (a code sent to your registered email when logging in from a new device) and the Steam Guard Mobile Authenticator (a TOTP-style code generated in the Steam mobile app every 30 seconds). The Mobile Authenticator is the recommended option. It is required for trading on the Community Market and provides meaningful protection against credential theft -- even if an attacker captures your password, they cannot access the account without the time-limited code from your device.

Note one important nuance: Vidar and similar infostealers target authentication cookies, not passwords. A stolen session cookie grants access to an already-authenticated session, which means Steam Guard does not protect an active session that was captured while it was valid. The protection Steam Guard provides is against new logins with stolen credentials, not against session hijacking of an existing active login. Logging out of Steam when not actively using it -- and using the Flatpak isolation to limit what a game process can read -- reduces the value of any credentials that might be exfiltrated.

Enable Steam Guard via Steam > Settings > Security > Manage Steam Guard. Use the Mobile Authenticator, not email-only verification. Store the recovery code in a secure location separate from the device.

Mod Security and Third-Party Sources

Game mods downloaded from sources outside the Steam Workshop -- Nexus Mods, GitHub repositories, Discord servers, or direct links from game communities -- are executable code or data files that run in the context of the game process. On Linux, mods that ship as native Linux libraries (.so files) or as scripts executed by the game engine have full user-level access. Mods for games running through Proton that ship as Windows DLLs are loaded by Wine and run with the same permissions as the game itself. The risk profile is identical to running an untrusted executable. This does not mean modding is unsafe, but it means the source matters: prefer mods from established authors with public code history, avoid mods that require you to disable antivirus or place files in unusual system locations, and treat direct messages from strangers linking to "must-have" mods as the social engineering vector they frequently are.

Performance Tuning: Environment Variables That Matter

Steam's launch options accept environment variables that Proton passes to the game process. A small set of these variables covers the overwhelming majority of real-world tuning scenarios:

# Order matters: env vars first, then wrapper executables, then %command%
# gamemoderun and mangohud are executables that exec the next argument as a child process.
# Any env var placed after them in the string is only exported into the current shell
# context and may not be inherited reliably by the child. Keep env vars to the left.

# Standard setup: env vars → wrappers → %command%
PROTON_LOG=1 gamemoderun mangohud %command%

# PROTON_LOG=1 -- writes ~/proton_<appid>.log. Use for diagnostics; remove during normal play.
# The log can grow to several hundred MB in a single session -- clean it up after use.

# DXVK_ASYNC=1 -- removed from DXVK mainline; no longer valid in standard Proton 9/10
# Only applies if using a specific GE-Proton build that re-includes the async patch.

# For NVIDIA hybrid laptops (dGPU + iGPU) -- forces the discrete GPU
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia gamemoderun %command%

# AMD Anti-Lag (RDNA2+ only) -- reduces input latency; requires Mesa 25.x or later
ENABLE_LAYER_MESA_ANTI_LAG=1 gamemoderun %command%

The PROTON_LOG=1 variable is the most underused diagnostic tool in Linux gaming. When a game crashes immediately on launch with no visible error, the log file will contain the Wine and DXVK error messages that explain what failed. Look for lines beginning with err: or fixme: that correspond to the point the crash occurred.

Controller Support: How the Input Stack Works

Controller support on Ubuntu is handled by a layered stack, and understanding which layer is responsible for a problem is the difference between a five-minute fix and an hour of confusion. From bottom to top: the Linux kernel exposes the physical controller as a /dev/input/event* device; SDL2 normalizes that raw device into a standardized gamepad layout; Steam Input sits above both and can remap, emulate, and override input for any game launched through Steam.

For games running under Proton, Steam Input is particularly important because Windows games are written against Microsoft's XInput API -- which Linux does not implement natively. Steam Input translates your controller into what appears to the game as an Xbox 360 or Xbox One controller, and Proton handles the XInput translation internally. For the vast majority of Proton games with a controller, you do not need to do anything beyond plugging in the controller before launching Steam. Xbox controllers (including the newer Xbox Series models), PlayStation DualSense and DualShock 4 controllers, and many third-party XInput-compatible pads work without additional configuration because their kernel drivers (xpad for Xbox, hid-playstation for DualSense) are included in the mainline kernel and Ubuntu ships with them.

Bluetooth controllers are supported by the same kernel drivers. DualSense over Bluetooth is fully supported, including haptic feedback and adaptive triggers in games that specifically implement them through the hid-playstation driver or Steam's own DualSense support layer. Xbox controllers over Bluetooth require the xone driver (for the newer Xbox One/Series USB receiver) which is not in the Ubuntu mainline kernel as of April 2026 -- it must be installed from the medusalix/xone GitHub repository. The older Xbox 360 wireless receiver uses the xpad driver which is already present.

# List all recognized input devices -- your controller should appear here
$ cat /proc/bus/input/devices | grep -A 5 -i -E "gamepad|joystick|controller"

# Check which kernel driver is handling your controller
$ ls /sys/bus/hid/drivers/ | grep -i -E "xbox|xpad|playstation|sony|hid"

# Test axes and buttons with evtest (install if not present)
$ sudo apt install evtest
$ sudo evtest  # select your controller device node from the list

# If a game won't detect the controller, add your user to the input group
# (rarely needed on Ubuntu 24.04, but resolves some permission issues)
$ sudo usermod -aG input $USER
$ newgrp input  # apply without logging out

Wayland vs. X11 for Gaming

Ubuntu 24.04 LTS defaults to Wayland with GNOME. For gaming, this matters because MangoHud, screen capture, and some older games were historically designed around X11 assumptions. The situation has improved significantly as of early 2026: MangoHud works under Wayland for Vulkan games, OBS Studio captures via PipeWire, and Proton games generally run without issues under GNOME's XWayland layer.

The key thing to understand is that most Proton games do not run as native Wayland clients even when your desktop is on Wayland. They run through XWayland -- an X11 compatibility server that GNOME starts automatically. XWayland is a full X11 server running alongside the Wayland compositor, and Proton games interact with it as though they were on a conventional X11 desktop. This is transparent to you and to the game. The practical distinction only surfaces in three areas: frame pacing, fullscreen exclusive mode behavior, and overlay injection.

If you encounter a specific game that refuses to render correctly under Wayland, or an overlay that will not appear, logging into an X11 session is still available at the Ubuntu login screen. Click your username, then the gear icon at the bottom right, and select "Ubuntu on Xorg." This is a per-session choice and does not change your default permanently.

Diagnosing Proton Failures: Reading the Log

When a game crashes immediately on launch with no visible error, PROTON_LOG=1 is where you start. Add it to the game's Steam launch options, reproduce the crash, then open the log file at ~/proton_<appid>.log. Most useful crashes leave a trace in the last 100 lines.

# Find the log file for a specific game (replace APPID with the number from the store URL)
$ ls ~/proton_*.log

# Show only hard errors from the log
$ grep "^err:" ~/proton_APPID.log | tail -40

# Show the last 80 lines (where most crashes are recorded)
$ tail -80 ~/proton_APPID.log

# Search for a specific DLL failure
$ grep -i "failed to initialize\|vkCreate\|NtCreateFile" ~/proton_APPID.log

# Check DXVK's own output for GPU/driver errors (separate from the Proton log)
# DXVK writes to the game directory -- look for dxgi.log or d3d11.log
$ find ~/.local/share/Steam/steamapps/common -name "dxgi.log" -o -name "d3d11.log" 2>/dev/null

The Practical ProtonDB Workflow

The workflow that experienced Linux gamers follow before starting a new title is straightforward and worth making a habit:

First, look up the game on ProtonDB. Read the three or four most recent Gold or Platinum reports that match your GPU vendor. Note any launch options or specific Proton version those reporters used. Second, if the game has an EAC or BattlEye dependency, cross-reference the GamingOnLinux anti-cheat tracker to confirm Linux support is enabled for that specific title. Third, install the game through Steam and launch it with PROTON_LOG=1 %command% on the first run -- not to read the log immediately, but to have it available if the launch fails. Fourth, if the launch succeeds, remove PROTON_LOG=1 and add gamemoderun mangohud %command% to measure baseline performance. Finally, after a few sessions, submit your own report to ProtonDB. The database is only as useful as the community that maintains it.

Where Ubuntu Gaming Stands in 2026

The numbers from Phoronix, GamingOnLinux, and Valve's own survey data tell a consistent story: Linux gaming has grown substantially, and Ubuntu remains the most tested desktop distribution in the ecosystem. Linux closed 2025 at approximately 3.5% of Steam's active user base, dipped to 2.23% in February 2026, then jumped to 5.33% in March 2026 -- a figure Phoronix described as an all-time high that put Linux at more than double the macOS share on Steam for the same month. That March spike drew scrutiny: analysts and the GamingOnLinux community noted that Steam's survey methodology can produce volatility when sampling weights shift, and that comparisons to January 2026 (rather than February) give a cleaner baseline. Even accounting for that variability, the directional trend over the prior 24 months is unambiguous -- Linux on Steam has roughly doubled from its 2024 share. A further factor is that SteamOS 3, which powers the Steam Deck, counts as Linux in the survey; as of early 2026, Steam Deck installs represented approximately 24% of the Linux share, down from 42% two years prior -- meaning conventional desktop Linux has grown to represent a larger portion of that total.

What has not changed is the fragmentation at the multiplayer edge. Single-player gaming on Ubuntu in 2026 is, for the overwhelming majority of titles, indistinguishable from Windows in practice. The setup overhead -- driver installation, Steam configuration, the occasional ProtonDB lookup -- is a one-time cost, not a recurring one. Online competitive gaming remains variable: many titles work without issue, some require checking the anti-cheat tracker first, and a small category involving kernel-level anti-cheat is flatly incompatible regardless of what Proton version you use.

The underlying infrastructure -- Proton 10.0-4, DXVK 2.7.x, VKD3D-Proton 3.0, Mesa 26.0, GameMode, MangoHud 0.8.2 -- is now mature enough that staying current with Ubuntu LTS releases and keeping your drivers up to date is genuinely sufficient for most gaming use cases. The year-of-Linux-gaming joke persists in certain circles, but for anyone willing to spend twenty minutes on initial setup, it largely ceased being a joke some time ago.