DayZ on Linux: Proton, BattlEye, vm.max_map_count, and dayz-ctl

There is something philosophically fitting about running DayZ on Linux. The game is built around scarcity, adaptation, and improvisation — the idea that resources you take for granted can disappear without warning. Linux gaming, at least until recently, asked the same things of the people who chose it. You learned to improvise. You learned the layers. You learned why things broke, not just how to fix them. And when it finally worked, you had a level of ownership over your environment that no Windows user could claim.

This guide is for the gamer who wants to go deep. Not just "here are the steps," but here is what is happening inside the machine when you run a Windows-only survival game on a Linux kernel through a compatibility layer that translates Direct3D graphics calls to Vulkan in real time while a kernel-level anti-cheat system tries to verify the integrity of a process running inside a Wine prefix. If that sentence made you lean forward in your chair, you are in the right place.

Part One: What You Are Actually Running

DayZ Is a Windows Game in a Compatibility Layer, Not a Port

DayZ (Steam App ID 221100), developed by Bohemia Interactive, has no native Linux binary. What you are running when you launch DayZ through Steam on Linux is a Windows PE (Portable Executable) binary executing inside a Wine environment that Valve ships as part of Proton. Wine is not an emulator. It is a compatibility layer that implements the Win32 API — the interface through which Windows applications talk to the Windows operating system — on top of POSIX-compliant systems like Linux.

The distinction between emulation and translation matters enormously for performance. An emulator intercepts machine-level instructions and replaces them. That is computationally expensive. Wine intercepts API calls — the higher-level requests a program makes of the operating system — and maps them to equivalent Linux system calls. Because modern x86-64 Linux and Windows CPUs are identical, the game's actual instructions run natively on your hardware. Only the OS interface layer is translated. This is why Proton-run games can approach or even match native Windows performance in some scenarios.

Valve's Proton is a packaged, hardened fork of Wine that includes several additional components: DXVK for DirectX 9/10/11 to Vulkan translation, VKD3D-Proton for DirectX 12 to Vulkan translation, Steam Linux Runtime (a containerized environment), pressure-vessel (a tool for creating reproducible container environments), and various media codecs.

The Graphics Translation Chain: Where DirectX Meets Vulkan

DayZ uses DirectX 11 for rendering. On Windows, DirectX 11 calls go to the Windows graphics driver, which translates them into hardware commands for your GPU. On Linux, there is no DirectX 11. Instead, DXVK intercepts those DirectX 11 calls and translates them to Vulkan, which Linux GPU drivers understand.

DXVK was created by Philip Rebohle (doitsujin) and is now maintained collaboratively, incorporated directly into Proton. When DXVK receives a DrawIndexedPrimitive call from DayZ, it translates that into the equivalent vkCmdDrawIndexed Vulkan command. This is not a one-to-one mapping — the two graphics APIs have different abstractions, different resource binding models, different synchronization primitives — and a significant amount of engineering work goes into making the translation correct and fast.

One of the most important optimizations in DXVK is shader compilation and caching. When DayZ loads a new area, DXVK needs to compile the game's HLSL-derived shaders into SPIR-V (the intermediate representation used by Vulkan). This compilation happens once and is cached on disk in your Steam compatibility data folder (typically ~/.steam/steam/steamapps/shadercache/221100/). On first launch, you may experience stuttering as shaders compile. On subsequent launches, the cache is warm and performance is much smoother.

Understanding where Proton puts DayZ's data is useful for troubleshooting. The Wine prefix for DayZ lives at ~/.steam/steam/steamapps/compatdata/221100/pfx/. This directory is a simulated Windows file system: drive_c/ maps to the C: drive, and DayZ's user-specific data — including profiles, keybinds, and local configuration — sits at drive_c/users/steamuser/Documents/DayZ/. If you need to back up your DayZ configuration before a reinstall or move to a new machine, that is the directory to copy.

Regarding shader caching: DXVK 2.7 (July 2025) removed the legacy per-game state cache entirely — the .dxvk-cache file format no longer exists in GE-Proton 10.x or current Valve Proton. It was superseded years earlier by VK_EXT_graphics_pipeline_library (GPL), which compiles pipeline state directly at load time and stores the results in the GPU driver's own disk cache rather than a separate DXVK-managed file. The actual shader cache to manage post-update is now Steam's Vulkan pre-cache at ~/.steam/steam/steamapps/shadercache/221100/. If you experience persistent graphical corruption, missing textures, or crashes after a DayZ or Proton update, delete that directory and let it rebuild on the next launch — at the cost of initial shader compilation stutter. You can monitor shader compilation activity in real time by adding DXVK_HUD=compiler to Steam launch options temporarily; it shows active pipeline compilation threads in the top-left overlay.

Part Two: The Critical Kernel Parameter That Breaks DayZ

vm.max_map_count: The Hidden Landmine

If there is one single piece of technical knowledge that separates DayZ players who get the game working on Linux from those who give up after repeated crashes and freezes at the loading screen, it is this:

The Linux kernel maintains a per-process limit on the number of virtual memory areas (VMAs) a single process can create. A VMA is a contiguous region of virtual address space with uniform permissions and characteristics — each mmap call, each loaded shared library, each anonymous memory mapping, each memory-mapped file creates at least one VMA. The kernel tracks these using a red-black tree data structure for efficient lookup.

The default value on many Linux distributions has historically been 65,530. That number was set a long time ago when processes were far less complex. DayZ, running through Wine/Proton, creates an enormous number of VMAs — far more than 65,530 — because Wine itself maps extensive memory regions to simulate the Windows memory model, and then the game's own allocations, all the loaded DLLs, the shader caches, and the game's streaming world data push the process well beyond the limit.

When a process hits this limit, it does not receive a graceful error message and shut down cleanly. It crashes. Which is why DayZ freezes mid-loading screen, or stutters and dies a few minutes into a session, with no obvious error message and nothing useful in logs for a user who doesn't know where to look.

The fix is to increase vm.max_map_count. This is a standard sysctl kernel parameter — readers who want to go deeper on Linux kernel tuning via sysctl will find a full treatment of performance-related parameters in a dedicated guide. To apply the fix immediately in the current session:

$ sudo sysctl -w vm.max_map_count=1048576

To make it permanent across reboots, add the following to /etc/sysctl.d/99-gaming.conf:

vm.max_map_count=1048576

$ sudo sysctl --system

