Anybody have an up-to-date experience using Proton for this game?
I notice kisak's comment about the game using CEG, which likely means it can't simply run with Proton and must instead use Windows version of Steam? (through own Wine prefix)

I just noticed Steam client now allows forcing Proton version on games that have native versions as well, so I'm interested to try it with Civ 5.
There are simply too many great mods out there that use DLL, which simply won't work with the native version.
Some mods also require various tweaks to run stably, which are frankly annoying in the long run (case-insensitive config directory, among other things).

EDIT: Not having a good time with Lutris. The game caused the rest of the desktop to lag unbearably when using Steam Windows + Wine.
Unable to run through Steam Linux, possibly due to that CEG stuff.

https://github.com/ValveSoftware/Proton/issues/753#issuecomment-954380381 https://github.com/ValveSoftware/Proton/issues/753#issuecomment-954541587

With the Steam client beta and Proton experiential Civ 5 works now.

The game works but opening the steam overlay with shift+tab crashes the game. Anyone else getting this? I'm using Proton Experimental.

DirectX 9 - works with proton experimental. DirectX 10/11 - works until I accept and proceed (first screen before main menu). (Radeon, kisak ppa for mesa)

DirectX 9 - works with proton experimental. DirectX 10/11 - works until I accept and proceed (first screen before main menu). (Radeon, kisak ppa for mesa)

I have the same problem: loading screen, than crash after i click on "accept and proceed". Tried both Proton Experimental and GE-Proton7-48.
steam-8930.log

Thanks for linking me into this ticket.
I did notice a bit of instability, but for the most part the game ran rather smooth with the exception of instantly crashing if I launch the steam overlay.
I can alt+tab, click on different monitors... so on. But not use steam overlay.

Final lines from the error log are the following:

23570.742:0310:0314:trace:seh:__regs_MSVCRT__setjmp3 buf=06B1F9D4 ebx=00000000 esi=565c84b0 edi=00000000 ebp=06b1fa1c esp=06b1f9bc eip=0016a1f8 frame=06b1ff20
23570.742:0310:0314:trace:seh:__regs_MSVCRT__setjmp3 buf=06B1F724 ebx=00000001 esi=565ca670 edi=00000000 ebp=06b1f76c esp=06b1f70c eip=0016a1f8 frame=06b1ff20
23570.746:0310:0314:trace:seh:__regs_MSVCRT__setjmp3 buf=06B1FD24 ebx=80011600 esi=5ac85ad0 edi=00000000 ebp=06b1fd6c esp=06b1fd0c eip=0016a1f8 frame=06b1ff20
23570.746:0310:0314:trace:seh:__regs_MSVCRT__setjmp3 buf=06B1FD24 ebx=80011600 esi=5ac862f0 edi=00000000 ebp=06b1fd6c esp=06b1fd0c eip=0016a1f8 frame=06b1ff20
23570.746:0310:0314:trace:seh:__regs_MSVCRT__setjmp3 buf=06B1FD24 ebx=80011600 esi=5b265a30 edi=00000000 ebp=06b1fd6c esp=06b1fd0c eip=0016a1f8 frame=06b1ff20
23570.746:0310:0314:trace:seh:__regs_MSVCRT__setjmp3 buf=06B1FD24 ebx=80011600 esi=5b269590 edi=00000000 ebp=06b1fd6c esp=06b1fd0c eip=0016a1f8 frame=06b1ff20
23573.762:0310:0314:fixme:steamclient:Steam_BGetCallback HACK: Steam overlay activated, disabling all input events.
pid 140982 != 140981, skipping destruction (fork without exec?)

Civilization V native Linux version from Aspyre worked, but would crash after increasingly shorter intervals while playing and also couldn't persist resolution settings.

So I decided to switch to Proton. So far, I've tried 8.0-2, 7.0-6, Experimental, 6.3-8 (in that order).
Every time, the Civ starter would kick (with DirectX version setting), and then clicking on Play, the game would just crash without further visual errors (regardless of the chosen DX version). 7.6 would at least show the loading fullscreen image for a short time.

So, currently, this game is not working at all; I do remember it working perfectly some 3 years ago, though.

