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.

[centuralcreations]

I am having trouble getting it working, I have a RTX 2060 TI, 16gb ram, i7 running on Mx Linux(Debian)

I can get it to the warning screen then it just crashes.. Ill try to figure out how to get the logs and more details

[frozen-sea]

Had no luck. The game crashed in less than 20 minutes when it launched.

Proton experimental gave this me. I tried 5 times:

I get the same most times with all of Proton 8, Experimental bleeding-edge, and GE 8-25. The crash isn't reliable though, the timing can change and sometimes it starts (about 20%). Weirdly it never allocates even close to 100% of VRAM. Anyway, I have 100% success rate when setting VKD3D_CONFIG=pipeline_library_app_cache

No issues to report once it's actually running.

Specs: CachyOS (Arch), KDE Plasma X11, 4070 Ti (driver 545.29.06)

[CHFernandes]

@frozen-sea I don't remember if I had tested this flag, but when I tried to run the game on Windows 11, it just kept crashing as well, switched to an AMD RX 6700 XT, initially I was just going to play on windows but I gave Linux a try and faced the same page fault issue that @zaps166 faced.

By sheer dumb luck it solved itself on Proton Experimental if I enabled vsync in game and disabled upscale. It stutters sometimes, but I'll gladly take it from the crash fest that was with Nvidia or crashing the game.

Launch Options:

PROTON_LOG=1 gamemoderun mangohud %command%

Didn't test any ray tracing though, was able to enter every single room in the castle in one go, something that was impossible before. Played on high settings was well and I'm able to get 60 fps. (Ultra is playable at around 42-47 but it stutters more)

This page fault error also appeared on F1 23 and the fix was the same, proton experimental + enable v-sync in game though on F1 it took a long while before it crashed because of it.

Funny story: I've bought the Nvidia GPU because I was sick and tired of the page faults errors in Baldurs, Hogwarts and F1. Switched for two months, everything became worse, switched back and everything works 🤷‍♂️ the universe sometimes has a sick sense of humor.

[jpVm5jYYRE1VIKL]

I solved Out of video memory error on NVIDIA (driver version 545.29.06) during startup following way :

deleted vkd3d-proton.cache (and vkd3d-proton.cache.write ) from Hogwarts Legacy/Phoenix/Binaries/Win64

and modified steam cmd line : VKD3D_SHADER_CACHE_PATH=0 %command%

Out of video memory error not appear anymore but nag long black screen at start before "preparing shaders" still irritate.

PS : look like problem with proton internal cache (ie DXBC/DXIL -> SPIR-V conversion caching). I think this issue have to be sent to vulkan developers

[zaps166]

I solved Out of video memory error on NVIDIA (driver version 545.29.06) during startup following way

I had occasional out of video memory errors on AMD Radeon when using VKD3D_SHADER_CACHE_PATH=0.

I enabled vsync in game and disabled upscale

I always use V-Sync and never use upscale (I just reduce the "resolution" a little) - I have occasional pagefaults on AMD anyway.

Ultra is playable at around 42-47 but it stutters more

I noticed if Hogwarts Legacy drops below 60 FPS on ultra it stutters also with FreeSync enabled (less than FreeSync disabled, but still stutters). It's smooth on Windows. My monitor range is 40-60 FPS.

[jpVm5jYYRE1VIKL]

I had occasional out of video memory errors on AMD Radeon when using VKD3D_SHADER_CACHE_PATH=0.

Sorry. I ma bit not get what relation your comment have to "out of video memory" issue on NVIDIA. On Nvidia this issue prevent booting of game completely until you change proton version. My workaround prevent constant changes of proton version.

[bluca]

With proton-experimental or proton-GE-8-27 the game fails to start and shows an error Failed to initialize DirectX 12. Graphics drivers may require an update, or graphic adapter may not be supported.

It launches with proton 8.0-4, however it takes 5 to 15 minutes to get past the initial black screen/epilepsy warning, every time. After that, it works well.

NVIDIA GTX 1060 6GB with 535.43.02 driver and kernel 6.5.13.

[Blisto91]

@bluca Hi there.
Could i get you to attach a log from Proton Experimental? If you run the game with PROTON_LOG=1 %command% as a launch option in Steam a log called steam-990080.log should appear in your users home folder.

[bluca]

Sure
steam-990080.log.gz

[alasky17]

@bluca Could you try a few things to try to narrow down the point of failure?

1. Does dx12 mode work on Proton 8.0-5rc? You can select that as a Beta option from the Proton 8 tool.
2. Could you try dropping in vkd3d-proton from 8.0-4 into Proton - Experimental?
   cp -rf ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib/wine/vkd3d-proton/* ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib/wine/vkd3d-proton/.
   cp -rf ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib64/wine/vkd3d-proton/* ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib64/wine/vkd3d-proton/.
   After you are done, you can delete the Proton - Experimental/files/lib64/wine/vkd3d-proton/ and Proton - Experimental/files/lib/wine/vkd3d-proton/ folders and "Verify integrity of files" on Proton - Experimental to get the original shipped versions.

[bluca]

1. No, same error, logs:
   steam-990080-8.0-5rc.log.gz

2. Yes it works, logs:
   steam-990080-copy.log.gz

[alasky17]

@bluca Thank you for the info! I'm assuming you aren't set up to build vkd3d-proton and run a bisect? Unfortunately we have been unable to repro, so that is the only way to try to figure out what is going wrong. If you are up for it, I went ahead and put the first build for a bisect here: https://www.codeweavers.com/xfer/alasky/hogwarts-legacy-bisect/ with lock code "hogwarts". To test, you can drop the tarball in ~/.steam/steam/compatibilitytools.d/. (you might need to create this folder) and reboot Steam. After that, the Proton version will show up in your drop-down menu and you can select it and see if this version succeeds or fails.

[bluca]

The linked version works. But I can bisect it myself - what's the version/sha that was included in 8.0-4?

[bluca]

nvm found it

[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.