search

ValveSoftware / Proton

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

Company of Heroes 2 (231430) #3875

Open Frambooisier opened 4 years ago

Frambooisier commented 4 years ago

Compatibility Report

System Information

I confirm:

steam-231430.log

Symptoms

S

Game freeze when more than 6 infantry units are present/spawn ,I am using the Cheatcommands II mod to do the testing and spawn units. if less than 6 infantry units are on the field game works perfectly. sometimes, it seems to be random (I couldn't tie any variables affecting the occurrence of this bug) the game gets stuck/freeze when the game finishes loading a match. when the game is stuck on a fully loaded screen, but the actual match does not start, the environment sounds of actual match plays correctly but player input does not work. Esync off prevents the game from freezing but it causes in match sound loops when there are multiple sounds played (more than 2 units shooting causes sound loop) when multiple sound sources played, the sound loop is permanent and that causes the inability to exit the match to the main menu. There is a known workaround to reduce (what I understand) the number of sounds played in game at once, decreasing sound looping but in competitive gaming, that solution is not acceptable. Update 26-05-2020 I did some additional testing and it appears that bug occurs only when a larger group of infantry units are close to each other, when spread across the map even in groups of 2 the bug does not occur(game freeze).

Reproduction

-Start the custom game build more than 6 infantry units, play. -Playing as OKW (obercommando west) spawn 4 volksgrenadier squads in close distance to each other, freeze should occur in about 5 seconds.

Other users reports

Eddie

- OS manjaro kde - CPU 3800x with x570 chipset (16GB ram) - GPU: 5700xt - Driver/LLVM version: Nvidia 440.82 - Kernel version: 5.6.11-1-default - Proton version:5.0.9 - launch options PROTON_NO_ESYNC=1 MANGOHUD=1 MANGOHUD_CONFIG=cpu_temp,gpu_temp,position=top-left,width=405 RADV_PERFTEST=aco %command%

Deck

i5-6400 16gb

YellowOnion commented 2 years ago

fix doesn't work with wine 7.

Cytomax55 commented 2 years ago

You are correct I updated my method on how to fix this if you go to ProtonDB.com You can check my method there

YellowOnion commented 2 years ago

There's a noticeable performance hit in proton 6.3, @kisak-valve can you advise on how to debug where to report the desync? I would like to play with 7 or above.

@Cytomax55 Apparently I've been running it fine with 6.3 for a while, would recommend that version instead of 5.0

kisak-valve commented 2 years ago

Hello @YellowOnion, can you share some specific performance numbers?

Please add PROTON_LOG=1 %command% to the game's launch options, run the game a little bit in an affected area, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, 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.

YellowOnion commented 2 years ago

@kisak-valve I'll get you performance numbers once mangohud starts working again: https://github.com/ValveSoftware/steam-runtime/issues/511 , the game was noticeably smoother with Proton Experimental back in March when I first started playing.

I'll get my friend to play a game with me soon when he wakes up, It's going to be a pain in the ass to get the game back to working state after getting a log, is there anything else I could do while I'm there?

YellowOnion commented 2 years ago

@kisak-valve

https://gist.github.com/YellowOnion/4332f533c063c52d8cd33df21185ea98 steam-231430.log

modz2014 commented 1 year ago

I just bought this game today game cant even play the senario just keeps saying invalid

SrEstegosaurio commented 1 year ago

The game does not work at 240Hz. If activated the game graphics would freeze during launch and the screen would become irresponsible. Although the music and sounds would be functional. In fact, you would hear the music from the intro videos and the sound effects of the menu (when hovering and/or clicking options).

If you're screen is configured to run at 240Hz during first launch the game would auto detect it and therefore freeze it. In that case you can try luck modifying the game config files (for some reason it only worked one time) or just reinstalling the game and opening it after setting your screen to 60Hz. You can revert that once opened with no problem.

kisak-valve commented 1 year ago

Steam overlay crash Company of heroes 2

Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/9411. @Frambooisier posted on 2023-04-29T01:30:03:

Your system information

Please describe your issue in as much detail as possible:

in coh2 on proton 7 after pressing Shift+tab to open Steam overlay it cause a freeze and then crash of the game, then I switched to proton experimental, 1st try overlay did not activeate at all (as if it was disabled in games properites, but it wasnt) 2nd try game creashed and window popped out with error message. Tried Red alert 3 and steam overlay works there no problem, no more testing has been done.

image

Steps for reproducing this issue:

  1. Lunch coh2
  2. press ALT+TAB for steam overlay
  3. game should crash or steamoverlay do not show up
kisak-valve commented 1 year ago

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

Also, please temporarily opt out of Steam's client beta and 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.

Frambooisier commented 1 year ago

hey, sorry for the delay, here is the update on the issue. Issues happen onlyl with Steam beta.

System information: https://gist.github.com/Frambooisier/1f23a13d7a75bae63482c0bcf61fa1c5

With Proton 7 oddly enough steam overlay in beta was working fine today tested two times, after following changes the situation has changed: 1.Switched to proton experimental and testing 2. switching Steam client from beta to stable and again to beta with testing. Now the game crash with proper bugsplat message after trying to activate steam overlay in the game, another abnormallity is that I cannot interact with bugsplat window, the cursor in the text box is flashing but cannot press buttons or input text, Im pretty sure I could do that before(not sure what caused this, if I run into "regular" bugspalt I will be able to confirm).

image

here is the proton log Steam overlay crash on Proton 7: steam-231430.log

With Proton experimental game freeze upon steam overlay activation with no apparent creash and transition to bugsplat window, the Proton log file grow in size in speed of about 30 MB/s until the game is force kill.

Proton experimental log file ( good that it compress so well :+1: ) steam-231430.zip

Additionally Steam overlay works fine in "Red faction" with proton experimental

kisak-valve commented 1 year ago

Thanks @Frambooisier, this is a blind guess, but does setting the game's launch options to VK_ICD_FILENAMES="/etc/vulkan/icd.d/nvidia_icd.json" %command% have any effect on the game and the Steam overlay's behavior? (It's a long shot guess.)

Separately, can you temporarily disable mangohud to eliminate it as a possible factor.

Frambooisier commented 1 year ago

@kisak-valve the more ideas the better :) the lunch option have no effect. When it comes to disableing mangohud I used MANGOHUD=0 launch option, no luck either.

Frambooisier commented 1 year ago

@kisak-valve unfortunately the issue still presist with stable and Beta builds as of 02.07.2023, currently on openSUSE Tumbleweed 20230617. tested with Proton 7.0-6, Sometimes overlay works without any problems, but thats rare. on Proton Experimental: image I cannot interact with the buttons other than "X" on the window itself

abigrock commented 7 months ago

I use hyprland and sway wm with multiple monitors and wanted to post something that is useful to get the game running with the correct resolution of my primary monitor AND avoid the Assertion failed! error at least on my setup. For this to work I have to use Proton GE because it includes the FSR patches for spoofing a custom resolution. Here's the launch options that work for me

WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_CUSTOM_MODE=3440x1440 mangohud gamemoderun %command% -window -nomovies -forceactive

The WINE_FULLSCREEN variables at the beginning of the command are what require Proton GE and allow for setting the desired resolution in-game, while the -window -nomovies -forceactive command parameters at the end prevent the Assertion failed error. I don't know how well this works outside of wlroots compositors as I have keybindings to easily fullscreen the game window after it launches in windowed mode.

Edit: Also worth noting that the in-game overlay works and doesn't cause any crashes.

kisak-valve commented 5 months ago

Company of Heroes 2 Succesfully Runs Only Once Post Installation

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7415. @surebia posted on 2024-01-16T14:57:39:

Compatibility Report

System Information

I confirm:

Symptoms

Company of Heroes 2, upon the second start of the game proceed to vanish from the screen and be impossible to bring back.

Reproduction

Just opening the game a second time after a fresh download will reproduce this issue. A couple of mentions in here might allude to the same issue: https://www.protondb.com/app/231430.

Temporary fix

The file ~/.steam/steam/steamapps/compat/231430/pfx/dosdevices/c\:/users/steamuser/My\\ Documents/My\\ Games/Company\\ of\\ Heroes\\ 2/configuration_system.lua, which is rebuilt after starting or closing the game seems to be malformed. Upon deletion of the mentioned file, the game opens as usual. It would probably be wise to check the configuration_user.lua file located in the same repository for this same issue. Deleting the aforementioned file works temporarily as the default file seems be used to run the game.

P.S tell me whether i should move this to the existing compatibility report. I figured, this way it would be easier to find for people who have the same issue.

Frambooisier commented 5 months ago

@surebia Can you run the game with -window -fullwindow steam launch options and see if it changes anything?

surebia commented 5 months ago

@surebia Can you run the game with -window -fullwindow steam launch options and see if it changes anything?

The issue is unchanged after introducing the two launch options.