Service_Code_30
Published
Game would be playable in a pinch, but I will be sticking with the windows version as long as I am dual booting.
mangohud gamemoderun %command%
Unlocked the FPS in the players/config.cfg file to match my moniter refresh rate.
Mouse sensitivity is tied to framerate which makes the sensitivity vary as you play. Had to increase the max fps in the config file to make the game playable at all.
Kino der Toten played fairly well, but the framerate varied widely between 80 - 200 FPS. Call of the Dead launched but was unplayable, fluctuating between 20 - 60 FPS. For reference, on Windows it stays locked in at 200 FPS at max settings on all maps.
Game worked fine right out of the gate, then crashed when I alt-tabbed one time. After that, the game would freeze on startup.
Maybe lowering certain settings could reduce framerate variability?
mangohud DXVK_FRAME_RATE=0 %command%
Set a keybind for increased FOV in the .../players/config.cfg file.
Mouse sensitivity tends to vary with the framerate. Increasing the max FPS can alleviate this. Also, try changing your mouse polling rate to 125Hz while playing this game.
Sometimes will freeze on startup, usually works on the second try.
The key to getting this game to run well is switching to a kernal with a PDS scheduler. With the default kernal for my distro (CFS scheduler), Call of the Dead was unplayable at 20 fps in the spawn room. After switching to the 'linux-tkg' kernal (PDS scheduler), I am now getting great performance on all the Zombies maps I have tried (150-200 FPS). Others have mentioned it in these reports and it really was night and day difference for me: https://github.com/Frogging-Family/linux-tkg
gamemoderun DXVK_FRAME_RATE=0 %command%
As of the Jan 11 steam client update, the forest cutscene crash (which has been plaguing this game for a few months) has been fixed. Played a couple rounds of zombies and it runs great. 150 - 200 FPS on my hardware, no stutters or any issues to speak of. Admitedly, FPS is slightly worse than Windows, but it is still smooth and perfectly playable now that this issue was fixed. Can finally play custom maps again!
Worked flawlessly, startup commands are not required. Similar performance as windows, runs very smooth.
mangohud gamemoderun %command%
Played a custom zombies map with a friend co-op online and it worked flawlessly. Did not try the multiplayer mode.
Custom Maps:
Custom zombies maps work solo and co-op! The location to install mods is:
.../steamapps/compatdata/10090/pfx/drive_c/users/steamuser/Local Settings/Application Data/Activision/CoDWaW/mods
- Mods in .zip format can be extracted normally (folder for each map must be named the same thing to play a custom map co-op)
- Mods in .exe installer can be opened with an archive manager and extracted (or run with Wine, install, and move files manually after)
- Mods from the UGX Map manager can be individually downloaded here: https://www.ugx-mods.com/downloads/manager/UMM.xml
FPS and FOV:
By default, the game is locked to 90 FPS (regardless of monitor settings) and 65 FOV. These can both be changed by editing this file:
.../steamapps/compatdata/10090/pfx/drive_c/users/steamuser/Local Settings/Application Data/Activision/CoDWaW/players/profiles/<YOUR_WAW_NAME>/config.cfg
Near the top, I added this line (Will work for solo, but may not work for mp, co-op, or some custom maps):
bind 0 "cg_fov 85; cg_fovMin 70; com_maxfps 170"
Screenshots:
WaW's built in screenshots will crash your game. Unbind them in the controls settings. The default Steam screenshot key should work fine.
unset SDL_VIDEODRIVER; %command%
You probably don't need any launch options. On Hyprland, I got a wayland error when starting the game and the launch option fixes it.
Works perfectly
Sometime steam overlay crashes the game but who cares.
For whatever reason, the game ran flawlessly at first. I was playing at Extreme settings getting 150FPS+ for the better part of 20 mins. Then, I went to tinker with the graphics setting and the game crashed when I applied. From that point onward, the game would launch fine but would be stuck at ~25 FPS. I can not explain why this happened after hours of troubleshooting and trying the lowest settings. I gave up and installed it on windows :(
Crashed when changing the graphics settings while in game
SDL_VIDEODRIVER=wayland gamemoderun mangohud %command%
Initially had trouble getting the game to load on my primary monitor.
- Game crashed with an error when starting the car during the "Caspian" level. Found a solution by googling.
- Whole computer froze a few seconds into the "Autumn" level cutscene. Turing down all settings to low/off allowed me to pass this point.
- Periodically it will crash with an error during the startup cutscene when loading. Launching it again usually works fine.
Played through the whole game on linux. Only a few minor crashes and bugs. From what I have read, the game is somewhat buggy even on Windows.
mangohud gamemoderun %command%
Game played well but I think it may just be generally unoptimized. This is the only game I have turned FSR on for. Struggled to pass 80 FPS, some boss fights got as low as 50 FPS which is not ideal given my hardware.
Currently, enabling voice chat or changing voip settings in menu will crash the game
I can't believe how simple this was. No launch options needed, plain ole proton expieremental. I'm impressed. They added this support silently in a "small patch" after the community was begging for it and it works nearly flawlessly. Played several games with no issues. Embark has earned my respect. Gameplay video if anyone is interested: https://youtu.be/bajHL_3YahI?si=yA_5OSAW91LmeCua
