nb1t.sh

The State of Gaming on Linux in 2026

Thu May 14 2026 · Nitin Bansal

#gaming#linux#proton

Table of Contents

What You Need to Know

Gaming on Linux in 2026 is in a strange place: technically impressive, practically fragile.

Valve’s Proton stack has made Linux gaming feel almost normal for a huge share of Windows-only Steam games. Proton combines Wine with VKD3D for DirectX 12-to-Vulkan translation and DXVK for DirectX 9/10/11-to-Vulkan translation, letting many games run without native Linux ports [10]. The Steam Deck, running Linux-based SteamOS, has pushed this further by giving publishers a real commercial reason to care about Proton compatibility [10]. Linux also crossed over 3% of Steam market share as of January 2026, and a Steam Machine is scheduled for release later in 2026 [10].

But the headline is not “Linux gaming is solved.” It is closer to this: single-player compatibility is dramatically better, while multiplayer compatibility is still controlled by anti-cheat vendors, publishers, and per-game configuration decisions.

BattlEye confirmed Proton and Steam Deck support in September 2021 [5]. VAC, BattlEye, and Easy Anti-Cheat all nominally support Proton at the SDK level [10]. Yet that support is opt-in. Each developer still has to enable it, test it, and ship it. Many major multiplayer games have not: Destiny 2, PUBG, Rainbow Six Siege X, Escape from Tarkov, Marathon, and GTA Online remain broken or effectively unusable on Linux because of anti-cheat decisions [4], [5]. GamingOnLinux tracks 210 games with some form of anti-cheat across vendors as of mid-2026, but the actual outcome varies wildly from title to title [5].

Performance is also uneven. AMD GPUs are reported to achieve near-parity with Windows through the open-source Mesa3D driver stack, while NVIDIA GPUs show a greater-than-10% DirectX 12 performance penalty on Linux, attributed to proprietary driver issues [10]. These claims matter, but they also come with a caveat: the available source bases them on personal experience and community links, not controlled benchmarks [10].

Then there is the Linux systems tax: kernel defaults, Wayland compatibility gaps, PulseAudio/PipeWire assumptions, missing native clients for Epic Games Store and GOG Galaxy, and the odd reality that native Linux ports are sometimes worse than running the Windows version through Proton [6], [10].

So the honest state of Linux gaming in 2026 is this: it has never been more viable, but it is still not boring. And for gaming platforms, boring is the real finish line.

The Real Breakthrough Is Proton

The most important thing in Linux gaming today is not a native porting renaissance. It is Proton.

Proton is the compatibility layer that turns Linux into a credible gaming platform for a large chunk of the Windows-first Steam library. It combines Wine with VKD3D for DirectX 12-to-Vulkan translation and DXVK for DirectX 9/10/11-to-Vulkan translation [10]. That stack is why so many Windows-only games can run on Linux without developers shipping a native Linux build.

This is the big shift. Linux gaming used to depend on whether a studio cared enough to port and maintain a Linux version. Now, the default path is often: ship Windows game, let Proton handle it, and fix what breaks if the Steam Deck audience is large enough to matter.

GE-Proton adds another layer to this. Maintained by Thomas Crider, also known as GloriousEggroll, it is a customized Proton fork with newer libraries and per-game patches [10]. The source characterizes it as sometimes offering “slightly better performance and compatibility with newer games,” with confidence 0.82 [10]. Heroic Games Launcher can manage GE-Proton versions, which extends some of this benefit outside Steam to Epic Games Store and GOG titles [10].

That is powerful, but it also creates a dependency chain:

Linux gamers → Proton/Wine → Windows game binaries → publisher anti-cheat configuration

Any break in that chain can make a game inaccessible. Proton can solve translation. It cannot force publishers to enable anti-cheat support, keep native depots alive, avoid Windows-only launchers, or maintain compatibility after a future update [10], [11].

There is also a quiet fragility in GE-Proton itself. It adds resilience because it gives users another track besides official Proton, but it is primarily maintained by one person, Thomas Crider [10]. That is not a criticism of the work. It is a reminder that much of the Linux gaming stack still depends on a small number of highly motivated maintainers.

