Monster Hunter World (582010)

[Yrds]

SystemInfo.txt

Distro: Arch
Kernel: 4.18.3-arch1-1-ARCH
GPU: Rx 480
Driver: mesa 18.1.6-1
CPU: FX 8350
RAM: 8GB 1333mhz

[JonasKnarbakk]

Distro: Ubuntu 18.04
Kernel: 4.15.0-32-generic
GPU: GTX980
Driver: 396.51
CPU: AMD Ryzen 7 2700X
RAM: DDR4 3000MHz 16GB

Launches to black screen after initial install. And will aggressively toggle windowed and full screen if you try to alt-tab out.

setting ScreenMode=Borderless in the config file graphics_option.ini located in the root folder of the installation and the game will work fine (Except for it taking ~10 seconds for the first logo to appear after launching). Didn't do much except load into a existing character and run around for a bit, but didn't notice any issues.

Already clocked a few hours on wine-esync-3.13-x86-64 which had little to no issues.

[kisak-valve]

Post from #199.
@LP0101 posted on 2018-08-23T01:01:40:

When exiting MH:W, the game closes completely, but the process doesn't quit, leaving your status as "in game" in steam.

~/.s/s/s/c/P/d/l/w/dxvk $ ps -aux | grep -i monster
luca     12753  0.0  0.1  63652 24812 tty2     S+   20:01   0:00 /bin/sh -c '/home/luca/.steam/steam/steamapps/common/Proton 3.7'/proton waitforexitandrun '/home/luca/.steam/steam/steamapps/common/Monster Hunter World/MonsterHunterWorld.exe'
luca     12754  0.0  0.1  91664 31920 tty2     S+   20:01   0:00 /usr/bin/python2.7 /home/luca/.steam/steam/steamapps/common/Proton 3.7/proton waitforexitandrun /home/luca/.steam/steam/steamapps/common/Monster Hunter World/MonsterHunterWorld.exe
luca     12832  153 17.2 7001288 2809540 tty2  Rl+  20:01  89:10 /home/luca/.steam/steam/steamapps/common/Monster Hunter World/MonsterHunterWorld.exe
luca     17022  0.0  0.0  21536  1112 pts/0    S+   20:59   0:00 grep --color=auto -i monster

The game does not quit until I manually kill PID 12832.

On Ubuntu 18.04

[LP0101]

I'm experiencing full system lockups on Proton. These completely lock me out of my computer, but audio still works. Can't even change TTY. Only way to recover is either a reboot, or to SSH in from a second PC and kill the Monster Hunter process.

This is not an issue until you alt tab out of the game the game loses focus. Once this happens even once, it will lock up eventually. Doesn't happen if the game never loses focus.

Also, Rumble is broken with Steam Controller. It sometimes get stuck on, and only turns off when pressing the Steam button. On an xbox pad, rumble doesn't work at all.

[libcg]

@LP0101 what's your hardware and software stack?

[LP0101]

@libcg
Hardware:
i7 5820k
16 GB DDR4 RAM
GTX 1080

I'm on Ubuntu 18.04, 396.51.0 nvidia drivers, Kernel 4.15

[drgnak]

I'm also getting freezes, using steam-runtime

$ uname -a
Linux lancelot 4.18.3-arch1-1-ARCH #1 SMP PREEMPT Sat Aug 18 09:22:54 UTC 2018 x86_64 GNU/Linux

nvidia 396.51

Contents of lshw is attached

[roadh0use]

Also having freezing issues with nvidia.
manjaro
nvidia 1060 6gb
driver 396.51
ive tried different kernels as well and all of them freeze randomly.

[libcg]

Anyone tried with 396.54 drivers?

[roadh0use]

reporting back that running the 4.14.65 kernel now and it has seemingly fixed the freezing issue on nvidia.

[LP0101]

I updated to 4.18.4 kernel and nvidia drivers 396.54. Not sure which is of these is the cause, but freezing it much more frequent now, game is practically unplayable. Will downgrade kernel and try again.

Edit: No luck downgrading kernel, looks like the issue is related to the 396.54 drivers

[libcg]

@LP0101 does enabling vsync help?

[LP0101]

@libcg I didn't play enough to draw any concrete conclusions, but I think that worked. Vsync & capping FPS at 60 certainly made it more stable, I'll update if it ends up crashing at any point tonight.