The value 1048576 (2^20) has become the community standard, adopted by Fedora, Pop!_OS, SteamOS, and as of April 2024, Arch Linux. The Arch announcement noted the change would address performance, crash, and start-up issues for memory-intensive applications, specifically naming Wine and Steam Proton use cases. DayZ is named in Ubuntu's Launchpad bug tracker (Bug #2057792) alongside Hogwarts Legacy, Counter-Strike 2, Payday 2, and Star Citizen as a triggering game for this issue.

Part Three: BattlEye on Proton

The Problem Anti-Cheat Was Never Designed to Solve on Linux

BattlEye is a kernel-level anti-cheat system developed by BattlEye Innovations e.K., founded in October 2004 by Bastian Suter. It was initially released as a third-party anti-cheat for Battlefield Vietnam in 2004 and was integrated into DayZ Standalone by Bohemia Interactive in 2013. Around 2014, BattlEye introduced a kernel-mode driver and new launcher for games including DayZ, and after the proactive system went live in early 2015, cheating in DayZ was reduced significantly.

BattlEye operates in both user mode and kernel mode, scanning process memory, checking loaded modules, monitoring API call patterns for cheat signatures, and maintaining a global ban infrastructure that tracks unique hardware identifiers to prevent ban evasion across account switches. If you are running a DayZ server on Linux and want to understand the server-side perspective on blocking cheaters on a DayZ Linux server, that is covered in a separate guide.

For years, BattlEye and Linux were simply incompatible. Running DayZ on Linux via Wine meant running without anti-cheat, which meant being blocked from any BattlEye-enabled server — effectively the entire game. The technical reason was that BattlEye's kernel-mode driver was written for the Windows kernel. It loaded as a Windows kernel driver, hooking into Windows kernel structures that simply do not exist in the Linux kernel. Wine cannot bridge kernel-mode code; it can only translate user-space API calls.

The December 2021 Breakthrough

The situation changed permanently in December 2021. Valve's Steam Deck was approaching launch and needed multiplayer gaming to work on Linux. Working with BattlEye directly, Valve engineered a solution. The official Steamworks announcement was brief and consequential:

No additional work is required by the developer besides that communication.

Valve Steamworks Development, BattlEye Proton integration announcement, December 2021

Bohemia Interactive was among the first developers to opt in.

The technical solution involves BattlEye operating at user-mode rather than kernel-mode within the Proton environment. The Proton BattlEye Runtime is a separate installable component in Steam that provides the hooks BattlEye needs to function inside the Wine/Proton prefix. The anti-cheat communicates through the game's normal network connection using encrypted packets, and the server-side component validates player integrity rather than relying exclusively on the local kernel driver for detection.

Part Four: The Launcher Problem and dayz-ctl

Why Bohemia's Own Launcher Fails Under Proton

Running vanilla DayZ without mods through Proton works well. The problem arises when you want to play on modded servers, which describes a very significant portion of the DayZ community. Modded servers running custom maps like Namalsk, DeerIsle, Takistan, and Chernarus Plus represent some of the game's most vibrant gameplay.

DayZ's official launcher — the separate application that appears before the game itself — handles mod installation, updates, and the construction of the -mod= launch argument that tells the DayZ client which mods to load. This launcher is a .NET application that communicates with Bohemia's servers via a Windows-specific API path. Under Proton, it fails to correctly install mods or pass launch parameters to the game client. The exact failure mode involves the launcher attempting to invoke SteamCMD-style mod management through pathways that break in the Wine environment, and the argument string construction can exceed length limits, especially on servers requiring many mods.

dayz-ctl: The Community Launcher

The primary community solution is dayz-ctl, created by developer WoozyMasta (Maxim Levchenko). The current release is version 0.2.0. The project's README is direct about why it exists:

The project's README states plainly that at the time dayz-ctl was created, Bohemia had still not produced a launcher capable of correctly installing modifications or connecting to game servers — and that failure is exactly what dayz-ctl was built to replace. (WoozyMasta, dayz-ctl README)

dayz-ctl is written entirely in Bash. This is not a limitation — it is an architectural decision that makes the tool maximally transparent, portable, and auditable. There are no compiled binaries. You can read every line of its logic. It depends on standard Unix utilities: curl for HTTP, jq for JSON parsing, fzf for the fuzzy-finding interactive terminal interface, gum for dialog and output styling, awk/grep/sed for text processing, and geoiplookup for server geolocation.

What dayz-ctl does under the hood illuminates how DayZ's modding works at the file system level. The game accepts a -mod= command-line argument that is a semicolon-delimited list of relative directory paths pointing to mod folders inside the DayZ installation directory. For example:

-mod=@CF;@DeerIsle;@VPPAdminTools;@DayZCommunityFramework

Each @ModName directory must contain the mod's PBO (Packed Bank of files) archives — Bohemia's proprietary container format used across the Enfusion and Real Virtuality engine lineage, structurally similar to a zip file but optimised for fast engine loading. Each PBO bundles game assets including scripts, configs, textures, and models, and carries a 20-byte SHA key signature appended to the end of the file that BattlEye and the server use for integrity verification. A mod's PBO must also include a meta.cpp descriptor. dayz-ctl bypasses the launcher entirely, queries the DayZSA Launcher API for server information including required mod lists, uses SteamCMD or manual Steam workshop subscriptions to ensure mods are downloaded, constructs the -mod= argument directly, and passes it to the DayZ client binary through Proton.

To install dayz-ctl:

$ curl -sSfLA dayz-ctl https://raw.githubusercontent.com/WoozyMasta/dayz-ctl/master/install | bash

This script detects your package manager (apt, yum, dnf, pacman, apk), installs dependencies, downloads the main script to ~/.local/bin/dayz-ctl, creates a desktop entry at ~/.local/share/applications/dayz-ctl.desktop, and optionally adds a dock launcher. The configuration lives in ~/.local/share/dayz-ctl/, with separate JSON files for the server database, mod database, and user profile.

Launch it by running dayz-ctl in a terminal or using the desktop shortcut. The fzf-powered interface presents an interactive server browser. You can search with compound filters: ^namalsk DE !PVE !RP would find servers whose name starts with "namalsk," hosted in Germany, excluding servers tagged as PVE or RP. The ^ anchors to the beginning, ! negates, and bare terms are fuzzy-matched anywhere in the server name.

Alternative Launchers: DZGUI and dayz-linux-cli-launcher

dayz-ctl is the primary community launcher, but two other tools appear frequently in player searches and are worth knowing about.

