Shadows have red tint, had to be disabled in-game with Alt+W, then graphics are normal, probs OpenGL bug with Intel GPUs with game, Intel iGPUs have issues on Windows as well
__GLX_VENDOR_LIBRARY_NAME=mesa %command%
Same as other CM games: this game used to work fine starting with Proton 8. Something has changed with the recent Nvidia OpenGl drivers (or packaging) where I can only run it with mesa/zink, but performance and playability is not really impaired on a decent system and it runs fine with this workaround.
On Proton Experimental, the Main Menu flickers heavily. This can be fixed by switching to Proton 8.0-5.
Now works without any Tinkering required thanks to the newest proton version. Perfect Wargame on the go for the Steam Deck.
Fails to load into Battles from time to time
Flickering initial menus, but all good once in a mission
Menus outside missions will often start flickering a lot.
Works fine out of the box. Custom patching no longer needed.
It don't open without tinkering (patching and compiling Proton)
As others have noted you have to compile proton from source with a patch for the game(and any combat mission games) to start. The good news is that once you do so the game runs perfectly. There are various visual issues such as LOD flickering, aliasing and odd looking lighting, but this is actually working as intended - the game engine is old and quirky and these oddities are also present on Windows. Performance is also poor, but again it's the same as Windows.
As stated in previeous review... I had to compile my own Proton after patching the cAlphaShift settings.
With the cAlphaShift patch compiled in to proton, the game starts and runs, I was able to play singleplayer fine.
cAlphaShift patch: https://www.winehq.org/pipermail/wine-bugs/2017-May/470327.html required to launch the game itself.
game world sometimes LODs, becoming low-res then high-res again. does not impact gameplay.
Opening the steam overlay breaks the game, so I disabled it. Switching workspaces in i3-wm worked fine.