This is pretty ugly, since to me, Civ V is better than Civ VI (which doesn't work either, btw.).

I must say, I find it pretty upsetting, getting set back to point 0 every few months, finding some favorite game just doesn't work anymore, for no obvious reason.

AMD Ryzen 7 5700X
Radeon RX 580
AMD Ellesmere HDMI Audio
Kernel 5.4.0-148
X.Org 1.20.13 driver: amdgpu
OpenGl 4.6
Mesa 21.2.6 direct render: Yes
Linux Mint / Ubuntu 20.04 focal

EDIT:
Launching again with 6.3-8, DX 9 installation would kick in again and after that, trying to run the game (with DX 9), the loading image was presented, like with 7.0, but then crash again.

Thanks for the hint, but, as pointed out, earlier versions suffer from the same issue, not starting at all, or at least not beyond the loading screen. I've reset to Aspyr's Linux native and are back to the old behavior of the game running, but crashing after a some more or less prolonged gaming. When leaving the initial low resolution (1366x768) I could play significantly longer, before things went south, actually some 2+ hours. So, the lower resolution may or may not have had an impact here.

EDIT:
My outdated Mesa version might point to the general problems I seem to encounter with Proton 8.x, of course, I'd need to verify that.

After upgrading my system (Kernel 5.15.x, Mesa 22.2.5), the native Linux mode (by Aspyr) sadly still suffers from the same crash problems, but gladly, Civ V now seems to work fine with Proton 8 and DirectX 9 and 11 (didn't try 7 and Experimental). Also setting and persisting video options works now. So: problem solved!

UPDATE: at first everything seemed fine after the system upgrade, but shortly after things went haywire, at a point where the "2k launcher" updated itself and never finished this job. After forcibly shutting down the installer from the Steam lib, the "2k launcher" and thus the Civ V installation was corrupted beyond repair and the launcher would crash every time.

Maybe due to trying to switch from Proton 8 to Experimental also Civ V was damaged and I had no choice but to delete the "2k launcher" entry and prefix from Steam, re-install the launcher and download and install Civ V into a completely new prefix, copying the backed-up savegames from the previous installation there, afterwards.

Now, Civ V sometimes will run for hours, oftentimes it will crash on the first one or two starting attempts while loading the last savegame, shortly after the music starts to play and breaking up with a crackling. After prolonged playing, the risk of crashing seems to rise and occurs almost inevitably after longer time, albeit not as frequently and often, as with the Linux native version.

Btw., I haven't activated Steam overlay, so this should be no issue here.

Also experiencing major issues, went back to 6.3-8, at least the game is almost stable now. Steam overlay still broken.

Using Proton 8.0-4 on a 64 GB Steam Deck running latest stable branch will cause Civ V to crash after around or under 15 minutes of playing. The crash restarts the Deck each time. I’m about to test proton Hotfix. I will edit this post if it works. First Edit: Proton 8.0-5 and Experimental did not fix this issue. Edit: Issue occurs in Hotfix too.

Can confirm, but this issue started occuring recently, after they have removed the 2k launcher.

For me, the game doesn't launch at all with Proton. I've tried every version available from 6.3-8 to Experimental, to Hotfix. Steam prompts me for a DX version. No matter what I pick, Steam says "Updating executable" for some variable amount of time, then the button reverts from "Cancel" to "Play."

For me, the game doesn't launch at all with Proton. I've tried every version available from 6.3-8 to Experimental, to Hotfix. Steam prompts me for a DX version. No matter what I pick, Steam says "Updating executable" for some variable amount of time, then the button reverts from "Cancel" to "Play."

Then it's dead somehow. I've also had this issue several times. In this case, try uninstalling and re-installing Civ V again.

Thanks. I guess second time's the charm because I had tried that once already, but doing it again fixed the issue. Maybe it was the moving it to a different drive then back? Or the verifying game cache in between? Not sure, but it seems to work now.

Sound's great! Please take care with moving this game into a different storage. It completely broke for me, and i had to reinstall Steam.

Thanks. I guess second time's the charm because I had tried that once already, but doing it again fixed the issue. Maybe it was the moving it to a different drive then back? Or the verifying game cache in between? Not sure, but it seems to work now.

Moving a game to a different drive or changing Proton version (which basically generates a whole new 'pfx' Wine/Proton prefix folder for the game, can lead to trouble.

When the game is located on a game library folder, that's not mounted at boot time, trying to start it will fail, so either you open the corresponding drive once each time before starting Steam, or you create an entry in /etc/fstab (which is certainly the better option in the long run).

Meanwhile Steam seems to have mitigated the issue of bloating the 'steamapps/compdata' folder with dangling prefixes, created for each Proton version tryout for each game, by deleting the previous version's prefix upon choosing a different one - at the price of having to re-create it each time.

Thanks to Steam's obfuscated game and pfx folder numbering system, things will get messy sooner or later, unfortunately.

Keeping track of which proton installations and game prefixes are still alive and well and belong to which game folder and steam configurations, is almost impossible, unless you've got nothing better to do.

With Lutris, installations are much more transparent and simpler. Just download your game installer, e. g. from GOG or directly via Lutris and it gets installed in its own, aptly named prefix, with the Wine or Proton version of your choice.
It's also easy to apply .exe patch files to the Lutris game prefixes.

You just get back the control you need to solve problems on your own, without all the distractive bloat. No DRM, no horrible startup times, just pure bliss.

Can confirm, but this issue started occuring recently, after they have removed the 2k launcher.

This is exactly my experience as well. WTF did they do when they removed the launcher?

Can confirm, but this issue started occuring recently, after they have removed the 2k launcher.

This is exactly my experience as well. WTF did they do when they removed the launcher?

It's heavily annoying at the moment tbh.