The Steam Deck has clearly changed publisher incentives. Source 10 argues that because of the Steam Deck’s success, more studios are making their games compatible with Proton, with confidence 0.8 [10]. But the source does not provide quantitative data on ProtonDB ratings or total compatible titles. So the direction looks positive, but the exact scale is not established by the available sources.

Anti-Cheat Is the New Compatibility Wall

If Proton is the breakthrough, anti-cheat is the wall.

For single-player games, Proton has solved a surprising amount of the old compatibility problem. For multiplayer games, the question is often much simpler and more brutal: did the publisher enable Linux-compatible anti-cheat or not?

BattlEye is a kernel-level anti-cheat system that performs dynamic and permanent scanning using specific and heuristic or generic detection routines [5]. It confirmed native Linux support and Proton/Steam Deck opt-in compatibility on September 24, 2021 [5]. On the server side, BattlEye’s Linux product is distributed per game through each game’s official channels [1]. Server-side BattlEye monitors game processes, system memory, and network traffic, generates logs, and requires administrator-level access to configure [1].

Easy Anti-Cheat also nominally supports Proton at the SDK level [10]. But the Rocket League case shows the important caveat: even a game with a native Linux build can end up with a Windows-only EAC configuration [11]. VAC also supports Proton, though the sources provide limited Linux-specific detail on VAC behavior [10].

The key distinction is SDK-level support versus practical game-level support. The former means the anti-cheat vendor has a path. The latter means the publisher actually enabled it, tested it, and shipped it.

That difference explains the messy state of BattlEye games.

Games confirmed working on Linux or Steam Deck as of mid-2026 include War Thunder, which migrated from EAC to BattlEye and enabled Linux support on January 24, 2025, with 87,363 concurrent Steam players at the time of migration [5]. Dune: Awakening launched on June 10, 2025 with BattlEye enabled for Linux, SteamOS, and Steam Deck [5]. ARK: Survival Evolved, ARK: Survival Ascended, DayZ, Arma 3, The Crew Motorfest, Skull and Bones, Riders Republic, Mount & Blade II: Bannerlord, PlanetSide 2, Insurgency, and Conan Exiles are also listed as working [5]. The Crew Motorfest requires Proton Experimental as of August 2025 [5]. Warframe, Arma Reforged, and Arc Raiders are cited by a community source [9].

But the broken list contains some of the exact games that most matter to mainstream multiplayer players: Destiny 2, PUBG: Battlegrounds, Escape from Tarkov, Tom Clancy’s Rainbow Six Siege X, Marathon, and GTA Online [4], [5]. GTA V single-player works, but GTA Online does not work normally [4], [5].

Linux support can also be removed. CRSED: Cuisine Royale developers confirmed the end of Linux/Steam Deck support in May 2025 [5]. That matters because it turns compatibility into a moving target. A game working today is not a guarantee it will keep working.

The most useful contradiction here is about how easy BattlEye support really is.

One community source claims developers “only need to contact BattlEye to enable it with no additional code changes” [4]. But the developer of DUCKSIDE reported unexpected issues while testing Proton support through both Easy Anti-Cheat and BattlEye, including games not launching, and said “it was not as simple as a switch flip” [5]. Source 5 is more credible on this point because it reflects an actual developer implementation experience. The “just flip the switch” version may be directionally true in some cases, but it is clearly oversimplified [4], [5].

Some BattlEye games also work on Steam Deck or SteamOS but not desktop Linux, or require specific Proton versions or launch arguments like SteamDeck=1 %command% [5]. That makes the platform story even messier. “Linux support” may mean SteamOS support, desktop support, a specific Proton branch, or a launch-argument workaround.

GTA Online Shows How Fragile This Still Is

GTA V is the cleanest case study because it shows how a game can be playable, popular, and still effectively blocked from normal Linux multiplayer use.

