Horizon Zero Dawn (1151640)

[NamoDev]

Compatibility Report

• Name of the game with compatibility issues: Horizon Zero Dawn
• Steam AppID of the game: 1151640

System Information

• GPU: GTX 1080 Ti
• Driver/LLVM version: nvidia 440.100
• Kernel version: 5.7.6
• Link to full system information report as Gist
• Proton version: 5.0.10-RC4

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.

Note: current NVIDIA driver is the latest version available in RPMFusion for Fedora 32

Symptoms

Game doesn't start - a dialog pops up saying "Unfortunately the game crashed" without providing any error details.

Reproduction

Just start the game through Steam.
steam-1151640.log

[olav-valle]

Same issue here. Identical error box, and nothing else.

System Information

• GPU: GeForce GTX 1080 Ti
• Driver/LLVM version: NVIDIA 440.95.01
• Kernel version: 5.4.0-7634-generic
• Link to full system information report as Gist:
• Proton version: 5.0-9

A comment further down noticed that the logs are different if you click "yes" or "no" to sending a report.
Here are logs for both cases:

Log when clicking "no" to sending crash report:
steam-1151640-no_crash_report.log

Log when clicking "yes" to sending crash report:
steam-1151640-yes_crash_report.log

Edit: Out of curiosity I tried with the newest GloriousEggroll/proton-ge-custom release, with seemingly same result.
Log here, in case it helps anyone: proton_5.9-GE-5-ST_steam-1151640.log

[NTMan]

Same issue here. Identical error box, and nothing else.
steam-1151640.log
Steam Sys-info

[korodarn]

Looking at the logs from everyone, looks like this is common point where error occurs.

warn:debugstr:OutputDebugStringA "An unknown unhandled exception (C06D007Eh) has occurred in thread 'Main' (0) at instruction location 000000007B00FC3Eh\n\nCall stack:\nBase address: 0x000140000000\n 0. 0x00007BCDAC6C RtlVirtualUnwind\n 1. 0x00007BCDAF82 RtlVirtualUnwind\n 2. 0x00007BCDB2FE NtRaiseException\n 3"

I"m having same issue, the same line was also in my proton log, along with the error cpu_context_win.cc:144] non-x64 context

[abhishek-rawal]

Same issue as mentioned by other users. However, I am still updating my results, incase it helps further to find the root cause.

System Info
steam-1151640_GE_5.9-5_ST.log
steam-1151640_Proton509.log
steam-1151640_Proton509_next.log

[fsyy]

same here
System Info

[Cxpher]

Same issue here.

[liberodark]

same here

[CuteSC2]

I think, "error cpu_context_win.cc:144] non-x64 context" is the crash-reporter crashing and not hzd.
When you click on no when being asked to send the error report, you get a much different proton log.
Then warn:debugstr:OutputDebugStringA "Initializing DLMalloc Heap\n" maybe looks like the evil witch, that caused all of this.
steam-1151640.log

[NextGenRyo]

It's also dx12 only. That might not help a lot either.

[77boaz]

I'm getting the same pop-up.. I tried multiple versions of proton including proton-ge and proton-tkg..

[wannfq]

I'm having the same issue

[ghost]

Then warn:debugstr:OutputDebugStringA "Initializing DLMalloc Heap\n" maybe looks like the evil witch, that caused all of this.
steam-1151640.log

It isn't. These logs have a lot of info and possibly not enough.

Point in fact you can look at

fixme:msvcrt:MSVCRT__stdio_common_vsnwprintf_s options 24 not handled
warn:debugstr:OutputDebugStringA "Initializing DLMalloc Heap\n"

and think that could cause a failure. But, it is highly likely a red herring.

Also, stuff like "execute_cfa_instructions", "raise_exception", "dump_unwind_info" can all be present in a working game. Logs can also present other challenges with log entries appearing at different places.

There's also fixme and warnings appearing for dx12 but that may or may not mean anything important as well.

fixme:d3d12_device_caps_init_feature_options1: TotalLaneCount = 3840, may be inaccurate.
fixme:dxgi:dxgi_adapter_QueryVideoMemoryInfo Returning fake video memory info.
fixme:dxgi:dxgi_adapter_SetVideoMemoryReservation iface 0xd97f40, node_index 0, segment_group 0, reservation 0x180000000 stub!
warn:d3d12_device_CheckFeatureSupport: Shader cache features not supported.fixme:d3d12_device_CheckFeatureSupport: Unhandled format 0x55.
fixme:d3d12_device_CheckFeatureSupport: Unhandled format 0x56.
fixme:d3d12_device_CheckFeatureSupport: Unhandled format 0x73.

