Also #4266, there's an issue with connecting to X on some computers.

As mentioned in #4278, the release requires enabling the kernel.unprivileged_userns_clone kernel flag:

bwrap: No permissions to creating new namespace, likely because the kernel does not allow non-privileged user namespaces. On e.g. debian this can be enabled with 'sysctl kernel.unprivileged_userns_clone=1'.

This is not acceptable -- this flag is for a feature that has not been fully vetted for security and has been disabled in several security-conscious distros. The best info I could find is in this article: https://lwn.net/Articles/673597/

Personally, I think that requiring user namespaces gains absolutely no value for Proton or the steam runtime and should not be required.

This mutter MR makes games work in a gnome wayland session when using the new runtime: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508

* Doesn't work on a Wayland desktop

The games I've tried on Plasma Wayland worked fine. The issue referred probably to Gnome, see Oschowa's comment.

This mutter MR makes games work in a gnome wayland session when using the new runtime: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508

Thanks, with this MR the issue Doesn't work on a Wayland desktop was gone.

I would like to add here that the cursor behavior has changed as well, I noticed this in Among Us as my mouse cursor was super super tiny on my 4K screen.

Going back to 5.0.9 uses the cursor from my window manager as expected.

I also want to chime in here to say that Proton 5.13 won't run on Debian 10 (Buster) due to some missing symbols in libraries:

/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so

Also it seems to have some problems with directories with spaces in their names ("Datei oder Verzeichnis nicht gefunden" means "File or directory not found"):

pressure-vessel-launch[7045]: Failed to start command: Failed to change to directory '/usr/local/games/SteamLibrary/steamapps/common/Streets Of Kamurocho' (Datei oder Verzeichnis nicht gefunden)

due to some missing symbols in libraries

Those warnings about gvfs modules are harmless, please ignore them. We know why they happen. They'll be fixed eventually, but because they're only cosmetic, it is not a high priority.

Also it seems to have some problems with directories with spaces in their names

The spaces are not the problem. The problem is that the game is in /usr/local, and the container runtime system replaces /usr with the read-only Steam Runtime, so the game isn't visible to the container. Workaround: use a different library directory below /home, /srv, /media or some other non-/usr directory.

Selecting Proton 5.13 for a game and launching it will only download "Proton 5.13" and not "Steam Linux Runtime - Soldier", resulting in no games launching properly. This can be avoided by either installing both by hand or restarting Steam after the initial launch.

Fixed in Steam beta client >= Oct 21.

