Multiplayer never worked for me either. Although some people at wine appdb say it works for them.

@OlliC Online works fine with my Lutris + Wine-Staging

Yeah Doom MP works thru lutris but crashes when using Steam Play

+1 Also share the same experience as @Reded100 using Ubuntu 16.04 LTS (x64) and NVIDIA 396.54 driver (Proton 3.7.1535035861):

Steam System Information

Can confirm this issue appears to be resolved with Wine Staging 3.14 and DXVK 0.70.

Hope that helps.

Ubuntu 16.04, NVIDIA GTX 970, Proton 3.7-4 Beta:

Steam System Information

^ Application crash when searching for other players (log)
^^ Default graphics API is OpenGL

Same issue. Arch Linux. Using amdgpu driver. Crashes as a multiplayer game is about to begin. Single Player working as expected using Vulkan API. Not posting a log since it is the same the one posted by @mimattr

Same here, I saw something about Wine 2.0 having DOOM multiplayer support, but I'm not sure what proton is: https://news.softpedia.com/news/wine-staging-2-0-adds-basic-aes-gcm-support-and-fixes-doom-2016-multiplayer-mode-511363.shtml

Does anyone know why it can be whitelisted when multiplayer doesn't work?

has the proton 3.16 beta fixed anything with this? i couldn't get a multiplayer match to check, because apparently nobody plays lol

has the proton 3.16 beta fixed anything with this? i couldn't get a multiplayer match to check, because apparently nobody plays lol

Still crash on 3.16 beta

@ashkitten @reded100 3.16 beta is where I tested it, if you go to team deathmatch you should be able to find a match

Same Problem here with 3.16

Same problem here.
Xubuntu 18.04
NVIDIA GTX 1060 @ 396.54

And same with
Ubuntu 16.04
Quadro K5000M @ 410.73

@Alexander88207 @Alexmitter @ViktorWalter What is the exact behavior you are seeing when entering a multiplayer match with 3.16-6? There have been some changes for 3.16-6 compared to earlier versions of 3.16, so please retest. If you are getting a failure, it would be helpful to take a +wininet,+winhttp,+winsock,+bcrypt,+secur32 log.

Confirming that I no longer have this problem on Arch with 3.16-6. Great job with the fix guys, I hope it works for everyone else.

And same with
Ubuntu 16.04
Quadro K5000M @ 410.73

Sorry, I was on the wrong version. With 3.16-6 it works fine.

@kisak-valve unfortunately the multiplayer issue still exists with Proton 3.16-6 Beta, a consistent application crash occurs before any match starts (tested on Ubuntu 16.04 LTS):

steam-379720.log (170MB, expires Jan 4)

Steam System Information

@mimattr From the log, it looks like you are still running into the libgnutls 26 problem. Since steam-runtime still uses libgnutls 26, you need to have libgnutls 30 installed locally. The log also looked like it picked up a libgnutls30 install, but perhaps it is broken?

Since steam-runtime still uses libgnutls 26, you need to have libgnutls 30 installed locally. The log also looked like it picked up a libgnutls30 install, but perhaps it is broken?

@alasky17 Is there a preferred method to test this? Installing gnutls-bin and executing the following command suggests GNU TLS 3.4.10 is installed and working:

$ gnutls-cli --version
gnutls-cli 3.4.10
Copyright (C) 2000-2016 Free Software Foundation, and others, all rights reserved.
This is free software. It is licensed for use, modification and
redistribution under the terms of the GNU General Public License,
version 3 or later <http://gnu.org/licenses/gpl.html>

Please send bug reports to:  <[email protected]>

@mimattr To double-check that libgnutls30 is installed, you can run "dpkg -l | grep libgnutls30" and make sure the lines have "ii" indicating they are installed (both the i386 and amd64 versions -- you may need both 32 and 64 bit).

The dev who worked on the libgnutls update looked at your log and said that it looks like you are not on a recent enough version of Proton. Just to make sure, you could delete the Proton 3.16 Beta folder from .steam/steam/steamapps/common and then verify the integrity of any game files with the beta selected in the Steam settings. This will redownload the current version.

you can run "dpkg -l | grep libgnutls30" and make sure the lines have "ii" indicating they are installed (both the i386 and amd64 versions -- you may need both 32 and 64 bit).

@alasky17 Executing the following command suggests GNU TLS 3.4.10 is installed and working:

$ dpkg -l | grep libgnutls
ii  libgnutls-openssl27:amd64  3.4.10-4ubuntu1.4  amd64  GNU TLS library - OpenSSL wrapper
ii  libgnutls30:amd64          3.4.10-4ubuntu1.4  amd64  GNU TLS library - main runtime library
ii  libgnutls30:i386           3.4.10-4ubuntu1.4  i386   GNU TLS library - main runtime library

you could delete the Proton 3.16 Beta folder from .steam/steam/steamapps/common and then verify the integrity of any game files with the beta selected in the Steam settings.

@alasky17 Unfortunately the issue still exists after deleting the following directories and validating the installation within Steam:

