Gaming

Linux is considered an "unofficial" gaming platform; the support and target audience provided to it is not a primary priority for most gaming organizations. This has seen some change starting from 2021 onward, as big players like Valve, the CodeWeavers group and the community have made tremendous changes over the past few months, allowing Linux to truly become a viable platform for gaming. Further, more and more indie development teams strive to use cross-platform rendering engines in order to have their game able to compile and run on Linux.

Related articles

When it comes to gaming, the majority of user's thoughts are often directed towards popular AAA games which are usually written for the Microsoft Windows platform. This is understandable, however, it is not the only and sole availability. Please refer to #Game environments and #Getting games further down the page where you can find software to run games from other platforms.

If you however are fixated on getting games written for Microsoft Windows to work on Linux, then a different mindset, tools and approach is required; understanding internals and providing functional substitution. Please read #Game technicality below.

Game technicality

There are ultimately two major problems that arise from attempting to play AAA games on Linux. They are:

  • Graphics SDK
    • Games written and compiled for an API that Linux does not recognize (such as DirectX).
  • Graphics Hardware
    • Drivers necessary to handle game rendering. (such as Nvidia Drivers)

From these problems, further two complications arise, in particular:

  • General Library Dependencies
    • Libraries necessary for doing general purpose operations during gameplay, such as saving ingame, loading config. (e.g Microsoft Visual C++, MFC, .NET)
  • Incompatible Interfaces
    • Aside from the frameworks mentioned above, there is a further problem with binary formats and compiled code generated by Windows which Linux does not recognize.
    • Lastly, lacking the appropriate driver to do the rendering results in a horseless cart situation.

The APIs above forward their graphical calls to the underlying driver which then proceeds to talking to the GPU hardware. AMD users fortunately have opensource drivers released by AMD itself. This is already a huge issue resolved. Nvidia users have to rely on other alternatives, which often comes packed as blobs. (microcode and firmware being fed through, as a result of Nvidia driver reverse engineering)

A huge amount of games use DirectX as their main driving SDK. Linux, natively supports only OpenGL and Vulkan. Linux by itself does not support DirectX or any of the aforementioned technologies (Visual C++, MFC, .NET).

Instead, several opensource equivalents have been written which attempt to provide identical functionality, ultimately achieving the same result from a graphics point of view. These equivalents have their "own" written substitutes which attempt to "re-invent" what the original SDK calls would possibly achieve from a black box point of view. Popular ones include:

  • Wine (Wine is Not Emulator) [provides a "loader vm", self written dependencies, interop and more]
  • Proton (forked Wine project, optimized for Steam by Valve)
  • Mono (.NET alternative)
  • MF-Media (media foundation dependencies)

For example, a call to load, transform and shade vertices on DirectX may be re-written from scratch in a new .dll/.so owned by Wine, providing their own "hypothetical" belief on what the function may be doing underneath, and forward it instead to an OpenGL alternative, effectively trying to achieve similar results. Since these calls are direct equivalents and treated "as if" DirectX was running, performance is not impacted. (with the exception of the starting overhead to interop with these)

These tools are often brought in the distribution together on the system at the same time. A prefix (Wine's terminology for a directory mimicking a Windows sandbox) is created and configured. Dependencies are installed inside the prefix (the "sandbox" still needs the game's redistributables), often with winetricks, followed by an attempt to run the game "as if" it was executed from Windows.

This, nowadays, fortunately works for most games (aside from anticheat protected ones, which require a kernel driver that Wine/Proton does not yet have). If a game does not work, it is usually as a result of incompatible packages, missing dependencies or unimplemented functionality by Wine/Proton.

If you are to run Wine/Proton, please make sure you use versions past 5.x as this is where most of the recent patches have been made into.

Lutris is a piece of software that provides runners and sandboxes that handle dependencies for you when you install games, if the above process is found tedious and/or complicated.

Common game dependencies

In order to gain a more in-depth understanding of what you will intend to do if you decide to go the Wine/Proton route, it is worthwhile to cover the common dependencies that games require in order to execute. Architecture also needs to be considered in mind, whether x86 or x64, preferably both.

A prefix would need to have the following populated into it in order to run most Windows games.

