ValveSoftware
Monster Hunter Wilds (2246340)
Compatibility Report
- Name of the game with compatibility issues: Monster Hunter Wilds Beta
- Steam AppID of the game: 2246340
System Information
- GPU: RTX 4070
- Video driver version: 550
- Kernel version: 6.8.0-40-generic
- Proton version: Experimental
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Symptoms
The game crashes on launch It appears to be an nvidia exclusive issue. It is fixed using the latest vkd3d-proton build. Can a new proton hotfix build be released including the vkd3d-proton changes?
Reproduction
Launch the Monster Hunter Wilds beta on an nvidia system.
Hello @CreatureDev, the automated [bleeding edge] beta branch (https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge) should include whatever upstream change to VKD3D-Proton you're interested in while you wait for that change to make it into a more formal release of Proton.
Hi, using Proton-Experimental [bleeding-edge] fixed the initial crash that also used to happen for me.
Also, after the logo's screen, the following error happen:
Using VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 in the game's launch options on Steam fixed it, and now it works normally.
Now is just to wait for the open beta to be properly released.
Using
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2in the game's launch options on Steam fixed it, and now it works normally.
From what I understand this is a driver issue. I created an issue for it as well in the vkd3d-proton repo, though, if it can be fixed there.
Game is crashing KDE Plasma on my end, and flickers in fullscreen. Same issues encountered on Dragons Dogma 2 since recent update, been unable to find a fix.
EDIT: Unlike DD2, running with Gamescope seems to fix the issue.
Confirming the findings noted in https://github.com/ValveSoftware/Proton/issues/8206#issuecomment-2450622534. Requiring use of self-built bleeding-edge, error after Re-Engine's splash, fixed with VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2. Linux Mint 22, NVIDIA GeForce RTX 4070 550.120, Linux 6.8.0-48-generic x86_64
Slightly different results for me, I had to switch to Proton Bleeding Edge in Steam, which allowed the game to start and compile the shaders and reach the "could not connect to servers" screen (as expected since the servers aren't up for another 4-5 hours) without any errors, no need to change any launch options. I'm also using KDE/Plasma and not seeing any flickering.
I'm on Bazzite 41, Linux bazzite 6.11.5-307.bazzite.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Oct 28 15:13:19 UTC 2024 x86_64 GNU/Linux, with Nvidia driver 565.57.01 (current beta driver I believe, I guess the default on Bazzite, I haven't intentionally changed that) on an RTX 3080 Ti.
Using
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2in the game's launch options on Steam fixed it, and now it works normally.
Tried this plus the bleeding edge experimental, with Void Linux, NVIDIA 550.127 drivers. Still crashes with the same error after RE logo.
EDIT: I just forgot to put %command% lol, fixed. It boots fine now.
My game renders the menu HUD, but not any 3D. Its just a black screen with HUD.
bleeding edge proton experimental amd 6750xt
My game renders the menu HUD, but not any 3D. Its just a black screen with HUD.
bleeding edge proton experimental amd 6750xt
Disabling the upscaller fixed it. Both AMD FSR 3 and XeSS dont work.
My game renders the menu HUD, but not any 3D. Its just a black screen with HUD. bleeding edge proton experimental amd 6750xt
Disabling the upscaller fixed it. Both AMD FSR 3 and XeSS dont work.
Played around with the settings. FSR 3 does work, but only when I set the upscaling mode to "AMD Native AA". It was also the only mode that let me see what I was doing in the character creation menu.
Experimental - bleeding edge/AMD RX6500
Once in the main game, the graphics are, to say the least, "not so nice":
Broken textures everywhere. Proton Experimental bleeding edge. NV 3060Ti, Driver version 560.35.03/565.57.01.
Once in the main game, the graphics are, to say the least, "not so nice":
Broken textures everywhere. Proton Experimental bleeding edge. NV 3060Ti, Driver version 560.35.03/565.57.01.
Can confirm that I'm having the exact same issue on the same drivers with an RTX 3080.
Adding to the above images, these aren't texture problems they appear to be widespread vertex/geometry shading problems. For the near-terrain geometry turning the appropriate settings down to low gets the terrain to actually appear on Nvidia cards (565.57.01). The most notable difference between the settings that I could notice at least by eye was possible displacement mapping which may have been disabled on low settings. Other effects that cause heavy artifacting are fur shading, and animation breaking for any skeletal meshes they are attached to, which can lead to detached limbs and vertex explosions in the most extreme cases.
If there's anything you would like me to try to grab such as API traces please let me know.
Can confirm the same artifacting and performance issues on an RTX 3090.
Tried on Proton Experimental Bleeding Edge as well as GE 9-17
Adding to the above images, these aren't texture problems they appear to be widespread vertex/geometry shading problems. For the near-terrain geometry turning the appropriate settings down to low gets the terrain to actually appear on Nvidia cards (565.57.01). The most notable difference between the settings that I could notice at least by eye was possible displacement mapping which may have been disabled on low settings. Other effects that cause heavy artifacting are fur shading, and animation breaking for any skeletal meshes they are attached to, which can lead to detached limbs and vertex explosions in the most extreme cases.
Setting that option to down did fix the terrain artifacts.
Running into an issue where game the crashes and completely locks up my system. Running Arch 6.11.5-arch1-1, AMD RX6800XT, mesa 1:24.2.6-1, proton bleeding edge, and running the game in gamescope. The crashes seem to happen randomly, sometimes after 5 minutes, the longest being after 30 minutes. From the proton log I'm getting a VK_ERROR_DEVICE_LOST. I've removed vk_image_aspect warning lines from the log as it seemed to be generating them every frame. The original log was 500MB. steam-3065170.log
I also experienced really bad artifacting and performance issues with RX6500XT and Proton Experimental, GE 9-16, and GE 9-17 on Ubuntu 22.04
Running into an issue where game the crashes and completely locks up my system. Running Arch 6.11.5-arch1-1, AMD RX6800XT, mesa 1:24.2.6-1, proton bleeding edge, and running the game in gamescope. The crashes seem to happen randomly, sometimes after 5 minutes, the longest being after 30 minutes. From the proton log I'm getting a VK_ERROR_DEVICE_LOST. I've removed vk_image_aspect warning lines from the log as it seemed to be generating them every frame. The original log was 500MB. steam-3065170.log
I also had the beta completely crash my computer, below is a cut from my journal.
After some further testing I was also able to get a similar crash in another game (SCP:5K) using vkd3d. The only difference between the two is in SCP:5K the system would soft recover eventually.
Oct 31 22:14:23 doompc kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32796) Oct 31 22:14:23 doompc kernel: amdgpu 0000:03:00.0: amdgpu: in process MonsterHunterWi pid 14795 thread vkd3d_queue pid 14951) Oct 31 22:14:23 doompc kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000010000008000 from client 10 Oct 31 22:14:23 doompc kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00701430 Oct 31 22:14:23 doompc kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa) Oct 31 22:14:23 doompc kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 Oct 31 22:14:23 doompc kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Oct 31 22:14:23 doompc kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Oct 31 22:14:23 doompc kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Oct 31 22:14:23 doompc kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x0 Oct 31 22:14:33 doompc kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=16021259, emitted seq=16021261 Oct 31 22:14:33 doompc kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process MonsterHunterWi pid 14795 thread vkd3d_queue pid 14951 Oct 31 22:14:35 doompc kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE Oct 31 22:14:35 doompc kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] ERROR failed to unmap legacy queue Oct 31 22:14:36 doompc kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] ERROR failed to halt cp gfx Oct 31 22:14:36 doompc kwin_wayland[937]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug Oct 31 22:14:37 doompc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] ERROR Failed to initialize parser -125! Oct 31 22:14:37 doompc systemd-coredump[15213]: [🡕] Process 1050 (Xwayland) of user 1000 dumped core.
System Specs: OS: Arch Linux DE: KDE Plasma 6.2.2 (Wayland) KERNEL: 6.11.5-arch1-1 CPU: AMD Ryzen 7 7800X3D 8-Core GPU: AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 18.1.8, DRM 3.59, 6.11.5-arch1-1) GPU DRIVER: 4.6 Mesa 24.2.6-arch1.1 RAM: 32 GB
Apart from the FSR/XeSS black screen and the weird textures issues, I'm having lot of stuttering with some textures and, sometimes, that stutter completely freezes my entire system forcing me to reboot.
OS: Arch with KDE Wayland CPU: Ryzen 5 5600X GPU: Nvidia GTX 1070 Video driver version: 565.57.01-1 Kernel version: 6.11.5.arch1-1 Proton version: Experimental + bleeding-edge
The beta seems to kill AMD GPU after running pretty perfectly for several minutes:
Nov 01 16:52:04 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=163945, emitted seq=163947
Nov 01 16:52:04 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: Process information: process MonsterHunterWi pid 9151 thread vkd3d_queue pid 9334
Nov 01 16:52:04 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: GPU reset begin!
Nov 01 16:52:04 ifrit-hpc kernel: iommu ivhd1: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=0000:00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
Nov 01 16:52:05 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: Dumping IP State
Nov 01 16:52:05 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: Dumping IP State Completed
Nov 01 16:52:05 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: MODE1 reset
Nov 01 16:52:05 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: GPU mode1 reset
Nov 01 16:52:05 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: GPU smu mode1 reset
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: GPU reset succeeded, trying to resume
Nov 01 16:52:06 ifrit-hpc kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000800000).
Nov 01 16:52:06 ifrit-hpc kernel: [drm] VRAM is lost due to GPU reset!
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: PSP is resuming...
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: reserve 0xa00000 from 0x82fd000000 for PSP TMR
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: RAS: optional ras ta ucode is not available
Nov 01 16:47:42 ifrit-hpc kernel: Bluetooth: RFCOMM socket layer initialized
Nov 01 16:47:42 ifrit-hpc kernel: Bluetooth: RFCOMM ver 1.11
Nov 01 16:47:45 ifrit-hpc kernel: warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Nov 01 16:52:04 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=163945, emitted seq=163947
Nov 01 16:52:04 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: Process information: process MonsterHunterWi pid 9151 thread vkd3d_queue pid 9334
Nov 01 16:52:04 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: GPU reset begin!
Nov 01 16:52:04 ifrit-hpc kernel: iommu ivhd1: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=0000:00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
Nov 01 16:52:05 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: Dumping IP State
Nov 01 16:52:05 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: Dumping IP State Completed
Nov 01 16:52:05 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: MODE1 reset
Nov 01 16:52:05 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: GPU mode1 reset
Nov 01 16:52:05 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: GPU smu mode1 reset
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: GPU reset succeeded, trying to resume
Nov 01 16:52:06 ifrit-hpc kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000800000).
Nov 01 16:52:06 ifrit-hpc kernel: [drm] VRAM is lost due to GPU reset!
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: PSP is resuming...
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: reserve 0xa00000 from 0x82fd000000 for PSP TMR
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: RAS: optional ras ta ucode is not available
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: SMU is resuming...
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: smu driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw program = 0, version = 0x00413e00 (65.62.0)
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: SMU driver if version not matched
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: use vbios provided pptable
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: SMU is resumed successfully!
Nov 01 16:52:06 ifrit-hpc kernel: [drm] DMUB hardware initialized: version=0x02020020
Nov 01 16:52:06 ifrit-hpc kernel: [drm] kiq ring mec 2 pipe 1 q 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: recover vram bo from shadow start
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: recover vram bo from shadow done
Nov 01 16:52:06 ifrit-hpc kernel: amdgpu 0000:43:00.0: amdgpu: GPU reset(2) succeeded!
Nov 01 16:52:06 ifrit-hpc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 01 16:52:06 ifrit-hpc kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Arch Linux with 6.11.5-zen1-1-zen, PowerColor RX 6700 XT, KDE Plasma Wayland
I can confirm both @N4gtan and @Doomguy1364 Issue on my end, The game will sometimes start to stutter so much that it will freeze my computer. One thing I had notice that repeats is that before it freezes, my monitor goes completely black and then the pc freezes, audio keeps playing and I'm forced to hit reset button, no way to recover. (Could this be maybe a GPU leak issue)
OS: EndeavourOS DE: KDE Plasma 6.2.2 (Wayland) Kernel: 6.11.5-arch1-1 (64-bit) CPU: AMD Ryzen 5600 GPU: AMD RX6600 Proton version: Experimental and GE Proton 9-15
The most worrying part is the issue not being able to be properly fixed before the beta ends, hopefully capcom ends up extending the time period for it cuz even on the windows side it's rough.
Can confirm the terrain issues reported, even with all settings turned down to the absolute lowest. I agree that it appears to be an issue with terrain "chunks" having their vertices... misplaced. Gameplay objects - particles, characters, decorations, etc. - appear to be unaffected. Also, it might just be my system configuration specifically, but I'm not getting menu effects or certain dialogue.
OS: Mint 21.3 DE: Cinnaon 6.0.4 Kernel: 6.11.3-x64v3-xanmod2 CPU: AMD Ryzen 9 3900X GPU: NVIDIA RTX 3060 Ti (LHR) Proton: GE 9-18
Like with others, I had to use VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 to get the game passed the opening logos. Based on similar experiences I've had trying to get Monado working, I'm going to guess that this is a problem with NVIDIA either poorly implementing or outright not implementing features in their Linux drivers.
I managed to catch AMD GPU hang on Steam Deck:
[Nov 1 17:44] [drm] Fence fallback timer expired on ring comp_1.0.0
[Nov 1 18:03] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=180525, emitted seq=180527
[ +0.000580] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0
[ +0.000619] amdgpu 0000:04:00.0: amdgpu: GPU reset begin!
[ +0.093958] amdgpu 0000:04:00.0: amdgpu: MODE2 reset
[ +0.010152] amdgpu 0000:04:00.0: amdgpu: GPU reset succeeded, trying to resume
[ +0.000586] [drm] PCIE GART of 1024M enabled (table at 0x000000F43FC00000).
[ +0.000122] [drm] PSP is resuming...
[ +0.022186] [drm] reserve 0xa00000 from 0xf43e000000 for PSP TMR
[Nov 1 18:04] amdgpu 0000:04:00.0: amdgpu: SMU is resuming...
[ +0.000379] amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully!
[ +0.009927] [drm] DMUB hardware initialized: version=0x0300000A
[ +0.077513] [drm] Failed to add display topology, DTM TA is not initialized.
[ +0.014550] [drm] kiq ring mec 2 pipe 1 q 0
[ +0.002349] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[ +0.000441] [drm] JPEG decode initialized successfully.
[ +0.000010] amdgpu 0000:04:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ +0.000006] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ +0.000004] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ +0.000003] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ +0.000004] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ +0.000003] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ +0.000003] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ +0.000003] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ +0.000003] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ +0.000004] amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[ +0.000003] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[ +0.000003] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
[ +0.000004] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
[ +0.000003] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
[ +0.000003] amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
[ +0.003168] amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow start
[ +0.000007] amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow done
[ +0.000110] amdgpu 0000:04:00.0: amdgpu: GPU reset(1) succeeded!
[ +1.135149] input: Steam Deck as /devices/pci0000:00/0000:00:08.1/0000:04:00.4/usb3/3-3/3-3:1.2/0003:28DE:1205.0003/input/input25
Steam Deck LCD
For anyone trying to troubleshoot the terrain/vertex issue, the setting which seems to affect it is called "Surface Quality", and it appears ONLY when accessing graphics options via the main menu.
If you access the graphics settings menu while loaded into the world, this option will not appear.
@minecraft2048 The sdma0 ring hanging is most likely unrelated to the game, that issue should go away if you update to SteamOS 3.6.
(To be clear, this is a different issue compared to the other GPU hangs where for example "ring gfx_0.0.0" times out. These gfx ring timeouts might not be fixed in 3.6, but the SDMA timeout is.)
I get identical amdgpu crash (page fault in thread vkd3d_queue) as https://github.com/ValveSoftware/Proton/issues/8206#issuecomment-2451340128. Graphics freeze after a few minutes while changing settings in main menu. Sound was still playing normally (not frozen or looping).
I can recover the system using Alt-SysRq r e i to kill Xorg, but after such crash it's safer to reboot anyway.
OS: Fedora Linux 39 (Thirty Nine) KERNEL: 6.11.5-100.fc39.x86_64 CPU: Intel Core i5-8400 @ 2.80GHz GPU: AMD Radeon RX 6600 (radeonsi, navi23, LLVM 17.0.6, DRM 3.59, 6.11.5-100.fc39.x86_64) GPU DRIVER: 4.6 Mesa 23.3.6 RAM: 16 GB Proton Experimental Bleeding Edge (1730411043 experimental-bleeding-edge-9.0-131609-20241031-p824747-w9c0d54-df74b2c-vdd7ad6)
Update: setting all graphics settings to the absolute lowest possible, including 1280x720 resolution and 30fps cap, allowed me to play the game for 1hr+ before crashing.
Cannot change any settings in game due to menu looping, game isn't unresponsive but it shares the same issues as Dragons Dogma 2 does for me where I cannot use the options menu.
for me i don't have issues to go into the game but isn't working fsr3 and intel xess with my rx 6600 tested with proton-exp :/ if i put fsr3 or intel xess i gonna have black screen (seem it needs HAGS)
for me i don't have issues to go into the game but isn't working fsr3 and intel xess with my rx 6600 tested with proton-exp :/ if i put fsr3 or intel xess i gonna have black screen (seem it needs HAGS)
thats not only a linux things its happening to windows users also