Rockstar added BattlEye to GTA V in September 2024 [4], [5]. Its FAQ reportedly stated: “Steam Deck does not support BattlEye for GTA Online. You will be able to play GTAV Story Mode but unable to play GTA Online” [4], [5]. A community petition followed in November 2025 [4]. As of February 2026, Rockstar’s stance remained unchanged [4].

The important detail is not that BattlEye cannot support Linux. It can. The issue is that Rockstar did not enable BattlEye’s Linux compatibility flag [2], [3], [4], [5]. Community sources frame this as deliberate [2], [3], but no official Rockstar statement on intent is available. It may be deliberate blocking, or it may be that Linux compatibility was simply not prioritized because the desktop Linux market is small. The sources do not resolve that ambiguity.

There are community workarounds, but they are not normal compatibility. They involve blocking BattlEye DNS servers through /etc/hosts and enabling Valve’s Proton BattlEye Runtime with a Steam launch option:

PROTON_BATTLEYE_RUNTIME=~/.local/share/Steam/steamapps/common/Proton\ BattlEye\ Runtime/ %command%

On Steam Deck, users also need a SteamDeck=0 parameter [2], [3].

Even then, the result is degraded. Linux users using these workarounds can access invite-only or closed-friend sessions, but not public lobbies [2], [3]. Windows players who want to play with Linux friends must also modify their hosts files [2], [3]. That creates a social tax: one Linux user can make the whole friend group do extra work.

The ban-risk question is unresolved. Community sources claim the workaround is “unlikely to result in a ban” if no cheats are used, but this is speculative, with confidence 0.35–0.45, and there is no official Rockstar confirmation [2], [3].

The sources also differ in how broken GTA Online is. Source 4 presents GTA Online as simply unplayable on Steam Deck/Linux [4]. The ArchWiki says GTA V Online via Proton “does not fully support BattlEye”—only the Windows version of BattlEye is supported, and users can access Online for only a few minutes at most [6]. Community guides describe invite-only workarounds but no public lobby support [2], [3].

These are not really contradictory. They describe different levels of brokenness. For regular play, all roads lead to the same conclusion: GTA Online is effectively non-functional on Linux.

One caveat matters: Source 4 is a low-confidence Steam Community forum post quoting an AI-generated Brave browser summary, and it does not provide a direct Rockstar FAQ URL for verification [4]. Source 5, the GamingOnLinux database entry, is higher confidence and corroborates the core claim that Rockstar did not enable BattlEye Proton support [5].

Marathon Shows the Bungie Pattern

Marathon, Bungie’s upcoming shooter, is another anti-cheat test case.

The game uses BattlEye kernel-level anti-cheat [7], [9] and did not support Linux during its Nextfest demo/playtest period in March 2026 [8]. A Linux gamer posted on Bungie’s official Marathon help center on March 11, 2026, confirming non-support across three Linux setups: CachyOS on desktop, Bazzite on laptop, and SteamOS on Steam Deck [8].

Steam Community users report that Steam Deck players are “completely locked out” of the game [9]. One user says they bought Marathon on Steam and requested a refund because it did not work on their Linux system [9].

Bungie has not issued a public statement on Linux support for Marathon or Destiny 2 in the provided sources [8], [9]. A claim that GamingOnLinux contacted Bungie’s press team multiple times without response is very low confidence, 0.15, and unverified [9].

The broader point is that Marathon does not look like an isolated issue. Destiny 2 is also listed as broken on Linux because Bungie has not enabled BattlEye Linux support [5], [9]. That suggests a pattern across Bungie’s catalog, but the available sources do not explain Bungie’s reasoning.

There is also a language problem here. Several community sources use phrases like “refuse to support” or “refuse to cater to Linux gamers” [7], [9]. That may be emotionally understandable, but the evidence only shows that support has not been enabled [4], [5], [8], [9]. A deliberate policy decision to block Linux is different from a low-priority backlog item, a playtest limitation, or an unresolved engineering issue. The sources do not let us distinguish between those.

Rocket League Is the Warning Sign

Rocket League is not yet a confirmed disaster in the provided evidence. It is more like a warning light.