Mandatory (for high coverage)
  • Microsoft Core Fonts
  • Microsoft Visual C++ 2015 (2017 has the most coverage, recommended) [2005, 2008, 2010, 2012, 2013, 2015, 2017-2018, 2019]
  • DirectX 9.0 (11.0 has the most coverage, recommended) [June SDK update 2010] {which consists of, to name a few:}
    • Direct3D
    • Direct2D
    • DirectShow
    • DirectInput
    • DirectPlay
    • DirectSound
    • DXGI
    • XAudio2
  • .NET Framework (3.5 has most coverage)
  • OpenGL
    • OpenAL
    • OpenAI
    • OpenCL
  • Vulkan

Optional (but still common)
  • XNA
  • PhysX
  • Media Foundation
  • Quicktime
  • Adobe Reader 11
  • Java SRE (e.g Minecraft)

Rare (less common)
  • Gamespy
  • MIDI driver
  • ACDSee

Machine requirements

It is not enough to just populate a prefix with the dependencies the game will need. The kernel itself has to have the substitution it will provide to the calls the game will make. As already mentioned, drivers and alternatives are available.

Drivers

Dependency for the machine & substitutes

This is mostly informative. Some of these packages install themselves once you install the major ones.

Game environments

Wine/Proton are not the only approaches to play games. Different environments exist to play games in Linux, and have just as many (or more) games than on Windows:

  • Native – games which have builds targeting the Linux platform, shipping with OpenGL and/or Vulkan graphics API support.
  • Emulators – required for running software designed for other architectures and systems. Most games run out of the box once the ROM is fed in to the emulator and issues are rarely encountered. For options, see Video game platform emulators.
  • Java - write once, run everywhere platform. Examples of popular games that run on Linux are Minecraft, Runescape, Wurm Online, Puzzle Pirates.
  • Web – games running in a web browser.
    • HTML5 games use canvas and WebGL technologies and work in all modern browsers.
    • Flash-based – you need to install the plugin to play.
  • Wine – Windows compatibility layer, allows to run Windows applications (and a lot of games) on Unix-like operating systems. Supports DirectX to Vulkan translation in runtime with the addition of Wine#DXVK, which improves performance in games which only support DirectX.
  • Virtual machines – can be used to install compatible operating systems (such as Windows). VirtualBox has good 3D support. As an extension of this, if you have compatible hardware you can consider VGA passthrough to a Windows KVM guest, keyword is "virtual function I/O" (VFIO), or PCI passthrough via OVMF.
  • Proton/DXVK – Fork of Wine designed for use in the proprietary steam platform, enabling better support for games than Wine. See Steam#Proton Steam-Play for more information.

Getting games

Just because games are available for Linux does not mean that they are native; they might be pre-packaged with Wine or DOSBox.

For list of games packaged for Arch in official repositories / the AUR see List of games.

  • Athenaeum — A libre replacement to Steam.
https://gitlab.com/librebob/athenaeum || athenaeum-gitAUR
  • Play.it — Automates the build of native packages. Also supports Wine, DOSBox and ScummVM games.
https://www.dotslashplay.it/ || play.itAUR

    Configuring games

    Certain games or game types may need special configuration to run or to run as expected. For the most part, games will work right out of the box in Arch Linux with possibly better performance than on other distributions due to compile time optimizations. However, some special setups may require a bit of configuration or scripting to make games run as smoothly as desired.

    Multi-screen setups

    Running a multi-screen setup may lead to problems with fullscreen games. In such a case, running a second X server is one possible solution. Another solution may be found in the NVIDIA article (may also apply to non-NVIDIA users).

    Keyboard grabbing

    Many games grab the keyboard, noticeably preventing you from switching windows (also known as alt-tabbing).

    Some SDL games (e.g. Guacamelee) let you disable grabbing by pressing .

    Starting games in a separate X server

    In some cases like those mentioned above, it may be necessary or desired to run a second X server. Running a second X server has multiple advantages such as better performance, the ability to "tab" out of your game by using /, no crashing your primary X session (which may have open work on) in case a game conflicts with the graphics driver. The new X server will be akin a remote access login for the ALSA, so your user need to be part of the group to be able to hear any sound.

    To start a second X server (using the free first person shooter game Xonotic as an example) you can simply do: 

    $ xinit /usr/bin/xonotic-glx -- :1 vt$XDG_VTNR

    This can further be spiced up by using a separate X configuration file:

    $ xinit /usr/bin/xonotic-glx -- :1 -xf86config xorg-game.conf vt$XDG_VTNR

    A good reason to provide an alternative xorg.conf here may be that your primary configuration makes use of NVIDIA's Twinview which would render your 3D games like Xonotic in the middle of your multiscreen setup, spanned across all screens. This is undesirable, thus starting a second X with an alternative configuration where the second screen is disabled is advised. Please note, that the X configuration file location is relative to the directory.

    A game starting script making use of Openbox for your home directory or may look like this:

    After making it executable you would be able to do:

    $ ~/game.sh xonotic-glx
    Note: If you want to avoid loading configs from /etc/X11/xorg.conf.d, you should also use the -configdir option, pointing to an empty directory.

    Adjusting mouse detections

    For games that require exceptional amount of mouse skill, adjusting the mouse polling rate can help improve accuracy.

    Binaural audio with OpenAL

    For games using OpenAL, if you use headphones you may get much better positional audio using OpenAL's HRTF filters. To enable, run the following command:

    echo "hrtf = true" >> ~/.alsoftrc

    Alternatively, install openal-hrtfAUR from the AUR, and edit the options in /etc/openal/alsoftrc.conf

    For Source games, the ingame setting `dsp_slow_cpu` must be set to `1` to enable HRTF, otherwise the game will enable its own processing instead. You will also either need to set up Steam to use native runtime, or link its copy of openal.so to your own local copy. For completeness, also use the following options:

    dsp_slow_cpu 1 # Disable in-game spatialiazation
