BoxG.lv

Info

If your game is not working, then check the posts below.

As a first step, check the logs using the Terminal:

Game is crashing as soon as I start it

There can be some incompatibilities with your Linux distribution, hardware and Lutris version.
Before debugging your issue further, it is worth to simply try using a different Wine version.
In Lutris this can be done very easily:
1) Open Lutris

2) Right-click on your game

3) Press "Configure"

4) Open "Runner options"

5) Chnage the "Wine version"

6) You will need to trial-and-error until you find a version that works for your system. Start with "GE-Porton-*", then try "wine-ge-*" and so on.

7) Press "Save"

8) Press "Play"

9) If your game crashes, try using a different WIne version.

Note: Some Wine versions will work when launched from Lutris, but will not work if lounched through Steam, this is especially noticable when using a Steam Deck.

My game is crashing on my PC with X GPU, but works on my PC with Y GPU

By default Lutris requires a somewhat modern GPU that properly supports Vulkan. The suport for Vulkan is quite old, it exists in GPUs starting from AMD Radeon HD 7000 series or Nvidia Geforce 600 series (with exceptions). It is also possible that Vulkan support in your Linux distribution and with your GPU drivers is broken.
You should try disabling "DXVK" and check if the game is working now.

1) Open Lutris

2) Right click on your game

3) Press "Confgiure"

4) Open "Runner Options" tab

5) Disable "DXVK" and disable "Enable DXVK-NVAPI / DLSS"
Note: If this helps, then it is very likely you have a driver issue, check others posts for a proper fix.

6) Press "Save"

7) Try playing your game

It is possible that some other incompatibilities exists with your system, but from here you should try multiple options and see if any of these help.
- Try disabling "Enable VKD3D"
- Try disabling "Enable D3D Extras"
- Try disabling "Enable Esync"
- Try disabling "Enable Fsync"

It is possible that combination of these settings are causing incompatibilities. It is recommended to disable all of them and turn on one-by-one until you find which setting is causing the issue.

Steam Deck buttons are not working
Note: This can also apply to game controllers too.

When running your game through Lutris, you are using your system's drivers to map your controler's buttons to proper inputs. Steam uses their own solution and has done a great job making sure many different types of controllers are working.
The solution is to simply run your game through Steam.

1) Open Lutris

2) Right click on your game

3) Press "Create a Steam shortcut"

4) You might need to restart your Steam client (or your device)

5) Open Steam

6) Your game should now be visible in Steam

7) Launcher your game

8) Your controller's buttons should be working now

Note: Your game might be crashing due to incompatible Wine version. Check this topic how to fix this.

Game was working on X Linux, but does not work on Y Linux

Most modern Linux distributions allow you to install Lutris in two ways:
a) using the system package manager (.rpm, .deb or other)
b) using a Flatpak image

You might have installed Lutris using the first or the second option. Try uninstalling Lutris and installing it using the other method.

If changing from system package to Flatpak (or vice versa) did not help, then you can try the following:
1) Open Lutris

2) Right click on your game

3) Press "Configure"

4) Open the "System options" tab

5) Disable (or enable) "Prefer system libraries"

6) Press "Save"

7) Play the game and check if it is working now

Lutris open.mp installer script does not work

During installation you may experience issues, especially during the .NET installation or Webview2 installation phase.

1) Make sure you did set "wine-ge-*" as Wine version globally. This can be done in Preferences>Runners>Wine>Runner options>Wine version.

2) Try disabling (or enabling) "Prefer system libraries" under Preferences>Runners>Wine>System options.

Game works if I disable DXVK

This usually is an idicator that you have driver issues, specifically missing GPU drivers.

First you should make sure that you have properly installed GPU drivers for your GPU and your selected Linux distribution.
For AMD GPUs:
- everything should be working, "amdgpu" drivers are usually added with the Linux kernel

For Intel GPUs:
- For most cases "i915" driver should be already added with the Linux kernel
- If you are willing to experiment to get a little more performance and have a recent Intel CPU on GPU, then you can try enable "Xe drivers", but this process might not be as easy. The process involves adding a "force probe" to your GRUB command line and can easily break your system if not done properly. Search for guides for your selected Linux distribution.

For Nvidia GPUs:
- Fedora Workstation
- Ubuntu

Note: You may need additional drivers if you are using Flatpak.

DXVK does not work in Flatpak

You most likely need the drivers to be available inside Flatpak, this can be done by installing the correct Flatpak image for your GPU. Run one of the commands in the Terminal.

For AMD and Intel GPUs: For Nvidia GPUs:
1) Find your current Nvidia driver's version: 2) Install the same version Nvidia runtime image, for example: Note: You will need to close Lutris after installing any of these images.

Picking the "right" wine runner

