Hellblade: Senua's Sacrifice (414340)

[lieff]

Distro: Ubuntu 18.04
GPU: GTX 980, Nvidia proprietary driver 390.48
Resolution: 2560x1440
RAM: 16GB
Proton 3.7-4 Beta

Played around hour, some audio stutter (not painful). Probably because of high resolution and max graphics settings. All other is fine.

[Cevantime]

Played today too (not the VR version).

Distro: Linux Mint 19
GPU: GTX 1060, Nvidia proprietary
Driver: 396.54
Resolution: 1920x1080
RAM: 16GB
Proton 3.7

Conclusions :

• Looks not as good as windows version : textures, water etc. (maybe it's normal)
• Lesser Performance comparing to windows (some FPS falls, not a big deal)
• Many sounds problems and audio is a very important part of this game : noises, delay between mouth movement and speech (in cinematics), bad audio "mixing" (some sounds are too loud, some other too low, depending on where you look)

The game is playable as such but I won't call it perfect.

[DesNZ]

Also had a go today.

Distro: Kubuntu 18.04
GPU: GTX 1070, Nvidia proprietary
Driver: 396.54
Resolution: 1920x1080
RAM: 16GB
Proton 3.7-Beta

Conclusions :
Haven't played on windows yet, so no comparisons here. I did have the occasional fps freeze (drops to two fps for a second then a couple more stuttering) then goes back to normal).

Sound doesn't seem right, whispers are (although they're whispers) too quiet and some sounds (like the flags waving and water fall) appear to cut in at full volume then cut out instantly. It feels like there's supposed to be a gradual volume increase and subsequent decrease (Faudio maybe??).

As mentioned above there can be some decent delay with audio playback. It appears as though it isn't a delay over the entire play time, but with each sound 'bite'.

There also appears to be some popping with the ambient sound, not sharp or too high pitched so could be a part of the original game, just doesn't feel right.

Apart from the fps drops, the game ran at ultra settings with my 1070 at 1080p 60fps -5fps and plus around 10fps. I'd consider this fps very playable especially for a game like this.

Stable but not completely, playable.

[lieff]

Yes, seems I was too haste about audio.

[mysticfall]

I had a similar problem with crackling audio, but overriding xaudio_2_7 to native, builtin with winecfg fixed it for me.

[Cevantime]

@mysticfall Thanks. That fixed audio problems for me too. For guys wondering how to complete this magic, let me give some explanations :

• run winecfg with the right prefix :

     env WINEPREFIX="~/.steam/steam/steamapps/compatdata/[HELLBLADE_PREFIX]/pfx" WINEPATH="~/.steam/steam/steamapps/common/Proton 3.7/dist/bin/wine64" winecfg

  You may have to install your own wine to make winecfg available.
• Go to Library tab and in the first dropdown, select xaudio_2_7 and click on Add
• Relaunch the game
• Enjoy a now very playable game !

[DesNZ]

Very nice, thanks for the fix! Looking forward to Faudio being included, hopefully alleviating some issues like this in a much nicer way...

[kisak-valve]

Hellblade: Senua's Sacrifice Crashes When Starting New Game (414340)

Issue transferred from #1292.
@Simmonz posted on 2018-09-06T23:02:40:

I tried running Hellblade: Senua's Sacrifice through Proton and it launches fine but when starting a new game it crashes seconds later before getting to any intro cinematic, level, etc. The Steam AppID of the game: 414340. I added PROTON_LOG=1 %command% to the game's launch options but no log was generated. I haven't found an existing compatibility report for this game and I have checked whether there are updates for my system available.

System Information

• OS: Solus

• GPU: RX 580 8GB

• Driver/LLVM version: Mesa 18.1.6

• Kernel version: 4.18.5-90.current

• Proton version: 3.7-3

• https://gist.github.com/Simmonz/ee96fbeb3d32de20b2ebea979bf1746f

[jarrard]

To get audio working for my little issue(DRG), I had to install the whole xact via winetricks using the same method mentioned by Cevantime, but with winetricks xact instead.

Valve should probably consider xact as a default install ?

[lieff]

There already issue about this #54

[DePingus]

I also had to override xaudio2_7 to Native because the sound was clipping and the volume on the effects were way off. BUT that caused the game to crash after the opening cutscene or when loading my previous save game. To fix this crash I had to add the launch option:

PROTON_NO_ESYNC=1 %command%

After these two changes I was able to play for 45 minutes without issue. Though, my system couldn't handle max settings, even with Feral GameMode.