[drgnak]

@libcg I believe enabling vsync may have helped me as well. I've been able to get two hours of playtime without crashing so far. Will update if it ends up doing so.

EDIT: Spoke too soon; crashed shortly after I posted that.

[LP0101]

@drgnak still, 2 hours is an improvement. Before I turned on vsync, I wouldn't last more than 20 minutes (on 369.54)

[tyisafk]

Game won't launch for me on Ubuntu. Black screen for about 10 seconds then it closes. Worked perfectly fine on Manjaro. Attaching a log. Another user on Reddit with the same GPU series (R9 390) on the same driver stack had the same issue and solved it by switching from the radeon kernel driver to amdgpu. I've been on amdgpu the whole time so I'm stumped.

Ryzen 1700
AMD R9 390X 8GB
16GB RAM
Ubuntu 18.04.1 LTS

steam-582010.log

[Eragon5779]

Can't get the game running on Arch. Some sort of network error. It wants to take me to a link, but disappears before I can even read it. I only have a single NIC set up, so I have no idea what is going on.

CPU: i7-6700K
GPU: GTX 1080
Driver: 396.54-1
RAM: 32GB DDR4-2400
Distro: Arch
Kernel: 4.18.4-arch1-1-ARCH

lshw.txt

[xeals]

Also getting a network error, but the popup box is just black and crashes.

Hardware info, but the crash log is 60MB and difficult to upload anywhere (or even analyse).

[setzer22]

Game worked flawlessly for me, out of the box. I get slight FPS drops (from 30 to 25), as compared to windows, where they're less frequent, but it's barely noticeable. Note that I play on the lowest possible settings due to my hardware, same as on Windows. Here's my system specs:

Distro: Antergos (Arch Linux)
Kernel: 4.18.3-arch1-1-ARCH
GPU: Nvidia GTX 860M
Driver: nvidia 396.51-5
CPU: i7-4710HQ
RAM: 16GB 1333Mhz

A minor issue, is that using KDE, I cannot easily minimize the game from fullscreen mode. Attempting to do so causes system freezes for a short while. Similar to what @JonasKnarbakk mentioned, but definitely not getting a full system when focus is lost in my case (as @LP0101 reported).

[Skylead]

Distro: Ubuntu 18.04
Kernel: 4.15.0-32-generic
GPU: GTX980
Driver: 396.51
CPU: AMD Ryzen 7 2700X
RAM: DDR4 3000MHz 16GB

Launches to black screen after initial install. And will aggressively toggle windowed and full screen if you try to alt-tab out.

setting ScreenMode=Borderless in the config file graphics_option.ini located in the root folder of the installation and the game will work fine (Except for it taking ~10 seconds for the first logo to appear after launching). Didn't do much except load into a existing character and run around for a bit, but didn't notice any issues.

Already clocked a few hours on wine-esync-3.13-x86-64 which had little to no issues

I had a similar experience with needing borderless mode to get it working properly

Distro: Arch 4.18.4
GPU: GTX970
Driver: 396.54
CPU: i7 3770k
RAM: DDR3 16GB

Controller support working, no issues playing game or with performance after the change to borderless

[cjwijtmans]

you should really try the .54 drivers which fixes resource leaks.

[Xaenalt]

On attempting to load the game, I run into E_FAIL: IDX11Device->CreateShaderResourceView(pres->getHandle(), &srvDesc, &mpView) and a black screen

Nvidia 396.54-1.fc28.x86_64
Proton 3.7

About half the time afterwards, it will exit, otherwise the process will linger until kill -9'd

[LP0101]

Anyone running this on Vega 64? How's the performance?

[Xaenalt]

I was able to fix the crash on first boot by messing with the graphics_setting.ini file. I set most of the variables to low and it finally loaded. I'll try to bisect which setting caused it

[Xaenalt]

Found it, setting VolumeRenderingQuality to Highest was the culprit, I can set the other settings as high as possible with no E_FAIL. Setting VolumeRenderingQuality to anything under Highest worked for me

[doitsujin]

@Xaenalt can you test if the error happens with Nvidia 396.51.02 (i.e. the Vulkan beta)? There's a known issue with the stable Nvidia driver failing to create buffer views in some cases, which might cause this issue.

