Playable
CoH may have problems with normal Proton but works exceptionally well on ProtonGE 9-27, I've tested various multiplayer matches vanilla and with mods (Europe at War) and it doesn't crash, not even after 1 hour of game.
If someone has audio problems, may want to use PULSE_LATENCY_MSEC=50 parameter, I've used it on other games and it adds latency but fixes any crackling or popping for me (deactivate it if otherwise).
-nomovies -refresh 144
Keyboard is not working while playing, game registers only a few keys (function row, ctrl, shift) but none of the letters or numbers work meaning you can't effectively use control groups, name a savefile etc. Tried different proton versions but none worked.
PROTON_NO_D3D11=1 -nomovies
After testing all proton and multiple commands i ended up with a " working " game. ( Proton 9-0-4 ) Sometime it will crash when lauching a mission randomly. When alt+tab it crashes the whole os.
Install it not on a NTFS HDD
Wollte nicht von meine zwei Festplatte mit NFTS formatirung starten. Auf die Haupt SSD geschoben und es läuft. 119.95FPS (Windows 99.5FPS) Benchmark
PROTON_NO_D3D11=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% -dev -mod EasternFront -w 1920 -h 1080 -nomovies
Changing the resolution or graphics settings causes the game to break. Set resolution with launch options, and use resets to get graphics settings if needed.
Crashes when match starts if on older version of Proton. Stay on latest build.
For Nvidia users, use the Nvidia Control Panel to enable Threaded Optimization for better performance and stability. Make sure that screen edges are off if you're on KDE Plasma to not interrupt the game. I also included options for 1080p (You can set your own resolution), the ability to load Eastern Front mod (Use this for the base game), and the ability to skip the intro to hop in the game. These are mostly optional as long as everything before %command% is included.
PROTON_NO_D3D11=1 %command% -nomovies
Crashed every time when trying to start a mission/in-engine cutscene unless I disabled D3D11
PROTON_NO_D3D11=1 %command% -nomovies
PROTON_NO_D3D11=1 does mean you can't enable Ultra for some graphical settings, but without it the game crashes.
It just works!
runs fine without any problems
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_NO_D3D10=1 %command% -nomovies -novsync
Sometimes starts it through Lutris to disable screensaver during play. It takes a long time to validate all the great maps from workshop, during which the screensaver might kick in, causing an X11 window failure. I'm running on Wayland.
Without disabling fsync and esync the game crashes to desktop one hour into the game. Proton log always shows lots of "EXCEPTION_WINE_CXX_EXCEPTION exception (code=e06d7363) raised". Years ago, on my older system with GTX970 and i7, the game just worked out of the box. I suspect the AMD 6800XT, but everything is new now, forcing me to run on mainline kernel.
PROTON_NO_D3D10=1 gamescope -w 1920 -h 1080 %command% -refresh 120 -nomovies -window -fullwindow -forceactive
It may work without gamescope as well, but I generally prefer enabling it. Parameters after %command% were required, otherwise there was only black screen on gamescope or no window at all without it - https://steamcommunity.com/app/231430/discussions/3/3090011896384600038/
PROTON_NO_D3D10=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1
Lowered the game settings very low and gradually increased them again to stop vc crash during loading of next scenerio
Initially I couldn't get past the first scenerio
Works with an older Proton version and the mentioned launch options. But crashes every few hours. Some missions have bad performance.
PROTON_NO_D3D11=1 %command%
Switched ALT and SHIFT back grip buttons, set D-PAD to attack on top, retreat on bottom, pause on right. Set right stick to zoom in/out on moving to top/bottom.
Some missions suffer from bad performance at high settings. Others run perfectly fine. Cutscenes run at a stuttery framerate, but this is likely not a performance issue, but an issue with the game itself.
The game is prone to unpredictable crashes during the campaigns. Save often.
Without launch options, the main menu loads, but you can't load into a game. With launch options and newer Proton versions, you can play, but specific campaign missions crash on load with an error. Currently this older Proton version in combination with the launch option appears to work fine for the missions that crashed before.
PROTON_NO_D3D10=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1
IMPORTANT: Use PROTON_NO_D3D10=1, do NOT use PROTON_NO_D3D11=1, otherwise the Steam Overlay will freeze your game when you open it via Shift+Tab
Other than the Alt+tab thing, the game runs perfectyl fine out of the box
When you Alt+Tab, there's a ~50% chance that you won't be able to fully fullscreen back untill your restart the game
Works with the mentioned launch options. Otherwise opens menu and crashes upon launching into a game.
PROTON_NO_D3D11=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
Switched ALT and SHIFT back grip buttons, set D-PAD to attack on top, retreat on bottom, open map on left. Set right stick to zoom in/out on moving to top/bottom.
PROTON_NO_D3D11=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
This was brief and only occurred during some cutscenes.
Game crashed after playing for about a couple of hours.
Game crashed after a few hours of play. This is acceptable to me for this game. I had to use extra launch options to get the game to play. A previous report about me using glorious eggroll was incorrect. I was not in fact using GE at the time.
Game locks up my computer and restart is the only fix.
Game locks up my computer on launch. Can't switch workspace to run terminal and kill game process with CLI. Power cycle via power button is the only fix.
PROTON_NO_D3D11=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
Without launch options PROTON_NO_D3D11=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% it didn't start
Issues only occurred when I tried to run the game with Deck connected to an external display. Crashes occurred the first time I tried launching on external display, and when I tried to run the graphics settings benchmarking tool. (To run on external display I changed the display resolution in the game's Steam Properties.)
Playing this game with Deck docked to external display may require minor tweaking, depending on your setup. However, once you do get it running, the game performs well even in 2K (not upscaled) resolution.
MSVC Error
PROTON_NO_D3D11=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
Produces a MSVC error on recent version of Proton, on older <6, does not start.
needed to add PROTON_NO_D3D11=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% to make it work. From some older report
PROTON_NO_D3D11=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
command line comment needed as above
Crash at start
PROTON_NO_D3D10=1 didn't fix de issue.
Using PROTON_NO_D3D10=1 helps with the crashes.
Using PROTON_NO_D3D10=1 helps with the crashes.
The game runs with no issues or crashes at all (played several games for 3+ hours straight), providing the same experience as it does in Windows, including multiplayer which works flawlessly.
If you get "Compatibility tool configuration failed" error - I did and had no idea why - just reinstall Proton and Steam Runtime. If Steam doesn't let you to, delete local files in the ./common folder on your own, and get them back by verifying integrity of the files in Steam.
Works okay.
Sometimes audio stops playing.
Crashes loading 2nd mission. You cannot play campaign past that
Always crashes loading 2 mission. No way (as far as I know) to bypass the mission, so it's impossible to continue the campaign
The game occasionally crashes, frequently after the hour of play has passed.
Use the launch option PROTON_NO_D3D10=1 to run the game, due to occasional crashes, it is recommended to save the games frequently after an hour of games, to avoid losing progress
PROTON_NO_D3D10=1 and forcing the Proton 6.3 on the game in the compatibility options make it work for me
Only PROTON_NO_D3D10=1 and forcing the Proton 6.3 on the game in the compatibility options make it work, but after ~1h30m it crashes again
Ryzen 3600, RX580 8GB, 16GB RAM
As long as you use launch option: PROTON_NO_D3D10=1. I think the majority of problems would stop.
Fixed with launch option:
PROTON_NO_D3D10=1
Randomly crashes during mission loading
Often crashed during mission loading. Starting the game (sometimes multiple times) resolved it and the next mission loaded fine. Only tested with tutorial and the first two missions.