Fedora 28 / GTX 1060 6gb / NVIDIA 396.54 drivers / AMD FX-8320 8gb

[jarrard]

what does ulimit -aH say your open files limit is?

[DePingus]

@jarrard

core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 31624
max locked memory       (kbytes, -l) 16384
max memory size         (kbytes, -m) unlimited
open files                      (-n) 4096
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) unlimited
cpu time               (seconds, -t) unlimited
max user processes              (-u) 31624
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

Not sure if the soft limit matters. I'm running a fresh install of Fedora 28.

[user@pc ~] $ ulimit -Hn
4096
[user@pc ~] $ ulimit -Sn
1024

[jarrard]

Yep there is ya problem,

https://github.com/zfigura/wine/blob/esync/README.esync

Something that should be possibly fixed in protons documentation, its kinda critical for its function yet most people don't know about it (I didnt)

[DePingus]

@jarrard What should increase them to?

[jarrard]

I have all 3 files on my system mentioned in the esync readme so I just made the edit to all 3 of the files as suggested. (1048576 is what is suggested)

[DePingus]

@jarrard Excellent!

Here is the esync readme for future readers...
https://github.com/zfigura/wine/blob/esync/README.esync

I made the changes to the 3 files, restarted, then removed the PROTON_NO_ESYNC from my launch options. Now the game runs normally...actually even better. Thanks!

[lavadrop]

Installing xact doesn't fix anything regarding sound. I keep hearing a constant rythmic pulsating sound with distortions. During the intro, when there are more than 2 voices, all sorts of sounds start playing that make the voices incomprehensible and sound like wood crashing with rocks.

*** What actually works is overriding the xaudio_2_7 library ***

I don't understand why the suggestion to install xact; it doesn't do anything for Skyrim:SE or this game.

OS: Kubuntu 18.04.1
Kernel: 4.18.5-041805-generic
Resolution: 2560x1080
DE: KDE / WM: KWin
CPU: AMD Ryzen 5 1600 (12) @ 3.200GHz / GPU: AMD Radeon RX 580 8 Gb
System Memory: 1748MiB / 7970MiB
Proton 3.7.6 Beta

[DePingus]

@lavadrop You have to install xact and then open winecfg to create an override for xaudio2_7, set that to Native. Both @mysticfall and @Cevantime mentioned it in this thread.

[lavadrop]

Although they both mention the override, they never mention that you have to install xact and then do the override.

[Gravemind]