DZGUI (github.com/aclist/dztui, also hosted at codeberg.org/aclist/dztui) is maintained by developer aclist and serves the same core function as dayz-ctl — replacing Bohemia's broken launcher for modded server access on Linux — but with a graphical interface built using Zenity dialog boxes rather than a terminal fzf interface. It is explicitly designed for both Linux desktop and Steam Deck, and its documentation was updated in January 2026. DZGUI queries server metadata in a tabular display, handles mod staging and argument construction, and connects directly to Steam and DayZ servers without routing through any intermediary endpoints. It requires a Steam API key to access server data; the documentation walks through the Steam Web API key registration process. For players who find dayz-ctl's terminal interface unwelcoming, DZGUI is the established GUI alternative.

dayz-linux-cli-launcher (github.com/bastimeyer/dayz-linux-cli-launcher) by developer bastimeyer is the older project that directly inspired dayz-ctl. It is the tool dayz-ctl's README credits as the originating idea. It is no longer actively maintained in the same way as dayz-ctl, but it appears extensively in archived guides and search results. If you encounter references to it, dayz-ctl is its functional successor — more actively developed, with SteamCMD integration, a larger feature set, and the same core architecture of constructing the -mod= argument and bypassing the Bohemia launcher entirely.

DayZSA Launcher (dayzsalauncher.com) is a third-party Windows application, not a Linux tool. It does not run natively on Linux under Proton. However, its API endpoint (https://dayzsalauncher.com/api/v1) is the server data source that both dayz-ctl and DZGUI query in the background. Players searching for "how to use DZSA Launcher on Linux" are looking for what dayz-ctl provides — the DZSA Launcher API is already doing its job behind the scenes whenever you use dayz-ctl or DZGUI to browse servers.

Part Five: Choosing and Configuring Proton

Stock Proton vs. GE-Proton

Steam ships with official Proton versions maintained by Valve. GE-Proton (maintained by Thomas Crider, "GloriousEggroll") is a community fork that ships bleeding-edge patches before they reach Valve's stable release. The current series as of early 2026 is GE-Proton 10.x (GE-Proton 10-34 released March 2026). For DayZ specifically, the community consistently recommends GE-Proton for several reasons.

GE-Proton typically includes the latest DXVK and VKD3D-Proton releases immediately, whereas Valve may take weeks or months to roll these into a stable Proton release. It also includes media codec support that Valve's builds omit for licensing reasons, and game-specific patches that haven't yet been upstreamed.

To install GE-Proton, download the latest release from github.com/GloriousEggroll/proton-ge-custom. Create the compatibilitytools directory if it does not exist, then extract the tarball directly into it:

$ mkdir -p ~/.steam/steam/compatibilitytools.d/
$ tar -xf GE-Proton*.tar.gz -C ~/.steam/steam/compatibilitytools.d/

Restart Steam after extraction, then right-click DayZ in your library, go to Properties > Compatibility, check "Force the use of a specific Steam Play compatibility tool," and select the GE-Proton version from the dropdown.

The Proton Version Regression Problem

In early 2024, a regression in Proton 9.0 caused DayZ server connections to fail with error code 0x00020009. A GitHub issue on the Valve steam-for-linux repository documented the problem as a regression introduced in the new version of Proton. The fix at the time was to roll back to Proton 8.0-5 or switch to Proton Experimental. The issue was ultimately resolved in later Proton 9.0 point releases.

This episode illustrates why tracking the state of Proton versions for your specific game matters. Checking ProtonDB before and after a Proton update is standard hygiene for serious Proton gaming.

The PROTON_BATTLEYE_RUNTIME Launch Option

To ensure BattlEye operates correctly, set the following in DayZ's Steam launch options (right-click DayZ > Properties > General > Launch Options). Steam launch options are executed as a bash command, so the space in the path must be escaped with a backslash:

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

Substitute the Flatpak path if you are running Steam as a Flatpak:

PROTON_BATTLEYE_RUNTIME=~/.var/app/com.valvesoftware.Steam/data/Steam/steamapps/common/Proton\ BattlEye\ Runtime/ %command%

Part Six: VKD3D-Proton and the Translation Stack

DayZ itself uses DirectX 11, meaning it primarily benefits from DXVK rather than VKD3D-Proton (which handles DirectX 12). However, understanding VKD3D-Proton matters for any serious Linux gamer because the evolution of the translation stack affects the entire Proton ecosystem, including the Wine version, DXVK integration, and how overlays and GPU features work.

VKD3D-Proton is maintained by Hans-Kristian Arntzen of Valve's Linux graphics team. The project released version 3.0 in November 2025, described by 9to5Linux as one of the tool's largest updates yet. Among the highlights was a complete rewrite of the DXBC shader backend — DXBC being the bytecode format used for DirectX shaders before DirectX 12's DXIL format. The release notes explain that DXVK and VKD3D-Proton now share the same DXBC frontend, giving cleaner and leaner IR to work with.

This matters specifically for DayZ because DXVK processes DayZ's DirectX 11 shader bytecode through this same DXBC path. The shared frontend means that improvements to DXBC handling in VKD3D-Proton 3.0 directly benefit DXVK as well — including better shader compilation, fewer crashes in edge cases, and improved compatibility with DXBC patterns that the legacy backend mishandled.

Part Seven: Performance Tuning

Linux provides extensive control over the translation stack through environment variables. These can be added to Steam's launch options, positioned before %command%:

Use the builder below to assemble your own launch option string. Select what applies to your setup:

Part Eight: The Wine Prefix and Troubleshooting Cache Corruption

Where DayZ Stores Its Data Under Proton

Every game running through Steam's Proton has its own isolated Wine prefix — a self-contained simulated Windows file system. For DayZ (App ID 221100), this prefix lives at:

~/.steam/steam/steamapps/compatdata/221100/pfx/

Inside this prefix, the drive_c/ directory is DayZ's simulated C: drive. Your DayZ profile data, keybinds, and local server history live at drive_c/users/steamuser/Documents/DayZ/. If you are migrating to new hardware or reinstalling Linux, copying this directory preserves your in-game settings and profile without requiring a full game reinstall.

Clearing Corrupted Shader Caches

When graphical corruption, random crashes, or severe loading stutters start after a DayZ patch or a Proton version change, the shader cache is the first suspect. An important technical note: DXVK 2.7 (July 2025) removed the legacy .dxvk-cache file format entirely. That per-game state cache file — the one older guides tell you to find at ~/.steam/steam/steamapps/common/DayZ/221100.dxvk-cache — no longer exists in GE-Proton 10.x or current Valve Proton. It was made obsolete by VK_EXT_graphics_pipeline_library, which compiles and stores pipeline state in the GPU driver's own disk cache rather than a separate DXVK-managed file. If you have a lingering 221100.dxvk-cache file from an older setup, it is safe to delete it, but deleting it has no effect on current DXVK versions.

The cache that actually matters today is Steam's Vulkan shader pre-cache for DayZ. Clear it with:

$ rm -rf ~/.steam/steam/steamapps/shadercache/221100/

This forces a full shader recompilation from scratch on the next launch. You will see initial compilation stutter in the first session. To monitor compilation activity in real time, add DXVK_HUD=compiler to Steam launch options temporarily — it displays active shader pipeline threads in the overlay and disappears when compilation is complete.

Verifying Proton and DXVK Are Active

If you want to confirm that DXVK is actually handling DayZ's rendering (and not Wine's fallback wined3d renderer), launch DayZ with the DXVK HUD enabled. Add this to Steam's launch options temporarily:

