Combat Mission: Battle for Normandy

Combat Mission: Battle for Normandy proton open

• SeanRamey · 2023-04-15 · Combat Mission: Battle for Normandy
  Yeah, I got rid of it, and now Combat Mission works fine.
• Blisto91 · 2023-04-13 · Combat Mission: Battle for Normandy
  You can get rid of it fine ye. Steam installed through Pacman (or any software utilizing it) on Arch based distros require one of the the 32bit Vulkan drivers as a dependency, so if you didn't have one when steam was ins...
• SeanRamey · 2023-04-13 · Combat Mission: Battle for Normandy
  @kisak-valve So, why do I even have amdvlk installed since I don't have an AMD gpu? Can I just get rid of it, or is it part of the linux kernel?
• kisak-valvemaintainer · 2023-04-12 · Combat Mission: Battle for Normandy
  The 32 bit Vulkan render path on your system is broken due to the AMDVLK issue being tracked at https://github.com/GPUOpen-Drivers/AMDVLK/issues/315.
• SeanRamey · 2023-04-12 · Combat Mission: Battle for Normandy
  @kisak-valve I tried installing that, and the game no longer crashes with that error message. But it does crash upon startup, this time straight to desktop without any kind of message. Here is the new log: [steam-2297010...
• kisak-valvemaintainer · 2023-04-12 · Combat Mission: Battle for Normandy
  Hello @SeanRamey, looking at your system information, your NVIDIA video driver install is missing the driver's 32 bit userspace libraries and Steam is falling back to mesa's faster CPU renderer, llvmpipe, to run at all. ...
• SeanRamey · 2023-04-12 · Combat Mission: Battle for Normandy
  Well, after personally trying this patched version, it did not solve the issue. Maybe I did something wrong? But I'm not sure what it could have been.