Mordhau (629760)

[KorinFlakes]

Whitelist Request

• Name of the game to be whitelisted: Mordhau
• Steam AppID of the game: 629760

System Information

• GPU: GTX 1060 (6gb)
• Driver/LLVM version: NVIDIA 418.56
• Distro version: Manjaro Linux
• Specs
• Proton version: 4.2-3

I confirm:

• that pressing the Play button in the Steam client is sufficient.
• that runtime config options are necessary to run the game.
• that no workarounds other than PROTON_* env variables are necessary.

Issues

• I haven't experienced any issues.
• There are no issues left open for this game.
• Although I consider the gaming experience equal to Windows there are remaining issues:

[Bumbadawg]

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]

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]

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

[kisak-valve]

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]

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

[Rabcor]

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]

#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]

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]

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]

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

[Rabcor]

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]

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

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

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]

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]

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]

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]

@waylon531 try disabling Steam overlay.

[aeikum]

@Fushko I believe this issue with your GPU should be fixed in 4.11-9. Please retest.

[f-fusco]

@Fushko I believe this issue with your GPU should be fixed in 4.11-9. Please retest.

The texture issue is fixed, thank you!
However, the game crashes on a few occasions. I'll try to see if I can reproduce it and report back with the logs.

[kisak-valve]

Hello @waylon531, can you retest if the performance issue you saw with this game and Proton 4.2-5 has been resolved?

[f-fusco]

steam-629760.log.tar.gz

App crash. FPS got very choppy a few seconds before crashing.
It seems to happen mostly in the "Frontline" game mode with high player counts.
Proton 5.0-5, 1660 Ti 440.44, Pop OS 19.10

[octinhuh]

The game doesn't seem to launch anymore after the latest patch. I've seen word on Reddit about both updating mod.io API keys, and deleting Saved and Intermediate folders in the steam library compatdata folder for Mordhau, but neither of these worked for me. Log file from Proton. System Information

[f-fusco]

The game doesn't seem to launch anymore after the latest patch. I've seen word on Reddit about both updating mod.io API keys, and deleting Saved and Intermediate folders in the steam library compatdata folder for Mordhau, but neither of these worked for me. Log file from Proton. System Information

Same here. mordhau-start-crash.log.gz
Though some windows users report crashes at start so it's probably on their end.

[kisak-valve]

Mordhau Patch #17 on Proton

Issue transferred from #3699.
@scraatch posted on 2020-03-28T19:47:07:

Compatibility Report

• Mordhau
• Steam AppID of the game: 629760
• Current Steam Discussion Thread Regarding This Issue: https://steamcommunity.com/app/629760/discussions/1/2149846913186214881/

System Information

• GPU: GTX 1050TI
• Driver/LLVM version: 440.64
• Kernel version: 5.4.28_1
• Proton version: 5.0-5

Symptoms

Does not Run

Reproduction

Newest update breaks game

This seems to be the issue for me and other users.

LogShaderLibrary: Display: Failed to load Shared Shader Library: Global and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: WebBrowserWidget and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: WebBrowserWidget_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: WebBrowserWidget and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: WebBrowserWidget_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: DiscordRpc and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: DiscordRpc_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: DiscordRpc and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: DiscordRpc_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: modio and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: modio_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: modio and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: modio_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: CryptoKeys and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: CryptoKeys_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: CryptoKeys and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: CryptoKeys_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: MeshEditor and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: MeshEditor_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: MeshEditor and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: MeshEditor_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: DatasmithContent and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: DatasmithContent_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: DatasmithContent and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: DatasmithContent_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: MediaCompositing and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: MediaCompositing_SC and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: MediaCompositing and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: MediaCompositing_SC and no native library supported.
LogRHI: Display: Failed to open default shader pipeline cache for Mordhau using shader platform 0.
LogShaderLibrary: Display: Failed to load Shared Shader Library: Mordhau and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: Mordhau_SC and no native library supported.
LogRHI: Display: Failed to open default shader pipeline cache for Mordhau using shader platform 0.
LogShaderLibrary: Display: Failed to load Shared Shader Library: Mordhau and no native library supported.
LogShaderLibrary: Display: Failed to load Shared Shader Library: Mordhau_SC and no native library supported.
LogRHI: Display: Failed to open default shader pipeline cache for Mordhau using shader platform 0.