DXVK_HUD=devinfo,fps %command%

If DXVK is active, a small overlay appears in the top-left corner of the game window showing the GPU name, the DXVK version string (for example, DXVK 2.7.1), and the current frame rate. If you see wined3d or nothing at all, Proton's DXVK integration is not activating correctly — which typically indicates a broken Proton installation or an incorrectly set compatibility tool override.

Part Nine: Distribution Considerations

Distribution choice affects driver availability, default kernel parameters, and gaming-specific tooling available out of the box. This is a genuinely technical consideration for DayZ on Linux. The game's current stable release is 1.29 (version 1.29.162510, released April 8, 2026) — a significant update delivering server performance improvements of up to 400% in internal testing, a full audio overhaul for assault rifles and pistols, terrain blending improvements across all maps, and an expanded underground bunker on Sakhal for Frostline players. Bohemia has also confirmed DayZ Badlands for 2026, the game's third major expansion, which will introduce Nasdara Province — a 267 km² desert terrain described as the largest official map ever created for DayZ. For a broader view of the current state of Linux gaming across all titles and tools, the state-of-the-union article covers the wider ecosystem.

Nobara Linux is explicitly designed for gaming and based on Fedora. It ships with the required vm.max_map_count value by default, includes GE-Proton integration, and packages gaming-focused kernel patches. It is consistently recommended in dayz-ctl's community discussions, particularly for hardware that no longer receives Windows driver support.

Arch Linux adopted the increased vm.max_map_count default in its April 2024 filesystem package update. It gives you access to the Arch User Repository (AUR), and its rolling release model means you will always have the latest Mesa, Linux kernel, and DXVK available — but also means you will encounter regressions first when they hit.

Ubuntu 24.04 LTS addressed the vm.max_map_count issue as part of its gaming experience improvements. Steam on Ubuntu is available as both a native .deb package and a Snap. The Snap version has caused intermittent issues with Proton games due to its sandboxed environment — the native .deb installation from Valve's repository is generally more reliable for gaming.

Pop!_OS from System76 has had the higher vm.max_map_count value for longer than many distributions and ships with NVIDIA drivers available from first boot, making it a low-friction option for NVIDIA GPU users.

SteamOS (Steam Deck) sets the reference point for what a DayZ Linux experience looks like when all the defaults are correct. Valve's own SteamOS ships with elevated vm.max_map_count, correct BattlEye runtime configuration, and the Steam Deck-optimized Proton build. If you are playing on a Steam Deck, DayZ works out of the box for vanilla play; the dayz-ctl installation process is identical to desktop Linux.

Part Ten: Running a DayZ Server on Linux

Bohemia Interactive provides official native Linux server binaries for DayZ. The server does not run through Wine or Proton — it is a genuine Linux executable. This is one of the significant cost advantages of Linux hosting: you are running a native binary without a compatibility layer, which eliminates translation overhead and gives you full control over the server environment without requiring a Windows Server license. As with any game server on Linux, you should never run the DayZ server process as root — create a dedicated low-privilege user and run the binary under that account.

Native Server Binaries

The DayZ server binary for Linux is available via SteamCMD. Install SteamCMD, authenticate anonymously or with a Steam account, and download App ID 1042420 (the DayZ Server tool):

$ steamcmd +login anonymous +force_install_dir /opt/dayzserver +app_update 1042420 validate +quit

The server binary is DayZServer. A minimal launch command looks like this:

$ ./DayZServer -config=serverDZ.cfg -port=2302 -profiles=serverProfiles -dologs -adminlog -netlog -freezecheck

Linux vs. Windows Server Performance

Community operators consistently report that the Linux server binary is as stable as or more stable than its Windows counterpart for an equivalent hardware configuration, and the absence of Windows licensing costs makes Linux the default choice for serious server operators. The 1.29 update delivered up to 400% server-side performance improvements in internal Bohemia testing, and those gains apply equally to both platforms. CPU core count and RAM matter more than OS choice at this point. The performance dynamics are technically similar to those documented in the Arma 3 and Arma Reforger Linux vs. Windows comparison, since DayZ shares the same engine family.

The Case Sensitivity Requirement

The most operationally important Linux-specific server detail is the file system case sensitivity requirement already noted in the launcher section: the addons and keys directories inside each mod folder must be lowercase. Linux's ext4 file system enforces case sensitivity strictly. Mods packaged on Windows may have inconsistent casing. Verify all mod directories before going live and automate a lowercase check as part of your mod installation workflow. A quick scan across all installed mods:

$ find /opt/dayzserver/mods -maxdepth 2 \( -iname "Addons" -o -iname "Keys" \) ! -name "addons" ! -name "keys"

Any path returned by that command has a casing problem. Rename it to lowercase. A full server hosting walkthrough — ports, firewall rules, BattlEye configuration, mission file management, mod management, and systemd service setup — is covered in the dedicated DayZ Linux server guide.

Part Eleven: Practical Questions Players Actually Ask

Will I Get Banned for Playing DayZ on Linux?

This is the anxiety question that shadows every Linux player considering a multiplayer game with kernel-level anti-cheat. For DayZ specifically, the answer is unambiguous: no, you will not be banned for playing on Linux with a correctly configured Proton setup. BattlEye's Proton implementation is an officially sanctioned, developer-opted-in system. Bohemia Interactive chose to enable it. The client presents itself to the server as a legitimate BattlEye-authenticated player because it is one — the user-space BattlEye runtime performs the same authentication handshake regardless of whether the underlying OS is Windows or Linux.

