Combat Mission: Battle for Normandy (2297010)

[SeanRamey]

Compatibility Report

• Name of the game with compatibility issues: Combat Mission: Battle for Normandy
• Steam AppID of the game: 2297010

System Information

• GPU: Nvidia GTX 1070
• Driver/LLVM version: Nvidia 530.41.03-3
• Kernel version: 6.2.10-arch1-1 (64-bit)
• system info from steam:
• Proton version: Experimental

I confirm:

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

steam-2297010.log

Symptoms

Game starts after hitting play on launcher, but crashes immediately with the message "Could not initialize OpenGL graphics. Please update your OpenGL drivers."

It seems that somebody has already found what the issue is.
https://www.winehq.org/pipermail/wine-bugs/2017-May/470327.html

and made a guide to compiling proton with the patch
https://github.com/Rufus111/combat-mission-linux-guide

[SeanRamey]

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.

[kisak-valve]

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. Install the lib32-nvidia-utils system package.

[SeanRamey]

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

[kisak-valve]

The 32 bit Vulkan render path on your system is broken due to the AMDVLK issue being tracked at GPUOpen-Drivers/AMDVLK#315.

[SeanRamey]

@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?

[Blisto91]

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 installed it probably fetched it along there. Any of them will work, but amdvlk is listed as the first option and so gets chosen by default if no active choice is made by the user or the application that installs it.

[SeanRamey]

Yeah, I got rid of it, and now Combat Mission works fine.