[hakzsam]

The issue seems to have been fixed by HansKristian-Work/vkd3d-proton@02c7ec4.

Feel free to give it a try by updating vkd3d-proton. Thanks for the report.

[kisak-valve]

Hello @nhkode, the SteamOS 3.3 beta update includes a video driver refresh. Can you opt into the beta and retest how this game behaves for you?

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

[nhkode]

Hello @nhkode, the SteamOS 3.3 beta update includes a video driver refresh. Can you opt into the beta and retest how this game behaves for you?

@kisak-valve : Looks like the issues are still there. While I was able to complete the "Under the Veil of Death" quest now with artifacts only showing up once for a very brief time I still had a crash and severe visual artifacts in the "Legiana left behind" quest. OS Build was 20220630.100.

[hakzsam]

Are you still experimenting issues RADV and up-to-date drivers here?

[euclip]

Hi, it's me again. Thanks so much for fixing the bug I reported earlier. Once again I am using a Gnome Wayland desktop session, and I am running the game with Proton Experimental.

Distro: Fedora Workstation 36
Kernel: 5.18.13-200.fc36.x86_64
GPU: AMD RX 6800 XT
Driver: Mesa 22.1.4-2.fc36
CPU: AMD Ryzen 7 5800X
RAM: 3600MHz 16GB

I'm not totally sure if this is an issue for this tracker, or if I should bring this somewhere else, but here goes: there seems to be some kind of bottlenecking going on with this game that I haven't noticed elsewhere. The TL;DR is that I can lower or raise the game's graphical settings without significantly affecting the game's framerate.

I can raise the graphics settings to highest, and see GPU utilization in 90s percentagewise, or lower the graphics settings to "mid" and see GPU utilization in the 70–80% range, or I can even go all the way down to the lowest graphical preset and see GPU utilization in the 60–70% range. I used Mangohud for measurements.

I've set the game to cap at 120 FPS. At mid settings the FPS varies a fair bit, very rarely peaking at 120 FPS, but mostly sits somewhere in the 90–110 FPS range. The strange thing is that I see roughly the same FPS at both the highest and lowest graphical presets. With all graphics presets CPU usage hovers around 50%.

[hakzsam]

@euclip Did this situation improve? I don't think this can be considered a bug though.

[euclip]

@hakzsam Thank you for asking. It did not, but I've come to believe that it's probably a problem with the game engine itself rather than Proton.

[hakzsam]

Can you guys report any issues with Mesa (RADV) and up-to-date driver?

[cain05]

I launched this game for the first time in a while today. DX12 mode is pretty much unplayable for me as there's a lot of stuttering. DX11 mode does not have this. It doesn't seem to be a shader issue, at least not to me because it never goes away. Using DX11 is the work around, but DX12 does offer a higher frame rate, so it would be nice if it was usable.

Proton: 7.0-5, Experimental
Distro: Arch
Kernel: Linux 6.0.12-zen1-1-zen
GPU: 5700XT
Driver: mesa 22.2.3-1
CPU: AMD 3600
RAM: 16GB 3600mhz

[TGRCdev]

At some point, this game's stability has regressed from perfect to unplayable. Any time I start a mission, my entire DE crashes 2 minutes in. DX11 and DX12 are the same, High or Low settings.

Proton: 8.0-2
Distro: Debian testing
DE: Xfce 4.18 (Also happened on KDE Plasma)
Kernel: Linux Liquorix 6.2.14-1
GPU: AMD Radeon RX 6500 XT, 8GB VRAM
Driver: mesa 22.3.6
CPU: AMD Ryzen 5 3600 6-core
RAM: 2x8GB DDR4 @ 2666 MHz

[kisak-valve]

Hello @TGRCdev, can you test how the game behaves with a 6.1.x kernel? I suspect you're seeing https://gitlab.freedesktop.org/drm/amd/-/issues/2457.

[TGRCdev]

Switching to Proton 7.0 made the game stable enough to finish a Jyuratodus hunt (~15-20 minutes). Though I will try playing with Proton 8.0 with Linux 6.1.0-8-rt-amd64.

---

Proton 8.0 is stable with kernel 6.1.0-8-rt-amd64 for another Jyuratodus hunt. I'll keep playing to see if it lasts.

[omar-selo]