BattlEye's ban detection operates on behavior signatures, memory scan results, and packet analysis — not on OS fingerprinting. The server has no mechanism to detect that the client is running through Wine, and BattlEye does not flag Wine or Proton as a cheat tool. The well-documented false-ban incident that affected Apex Legends in 2021 involved Easy Anti-Cheat, not BattlEye, and occurred because EAC's Linux implementation was newly deployed and had calibration issues. BattlEye's Proton implementation has been stable since 2021 and Bohemia has maintained their opt-in across every DayZ update since. There are no documented false-ban incidents specific to Linux DayZ players with a correctly installed Proton BattlEye Runtime.

Does DayZ Run Slower on Linux Than Windows?

This is a legitimate and frequently asked question that deserves a direct answer rather than deflection. The honest picture is: modest overhead exists, but it is smaller than the community's reputation suggests, and for DayZ specifically it is often imperceptible in practice.

Proton's translation layer introduces two main sources of overhead. First, DXVK's DirectX 11 to Vulkan translation adds per-draw-call processing cost that is not present when the game talks to DirectX natively on Windows. In practice, this overhead ranges from roughly 3 to 10 percent on modern hardware with current DXVK builds, down significantly from the 15 to 20 percent penalties seen with older DXVK versions before Graphics Pipeline Library support was introduced. Second, Wine's Win32 API translation adds CPU overhead on certain call patterns, particularly around thread synchronization — and this is worth understanding in detail.

Windows games are heavily multi-threaded, and threads coordinate via NT synchronization primitives: mutexes, semaphores, and events. Wine's original approach was to implement these through round-trip RPC calls to a single-threaded dedicated process called wineserver. For a game making thousands of these calls per second, the wineserver became a bottleneck that manifested as frame stutters and inconsistent frame pacing even when average FPS looked fine. Two workarounds were developed. Esync, written by Elizabeth Figura at CodeWeavers, replaced the wineserver round-trip with Linux's eventfd system call — each synchronization object got its own file descriptor, which is why some systems hit file descriptor limits with esync-heavy games. Fsync followed, using Linux futexes (futex_waitv, merged in kernel 5.16) for better throughput. Both esync and fsync reduced overhead substantially but were userspace approximations: edge cases like NtPulseEvent() and the wait-for-all mode of NtWaitForMultipleObjects() required kernel-level queue management that userspace could not correctly provide.

The definitive solution is NTSYNC, merged into the mainline Linux kernel in version 6.14 (early 2025). Developed by the same engineer (Elizabeth Figura), NTSYNC exposes a /dev/ntsync kernel device that implements Windows NT synchronization objects natively in the kernel, eliminating the wineserver bottleneck and the approximation limitations of esync/fsync simultaneously. Mainline Wine 11 (January 2026) ships with NTSYNC support and activates it automatically when a kernel 6.14+ build exposes /dev/ntsync. GE-Proton has included NTSYNC support since version 10-9, but unlike mainline Wine it does not activate automatically — you must add PROTON_USE_NTSYNC=1 to Steam's launch options, and your kernel must expose /dev/ntsync (confirmed by running ls /dev/ntsync). On some distributions you also need to load the module at boot: add ntsync to a file in /etc/modules-load.d/. Valve added the NTSYNC driver to SteamOS 3.7.20 beta with module loading enabled by default, so Steam Deck users on that branch get it without the env var. On a system running kernel 6.14 or later — Fedora 42, Ubuntu 25.04, Arch, Bazzite, and CachyOS — DayZ can benefit from the correct kernel-level implementation once the opt-in is configured. On older kernels, fsync remains the active path. The incremental gain from NTSYNC over fsync is modest for most players who already had fsync, but NTSYNC is semantically correct in ways fsync was not, and for synchronization-heavy titles the difference can be material.

AMD GPU users on Mesa often see performance that is competitive with or equal to Windows, because the open-source AMDGPU driver and Vulkan support in Mesa are mature and well-tuned. NVIDIA users running the proprietary driver see slightly more overhead, because NVIDIA's Linux driver historically lacked some of the latency optimizations present in its Windows counterpart, though the gap has narrowed significantly with recent driver releases.

The practical result for DayZ: community reports on recent hardware consistently describe stable 60+ FPS at 1440p on Extreme settings under GE-Proton with a warm shader cache. The first-launch shader compilation stutter is the most noticeable Linux-specific performance characteristic, and it disappears after the initial session. If you are chasing the last few frames of competitive performance, Windows retains a narrow advantage. If you are playing DayZ for the survival experience, the difference is not noticeable in normal play.

Does the DayZ Launcher Overlay Get Stuck on Screen?

Yes, this is a known and documented cosmetic issue specific to Linux. When you launch DayZ through Steam and the Bohemia launcher window appears before the game client loads, if you leave that launcher window open rather than closing it, a ghost outline of the launcher window can remain visible as an overlay on top of the game. The fix is simple: close the Bohemia launcher window once the game client has finished loading. The game continues running normally and the overlay disappears. dayz-ctl bypasses the launcher entirely, so this issue does not occur when using dayz-ctl to connect to servers.

Does Audio Work Correctly in DayZ on Linux?

For the overwhelming majority of players, yes. DayZ's audio under Proton is handled through Wine's PulseAudio backend. On most modern Linux distributions — Arch, Fedora, Ubuntu 22.04+, Nobara, Bazzite, and their derivatives — the PulseAudio API is implemented by pipewire-pulse, which is PipeWire's drop-in PulseAudio compatibility layer. Wine talks to the PulseAudio API, pipewire-pulse receives those calls and hands them to PipeWire, and PipeWire sends audio to your hardware. In most configurations this chain is completely transparent and DayZ's audio sounds identical to Windows.

A documented class of issue affects Proton games specifically under PipeWire: audio crackling, popping, or stuttering, particularly during moments of high CPU load or when multiple audio streams are active. The root cause is that PipeWire's default minimum quantum (its internal audio buffer size) is set very low — typically 256 samples — which suits low-latency professional audio work but produces buffer underruns under the irregular load patterns that games generate through Wine. These underruns are what you hear as crackling.

First: Confirm You Are Running PipeWire

Before applying the fix, verify that PipeWire is actually your audio server. Run:

$ pactl info | grep "Server Name"

If you see PulseAudio (on PipeWire) or similar, PipeWire is running and the fix below applies. If you see PulseAudio without the PipeWire qualifier, you are running native PulseAudio — skip to the PulseAudio path at the end of this section. If the command is not found at all, run systemctl --user status pipewire pipewire-pulse to check service state.

Then: Create the Drop-in Configuration File