The game has an existing native Linux build, depot 252961, sized 10.05 GiB, and Steam Deck Verified status tested on February 16, 2022 [11]. But a SteamDB changelist from January 27, 2026, changelist #33486621, added a new launch option referencing Binaries/Win64/RocketLeague_EAC.exe with oslist: windows, under the devqa beta key [11].

That does not prove Linux support is ending. The native Linux build still existed as of the source date, and the poster is speculating that it may be deprecated [11]. The devqa beta key also means the change is still in testing. It is unknown whether this EAC integration uses the Linux-compatible EAC SDK or a Windows-only variant [11].

Still, the anxiety is understandable. Psyonix is owned by Epic Games, and the source notes community concern because of Epic’s perceived history with Linux [11]. The GTA V precedent is also cited: a popular game adds anti-cheat, and Linux/Steam Deck users get cut off [11].

This is the deeper fear in Linux gaming now. The problem is not just that some games do not work. It is that a game can work for years and then lose practical compatibility because an anti-cheat implementation changes.

GPU Performance Depends Heavily on Vendor

The GPU story is not symmetrical.

AMD GPUs are reported to deliver comparable Linux and Windows gaming performance, with confidence 0.75, through the open-source Mesa3D driver stack [10]. The source author implicitly treats AMD’s open-source approach as superior for Linux gaming [10].

NVIDIA GPUs are reported to suffer a greater-than-10% DirectX 12 performance penalty on Linux compared with Windows, with confidence 0.8 [10]. The source attributes this to NVIDIA’s proprietary driver issues [10]. The penalty is specific to DirectX 12 workloads and may not apply equally to Vulkan-native titles.

The caveat is important: these performance claims are based on personal experience and community forum links, not controlled benchmarks [10]. No raw performance data, benchmark methodology, or specific game-by-game test results are provided. The greater-than-10% NVIDIA figure should be treated as an estimate rather than a precise measurement [10]. The provided sources also do not cover NVIDIA’s open-source kernel module efforts or AMD’s ROCm compute stack in a gaming context.

Still, the practical implication is obvious. NVIDIA holds the majority of the discrete GPU market. So even if AMD Linux gaming is in good shape, many PC gamers considering a Linux switch may run straight into the DirectX 12 NVIDIA penalty [10].

There is also a kernel-level performance trap. Since kernel 6.2, the split_lock_mitigate sysctl is enabled by default and significantly harms performance in Counter-Strike: Source engine games and BattlEye titles [6]. The workaround is to set:

kernel.split_lock_mitigate = 0

GameMode can toggle this parameter at runtime [6]. This is a very Linux kind of issue: a security-focused kernel default silently hurting gaming performance unless the user knows the right sysctl.

Linux Gaming Is Growing, But Still Small

Linux had over 3% Steam market share as of January 2026, according to the Steam Hardware & Software Survey cited by Source 10 [10]. The exact figure is not provided.

That is still low single digits, but it is no longer invisible. The Steam Deck matters here because it turned Linux gaming from a hobbyist desktop story into a consumer hardware story [7], [8], [9], [10]. It gives developers a reason to care about Proton compatibility even if they never cared about desktop Linux.

A Steam Machine is scheduled for release in 2026 [10]. Source 10 assumes that if it gains market acceptance, it could further accelerate Proton compatibility work, but this is uncertain, with confidence 0.65 [10]. No manufacturer, pricing, or specification details are provided in the available sources.

The Steam Deck creates pressure, but not enough to compel every publisher. Rockstar and Bungie remain major holdouts in the provided evidence [4], [5], [8], [9]. That is the market-share trap: Linux is now large enough to be noticed, but not always large enough to force support.

SteamOS, CachyOS, Bazzite, and the Tooling Layer

Linux gaming is not one platform. It is a stack of distributions, launchers, compatibility layers, and per-game hacks.

SteamOS is Valve’s Linux-based Steam Deck OS. Some BattlEye games work only on Steam Deck or SteamOS, which makes it a privileged environment inside the broader Linux gaming world [5], [8], [10].