• ~/.steam/steam/steamapps/compatdata/379720
• ~/.steam/steam/steamapps/compatdata/shadercache/379720
• ~/.steam/steam/steamapps/common/Proton 3.16 Beta

Updating to the latest Steam Client Beta has not resolved the issue either (steam-runtime-beta-release_2019-01-10)

Has anyone reported successful multiplayer functionality with a standard Ubuntu 16.04 LTS install?

I tried it today with Proton 3.16-7 and the multiplayer is working. Didn't worked with whitelisted version.

Here are my specs

Crashing with 3.16-8 Beta as of today out of the box.

Installed GNUTLS 3.6.4 and still crashing. This time I'm crashing as I join in match making, before even loading... :/

Not a working user experience.

Tried with 3.16-8 and the multiplayer is running fine. Finished one team deathmatch game without any issue.
My specs

@Zlopez maybe it's because you're AMD? I'm nvidia GTX 960, 418.43

@BloodyIron Yes, this could be the case.

@BloodyIron @Zlopez I can not say if that changed for the last proton version, but i was able to play MP with my 1060 and as well now with my Radeon VII

@Alexmitter what version of Steam Play you using? Any steps you had to take?

@BloodyIron To start, could you get a log with these channels: +bcrypt,+secur32,+wininet,+winhttp,+winsock You can do this by editing user_settings.py in $HOME/.steam/steam/steamapps/common/Proton 3.16 Beta.

Also, make sure that you switched to the 3.16 Beta in the properties for DOOM itself - a recent change to Steam means that you now have to specify Proton version in the game specific settings for any whitelisted title. (Sorry if you know this already, just wanted to cover the bases).

@alasky17 I'll get that for you in a bit :)

@alasky17 need some clarification please.

1. I don't have a user_settings.py file, do you want me to just copy from the default example file?
2. Do you want me to add those parameters and commas to the "WINEDEBUG" compoonent, or replace the default ones?
3. Once I've tried multiplayer with those things set, then what? You want logs, or? And from where?

@BloodyIron thank you for the questions :)

1. Yes, you can just cp the user_settings.sample.py file to user_settings.py in the same folder.
2. Yes, you can edit user_settings.py and add the extra channels on the winedebug line with the same formatting as the rest of the line.
3. After setting up user_settings.py, a log with those parameters will be created automatically when you launch a Proton game and stored in your home directory $HOME or ~. The log will have the game steam ID in the title, and if you launch a game again without renaming the log, it will be overwritten with the new launch.

After setting up the logging, please launch DOOM and navigate until you hit the crash and the game exits so that the log will include the crash. I believe that you can upload the file by dragging it onto your github comment while you are editing it.

I hope this made the process more clear!

steam-379720-Crash-Proton-Multiplayer-BloodyIron-Mar16-2019.zip

Tada! \o/

Also, your clarification most certainly did help! Thanks! :D

Man that 7.6MB file took forever to upload, WTF MS?

@BloodyIron thank you! I will take a look at those logs.

@mimattr We made some more changes to the code that touches the gnutls work. If you are still seeing the same problem with 3.16-8 Beta, could you also provide a +bcrypt,+secur32,+wininet,+winhttp,+winsock log? I have outlined how to do to that in some comments above if you are unsure. Thank you for being patient!

@BloodyIron could you also attach your system specs? The info is all listed in the Steam menu under Help -> System Information and you can copy that into an attachment. Thank you!

doesn't seem to accurately represent my soundcard though lol:

28:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller

We made some more changes to the code that touches the gnutls work.

@alasky17 Confirmed, the multiplayer mode now functions as expected with Proton 3.16-8 Beta.

@kisak-valve Once Proton 3.16-8 Beta becomes stable the SteamPlay whitelist should be updated, currently Proton 3.7-8 does not provide the full product experience.

As always kudos to all involved for their continued time and support on this issue!

Why is that version working for you and not me I wonder?

Why is that version working for you and not me I wonder?

@BloodyIron Are you able to play the singleplayer campaign without issues? If so open a terminal window and execute the following command:

dpkg -l | grep gnutls && locate libgnutls

Copy the output and either save it as a text file or ideally create a gist, which can then be added to this discussion for further analysis.

Hopefully that will help highlight any potential problems.

I was able to play several single player levels without installing gnutls, without observed issue, but as part of recent multiplayer troubleshooting I figured I'd try installing it, and it did not solve the crashing.

Installed version of gnutls : gnutls-bin/cosmic-updates,now 3.6.4-2ubuntu1.1 amd64 [installed]

@BloodyIron one more question (for now) - when exactly are you seeing the crash? Is it crashing when you try to enter a multiplayer instance after the server has indicated that there are enough players to start a session? or some other time (or inconsistent)?

This, consistently, happens right after all players have been matched for a game, then it looks like each player is told to connect to the server, and that's when I crash. At least, that's what I'm seeing from the UX perspective.

@BloodyIron From the initial log, it looks like this is a different problem from the gnutls issue. Could you follow the same method and create a new log with +d3d +vulkan added to the logging channels as well? This will likely slow the game down quite a bit, so make sure to delete it afterwards :)