Game crashes after launch. Using Proton 8.0-2. Linux 6.2.0-23-generic.
steam-582010.log

[ThePyrotechnic]

Game crashes for me while in a hunt while in a fight (will never crash while walking around a safe zone)
I truncated the log file since the middle of the file seems to only contain 1 or 2 vulkan debug lines, but I can upload more if needed.
steam-582010-truncated.log

[Steamvoker]

Having an issue where the in-game tutorial videos show SMPTE color bars instead.

Distro: EndeavourOS
Kernel version: 6.4.1-arch2-1
GPU: RTX 4090
Driver/LLVM version: nvidia 535.54.03
Proton version: experimental
CPU: AMD Ryzen 9 7950X
RAM: 2x32GB DDR5 6000MHz

[FlpCastilho]

Game display heavy artifacts (vertex explosions) independently of the Proton version used (some users recommend using Version 7 as it solves the artifacts for them).

Distro: Arch Linux
Kernel Version: 6.6.5-arch1-1
GPU: RTX 2080S
Driver version: Nvidia 545.29.06
CPU: Ryzen 7 5700x

[GoLD-ReaVeR]

Replying to #175 (comment)

Can we see a screenshot of this issue?

[FlpCastilho]

Here are two screenshots I took yesterday after posting the comment, some pointers: I have tested what most people suggest on ProtonDB for the game (some people there are also having artifacting issues): Change to VKD3D and use an older version of Proton (normally 7).
Having tested both methods separately and together my findings are: changing the version from DX11 to DX12 helps to diminish the intensity and number of artifacts, but they still occur, both screenshots shows relatively mild artifacts as they can flash and take up the whole game window. Using older Proton versions did not help me, apart from severely lowering my FPS.
Edit: Decided to play some hunts and managed to reproduce it again, added screenshots.

Screenshots

[GoLD-ReaVeR]

Alright, I went to the same location and was unable to reproduce this issue.

I'm running an rtx3090ti with tkg build compiled at 2023-10-29 with command line arguments:
PROTON_LOG=1 OBS_VKCAPTURE=1 VKDTO_HUD=1 VKDTO_OPT="pos=tr" VKDTO_FILE=/tmp/linux-hunter PROTON_ENABLE_NVAPI=1 PROTON_USE_SECCOMP=1 DXVK_STATE_CACHE=0 VKD3D_FEATURE_LEVEL=12_0 %command% -nofriendsui -udp

I run in D3D12 mode with high res textures enabled. My driver version is 535.43.11.

@ChorizoLinguizo Looking at that I would first recommend upgrading the nvidia drivers. The artifact shouldn't happen due to a driver bug, but just in case. In the nvidia settings I have allow flipping and use conformant texture clamping enabled. The image settings is set to high performance. You should try copying these settings and see if that helps. I've heard of some bugs pertaining to conformant texture clamping so it's not that far fetched that this causes an issue for you.

[FlpCastilho]

@GoLD-ReaVeR unfortunately following your instructions did not help, artifacts are still present, again, they happen at random so I'm not entirely sure what would be steps to repro this issue, apart from the fact that they are more common in the green and blue fireflies and with certain monsters attacks.

[GoLD-ReaVeR]

Well besides that I got nothing. If you say it occurs on older versions as well you have a scenario that you shouldn't be having and that I never encountered. The last time I had rendering glitches was when I switched to D3D12 when the support for it was literally bleeding edge (aka prone to breaking), but those issues have pretty much been fixed now. I used to run a GTX1080 as well and had no rendering issues either. It could be related specifically to your video card in Linux, because I also remember not seeing these issues in windows with a streamer I followed and I recall him having the same video card (RTX2080) at the time.

[mits-haruko]

@ChorizoLinguizo For some reason I can "fix" this issue by reverting to the Nvidia 525 driver family, which makes me think this is a weird interaction with whatever new Nvidia has included in their new drivers.

[kisak-valve]

Monster hutner world: controler not being dected and mosue camera control is broken

Issue transferred from #7811.
@testc2n14 posted on 2024-06-03T22:15:47:

Compatibility Report

• Name of the game with compatibility issues: monster hunter world
• Steam AppID of the game:582010

System Information

• GPU: 6800
• Video driver version: OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.0.8
• Kernel version: e.g. 6.8.11-300.fc40.x86_64
• Link to full system information report as Gist:
• Proton version:steam default

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.

