search

ValveSoftware / Proton

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

Company of Heroes 3 (1677280) #6568

Open josef256 opened 1 year ago

josef256 commented 1 year ago

Compatibility Report

System Information

I confirm:

steam-1677280.log

Symptoms

i got a desync error whenever i join a multiplayer match

20230225112339_1

Reproduction

ahjolinna commented 1 year ago

apparently according to protondb to fix the desync in MP you need to download the 'vc_redist.x64.exe' file from https://www.microsoft.com/en-us/download/details.aspx?id=48145 and run the commands: cabextract vc_redist.x64.exe, cabextract a10, mv ucrtbase.dll $HOME/.steam/steam/steamapps/compatdata/2245830/pfx/drive_c/windows/system32/.

kisak-valve commented 1 year ago

Company of Heroes 3 on laptop with nvidia

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6572. @b3nis posted on 2023-02-25T19:49:21:

Compatibility Report

System Information

I confirm:

My system: https://gist.github.com/b3nis/1235a9ae56f8015f0ca6d16b66e824d3

Proton log: https://gist.github.com/b3nis/27ea6c8b0a320849f010199b5dc9e0d1

Symptoms

A dialog window with the text "Sorry, something went wrong. For solution please visit: https://support.codefusion.technology/CoH3_gjsa_8945/?e=88500006&l=english"

Reproduction

Install the game on a laptop with nvidia dgpu and launch it. All other games I play, including COH2, works with any mods. Seems to be something with the dgpu + proton + wine maybe? Seems to be working for a lot of people on desktop computers (with single gpu).

jrbergen commented 1 year ago

apparently according to protondb to fix the desync in MP you need to download the 'vc_redist.x64.exe' file from https://www.microsoft.com/en-us/download/details.aspx?id=48145 and run the commands: cabextract vc_redist.x64.exe, cabextract a10, mv ucrtbase.dll $HOME/.steam/steam/steamapps/compatdata/2245830/pfx/drive_c/windows/system32/.

See also this gist which addresses the same problem for CoH2 and should apply for CoH3.

