Hogwarts Legacy (990080)

[kzdixon]

Compatibility Report

• Name of the game with compatibility issues: Hogwarts Legacy
• Steam AppID of the game: 990080

System Information

• GPU: RX 7900 XTX
• Driver/LLVM version: Mesa 22.3.4; LLVM 15.0.7 (also tested latest mesa 23.1-devel)
• Kernel version: 6.1.10-zen1
• Link to full system information report as Gist: https://gist.github.com/kzdixon/939144ca6c2c3a1928b90c38b0f05b59
• Proton version: Experimental (Bleeding Edge), GE-Proton7-49

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.

Proton Log (had to compress, took a bit to get it to crash but the incorrect shaders on close NPCs was consistently appearing the entire time):
steam-990080.log.zip

Symptoms

• Very often, characters will load in their shaders for clothes, etc., and when getting closer to the player will have them unload and become completely black. This typically persists forever unless a scene reloads, but there is another issue with loading scenes after seeing this occur...
• Loading scenes (especially so after seeing the black shaders) seems to oftentimes lead to a complete crash of the game. This means loading for a quest, fast travel, or going to the main menu to try and reload a save.

Reference Pictures:

Reproduction

Simply playing the game on a RX 7900 XTX with Proton using the latest stable driver release seems to result in this issue pretty regularly.

[rabidcopy]

Can't say I can reproduce the missing/black materials on my RX 570, though performance of the game does seem a bit rough. Long pauses/loading between pausing and unpausing the game. Game seems to want a lot of RAM and running without a swapfile is unadvised if you have only 16GB to work with. Used Proton 7.0-6.

[kzdixon]

Looks like RADV_DEBUG=nodcc,nohiz seems to be fixing the LOD/Shading issue so it might be another RDNA3 specific LOD issue like with Hi-Fi Rush... Will add it to my report on the mesa side.
Note: This doesn't fix the crashing when sometimes teleporting via fast travel.

[KawaiiDinosaur]

Using Proton Experimental

System: Arch (Kernel 6.1.9-arch1-2)
CPU: AMD Ryzen 7 3700X
GPU: AMD Radeon RX 6750 XT
DRIVER: Mesa 22.3.4
RAM: 16 GB

Looks and runs really well at Ultra Settings in 1440p+FSR2 Quality. The only issues I encountered are:

1. After around 2 to 3 hours of playing, the game will freeze and crash (memory leak?);
2. If you set the launch options RADV_PERFTEST=rt and VKD3D_CONFIG=dxr11 it freezes the game during the first load screen.

[Aztorius]

With an RX 6700 I do not have shaders issue. But yes, sometimes with scene loading or fast travel I have an instant crash. Restarting the game allows me to play past that loading screen but it will eventually crash a few scenes later.

[SeanMcnabb]

Played for a few hours, now the game won't launch at all and I am presented with an error box with a link to the following page: https://support.codefusion.technology/pp_inaa2nm/?e=88500006&l=english which I guess is probably broken DRM or something

[TsPG128]

I can confirm the crashes on my 1060 6gb, though no shader issues.

Looks to me like a memory leak...

• before it crashes (and the crashes occurred to me only while on the loading screens between scenes, though not every time), the quest scenes get very laggy.
• Starting the game after the crash the same scene gets repeated because the last save was before the scene, but then the frame rate is fine.
• Then it goes through the same loading screen that crashed before and passes it without crashes
• after a few scenes the same thing repeats, starting with the lag/very low framerate on a different scene

[Baysul]

I'm having issues where the game will crash during a loading screen on my 6700 XT.

[PedroHLC]

* before it crashes (and the crashes occurred to me only while on the loading screens between scenes, though not every time), the quest scenes get very laggy.

* Starting the game after the crash the same scene gets repeated because the last save was before the scene, but then the frame rate is fine.

* Then it goes through the same loading screen that crashed before and passes it without crashes

Same crash here, Proton Experimental (bleeding-edge) and Proton-GE 49. I get this in stderr when it crashes:

Win64\HogwartsLegacy.exe: ../src-wine/dlls/ntdll/unix/virtual.c:1481: create_view: Assertion `!((UINT_PTR)base & page_mask)' failed.

[nadrolinux]

I can confirm that game crashes a lot during fast travel/loading screens on my both PC. One with RX 5600 XT and second with RX 6600 XT.

[sorat0mo]

For me the game stays on the "Warning" screen indefinitely. And I suddenly discovered that my game runs fine when I did not focus the window at the game. (That means I have the game running in background, and it shows up just fine as I am typing this. Once I switched back, making it full screen, the game freezes again.

[Blisto91]

Hello.
Could any of you people with the crash issue try something to see if it helps?
In /proc/sys/vm/max_map_count up the default value to something like 1000000 and then try to play the game again.

To make it permanent across reboots you'll instead have to add vm.max_map_count = 1000000 to /etc/sysctl.conf
This change should kick in after a reboot or if you run sudo sysctl -p

You can read a short description of what it does here https://sysctl-explorer.net/vm/max_map_count/

Steam Deck already ship with a much higher value than default which might be why i haven't seen any report of this on Deck.

Edit: On newer versions of systemd a conf file might need to be created in a different location.
See #6510 (comment)

[TsPG128]

@Blisto91 thanks for the idea, i am trying it out now, changed it in proc, will keep you updated

[michael-hardeman]

I was able to play the game 1 time, but trying to launch it again leads to it crashing. The logs are quite strange... Proton Logs Here: https://filebin.net/96b7nxeu1hld0spc

The game seems to enter some kind of loop where it keeps printing:

01ec:warn:d3d12_pipeline_library_load_pipeline: Pipeline "2B1C3EF2891BAC37" does not exist.

then I think it tries to create a new pipline, then it complains that pipeline doesn't exist until it hits:

eventfd: Too many open files
x11drv: Can't allocate handle for display fd
365.751:0118:0210:warn:seh:OutputDebugStringA "Shutdown handler: cleanup.\n"

Hello. Could any of you people with the crash issue try something to see if it helps? In /proc/sys/vm/max_map_count up the default value to something like 1000000 and then try to play the game again.

To make it permanent across reboots you'll instead have to add vm.max_map_count = 1000000 to /etc/systctl.conf This change should kick in after a reboot or if you run sudo systctl -p

You can read a short description of what it does here https://sysctl-explorer.net/vm/max_map_count/

Steam Deck already ship with a much higher value than default which might be why i haven't seen any report of this on Deck

I did try this even though I didn't think it would help with my issue and yeah it didn't help.

Any ideas?

[Blisto91]

@MichaelAllenHardeman I have been told that might be an esync "issue" (maybe not a issue with esync itself per say, but can trigger it when a low fd limit is set).
You could try launching with PROTON_NO_ESYNC=1 %command% and see if that helps? CPU performance might decrease tho. People with kernel 5.16+ use fsync by default instead.

[michael-hardeman]

@Blisto91 game has successfully launched three times in a row with that option. Thanks 👍

[t-jonesy]

@Blisto91 I think the map count did the trick for the loading screen crashes. I've been able to fast travel to 6 different locations and it still hasn't crashed. My best before the change was 2. My max_map_count was only 65530 before the change

[kisak-valve]

Hello @MichaelAllenHardeman, please verify that ulimit -Hn gives you a high value and not 4096.

[KawaiiDinosaur]

Hello. Could any of you people with the crash issue try something to see if it helps? In /proc/sys/vm/max_map_count up the default value to something like 1000000 and then try to play the game again.

To make it permanent across reboots you'll instead have to add vm.max_map_count = 1000000 to /etc/sysctl.conf This change should kick in after a reboot or if you run sudo sysctl -p

You can read a short description of what it does here https://sysctl-explorer.net/vm/max_map_count/

Steam Deck already ship with a much higher value than default which might be why i haven't seen any report of this on Deck

On newer versions of systemd you need to create a .conf file inside /etc/sysctl.d/.
I created file named 99-max_map_count.conf with the parameter vm.max_map_count=1048576.

On the next boot, you can check the value of 1048576 with cat /proc/sys/vm/max_map_count.

[Blisto91]

Thanks. Edited my comment to link to yours

[n3wsw3]

Changing vm.max_map_count=1048576 seems to have fixed the crashes in my limited testing.

[michael-hardeman]

ulimit -Hn

$ ulimit -Hn
16384

[kisak-valve]

That's generally too low for eventfd-based thread synchronization to be reliable. The link I posted with the question recommends around a million, and systemd sets it to something like half a million.

[michael-hardeman]

@kisak-valve Is this better?

$ ulimit -Hn
1048576
$ ulimit -Sn
524288

[kisak-valve]

I recall there being downsides to increasing the soft limit, but not any specific details and the soft limit is not relevant to what esync is doing. Regardless, you should test the game without PROTON_NO_ESYNC and re-evaluate for yourself.

[nadrolinux]

@Blisto91 thanks for this tip. vm.max_map_count=1048576 solved issue with a crash during loading/fast travel on my both PC (Fedora 37 on both).

My OS limits looks following:
ulimit -Hn: 1048576
ulimit -Sn: 1024

[kzdixon]

Can report that vm.max_map_count=1048576 (thanks #6510 (comment) #6510 (comment)) seems to solve the scene-loading crashes. Been playing for several hours today with no issues.

$ ulimit -Hn
524288
$ ulimit -Sn
1024

[lfelipe]

steam-990080.log

Game crashes at startup right after the very first screen with "Warning: Read before playing". This is on kernel 6.2.0-060200rc4-generic with mesa 23.1.0-devel (git-3e2c768), running on Arc 770m.

[bluca]

The README said you could just rebuild the same builddir and it should work, but that is apparently not the case, and was causing that build problem. By blasting it away on each bisect step it fixes that.

And I found the problem - the first bad build is this commit which enables DXR by default: HansKristian-Work/vkd3d-proton@1a049c6

And sure enough, by setting VKD3D_CONFIG=nodxr the game launches just fine with the current Proton Experimental.

[kisak-valve]

Hello @bluca, NVIDIA 535.43.02 is relatively old and also marked beta in that release series. Are you able to test a newer driver version without treading into the Franken-Debian realm?

[runar-work]

I reproduced the out of memory errors on launch with GTX 1660 Ti and RTX 4070. It happened reliably on both if I deleted the shader cache between launches, though it would usually only happen for a single launch on the 4070, unlike the 1660 where it would continue until I deleted the vkd3d-proton.cache file as well.

I tested the 4070 with 535.43.22 (the Vulkan beta driver) and wasn't able to reproduce the errors with that, so hopefully that should work better.

[bluca]

Hello @bluca, NVIDIA 535.43.02 is relatively old and also marked beta in that release series. Are you able to test a newer driver version without treading into the Franken-Debian realm?

@kisak-valve @alasky17 I have installed the latest nvidia production branch release, 535.154.05, released two days ago, and it does not make a difference, still the same error.

[kisak-valve]

Hogwarts Legacy (990080): Crash on boot "Error of failed request: BadMatch (invalid parameter attributes)\

Issue transferred from #7421.
@MagiusCHE posted on 2024-01-18T20:29:33:

Compatibility Report

• Name of the game with compatibility issues: Hogwarts Legacy
• Steam AppID of the game: 990080

System Information

• GPU: NVIDIA GTX 4070 ti
• Video driver version: NVidia 545.29.6.0
• Kernel version: 6.7.0
• Link to full system information report as inxi.log:
• Proton version: 8.0-104

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.

proton.log

Symptoms

I just run the game with varius combination of ENV variables.
The problem is the same every time.
I got error just after 1 or 2 second after game start.

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  149 ()
  Minor opcode of failed request:  4
  Serial number of failed request:  636
  Current serial number in output stream:  647

I tried PROTON 8 and Experimental, even GE. Same error.

Reproduction

1. Run the game via commandline just using PROTON

PROTON_LOG=1 VKD3D_CONFIG=dxr PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_NO_ESYNC=1

2. Game crash on error as reported

[MagiusCHE]

An update... today i've managed to start the game without changes any paramters or variables.
The game starts without problem.
After initial wizard i've closed the game and....now...

It wont starts anymore!!!!!

I've tried a dozen times but nothing happend. Same error as before.

It is so strange...

[mbenkmann]

I have a weird reproducible crash of Hogwarts Legacy. In the error condition, a few seconds after starting the game, before even the Epilepsy Warning screen is shown, the game will open a small window titled "The Phoenix game has crashed and will close" with contents only the words "Fatal Error". Note that this is different from the message a lot of Windows users seem to encounter that contains more text and starts with "LowLevelFatalError".

Now for the weird part: If I start Steam from a terminal, then Hogwarts starts without issues. If I start Steam with the .desktop file that has Terminal=false from my desktop environment (which is Cinnamon), Hogwarts crashes with the above error. It's 100% reproducible.

It does not seem to be related to stdin/stdout/stderr. I can redirect all 3 from/to /dev/null when launching steam and the game will still work if steam is started from a terminal. It's also not necessary that the terminal window is still around, when the game is started. My current start script to work around this bug looks like this:

#!/bin/bash
set -m #enable job control in script
steam >/dev/null </dev/null 2>/dev/null &
disown
sleep 2

I launch this from the steam.desktop file with Terminal=true, so the terminal opens for 2 seconds and then closes.

Some theories on what could be responsible:

• Something to do with process groups/controlling terminal
• Some process settings/limits applied by PAM differently for a terminal session than for the main window manager session

The system is Ubuntu 22.04 with the Cinnamon desktop environment. I've tried both Proton 8.05 and Experimental. Same behavior.

[vallode]

RE: vm_max_map_count
Arch is increasing the default value to reduce crashes: https://archlinux.org/news/increasing-the-default-vmmax_map_count-value/ so this should no longer be required as a change on latest Arch releases.

[esullivan-nvidia]

@bluca Are you able to reproduce the initialization issue with the latest 550 production driver? Right now this would be 550.67.

[zaps166]

I've checked DualSense 5 game pad after game update on Windows - gamepad works very well there with haptics, rumble. On Proton it still doesn't have any haptics. Rumble works only when DS5 gamepad is detected as Xbox (sometimes after hot-plugging).

[phodina]

Compatibility Report

• Name of the game with compatibility issues: Hogwarts Legacy
• Steam AppID of the game: 990080

System Information

• GPU: NVIDIA Corporation GA106 [Geforce RTX 3050]
• Video driver version: nvidia 550.78.0.0
• Kernel version: 6.6.32
• Link to full system information report as Gist: https://gist.github.com/phodina/0ba43f42caa43147ab92879e72f89bcf
• Proton version: 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.

steam-990080.log

Hogwarts_Legacy.mp4

Symptoms

The game starts but the window does not display any graphical output. Sound can be heard.

Reproduction

Launch the game

[kisak-valve]

Hello @phodina, as a quick test, can you try an X based user session instead of a wayland based user session and see if the game's behavior changes?

The many lines of err:vkd3d-proton:dxgi_vk_swap_chain_recreate_swapchain_in_present_task: Failed to create swapchain, vr -3. in your Proton log hints that there's a broken render path in your video driver stack which is giving the game a hard time. If this was my system, I'd try to find a way to temporarily switch the egl render path (https://gist.github.com/phodina/0ba43f42caa43147ab92879e72f89bcf#file-hogwarts-legacy-system-information-L271-L280) from zink to NVIDIA proprietary to see if that's a contributing factor.

[phodina]

Hi @kisak-valve ,
yes so I switched to X based session instead of Wayland GNOME session. The window also provides no graphics just graphs the buffer for whole desktop. There's no sound and the dialog about wait/kill pops up. After several wait buttons press I killed the app and it completely crashed the session.

Same on the second attempt.

Here's the log.

steam-990080_first_attempt.log

steam-990080-second_attempt.log

I'll check the egl render path as you suggested.

[zaps166]

The game is still resetting the AMD GPU (sometimes without pagefault im dmesg, sometimes can soft-recover after few seconds of freeze):

[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=4033305, emitted seq=4033307
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HogwartsLegacy. pid 4394 thread vkd3d_queue pid 4537

or

amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:32780)
amdgpu 0000:03:00.0: amdgpu:  in process HogwartsLegacy. pid 9282 thread vkd3d_queue pid 9422
amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x00008000a0be5000 from client 0x1b (UTCL2)
amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501430
amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=4909244, emitted seq=4909246
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process HogwartsLegacy. pid 9282 thread vkd3d_queue pid 9422

or

amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32779)
amdgpu 0000:03:00.0: amdgpu:  in process HogwartsLegacy. pid 13107 thread vkd3d_queue pid 13247
amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080008ad6e000 from client 0x1b (UTCL2)
amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401430
amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: SQC (data) (0xa)
amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered

Mesa: 24.1.5 (compiled)
Kernel: 6.10.3 (Manjaro)

Any ideas?

[simifor]

@zaps166 I haven't been able to reproduce this with my card in the 2 hours I tried. How often would you say you encounter these crashes? Do you see it happen more often in specific areas or doing certain actions? What model is your card? I see that you've been affected for a few months at least, but would you say the crashes were always there for you or did they start at some point?

[zaps166]

@simifor

How often would you say you encounter these crashes?

For me it looks random - sometimes few hours no crash, sometimes few minutes, sometimes within 1-2 hours.

Never tried to play longer on Nvidia and/or Windows, so can't tell about them.

---

I use VKD3D_SHADER_CACHE_PATH=0.

It also doesn't depend when I use Ultra or High image quality, FreeSync doesn't matter, too. I have V-Sync always enabled, TAA without other upscaling. Image size (resolution) also doesn't matter. Motion blur, CA, Film Grain - disabled, FoV set to max. RT off.

---

What model is your card?

RX 6900 XT. It never happened in different games. Currently only in this game or my Vulkan applications when I do a mistake.

Do you see it happen more often in specific areas or doing certain actions?

I have to look more carefully when this happen again, but it's in various locations/actions - flying, walking, running, fighting...

I see that you've been affected for a few months at least, but would you say the crashes were always there for you or did they start at some point?

I play occasionally also other people sometimes play on my PC on their accounts - all have same issues in various locations in game. Also I see similar crashes from other people here - did it stopped crashing for them or they stopped reporting it? I see similar crashes since the first game release (so game update, kernel update, mesa update doesn't matter).

[simifor]

@zaps166 It's hard to say for certain what the cause might be, but one thing that comes to mind is this https://gitlab.freedesktop.org/drm/amd/-/issues/3131 if you use mangohud you can check your clockspeed to see if it might be clocking too high. If you limit the speed and stop seeing the crash, it would be worth sharing your experience in that thread.

[zaps166]

@simifor Recently (for few weeks) I already limited GPU clocks to 2 GHz and I see same crashes, but I have drastically lower power consumption and only little lower graphics settings. In the past I remember I used stock clocks without any manual adjustments - same crashes.

Next time when I'll play, I'll monitor all clocks, voltages, temperatures, etc.

Is it any (simple) way to debug it somehow?

[simifor]

@zaps166 well, at this point it's just a guess that the card might be clocking too high and leading to a gpu crash. If that's the case, the card should be clocking higher than the manufacturer advertised speed, so you can use something like mangohud to keep an eye on clockspeeds to make sure it's not actually going higher than your limits..

Now, to be fair, clocking higher than manufacturer speeds is actually expected, and this is something that happens on both windows and linux, but in some cases it seems that linux is clocking even higher than windows. IF the card is clocking higher than manufacturer speeds and crashing, it's a good idea to ensure that you can actually cap it to a lower point and see if crashes still happen to discard or confirm that this is the issue here.

[zaps166]

@simifor Yes, I already lowered clocks to 2 GHz (normally it boosts to ~2.5 GHz) and I had same crashes.

Today I haven't crashed yet, but in logs I have a lot of lines like this:

38643.969:0130:02d4:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 4096 < 65536 (dim 3, 256 x 256 x 1, 9 levels, 1 samples, fmt #53, flags #0).

[ThisNekoGuy]

Compatibility Report

• Name of the game with compatibility issues: Hogwarts Legacy
• Steam AppID of the game: 990080

System Information

• Distro: Gentoo Linux (LLVM18-based)
• CPU: AMD Ryzen 7 3700X 8-Core
• GPU: RX 7800 XT
• Video driver version: Mesa 24.2.2 (radeonsi, navi32, LLVM 18.1.8, DRM 3.57)
• RAM: 32 GB @ 3600 MHz
• Kernel version: 6.10.9-tkg-eevdf-gentoo-llvm18-generic_v3
• Link to full system information report: Gist
• Desktop Environment: KDE Plasma 6.1.4
• Display Session: Wayland
• Proton version: 9.0-3 experimental-bleeding-edge-9.0-121840-20240920-pc506af-w9d08b8-d43c276-v2ce6df

I confirm:

• that I have checked whether there are updates for my system available.

steam-990080.log

Symptoms

The game froze from what I presume must be a thread issue related to my usage of a PS4 controller (references to HID and controller are found in the log).

. . .

"../src-wine/dlls/xinput1_3/main.c: controllers[0].crit" wait timed out in thread 0134, blocked by 02fc, retrying (60 sec)
"../src-wine/dlls/winebus.sys/main.c: cs" wait timed out in thread 0080, blocked by 0070, retrying (60 sec)

. . .

Steam itself then becomes unresponsive, forcing me to close the game with ALT+F4 instead of the "stop game" button in the Steam client.

For additional context: my PS4 controller was low on battery at this time but had not disconnected from it quite yet; my desktop still reported it as connected, so I'm not quite sure what triggered this xinput error in Proton.

Screenshot:

(Ignore the faded color; I took this screenshot after KDE Plasma decided that the process was no longer responding when I used ALT+F4)

Reproduction

1. Advanced Launch Options: PROTON_LOG=1 DXVK_HUD=compiler PROTON_HIDE_NVIDIA_GPU=1 gamemoderun %command%
2. Use an (official) Sony PS4 controller via Bluetooth
3. Start the game (new game)
4. Progress past the initial prologue until you have access to walk around freely
5. Do the "Charm" class quest (This was the order I did it in but this might not be required)
6. Attempt to do the "Defense Against the Dark Arts" quest <- (Froze for me at the point)

[ThisNekoGuy]

Also, controller hotpluging seems to not work... For me, if the controller becomes disconnected during gameplay, attempting to reconnect it makes the game stop recognizing its inputs.

EDIT: Additionally, when launching the game, sometimes my inputs get changed via the Steam Input menu automatically; most frequently, the Left Bumper/L1 gets rebound to Left Trigger for some reason.

[zaps166]

Also, controller hotpluging seems to not work... For me, if the controller becomes disconnected during gameplay, attempting to reconnect it makes the game stop recognizing its inputs.

Whole below text is about DS5 gamepad.

I can confirm, but it depends on settings, etc. When Steam Input is enabled for this game, it can't detect after hot plugging. Otherwise it can detect again, but it can be detected as XBox or PlayStation (random which glyphs get).

When Steam Input is enabled:

• no hot plugging
• on Proton Experimental we have regular rumble and PlayStation glyphs
• on Proton 9 we have regular rumble and XBox glyphs

When Steam Input is disabled:

• hot plugging working, but poorly (see below text)
• no rumble
• gamepad connected via USB - no audio haptics in this game (on Windows it works correctly), game doesn't open any audio stream for gamepad

[ThisNekoGuy]

And sometimes it just hangs on a black screen upon launching the game with gamescope...
(Launched gamescope in a terminal, then added DISPLAY=:1 to the game's launch options)

I launched the game 3 times so far this afternoon and now I just can't seem to get past this. :/

EDIT: Wait, what? That's... odd. My proton version was changed to experimental for some reason. Rather, I guess I was using experimental the whole time and just thought I was until now?

[zaps166]

EDIT: Wait, what? That's... odd. My proton version was changed to experimental for some reason. Rather, I guess I was using experimental the whole time and just thought I was until now?

Experimental is used for this game by default (why?). You can change it in game properties by manually selecting different Proton version.

[kisak-valve]

Hello @zaps166, there is no "default" Proton version with the desktop Steam for Linux client. You can see what Proton version is used by a game and why by going to the Steam Library view, selecting the game, and then clicking the ⓘ button on the right side. At some point you selected a compatibility tool in Steam's global settings (Steam -> Settings -> Compatibility) and odds are that's where your preference is being set.

[ThisNekoGuy]

@kisak-valve I assure you that is not the case:

[zaps166]

@kisak-valve I can confirm with @ThisNekoGuy post.