The correct approach is a drop-in file inside pipewire-pulse.conf.d/ rather than editing the main pipewire-pulse.conf directly. Drop-in files survive PipeWire package updates, are easy to remove if something breaks, and do not risk corrupting the base configuration. Create the directory and the file:

$ mkdir -p ~/.config/pipewire/pipewire-pulse.conf.d/

Then create the file ~/.config/pipewire/pipewire-pulse.conf.d/gaming.conf with the following content. Use your text editor of choice — nano, vim, or any GUI editor — and make sure the file contains exactly this and nothing else:

pulse.properties = {
    pulse.min.quantum = 1024/48000
}

The value 1024/48000 means 1024 samples at 48,000 Hz — PipeWire's standard audio rate. This increases the minimum audio buffer from the default 256 samples to 1024 samples, which gives Wine enough buffer headroom to prevent underruns under game load. The trade-off is about 21ms of additional audio latency, which is completely imperceptible during gameplay.

Then: Restart PipeWire — No Reboot Needed

$ systemctl --user restart pipewire pipewire-pulse

Launch DayZ and confirm the crackling is gone. If audio has disappeared entirely after the restart, run systemctl --user status pipewire pipewire-pulse to check for errors and ensure both services are in the active (running) state.

If the Drop-in Fix Alone Is Not Enough

On some hardware and driver combinations, increasing the quantum alone does not eliminate all crackling. The secondary fix is to set the PULSE_LATENCY_MSEC environment variable in DayZ's Steam launch options, which instructs Wine to request a larger buffer from PulseAudio/PipeWire at the application level rather than relying on the system default. Add this before %command% in Steam's launch options field:

PULSE_LATENCY_MSEC=60 %command%

This tells Wine to request a 60ms PulseAudio buffer. Combined with the PipeWire quantum fix, this resolves crackling on the widest range of hardware. You can increase to 90ms if crackling persists, though values above 100ms will introduce audible delay between in-game events and the sounds they produce.

Does DayZ Support Controllers on Linux?

Yes. DayZ has native controller support in its Windows build, and Steam Input handles controller mapping transparently on Linux before the game process even sees the input. When you connect a controller — whether a DualSense, Xbox controller, or any XInput-compatible gamepad — Steam Input maps it to the XInput API that DayZ expects, and the game responds exactly as it does on Windows. No special configuration is needed.

If your controller is not being detected, confirm that Steam Input is enabled for DayZ specifically: right-click DayZ in your library, go to Properties > Controller, and ensure "Enable Steam Input" is set rather than "Disable Steam Input."

On Steam Deck, DayZ's default gamepad profile works for vanilla play with no changes required. For modded servers where inventory management and survival mechanics make a pure gamepad layout harder to work with, Steam Deck users often create a custom layout that maps select actions to the back buttons and the right trackpad for camera and inventory navigation. You can download community controller layouts directly from the Steam Input configuration screen — hold the Steam button, go to Controller Settings, and browse community layouts for DayZ. The DZGUI launcher, designed explicitly for Steam Deck, can also be used to connect to modded servers without the argument-length problems that affect the official launcher on Deck.

What Is the LD_PRELOAD Error in My Logs?

Players running DayZ on Linux through Steam frequently see messages like this in their logs or terminal output:

ERROR: ld.so: object '~/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so'
from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

This is not an error that affects DayZ or Proton. It is a benign Steam housekeeping message. Steam preloads both 32-bit and 64-bit versions of its overlay renderer library into the environment; only one ELF class will match the running process, and the dynamic linker logs a notice when the other is ignored. The Steam overlay continues to function correctly. You will see this message even when DayZ is running perfectly — it appears regardless of whether the game launches or crashes, and its presence or absence has no diagnostic value. No action is required. If you see it referenced in forum posts or older guides suggesting specific LD_PRELOAD fixes for DayZ on Linux, those threads are almost certainly addressing a different, unrelated issue. The full mechanics of LD_PRELOAD in the Steam Linux gaming context — including when it actually is relevant, the overlay tradeoff, and the lag timebomb scenario — are covered in a dedicated guide.

Does DayZ Not Support Steam Cloud Saves — and Why Does That Matter?

DayZ does not support Steam Cloud synchronization. Your character profile, keybinds, graphics settings, and server history exist exclusively in the local Wine prefix at ~/.steam/steam/steamapps/compatdata/221100/pfx/drive_c/users/steamuser/Documents/DayZ/. Steam will not back this up, and it will not migrate it when you reinstall or move to different hardware. This makes manual backup important in a way it is not for games with cloud save support. Copy that directory to external storage or a backup location before any major system change — reinstalling Linux, replacing storage, or rebuilding a Proton prefix.

The absence of cloud saves also means there is no cross-device play between a Linux desktop install and a separate Steam Deck install without manually copying the prefix data. If you want to play on both devices, copy the Documents/DayZ directory from one prefix to the equivalent location in the other after each session, or set up a sync tool like Syncthing to automate the transfer.

Does FSR Work in DayZ on Linux?

Yes. AMD FidelityFX Super Resolution (FSR) works in DayZ under GE-Proton. Community testing confirms FSR activates correctly through GE-Proton's implementation, making it a useful tool for lower-end hardware that cannot maintain target frame rates at native resolution. FSR can be enabled through DayZ's in-game video settings — it appears in the upscaling options when the game is running under a supported Proton version. No additional launch options or environment variables are needed for FSR 2.

GE-Proton 10.x also introduced support for FSR 4 via the PROTON_FSR4_UPGRADE environment variable, which automatically downloads the required AMD DLL and upgrades games that expose FSR 3.1 upscaling to use FSR 4 instead. DayZ's in-game FSR implementation does not currently expose the FSR 3.1 hook that this upgrade path requires, so for DayZ the in-game FSR 2 option remains the primary path. Monitor ProtonDB and GE-Proton release notes for changes as DayZ updates through its 1.29 cycle.

If FSR does not appear in the in-game menu, ensure you are using GE-Proton rather than stock Valve Proton, and that your GE-Proton version is current. GE-Proton's FSR integration uses AMD's reference implementation and is updated alongside DXVK and VKD3D-Proton in each release.

How Do I Update or Remove Mods Installed by dayz-ctl?

dayz-ctl handles mod lifecycle through its interactive menu. When you connect to a server using dayz-ctl, it checks the server's current mod list against the versions installed locally. If a mod has been updated on the Steam Workshop, dayz-ctl detects the version mismatch and prompts you to update before connecting. This is one of the functions the official Bohemia launcher was supposed to handle and routinely failed to perform correctly under Proton.