snd_spatialize_roundrobin 1 # Disable spatialization 1.0*100% of sounds
dsp_enhance_stereo 0 # Disable DSP sound effects. You may want to leave this on, if you find it does not interfere with your perception of the sound effects.
snd_pitchquality 1 # Use high quality sounds

    Tuning PulseAudio

    If you are using PulseAudio, you may wish to tweak some default settings to make sure it is running optimally.

    Enabling realtime priority and negative nice level

    Pulseaudio is built to be run with realtime priority, being an audio daemon. However, because of security risks of it locking up the system, it is scheduled as a regular thread by default. To adjust this, first make sure you are in the group. Then, uncomment and edit the following lines in :

    and restart pulseaudio.

    Using higher quality remixing for better sound

    PulseAudio on Arch uses speex-float-1 by default to remix channels, which is considered a 'medium-low' quality remixing. If your system can handle the extra load, you may benefit from setting it to one of the following instead:

    resample-method = speex-float-10

    Matching hardware buffers to Pulse's buffering

    Matching the buffers can reduce stuttering and increase performance marginally. See here for more details.

    Double check your CPU frequency scaling settings

    If your system is currently configured to properly insert its own cpu frequency scaling driver, the system sets the default governor to Ondemand. By default, this governor only adjusts the clock if the system is utilizing 95% of its CPU, and then only for a very short period of time. This saves power and reduces heat, but has a noticeable impact on performance. You can instead only have the system downclock when it is idle, by tuning the system governor. To do so, see Cpufrequtils#Tuning the ondemand governor. Recent Intel CPU (SandyBridge +) use frequency scaling driver `intel_pstate` that does not work with ondemand governor. You can switch from "powersave" (default) to "performance", but the difference is minimal.

    Remote gaming

    Cloud gaming has gained a lot of popularity in the last few years, because of low client-side hardware requirements. The only important thing is stable internet connection (over the ethernet cable or 5 GHz WiFi recommended) with a minimum speed of 5–10 Mbit/s (depending on the video quality and framerate).

    See Gamepad#Gamepad over network for using a gamepad over a network with services that do not normally support this.

    Service Installer In browser client Use your own host Offers host renting Full desktop support Controller support Remarks
    Dixper???
    ReemoYou can also install the software with the official installation script in the download section via their website.
    Xbox Cloudxbox-cloud-gamingAURYou need Game Pass Ultimate to be able to use XCloud.
    GeForce NowYou must have games on Steam, Epic Client or GOG to use this service. Not all games are available.
    MoonlightThis is only a client. Host machine must use either GeForce Experience (windows only) or Sunshine (multiplatform).
    Parsec (experimental)Cloud hosting no longer available
    VDI Stream Clientvdi-stream-clientAURVDI client with 3D GPU acceleration and built-in USB redirection
    Playkey?????
    PlayStation NowRuns under Wine or Steam's protonPlay PS4, PS3 and PS2 games on PC. Alternatively, you can use emulators.
    PlayStation Remote PlayPlay games from your PS4 and/or PS5 on PC.
    RainwayComing in 2019 Q3?
    ShadowStable:
    Beta:     		Controller support is dependent on USB over IP, and currently AVC only as HEVC is not supported
    Steam Remote PlayPart of
    Stadia
    Vortex?
    VNCtigervnc or General purpose remote desktop protocol, but the latency should be low enough to use it for gaming over a LAN. See Gamepad#Gamepad over network for gamepad support.
    xrdpAnother general purpose remote desktop protocol, has both OpenGL and Vulkan support after configuring graphical accleration. Recommended for gaming over a LAN. See Gamepad#Gamepad over network for gamepad support.
    X11 forwardingX forwarding over SSH with VirtualGL supports OpenGL and works for some but not all games. See Gamepad#Gamepad over network for gamepad support.

    Improving performance

    See also main article: Improving performance. For Wine programs, see Wine#Performance. For a good gaming experience low latency, a consistent response time (no jitter) and enough throughput (frames per second) are needed. If you have multiple sources with a little jitter they are likely to overlap sometimes and produce noticeable stutter. Therefore most of the time it is preferable to decrease the throughput a little to gain more response time consistency.

    Improve clock_gettime throughput

    User space programs and especially games do many calls to clock_gettime(2) to get the current time for calculating game physics, fps and so on. The time usage can be seen by running 

    # perf top

    and looking at the overhead of read_hpet (or acpi_pm_read).

    If you are not dependent on a very precise timer you can switch from hpet (high precision event timer) or acpi_pm (ACPI Power Management Timer) to the faster TSC (time stamp counter) timer. Add the kernel parameters

    tsc=reliable clocksource=tsc

    to make TSC available and enable it. After that reboot and confirm the clocksource by running 

    # cat /sys/devices/system/clocksource/clocksource*/current_clocksource

    You can see all currently available timers by running

    # cat /sys/devices/system/clocksource/clocksource*/available_clocksource

    and change between them by echoing one into current_clocksource. On a Zen 3 system benchmarking with shows a ~50 times higher throughput of compared to or .

    Tweaking kernel parameters for response time consistency

    You can install the realtime kernel to get very good response time consistency out of the box at the price of quite some CPU throughput loss. Additionally the realtime kernel is not compatible with and does not change the scheduler for SCHED_NORMAL (also named SCHED_OTHER) processes, which is the default process scheduling type. The following kernel parameter changes improve the response time consistency for the realtime kernel even further, as well as other kernels such as the default linux kernel:

    Disable proactive compaction because it introduces jitter according to kernel documentation:

    # echo 0 > /proc/sys/vm/compaction_proactiveness

    If you have enough free RAM increase the number of minimum free Kilobytes to avoid stalls on memory allocations: . Do not set this below 1024 KB or above 5% of your systems memory. Reserving 1GB:

    # echo 1048576 > /proc/sys/vm/min_free_kbytes

    Avoid swapping (locking pages that introduces latency and uses disk IO) unless the system has no more free memory:

    # echo 10 > /proc/sys/vm/swappiness

    Disable zone reclaim (locking and moving memory pages that introduces latency spikes):

    # echo 0 > /proc/sys/vm/zone_reclaim_mode

    Disable Transparent Hugepages (THP). Even if defragmentation is disabled, THPs might introduce latency spikes.

    Note that if your game uses TCMalloc (e.g., Dota 2 and CS:GO) then it is not recommended to disable THP as it comes with a large performance cost.

    Reduce the maximum page lock acquisition latency while retaining adequate throughput :

    # echo 1 > /proc/sys/vm/page_lock_unfairness

    Tweak the scheduler settings. The following scheduler settings are in conflict with cfs-zen-tweaksAUR so for each setting choose only one provider. By default the linux kernel scheduler is optimized for throughput and not latency. The following hand-made settings change that and are tested with different games to be a noticeable improvement. They might not be optimal for your use case; consider modifying them as necessary :

    Make the changes permanent

    Usually, the advice for permanently setting kernel parameters is to configure create a sysctl configuration file or change your boot loader options. However, since our change span both procfs (, containing sysctl) and sysfs (), the most convenient way is to use systemd-tmpfiles:

    After that reboot and see if the values applied correctly.

    Load shared objects immediately for better first time latency

    Set the environment variable

    LD_BIND_NOW=1

    for your games, to avoid needing to load program code at run time (see ), leading to a delay the first time a function is called. Do not set this for startplasma-x11 or other programs that link in libraries that do not actually exist on the system anymore and are never called by the program. If this is the case, the program fails on startup trying to link a nonexistent shared object, making this issue easily identifiable. Most games should start fine with this setting enabled.

    Gamemode

    Gamemode is a Daemon/lib combo for Linux that allows games to request a set of optimisations be temporarily applied to the host OS. This can improve game performance.

    ACO compiler
    Note: The method shown below only works on AMD GPUs running the AMDGPU drivers.

    See AMDGPU#ACO compiler

    fsync patch

    See Steam#fsync patch.

    Reducing DRI latency

    Direct Rendering Infrastructure (DRI) Configuration Files apply for all DRI drivers including Mesa and Nouveau. You can change the DRI configuration systemwide in or per user in . If they do not exist, you have to create them first. Both files use the same syntax; documentation for these options can be found at https://dri.freedesktop.org/wiki/ConfigurationOptions/. To reduce input latency by disabling synchronization to vblank, add the following:

    <driconf>
   <device>
       <application name="Default">
           <option name="vblank_mode" value="0" />
       </application>
   </device>