CachyOS is Arch-based and performance-oriented. It has a cachyos-gaming-applications meta-package bundling Steam, Lutris, and Heroic [8], [10]. Bazzite is a Fedora-based immutable distribution designed for gaming and used on laptops and handhelds [8]. One Marathon help-center user reported using CachyOS on desktop, Bazzite on laptop, and SteamOS on Steam Deck, which neatly captures how fragmented Linux gaming setups can be [8].

The tooling layer is just as important as the distributions.

Steam is still the center of gravity. It has had a native Linux client since 2013 and is where Proton integration matters most [10]. Lutris works as a multi-source game manager, supporting Steam, Epic, GOG, Wine, Proton, and ScummVM runtimes [2], [10]. Heroic Games Launcher covers Epic Games Store, GOG, and Amazon, and can manage GE-Proton versions [10]. Source 10 says Heroic is reportedly faster than the official Epic Games Store client, with confidence 0.7 [10].

GameMode handles runtime performance tuning and can toggle kernel.split_lock_mitigate [6]. GE-Proton provides newer libraries and per-game patches [10].

The missing piece is official storefront support outside Steam. GOG Galaxy and Epic Games Store do not offer native Linux clients [10]. Linux users therefore rely on community alternatives like Heroic and Lutris. Those tools are impressive, but their existence also proves the point: non-Steam gaming on Linux is still treated as second-class by major storefronts [10].

There are also gaps in the evidence. Source 10 does not cover Itch.io, Ubisoft Connect, or EA App [10]. GamingOnLinux’s anti-cheat database tracks Steam/SteamOS-based gaming, so BattlEye status through non-Steam launchers like Epic Games Store is not tracked [5].

Native Linux Ports Are Not Automatically Better

A native Linux port sounds like the ideal outcome. The evidence says: not always.

Borderlands 2’s native Linux version lacks working Steam multiplayer, cannot use Steam Cloud saves made on Windows, does not support the Commander Lilith DLC, and has other issues. In that case, the Windows version through Proton is the better option [6].

Civilization VI has a similar pattern: many users report better performance using the Windows version through Proton, with confidence 0.7 [6].

This flips the old assumption. Native ports can be better when they are maintained well. But a stale native port can age badly, while Proton keeps improving underneath the Windows version. In the provided sources, there are more examples of native-port failure than native-port success [6].

That creates a perverse incentive. If Proton is often better than a weak native port, why should publishers invest in native Linux versions at all? The sources do not answer that, but the pattern is hard to ignore.

The Desktop Linux Tax

Beyond Proton, anti-cheat, and drivers, desktop Linux still has a stack of smaller compatibility traps.

Wayland remains incomplete for gaming in the provided evidence. Steam Link does not work with Wayland, producing either a blank screen or flickering when connecting to a Steam host running on Wayland [6]. Some games require SDL_VIDEODRIVER=x11 to function under Wayland, with Crypt of the NecroDancer mentioned in a May 2024 context [6]. This suggests X11 remains more reliable for gaming, even while the broader Linux desktop moves toward Wayland.

Audio is another source of friction. PipeWire users may need pipewire-alsa for games using FMOD, including Project Zomboid, Don’t Starve, and Unrailed [6]. Unity-based games such as Papers Please and Vampire Survivors expect PulseAudio and can crash with SIGSEGV if it is not installed [6].

Then there is the kernel 6.2 split-lock mitigation default, which can significantly hurt Counter-Strike: Source engine games and BattlEye titles unless disabled or managed through GameMode [6].

None of these issues is necessarily fatal. But together they create the Linux tax: the user needs to know what display server they are running, what audio stack a game expects, what kernel setting hurts performance, which Proton version to use, and whether the anti-cheat runtime is enabled.

Windows has problems too. But it usually does not ask a gamer to learn this much vocabulary just to play.

Steam Deck Is Not the Same as Desktop Linux

The Steam Deck is the best thing that has happened to Linux gaming, but it may also split Linux gaming into two worlds.

