Proton icon indicating copy to clipboard operation
Proton copied to clipboard
Published 2 weeks ago • verified publisher icon ValveSoftware

Deadlock (1422450)

Open DavidPSterling opened this issue 1 year ago • 20 comments

Compatibility Report

  • Name of the game with compatibility issues: Deadlock
  • Steam AppID of the game: 1422450

System Information

  • GPU: NVIDIA GeForce RTX 3080 Laptop

  • Video driver version: 555.58.02

  • Kernel version: 6.8.0-40-generic

  • Link to full system information report as Gist: https://gist.github.com/DavidPSterling/e552494595baff11dd3fc3e7d0be9299

  • Proton version: Experimental

I confirm:

  • [ x ] that I haven't found an existing compatibility report for this game.
  • [ x ] that I have checked whether there are updates for my system available.

steam-1422450.log

Symptoms

Game crashes when connecting to server.

Reproduction

Open game. Click "join queue", select your heroes, click join, once the game starts connecting it crashes

DavidPSterling avatar Aug 24 '24 09:08 DavidPSterling

Workaround: Raise vm.max_map_count similarly to https://archlinux.org/news/increasing-the-default-vmmax_map_count-value/.

kisak-valve avatar Aug 24 '24 13:08 kisak-valve

The "Processing Shaders" step happens every time I launch the game, and takes several minutes every time. This is unusual compared to almost every other game running on Proton. Is there a reason this game refuses to save the output of shader compilation to disk?

EDIT: Turns out, the game just updates like 15 times a day, and after every update it requires a new shader compilation. Annoying, but I get it.

Daktyl198 avatar Aug 29 '24 19:08 Daktyl198

I'm facing an issue where some arbitrary action in-game kills my frames and I have to restart the game. It's pretty hard to reproduce because I have no idea of the conditions, but any game that lasts long enough has it. Mostly happens during some big fight

lucasreis1 avatar Aug 30 '24 03:08 lucasreis1

Textures dont properly render for me, a lot are plain black, some are black with a metallic shine. Also, its random if player models show up in the game CPU: Intel(R) Core(TM) i5-8265U GPU: Intel UHD Graphics 620

Zetabite avatar Sep 23 '24 00:09 Zetabite

I'm on Pop!OS 22.04, Nvidia RTX 3080, GNOME/X11 session:

I've been playing the game for 2 weeks with zero issues. As of the latest update, the game semi-freezes GNOME on launch: the game is visually frozen on Valve's logo and my side monitor is frozen on whatever window I had open. I can still move my mouse, and the cursor updates if I move it over a window titlebar/over the game monitor. However, the game audio is still playing, and I can hear audio cues from mousing over/clicking on buttons in game. Each time I launch and the game freezes, I'm unable to recover my system and have to do a hard reboot.

If I launch the game, then immediately select another window on my side monitor, the game launches as normal, briefly displays GNOME's "This application is not responding" dialog, then the dialog disappears, the game runs normally, and I'm able to click back into the game window and play.

parasnailor avatar Sep 23 '24 19:09 parasnailor

game is unlaunchable debian bookworm system info: https://gist.github.com/mathew2214/f75390c266e293080b8c44526849d8a2

mathew2214 avatar Dec 17 '24 02:12 mathew2214

Archlinux game is crashing for me on start, regardless of what proton version I use, this is logs from 8.0 steam-1422450.log

Quackdoc avatar Dec 24 '24 08:12 Quackdoc

my problem : game crashing just after the loading screen on game launch

Here is what solve the problem (from "Ari melody" on protonDB)

If you experience crashing while (pre-)loading the map (or proton logs otherwise mention mmap() error cannot allocate memory), 
you may need to adjust vm.max_map_count to something higher than your default.

to see your current value, run sudo sysctl vm.max_map_count. temporarily adjust with 
sudo sysctl -w vm.max_map_count=<num> (262144 works for me, YMMV), 
and when satisfied, set it by adding the value (vm.max_map_count=<num>) in /etc/sysctl.d/99-steamplay.conf.