the game dose not not launch affter trying to run the game with that command, even with otu the command

Symptoms

so nwo affter runnign the proton log command the game dose not launch at all but befor the gaem woudl not reconsie the controler at all even tho both steam and my OS could reconise it perfectly fine and take inputs from it.
thought this might be helpfull to add

             .',;::::;,'.                c2n14@fedora 
         .';:cccccccccccc:;,.            ------------ 
      .;cccccccccccccccccccccc;.         OS: Fedora Linux 40 (KDE Plasma) x86_64 
    .:cccccccccccccccccccccccccc:.       Host: B650M DS3H 
  .;ccccccccccccc;.:dddl:.;ccccccc;.     Kernel: 6.8.11-300.fc40.x86_64 
 .:ccccccccccccc;OWMKOOXMWd;ccccccc:.    Uptime: 8 hours 
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:.   Packages: 3164 (rpm), 78 (flatpak) 
,cccccccccccccc;MMM.;cc;;WW::cccccccc,   Shell: bash 5.2.26 
:cccccccccccccc;MMM.;cccccccccccccccc:   Resolution: 3840x2160 
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc:   DE: Plasma 6.0.5 
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc;   WM: kwin 
ccccc:XM0';cccc;MMM.;cccccccccccccccc'   Theme: Breeze-Dark [GTK2], Breeze [GTK3] 
ccccc;MMo;ccccc;MMW.;ccccccccccccccc;    Icons: Vivid-Dark-Icons [GTK2/3] 
ccccc;0MNc.ccc.xMMd:ccccccccccccccc;     Terminal: konsole 
cccccc;dNMWXXXWM0::cccccccccccccc:,      CPU: AMD Ryzen 7 7800X3D (16) @ 5.050GHz 
cccccccc;.:odl:.;cccccccccccccc:,.       GPU: AMD ATI Radeon RX 6800/6800 XT / 6900 XT 
:cccccccccccccccccccccccccccc:'.         Memory: 10857MiB / 31723MiB 
.:cccccccccccccccccccccc:;,..
  '::cccccccccccccc::;,.                                         
                                                                 

Reproduction

---

@testc2n14 commented on 2024-06-03T22:17:28:

i know ia dded the hardwre info but i guess i didn;t i will palce ti ehre, gpu is a 6800, drivers for mesa are 24.0.8. the kernnel is: 6.8.11-300.fc40.x86_64, and ehre is a pastbin thign to the full steam system report https://pastebin.com/9XhgCitP

[kisak-valve]

Fcitx5 can't input chinese character in Monster Hunter World

Issue transferred from #7994.
@po4920826 posted on 2024-08-17T17:05:13:

Compatibility Report

• Name of the game with compatibility issues:Monster Hunter:World
• Steam AppID of the game:582010

System Information

• GPU: RTX 4070 SUPER
• Video driver version: nvidia 555.58.02
• Kernel version: 6.10.5-arch1-1
• Link to full system information report as Gist:
• Proton version:proton-9.0-2
  steam-582010-proton9-2.log

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.

Symptoms

I am using the Steam Proton-9.0-2 compatibility layer on Arch Linux with the KDE Plasma 6 desktop (in Wayland mode) to play Monster Hunter: World. When I press Enter in-game to open the chat window, I am unable to type text using the Fcitx5 Chinese input extension. The input extension is running properly, but no Chinese characters are being input into the chat window. This issue does not occur when using the Proton-8.0-5 version.

Reproduction

install fcitx5 IME:
sudo pacman -S fcitx5 fcitx5-gtk fcitx5-qt fcitx5-chinese-addons fcitx5-config-qt

edit ~/.bash_profile , add these lines:
export XMODIFIERS=@im=fcitx
export GTK_IM_MODULE=fcitx
export QT_IM_MODULE=fcitx

Reboot, open systemsettings -- input method -- add input method ,add pinyin

Launch steam ,play Monster Hunter :World , press Enter in-game to open the chat window.Input chinese character with fcitx5 pinyin (just typing randomly ,press space to submit).In my case,no Chinese characters are being input into the chat window.

I have uploaded a video on youtube:
https://www.youtube.com/watch?v=ug7eZd-fm90