ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.44k stars 1.07k forks source link

Sid Meier’s Civilization VI (289070) #4068

Open TheGreatestJannet opened 4 years ago

TheGreatestJannet commented 4 years ago

Compatibility Report

System Information

I confirm:

Symptoms

Game gets stuck on a grey screen.

Reproduction

Launch the game.

Additional Information

Seems to be related to this: https://bugs.winehq.org/show_bug.cgi?id=49315

uniformbuffer commented 4 years ago

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.

dodafish commented 4 years ago

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...

uniformbuffer commented 4 years ago

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.

dodafish commented 4 years ago

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.

uniformbuffer commented 4 years ago

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

ThaChillera commented 3 years ago

System Information

I confirm:

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 :)

rosefromthedead commented 3 years ago

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 Screenshot_20210625_213310

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

wwmm commented 3 years ago

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.

kisak-valve commented 3 years ago

Hello @wwmm, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

wwmm commented 3 years ago

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.

wwmm commented 3 years ago

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
wwmm commented 3 years ago

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.

wwmm commented 3 years ago

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

alasky17 commented 3 years ago

@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 :)

wwmm commented 3 years ago

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 :-)

wwmm commented 3 years ago

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

alasky17 commented 3 years ago

@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:

kisak-valve commented 2 years ago

Civilization 6 regression

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5601. @MissyMalaprop posted on 2022-02-22T05:10:33:

Compatibility Report

System Information

I confirm:

Symptoms

This game used to work fine with DX12 mode, and still does seem to work fine with Proton 7.0-1, the problem only seems to be with latest Experimental updates on Feb 18th 2022. When using latest Experimental, it only runs for a while (20-30 minutes), and the screen will eventually freeze even though the game is technically still running. Getting out of the game and killing it is a pain as the Civ6 cursor stays stuck over everything and trying to kill everything command line only. I assume its something to do with vkd3d changes, as I used to play for many hours with no issues. I have seen this happen on a friends AMD GPU system and my nvidia GPU system, so its not GPU or driver specific. I have had to kill my system twice and risk issues due to this, so I will not reproduce it again. FYI, I know there is a Native Linux version of this game, but it runs like total trash and is almost unplayable in giant games, while it runs fantastic in Proton (until this update).

Reproduction

Just play the game for a while in DX12 mode after latest Experimental as of 02/18/2022

alasky17 commented 2 years ago

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

MissyMalaprop commented 2 years ago

@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.

MazdaRazda commented 2 years ago

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.

wwmm commented 2 years ago

@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.

MazdaRazda commented 2 years ago

@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.

4) 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.

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

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

kisak-valve commented 1 year ago

HUGE VULBURABILITY ---- CIV VI

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6816. @gmod64bit posted on 2023-06-01T21:05:38:

Compatibility Report

System Information

I confirm:

PROTON LOG (useless?)

https://mega.nz/file/Xr52nZ7R#487kpYlFZHwSBKy5oI7ze9jAM5OhrxKRndnSOTzo7fw

### BUG: CHANGES ENTIRE DRIVE TO READ-ONLY (PRIVILEGE ESCALATION EXPLOIT)

Reproduction

  1. Launch the game
  2. Get literally fucked-->

The proton log command will crash the game and the drive will not become read-only.

Without proton-log, the game runs, the drive becomes read-only, and that is a huge problem.

This is a vanilla arch install using BRTFS filesystem.

Please give me more things to paste for logs since the proton-log is useless in this case.

This is a gigantic issue that needs addressed immediately.

kisak-valve commented 1 year ago

Hello @gmod64bit, Steam and all Steam games are run as a regular user. You've described either impending hardware failure or a kernel bug which should be evaluated by the btrfs dev(s).

gmod64bit commented 1 year ago

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

kisak-valve commented 1 year ago

Civilization VI: degraded multiplayer performance

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7019. @sandervalcke posted on 2023-08-15T20:32:01:

Compatibility Report

System Information

I confirm:

Symptoms

With proton 7, 8 or experimental, my online FPS tanks, going up and down between 5 and 20. Using 6.3-8 I don't have this issue, a steady 100+. Offline play doesn't have this issue, works flawlessly in all of these versions. Issue is already present when creating an internet game with only computer opponents.

Reproduction

Whether the issue is present can already be seen from the game creation lobby:

Multiplayer > Internet > Create Game > Confirm Settings

with newer versions of proton my FPS is at 30 or below here, the animated background is jittery. With 6.3-8 FPS is 60-70 and everything is smooth. Actually proceeding to in-game the FPS will be even worse.

kisak-valve commented 1 year ago

Hello @sandervalcke, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

alasky17 commented 1 year ago

@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?

Furyspark commented 1 year ago

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

kisak-valve commented 9 months ago

Civilization VI crashes with PROTON_USE_WINED3D=1

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7454. @andyflight posted on 2024-01-28T23:39:01:

I'm new to Linux, I've just installed Ubuntu 23.10 and installed civilization VI from Steam. However, for some reason I have maximum 25 fps in the game, when on Windows I got stable 60 fps. I tried to run game with the OpenGL instead of Vulkan using PROTON_USE_WINED3D=1 PROTON_USE_WINE_DXGI=1 PROTON_NO_D3D11=1 but every time I launch game it crashes.

System Information

logs in terminal

proton log

Symptoms

When I try run a game with PROTON PROTON_USE_WINED3D=1 PROTON_USE_WINE_DXGI=1 PROTON_NO_D3D11=1 game crashes in a few minnutes after launch.

Reproduction

set PROTON_USE_WINED3D=1 PROTON_USE_WINE_DXGI=1 PROTON_NO_D3D11=1 to launch options

BobobUnicorn commented 8 months ago

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

kisak-valve commented 3 months ago

Civilization VI starts in offline mode

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7890. @DzyubSpirit posted on 2024-07-12T11:42:36:

Compatibility Report

System Information

I confirm:

Symptoms

Game starts in offline mode. Multiplayer features are not working.

Reproduction

Steam Runtime Diagnostics

civ_bad.log

Another issue for other games starting in offline mode might be related

I'm able to start the game in online mode if I clear the cache of 2K Launcher, wait for a bit and start Civilization VI: civ_good.log But the next time I start the game it again starts in offline mode

jdsmall25 commented 3 months ago

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.

cirrus-zz commented 2 months ago

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!