Since there are many different Linux distributions out there, you might encounter issues with your specific installation. This section lists some commonly encountered issues and their solutions.
-
Launcher (BSG/SPT)
-
In-Game
-
Lutris / Installer scripts
-
Manual installation / Others
Description
After clicking Play, the game briefly opens & closes shortly after.
Solution
Usually this means the DLL override for winhttp is missing!
Manually set winhttp to n,b in Configure > Runner options > DLL Overrides.
If the game worked previously & this happens after installing new mods, chances are you're running into issues with the mod(s). Check compatibilty of the mod with other mods as well as the installed SPT version.
Description
The BSG Launcher will not show correct fonts (Bender font family) for some text.
Solution
To fix fonts in the BSG Launcher, you can download & install the Bender font (external link, *.zip archive) on your distribution.
Unfortunately, this will not work when using a Proton runner for the application.
Description
The game crashes while playing a raid or being in the hideout.
Solution
-
Make sure you've
Swapset up on your system. Tarkov will need at least someSwap, even on systems with a lot of RAM available. -
Another issue could be the
vm.max_map_countlimit (mostly on older distros).A detailed explaination of what that is can be found here.
The recommended solution is to raise it to a recommend value of
1048576e.g. by adding:vm.max_map_count=1048576to
/etc/sysctl.confand runsudo sysctl -pas stated here.
As of early 2024, most common distros changed their default value as well.
Description
Sounds in the game are crackling / distorted.
Solution
In Lutris on the game shortcut, enable:
Configure→system options→Reduce PulseAudio latency
That should fix the issue.
Description
With NVIDIA proprietary drivers on Wayland at Raid-Start or Raid-End the screen freezes. The game is still running in the background (e.g. sounds still play when the mouse hovers UI elements).
Solution
This was a bug in NVIDIA drivers prior to version 560 - It's related to high VRAM usage and Wayland. The driver did not fallback to virtual memory / swap whenever the GPUs VRAM was maxed out.
If you check your kernel log with journalctl -b -r shortly after it occurs, you'd probably see the following error:
Jun 11 19:28:15 kernel: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00002600] Failed to allocate NVKMS memory for GEM object
We recommend using a Nvidia driver version >= 560 and let the GSP firmware blob enabled to fix the issue.
Description
You can get different error codes at different steps throughout the installation process.
Solution
It's hard to pinpoint the exact issue since many different apps use the same exit codes and there are many different tasks performed. Try to keep game files and restart the script.
If the error persists after multiple attempts, please open up a bug report containing:
- A detailed description of the issue
- The task shown when the error occurs (e.g. "
Installing game dependencies ..." or "Launching BSG Launcher ...") - If possible, try to take a screenshot or a short video of the issue
- If the Lutris installer fails while showing "
Installing SPT ...", please attach thespt-linux-additions.loglog file (usually found inside~/.cache/spt-linux-additions) to the bug report
To get more details if something breaks, you can launch Lutris in debug mode using the following command in a terminal:
lutris -d &> lutris.log
flatpak run net.lutris.Lutris -d &> lutris.log
This will generate a lutris.log file in your current or home directory.
To debug issues that might be caused by Wine, you also need to enable debug logging for Wine:
Configure→Runner options→Output debugging info→Enabled
That should enabled wine logs in the console / output added to the lutris.log file.
Description
The installation fails with the log containing something like:
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 156 (NV-GLX)
Minor opcode of failed request: 43 ()
Serial number of failed request: 149
Current serial number in output stream: 150
Solution
It looks like there is an open Nvidia/Wine bug report that is working on fixing that issue.
You can try to disable your iGPU in your bios settings if possible. The corresponding option often is called GFX/iGPU Multi-Monitor or similar.
This should make sure that Lutris is seeing your discrete GPU only.
Description
When using Lutris 0.5.17 & running the SPT.Server via Proton (Proton ≠ Wine!), the server will keep running in the background after closing the window.
Solution
(Updated 2024/12/23)
It's a missing ""feature"" in Lutris.
It's possible to work around the issue by disabling CLI mode in the system options tab & changing/setting the value of the environment variable PROTON_VERB to run. This will launch the server window in a custom windows-like CMD window (without ANSI/color support).
Description
When launching SPT.Launcher, either one of two issues can occur:
- A window pop-up appears which says that .NET Desktop Runtime is not installed. OR
- Launcher not coming up and the lutris console log shows a semi-random error code e.g.
40960
Solution
Unfortunately, this can mean a bunch of things. Here's a check-list:
-
Make sure .NET Desktop Runtime 8.0 is installed inside the wine prefix. You should find a
dotnetfolder atWINEPREFIX/drive_c/Program Files/dotnet/containing thedotnet.exeexecutable. -
Try to set no value for
DOTNET_ROOTandDOTNET_BUNDLE_EXTRACT_BASE_DIRin the environment variables for your wine application.- Bottles:
Settings→Environment variables - Lutris:
Configure→System options→Environment variables
- Bottles:
-
Proton only: When using a Proton runner, sometimes it can help to get rid of the
vrclientdirectory indrive_c. It's not needed for running the Launcher & for whatever reason it seems to cause issues sometimes. Root of this likely is a missing registry entry forHKEY_CURRENT_USER\\Software\\Wine\\VR. More details can be found here. -
Sometimes the Lutris runtime or a wine runner can cause issues as well.
-
Check if the correct
wine versionis set for the game and the runner is working. -
If that didn't help, you could try deleting the
runtimedirectory in:- Flatpak:
~/.var/app/net.lutris.Lutris/data/lutris/runtime - Native:
~/.local/share/lutris/runtime
& re-download the runtime from
Preferences>Updates:
- Flatpak:
-
-
There's a rare issue sometimes with the
icu.dllused by the prefix & some wine versions. Usually it will show a log entry mentioningicu.dlloricucin the wine/proton log. You can try to disable theicu.dllin theDLL overrides:- Bottles:
Settings→DLL overrides: Add keyicu, selectdisabledas value & save the changes. - Lutris:
Configure→Runner options→DLL overrides: Add keyicu, valued& save the changes.
- Bottles:
Description
When launching the game using Bottles, it crashes with the log message "Failed to create D3D shaders".
Solution
Usually the error indicates that the dependency d3dcompiler_47 is missing.
Either the bottle is not set up using the Gaming preset or Bottles failed to fetch required dependencies (e.g because no internet connection was available).
By default Bottles should install the following dependencies when using the Gaming preset:
d3dx9, msls31, d3dcompiler_43, d3dcompiler_47, arial32, times32, courie32.
- Make sure all dependencies are listed as installed at the bottom of
Options→Dependencies. If not, install them manually and try again.
Description
When using a Proton runner, only one application can be launched at a time. When trying to launch a second application inside the same prefix, it will quit instantly.
Solution
This is the default behaviour for running games using Proton. You can override the behaviour by setting the environment variable PROTON_VERB to runinprefix before running the executable(s):
- Bottles:
Settings→Environment variables - Lutris:
Configure→System options→Environment variables