Its possible this one may take months or more to solve. Just depends on the problems and how many.

[karzinogen]

Same issue here. Identical error box.
steam-1151640.log
steam-sysinfo.txt

[korodarn]

I added some additional debug channels for this log that will hopefully be helpful.

steam-1151640.zip
sysinfo.txt

[ghost]

I added some additional debug channels for this log that will hopefully be helpful.

steam-1151640.zip
sysinfo.txt

That does help a bit. The logs previously I don't think any other logs here show the dialog - the issuer's doesn't and I checked one other making two before this large one you provided.

You get that crash dialog box within [edit: 3k] lines [probably ~2.7 or 2.8k] of the dx12 info I posted above notably

"warn:d3d12_device_CheckFeatureSupport: Shader cache features not supported"
fixme:d3d12_device_CheckFeatureSupport: Unhandled format 0x56

Since its mostly garbage in between, its probable that its happening at the dx12 stuff or before (I haven't looked into it yet any further).

The error dialog.

0150:Ret  PE DLL (proc=0x11007bb8,module=0x11000000 L"amd_ags_x64.dll",reason=THREAD_ATTACH,res=(nil)) retval=1
0150:Starting thread proc 0x140375730 (arg=0x4fc5500)
0150:Call user32.MessageBoxW(00000000,141b588b0 L"Unfortunately the game has crashed.\nDo you want to help us fix the issue by sending a crash report?",141b59dc0 L"Error",00040014) ret=1403757c8

So it looks like much of the log is the end result of it crashing. I included the amd dll line in there just because its next to it and it may not mean anything.

[zagortenej]

I tried the game on Windows 10 too and it also won't run, displaying exactly the same dialog box.

However, before the "Unfortunately the game has crashed..." error, it displays different dialog box that says the game will only run with driver version 27. This is NVidia DirectX driver version and that version supports DirectX12 Ultimate, which I couldn't install on the computer I have running Windows 10 because... reasons...

So, I assume that the reason for this crash on Proton is essentially because there is no DirectX 12 Ultimate support either in Proton, or DX dlls being used in Proton prefix for this game, or because NVidia driver I have on Linux (440.100) does not provide features needed to implement/emulate DX12 Ultimate, or some other place (I'm not really familiar with all the Wine/Proton stack to be able to pinpoint this more precisely).

Just my 2 cents, thought it may help in some way.

[ghost]

So, I assume that the reason for this crash on Proton is essentially because there is no DirectX 12 Ultimate support either in Proton, or DX dlls being used in Proton prefix for this game, or because NVidia driver I have on Linux (440.100) does not provide features needed to implement/emulate DX12 Ultimate, or some other place (I'm not really familiar with all the Wine/Proton stack to be able to pinpoint this more precisely).

Its certainly possible. Though Death Stranding is I believe the only other game that is using this version of the Decima engine and dx12, and it has been working with the Proton next version, although that seems to be iffy and not without problems.

VKD3D is still a work-in-progress but they also note that 440.100 is one that works with dx12 and also a higher version driver may be needed. I'm not sure anyone has tested here with the Nvidia Vulkan developer beta driver as well.

But, it definitely looks possible that everyone may need to wait for VKD3D to improve and to have a driver that will work with it. Should find out in time.

[NextGenRyo]

it is most probably a dx12 issue, I get "fixme:d3d12_device_CheckFeatureSupport: Unhandled feature 0x13." before it crashes, in logs.

Looks like we have to wait for vkd3d to progress more.

[Danacus]

it is most probably a dx12 issue, I get "fixme:d3d12_device_CheckFeatureSupport: Unhandled feature 0x13." before it crashes, in logs.

Looks like we have to wait for vkd3d to progress more.

You can get rid of these error in a dirty way by adding some lines to vkd3d. It doesn't make a difference. Copying dxcompiler.dll from the tools directory to the executable's directory does make it show the loading screen, but it still crashes with the same message, so it's not really useful.

[Vbitz]

I noticed doing some debugging that the error message is from a generic exception handler. It doesn't indicate what's happening behind the scenes except that the game crashed.

[qsniyg]

As @Danacus says, the initial error is likely due to dxcompiler.dll being missing (from @korodarn's log - thank you!):

00bc:Call KERNEL32.LoadLibraryExA(141e94fc0 "dxcompiler.dll",00000000,00000000) ret=1416abd49
...
00bc:Ret  KERNEL32.LoadLibraryExA() retval=00000000 ret=1416abd49
00bc:Call KERNEL32.GetLastError() ret=1416abd57
00bc:Ret  KERNEL32.GetLastError() retval=0000007e ret=1416abd57
00bc:Call KERNEL32.RaiseException(c06d007e,00000000,00000001,0021e290) ret=1416abd9d

If someone who has copied dxcompiler.dll from the tools directory to the executable's directory (and got to the loading screen, as Danacus stated) could provide a WINEDEBUG=+relay,module,seh,timestamp log, it might help find a way around it :) (remember to compress it, otherwise it'll be pretty huge haha)

[korodarn]

I don't think it got to loading screen, but log does look a bit different so maybe it will be useful, maybe not.
steam-1151640_2.zip

[qsniyg]

@korodarn No idea if this will help or not, but try installing the native d3dcompiler_47 (protontricks 1151640 d3dcompiler_47):

73612.804:00bc:Call d3dcompiler_47.D3DCreateBlob(0000022c,0021e360) ret=1401f327e
73612.804:00bc:Ret  d3dcompiler_47.D3DCreateBlob() retval=00000000 ret=1401f327e
...
73612.804:00bc:trace:seh:raise_exception code=c0000005 flags=0 addr=0x1400f0787 ip=1400f0787 tid=00bc

[korodarn]

steam-1151640_1.zip
I copied the d3dcompiler_47 into the executable folder as well the run prior to the one I uploaded. I zipped it right before so it is here

*I know this might not do exactly the same thing as the install, since I didn't change the setting so I'm verifying if it used this file and will try re-running after.

[qsniyg]

I'm guessing this might be related to cause of the crash then:

warn:d3d12_swapchain_set_display_mode: Failed to find closest matching mode, hr 0x887a0001.
...
err:d3d12_swapchain_resize_target: Failed to set display mode, hr 0x887a0001.
...
73337.021:00bc:trace:seh:raise_exception code=c0000005 flags=0 addr=0x1400f0787 ip=1400f0787 tid=00bc

There are also a few warning messages above it, not sure if they're relevant:

d3d12 fixmes in log

fixme:d3d12_rtv_desc_create_rtv: NULL resource RTV not implemented.
fixme:d3d12_pipeline_library_LoadGraphicsPipeline: iface 000000000086E0F0, name "a7c87623f47cdb58f8e2d75445db3985", desc 000000000021E3E0, iid {765a30f3-f624-4c6f-a828-ace948622445}, pipeline_state 000000000021E3A0 stub!
fixme:d3d12_pipeline_library_StorePipeline: iface 000000000086E0F0, name "a7c87623f47cdb58f8e2d75445db3985", pipeline 00000000008EC1F0 stub!
fixme:d3d12_pipeline_library_LoadGraphicsPipeline: iface 000000000086E0F0, name "2537307d2151a4df271e4f83d59bb13a", desc 000000000021E7A0, iid {765a30f3-f624-4c6f-a828-ace948622445}, pipeline_state 000000000021E760 stub!
fixme:d3d12_pipeline_library_StorePipeline: iface 000000000086E0F0, name "2537307d2151a4df271e4f83d59bb13a", pipeline 00000000008ECC80 stub!
fixme:d3d12_pipeline_library_LoadGraphicsPipeline: iface 000000000086E0F0, name "21027ab47f814a59b74aac09a0de8a03", desc 000000000021E7A0, iid {765a30f3-f624-4c6f-a828-ace948622445}, pipeline_state 000000000021E760 stub!
fixme:d3d12_pipeline_library_StorePipeline: iface 000000000086E0F0, name "21027ab47f814a59b74aac09a0de8a03", pipeline 00000000008ED710 stub!
fixme:d3d12_pipeline_library_LoadGraphicsPipeline: iface 000000000086E0F0, name "27b94cf050813cc52a0b50f27d19c573", desc 000000000021E740, iid {765a30f3-f624-4c6f-a828-ace948622445}, pipeline_state 000000000021E700 stub!
fixme:d3d12_pipeline_library_StorePipeline: iface 000000000086E0F0, name "27b94cf050813cc52a0b50f27d19c573", pipeline 00000000008EE1A0 stub!

[fsyy]

Patch 1.01 is out, i didn't get to test it yet.

https://www.reddit.com/r/horizon/comments/i9jaa0/horizon_zero_dawn_complete_edition_for_pc_patch/

[intersectRaven]

Still crashes for me.

[ghost]

Suppose its worth nothing and giving intersectRaven a break for the low quality post as the patch includes "Some players are experiencing startup crashes. Patch 1.01 fixes a few, but not all, of these crashes."

That patch should only benefit you when you can run it.

But, it still may need Proton/Wine/VKD3D/etc fixes before this game even runs.

[neeasade]

Another datapoint, crashing within a min consistently on kernel 6.4.3, nvidia drivers 535.54.03, nvidia 4080, proton experimental

dmesg:

[   94.409640] NVRM: Xid (PCI:0000:01:00): 31, pid=4712, name=HorizonZeroDawn, Ch 0000001e, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0x0_00000000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ

edit: looks like my issue is this bug: https://forums.developer.nvidia.com/t/multiple-cuda-rtx-vulkan-application-crashing-with-xid-13-109-errors/235459?page=7 tracked upstream, no resolution yet (may not be present on 520.X drivers, but with a 4080 the earliest version I can use is 525.X

[Skiski]

I've upgraded to Fedora 38 with 535 drivers, but the game still freezes at the same point. It's not really a question of ingame time since I've left it idle for a few minutes (not in pause, just not touching the gamepad) and it crashed quickly after I started playing.

[jorgicio]

I'm using EndeavourOS and I own an RTX 3060. Latest drivers since 525 broke the compatibility with the game. Tried the 520 version, but it gave me some glitches like blue tone and black rendering. I had to downgrade to 515 version and using an LTS kernel to make it work and now it works flawlessly. It's sad to do that depending on what implies in the future using older drivers.

Just a question: The same issue happens when using the Flatpak version of Steam?

[ChaosBlades]

I'm using EndeavourOS and I own an RTX 3060. Latest drivers since 525 broke the compatibility with the game. Tried the 520 version, but it gave me some glitches like blue tone and black rendering. I had to downgrade to 515 version and using an LTS kernel to make it work and now it works flawlessly. It's sad to do that depending on what implies in the future using older drivers.

Just a question: The same issue happens when using the Flatpak version of Steam?

I highly doubt they will change.

Best advice is to trade/sell the card for AMD card. Seems almost every proton issue is an Nvidia driver issue anymore. Or it is a proton issue and gets fixed in a week or two😆.

[jorgicio]

I have the exact same problem on Fedora 36 with a RTX 3070 Ti with nvidia drivers 530.41.03-1. Here are my launch options: __GL_b5f2b3=0xFFFFFFFF ENABLE_VKBASALT=0 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 gamemoderun %command% The first one was suggested a few days ago in this thread but it did not change anything. I think it was working great with drivers 525 or 520 but the update broke the game and it has not been working since. Each time it freezes after a few minutes of game.

520, because the freezing issue starts with driver 525. I tested by myself several times from this version onwards.

btw, have you tried Nobara?

[tuxtergames]

Replying to #4125 (comment)

Testing since yesterday with Nobara 38, the same happen, playing for a few time the game freezes, after a few years playing on linux I start think to come back to windows, linux gaming sometimes is a headacke.

[AgostinoA]

Replying to #4125 (comment)

Testing since yesterday with Nobara 38, the same happen, playing for a few time the game freezes, after a few years playing on linux I start think to come back to windows, linux gaming sometimes is a headacke.

It's not Linux's fault, but the fault is that they do things ... badly,
between the launcher which seems to be starting a neural network training, each launch magically recompiles the Vulkan, 1000 times and Proton 8 which crashes like never before. Things done without standards without a certain criterion of order, without trial tests... Proton 8 is an absurd regression, I hope they fix it otherwise.
I recommend you do a test, not for NVDIA, AMD or other drivers.
Given the black magic of DVXK and Proton, try Steam with Heroic Launcher and launch the game with Wine 8.16 and the latest DVXK and NVAPI updates. Let me know how it goes because if it works better, I'll share a solution for everyone.
People have to download and play, not manage 1000 facts for example for a Steam Deck to try 10 versions of Proton to hope that the game starts. Steam Deck and PC must have the same solutions, one game works on one side, another doesn't and vice versa

[ArcAngelM666]

Just another Issue: are you aware of that since Kernel 6.5.x that slow motion "bug" is back?

Temporary workaround: Booting 6.4.x works
Using Debian 12 Testing (bookworm)
Neither latest Proton 8.0-3 nor GE-Proton8-16 are addressing this issue

Last time this issue occurred and was fixed was back in version https://github.com/ValveSoftware/Proton/releases/tag/proton-7.0-2

Fix Horizon Zero Dawn running in slowmotion.

[extract]

Another datapoint, crashing within a min consistently on kernel 6.4.3, nvidia drivers 535.54.03, nvidia 4080, proton experimental

dmesg:

[   94.409640] NVRM: Xid (PCI:0000:01:00): 31, pid=4712, name=HorizonZeroDawn, Ch 0000001e, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0x0_00000000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ

edit: looks like my issue is this bug: https://forums.developer.nvidia.com/t/multiple-cuda-rtx-vulkan-application-crashing-with-xid-13-109-errors/235459?page=7 tracked upstream, no resolution yet (may not be present on 520.X drivers, but with a 4080 the earliest version I can use is 525.X

Same issue that CP2077 has had for a while now.
Update from NVIDIA employee, so it seems they are working on it again.

amrits Moderator
https://forums.developer.nvidia.com/t/cyberpunk-2077-1-62-1-63-crashes/260799/29
We are seeing similar crash issue with another game Horizon Zero Dawn.
Team is actively working to root cause the issue.

[kerberizer]

amrits from Nvidia is asking:

Anyone knows the last passing driver where Horizon Zero Dawn did not freeze?

I already gave him some references from the discussion here (#4125 (comment) and #4125 (comment), to be precise), but since I do not own the game it would be great if somebody could double-check this.

[jorgicio]

Breaking news: Tried with recent versions of drivers, the latest 535 and the latest Vulkan beta. The issue still remains.

[jsgh]

amrits from Nvidia is asking:

Anyone knows the last passing driver where Horizon Zero Dawn did not freeze?

I know that it works with NVIDIA-Linux-x86_64-515.86.01.run but freezes with NVIDIA-Linux-x86_64-525.60.11.run (and both absolutely reliably so), both I believe from what is currently called the Production Branch (though I'm not so certain about that for 515...) Given their obtuse and non-public versioning convention along with a lack of a consistent changelog for any particular stream and an almost completely useless "historical version download" facility, I'm not sure how anyone could do better than to say what they just happen to have downloaded at the time and whether that works or not.

[tuxtergames]

I don't know why, but reading this messages, I've decided to test it again here, I was playing on windows, not finished the game yet, then copy my save to my Nobara 38, and for the miracle I'm playing since 6:30pm, now its 9:36pm and game its working, maybe could be a bug of the beginning of the map?
honestly I don't know how but its working, on Nvidia 535.104.05 with kernel 6.5.5-202.fsync.fc38.x86_64, its comming on nobara kde base, if anyone want to test, I can upload my save, I've cross the map and now playing deep secrets of the earth mission.

[jsgh]

Actually, given the source thread, I'll point this out here (I don't have an account on the nv forums): I've been playing CP2077 for about three weeks absolutely flawlessly, under NVIDIA-Linux-x86_64-535.113.01.run and an up to date kernel that can compile it. I got the 2.01 update about a week ago - I definitely noticed when the command tips started giving actual keyboard control tips and not xbox controller tips so I didn't have to pause and google the keyboard bindings every time I wanted to do something - and that also worked just fine. We're talking up to 10 hours playtime in a single session with no crashes.

Then on Sunday steam downloaded both some new CP2077 update (claims it was a shader update or something but steam is crap at changelogs too - I did notice the motorbike OSD visuals changed...) and a new Proton, and I started getting Xid 31 errors within seconds to about an hour of starting it. (Screen freezes, sound continues in a loop until the game is killed.) Eventually I found that switching to Proton 7.0-6 restored it to stability.

(So I'm not sure that the CP and HZD issues are quite the same: absolutely nothing I've tried gets HZD to be stable except for backing off to the earlier nv drivers. Not different proton versions, not different commandline options, not different nvidia-settings settings, not in-game settings. But CP was absolutely stable under newer drivers that stiff HZD, and only started doing that thing when, apparently, proton got updated without a change of nv driver, and now is stable again under an earlier proton version.)

[jsgh]

(Oh, also on the HZD front: I found that a brand new game absolutely reliably freezes during the intro FMV, where Aloy ventures into the field and gets shunned by the bigoted mother. Literally within the same 60 second span during that scene. But if you switch to a working driver version and start playing for a bit, then switch back to the buggy driver, you can usually play for quite some time - long enough to think you've solved it - but then anywhere from minutes to hours later it will freeze again.)

[kenthinson]

FYI in my testing Horizon Zero dawn in stable if you disable Nvidia DLSS in the game options menu. I have played for several hours without issue. If I turn DLSS back on it will run between a 1-5 minutes before crashing.

Proton: 8.0-4
NVIDIA Driver: 535.113.01
GPU: RTX 3090
CPU: Ryzen 5800X3D
Distro: Debian 12
Kernel: 6.1.0-13

[tuxtergames]

FYI in my testing Horizon Zero dawn in stable if you disable Nvidia DLSS in the game options menu. I have played for several hours without issue. If I turn DLSS back on it will run between a 1-5 minutes before crashing.

Proton: 8.0-4 NVIDIA Driver: 535.113.01 GPU: RTX 3090 CPU: Ryzen 5800X3D Distro: Debian 12 Kernel: 6.1.0-13

tomorow after a few hours playing game freezes again, today changing to the same proton stable as you working nice, I can play for almost 2 hours without freezing.

[kenthinson]

FYI in my testing Horizon Zero dawn in stable if you disable Nvidia DLSS in the game options menu. I have played for several hours without issue. If I turn DLSS back on it will run between a 1-5 minutes before crashing.
Proton: 8.0-4 NVIDIA Driver: 535.113.01 GPU: RTX 3090 CPU: Ryzen 5800X3D Distro: Debian 12 Kernel: 6.1.0-13

tomorow after a few hours playing game freezes again, today changing to the same proton stable as you working nice, I can play for almost 2 hours without freezing.

Glad to hear it worked for you as well. It took me several hours of trying different versions of proton / different game settings to isolate it down to the DLSS setting on my machine. If it's the problem for all of us Nvidia users then I hope that can save the proton devs time as they will know where to start looking for the problem in the code.

[kenthinson]

(Oh, also on the HZD front: I found that a brand new game absolutely reliably freezes during the intro FMV, where Aloy ventures into the field and gets shunned by the bigoted mother. Literally within the same 60 second span during that scene. But if you switch to a working driver version and start playing for a bit, then switch back to the buggy driver, you can usually play for quite some time - long enough to think you've solved it - but then anywhere from minutes to hours later it will freeze again.)

@jsgh Can you test with DLSS option turned off in the game settings and proton 8.0-4. It's the configuration that has worked for me. I believe that the DLSS option is what is causing the freezing but would like to double check with others that they experience the same results.

[ipkpjersi]

I had/have freezing without DLSS so it's not that.

[kenthinson]

I had/have freezing without DLSS so it's not that.

I would say we have multiple issues then not that mine is invalid.
Thanks for the information.

[jorgicio]

Breaking news:

I just updated the drivers to the 545 version, then I tried the benchmarking test inside the game and it didn't crash or freeze. It seems that the issue is fixed, at least for me, but when I play this game I'll get you more of my appreciations.

The result is the same as the 515 driver, but it freezes when using drivers between 525 and 535. So I think this is good news.

Benchmarking test is awesome btw.

EDIT: I played the game about an hour and it worked flawlessly. Zero freezes or crashes. Even with DLSS and high settings.
Also tried with kernels 6.1 LTS and 6.5.

[jsgh]

For reference, in HZD the DLSS setting is one of the options on the Settings>Display>Upscale Method option.

Running with:
Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
RTX 3060
kernel-6.4.15-100.fc37.x86_64
NVIDIA-Linux-x86_64-535.113.01.run
Proton 8.0-4

With Upscale Method set to Off, and selecting New Game, I get as far into the intro as the kid handing his berries to Mom before it freezes with:

[Wed Oct 18 02:03:41 2023] NVRM: Xid (PCI:0000:01:00): 31, pid=2993126, name=HorizonZeroDawn, Ch 00000086, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0x0_00000000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ
[Wed Oct 18 02:17:57 2023] NVRM: Xid (PCI:0000:01:00): 31, pid=2994229, name=HorizonZeroDawn, Ch 00000123, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0x71b0_00000000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ

(Two runs there, both froze within 10 seconds of the same point.)

So, apparently not DLSS related...

[kenthinson]

Replying to #4125 (comment)

Thanks for checking for me. It's a bummer it didn't work for you. I'm now 20 hours in without crashing 🤷‍♂️

[NXTler]

I get random system freezes and game crashes with all the logs ending in
warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
Any what this could be?

[UsernamesAreNotMyThing]

There's still some issues with this game on Steam Deck:

1. The game sometimes shows an assertion dialog when exiting, and it appears to have started with the 3.5 Steam Deck update:

Assertion failed!

Program: Z:\home\deck\.local\share\Steam
\steamapps\common\Horizon Zero Dawn
\HorizonZeroDawn.exe
File: ../src-wine/dlls/winevulkan/loader_thunks.c
Line: 5554

Expression: "!status && "vkQueueSubmit2""

Press OK to exit the program, or Cancel to start
the Wine debugger.

2. Audio sometimes glitches out after putting the unit to sleep, meaning it sounds badly distorted, and other people have mentioned this issue on ProtonDB.
3. Looking at ProtonDB, other people are also having issues with controller input not working after sleep, particularly the right stick, but I haven't seen this issue personally.
4. The game's benchmark incorrectly reports zero FPS.
5. I've ran into an issue a few times where the game behaves as if it's starting up way faster than normal, with the most noticable symptom being the text on the loading screen when loading a save being switched several times a second, and it ultimately seems to get stuck on that screen. I suspect this may be related to the old slowmo bug, but in reverse: it's going too fast.
6. The game seems to treat Steam Deck inputs as a Steam Controller rather than Xbox, which is apparent with button icons shown in-game and the controller shown in the game's controls settings.
7. I've ran into a missing texture bug with switching armor.

As far as I can tell, nobody else has mentioned any of these problems on this thread except # 4.

Log with the audio glitch; I don't have logs for any of the other issues at this time.

[lmm1191]

Not sure if anyone still having issues with this game. But, I got it working even with DLSS enabled using the latest Wine GE and Nvidia-DKMS driver on Arch linux. Played for 8 hours to test if it will still crash. No crashes but frequent frame drops even going to 20fps do happen. Not sure what's causing it though as it didn't happen when I played it on the same device before.

System Specs:

OS: Arch Linux
Processor: Intel i5 10th gen mobile
GPU: Nvidia RTX 3070 Mobile Max-Q
RAM: 32GB 3200 MHz
Device: Acer Predator Helios 300

[anark10n]

The issue persists with 550.67 driver, and just about every version of proton and proton ge i've attempted it with. If the game doesn't freeze, it will freeze the whole os along with scratchy audio sound (sometimes persistent, sometimes short) which i have to force shutdown with the power button.

OS: Arch Linux
CPU: Intel i7-6700
RAM: 16GB DDR4 2133 MHz
GPU: Nvidia RTX 3060

[ChaosBlades]

These Nvidia crashes/freezes should be discussed on the GeForce forums. It isn't a proton issue it is an Nvidia driver issue. You are not going to get any help here and I am pretty sure Nvidia does not read this thread.

I play this game all the time on both my 6900xt systems pop OS and chimera os. Not a single issue. Game runs flawlessly. Even HDR works.

[valpackett]

Here's a non-nvidia thing, currently on a game streaming cloud server with an AMD GPU, I'm hitting the exact same problem as reported on reddit: Horizon Zero Dawn freezes when exiting settings, never finishes loading when loading a save (and this discussion seems to be about a very similar issue on Windows).

When pressing Esc to quit the in-game settings, strace shows the process hanging on futex_waitv (or readv if FSYNC and ESYNC are disabled).

…now that I read the Steam thread a bit, this is interesting:

General thought: I am surprised an Athlon 3000G caused such problems, because I was able to get HZD to run on a simulated 2C/4T computer (I did this by taking an i3 10100 and artificially reducing the core count), but it would not work properly on a simulated 2C/2T computer.

The Linux Reddit thread also mentions an Athlon 200GE. And uhhhh the cloud instance I was testing on was also 2C/4T, so it must be that. Such a weird failure mode though, I wonder if anyone with more Windows/Wine skills would be interested in doing a bit deeper debugging.