Hi,
i'm also interested on this bug, even if i never tried the window version of the game yet. i don't know if someone have noticed this, but probably the reason of why civilization 6 (linux version) run so bad is simply because it is not a porting, but they ship the window client with a preconfigured wine environment to run it (if you look at the folders you will find "wine64steam" with window client inside). Obviously the shipped wine is old, without dxvk and probably even esync. Anyway, this is a good news since this means that a way to run it on wine (and so in proton) exist since the linux version already use wine. Do you think is possible to give a look at the wine prefix and configuration shipped on the linux version and make the same settings for a general wine (or proton) version? So it can be run with all the new features like dxvk, esync and so on.

I just want to add, that although there is a "working" Linux version of the game, there still is a very crucial feature missing in it. This feature being that unified cross-play multiplayer, which allows both Steam and Epic Games players to play with each other. I do not know why, but it is simply missing in the main menu of the Linux version. If devs would support this for Linux, there would be no real necessity for a working Win/Proton version...

I just want to add, that although there is a "working" Linux version of the game, there still is a very crucial feature missing in it. This feature being that unified cross-play multiplayer, which allows both Steam and Epic Games players to play with each other. I do not know why, but it is simply missing in the main menu of the Linux version.

Unfortunately that has nothing to do with wine/proton, but simply the developers have decided to make the two clients incompatible. Even on Window you cannot connect between Epic and Steam clients.
Don't get me wrong, i agree that this choice make no sense, it probably come from some strange commercial agreement.

Also i would like to make notice that making Window client working on Linux will allow to play online immediately after a patch, since, as i have noticed, Linux user have to wait that the Window patch is adapted for the Linux client, making impossible to play online during that time due to version mismatch. Honestly i feel like a "second class citizen", even if i pay for the game the same amount of Window users.
For this reason, even if Civilization 6 have a """"Linux Client"""", is important to get it working directly from Window version with Wine/Proton, so we don't need to depend from anyone.

The windows version does have the capability to play with steam and epic players. Already played tons of hours this way. It just isn't present on Linux.

The windows version does have the capability to play with steam and epic players. Already played tons of hours this way. It just isn't present on Linux.

Oh, you are right, i was sure about that, sorry. So in this case seems that the ""Linux Client"" have some differences from the Window Client that make them incompatible, on both Window and Epic (even if at the end it is wrapped inside a Wine Machine).

Edit: i read wrong, the folder name is "win64steam". Anyway it is strange that there are Window binaries inside Linux client

System Information

• GPU: RX 580
• Driver/LLVM version: Mesa 20.3.2/11.0.0
• Kernel version: 5.10.4-arch2-1
• Link to full system information report: Gist
• Proton version: experimental-5.13-dxvk-d3d11-funny-refcount-20210108 / 5.0-10

I confirm:

• [x] that I have checked whether there are updates for my system available.

steam-289070.log with experimental

Symptoms

Proton experimental: The launcher is a black screen that can't be interacted with.
Proton 5.0-10: After the launcher is a gray screen

Reproduction

Start the game

Additional comments

Even though this game has a linux native version, sometimes updates disable crossplay. In those cases a working windows version with proton is very much appreciated :)

The game crashes in the graphics benchmark with DX12 version from legendary running in the proton 6.3-5 that just came out on steam. To reproduce click benchmark->graphics in the main menu and wait, it happens during the Teddy Roosevelt screen, and some of the text on this screen is messed up

GPU: RX 580
Driver: mesa 21.1.3
Kernel version: 5.12.12-arch1-1
on kwin_wayland

The game crashes in the graphics benchmark with DX12 version from legendary running in the proton

I was able to reproduce that crash while testing the llvm backend on my rx 5700 xt. It does not happen when using aco. I have also noticed that the this game is a lot slower on the current proton experimental when compared to 6.3-7. Almost 50% slower.

Link to my system information https://gist.github.com/wwmm/47fa68e8fa4a02aa86ca753cfc48daad. This is the proton log with the crash that happens when the llvm backend is used steam-289070.zip