Some BattlEye games work only on Steam Deck or SteamOS, not desktop Linux, or need Deck-specific launch arguments like SteamDeck=1 %command% [5]. The GTA Online workaround also differs between Steam Deck and desktop, requiring SteamDeck=0 on Steam Deck [2], [3].

That matters because SteamOS is controlled. Desktop Linux is not. Desktop users vary across distributions, kernels, drivers, Wayland/X11, PulseAudio/PipeWire, launchers, and Proton variants. SteamOS gives Valve a stable target. Desktop Linux gives publishers a matrix.

The risk is that “Linux support” increasingly means “works on Steam Deck,” not “works cleanly across Linux.” That may still be a net win, but it is not the same thing as broad Linux parity.

What This Means

Anti-cheat is now the main compatibility frontier. Proton has made game launching dramatically better, especially for single-player titles, but multiplayer compatibility still depends on publisher-controlled anti-cheat settings [1], [2], [3], [4], [5], [7], [9], [11].

Valve has leverage, but not command authority. It can build Proton, ship the Proton BattlEye Runtime, sell the Steam Deck, and launch a Steam Machine. It cannot force Rockstar, Bungie, or any other publisher to enable Linux support [2], [3], [10].

Community workarounds are clever but fragile. GTA Online workarounds require DNS manipulation, degraded invite-only play, uncertain ban risk, and sometimes changes by Windows friends too [2], [3]. That is not mainstream compatibility. That is enthusiasts holding the bridge together with shell commands.

NVIDIA performance is a practical barrier. If AMD is near Windows parity and NVIDIA has a greater-than-10% DirectX 12 penalty, the GPU vendor choice becomes part of the Linux gaming decision [10]. But again, the available evidence lacks controlled benchmarks, so the exact magnitude remains uncertain [10].

Native ports have lost some moral authority. Borderlands 2 and Civilization VI show that a Windows build through Proton can be better than a native Linux version [6]. That may make users more pragmatic, but it also makes the platform more dependent on Proton.

Official storefront support is still incomplete. Steam is strong. Epic Games Store and GOG Galaxy lack native Linux clients, pushing users toward Heroic and Lutris [10]. Those tools are useful, but they are also a sign that Linux still depends heavily on community infrastructure.

The big picture: Linux gaming in 2026 is not held back by one unsolved problem. It is held back by an interaction of business incentives, anti-cheat policy, driver quality, kernel defaults, desktop fragmentation, and missing official clients.

Where This Could Go Next

The optimistic case is easy to imagine. Steam Deck keeps growing. The 2026 Steam Machine gives publishers another reason to care [10]. More studios follow the War Thunder and Dune: Awakening path by enabling BattlEye support properly [5]. NVIDIA improves DirectX 12 performance. Wayland gaming matures. GameMode or similar tools hide the kernel-tuning mess [6]. Linux gaming crosses 5% Steam share and becomes boringly functional for most users.

The base case is more likely from the available evidence. Anti-cheat remains patchy. Some publishers enable Linux support, many do not [5]. SteamOS stays relatively smooth because Valve controls the target. Desktop Linux remains powerful but configuration-heavy, with kernel, display server, and audio issues still showing up [6]. Native ports remain inconsistent, and Proton remains the safer bet for many games [6]. The Steam Machine finds a niche audience [10]. Linux sits somewhere around a minority 3–5% Steam share. GE-Proton, Lutris, Heroic, and community workarounds keep closing gaps where publishers do not [10].

The pessimistic case is that publishers increasingly adopt kernel-level anti-cheat configurations incompatible with Proton. Bungie’s Marathon and Destiny 2 pattern becomes normal [5], [8], [9]. Rocket League-style fears become actual regressions [11]. The Steam Machine underperforms. NVIDIA does not fix its DirectX 12 penalty. Wayland creates a painful transition period. Kernel security defaults keep colliding with performance. Linux’s over-3% Steam share stagnates or declines [10].