FWIW, I play with a custom wine build and custom wineprefix, and winetricks xact+native xaudio did not fix the audio for me either (actually it's worst), but installing prerequisites provided by Steam Hellblade fixed it:

export WINEPREFIX=...my/hellblade/wine/prefix...
cd ...my/steam/library.../steamapps/common/Hellblade/_CommonRedist
wine "vcredist/2012/vcredist_x86.exe" /quiet /norestart
wine "vcredist/2012/vcredist_x64.exe" /quiet /norestart
wine "vcredist/2013/vcredist_x86.exe" /quiet /norestart
wine "vcredist/2013/vcredist_x64.exe" /quiet /norestart
wine "vcredist/2015/vc_redist.x86.exe" /quiet /norestart
wine "vcredist/2015/vc_redist.x64.exe" /quiet /norestart
wine "DirectX/Jun2010/DXSETUP.exe" /silent

Then still adding xaudio2_7 as native, builtin (WINEDLLOVERRIDES="xaudio2_7=n,b"), and it's fixed, no more constant audio rhythmic crackling/fluttering.
I'm thinking winetricks' and steam's vcredist/directx installers might differs ?! ... or missed something...

(Found this by looking at appmanifest_414340.acf and its installscript.vdf. Someday could be automated...)

So @lavadrop, if you use a custom wineprefix, or not afraid of command-lines, this might help... or try to "verify integrity of game files" and/or somehow re-install the prerequisites from steam (still in addition to setup xaudio2_7 as native)...

EDIT: It seems winetricks xact does not install 64-bit dlls since winetricks 20180513 (Winetricks/winetricks@f2b3d26)

[lavadrop]

Yesterday I tested my theory with The Turing test: Valve includes libraries for unreal engine games. You just need to do the xaudio_2_7. It worked. No need to install xact.

[ibrokemypie]

even with xact installed and the override set to xaudio2_7, the mixing is terrible (six plays way too loud even on the minimum volume) and in cinematic the audio is out of sync from the video by a good 5 seconds or so. Playable, but annoying

[lavadrop]

I’ll have to revisit the game. Fortunately Ethan Lee now works with Codeweavers and should contribute to solving these kinds of audio issues.

[NTMan]

AMD GPU open source stack needs this patch https://gitlab.freedesktop.org/xorg/xserver/merge_requests/48 for working this game.

[ibrokemypie]

is there some problem with it on wayland? graphically it is fine on xorg for me on amdgpu

[NTMan]

is there some problem with it on wayland? graphically it is fine on xorg for me on amdgpu

On my Vega 56 and Vega 64 many Games under steam play stuck immediately after start no matter which gnome session was launched by X or Wayland.
This patch fixes this. For Wayland have another big benefit because make picture smoothness same as X session if enable Vsync in game. This make possible play in 4K in games such as Shadow of the Tomb Rider on Linux via steam play on my PC.

[sebastian-de]

For anyone with an AMD card, I can highly recommend to test ACO:
https://steamcommunity.com/app/221410/discussions/0/1640915206474070669/

Using ACO instead of LLVM fixes the stuttering and audio-sync issues on my end. Finally, Hellblade runs completely flawless on Linux for me (applies to the GOG version as well).

[puleglot]

WINEDLLOVERRIDES="xaudio2_7=n,b" have fixed audio in cutscenes for me (Proton 4.11.x)

[jeroenev]

I can't even get audio crackling to stop on Windows
weird you guys manage to fix it on Linux

[emmecii]

Problem: The game crashes with grahpic artifact seems due to resettting of the GPU.

During the crash i entered in a TTY to see dmesg with [drm:amdgpu_cs_ioctl [amdgpu]] ERROR Failed to initialited parser -125 in a great number of lines. Reserching this issue i found this bug with my same exactly issue stating about resetting of GPU with a certain kernel version here, resolved with a newer kernel version (actually not included on Ubuntu 18.04.4 HWE stack, 5.4 it's for now on 20.04 but for 18.04 users upgrade will be available withing a month) https://bugzilla.kernel.org/show_bug.cgi?id=205089

My hw:
Distro: Ubuntu 18.04.4 LTS with HWE
GPU: Radeon RX560
Driver/LLVM version: Mesa 19.2.8 (padoka PPA stable)/9.0.0
Kernel version: 5.3.0-61-generic
Proton version:5.0-9

[astatide]

I had similar threadripper issues (as reported by AwesamLinux) that seem 'fixed' when running in a VM without any NUMA topology.

Launching Hellblade resulted in a "Fatal error!" crash. I virtualized the install with qemu/kvm (using cpu model passthrough) and GPU passthrough using 42 pinned cores, but specifically did not give the VM a numa topology. Hellblade works as expected. Modifying the VM to passthrough a virtual NUMA topology results in Fatal Error appearing again.

Unlike AwesamLinux, I'm running 64 GB of quad channel memory out of the gate and still hit this problem. This suggests NUMA-related issues somehow. For now I'm just leaving the NUMA topology disabled. I suspect that disabling cores on the kernel launch options would workaround this problem but specifically disabling cores isn't a great solution (and I didn't try it anyway).

Distro: Arch Linux
CPU: TR 2970WX
GPU: Radeon VII
Driver/LLVM: Mesa 20.1.4-3
Kernel: 5.7.12
Proton: 5.09

[kapsh]

System Information

• GPU: RX 5700XT
• Driver/LLVM version: mesa 20.2.2, LLVM 11.0
• Kernel version: 5.9.10-zen1
• Link to full system information report: https://gist.github.com/kapsh/384d662389acc59d29095cbbfcb08588
• Proton versions: Proton 5.0.10 from Steam, Proton 5.9-GE-8-ST

steam-414340_proton-5.log
steam-414340_proton-ge.log

Symptoms

When starting new game, briefly shows splashscreen, then crashes to desktop.

[kisak-valve]

Hello @kapsh, your log indicates a video driver issue:
eGame\Binaries\Win64\HellbladeGame-Win64-Shipping.exe: ../mesa-20.2.2/src/compiler/nir/nir.h:2352: nir_instr_as_alu: Assertion `parent && parent->type == nir_instr_type_alu' failed. leading to wine: Assertion failed at address 00007F62D74FC945 (thread 0180), starting debugger... and Unhandled exception: assertion failed in 64-bit code (0x00007f62d74fc945).

[kapsh]

@kisak-valve oh, silly me. Gotta admit I only scanned log quickly and misread it as segfault in wine. Checked another time with mesa from git master (namely https://github.com/mesa3d/mesa/commit/b3504f41733a55c7680fbd2f6240df2c0e9f8c3d): it does run (at least 5 minutes after first cutscene).

[hakzsam]

Are you still experimenting issues with RADV?

[kapsh]

@hakzsam are you asking anyone in particular? Personally I can install and test in on available mesa 20.3.3 if you need status on current release.

[hakzsam]

Yes, anyone.

[AwesamLinux]

System Information

• GPU: RX 5700
• GPU Driver: Mesa 20.3.3 - kisak-mesa PPA
• Kernel version: 5.11.0-051100rc4-generic
• Distro version: Mint 20.1 (64bit) (Cinnamon)
• Proton version: 5.13-5

Retest Compatibility Report

The game still works for me with my current setup (with quad channel memory, did not try with dual channel). I did notice some blocky graphics (see the distant trees) at the intro of the game in all proton versions I tried

This is probably completely normal just that I haven't noticed it ever before, mentioning it just in case and including a screenshot of the settings used:

Logs:
steam-414340-experimental-5.13-20210126.log
steam-414340-proton-3.16-9.log.tar.gz
steam-414340-proton-5.13-5.log
system_info.txt

[kisak-valve]

"Hellblade Senua's Sacrifice" stopped to work after 2021 Update

Issue transferred from #5356.
@spagoc posted on 2021-11-28T11:21:03:

On my PC, after the 2021 November update, "Hellblade Senua's Sacrifice" stopped to work giving the following error:

DX12 is not supported on your system. Try running without the -dx12 or -d3d12 command line argument.

I don't know if there is a workaround to solve the problem.
My conf:
Ryzen 3600, Nvidia 2060 Super GPU with v. 470.82.00 driver
Proton 6.3-8 and Proton Experimental
Ubuntu 21.10 with X11

[spagoc]

The game works again with "-d3d11" as start option.
It appears that the two patches of 2021 (November and 7th December) have ported the game to DirectX 12 API in a way that is not yet compatible with Proton.

[AwesamLinux]

System Information

• GPU: RX 5700
• GPU Driver: Mesa 21.3.1 - kisak-mesa PPA
• Kernel version: 5.13.0-22-generic
• Distro version: Mint 20.1 (64bit) (Cinnamon)
• Proton version: 6.3-8

App ID: 414340
Build ID: 7800612

Game with the most recent update is working on my setup with DX12

As for the blocky graphics issue that I previously pointed out, I have checked occured on different system on Windows too (you just have to pay close attention to spot it). So that was not a Proton/driver issue.

[MrRobbin]

System Information:

• GPU: AMD Radeon RX 6900 XT
• GPU Driver: AMDVLK
• Kernel version: 6.6.0
• Distro version: Ubuntu 22.04
• Proton version : Proton Experimental

Hi , this Game observed crash or hang in Proton Experimental, while works well under Proton 8.0-4.
And the rendered scene looks very slowly on Radv under Proton experimental, while looks better under Proton 8.0-4.

Could anyone have a look ? : )

Thanks

There attached the crash and hang info.

Crash Info:

Hang Info:

[166713.308969] amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:88 vmid:4 pasid:32781, for process HellbladeGame-W pid 2538499 thread HellbladeGame-W pid 2538499)
[166713.308978] amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[166713.308982] amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x004012B0
[166713.308985] amdgpu 0000:09:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (inst) (0x9)
[166713.308987] amdgpu 0000:09:00.0: amdgpu:     MORE_FAULTS: 0x0
[166713.308990] amdgpu 0000:09:00.0: amdgpu:     WALKER_ERROR: 0x0
[166713.308992] amdgpu 0000:09:00.0: amdgpu:     PERMISSION_FAULTS: 0xb
[166713.308994] amdgpu 0000:09:00.0: amdgpu:     MAPPING_ERROR: 0x0
[166713.308996] amdgpu 0000:09:00.0: amdgpu:     RW: 0x0
[166713.309118] amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:88 vmid:4 pasid:32781, for process HellbladeGame-W pid 2538499 thread HellbladeGame-W pid 2538499)
[166713.309123] amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[166713.309126] amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x004012B0
[166713.309128] amdgpu 0000:09:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (inst) (0x9)
[166713.309131] amdgpu 0000:09:00.0: amdgpu:     MORE_FAULTS: 0x0
[166713.309133] amdgpu 0000:09:00.0: amdgpu:     WALKER_ERROR: 0x0
[166713.309135] amdgpu 0000:09:00.0: amdgpu:     PERMISSION_FAULTS: 0xb
[166713.309137] amdgpu 0000:09:00.0: amdgpu:     MAPPING_ERROR: 0x0
[166713.309139] amdgpu 0000:09:00.0: amdgpu:     RW: 0x0
[166713.309152] amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:88 vmid:4 pasid:32781, for process HellbladeGame-W pid 2538499 thread HellbladeGame-W pid 2538499)
[166713.309156] amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[166713.309159] amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x004012B1
[166713.309161] amdgpu 0000:09:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (inst) (0x9)
[166713.309163] amdgpu 0000:09:00.0: amdgpu:     MORE_FAULTS: 0x1
[166713.309165] amdgpu 0000:09:00.0: amdgpu:     WALKER_ERROR: 0x0
[166713.309167] amdgpu 0000:09:00.0: amdgpu:     PERMISSION_FAULTS: 0xb
[166713.309169] amdgpu 0000:09:00.0: amdgpu:     MAPPING_ERROR: 0x0
[166713.309171] amdgpu 0000:09:00.0: amdgpu:     RW: 0x0
[166713.309177] amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:88 vmid:4 pasid:32781, for process HellbladeGame-W pid 2538499 thread HellbladeGame-W pid 2538499)
[166713.309180] amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[166713.309182] amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x004012B0
[166713.309184] amdgpu 0000:09:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (inst) (0x9)
[166713.309187] amdgpu 0000:09:00.0: amdgpu:     MORE_FAULTS: 0x0
[166713.309189] amdgpu 0000:09:00.0: amdgpu:     WALKER_ERROR: 0x0
[166713.309191] amdgpu 0000:09:00.0: amdgpu:     PERMISSION_FAULTS: 0xb
[166713.309193] amdgpu 0000:09:00.0: amdgpu:     MAPPING_ERROR: 0x0
[166713.309195] amdgpu 0000:09:00.0: amdgpu:     RW: 0x0
[166713.309200] amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:88 vmid:4 pasid:32781, for process HellbladeGame-W pid 2538499 thread HellbladeGame-W pid 2538499)
[166713.309204] amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[166713.309206] amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x004012B1
[166713.309208] amdgpu 0000:09:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (inst) (0x9)
[166713.309210] amdgpu 0000:09:00.0: amdgpu:     MORE_FAULTS: 0x1
[166713.309212] amdgpu 0000:09:00.0: amdgpu:     WALKER_ERROR: 0x0
[166713.309214] amdgpu 0000:09:00.0: amdgpu:     PERMISSION_FAULTS: 0xb
[166713.309216] amdgpu 0000:09:00.0: amdgpu:     MAPPING_ERROR: 0x0
[166713.309218] amdgpu 0000:09:00.0: amdgpu:     RW: 0x0
[166713.309224] amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:88 vmid:4 pasid:32781, for process HellbladeGame-W pid 2538499 thread HellbladeGame-W pid 2538499)
[166713.309227] amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[166713.309230] amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x004012B1
[166713.309232] amdgpu 0000:09:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (inst) (0x9)
[166713.309234] amdgpu 0000:09:00.0: amdgpu:     MORE_FAULTS: 0x1
[166713.309236] amdgpu 0000:09:00.0: amdgpu:     WALKER_ERROR: 0x0
[166713.309238] amdgpu 0000:09:00.0: amdgpu:     PERMISSION_FAULTS: 0xb
[166713.309240] amdgpu 0000:09:00.0: amdgpu:     MAPPING_ERROR: 0x0
[166713.309242] amdgpu 0000:09:00.0: amdgpu:     RW: 0x0
[166713.309247] amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:88 vmid:4 pasid:32781, for process HellbladeGame-W pid 2538499 thread HellbladeGame-W pid 2538499)
[166713.309251] amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[166713.309253] amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x004012B1
[166713.309255] amdgpu 0000:09:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (inst) (0x9)
[166713.309257] amdgpu 0000:09:00.0: amdgpu:     MORE_FAULTS: 0x1
[166713.309259] amdgpu 0000:09:00.0: amdgpu:     WALKER_ERROR: 0x0
[166713.309261] amdgpu 0000:09:00.0: amdgpu:     PERMISSION_FAULTS: 0xb
[166713.309263] amdgpu 0000:09:00.0: amdgpu:     MAPPING_ERROR: 0x0
[166713.309265] amdgpu 0000:09:00.0: amdgpu:     RW: 0x0
[166713.309270] amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:88 vmid:4 pasid:32781, for process HellbladeGame-W pid 2538499 thread HellbladeGame-W pid 2538499)
[166713.309274] amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[166713.309276] amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x004012B1
[166713.309278] amdgpu 0000:09:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (inst) (0x9)
[166713.309280] amdgpu 0000:09:00.0: amdgpu:     MORE_FAULTS: 0x1
[166713.309282] amdgpu 0000:09:00.0: amdgpu:     WALKER_ERROR: 0x0
[166713.309284] amdgpu 0000:09:00.0: amdgpu:     PERMISSION_FAULTS: 0xb
[166713.309286] amdgpu 0000:09:00.0: amdgpu:     MAPPING_ERROR: 0x0
[166713.309289] amdgpu 0000:09:00.0: amdgpu:     RW: 0x0
[166713.309294] amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:88 vmid:4 pasid:32781, for process HellbladeGame-W pid 2538499 thread HellbladeGame-W pid 2538499)
[166713.309297] amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[166713.309300] amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x004012B1
[166713.309302] amdgpu 0000:09:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (inst) (0x9)
[166713.309304] amdgpu 0000:09:00.0: amdgpu:     MORE_FAULTS: 0x1
[166713.309306] amdgpu 0000:09:00.0: amdgpu:     WALKER_ERROR: 0x0
[166713.309308] amdgpu 0000:09:00.0: amdgpu:     PERMISSION_FAULTS: 0xb
[166713.309310] amdgpu 0000:09:00.0: amdgpu:     MAPPING_ERROR: 0x0
[166713.309312] amdgpu 0000:09:00.0: amdgpu:     RW: 0x0
[166713.309318] amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:88 vmid:4 pasid:32781, for process HellbladeGame-W pid 2538499 thread HellbladeGame-W pid 2538499)
[166713.309321] amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
[166713.309323] amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x004012B1
[166713.309325] amdgpu 0000:09:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (inst) (0x9)
[166713.309328] amdgpu 0000:09:00.0: amdgpu:     MORE_FAULTS: 0x1
[166713.309330] amdgpu 0000:09:00.0: amdgpu:     WALKER_ERROR: 0x0
[166713.309332] amdgpu 0000:09:00.0: amdgpu:     PERMISSION_FAULTS: 0xb
[166713.309334] amdgpu 0000:09:00.0: amdgpu:     MAPPING_ERROR: 0x0
[166713.309336] amdgpu 0000:09:00.0: amdgpu:     RW: 0x0

[Blisto91]

@MrRobbin Hi there.
Experimental have enabled the support for Ray Tracing out of the box so i assume radv is slow there because the game turns it on in the options. As for the crash or hang when using amdvlk if the same doesn't happen with radv then it is probably better to report at the amdvlk tracker.

[kisak-valve]

[Regression] Hellblade Senoa's sacrifice (414340)

Issue transferred from #7488.
@HarissaHero posted on 2024-02-09T19:12:42:

Compatibility Report

• Name of the game with compatibility issues: Hellblade Senoa's sacrifice
• Steam AppID of the game: 414340

System Information

• GPU: RX 650 XT
• Video driver version: Mesa 23.2.0-devel
• Kernel version: Ubuntu 23.10
• Proton version: 8.0-5 and Experimental

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

Crash on startup with error

Works fine with Proton 7, according to other's tests seems to work with proton 8.0-4

Reproduction

Run the game with compatibility

[kisak-valve]

Hello @HarissaHero, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

[HarissaHero]

Hi @kisak-valve, sure here are the files:
Steam Runtime Diagnostics
steam-414340.log

[kisak-valve]

Thanks, the extended diagnostics tells us that you're using mesa/RADV 23.2.1 (https://gist.github.com/HarissaHero/9d0879618d4b6f3a1fdfcf57baaf9f84#file-gistfile1-txt-L310) and warn:seh:handle_syscall_fault backtrace: --- Exception 0xc0000005 at 0x7ff9a08c3d34: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/vulkan/08/libvulkan_radeon.so + 0x2c3d34. hints that there was an access violation (c0000005) in the video driver.

Mesa 23.2.1 was the first point release that enabled raytracing by default with RADV. I'd test how the game behaves with a newer build of mesa from a PPA like oibaf or kisak-mesa, but I'm also seeing there's mesa installed in /opt/amdgpu (https://gist.github.com/HarissaHero/9d0879618d4b6f3a1fdfcf57baaf9f84#file-gistfile1-txt-L998) and we've seen driver dependency problems between stuff in /opt and PPAs so some extra care is needed there.