I did more tests about the performance loss and it seems to be happening only when in dx12 mode. In the latest proton experimental the dx12 performance became as bad as the one in dx11 mode. I will do more tests but I can see clearly that there is a huge drop in cpu and gpu usage.

In the built-in benchmark gathering storm graphics I see something like this

- dx12 mode in proton 6.3-7: average frame time = 38 ms
- dx12 mode in proton experimental: average frame time = 76 ms

I did new tests with the proton experimental released a few hours ago and the behavior is the same. The dx12 mode is a lot slower when compared to proton 6.3-7. So far nothing seems to have any effect on the performance. Tests on ultra have the same behavior as the ones on low quality. Passing nosam to Mesa or disabling esync also have no noticeable effect.

I do not know if it will help but this is the proton log of one benchmark run in the latest proton experimental release
steam-289070.zip

@wwmm Thank you for reporting this! We looked into it and this should be fixed in the next experimental build - I'm not sure yet when it will come out, but you seem to be keeping an eye out for the updates :)

I did some tests with the new proton experimental version and I confirm that the regression was fixed. Now the average frame time on the same benchmark is

22 ms

A lot lower even than the one I used to see on 6.3-7 :-)

2KLauncher/LauncherPatcher.exe is crashing on the latest Proton Experimental 2021/11/04
steam-289070.log. The same thing happens on XCOM 2

@wwmm Thank you! The 2k launcher should be fixed with the next experimental release. Your regression reports are greatly appreciated :)

Edit: It's live now :tada:

@MissyMalaprop Are you still seeing this crash with current experimental? We believe the most recent hopefully fixed this crash.

@MissyMalaprop Are you still seeing this crash with current experimental? We believe the most recent hopefully fixed this crash.

Its been a while since I checked on this, I had just been playing with version 7.
It appears to be fixed. I switched back to experimental and I played for a few hours and never saw any freezing.

Has there been any new fixes for Civ VI? The latest 85% Steam Sale caused me to buy the whole package, and it was initially working under Experimental until, next day, it refuses to let the 2K Launcher stay on the screen.

I tried other versions, no luck.

I see on ProtonDB that there's a supposed fix for this problem? But I have inputed the custom launch and still have yet to see the launcher stay active.

The only thing I see from the launcher is "Please Wait...." and poof, disappears.

@MazdaRazda try to get proton logs or at least the output of sudo journalctl -b | grep -i steam after the crash. I am also using proton experimental and the game still launches.

@wwmm I solved the problem. I ran Steam via the command line and saw that it was forever stuck in a perpetual debugging loop. Confused, I simply uninstalled the game, initially assuming that it might have encountered corrupted files or something. After reinstalling the game I did the following:

1. I cleared out the Custom Launch Options.

2. Ran the "new game" with Experimental only.

3. At the 2K Launcher, instead of hitting play again, I checked the settings, and it was running on version 0.0.

• Basically the Launcher was acting as if it's brand new (or just completely outdated). I thought "oh, so it just needs an update to actually let me play it next time".
• Clicked on Update and Restart. Waited for it to come back. It never did. The problem lies with the Launcher not cooperating with (possibly) my Linux distribution (openSuse).

1. Checked online for a Launcher fix, and came across the same Custom Launch code, but it was slightly different, yet claims it was from ProtonDB.

2. Tried the altered version, and bam, bypassed the Launcher and I'm now able to play the game.

• There was a typo in the Custom Launch code that everyone was reposting on ProtonDB. You do not need to state "...CivilizationVI.exe..." but instead remove the ". exe" bit and bam, fixed.

Running the game with Experimental and the fixed Custom Launch code. Peace has been restored.

Hi, so I have swapped the SSD for a new one, reinstalled arch on it, BRTFS filesystem, and this bug still occurs. Is this worth addressing at all? I feel like this is a big problem if it's replicable to this scale. If specific people were to encounter this bug, it could be extremely detrimental

