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 https://github.com/ValveSoftware/Proton/issues/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.

[Zero86Sk]

The game is on a black screen when you run it, for a but. But once you get ingame it plays the same as on Windows for me. I did a few quests Online and it went without problems.

My Specs: omputer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected

Processor Information: CPU Vendor: AuthenticAMD CPU Brand: AMD FX(tm)-8350 Eight-Core Processor CPU Family: 0x15 CPU Model: 0x2 CPU Stepping: 0x0 CPU Type: 0x0 Speed: 4000 Mhz 8 logical processors 8 physical processors HyperThreading: Unsupported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Supported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported

Operating System Version: Linux Mint 19 Tara (64 bit) Kernel Name: Linux Kernel Version: 4.15.0-33-generic X Server Vendor: The X.Org Foundation X Server Release: 11906000 X Window Manager: Mutter (Muffin) Steam Runtime Version: steam-runtime-beta-release_2018-06-14

Video Card: Driver: NVIDIA Corporation GeForce GTX 1050 Ti/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 396.54 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz VendorID: 0x10de DeviceID: 0x1c82 Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1080 Desktop Resolution: 1920 x 1080 Primary Display Size: 20.08" x 11.42" (23.07" diag) 51.0cm x 29.0cm (58.6cm diag) Primary Bus: PCI Express 16x Primary VRAM: 4096 MB Supported MSAA Modes: 2x 4x 8x 16x

Sound card: Audio device: Realtek ALC889

Memory: RAM: 7994 Mb

Miscellaneous: UI Language: English LANG: sk_SK.UTF-8 Total Hard Disk Space Available: 505611 Mb Largest Free Hard Disk Block: 191015 Mb VR Headset: None detected

Recent Failure Reports:

only minor issue could be alt+tab dosnt work.

[Xaenalt]

When attempting to use a third party xbox controller, I did encounter a fair number of issues. It seems the mapping in config.ini starts at 0, whereas the input mappings from xboxdrv start at 1. This resulted in some very odd gameplay for a bit until I changed it

Controller:        Rock Candy Gamepad Wired Controller
Vendor/Product:    0e6f:011f
USB Path:          001:009
Controller Type:   Xbox360

I was able to get the triggers set up finally: xboxdrv --silent --trigger-as-button --detach-kernel-driver

[JOYPAD]
A=0
B=1
X=2
Y=3
LEFT=POV
RIGHT=POV
UP=POV
DOWN=POV
START=9
BACK=8
LT=6
LB=4
RT=7
RB=5
LSTICK_PUSH=11
LSTICK_VERT=Y
LSTICK_HORZ=X
RSTICK_PUSH=12
RSTICK_VERT=RX
RSTICK_HORZ=Z

[Xatulu]

Game working smoothly for me, Performance not as great as with Windows (might be that i did not notice it in Windows due to GSYNC), but very playable.

However, after beating Xeno, the Save Game Corruption happens and I can't load this save file anymore, due to missing Codecs so the cinematic can't be played and the game crashes to Desktop.

[Xaenalt]

@doitsujin You wouldn't happen to have an rpm repo that contains it handy would you? If not, let me see what I can do. if nothing else, I'll update when that driver makes it mainstream

Also, can confirm that alt-tabbing out of the game does cause a crash and/or host lockup at some points. Think that one's Nvidia-related too?

[Kaylebor]

It worked for me with the latest Nvidia drivers and Linux kernel, I spent yesterday's afternoon playing without much issue. Hardware includes an AMD Ryzen 7 2700X paired with an NVIDIA 1700 Ti, on Ubuntu Budgie 18.04. On the software side, apart from the prerequisites of using latest drivers (396 on Nvidia) and kernel (4.18.5), I activated the beta version of Proton (3.7.4).

Note that the game did work with outdated kernel and drivers on the main Proton version (3.7), but the Xinput issues outlined below prevented me from playing, and there were some graphic artifacts in the main menu, so this should be discouraged.

Issues:

• Performance loss (expected because of the DirectX-Vulkan translation, not an issue with the shown hardware with some conservative graphics options)
• V-Sync issues (lower performance with it activated, pronounced screen tearing with it disabled. Graphical issues mostly, not that noticeable after a while)
• Small freezes/hiccups (not common, but they are there; might be a game issue though. I had only 2 or 3 in the entire play session of roughly 4 hours)
• Xinput issues
  • Initially, could not play the game because something was sending random direction inputs, rendering menu navigation impossible.
  • Don't know what solved this, but keeping the latest driver/kernel update and after an OS update/restart, the issue disappeared.
  • Could be related to the Steam Controller? Though I could play perfectly with the controller afterwards.
• Complete game freeze after long playing sessions. Maybe once every hour and a half or so, I had this happen twice.
  • The OS itself worked fine, so I could just kill the game with "kill -9". Still, this can be a deal breaker for some.

In my case the game is playable, but there are still some rough edges to keep track of.

[LP0101]

Can anyone confirm if the complete game/OS freezes happen on AMD as well, or if it's only an Nvidia-related issue?

[bentrevett]

Distro: Ubuntu 18.04 Kernel: 4.15.0-33-generic GPU: GTX1080 Ti Driver: 396.54

Game works perfectly fine except for the same OS lockups as @LP0101 and @Kaylebor mention. Seem to happen completely at random, sometimes the game will only run for 20 minutes, sometimes for multiple hours.

EDIT: Tried updating kernel to 4.18, Proton to 3.7-4 beta and using V-Sync on/off with windowed and borderless windowed. Still getting OS lock-ups.

[LP0101]

It seems like playing in Windowed Mode with V-Sync on fixes the lockup issues. I was able to play for over 4 hours without a lockup, which is longer than I've ever managed in borderless window.

Driver version: 396.54 Kernel Version: 4.18.5-041805-generic

[suika-ibuki]

Unfortunately, I still experienced lockups with both Windowed & Borderless Windowed + V-Sync after approximately 1-2 hours of being in game, sometimes less. For what it's worth, in both instances, I made sure to intentionally lose window focus as per @LP0101's earlier post. As of yet, I haven't tried playing for any length of time without losing window focus to see if the game doesn't lockup.

Distro: KDE Neon (Ubuntu 16.04) Kernel: 4.15.0-33-generic GPU: GTX 1070 Driver: 396.54 CPU: Intel 6700K RAM: 16GB DDR4 @ 3000MHz Proton Version: 3.7-4 Beta

[damienleone]

Could you please attach nvidia-bug-report.log.gz next time you experience a lockup?

[suika-ibuki]

Certainly, here you go, @damienleone.

nvidia-bug-report.log.gz

[ghost]

Playing any video in-game results in a page fault due to missing function implementation;

wine: Call from 0x7b44abbc to unimplemented function mfplat.dll.MFCreateMFByteStreamOnStream, aborting

This function has yet to be implemented upstream.

Log: steam-582010.log

Replication steps: When in-game, press start, go to Info->Player Guide->View Tutorials->Hunter Equipment and press Play Movie.

Note: This does not happen to scenes in-game, they are not pre-rendered video files, thus does not crash the game.

[ghost]

The forever running process when exiting out, is caused by an exception;

wine: Unhandled exception 0x40000015 in thread 53 at address 0x1428f3032 (thread 0053)

which then ends up with a forever ending wait;

err:ntdll:RtlpWaitForCriticalSection section 0x14484a320 "?" wait timed out in thread 0053, blocked by 002d, retrying (60 sec)

Log: steam-582010.log

[setzer22]

@fureloka I cannot replicate the issue you mention with playing in-game videos. To confirm this, I just opened the gallery and watched a couple of scenes. Please note that I have not completed the game so I cannot verify wether all scenes work, but I've been able to play all the way to HR14 watching the videos just fine.

[Xatulu]

@setzer22 @fureloka Based on my experiences, it plays just fine - at least until you beat the final boss. The video file trying to get played after leads to game crashes. Probably due to codecs missing (this also happens on Windows in Certain Regions where the Codecs are missing).

Also, what crashes my game is playing Preview Videos of Weapons/Tools in the Inventory.

Other In Game Videos were working perfectly fine.

[ghost]

@setzer22 @Xatulu Apparently I wasn't specific enough, I'm not talking about the in-game rendered scenes, these are rendered in real time with the engine, thus plays fine. Capcom wouldn't have the time to make pre-rendered video for those, due to the amount of style combinations.

What I'm referring to are the pre-rendered video files that are played in-game, mostly tutorials and previews which @Xatulu mentioned.

When in-game, press start, go to Info->Player Guide->View Tutorials->Hunter Equipment and press Play Movie.

If it doesn't crash there, you have a magical version of Proton. This will also crash with the latest version of Wine, as MFCreateMFByteStreamOnStream is unimplemented.

[LP0101]

Has anyone gotten a chance to test the latest proton beta? Has it done anything about the crashes?

[Xaenalt]

Crashes, full system hangs, and game persisting after window exit still occur on 3.7-5 Beta Nvidia 396.54-1.fc28.x86_64 Kernel 4.17.19-200.fc28.x86_64

There may be some fixes in the Nvidia beta driver, but I can't find a good beta rpm to install to check

[kisak-valve]

Monster Hunter World - all surfaces have specular highlighting

Issue transferred from https://github.com/ValveSoftware/Proton/issues/1092. @shadywack posted on 2018-08-31T19:51:15:

Issue: specular highlighting on all surfaces Steps to reproduce: launch game and observe surfaces Observations: it depends on the texture and what the game engine calls for, in some cases its subtle, but it depends on the material to make it more obvious. In a rainy environment it actually looks cool, but I don't think it's what the renderer intends. I'd take a screenshot but it's obvious in motion. Wood should not have a specular highlight on its surface. System: Ryzen 7 1800X on a Vega64 using the RADV/Mesa 18.3 driver (from the Padoka PPA listed in the quickstart guide) Ubuntu 18.04, Steam beta client running Proton 3.7-5

On a personal note: Thanks for all your hard work! This is some awesome coding to see, and probably the best thing I've ever seen Valve do. If there's a fix for this issue great, but if not, it's really not the end of the world. I can play this game natively at 4k in Windows but on Proton there's a pretty substantive hit to drop the fps down to 20-ish on my hardware. It runs buttery smooth at 60fps at 1440p however and I absolutely love it. Many thanks.

[kisak-valve]

Monster Hunter World - Crash on Credits Cutscene - Missing Windows Media Codecs

Issue transferred from https://github.com/ValveSoftware/Proton/issues/1125. @Estard posted on 2018-09-01T10:28:18:

After defeating the final boss in MH: World the game tries to load a cutscene where, according to this reddit post: https://www.reddit.com/r/MonsterHunter/comments/99cqi4/xeno_save_corruption_bug_does_not_exist_proof/ it needs certain codecs contained in the Windows Media Feature Pack in order to play said cutscene. I suppose that is the reason why the game also crashes at that point when playing it with Proton. It would be well appreciated if a workaround could be implemented for this and other games that require it.

Tested on Proton 3-7-5 and winestaging 3.14 (64 bit) esync + dxvk

[Xaenalt]

@doitsujin Can confirm that VolumeRenderingQuality can be set to Highest on Nvidia 396.54.02

Testing if the crash is reproducible with that driver

[Xaenalt]

Can confirm the game still crashes accompanied with a system lockup on Nvidia 396.54.02

[roadh0use]

What a letdown. I was hoping newest nvidia driver would fix the lock up. has anyone narrowed down what causes the freezing? I get a full system lockup that can only be fixed by power cycle I have tried almost every kernel manjaro has listed. the latest lts kernel gives the least amount of lockups but it still happens

[Xaenalt]

I'm not sure what debug logs to provide, if someone can post a what to do and what logs are needed, I'll gladly provide them. I'd imagine something like perf record?

[LP0101]

Has anyone tried replacing the proton-provided DXVK binaries with the newly-released 0.71 binaries, see if that fixes anything?