Proton: Call of Duty: World at War (10090)

[Vaporeon]

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.

[xDShot]

Keep in mind that first time you launch it after downloading it, don't cancel DirectX installation. Otherwise, you get missing sounds.

[Vaporeon]

Also that caveat should be fixed by https://github.com/ValveSoftware/wine/issues/2

[kisak-valve]

Crackling sound in all games

Issue transferred from https://github.com/ValveSoftware/Proton/issues/1395.
@PureTryOut posted on 2018-09-11T15:22:19:

Compatibility Report

• Name of the game with compatibility issues: all games, but some worse than others, using COD:WAW for this
• Steam AppID of the game: 10090

System Information

• GPU: RX480
• Driver/LLVM version: Mesa 18.2/6.0.1
• Kernel version: 4.18.7
• Link to full system information report as Gist: https://gist.github.com/PureTryOut/ffad4816866322e165dd4047f009c4f9
• Proton version: any, but right now 3.7-6 Beta

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.

Symptoms

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

Reproduction

1. Launch COD:WAW
2. Open the server browser, you'll hear explosions in the background which should crackle
3. If the sound doesn't crackle, you've caught the lucky 10%, and you have to restart the game

[mirh]

I wonder how many games couldn't be basically summed up with "wait for FAudio"

[Vaporeon]

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.

[PureTryOut]

I do not, I see no reason to with Proton. Anyways, it's already resolved (a workaround) in #120.

[Holzhaus]

I have no issues, everyhing works fine (even multiplayer).

[wundrweapon]

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.

[kisak-valve]

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:

Compatibility Report

• Name of the game with compatibility issues: Call of Duty World at War
• Steam AppID of the game: 10090

System Information

• GPU: GTX1050
• Driver/LLVM version: NVIDIA 440.43.01
• Kernel version: 5.4.6-arch1-1
• Proton version: 4.11.11

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-10090.log

Symptoms

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.

[kisak-valve]

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.

[iWeaker4you]

@kisak-valve thanks, its works very well with PROTON_FORCE_LARGE_ADDRESS_AWARE=1, no crash anymore.

[kisak-valve]

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:

Compatibility Report

• Name of the game with compatibility issues: Call of Duty: World at War
• Steam AppID of the game: 10090

System Information

• GPU: AMD R5 M430
• Driver/LLVM version: Mesa 20.0.5
• Kernel version: 5.4.0-48-generic
• Link to full system information report as https://gist.github.com/billybob32/a5da6bab842d3bdc4ebb1a9891a0a179
• Proton version: 5.0-9

I confirm:

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

<Proton log omitted, please see #4256>

Symptoms

Game just doesn't run. It runs for a bit, then crashes. used to crash my whole pc. Now it just crashes the game.

Reproduction

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.

[kisak-valve]

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.