gaming-centric distros will  #likely have a larger vm.max_map_count by default.

in my case, "Pre-loading map and shaders" was stuck at "0 of 0" at the top of my screen, even when having entered the map.
you can get rid of this with -no_prewarm_map, though i would expect loading times to be worse.

juleslagarde avatar Apr 12 '25 19:04 juleslagarde

The game stopped launching yesterday, it worked the day before that. After pressing "PLAY" it says "Running" but no window appears, the main game process (deadlock.exe) is left in zombie state. Here's my system info: https://gist.github.com/rkfg/5d567350048d04be36bb39a7626b9ef8 Proton output: https://gist.github.com/rkfg/21fc98f914f67110f2e3acc54ba5e447

What I tried:

  • verifying game files
  • verifying proton/steam runtime files
  • switching to steam Beta and back
  • using different Proton versions
  • using older kernel
  • turning off AppArmor
  • updated NVIDIA driver
  • turning off compositor/scaling workarounds (I set -system-composer -forcedesktopscaling 1.5 parameters, tried without them)
  • clearing Steam cache
  • removing the game prefix
  • reinstalling the game
  • looking at strace not knowing what to actually look for
  • rebooting
  • turning the PC off completely including PSU switch, in case it's a hardware issue that can persist between regular reboots
  • vm.max_map_count is 8388600 since forever so doesn't apply

I managed to launch the game a couple of times but it doesn't happen anymore so I'm pretty much stuck. The weird thing is that it worked on May 3 and I haven't even restarted Steam since then AFAIR, and then it stopped working like that. I believe Steam isolates the environment from the main system so the libraries and programs I have installed shouldn't interfere with it or the games. But just for the sake of completeness, I updated these programs some time between the moments when game worked and stopped:

