search

ValveSoftware / Proton

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

Mordhau (629760) #2629

Open KorinFlakes opened 5 years ago

KorinFlakes commented 5 years ago

Whitelist Request

System Information

I confirm:

Issues

Bumbadawg commented 5 years ago

Bug report: using proton 4.2-3, nvidia-430, disabling shader cache or not, the game freezes whatever you do 30s after launch.

kisak-valve commented 5 years ago

Hello @Bumbadawg, 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. Also, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

Bumbadawg commented 5 years ago

Hello @kisak-valve , here is my config here is the report

kisak-valve commented 5 years ago

Looks like this game uses Media Foundation. warn:module:load_builtin_dll cannot open .so lib for builtin L"mfplay.dll": /home/bumbaget/.steam/steam/steamapps/common/Proton 4.2/dist/lib/wine/mfplay.dll.so: cannot open shared object file: No such file or directory

Bumbadawg commented 5 years ago

@kisak-valve i solved my freeze issue, it was due to using firejail on Steam, which might have locked some system components out of the game's reach in order to function properly. Still, that Media Foundation is missing and prevents from playing the credits and loading screen video, which is not game breaking.

The audio works fine, but i can't tell if it works past stereo. One would need to report about a 7.1 setup.

mawww commented 5 years ago

Bug report: Crashes here during the initial loading screen, takes a variable amount of time (1s to 1min), using Proton 4.2-3. link to proton log and config

kisak-valve commented 5 years ago

Hello @mawww, your log has err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased.

Please run ulimit -Hn and verify it gives you a high value and not 4096.

mawww commented 5 years ago

Hello, I had tried to raise thtn to 8192 with no success, but just tried with 100000 and the game launches. Sorry about that.

Rabcor commented 5 years ago

I have been playing this game with fairly good success through proton 4.2-4; no options or tweaking was required, I just installed it and pressed play. I have been encountering a very strange issue though.