To update all installed mods outside of a server connection, run dayz-ctl, navigate to the mods management menu, and select the update option. To remove a specific mod, navigate to the mod management section, select the mod, and choose remove. This also cleans up the shortened directory name or symlink that dayz-ctl created during installation. Mods that dayz-ctl installs through SteamCMD also appear in your Steam Workshop subscriptions — unsubscribing there removes the source files, but dayz-ctl's internal database entry should also be cleared through the tool itself to avoid orphaned references in its mod tracking JSON.

Part Twelve: How to Set Up DayZ on Linux with Proton

Step 1: Install Steam Using the Native Package

For Ubuntu or Debian, install Steam from Valve's repository rather than the Snap store. Download the .deb package from Valve and install it with sudo dpkg -i steam.deb && sudo apt-get install -f. Then enable Steam Play for all titles under Steam > Settings > Steam Play.

Step 2: Fix vm.max_map_count Permanently

Create /etc/sysctl.d/99-gaming.conf and add the line vm.max_map_count=1048576. Then run sudo sysctl --system to apply the change immediately without rebooting. This single step resolves the loading screen crashes and mid-session freezes that defeat many players on a first attempt.

Step 3: Install the Proton BattlEye Runtime and Force GE-Proton

In the Steam Library, search for "Proton BattlEye Runtime" and install it. Then download the latest GE-Proton release from the GloriousEggroll GitHub repository. For native Steam installations, extract it to ~/.steam/steam/compatibilitytools.d/; for Flatpak Steam installations, extract it to ~/.var/app/com.valvesoftware.Steam/data/Steam/compatibilitytools.d/ instead. Restart Steam and force DayZ to use GE-Proton via Properties > Compatibility. These two steps together enable BattlEye-protected multiplayer and provide the best translation stack for DayZ's DirectX 11 rendering.

Step 4: Install dayz-ctl for Modded Servers

Run curl -sSfLA dayz-ctl https://raw.githubusercontent.com/WoozyMasta/dayz-ctl/master/install | bash to install the community launcher. Launch dayz-ctl from the terminal or the desktop shortcut to browse and connect to modded servers. dayz-ctl handles mod downloads, the -mod= argument construction, and BattlEye runtime configuration automatically — all the steps that the official Bohemia launcher fails to execute correctly under Proton.

Step 5: Clear the Shader Cache After Updates

After any DayZ patch or Proton version change, if the game shows graphical corruption or crashes on load, clear the Steam Vulkan shader pre-cache: rm -rf ~/.steam/steam/steamapps/shadercache/221100/. The cache rebuilds automatically on the next launch. Note that the old 221100.dxvk-cache file that older guides reference was removed in DXVK 2.7 and no longer exists in GE-Proton 10.x — the Steam Vulkan pre-cache directory is the correct target on current setups.

Step 6: Verify DXVK Is Active

Confirm DXVK is handling rendering — not Wine's fallback wined3d renderer — by adding DXVK_HUD=devinfo,fps %command% to Steam launch options temporarily. A small overlay in the top-left corner of the game window will show the GPU name and DXVK version string. If you see this overlay, DXVK is active and the translation stack is working correctly. Remove the environment variable from your launch options after verifying.

Part Thirteen: Troubleshooting Decision Tree

Work through the tree below before going to forums. Each branch leads to a specific, actionable fix.

Frequently Asked Questions

Why does DayZ crash or freeze at the loading screen on Linux?

The most common cause is the Linux kernel's vm.max_map_count limit, which defaults to 65,530 on many distributions. DayZ running through Wine/Proton creates far more virtual memory areas than this limit allows. Fix it permanently by adding vm.max_map_count=1048576 to /etc/sysctl.d/99-gaming.conf and running sudo sysctl --system.

Does BattlEye anti-cheat work on Linux with Proton?

Yes. Since December 2021, Valve and BattlEye collaborated on a Proton-compatible implementation. Bohemia Interactive opted in for DayZ, meaning BattlEye-enabled servers are fully accessible to Linux players. You must install the Proton BattlEye Runtime from the Steam Library tools section for it to function correctly.

How do I play on modded DayZ servers on Linux?

The official Bohemia launcher fails under Proton and cannot correctly install mods or pass launch parameters to the game client. The community-built dayz-ctl tool, written in Bash by WoozyMasta, replaces the launcher entirely. It queries server mod lists, downloads mods, constructs the -mod= launch argument, and passes it directly to the DayZ client through Proton. Install it with: curl -sSfLA dayz-ctl https://raw.githubusercontent.com/WoozyMasta/dayz-ctl/master/install | bash

Should I use stock Proton or GE-Proton for DayZ?

The community consistently recommends GE-Proton (maintained by GloriousEggroll) for DayZ. GE-Proton ships the latest DXVK and VKD3D-Proton releases faster than Valve's stable builds, includes media codecs Valve omits for licensing reasons, and applies game-specific patches earlier. Download the latest release from the GloriousEggroll GitHub repository and extract it to ~/.steam/steam/compatibilitytools.d/.

How do I fix DayZ graphical corruption or crashes after a patch on Linux?

Post-update graphical corruption or crashes are caused by stale shader pipeline state. On current GE-Proton 10.x and Valve Proton (which include DXVK 2.7+), the old 221100.dxvk-cache file no longer exists — it was removed when the legacy DXVK state cache was dropped in July 2025. The correct fix now is to clear Steam's Vulkan shader pre-cache: rm -rf ~/.steam/steam/steamapps/shadercache/221100/. Both the GPU driver cache and Steam's pre-cache rebuild automatically on the next launch, with some initial shader compilation stutter on first load.

Where is my DayZ profile data stored on Linux?

DayZ profile data — keybinds, character name, server history, and local configuration — is stored inside the Proton Wine prefix at ~/.steam/steam/steamapps/compatdata/221100/pfx/drive_c/users/steamuser/Documents/DayZ/. Copy this directory before reinstalling Linux or migrating to new hardware to preserve your settings without requiring a full reconfiguration.

Will I get banned for playing DayZ on Linux?

No. BattlEye's Proton implementation is an officially sanctioned system that Bohemia Interactive chose to opt into and has maintained across every DayZ update since December 2021. BattlEye does not flag Wine or Proton as a cheat tool — it detects behavioral signatures, memory patterns, and packet anomalies, none of which are produced by a clean Proton installation. There are no documented false-ban incidents tied specifically to Linux players with a correctly installed Proton BattlEye Runtime.