Upgrade: librados2:amd64 (18.2.4+ds-13+b1, 18.2.6-1), libxapian30:amd64 (1.4.25-2, 1.4.29-2), libqt6help6:amd64 (6.8.2-4, 6.8.2-5), coreutils:amd64 (9.7-1, 9.7-2), libgles2-mesa-dev:amd64 (25.0.3-1, 25.0.4-1), assistant-qt6:amd64 (6.8.2-4, 6.8.2-5), iputils-ping:amd64 (3:20240905-1, 3:20240905-3), libglx-mesa0:amd64 (25.0.3-1, 25.0.4-1), libglx-mesa0:i386 (25.0.3-1, 25.0.4-1), libssh-4:amd64 (0.11.1-1, 0.11.1-2), mesa-common-dev:amd64 (25.0.3-1, 25.0.4-1), gdb:amd64 (16.2-8, 16.3-1), sgml-base:amd64 (1.31, 1.31+nmu1), libusageenvironment3:amd64 (2:2025.01.17-dmo1, 2:2025.04.24-dmo1), libosmesa6-dev:amd64 (25.0.3-1, 25.0.4-1), python3-lazr.restfulclient:amd64 (0.14.6-2, 0.14.6-3), libcap2-bin:amd64 (1:2.75-6, 1:2.75-7), kwayland5-data:amd64 (4:5.115.0-6, 4:5.116.0-1), libkf5notifications-data:amd64 (5.115.0-2, 5.116.0-1), qt6-tools-dev-tools:amd64 (6.8.2-4, 6.8.2-5), qdbus-qt6:amd64 (6.8.2-4, 6.8.2-5), libgbm1:amd64 (25.0.3-1, 25.0.4-1), libgbm1:i386 (25.0.3-1, 25.0.4-1), librbd1:amd64 (18.2.4+ds-13+b1, 18.2.6-1), libgbm-dev:amd64 (25.0.3-1, 25.0.4-1), gdbserver:amd64 (16.2-8, 16.3-1), sse3-support:amd64 (26, 27), qt6-tools-dev:amd64 (6.8.2-4, 6.8.2-5), libkf5config-bin:amd64 (5.115.0-2+b1, 5.116.0-1), libspnav0:amd64 (1.1-2, 1.2-1), mesa-libgallium:amd64 (25.0.3-1, 25.0.4-1), mesa-libgallium:i386 (25.0.3-1, 25.0.4-1), libkf5filemetadata-data:amd64 (5.115.0-3, 5.116.0-1), gimp-data:amd64 (3.0.2-1, 3.0.2-2), libkf5windowsystem5:amd64 (5.115.0-2+b1, 5.116.0-1), libxatracker2:amd64 (25.0.3-1, 25.0.4-1), isa-support:amd64 (26, 27), libgl1-mesa-dev:amd64 (25.0.3-1, 25.0.4-1), libgl1-mesa-dri:amd64 (25.0.3-1, 25.0.4-1), libgl1-mesa-dri:i386 (25.0.3-1, 25.0.4-1), libosmesa6:amd64 (25.0.3-1, 25.0.4-1), designer-qt6:amd64 (6.8.2-4, 6.8.2-5), libegl1-mesa-dev:amd64 (25.0.3-1, 25.0.4-1), libqt6designercomponents6:amd64 (6.8.2-4, 6.8.2-5), diffutils:amd64 (1:3.10-3, 1:3.10-4), sensible-utils:amd64 (0.0.24, 0.0.25), qt6-documentation-tools:amd64 (6.8.2-4, 6.8.2-5), breeze-icon-theme:amd64 (4:5.115.0-4, 4:5.116.0-1), libcap2:amd64 (1:2.75-6, 1:2.75-7), libcap2:i386 (1:2.75-6, 1:2.75-7), gimp:amd64 (3.0.2-1, 3.0.2-2), libcap-dev:amd64 (1:2.75-6, 1:2.75-7), libkf5configcore5:amd64 (5.115.0-2+b1, 5.116.0-1), libcpan-changes-perl:amd64 (0.500004-1, 0.500005-1), brave-browser-beta:amd64 (1.79.95, 1.79.97), libkf5waylandclient5:amd64 (4:5.115.0-6, 4:5.116.0-1), libkf5coreaddons-data:amd64 (5.115.0-2, 5.116.0-1), mesa-vulkan-drivers:amd64 (25.0.3-1, 25.0.4-1), python3-bs4:amd64 (4.13.3-2, 4.13.4-1), python3-prompt-toolkit:amd64 (3.0.50-1, 3.0.51-2), breeze-icon-theme-rcc:amd64 (4:5.115.0-4, 4:5.116.0-1), libkf5wallet-bin:amd64 (5.115.0-4, 5.116.0-1), linguist-qt6:amd64 (6.8.2-4, 6.8.2-5), python3-html2text:amd64 (2024.2.26-1, 2025.4.15-1), libqt6uitools6:amd64 (6.8.2-4, 6.8.2-5), libkf5config-data:amd64 (5.115.0-2, 5.116.0-1), slirp4netns:amd64 (1.2.1-1+b1, 1.2.1-1.1), libkf5notifications5:amd64 (5.115.0-2+b1, 5.116.0-1), libqt6designer6:amd64 (6.8.2-4, 6.8.2-5), qdoc-qt6:amd64 (6.8.2-4, 6.8.2-5), btrfs-progs:amd64 (6.12-1+b1, 6.14-1), brave-browser:amd64 (1.77.101, 1.78.94), libkf5windowsystem-data:amd64 (5.115.0-2, 5.116.0-1), libkf5coreaddons5:amd64 (5.115.0-2+b1, 5.116.0-1), m4:amd64 (1.4.19-7, 1.4.19-8), libpam-cap:amd64 (1:2.75-6, 1:2.75-7), libegl-mesa0:amd64 (25.0.3-1, 25.0.4-1), libkf5solid5-data:amd64 (5.115.0-3, 5.116.0-1), gir1.2-gimp-3.0:amd64 (3.0.2-1, 3.0.2-2), mesa-vdpau-drivers:amd64 (25.0.3-1, 25.0.4-1), libgimp-3.0-0:amd64 (3.0.2-1, 3.0.2-2), qt6-l10n-tools:amd64 (6.8.2-4, 6.8.2-5), wdiff:amd64 (1.2.2-8, 1.2.2-9), iputils-tracepath:amd64 (3:20240905-1, 3:20240905-3)
Upgrade: python3-tz:amd64 (2025.1-3, 2025.2-2), python3-lxml-html-clean:amd64 (0.4.1-1, 0.4.2-1), packagekit-tools:amd64 (1.3.0-3+b1, 1.3.1-1), python3-pytz:amd64 (2025.1-3, 2025.2-2), resolvconf:amd64 (1.92, 1.94), node-ip:amd64 (2.0.1+~1.1.3-1, 2.0.1+~1.1.3-3), libnuma1:amd64 (2.0.18-1+b1, 2.0.19-1), libnuma1:i386 (2.0.18-1+b1, 2.0.19-1), gir1.2-packagekitglib-1.0:amd64 (1.3.0-3+b1, 1.3.1-1), packagekit:amd64 (1.3.0-3+b1, 1.3.1-1), libnbd0:amd64 (1.22.0-1+b1, 1.22.2-1), libpackagekit-glib2-18:amd64 (1.3.0-3+b1, 1.3.1-1), nlohmann-json3-dev:amd64 (3.11.3-2, 3.11.3-2.1), libnuma-dev:amd64 (2.0.18-1+b1, 2.0.19-1)