Desktop Notifications (does not apply to steam's in-game notifications) can break the game causing either it's framerate to get permanently reduced by quite a lot (my avg fps is like 80, often going to 100, the performance is really good in general, but when this issue happens at one point it dropped to the 5-10fps range) or the game just outright freezes and crashes. The latter result (e.g. freeze/crash) is more common than the framerate issue which has only happened to me two or three times.

I had to disable discord's desktop notifications because everytime someone would talk to me I ran the risk of the game breaking, and if the first message didn't ge tthe job done, then the following messages always managed to (someone sends me 3 or 4 messages and something is bound to happen).

It is possible that the framerate drop only happens in fullscreen exclusive mode (I switched to borderless windowed after I started having issues, it seemed to work better in general as long as I don't get desktop notifications)

Just now the game froze and crashed for me because I was tweaking my volume with keyboard buttons and got a notification for it.

Update: It MAY have something to do with compositing, I noticed disabling compton and tweaking my sound has not caused issues yet (but it also doesn't 100% for certain cause issues with compositing on either) discord message notifications have a strong track record for crashing the game though so I need to test that a bit further. I am using xfce, I think the notification daemon is called xfce4-notifyd.

Bumbadawg commented 5 years ago

regression Reporting for 2.4-5, unplayable.

Whether in Ultra or low settings, I had drops from 110fps to 30fps everytime i looked 15° left/right. I switched the DXVK DLLs back to 1.2 and it was playable again.

kisak-valve commented 5 years ago

Hello @Bumbadawg, your claim doesn't make sense because Proton 4.2-5 ships with DXVK 1.2.1. Please verify Proton 4.2's files and verify it's back to the shipped version of DXVK, add PROTON_LOG=1 %command% to the game's launch options, reproduce the issue, and drag and drop the generated $HOME/steam-$APPID.log into the comment box. Also, is your performance issue from the first run after updating Proton or did the issue persist?

Bumbadawg commented 5 years ago

your claim doesn't make sense because Proton 4.2-5 ships with DXVK 1.2.1.

indeed it ships with 1.2.1. and thus because of the issue, i downloaded back 1.2 DLLs and it fixed my issue (misunderstanding here)

About the test, i'll do right now for the log.

Also, is your performance issue from the first run after updating Proton or did the issue persist?

yes, and after reboot.

EDIT: i redownloaded 1.2.1 DLLs and put them into Proton, it all works just fine so you can dismiss the first issue i reported.

But, there's an issue in file checking: I then removed all DLLs from Proton's folder, checked files integrity: "All files were successfully validated" while it was missing the DLLs.

Bumbadawg commented 5 years ago

also mind my manners, Hello @kisak-valve =)

Rabcor commented 5 years ago

I still get these framerate cuts from time to time with compositing disabled, e.g. I'm playing and then all of a sudden my framerate is cut in half, this can happen multiple times, e.g. I go from 60 to 30 then 30 to 15 to 7 lol. It's relatively rare though.

Also quite sadly, I can't seem to get lute bot to work.

Bumbadawg commented 5 years ago

@kisak-valve to complete your testimony @Rabcor, when using KDE, using the Audio volume OSD or using notify-send lowers my framerate for the time it stays up, then rises up again once vanished, whereas yours keep being lowered. But, i encounter a window management bug with the audio volume OSD. KDE volume OSD steals the control from the window, and the mouse coordinate seems to lock in an ingame 45° angle cone. Which forces me to (1) click the window to refocus, (2) press escape to reset the mouse cone to fullscreen mouse control, (3) repress escape to get back into the game. Basically it's workaroundable but quite tedious when changing audio volume in KDE. All these in fullscreen, gotta try in borderless.

Rabcor commented 5 years ago

@kisak-valve to complete your testimony @Rabcor, when using KDE, using the Audio volume OSD or using notify-send lowers my framerate for the time it stays up, then rises up again once vanished, whereas yours keep being lowered. But, i encounter a window management bug with the audio volume OSD. KDE volume OSD steals the control from the window, and the mouse coordinate seems to lock in an ingame 45° angle cone. Which forces me to (1) click the window to refocus, (2) press escape to reset the mouse cone to fullscreen mouse control, (3) repress escape to get back into the game. Basically it's workaroundable but quite tedious when changing audio volume in KDE. All these in fullscreen, gotta try in borderless.

I have encountered the same issue with the mouse being locked to a 45° cone, it seems to happen at random for me though and like the fps cut thing, it is rare, I noticed that xfce4-notifyd had some built-in compositing effects like fade and opacity that worked independent of compton, I tried turning them off maybe this will solve some of my issues.

KorinFlakes commented 5 years ago

I have encountered the same issue with the mouse being locked to a 45° cone

This happens to me occasionally if I alt-tab out (or if something forces me out) and then attempt to alt-tab back in. Usually, I can recover it through a painful process of alt-tabbing, shift-tabbing and window/full screening until the mouse goes normal. I just keep a general rule of don't alt-tab unless absolutely necessary.

FWIW, I have similar alt-tab issues in many different games running on Proton.

waylon531 commented 5 years ago

There's been a performance regression with this game. In Mordhau with Proton 4.2-5 there's random freezes, though these freezes are only for a second or so and happen maybe once ever few minutes they can be a game ruining experience. A short freeze means basically guaranteed death in this game.

Proton 3.16-9 Beta does not appear to have this problem so it looks like there's been some sort of regression in Proton. Other than that this game runs flawlessly.

kisak-valve commented 5 years ago

Hello @waylon531, 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. Also, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

waylon531 commented 5 years ago

Alright, here it is:

https://gist.github.com/waylon531/a0a757afba5f562bf92b27b43301dd9c ^ System Information

I ended up playing a full game of frontline with logs enabled. I did that for both the old version, 3.16-9, and the latest, 4.2-5. The log files are ~100MB and github won't let me stick them in a comment, so here are the links:

https://gitlab.com/waylon531/log_files/raw/master/proton-3.16-steam-629760.log https://gitlab.com/waylon531/log_files/raw/master/proton-4.2-steam-629760.log

It looks like other people might be having the same issue, I took a look at protondb and it seems like other people are having problems with the game stuttering/freezing: https://www.protondb.com/app/629760

Bumbadawg commented 5 years ago

@waylon531 try disabling Steam overlay.

ghost commented 5 years ago

The newest update causes the game to not load servers at all. The "Search" option in the main menu in greyed out and connecting fails when attempting to manually connect. This is since the new update a few hours ago.

Downgrading to 3.16 works but the performance on that version is pretty bad.

danich93 commented 5 years ago

I can confirm. New proton update killed mordhau 8(

kisak-valve commented 5 years ago

Hello @manJerky, @Ohmu93, can one of of you please add PROTON_LOG=1 %command% to the game's launch options, reproduce the issue, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

ghost commented 5 years ago

steam-629760.log

Here's just a log of me starting the game, going to the game server selection menu, selecting a server and receiving a failed connection message.

L-as commented 5 years ago

I can confirm that 4.2-8 causes you to not be able to join any remote servers. I can still host a local match, though whenever I try joining a server it says "Failed to connect to server". There are only 10 commits since 4.2-7, so it should be easy to bisect though. One of those is updating wine though, which seems to be the most likely cause. I can't quite tell what new wine commit would cause it though, since they all seem to be graphical changes.

Plagman commented 5 years ago

We made a branch so that you can roll back to 4.2-7 while this is being investigated. Find Proton 4.2 in your Library, then go into its properties, find the Beta tab, and select 4.2-7 from the dropdown.

krompus commented 5 years ago

@Plagman Thank you so much! MORDHAU is back up and running. :)

I'll note that, perhaps a little confusingly, it still shows "4.2-8" on the library page / properties window, even though it's actually the 4.2-7 beta.

Ljit0 commented 5 years ago

The commits that broke it were the ones yesterday, I was able to play in the morning but later in the evening I was not able to. With the 4.2-7 it runs fine.

kisak-valve commented 5 years ago

Per "Fixes for multiplayer functionality in Mordhau, SOULCALIBUR VI, and others with problems from 4.2-8." in the Proton 4.2-9 update, please opt out of the Proton 4.2 beta branch and retest the networking issue.

danich93 commented 5 years ago

Confirmed works. Thanks for fast fix guys!

krompus commented 5 years ago

This game has been running beautifully on my system (Arch Linux, Vega 64, mesa-aco-git) through Proton until now (playing daily since release, about 500 hours), but I've found a regression in Proton 4.11-2; when editing the name of a loadout, or selecting the server browser search box, the game freezes entirely.

alasky17 commented 5 years ago

@krompus Thank you for the specific examples! I was able to reproduce the crashes and we can see what is going wrong. We hope to have a fix shortly.

danich93 commented 5 years ago

The game now also freezes dead when opening in-game chat.

NoeelMoeskops commented 5 years ago

proton 4.11-2 and 4.2-9 fails to launch. The Mordhau window is just a 'screenshot' of my current desktop. PROTON_USE_WINED3D enables me to launch but had render and performance issues. my system

-edit: turned out it was because of flatpak, normal steam installation works-

aeikum commented 5 years ago

The in-game chat crashes and freezes should be resolved in Proton 4.11-3. Please retest.

danich93 commented 5 years ago

@aeikum New update fixed it, thanks!

MrJakob99 commented 5 years ago

I got a graphic glitch. The body parts and clothes of the characters appear and dissapear very fast. after a while all the characters start blinking making the game unplayable. Could that be proton realated or is there something wrong with my graphic engines ?

kisak-valve commented 5 years ago

Hello @MrJakob99, 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.

If possible, please check if a newer video driver is available and has behaves better.

MrJakob99 commented 5 years ago

https://gist.github.com/MrJakob99/e44bc9bac9005fa2da44901b8586f0f1

kisak-valve commented 5 years ago

Your video driver is older than the minimum supported version (noted at https://github.com/ValveSoftware/Proton/wiki/Requirements#nvidia), so it wouldn't be surprising if there is a known issue that got fixed a while ago.

https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa should have newer drivers to try out (418 series and 430 series as of this comment).

kisak-valve commented 5 years ago

Mordhau (629760)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3156. @Gregzenegair posted on 2019-10-16T20:00:37:

Compatibility Report

System Information

OS: Linux Mint 19.2 Tina (64 bits) KERNEL: 4.15.0-58-generic CPU: Intel Core i5-4690K @ 3.50GHz GPU: NVIDIA GeForce GTX 970 GPU DRIVER: NVIDIA 430.40 RAM: 16 GB Sound card : 0 [CA0106 ]: CA0106 - CA0106 Live! 7.1 24bit [SB0410] at 0xc000 irq 16

I confirm:

steam-629760.log

The game only outputs stereo audio whereas I have a surround 5.1 audio system.

Reproduction

Launch the game, try to hear sound spatialized with 5.1 outputs

f-fusco commented 5 years ago

4.11-8 gives me LOD/texture issues. Map props are always in low poly mode and exhibit serious pop-in. 4.11-7 didn't have this issue. I rolled back to 4.2-9 and the issue went away.

GPU: 1660 Ti on driver 435.21, Pop OS 19.10

kisak-valve commented 5 years ago

Hello @Fushko, with Proton 4.11-8, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

f-fusco commented 5 years ago

Hello @Fushko, with Proton 4.11-8, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

Here it is: steam-629760.log Thank you.

Screenshot of the issue for reference: 20191110185600_1

alasky17 commented 5 years ago

@Fushko Could you try out a couple of things to try to narrow down what caused the change? 1) Try putting the following override in the launch options for the game instead of the logging (the quotations are important): WINEDLLOVERRIDES="dxgi=n" %command% 2) If that makes the game revert back to the good behavior, could you remove the launch option and get a log of the failure state with +dxgi,+d3d

You can get the log with the extra logging channels by going to ~/.steam/steam/steamapps/common/Proton 4.11 (or wherever your steam common folder is located) and copying the file user_settings.sample.py with the name "user_settings.py". Then edit user_settings.py and add +dxgi,+d3d to the end of the "WINEDEBUG" line.

f-fusco commented 5 years ago

The override makes the game normal again.

Here are the logs with no launch options and "+dxgi,+d3d" to WINEDEBUG: https://gofile.io/?c=ZWeORY (too big for GitHub)

alasky17 commented 5 years ago

@Fushko thank you for confirming the issue! This is a pretty complex problem, so I would suggest just using the override in the launch options in the meantime.

Thank you for the report, and I'll let you know if/when more testing would be useful :)

alasky17 commented 5 years ago

@Fushko After taking a look at the log you provided, there are a couple of follow up questions/requests. 1) There was a line in the log referencing a GeForce GTX 470 GPU -- I just wanted to double check that the only GPU you have in your rig is the 1660 Ti that you reported earlier?

2) Could you also get a log with the same channels (+dxgi,+d3d) of a "good" run with the dxgi=n override + 4.11-8?

kisak-valve commented 5 years ago

Hello @alasky17, GTX 470 is the expected fallback name for a generic DX11 capable nvidia card that Wine hasn't been taught about, found at https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/wined3d/directx.c#l803.