I wonder if there is a way to make this fix unnecessary though. I have submitted a bug report to SEGA; perhaps if enough people do this, they will try to fix it (although I'm not sure if it is strictly a Proton issue..).

sfxworks commented 1 year ago

Compatibility Report

System Information

I confirm:

Symptoms

Low FPS

For this game, I can only achieve 60 fps if I run it at 800x600, and only in the menu. It runs incredibly slower than the alpha which had a stable 60 on max settings. 1920x1080 runs at 40fps and even lower in the campaign. Lucky to even get 20 at 4k. This is all with min settings.

Reproduction

Launch company of heroes 3 using proton experimental Use FPS counter in steam

b3nis commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/6568#issuecomment-1445403256

I have a tought. I might out on deep water, but what if the Coh3 app is not recoqnized as a "game"/"heavy 3D app"? Because in my case I actually got it to start now - but only on my igpu. Maybe it's similar for you - and that you GPU is just idling (that is why you get so low fps). Have you checked with Mangohud if you GPU is using more than 20 watts when the game is on?

b3nis commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/6568#issuecomment-1445191370

Update: I can start the game - but it only runs on the igpu for some reason. All other games runs, without any specific launch options, on the dgpu.

sfxworks commented 1 year ago

Radeon Profiler was showing an increase in watts used and even proc'd the fans

ahjolinna commented 1 year ago

for me the game won't launch at all (tried v7.0-6, experimental and GE7-49) Log file with experimental: steam-1677280.log

PS . I don't know if this is proton issue or openSUSE MicroOS issue, as this is my first time using it for past few days....but other games I have tested before still work for me just fine, with some exception of few mmorpg (FF XIV, GW2 and SWTOR).

my system spec:


             .;ldkO0000Okdl;.                
         .;d00xl:^''''''^:ok00d;.            OS: openSUSE MicroOS
       .d00l'                'o00d.          Kernel: x86_64 Linux 6.1.12-1-default
     .d0K^'  Okxoc;:,.          ^O0d.        Uptime: 12h 47m
    .OVVAK0kOKKKKKKKKKKOxo:,      lKO.       Packages: RPM / Flatpak
   ,0VVAKKKKKKKKKKKKK0P^,,,^dx:    ;00,      Shell: bash 5.2.15
  .OVVAKKKKKKKKKKKKKk'.oOPPb.'0k.   cKO.     Resolution: 3072x1728
  :KVAKKKKKKKKKKKKKK: kKx..dd lKd   'OK:     DE: KDE 5.103.0 / Plasma 5.27.1
  lKlKKKKKKKKKOx0KKKd ^0KKKO' kKKc   lKl     WM: KWin_wayland
  lKlKKKKKKKKKK;.;oOKx,..^..;kKKK0.  lKl     GTK Theme: Breeze [GTK2],  [GTK3]
  :KAlKKKKKKKKK0o;...^cdxxOK0O/^^'  .0K:     Icon Theme: Papirus-Dark
   kKAVKKKKKKKKKKKK0x;,,......,;od  lKP      Disk: 16T / 21T (75%)
   '0KAVKKKKKKKKKKKKKKKKKK00KKOo^  c00'      CPU: AMD Ryzen 7 5700G with Radeon Graphics @ 16x 4.3GHz
    'kKAVOxddxkOO00000Okxoc;''   .dKV'       GPU: NVIDIA GeForce RTX 3060 Ti (Driver: v525.89.02)
      l0Ko.                    .c00l'        RAM: 12736MiB / 47963MiB
       'l0Kk:.              .;xK0l'         
          'lkK0xc;:,,,,:;odO0kl'            
              '^:ldxkkkkxdl:^'
ahjolinna commented 1 year ago

okay after the 1.0.2 hotfix update the game still don't launch for me BUT now it get stuck in running/playing ...and the log file is huge, here is a 163,6MiB file: steam-1677280.log

sfxworks commented 1 year ago
Screenshots ![image](https://user-images.githubusercontent.com/5921035/222275193-2aea6931-a449-4a05-a320-5b014f645e60.png) ![image](https://user-images.githubusercontent.com/5921035/222275266-776d71c8-835c-4253-b295-747ba597e985.png) ![image](https://user-images.githubusercontent.com/5921035/222275299-cc89d3e1-1595-4f07-8a54-6cd16b028ad9.png) ![image](https://user-images.githubusercontent.com/5921035/222275316-d74359ab-a9a7-446d-a3bb-4be41447a256.png) ![image](https://user-images.githubusercontent.com/5921035/222275338-e43ea639-fc89-48a6-b991-27f907ec4615.png)

I don't know how Coh3 rates the different fps types, but it does seem that main and render is the bottleneck

ahjolinna commented 1 year ago

here is my new log after 1.0.4 hotfix update: steam-1677280.log no big log files anymore

b3nis commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/6568#issuecomment-1445191370

Managed to sort this by https://github.com/doitsujin/dxvk/blob/master/README.md#device-filter Dunno why DXVK has no problem with any other game (this setting is not needed). Anyway, fixes my issue with not wanted to start on dgpu.

Update: Only works with x.org, not Wayland. Nvidia I guess? Gah.

sfxworks commented 1 year ago

Anyone have a solution to my issue? Or seeing similar symptoms? Only gpu I have is the radeon and my 5950x doesn't have an embedded gpu

sfxworks commented 1 year ago

1.0.5 patch: image

sfxworks commented 1 year ago

image Between then and now, after a fresh restart after the 1.5 I'm getting a stable 60!!!

ahjolinna commented 1 year ago

Finally some great news for me at least with the new 1.0.6 hotfix update.

I can now for the FIRST time actually launch (& play) the damn game.

Now my only issue is that the game gives me error that says my drivers are too old/unsupported ... don't know if this is a game issue or proton one (I have the latest stable v525.89.02 drivers)

image

here is the new log file: steam-1677280.log

Update, here is my benchmark results: image

sfxworks commented 1 year ago

image damn I spoke too soon

JonathanBrouwer commented 1 year ago

I can play the main game fine. Has anyone managed to get the EssenceEditor.exe (the provided modding tool) working? When I run it, I get the following logs: https://gist.github.com/JonathanBrouwer/4aaf81ce5f572058f748cd14f222d00a

Essence.Editor.Bridge.dll is in the same directory as the essence editor, so I'm not sure why it can't find it

sfxworks commented 1 year ago

I can play the main game fine

What are the specs of your machine? Curious if you're running nvidia or amd and which divers.

JonathanBrouwer commented 1 year ago

I can play the main game fine

What are the specs of your machine? Curious if you're running nvidia or amd and which divers.

i7 6700k RX 7900 XTX Mesa 23.0.0

If you want any other information, let me know

sfxworks commented 1 year ago

If you want any other information, let me know

Wayland or X11?

JonathanBrouwer commented 1 year ago

If you want any other information, let me know

Wayland or X11?

I mainly run on KDE Wayland (Running the game under XWayland), but I just tried running it in KDE under X11 and that also works fine

b3nis commented 1 year ago

Mainly a reply to myself and if somebody got the same challenges:

sfxworks commented 1 year ago

Mesa 23.0.0


glxinfo | grep Mesa

client glx vendor string: Mesa Project and SGI OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.3.5 OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.3.5 OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.3.5 


 Maybe that's why. I'm on 22.
JonathanBrouwer commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/6568#issuecomment-1476838752

I also took the benchmark, for some reason the graph does not seem to be rendered right, but the numbers at the bottom are reliable. I'm on mesa 23 already because the 7900 XTX does not work well on mesa 22. I also had to apply the dll copy to be able to play multiplayer. Also looks like I'm playing at a lower resolution than you, but that shouldn't explain how large the gap in performance is.

20230320205519_1

sfxworks commented 1 year ago

image That must have been it. Manjaro still had me on mesa 22. 23 did the trick.

mikeframpo commented 1 year ago

I'm seeing a similar issue to @sfxworks . Constant frame drops on Ubuntu 22.10. I have Mesa 23.0 installed. Is anyone else seeing similar issues?

Screenshot from 2023-04-07 13-59-51

sfxworks commented 1 year ago

Your issue looks different as I was floating around 14fps with spikes upward https://github.com/ValveSoftware/Proton/issues/6568#issuecomment-1464830070

mikeframpo commented 1 year ago

Does anyone else have any idea why it seems to be so stuttery? Other people on protondb are reporting camera stutter - which might be the same issue https://www.protondb.com/app/1677280

josef256 commented 1 year ago

is the mp disconnect still present even with the lates GE versions ?

kisak-valve commented 7 months ago

Company of heroes 3

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7449. @EliasDadde posted on 2024-01-27T14:05:20:

Heavy Camera Sluttering makes the game unplayable . Proton Experimental (although i used many different proton version so i dont think it matters , it's a universal issue with proton and he game).

My System Information ``` Computer Information: Manufacturer: Micro-Star International Co., Ltd. Model: PRO Z790-A WIFI (MS-7E07) Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Core(TM) i9-14900K CPU Family: 0x6 CPU Model: 0xb7 CPU Stepping: 0x1 CPU Type: 0x0 Speed: 5701 MHz 32 logical processors 24 physical processors Hyper-threading: Supported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported AVX2: Supported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Supported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: "openSUSE Tumbleweed" (64 bit) Kernel Name: Linux Kernel Version: 6.7.2-lqx1-1-liquorix X Server Vendor: The X.Org Foundation X Server Release: 12101011 X Window Manager: KWin Steam Runtime Version: steam-runtime_0.20231127.68515 Video Card: Driver: NVIDIA Corporation NVIDIA GeForce RTX 4090/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 550.40.07 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 143 Hz VendorID: 0x10de DeviceID: 0x2684 Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 3840 x 2160 Desktop Resolution: 3840 x 2160 Primary Display Size: 24.41" x 13.39" (27.83" diag), 62.0cm x 34.0cm (70.7cm diag) Primary Bus: PCI Express 16x Primary VRAM: 24564 MB Supported MSAA Modes: 2x 4x 8x 16x Sound card: Audio device: %1$s Memory: RAM: 31872 Mb VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: en_US.UTF-8 Total Hard Disk Space Available: 1811981 MB Largest Free Hard Disk Block: 1589847 MB Storage: Number of SSDs: 6 SSD sizes: 4000G,3000G,2000G,960G,240G,180G Number of HDDs: 0 Number of removable drives: 0 ```
EliasDadde commented 7 months ago

To update the post , seems to be a lot of frames drop , doesn't matter really low quality graphics or high quality graphics , the heavy frame drops are the cause of the sluttery camera feeling, sadly been working on the game for a week or so , cant get it to run at a stable frame rate ![Uploading Screenshot_20240127_232418-1.png…]()

LDprg commented 5 months ago

I have found a fix for PCs/Laptops running CoH3 and having fps issues (at least with dedicated Nvidia GPU)! Because the game sometimes actively priorities the integrated (slow) GPU over the dGPU even when offloading. A simple fix is to filter GPUs with DXVK_FILTER_DEVICE_NAME="GPU NAME". Works on Wayland and X11, however on X11 I did get some strange bugs about wrong gpu detection and the screen flickering like crazy.

EliasDadde commented 5 months ago

I have found a fix for PCs/Laptops running CoH3 and having fps issues (at least with dedicated Nvidia GPU)! Because the game sometimes actively priorities the integrated (slow) GPU over the dGPU even when offloading. A simple fix is to filter GPUs with DXVK_FILTER_DEVICE_NAME="GPU NAME". Works on Wayland and X11, however on X11 I did get some strange bugs about wrong gpu detection and the screen flickering like crazy.

are you sure about that DXVK is a dx11 , and im not sure coh 3 has a dx11 path , its a dx12 games , unless i'am mistaken.

LDprg commented 5 months ago

are you sure about that DXVK is a dx11 , and im not sure coh 3 has a dx11 path , its a dx12 games , unless i'am mistaken.

@EliasDadde actually I do not know, but it only works on my system with the env var (without it it will use iGPU). For vkd3d (dx12) there is VKD3D_FILTER_DEVICE_NAME, which does the same but has no effect on my system (when playing CoH3). So I guess it uses dx11.

Here are my full launch options:

DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 3060"  PROTON_HIDE_NVIDIA_GPU=0  PROTON_ENABLE_NVAPI=1 DXVK_ASYNC=1 gamemoderun %command%
mgruberb commented 4 months ago

Hi, for people who reported bad stuttering in Company of Heroes 3: I had the same experience and found that Kernel's split lock mitigation caused these problems on my system (Ubuntu 22.04, Nvidia 4070 Ti, Intel i5 12500).

After running CoH 3 with all its stuttering and bad fps, dmesg was full of lines like:

#AC: RelicCoH3.exe/63356 took a split_lock trap at address: 0x154f93c1b

Once I disabled split lock mitigation the game ran perfectly at 120 fps without any suttering. You can do this by using gamemode >= 1.8.0 and configuring enabling disable_splitlock=1 in the gamemode configuration.

Alternatively, you can also disable the split lock mitigation by running

sudo sysctl kernel.split_lock_mitigate=0

in the terminal before playing.

Hope this helps!

EliasDadde commented 4 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/6568#issuecomment-2105716251

this is true indeed , however sysctl doesn't seem to work nor the gamodemode.ini im still getting this split_lock , seems like steam encourage this behaviour while kernel don't , seems more like a valve proton issue that they can solve themself , but thank you for catching this up . [137185.322270] x86/split lock detection: #AC: RelicCoH3.exe/26727 took a split_lock trap at address: 0x15a0539d4 [137186.046481] x86/split lock detection: #AC: RelicCoH3.exe/26720 took a split_lock trap at address: 0x15a0539d4 [137186.448791] x86/split lock detection: #AC: RelicCoH3.exe/26712 took a split_lock trap at address: 0x14420ead2 [137189.911775] x86/split lock detection: #AC: RelicCoH3.exe/26710 took a split_lock trap at address: 0x14420eb82 even after i tried to change the kernel parameter with sysctl.

yeah i noticed the difference it's huge , still not 100% smooth but at least it's now playable 2v2 , thanks so much for pointing this out , hopefully valve will fix this issue once and for all

Just A Quick Note disable_splitlock=1 in /etc/gamemode.ini doesn't really fix the sluttering the only way to fix it is to use sysctl and change kernel parameter then the game will work flawlessly .