FWIW, the game still works on my Steam Deck. The other games work on PC too, tried HL2 RTX (also Source engine so should probably be close enough?). Only Deadlock is dead.

rkfg avatar May 05 '25 09:05 rkfg

Okay, localized the culprit. It's the very recent update in Debian, the package is mesa-vulkan-drivers. Version 25.0.3-1 works, version 25.0.4-1 breaks Deadlock. The exact file that triggers the bug seems to be /usr/lib/x86_64-linux-gnu/libvulkan_gfxstream.so, I copied it over from 25.0.3-1 and the game now launches. There is a bug reported: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104326 however, the suggested update to 25.0.5-1 does NOT fix this issue.

rkfg avatar May 05 '25 12:05 rkfg

Compatibility Report

  • Name of the game with compatibility issues: Deadlock
  • Steam AppID of the game: 1422450

System Information

  • GPU: RTX 3080
  • Video driver version: nvidia 575.64.03
  • Kernel version: 6.15.4-arch2-1
  • Link to full system information report as Gist:
  • Proton version: Proton Experimental, Proton 10.0-1 (beta), Proton 9.0-4

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

steam-1422450.log

Symptoms

While playing the game, at any point (Joining a match, while playing, on public matches or test server, even at start) the following message will pop up and the game will close up. I have to verify file integrity each time this happens and the game will re download 2 or 3 files every time but without a specific fix.

Image Image

Reproduction

No special reproduction needed, it can happen at startup, match join or match look up. Issue happens both on DX11 and Vulkan, sometimes happens after 2 matches, other times happens when joining a match

DavidVallaLope avatar Jul 09 '25 02:07 DavidVallaLope

Adding the root cause and temporal solution to this issue: After some investigation, seems that this issue is related to RAM Frequency (this happens on source 2 games like CS2 and DOTA 2) where if you use the max available frequency of your RAM (I run Memtest to check for a faulty RAM but no issues where found on both 3600Mhz and 3200Mhz frequency configurations) it throws this error that the pak01.vpk file is corrupted. After changing the Frequency of my ram from 3600 Mhz to 3200 Mhz the crashes haven't happened so far. No other games present this behavior where if I use the max frequency of my RAM's stick, it crashes.

NOTE: This error doesn't happen when I dual boot to Windows, I did this as well to rule out a faulty RAM.

