ngoomie
Published
Tutorial works, but once you finish it you're screwed
The game throws you into a tutorial directly after the splash screen if it's your first time playing which does actually work, but then if you attempt to exit from the tutorial to the title screen, the game will crash. If you finish the tutorial, then the game will send you to the title screen, and once again crash, and then after this point will never again automatically enter the tutorial on launch, thus causing the game to always crash after displaying the splash screen.
Without tinkering, will throw error "src/tcmalloc.cc:390] Attempt to free invalid pointer" on some systems and instantly crash.
Replace lib shipped with game with a version you install yourself
To fix this issue, the libtcmalloc_minimal.so.0 file in game/bin/linuxsteamrt64/ must be replaced with a libtcmalloc_minimal.so.* file you grab from either package gperftools on some systems or gperftools-lib on others (for me it was provided by the first package). The file you need will probably be in /usr/lib64/. The version number at the end doesn't need to match, just make sure you overwrite the version shipped with the game with the new one instead of having both coexisting in the game folder.
This seems to be related to a bug documented as happening with Source 1 games if launched with -vulkan: https://github.com/ValveSoftware/csgo-osx-linux/issues/2887#issuecomment-994243273
The game reported that I was offline, thus I was unable to even really play the game, as co-op was what I had intended to do, here.
In addition to the online issue, it's probably worth a note that the game yelled at me about how my PC's specs are below the minimum requirements, even though I'm pretty certain mine exceed even the recommended requirements, so that makes me wonder if the internet issue was because it just couldn't detect any of my hardware or other setup at all. That's just a guess, though. Good chance I could be wrong.
Runs briefly and then stops
Game does not even briefly spawn a window or anything of the sort. It just shows up as running for under a second and silently dies.
Easy Anti-Cheat settings have been changed and now the game no longer works on Linux
My config is the exact same as it was a couple of months ago when I was actively playing the game regularly before taking a break to focus on other things. Seems with the recent big update they've changed their EAC version/config/etc and now the game just doesn't work on Linux.
Game works generally fine minus completely missing sound (which I admittedly find very irritating) and one super minor graphical issue.
There's just no audio, plain and simple.
On the little balloon that shows you how many troops are inside a building, there's a sliver of white at the bottom between the coloured area and the outline, like the coloured area is slightly misplaced. Really not that big of a deal, and probably not even noticeable if you've never played in on Windows before.
Doesn't work, don't bother with the Linux native version, just use the Windows version in Proton instead.
The entire screen was red and black on first launch, on subsequent launches it only happens after either tabbing out of and back into the game or adjusting 3D acceleration settings.
Framerate is choppy during cutscenes, but is completely fine otherwise.
Using Proton 5.13-6 fixes the red and black graphics after tabbing out and back in issue, and using the popcapgame1 executable as described by previous reporters fixes issues with cutscene lag.
Perfect except for one small issue
Minimizing the software while it's in the boot process or switching workspaces will sometimes cause the screen to go black and become entirely unresponsive.
Other than the odd blackscreen issue, it's generally perfect. The blackscreening is also somewhat infrequent so it's not too disruptive.
Works pretty much perfectly, the only problem is that the web browser in the Steam overlay is almost unbearably laggy to use, but I tend not to really use it anyways so it's nbd
Game sits at a black screen with all of my tinkers, doesn't even launch otherwise
Added KeepRes=1 to conquests.ini
Even removing the KeepRes tinker (which seemed to be what caused the blackscreen) and trying again to see if I could just play windowed and move the window into the middle of my screen (and maybe use GameScope or something), the game would keep blackscreening. It just really didn't like me making that change, I guess!
Fullscreen would take up only a small portion of the upper left corner of my screen
After playing the game for not even that long of an amount of time, the game will cause my PC as a whole to force restart itself. There's no rhyme or reason to the crashes, and no other game I have does this, so I can only assume it's a problem with the game itself.
Game doesn't even run, I'm having the same error others have mentioned already.
With or without tweaks, it doesn't matter. Game's broken.
Getting it working is like playing Russian Roulette
This game tends to work flawlessly on the occasion that it does work, but it works so infrequently that I can't in good faith mark it as working. Whether on my computer or laptop, on any version of vanilla Proton or GE Proton, or whichever Linux distro and kernel I'm using, most of the time when I open it it'll say its running but no window will ever appear. The real kicker is it worked the other day when I opened it briefly just to check if it'd work, and now that I want to actually play it again I can't :(
It's a gamble as to whether the game will even launch when you try to run it, sometimes it runs on less than half of my attempts to launch it. This is the case with or without any form of tweaking. Works flawlessly when it does run, however.
Proton-7.0rc3-GE-1, replacement Japanese fonts installed with protontricks
Even when forcing the locale to EUC-JP as suggested by another submitter (and SHIFT-JIS too just in case), the Japanese text is mojibaked. I could get the missing font issue fixed very easily with protontricks, but that doesn't mean much when the text is rendered unreadable otherwise, in this case by the wrong text encoding being used. Worth noting though that I'm not quite sure if I generated the ja-JP.eucJP locale correctly as I've never used localedef before and am instead only really used to locale-gen.
Looks like it works just fine if you intend to play it in English, though.