</driconf>

    Improving frame rates and responsiveness with scheduling policies

    Most games can benefit if given the correct scheduling policies for the kernel to prioritize the task. These policies should ideally be set per-thread by the application itself.

    For programs which do not implement scheduling policies on their own, application known as , and its associated daemon schedtooldAUR can handle many of these tasks automatically.

    To edit what programs relieve what policies, simply edit and add the program followed by the schedtool arguments desired.

    Policies

     
    (only implemented in BFS/MuQSSPDS schedulers found in -pf and -ck kernels) – will not only allow the process to use a maximum of 80 percent of the CPU, but will attempt to reduce latency and stuttering wherever possible. Most if not all games will benefit from this:
    bit.trip.runner -I
    provides an alternative, that can even work better. You should test to see if your applications run more smoothly with , in which case by all means use it instead. Be warned though, as  runs the risk of starving the system! Use this in cases where -I is used below:
    bit.trip.runner -F -p 15

    Nice levels

    Secondly, the nice level sets which tasks are processed first, in ascending order. A nice level of -4 is recommended for most multimedia tasks, including games:

    bit.trip.runner -n -4

    Core affinity

    There is some confusion in development as to whether the driver should be multithreading, or the program. Allowing both the driver and program to simultaneously multithread can result in significant performance reductions, such as framerate loss and increased risk of crashes. Examples of this include a number of modern games, and any Wine program which is running with GLSL enabled. To select a single core and allow only the driver to handle this process, simply use the flag, where # is the core number, e.g.:

    bit.trip.runner -a 0x1

    uses first core.

    Some CPUs are hyperthreaded and have only 2 or 4 cores but show up as 4 or 8, and are best accounted for:

    bit.trip.runner -a 0x5

    which use virtual cores 0101, or 1 and 3.

    General case

    For most games which require high framerates and low latency, usage of all of these flags seems to work best. Affinity should be checked per-program, however, as most native games can understand the correct usage. For a general case:

    bit.trip.runner -I -n -4