Does DayZ run slower on Linux than on Windows?

A modest overhead exists — roughly 3 to 10 percent on modern hardware — from DXVK's DirectX 11 to Vulkan translation. In practice, this is imperceptible for the survival gameplay DayZ offers. Community reports consistently describe stable 60+ FPS at 1440p Extreme settings under GE-Proton with a warm shader cache. The most noticeable Linux-specific behavior is first-launch shader compilation stutter, which does not recur after the cache is built. AMD GPU users on Mesa often see performance competitive with Windows. NVIDIA users may see slightly more overhead but the gap has narrowed significantly with recent proprietary driver releases.

Does audio work correctly in DayZ on Linux?

For most players, yes. If you experience crackling or popping, first confirm PipeWire is your audio server with pactl info | grep "Server Name". If it is, create ~/.config/pipewire/pipewire-pulse.conf.d/gaming.conf containing pulse.properties = { pulse.min.quantum = 1024/48000 }, then run systemctl --user restart pipewire pipewire-pulse. If crackling persists, also add PULSE_LATENCY_MSEC=60 %command% to Steam's launch options for DayZ. On systems running native PulseAudio rather than PipeWire, the PULSE_LATENCY_MSEC Steam launch option is the primary fix. The full step-by-step procedure with all variants is in the Practical Questions section above.

Does FSR work in DayZ on Linux?

Yes. FidelityFX Super Resolution (FSR 2) works in DayZ under GE-Proton and appears in DayZ's in-game video settings under the upscaling options. No additional launch options or environment variables are required. GE-Proton 10.x also supports FSR 4 via PROTON_FSR4_UPGRADE, but DayZ's current in-game implementation does not yet expose the FSR 3.1 hook that upgrade path requires, so FSR 2 in-game remains the active path for DayZ. If FSR does not appear in the menu, ensure you are using a current GE-Proton release rather than stock Valve Proton.

Does DayZ support Steam Cloud saves on Linux?

No — DayZ does not support Steam Cloud synchronization on any platform. All profile data is stored locally in the Wine prefix at ~/.steam/steam/steamapps/compatdata/221100/pfx/drive_c/users/steamuser/Documents/DayZ/. Steam will not back this up. Copy that directory manually before any major system change to avoid losing your keybindings, settings, and server history.

Will DayZ Badlands work on Linux?

DayZ Badlands is a major expansion confirmed for 2026, introducing the Nasdara Province terrain and new gameplay systems. As an expansion built on the same DayZ client, it will run through the same Proton stack with no additional Linux-specific configuration expected. Monitor ProtonDB reports after release for any compatibility findings specific to the expansion content.

What is the alternative to dayz-ctl for players who prefer a GUI?

DZGUI (github.com/aclist/dztui), maintained by developer aclist and updated in January 2026, is the established graphical alternative. It provides a Zenity-based GUI for browsing and connecting to modded DayZ servers on both Linux desktop and Steam Deck, solving the same broken-launcher problem as dayz-ctl but with a point-and-click interface. It requires a Steam Web API key to query server data. The older dayz-linux-cli-launcher by bastimeyer (github.com/bastimeyer/dayz-linux-cli-launcher) is also referenced in many archived guides and is the project that directly inspired dayz-ctl; if you encounter references to it, dayz-ctl is its active successor.

What does the LD_PRELOAD error in my Steam logs mean?

The ERROR: ld.so: object '...gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class) message is a benign Steam housekeeping notice, not an error affecting DayZ. Steam preloads both 32-bit and 64-bit versions of its overlay renderer; the dynamic linker logs a notice when one ELF class does not match the running process. The overlay continues to function correctly. This message appears regardless of whether DayZ is running perfectly or crashing, and its presence or absence has no diagnostic value. No action is required.

Can I run a DayZ server on Linux?

Yes. Bohemia Interactive provides official native Linux server binaries (Steam App ID 1042420) that run without Wine or Proton. Download via SteamCMD, launch with ./DayZServer -config=serverDZ.cfg -port=2302 -profiles=serverProfiles -dologs -adminlog -netlog -freezecheck, and never run the process as root — create a dedicated low-privilege user. The critical Linux-specific requirement is that all mod addons and keys directories must be lowercase, as Linux file systems enforce case sensitivity strictly. Community operators consistently report Linux server performance equivalent to Windows for equivalent hardware.

Sources and References

Technical details in this guide are drawn from official documentation, community-maintained repositories, and verified sources.

• GamingOnLinux -- independent Linux gaming journalism; DayZ Proton testing, GE-Proton 10.x release coverage 2025–2026
• Phoronix -- Arch Linux vm.max_map_count increase announcement, April 2024
• WoozyMasta/dayz-ctl GitHub -- dayz-ctl source code, README, and documentation; current release v0.2.0
• aclist/dztui (DZGUI) GitHub -- DZGUI graphical server browser and launcher for DayZ on Linux and Steam Deck; documentation updated January 2026
• bastimeyer/dayz-linux-cli-launcher GitHub -- the original CLI launcher project that inspired dayz-ctl; referenced widely in archived guides
• Steamworks Development -- official BattlEye Proton integration announcement, December 3, 2021
• ValveSoftware/steam-for-linux Issue #10542 -- Proton 9.0 DayZ regression documentation
• Red Hat Customer Portal -- kernel vm.max_map_count documentation
• 9to5Linux -- VKD3D-Proton 3.0 coverage, November 2025
• Ubuntu Launchpad Bug #2057792 -- vm.max_map_count gaming impact tracker
• ProtonDB -- community compatibility reports for DayZ (App ID 221100)
• BattlEye Wikipedia -- anti-cheat technical overview and history
• DayZ 1.29 Stable Update -- official Bohemia Interactive release announcement, April 8, 2026
• Proton 10.0-3 Release Notes -- Valve/CodeWeavers changelog, November 2025; includes DayZ mod tooling fix
• DayZ Badlands Steam page -- official expansion listing; Nasdara Province, 267 km², 2026 release
• DXVK 2.7 Release Notes -- July 2025; documents removal of the legacy state cache format
• GamingOnLinux — NTSYNC kernel 6.14 -- coverage of the NTSYNC driver merge; Wine 11 / kernel 6.14 thread synchronization architecture
• Bohemia Interactive Community Wiki — PBO File Format -- official documentation; PBO = Packed Bank of files, file structure, SHA key signatures
• DayZ Modding Basics -- official Bohemia documentation; Linux server binary requirement for lowercase addons/keys folder names