@sandervalcke Someone else reported similar behavior that was fixed by reverting to the 6.1.12 kernel. Does this also fix the issue for you?

I have the exact same issue as @sandervalcke. FPS is absolutely fine in singleplayer, but in multiplayer, even when just in my own private lobby, the FPS drops immensely, which is already noticable in the lobby menu.

I'm not sure about the Linux kernel, but I can confirm that this issue does not exist when using Proton 6, as per a report from KaptainObvious on ProtonDB.

Here's a log file from running Civilization VI with Proton 8.0-3, making a private internet lobby, starting the game, and panning the camera a bit ingame before exiting the application. The massive FPS drops were present.

System Information

• GPU: AMD Radeon 7900 XTX
• CPU: AMD Ryzen 9 7900X 12-Core Processor
• Video driver version: Mesa 23.1.7
• Kernel vresion: 6.5.3-arch1-1
• Proton version: 8.0-3

I've discovered that adding PROTON_NO_FSYNC=1 seems to fix the stuttering issues, or at least mitigate it. I've attached a zip of three log files, one using Proton Experimental (bad.log), one using Proton 6.3-8 (good.log), and one using Proton Experimental with the above flag (fsync_disabled.log).

Of particular note is that bad.log contains a ton of exceptions being dumped (RtlVirtualUnwind appears a significant number of times in the log, pretty much every couple of frames), whereas good.log does not contain the same quantity at the same frequency. The exceptions still appear with fsync disabled, but it seems like the stuttering itself has stopped while playing.

The archive is actually a 7z within a zip to get around file size limits.
civ6_logs.7z.zip

I've discovered that adding PROTON_NO_FSYNC=1 seems to fix the stuttering issues, or at least mitigate it. I've attached a zip of three log files, one using Proton Experimental (bad.log), one using Proton 6.3-8 (good.log), and one using Proton Experimental with the above flag (fsync_disabled.log).

Of particular note is that bad.log contains a ton of exceptions being dumped (RtlVirtualUnwind appears a significant number of times in the log, pretty much every couple of frames), whereas good.log does not contain the same quantity at the same frequency. The exceptions still appear with fsync disabled, but it seems like the stuttering itself has stopped while playing.

The archive is actually a 7z within a zip to get around file size limits. civ6_logs.7z.zip

For anyone else suffering from poor FPS in normal multiplayer mode with proton versions newer than 6.3, setting PROTON_NO_ESYNC=1 and PROTON_NO_FSYNC=1 resolved the issue for me. With those set, running Proton Experimental works flawlessly.

FPS stuttering in Multiplayer was resolved for me by simply adding PROTON_NO_ESYNC=1 to the Steam Launch Options, the FSYNC one wasn’t even required!

Weather I install this game using the native linux version or the windows version running in Proton, my mouse cursor is never visible in the game unless I have the game running in window mode. When in fullscreen, the cursor is hidden.

Also is there a way to get the Steam overlay with the linux version? I found this annoying since it is hard to accept invites to games so that is why I installed the Windows version.

Civilization VI: Incorrect time zone

Compatibility Report

• Name of the game with compatibility issues: Sid Meier’s Civilization VI
• Steam AppID of the game: 289070

System Information

• GPU: AMD Radeon RX 560
• Video driver version: Mesa 26.1.5
• Kernel version: 7.1.4-arch1-1
• Proton version: Experimental and 11 affected, 10 and 9 not affected

I confirm:

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

Symptoms

Timezone appears incorrectly in game. It shows the time in GMT rather than my local timezone.

This is a regression starting with Proton 11 also affecting Proton Experimental. Proton 10 and Proton 9 work correctly.

Reproduction

Start a new game or load a save file. The time will be displayed at the top-right of the screen. Hovering over the time shows the timezone.

Log file

proton-log.zip

Added log file

@weirddan455 I haven't been able to repro. Could you get a log with PROTON_LOG=+ntdll,+reg,+msvcrt %command%?