The following bugs occur when playing both in private and co-op matches, or while exploring the Hideout.
Bugs when using DX11:
When running with Proton 9 and Experimental, the DX11 renderer produces corrupted text, either showing incorrect text lines (such as "566577" having appeared when killing Kelvin) or completely garbled text.
Likewise, a graphics driver panic may occur which crashes the user session when using the DX11 renderer. This takes about 50-60 minutes of gameplay to occur, and is likely related to poor resource handling in DXVK (I have not been able to diagnose this). Based on a search of the forums, this may be the result of a memory leak leading to resource exhaustion.
Bugs when using Vulkan:
Switching to the Vulkan renderer clears the text corruption and several animations play more fluidly.
However, intermittent stuttering or drop-outs of audio may occur when using the Vulkan renderer (this is not present with DX11). Causes are unknown, but appear to be related to PulseAudio (as opposed to PipeWire or similar, which is present on Debian 12 and later installations; however, this may simply be what's exposed when the
General Audio Bugs:
Bugs when using DX11:
When running with Proton 9 and Experimental, the DX11 renderer produces corrupted text, either showing incorrect text lines (such as "566577" having appeared when killing Kelvin) or completely garbled text.
Likewise, a graphics driver panic may occur which crashes the user session when using the DX11 renderer. This takes about 50-60 minutes of gameplay to occur, and is likely related to poor resource handling in DXVK (I have not been able to diagnose this). Based on a search of the forums, this may be the result of a memory leak leading to resource exhaustion.
Bugs when using Vulkan:
Switching to the Vulkan renderer clears the text corruption and several animations play more fluidly.
However, intermittent stuttering or drop-outs of audio may occur when using the Vulkan renderer (this is not present with DX11). Causes are unknown, but appear to be related to PulseAudio (as opposed to PipeWire or similar, which is present on Debian 12 and later installations; however, this may simply be what's exposed when the
pipewire-pulse package is available).General Audio Bugs:
- Selecting audio devices other than "System Default" or "PulseAudio" results in a loss of sound.
- When a Bluetooth audio device is the current default or has been selected as the output device within Deadlock, the application will fail to launch, becoming stuck before the experimental build notice dialog. Currently tested with a "Poly BT700" device.
- Switching to Bluetooth audio device may cause the application to hang or crash unexpectedly.
- Debian 13, all "stable" updates installed as of 31 Jan 2026.
- Tested with Proton 9.0-4 (compatibility default) and Proton Experimental.
- Linux Kernel 6.12.63-1.
- PipeWire 1.4.2-1 (includes PulseAudio and ALSA support); PulseAudio is not installed.
- MESA 25.0.7-2 (on an AMD RX6600).
- Vulkan 1.4.309.0-1.
