search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.49k stars 1.07k forks source link

Hellblade: Senua's Sacrifice (414340) #943

Open lieff opened 6 years ago

lieff commented 6 years ago

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.

astatide commented 4 years ago

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 commented 3 years ago

System Information

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

Symptoms

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

kisak-valve commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

Are you still experimenting issues with RADV?

kapsh commented 3 years ago

@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 commented 3 years ago

Yes, anyone.

AwesamLinux commented 3 years ago

System Information

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 screenshot3

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: settings

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 commented 2 years ago

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

Issue transferred from https://github.com/ValveSoftware/Proton/issues/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 commented 2 years ago

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 commented 2 years ago

System Information

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 commented 10 months ago

System Information:

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:

image

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 commented 10 months ago

@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 commented 9 months ago

[Regression] Hellblade Senoa's sacrifice (414340)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7488. @HarissaHero posted on 2024-02-09T19:12:42:

Compatibility Report

System Information

I confirm:

Symptoms

Crash on startup with error image

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 commented 9 months ago

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.

lyingpasta commented 9 months ago

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

kisak-valve commented 9 months ago

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.