Proton 5.13 doesn't seem to set up wine prefixes properly for me. There are several folders in user folder that don't get created. This results in certain games misbehaving because they can't find for instance the My Documents folder, which they need to write to and read from, and the games don't (can't?) create those directories by themselves if they are missing.

So far I know that Fable - The Lost Chapters and Final Fantasy XIV fail to run if My Documents folder is not present. You would have to manually create that folder after installing the game before it works (that, or use an older version of Proton.)

It also does not work along side amdgpu-pro
#4288

• Doesn't work on a GNOME Wayland desktop (needs https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508)
• Steam "Force Quit" feature doesn't work

Fixed in Steam beta client >= Oct 22 (make sure to switch 'Steam Linux Runtime - Soldier' to 'client_beta' branch for test).

Did anyone test proton 5.13 with a xbox controller? I tried now in Monster Hunter World and a few functions are mapped to the wrong keys.

Enabling the xbox configuration support in Steam's general controller settings fixed it. For some reason that was not needed in the previous versions.

modorganizer2's (v2.2.2.1) vfs does not work with 5.13 - works with 5.0

there are no errors but it silently fails.

I would like to add here that the cursor behavior has changed as well, I noticed this in Among Us as my mouse cursor was super super tiny on my 4K screen.

Going back to 5.0.9 uses the cursor from my window manager as expected.

I too use a 4k monitor and have noticed the tiny cursor in games. It doesn't effect games with a custom cursor though... just games that use the system cursor.

EDIT: I was wrong. All cursors are smaller then normal.

It seems like Optimus systems are also borked with Proton 5.13, due to runtime.

http://us.download.nvidia.com/XFree86/Linux-x86_64/455.38/README/primerenderoffload.html

Which means you're on Intel all the time.

While i don't have a setup that needs DRI_PRIME ( Mesa stack ) , likely it is borked too. It is used for device selection for both GL and VLK.

@Leopard1907 Seems to be borked for me with 5.13-1. Setting DRI_PRIME=1 still uses the integrated GPU instead of the discrete GPU.

I've noticed that Proton 5.13 doesn't work when I change the user to nobody. This happens as my Steam library is stored on my NFS server.

I think there are two issues with proton 5.13 and steam runtime soldier.

The changes in proton 5.13 have changed the preferred gpu for dxvk, so the following options should work for games that use dxvk. (Previously, of igpu and dgpu, dgpu was preferred.)
DXVK_FILTER_DEVICE_NAME="GTX 1050" %command%

Also previously, to use dgpu in vulkan games like doom 2016,
I was using options like VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/nvidia_icd.json", but with the steam runtime soldier won't work. (It worked by Editing _v2-entry-point to disable soldier.)

@yuiiio Thanks for this! Setting DXVK_FILTER_DEVICE_NAME works for me with 5.13.-1 where setting DRI_PRIME would not.

That's kind of a big deal, thanks @yuiiio !

I used this guide for setting up proton 5.0-9, but it doesnt work with 5.13-1 at all, since it was released.
https://community.chakralinux.org/t/how-to-use-steams-proton-to-launch-any-non-steam-apps/8236
I get the error described in #4269

re: comments in the other issue that closed, which repo should an issue for not requiring kernel.unprivileged_userns_clone go? Is that a runtime issue or a Proton issue?

Hi @kisak-valve, I don't think that the flag should be required even if Debian changes their position on it. I filed ValveSoftware/steam-runtime#297 to track this.

I've tried to set the cpu affinity for a game through taskset -c 0,1,2,3 %command% and it did not work. Is this happening for the same reason as

Using a custom per-game driver (like with VK_ICD_FILENAMES or LIBGL_DRIVERS_PATH)

?

kernel.unprivileged_userns_clone = 0 on LMDE here (debian base), and I've never had issues running games using Proton 5.13-1. Am I missing something? Does it depend on kernel version?

@Ammako that should go into the new ticket.

Regarding kernel.unprivileged_userns_clone, see https://github.com/ValveSoftware/steam-runtime/issues/297#issuecomment-722331070.

On my system (Kubuntu Linux with Plasma), Proton 5.13-1 does not automatically disable the Compositor when running Elder Scrolls Online (306130, #556) in full-screen mode, while Proton 5.0-10 does, resulting in screen tearing (and possible slightly worse performance). I've also checked this by testing whether desktop transparency effects (that require the Compositor to be enabled) are still active when running ESO is full-screen mode.

This method allows vulkan layers, overlays, etc to work while still running inside the container:

https://www.reddit.com/r/linux_gaming/comments/jc2b77/mangohud_workaround_for_proton_513/gbx4cz6/?utm_source=reddit&utm_medium=web2x&context=3

I think there are two issues with proton 5.13 and steam runtime soldier.

The changes in proton 5.13 have changed the preferred gpu for dxvk, so the following options should work for games that use dxvk. (Previously, of igpu and dgpu, dgpu was preferred.)
DXVK_FILTER_DEVICE_NAME="GTX 1050" %command%

Also previously, to use dgpu in vulkan games like doom 2016,
I was using options like VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/nvidia_icd.json", but with the steam runtime soldier won't work. (It worked by Editing _v2-entry-point to disable soldier.)

Thankyou so much for the suggestion to use DXVK_FILTER_DEVICE_NAME=, I just tried it and now Proton 5.13 works for me. Previously it didn't work for any game it seems that uses DirectX 10 or 11 (but did for DX9 games). It also worked fine if I used the Proton launch command PROTON_USE_WINED3D. I've verified Vulkan is setup and working fine on my PC, so it wasn't that.

I have a laptop with RTX 2060 and naturally an onboard Intel GPU as well, so I guess the issue was that it was defaulting to the Intel GPU and not the RTX 2060? Is there some kind of permanent solution for this?

@mindinsomnia
I recommend you to set the environmental variables inside
/etc/environment
And then reboot
Its not an elegant solution but It make permanent until you delete the entry.

@mindinsomnia
I recommend you to set the environmental variables inside
/etc/environment
And then reboot
Its not an elegant solution but It make permanent until you delete the entry.

Thanks for the suggestion!
Do you (or anyone following this discussion) know if this issue is related to Proton or DXVK or something screwy with my setup?

The changes in proton 5.13 have changed the preferred gpu for dxvk, so the following options should work for games that use dxvk. (Previously, of igpu and dgpu, dgpu was preferred.)
DXVK_FILTER_DEVICE_NAME="GTX 1050" %command%

I just wanted to confirm that this fixed my blank screen issue with 5.13, and to note that this environment variable (and instructions -- basically use vulkaninfo to find out your deviceName) is documented in the dxvk repository. It wasn't clear to me if the change in default behavior was caused by proton or dxvk, but either way, the current behavior doesn't seem ideal.

It seems like the first time setup (FTS) that is normally run when a game is started after a new install is not run when using Proton 5.13.
This made Killer Instinct crash with an error on first start.
Had to switch back to Proton 5.0, got the FTS to run ~and then I switched back to 5.13, and got the game successfully running.~
EDIT: turns out I didn't really switch back to 5.13 and kept running the game on 5.0. Proton-5.13 always make the game crash on start for me.

Deus Ex: Mankind Divided is affected by a black screen on Proton 5.13-2.
The only Proton build on which this game works is Proton 5.0-10.
Logs:
Proton-5.0-10_steam-337000.zip
Proton-5.13-2_steam-337000.zip

The same situation is with Mad Max.
Logs:
Proton-5.0-10_steam-234140.zip
Proton-5.13-2_steam-234140.zip

It wasn't clear to me if the change in default behavior was caused by proton or dxvk,

One way to test might be to try an older version of DXVK with the current version of Proton. Would that narrow down the issue?

I think Proton versions installed system-wide get not picked-up/mapped by the new runtime.
I just tested with a system-wide install of Proton-5.21-GE-1 and got:

pressure-vessel-adverb[17685]: Failed to execute child process "/usr/share/steam/compatibilitytools.d/Proton-5.21-GE-1/proton" (No such file or directory)

Should I report this on the runtime issue tracker?

will do :+1:, sorry for the spam

reshader is not working with 5.13

Network issues with Proton 5.13-1
system-info:
https://gist.github.com/nutta-git/ffccb825c1906774297247eb0d4e2f31
related:
[#4001 (comment)](https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-709665083)
[#175 (comment)](https://github.com/ValveSoftware/Proton/issues/175#issuecomment-710733727)
[#1509 (comment)](https://github.com/ValveSoftware/Proton/issues/1509#issuecomment-709639388)

Updating Issue as Proton 5.13-2 RC was released. The network issues are still present with RC.
Sysinfo: https://gist.github.com/nutta-git/9d5c15cbfa6543510f359663e13c6fb3
Logs:
thedivision-365590.log
titanfall2-1237970.log
pathofexile-238960.log
monsterhunterw-582010.log

issue has been randomly resolved :)

PROTON_DUMP_DEBUG_COMMANDS with 5.13 does not dump commands to run/debug the target inside the container runtime.

With Proton 5.13 onwards, there is no way for me to launch arbitrary executables alongside games anymore. This breaks a few modding setups that require me to launch executables after a game has started or before a game has started.

With Proton 5.13 onwards, there is no way for me to launch arbitrary executables alongside games anymore. This breaks a few modding setups that require me to launch executables after a game has started or before a game has started.

https://github.com/lazanet/protonPreloader

MangoHud is working now with latest update of SteamRuntime-Solider. I no longer need to bypass _v2-entry-point.

maybe I have a issue related with jackd2 connection and SteamRuntime-Solider (beta)

Please report any new issues separately. If people keep adding new issue reports to this one, we'll have to spend more time keeping track of what's already fixed and what isn't, which reduces the amount of time we can spend on actually fixing bugs.

Is proton completley broken atm? Getting errors like this popping up from different processes (install, running a game, etc):

wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

nstalling breakpad exception handler for appid(steam)/version(1603487799)
GameAction [AppID 471710, ActionID 2] : LaunchApp changed task to ProcessingInstallScript with ""
/data/src/clientdll/compatmanager.cpp (844) : Assertion Failed: GetCompatibilityToolCommandLineInternal on dependent tool failed
/data/src/clientdll/compatmanager.cpp (844) : Assertion Failed: GetCompatibilityToolCommandLineInternal on dependent tool failed
Installing breakpad exception handler for appid(steam)/version(1603487799)
assert_20201203080607_160.dmp[100361]: Uploading dump (out-of-process)
/tmp/dumps/assert_20201203080607_160.dmp
assert_20201203080607_160.dmp[100361]: Finished uploading minidump (out-of-process): success = no
assert_20201203080607_160.dmp[100361]: error: Couldn't connect to server
assert_20201203080607_160.dmp[100361]: file ''/tmp/dumps/assert_20201203080607_160.dmp'', upload no: ''Couldn't connect to server''
Installing breakpad exception handler for appid(steam)/version(1603487799)
_v2-entry-point[100365]: STEAM_COMPAT_APP_ID=471710
_v2-entry-point[100365]: STEAM_COMPAT_SESSION_ID=7ee99516292af1e4
_v2-entry-point[100365]: XDG_RUNTIME_DIR=/run/user/1000
Proton: Upgrading prefix from None to 5.13-1 (/mnt/thumper/SteamLibrary/steamapps/compatdata/471710/)
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
**
pressure-vessel:ERROR:../pressure-vessel/runtime.c:2441:collect_vulkan_layers: assertion failed: (details->resolved_library != NULL)
/mnt/thumper/SteamLibrary/steamapps/common/SteamLinuxRuntime_soldier/_start-container-in-background: line 156: 100377 Aborted                 (core dumped) "${run_in_steamrt}" --arch=amd64,i386 --deploy --runtime=com.valvesoftware.SteamRuntime.Platform --suite="${suite}" "${deploy}" -- --filesystem="$pressure_vessel" --filesystem="$rendezvous" --launcher --pass-fd=3 "$@" -- --info-fd=3 --socket-directory="$rendezvous" < /dev/null 1>&2 3> "$rendezvous/fifo"
ln: failed to create symbolic link ‘/tmp/SteamPVSockets.NUVFTI/SteamLinuxRuntime.7ee99516292af1e4/socket’ -> ‘’: No such file or directory
_v2-entry-point[104799]: STEAM_COMPAT_APP_ID=471710
_v2-entry-point[104799]: STEAM_COMPAT_SESSION_ID=7ee99516292af1e4
_v2-entry-point[104799]: XDG_RUNTIME_DIR=/run/user/1000
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
wine: failed to initialize: /home/vagrant/build-proton_5.13-local/dist-wine32/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory
**

o_O I hate github. Swear I searched for the error! Thanks.

Controller hotplugging is hopefully much improved in the 5.13-3 Release Candidate build. You can find more information about it on its issue: #4435 .

related with mangohud and proton 5.13... I needed to do 2 things to make it works

1. use gamemoderun and mangohud together on startup command

gamemoderun mangohud PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%

1. and add the following command in the beginning of _v2-entry-point file

shift 4
exec "${@}"

head ~/.steam/steam/steamapps/common/SteamLinuxRuntime_soldier/_v2-entry-point 
#!/usr/bin/env bash

shift 4
exec "${@}"

set -eu
me="$(readlink -f "$0")"
here="${me%/*}"
me="${me##*/}"

I believe Call of Duty: World At War's sound is disabled by this version. I've tried a handful of Proton versions, including GloriousEggroll forks, and found that 5.13+ guarantees the game will be silent, whereas previous versions (including 5.9) do not. In a cruel twist of irony, the game runs exponentially better on 5.13+, which makes researching the cause rather important to me. Peeking at pasystray reveals there isn't even a PulseAudio stream tied to the game. A friend has confirmed this on their PC, with a similar setup to mine. See my new comment, which suggests the audio issue isn't due only to the container.

Edit — here's a list of Proton versions I've tested, all with FLAA, and all follow the behavior described above: 5.21-GE-1, 5.9-GE-8, 5.13-4, 5.0-10, 4.11-13

Halo mcc doesn't seem to work properly with Proton 5.13 and Ge 5.21.1 since both of them use Soldier container. The game freezes once I log into xbox live.

5.13+ also seems to break audio in Just Cause 3, which the same friend and I independently discovered. Perhaps our audio issues are tied not to the container but to our systems (which is set up very similarly)? Reports on ProtonDB seem to never refer to audio issues for either title.

5.13+ also seems to break audio in Just Cause 3, which the same friend and I independently discovered. Perhaps our audio issues are tied not to the container but to our systems (which is set up very similarly)? Reports on ProtonDB seem to never refer to audio issues for either title.

What are your complete system specs?

@jvschiavo this lshw output should answer whatever you mean by "complete".

If you're looking for software info, it's a Void Linux 64-bit glibc install and I can throw in any info you specify

@jvschiavo this lshw output should answer whatever you mean by "complete".

If you're looking for software info, it's a Void Linux 64-bit glibc install and I can throw in any info you specify

Speaking of myself, I know nothing about this. But I'm sure @kisak-valve will find this info useful to analyze your issue.

5.13+ also seems to break audio in Just Cause 3, which the same friend and I independently discovered. Perhaps our audio issues are tied not to the container but to our systems (which is set up very similarly)? Reports on ProtonDB seem to never refer to audio issues for either title.

You're not alone. On my system audio in games launched via Proton 5.13 goes through ALSA (not pulseaudio), which only works when everything else has been silent for a while and pulseaudio has had a chance to release the audio device. When I look at pavucontrol when a game is running, it's not there: it goes directly through ALSA. This also means output via HDMI or Bluetooth doesn't work at all.

I have both libasound2-plugins:amd64 and libasound2-plugins:i386. Everything works fine in native Linux games and older Proton versions. Any idea how to debug this?

https://github.com/ValveSoftware/Proton/issues/576#issuecomment-767497909 discovered this for Resident Evil family of games (currently playable only via winetricks wmp11 workaround, which itself is broken with this version of Proton).

Starting with Proton 5.13-5, Proton experimental is affected as well, many fullscreen games start on my left monitor instead of my primary on the right side. This wasn't the case with any previous Proton versions, including 5.13-4. This is not an issue with the Runtime Container, I used the hack to disable it and it still happens.

Any affected game opens on the correct monitor when I use Proton 5.0.

@aeikum there is an issue with running Deus Ex: Human Revolution - Director's Cut on Proton 5.13-6 using D3D11 but when I use D3D9 then it works well.
The same situation is with all D3D9 and D3D11 games, e.g. GTA IV with D3D9 works well but GTA V with D3D11 doesn't.
Proton 5.0-10 is not affected by this issue.
When D3D9 is selected then my dedicated and integrated GPU's models are correctly recognized in opposite to D3D11.
@doitsujin suggested a workaround that works for me, i.e. WINEDLLOVERRIDES=dxgi=n %command%.

@jqadev Yeah unfortunately that's a known issue. We have a dev working on it, but it's quite complicated (wined3d supports both Vulkan and OpenGL, and integrating the two is challenging). Using that workaround should be fine.