Keep in mind that first time you launch it after downloading it, don't cancel DirectX installation. Otherwise, you get missing sounds.
Also that caveat should be fixed by https://github.com/ValveSoftware/wine/issues/2
Crackling sound in all games
Issue transferred from https://github.com/ValveSoftware/Proton/issues/1395.
@PureTryOut posted on 2018-09-11T15:22:19:
Sound crackling in every game. It doesn't always happen, and for some games it happens more than others (for example in Call of Duty: World at War it happens about 90% of the time, where with GTA5 it happens about 20% of the time and only after playing for a bit).
I've uploaded a sound fragment from a game of COD:WAW where you can hear it clearly (a .wav in a .zip).
cod-crackling-sound.zip
I wonder how many games couldn't be basically summed up with "wait for FAudio"
Are you a GPU passthrough user by any chance @PureTryOut?
I have the exact same audio issues in some games on wine/proton including this one but it only happens if a guest VM has been started that boot, apparently it is a known iommu bug but no one knows the exact cause.
If no vfio VM is ever started then audio is fine in wine and it's forks.
I do not, I see no reason to with Proton. Anyways, it's already resolved (a workaround) in #120.
I have no issues, everyhing works fine (even multiplayer).
The performance hit on W@W is nasty (my Vega 56 can only get 45FPS in zombies solo, min settings).
UPDATE: trying to run the game using PROTON_USE_D9VK=1 %command%, with or without T4M, runs at the same low framerate as before, except this time it crashes upon loading a map. Also, removed T4M comment for being irrelevant.
Call of Duty World at War crash with Proton 4.11.11 ( does not use DXVK because DirectX installation)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3351.
@iWeaker4you posted on 2019-12-22T21:29:31:
DirectX installation causes the game not to start with the D9VK dll (DXVK 1.5 ), i use the PROTON_USE_D9VK=1 %command%, it works but in certain points crash , the first time crashing at 5 minutes, in the second attempt crashing at 20min.
Hello @iWeaker4tyou, the log has a bunch of err: DxvkMemoryAllocator: Memory allocation failed, which hints that you encountered https://github.com/doitsujin/dxvk/issues/1100#issuecomment-552784194. You might get lucky trying PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_USE_D9VK=1 %command% in the game's launch options.
@kisak-valve thanks, its works very well with PROTON_FORCE_LARGE_ADDRESS_AWARE=1, no crash anymore.
Call of Duty World at War Crashes with DXVK
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4256.
@billybob32 posted on 2020-10-12T01:12:09:
<Proton log omitted, please see [#4256](/issue/ValveSoftware/Proton/4256)>
Game just doesn't run. It runs for a bit, then crashes. used to crash my whole pc. Now it just crashes the game.
I just have to launch it on steam, it crashes. Forcing it to not use DXVK with PROTON_USE_WINED3D=1 %command% fixes the issue.
Hello @billybob32, since this issue report was last commented on, PROTON_FORCE_LARGE_ADDRESS_AWARE was enabled by default with Proton 5.0, so there's no point in testing that. It would have been nice to have had the extended diagnostic information in your system info to confirm that you have a working 32 bit vulkan driver stack. Please verify that mesa-vulkan-drivers and mesa-vulkan-drivers:i386 are installed with something like apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386.
Also, it may be worthwhile testing a newer mesa build from a PPA like oibaf or kisak-mesa.
I've noticed that while the game runs well enough, some audio is missing. Repairing barriers and opening doors in zombies are particularly common offenders. I've confirmed this on all versions since 4.11, including 5.13-5 with the latest beta SLC Soldier
I find the game runs perfectly with and without mods using Proton 4.11-13.
However when using the latest version of Proton 8.0-4, the game runs fine without mods, but if not all zombie maps mods will not load and cause the game to either crash or freeze when loading the zombie map.
Here are the logs for this using Proton 8.0-4 loading Nacht Der Untoten Reimagined (Version 2.1) mod.
What about 5.0, 5.13, 6.3 or 7.0?
I get the same results with 7.0 as I do with 8.0-4.
Call of Duty: World at War immediately stops after pressing the play button in Steam when the game is installed to my HDD I mounted to /mnt/7200RPM_HDD.
/home mount pointHello @bigjoe54321, the noexec lines in your Proton log point towards there being an issue with the execute permission on the partition used with your secondary Steam library folder.
Thanks for your reply, @kisak-valve. I tried the following fixes, but the main problem still remains.
fd -H -tf -e exe . . -X chmod +x -c in /mnt/7200RPM_HDD/SteamLibrary/steamapps/compatdatafd -H -tf -e dll . . -X chmod +x -c in /mnt/7200RPM_HDD/SteamLibrary/steamapps/compatdatafd -H -tf -e exe . . -X chmod +x -c in /mnt/7200RPM_HDD/SteamLibrary/steamapps/common/Call of Duty World at Warfd -H -tf -e dll . . -X chmod +x -c in /mnt/7200RPM_HDD/SteamLibrary/steamapps/common/Call of Duty World at WarHere's a new log:
steam-10090.log
I think I figured out what you meant, because of what this command showed me. I'll learn how to remove noexec. I just learned that noexec is not in my fstab file.
❯ mount | rg "btrfs.*noexec"
/dev/sdb1 on /mnt/5400RPM_HDD type btrfs (rw,nosuid,nodev,noexec,noatime,compress=zstd:3,space_cache=v2,commit=120,subvolid=5,subvol=/,user)
/dev/sdc1 on /mnt/7200RPM_HDD type btrfs (rw,nosuid,nodev,noexec,noatime,compress=zstd:3,space_cache=v2,commit=120,subvolid=5,subvol=/,user)
I found this.
https://man7.org/linux/man-pages/man8/mount.8.html#:~:text=This option implies
the options noexec
users Allow any user to mount and to unmount the filesystem, even when some other ordinary user mounted it. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line users,exec,dev,suid)
It seems the problem will be fixed after I make the following change to my fstab file:
-UUID=4de52f34-a880-40e6-8131-c316a9c2a554 /mnt/7200RPM_HDD btrfs noatime,compress=zstd,commit=120,user 0 0
+UUID=4de52f34-a880-40e6-8131-c316a9c2a554 /mnt/7200RPM_HDD btrfs noatime,compress=zstd,commit=120,user,exec 0 0
Yes, adding the exec option to that line in fstab fixed the problem 🙂 Thanks again for your help, @kisak-valve.
proton experimentalx1 2026-06proton 4.11-13x1 2023-11proton 8.0-4x1 2023-11proton 5.0x1 2020-10proton 4.11x1 2019-12PROTON_FORCE_LARGE_ADDRESS_AWAREx1 2020-10PROTON_USE_WINED3D=1x1 2020-10PROTON_FORCE_LARGE_ADDRESS_AWARE=1,x1 2019-12PROTON_USE_D9VK=1x3 2019-12PROTON_FORCE_LARGE_ADDRESS_AWARE=1x1 2019-12PROTON_USE_WINED3D=1 %command%x1 2020-10PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_USE_D9VK=1 %command%x1 2019-12PROTON_USE_D9VK=1 %command%x2 2019-12
Has been working really well, there are no issues other than the expected performance hit of dx9 translation.
I did not even bother with punkbuster though as you need a 3rd party fix for that even on windows, the game still works perfectly without it sans joining PB servers.