[alasky17]

For anyone encountering this failure: Turning off esync should get you in-game as described on Protondb. (If you have fsync, you will need to turn off both fsync and esync.)

Add the following to your launch options for Mordhau: "PROTON_NO_ESYNC=1 %command%"

[smirgol]

With Proton 5.0-6 the game does not start for me.
When I force to use 4.11-13 it starts, but black screen. When I then apply PROTON_NO_ESYNC=1 (to 4.11-13) it then starts (and works pretty well).
I'm wondering why it does not work in the higher Proton version.

[kisak-valve]

Mordhau : Compatibility issue

Issue transferred from #3830.
@htjan posted on 2020-05-04T14:01:53:

Compatibility Report

• Name of the game with compatibility issues: Mordhau
• Steam AppID of the game: 629760

System Information

• GPU: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280]
• Driver/LLVM version: Mesa 19.1.2 - padoka PPA (LLVM 8.0.0)
• Kernel version: 5.4.0-0.bpo.4-amd64
• Link to full system information report as Gist: https://gist.github.com/htjan/987e32af503947a8e66e560a4569f72a
• Proton version: 5.0-7, 4.11-13, 4.2-9, 3.16-9, Proton-5.2-GE-2, Proton-5.4-GE-3, Proton-5.6-GE-2

I confirm:

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

steam-629760.log

Symptoms

Hi,
I can't start Mordhau. When I launch the game, it crashes in less than a second.
Steps :

• Open Steam
• Select Mordhau
• Press the "play" button.
• The play button turns to a "stop" button for less than a second
• The button turns back to the play button.
• Neither Mordhau screen nor error message are displayed.
  I tried several Proton version, including some Glorious Eggroll one's without any succes, and experiencing the same problem.

Reproduction

On steam, select Mordhau then press play.

[k4ffee]

hi @htjan , just a shot in the dark - did you tried to start Mordhau with PROTON_NO_ESYNC=1 %command% as launch option ?
Also, your steam-log is empty, what looks strange to me. But I have no clue how to address this :/

[htjan]

Hi @k4ffee,
thanks for your answer.

I tried to start mordhau with PROTON_NO_ESYNC=1 %command% launch option but it didn't give any result.

I can understand that without log, you can't do anything.

I give up with this problem for the moment. I wanted to install mint/lmde and manjaro for a few months now. I'll see if mordhau can launch this way.

Thanks a lot for trying to help me. Bye :)

[htjan]

Hi @k4ffee,

For a reason I can tell, Mordhau now works on my system.

I just upgraded my system with security and recommanded update, upgraded my kernel and tried, with success to launch MORDHAU with the last proton version avalaible now.

If it might help anyone, MODHAU works fine now, with :

• kernel : 4.19.0-9-amd64 Plans for contributing back to upstream? #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux
• Proton : 5.0.9
• libdrm-amdgpu1:amd64 : 2.4.100-3bpadoka0
• libegl-mesa0:amd64 : 19.1.2-0bpadoka0

I have to tinker it a little to get a better fps average.

[Unkn0wn-MDCLXIV]

@waylon531
Have you found a way to fix the random freezes?

[Rsad1234]

Ubuntu 20.04.2 Nvidia GTX 1070(Official Nvidia card). Ryzen 7 3700x 8 Core. Heavy Choppyness and freezing. Used multiple different drivers including manually installing beta branches of both the vulkan and nvidia ready releases. Tried the GE proton and official proton versions down to Proton v5.xx. Not found out how to get rid of choppyness and game eventually always crashes after about 20m

[slizersteam]

currently proton experimental.
but same issues on older versions.
shows 150+ fps but it feels slow is this normal behavior ?
amd vega64 on os drivers
Arch manjaro
edit:

was missing vulkan libs works great now :)

[ManInTheSuit]

Runs great on Proton experimental, doesn't run with Proton GEs (tested 6.13 and 6.20). I would like it to be able to run with GE to use FSR

[slizersteam]

what happend, suddenly Message, "DX11 feature level 10.0 is required to run the engine." [OK]
current proton experimental.

-dx12 run paramenter fixed it

[Rorkh]

Shown in steam as "Running" but no window appears. Tried with Proton Experimental, 8.0-4 and 5.13-6 same result and empty log