All three futures are plausible from the evidence. The difference is whether publishers decide Linux users are worth supporting before compatibility regressions outpace Proton’s gains.

Unknowns and Open Questions

The exact Linux market share percentage on Steam as of mid-2026 is unknown. Source 10 only provides “>3%” as of January 2026 [10].

The number of BattlEye games tracked separately from the 210 anti-cheat games across all vendors is not provided [5].

The actual technical requirements for enabling BattlEye Proton support remain unclear. One source frames it as trivial [4], while the DUCKSIDE developer experience suggests real troubleshooting may be required [5].

BattlEye’s official Proton/Linux support policy as of 2026 is not directly available in the provided sources [7], [8], [9].

Bungie’s reasoning for not enabling BattlEye Proton support for Marathon or Destiny 2 is unknown [8], [9].

Rocket League’s future is unresolved: the native Linux build may be maintained, deprecated, or replaced [11]. It is also unknown whether Rocket League’s EAC integration uses the Linux-compatible EAC SDK or a Windows-only variant [11].

The provided sources do not give Steam Machine model, partner, price, or specification details for the scheduled 2026 release [10].

The state of storefronts beyond Steam, Epic, GOG, and Amazon—such as Itch.io, Ubisoft Connect, and EA App—is not covered [10].

Current ProtonDB compatibility rates, including Gold and Platinum shares, are not provided [10].

Controlled benchmarks validating AMD near-parity and NVIDIA’s greater-than-10% DirectX 12 penalty are missing from the available evidence [10].

It is unknown whether Rockstar changed its GTA Online stance between February 2026 and May 2026 [4].

The scale of SteamOS-only versus desktop Linux divergence for BattlEye games is not quantified [5].

The interaction between AMD/NVIDIA driver stacks, anti-cheat, and real-world gaming performance in 2026 is not covered in depth.

There is no aggregate player-count estimate for how many Linux or Steam Deck users are affected by anti-cheat incompatibility across all titles.

It is completely unknown whether Rockstar or any publisher has issued bans for DNS-blocking workarounds [2], [3].

Marathon’s full-release Linux support status is unknown because the sources only cover the playtest period [8].

There is no historical trend data showing how many games have gained versus lost Linux anti-cheat compatibility over time [5].

References

  1. BattlEye Linux: Installation, Usage, and Best Practices - https://linuxvox.com/blog/battleye-linux
  2. How to play GTA Online on Linux (post BattlEye) - https://steamcommunity.com/sharedfiles/filedetails?id=3658540317
  3. How to play GTA Online on Linux (Post BattlEye) - https://reddit.com/r/linux_gaming/comments/1sjce6o/how_to_play_gta_online_on_linux_post_battleye
  4. Rockstar Games refuses to enable BattlEye on Linux/Steam Deck for GTA Online — Community Discussion - https://steamcommunity.com/app/271590/discussions/0/733658398226309921
  5. BattlEye Anti-Cheat Games on Linux / Steam Deck / SteamOS - GamingOnLinux - https://gamingonlinux.com/anticheat/vendor/battleye
  6. Steam/Game-specific troubleshooting - ArchWiki - https://wiki.archlinux.org/title/Steam/Game-specific_troubleshooting
  7. Marathon anti-cheat excludes Linux gamers from future shooter games (Facebook post by Meena Rani) - https://facebook.com/fbvideo/posts/marathon-anti-cheat-excludes-linux-gamers-from-future-shooter-gamesanti-cheat-ha/1195325116087430
  8. Linux Support - Marathon Help - https://help.marathonthegame.com/hc/en-us/community/posts/47097928909716-Linux-Support
  9. Marathon uses BattlEye anti-cheat, which has officially supported Proton/Linux since 2021 - https://steamcommunity.com/app/3065800/discussions/0/766312101614554226
  10. Gaming on Linux - https://somethinglikegames.de/en/blog/2026/linux_05_gaming
  11. This may be the end for the Rocket League on Linux - https://reddit.com/r/linux_gaming/comments/1qvm6jh/this_may_be_the_end_for_the_rocket_league_on_linux

Related