It would be nice to know what is the cause on this only happening on Source 2 based games when they are run using proton.

Reference posts:

DavidVallaLope avatar Jul 11 '25 15:07 DavidVallaLope

Image

Game does not launch on Linux, displaying a grey picture for a few seconds before closing out.

Regardless of proton version

Launch commands:

gamescope -W 2560 -H 1440 -r 170 -- %command%

(doesn't work even if I don't use gamescope either)

officialnochill avatar Aug 24 '25 20:08 officialnochill

Running into the same issue as @officialnochill on arch linux + hyprland

steam-1422450.log

drj17 avatar Aug 25 '25 00:08 drj17

steam-1422450.log

Log^

officialnochill avatar Aug 25 '25 19:08 officialnochill

@officialnochill are you running hyprland by any chance? because it could be a hyprland only issue https://github.com/hyprwm/Hyprland/discussions/10485

edit: the solution for hyprland is to run the game with SDL_VIDEODRIVER=windows %command%, also please consider upvoting the discussion at the Hyprland's repo in hopes it gets fixed

junovell avatar Aug 26 '25 14:08 junovell

Deadlock (1422450)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/9286. @19krikma posted on 2025-12-06T03:13:28:

Compatibility Report

  • Name of the game with compatibility issues: Deadlock
  • Steam AppID of the game: 1422450

System Information

  • GPU: Intel Arc B580
  • Video driver version: 4.6 (Compatibility Profile) Mesa 25.1.5-1pop0~1753463422~24.04~8af185e
  • Kernel version: 6.17.4-76061704-generic
  • Link to full system information report as Gist: https://gist.github.com/19krikma/948cd62173e537fcee0dc34efc22a0ac
  • Link to System Runtime Diagnostics: https://gist.github.com/19krikma/0fefe4fdfb87973a10bd768bf366f411
  • Proton version: Hot-fix, Experimental, 10.0-3, 9.0-4

I confirm:

  • [ X] that I haven't found an existing compatibility report for this game.
  • [ X] that I have checked whether there are updates for my system available.

steam-1422450 experimental.log steam-1422450 hot-fix.log steam-1422450 Proton 10.0-3.log

Symptoms

Steam will launch the game, the window pop will show up and freeze, steam will crash and game window will remain frozen, requires kill, logout or system restart. Only once my system froze completly and had to force shutdown.

Reproduction

Install Intel ARC B580, install drivers following intel linex driver instructions, delete NVIDIA drivers, reboot and try playing Deadlock

kisak-valve avatar Dec 06 '25 13:12 kisak-valve

Hello @19krikma, are you able to test how the game behaves with a current point release of mesa from a PPA like kisak-mesa? If you can reproduce the issue with a current point release of mesa, then you should also mention your findings to your video driver vendor.

kisak-valve avatar Dec 06 '25 14:12 kisak-valve

Hello @19krikma, are you able to test how the game behaves with a current point release of mesa from a PPA like kisak-mesa? If you can reproduce the issue with a current point release of mesa, then you should also mention your findings to your video driver vendor.

I installed the latest kisak-mesa the issue is still there.

19krikma avatar Dec 07 '25 01:12 19krikma

@kisak-valve Hello, I got it fixed. I reinstalled PopOS 24.04 and now I can play Deadlock, I suspect the issue was that I installed these drivers, I wasn't sure if I needed them so on old build i had them and on this fresh install I don't have them. I am back on Mesa 25.1.5-1pop0~1753463422~24.04~8af185e I am experiencing a bug where game renders the "Strings or the thing that players can travel on a lane" through buildings, so I pretty much see other lanes. I will try to install latest kisak-mesa today or tomorrow and see if the issue remains but so far game runs great, just needed some tinkering because game launched in 2k windowed mode and had to fidget around to get the game in full screen and switch from "Vulkan" to "DirectX 11".

19krikma avatar Dec 08 '25 14:12 19krikma