Amnesia.bin64 -I -n -4
hl2.exe -I -n -4 -a 0x1 #Wine with GLSL enabled

    etc.

    Optimus, and other helping programs

    As a general rule, any other process which the game requires to operate should be reniced to a level above that of the game itself. Strangely, Wine has a problem known as reverse scheduling, it can often have benefits when the more important processes are set to a higher nice level. Wineserver also seems unconditionally to benefit from , since it rarely consumes the whole CPU and needs higher prioritization when possible.

    optirun -I -n -5
wineserver -F -p 20 -n 19
steam.exe -I -n -5

    Peripherals

    Mouse

    You might want to set your mouse acceleration to control your mouse more accurately.

    If your mouse have more than 3 buttons, you might want to see Mouse buttons.

    If you are using a gaming mouse (especially Logitech and Steelseries), you may want configure your mouse such as DPI, LED... using . See this page for a full list of supported devices. Or solaar for logitech devices only

    LEDs

    You can change the motherboard and ram lighting with

    gollark: *so vampires are just a convoluted mechanic for abandoning eggs early?*
    gollark: *what*
    gollark: Blued and plorange.
    gollark: 📵 🚱 🚱 🚯 🚷
    gollark: THE FISH OF SUNS¡

    See also
    • - Forum on reddit.com with gaming on linux as its topic, subpages: Wiki, FAQ.
    • Linux Gaming Guide - Compilation of different techniques for optimizing the Linux gaming experience.
    This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.