Depending on your Linux distribution, you may need a small fix to get Valve's new game Deadlock to work properly. So here's what you need to know. Currently the game does not have a Native Linux version, so you need to run it with Proton and it runs pretty well. It's also invite-only, so find a friend somewhere to invite you.
If you find the game crashes when connecting to a server or otherwise, you likely need to raise your "vm.max_map_count". Yes, it strikes again. Many Windows games via Wine / Proton need a higher vm.max_map_count than some Linux distributions ship with out of the box.
You can find what yours currently is with this terminal command:
cat /proc/sys/vm/max_map_count
To set it temporarily higher you can do this in terminal:
sudo sysctl -w vm.max_map_count=1048576
That above is the newer default that Ubuntu, Fedora and Arch Linux were updated with. Previously many distributions had it quite low at 65530.
For a permanent change you can edit the "/etc/sysctl.conf" file or "/etc/sysctl.d" depending on your distribution, add "vm.max_map_count=1048576" to the bottom and then run:
sudo sysctl -p
Which should keep the change.
Last edited by Bogomips on 27 August 2024 at 12:21 pm UTC
Since I found out it is the value I use in Linux Mint 22.
Quoting: [email protected]I need an invite.https://www.reddit.com/r/DeadlockTheGame/comments/1f0e1bo/megathread_ask_for_invites_to_the_playtest_here/
Quoting: PhiladelphusAre there any potential complications/consequences for setting vm.max_map_count higher, or is this a set-it-and-forget-it sort of change?
https://github.com/torvalds/linux/blob/v5.18/include/linux/mm.h#L178
Quoting: BogomipsQuoting: PhiladelphusAre there any potential complications/consequences for setting vm.max_map_count higher, or is this a set-it-and-forget-it sort of change?
https://github.com/torvalds/linux/blob/v5.18/include/linux/mm.h#L178
The way I read that is: unless you are trying to track down crashes in ancient Linux binaries, the old default is not relevant.
Quoting: PhlebiacQuoting: BogomipsQuoting: PhiladelphusAre there any potential complications/consequences for setting vm.max_map_count higher, or is this a set-it-and-forget-it sort of change?
https://github.com/torvalds/linux/blob/v5.18/include/linux/mm.h#L178
The way I read that is: unless you are trying to track down crashes in ancient Linux binaries, the old default is not relevant.
I also understand it that way, but being on Debian stable, everything is old :P so I try to not go overboard and keep it at the new normal level (i.e. 1048576).
Quoting: [email protected]I need an invite.
If you havent got it yet I have sent you a friend request by the Steam Name "Saladin"
See more from me