This is more for advanced users that want to understand what kind of difference is it going to make when using a different Wine version.
If you are using an up-to-date Wine or any of its forks, you should NOT see any difference in open.mp, the installation process is a different story as af 2026 (might be fixed in the future), but other games might see some differences.
Below you can find explanation of each Wine version (fork), why it exists and what it solves.

Wine:
The original runner, it is mainly used to run various Windows applications, but the "vanilla" Wine is not often used for gaming. While other Wine versions are more commonly used for gaming, it is mostly because of the "patches" that are provided with other versions of Wine. These patches are usually special flags and workarounds that are automatically enabled when running a specific game. The "vanilla" Wine should be viewed as a foundation and you need a lot of manual work to get your games working. Note that these patches are more of a list of recommended settings for a specific game rather than a global issue. Many will notice that in "vanilla" Wine cutscenes and movies don't work, this is because "vanilla" Wine does not include proper support for Microsoft Media and various codecs. "Vanilla" Wine goal is to get Windows apps working on Linux, but multimedia is not their goal. Other Wine versions step in to fix this.

Proton:
Valve (Steam) developed a tool that packages Wine in a container, added various patches and fixes and added Steam features on top of it, especially Steam runtime. As a result, Proton is one of the most reliable Wine versions for gaming on Linux. Importantly for performance, Wine does not provide DXVK and DXVK-NVAPI by default, which is highly recommended for demanding games since Vulkan can provide significant hardware level boost when GPU and Linux support it. Proton also includes many fixes for various games, which you would need to apply manually if you had used "vanilla" Wine. The major drawback with Proton is that it requires Steam (or parts of it), which makes it a less than desirable option for those, who don't use Steam. There are multiple versions of Proton indicated by a number such as Proton-8, Proton-9, Proton-10, these versions are not based on "wine-8", "wine-9" or "wine-10", rather Valve relases a new Proton version as a "patch set", which does include backported fixes from a newer Wine version, but it can also simply be with a set of patches currated by Valve. Proton does include multimedia related fixes, which makes cutscenes and movies work in games. You can manually apply patches to a game using a tool called "protontricks".

Proton-GE:
A dedeveloper called "GloriousEggroll" adds additional fixes. Proton-GE should be viewed as bleeding edge version of Proton and the exact fixes will differ from time to time. For now, Proton-GE focuses on backporting latest Wine fixes and adding latest community-driven patches for various games. Some of the fixes that Proton-GE add might end up Proton. In many cases if your game is not working, it might be working in Proton-GE and later start working in a newer version of Proton too. Proton-GE also requires Steam.

Wine-GE (deprecated):
Contrary to Proton-GE, this version of Wine is based on "vanilla" Wine and some fixes that are found in Proton are added on top of it rather than basing everything on Proton. The main reason you might want to use it is because it does not require Steam runetime to be available. Similar to Proton, Wine-GE can have multiple version, but these versions indicate which Wine version was used as a base, for example, "wine-ge-8", "wine-ge-11". Some Microsoft related installers work better on "wine-ge". You can manually apply patches to a game using a tool called "winetricks".

UMU Launcher:
This can come in various version such as "umu-proton-10", "umu-rproton-11". The main reason this type of Wine version exists is to solve the Proton's problem that Proton requires Steam, UMU Launcher does not need Steam to run games. It is supposed to be a replacement for Wine-GE. There are rare cases where the Steam overlay or Steam libraries can be causing issues with your game, though there are ways to solve it, UMU Launcher is meant to make a "unified" Wine version to contain all known patches.

Flatpak or native?

Native system package installs of Lutris/Bottles and even other runners make your app run using the system's libraries. As a result, you need to have a compatible package version between all binaries and libraries that are involved in running your game.
The problem usually is with dependencies, since you require quite strict versions between each packages on your system, you might encounter a situation where you cannot update because a package requires an older version (dependency hell).

To solve this, many use "Flatpak" which are images that contain all the needed binaries and libraries with the correct versions and will work regardless of what your system package version is. A feature that comes wih Flatpaks is that the process is sandboxed and is considered to be more secure, but as a side effect sometimes Flatpaks might have issues reaching certain hardware in your system or even certain files that may be required for your game to run.

Currently most (gaming) issues with Flatpak can be fixed by searching for a solution. Most commonly you will need to either install an additional Flatpak (especially relevant in case of Nvidia) or add access to a certain folder using "Flatseal".
Since Flatpaks take care of the library and binary versions themselve, you can expect more frequent and more up-to-date features added to Flatpaks instead of native packages.

Adding a custom runner in a Flatpak might be difficult and finding the right folder to place files for the game to pick up also might be more difficult, but these issues can be solved by searching for a solution for your specific game. Therefore consider trying a Flatpak first and if something does not work, then try installing a native system package.