Same here.

• GPU: AMD Radeon RX 6700XT
• Video driver version: Mesa 24.2.4
• Kernel version: 6.11.4
• Proton version: Proton experimental-9.0-20241022

same here .. tried with different versions of proton (proton-experimental, stable, proton-ge, .. ), result is always the same.

Someone on the Nixxes team gave me a workaround. Adding the -showlinkingqr launch option completely disables the PSN requirement.

I was able to connect to my PlayStation account just fine. I am using Proton Experimental.

Nvidia users at the very least probably prefer to use the -showlinkingqr method. Using SteamDeck=1 on Nvidia can trigger a bug (in the games Steam Deck mode) where the image will appear to be jittering/shaking slightly when using DLAA or DLSS.

Someone on the Nixxes team gave me a workaround. Adding the -showlinkingqr launch option completely disables the PSN requirement.

For me it still requests PSN acc.

How are you using it. If you have %command% in your launch options then you have to put it after e.g %command% -showlinkingqr or just on its own If you have no other launch options.

After getting through the PSN account linking issue (which is possible), I now have the issue that after only a few minutes of gameplay (sometimes even less than a minute) the game processes crashes in a failed pointer page alignment assertion in the WINE/Proton implementation of NtAllocateVirtualMemory. So far I've seen mostly the main entry thread, and the threads named Background <n> and Worker <n> being affected.

GDB backtrace:

#0  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1  0x00007fab9beff68f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2  0x00007fab9beb0822 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#3  0x00007fab9be994af in __GI_abort () at ./stdlib/abort.c:79
#4  0x00007fab9be993d7 in __assert_fail_base (fmt=0x7fab9c011bf8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fab9a52d770 "!((UINT_PTR)base & page_mask)", 
    file=file@entry=0x7fab9a528360 "../src-wine/dlls/ntdll/unix/virtual.c", line=line@entry=1907, function=function@entry=0x7fab9a536e98 <__PRETTY_FUNCTION__.65> "create_view") at ./assert/assert.c:94
#5  0x00007fab9bea9342 in __assert_fail (assertion=0x7fab9a52d770 "!((UINT_PTR)base & page_mask)", file=0x7fab9a528360 "../src-wine/dlls/ntdll/unix/virtual.c", line=1907, 
    function=0x7fab9a536e98 <__PRETTY_FUNCTION__.65> "create_view") at ./assert/assert.c:103
#6  0x00007fab9a5180d8 in create_view () from target:/opt/steam/.local/share/Steam/steamapps/common/Proton Hotfix/files/bin/../lib64/wine/x86_64-unix/ntdll.so
#7  0x00007fab9a51a119 in map_view () from target:/opt/steam/.local/share/Steam/steamapps/common/Proton Hotfix/files/bin/../lib64/wine/x86_64-unix/ntdll.so
#8  0x00007fab9a51c2bc in allocate_virtual_memory () from target:/opt/steam/.local/share/Steam/steamapps/common/Proton Hotfix/files/bin/../lib64/wine/x86_64-unix/ntdll.so
#9  0x00007fab9a51ed93 in NtAllocateVirtualMemory () from target:/opt/steam/.local/share/Steam/steamapps/common/Proton Hotfix/files/bin/../lib64/wine/x86_64-unix/ntdll.so
[#10](/issue/ValveSoftware/Proton/10) 0x00007fab9a4f1a02 in __wine_syscall_dispatcher () from target:/opt/steam/.local/share/Steam/steamapps/common/Proton Hotfix/files/bin/../lib64/wine/x86_64-unix/ntdll.so
[#11](/issue/ValveSoftware/Proton/11) 0x00007fab9a50e2b4 in start_thread () from target:/opt/steam/.local/share/Steam/steamapps/common/Proton Hotfix/files/bin/../lib64/wine/x86_64-unix/ntdll.so
[#12](/issue/ValveSoftware/Proton/12) 0x00007fab9befd962 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:447
[#13](/issue/ValveSoftware/Proton/13) 0x00007fab9bf78b08 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

How are you using it. If you have %command% in your launch options then you have to put it after e.g %command% -showlinkingqr or just on its own If you have no other launch options.

If you have %command% you put it after it just like your example.

With "steam[5051]: roDawnRemastered.exe: ../src-wine/dlls/ntdll/unix/virtual.c:1907: create_view: Assertion `!((UINT_PTR)base & page_mask)' failed."

I applied vm.max_map_count = 2147483642 to sysctl and for now it seems better, benchmark did not crash and map view did not crash.

https://forums.playdeadlock.com/threads/temp-solution-found-linux-crashes-when-trying-to-enter-map-from-menu.1332/#post-20795
or
https://www.reddit.com/r/linux_gaming/comments/104wop6/steam_dota2_proton/

Someone on the Nixxes team gave me a workaround. Adding the -showlinkingqr launch option completely disables the PSN requirement.

For me it still requests PSN acc.

for me the QR and the link in game are mangled, after manually following the referral_url part i was able to link steam and PSN

Added vm.max_map_count=262144 to /etc/sysctl.d/99-sysctl.conf and restarted. Works great. Issue resolved. Thank You!

Since the game does not complain about the PlayStation PC SDK being missing, does it actually work now aside from the fact the game won't connect to their Internet without workarounds?

Since the game does not complain about the PlayStation PC SDK being missing, does it actually work now aside from the fact the game won't connect to their Internet without workarounds?

I've beat the main quest just yesterday; played through the whole thing using Linux using the -showlinkingqr launch options and after increasing vm.max_map_count to 16744443 (2^24 - 2^16 - 5; default value is 2^16-5).

Since the game does not complain about the PlayStation PC SDK being missing, does it actually work now aside from the fact the game won't connect to their Internet without workarounds?

I've beat the main quest just yesterday; played through the whole thing using Linux using the -showlinkingqr launch options and after increasing vm.max_map_count to 16744443 (2^24 - 2^16 - 5; default value is 2^16-5).

I believe the PlayStation Overlay is an indicator. Is it working by any chance?

I've beat the main quest just yesterday; played through the whole thing using Linux using the -showlinkingqr launch options and after increasing vm.max_map_count to 16744443 (2^24 - 2^16 - 5; default value is 2^16-5).

I'm curious how it ran for you. I'm getting horrible strutters whenever I pan the camera.

I've beat the main quest just yesterday; played through the whole thing using Linux using the -showlinkingqr launch options and after increasing vm.max_map_count to 16744443 (2^24 - 2^16 - 5; default value is 2^16-5).

I'm curious how it ran for you. I'm getting horrible strutters whenever I pan the camera.

I messed up starting OBS properly recording in the latter parts of the game. But here's some actual game play captured doing the "The Queen's Gambit" quest: https://www.youtube.com/watch?v=N5Esiy37_xg

I messed up starting OBS properly recording in the latter parts of the game. But here's some actual game play captured doing the "The Queen's Gambit" quest: youtube.com/watch?v=N5Esiy37_xg

A 30fps video without a frametime graph doesn't tell me much unfortunately. Here's what it's like for me:
2024-11-11 14-17-08-00.00.08.000-00.00.40.000.webm

Here's a benchmark setup: i512600kf, 32Gb ddr4, RTX4060, 2560X1440@120hz. Debian 12, stock Nvidia 535 driver, Proton experimental. Dedicated fullscreen, high settings, vsync on, DLSS set to balanced, antialiasing set to DLAA, Dynamic Res Scaling set to 60, Nvidia reflex off, Frame generation off.

To get DLSS working, I had to download the exact same driver version from the Nvidia website as the one from the Debian repo. I just used the search tool to find it. Unpack it with the --extract-only switch. Find the two dlss dlls and copy them to the root folder of the game. I have a guide up on Steam if you want more details. After copying the dlls, I could select DLSS. There were only intel and amd options present before that.

I get a fairly solid 60fps with dips into the mid to low 50's in Meridian and some stuttering during combat. There is another guide up on the HZDR Steam section that details turning off mouse deceleration by setting a registry key to get rid of the stuttering. I haven't tried it yet. The key is Computer\HKEY_CURRENT_USER\SOFTWARE\Guerrilla Games\Horizon Zero Dawn Remastered\Input Located in the games prefix registry, it should be set to 0.

Hope that helps. I'll post again if I get to test the mouse thing.

Nvidia users at the very least probably prefer to use the -showlinkingqr method. Using SteamDeck=1 on Nvidia can trigger a bug (in the games Steam Deck mode) where the image will appear to be jittering/shaking slightly when using DLAA or DLSS.

I have read about the "-showlinkingqr" switch a bunch of times now but for me it just does nothing...
I still get a QR code and a "Continue" button which tries to open a playstation page (which doesn't load for me... In austria...)
I tried multiple Proton versions Availible in steam with an even bigger list of launch options with and without gamescope...
Proton: Experimental, 9.0-3, 8.0-5, Hotfix...
GPU: NVIDIA 3080TI
OS: Arch (last updated a few days ago)

If anyone has any ideas what other switches or combinations i could try i would be very happy!
(I am gonna try installing the old "complete Edition" and gonna try to convert over a save file to see if they are checking for this separately...)

-showlinkingqr only works on the Steam edition of the game. On the Epic edition, which I have, there is no workaround. On that edition, the -steamdeck option doesn't work either. I have been unable to run the official PSN (despite trying to manually pre-run the exe in the prefix to ensure it's enabled).

Proton: Experimental, 9.0-3 and a few others, not sure.
GPU: Nvidia 3070
OS: Bazzite 41 (Updated today)

-showlinkingqr only works on the Steam edition of the game.

For me the "-showlinkingqr" option doesn't work on the Steam edition...

I don't think -showlinkingqr bypasses the PSN account requirement. It just shows an alternate QR code menu that's built into the game.

I registered via the PSN website and then linked Steam via the menu option on Horizon Forbidden West. After doing that I received the free items for HFW. The next time I started HZDR I also got the free items for that game and the "No internet" dialog didn't show up. The game just proceeded to the logos then the cutscene.

I no longer need the -showlinkingqr switch to start the game further reinforcing the idea that it's not a bypass, and just an aid to link your Steam account.

I remember someone on Steam mentioning issues with the wrong country showing up in the PSN registration URL page and being able to register after manually changing it. I can't find that thread on Steam again though. It's worth a shot to look into.

It doesn't bypass the PSN account requirement, however it does bypass the PSN API Software requirement; this software does not successfully work on Linux, even when run manually.

So does anyone happen to know why the PlayStation PC SDK isn't working properly under Proton at this time?

I'm experiencing a random freeze on HZDR, seemingly regardless of what graphic settings I have. The game works normally for a while, between 10 and 120 minutes, and then freezes hard and crashes to desktop. Can't see anything obvious in the proton logs, and tried the suggestions here, that is to set vm limit before starting game, and use empty LD_PRELOAD.
I am leaning towards graphic card having an overheating issue, but not had any other game freezing. Attached steam log.
steam-2561580.zip
Note, I haven't had any issues with PSN, maybe due to connecting to it from some other Steam game - HZDR just started for me and had no issues other than that random freeze/crash.

HZDR ran fine for a while, but now I have an issue with audio. It just randomly stops after around 20 minutes. The rest of the game continues normally. I can't see anything in the Proton logs that relates to audio as far as I can tell.

HZDR ran fine for a while, but now I have an issue with audio. It just randomly stops after around 20 minutes. The rest of the game continues normally. I can't see anything in the Proton logs that relates to audio as far as I can tell.

Yeah, I have those sometimes, too – also in HFW, for that matter. However, my suspicion is, that this might be an actual RC bug in the game engine itself: Whenever I attach a debugger to the game and look at its thread status I see the audio threads waiting on a synchronization primitive to be released in a different thread. I also noticed, that sometimes that wait times out, and audio resumes.

Add to that, that I observed that bug in Windows, too, just much much rarer, my suspicion is, that there's some unmitigated locking issue there, that depends on peculiarities scheduler timing and the time behavior of the audio subsystem among other things.

On my Linux gaming rig I've given the audio daemon (Pipewire or PulseAudio) a higher priority and that seems to help.

On my Linux gaming rig I've given the audio daemon (Pipewire or PulseAudio) a higher priority and that seems to help.

I checked and both pipewire and pipiwire-pulse were already at a nice value of -11, but I bumped it down (or up, depending on how you want to lock at it) to -15. I'll check tomorrow if it helps. Thank you for the suggestion @datenwolf!

Also to add to the issue somewhat I tried Proton 9.0-4, Proton Experimental, GE-Proton9-23 and GE-Proton9-13. Subjectively Proton 9.0-4 seems to take longer for the audio to crash so I'm using that atm but what's weird is that I'm around 24 hours into the game and the first 20 were on GE-Proton9-13 with absolutely no issues whatsoever.

No luck. Dialogue and/or all audio still cuts out eventually and I need to restart.

EDIT: This fix by a HFW player seems to work for the most part!

Needs further discovery, but it may be that the PSN requirement is being ameliorated to some extent.

https://blog.playstation.com/2025/01/29/new-in-game-content-incentives-coming-to-playstation-games-on-pc/

Making PSN optional hopefully means that playing without the PSN API software installed becomes possible, which will lead to Linux gameplay becoming possible without having to somehow figure out how to enable the software. My fingers are crossed...

I just got to the main menu on the Epic Games Store edition of HZD:Remastered. I got an error message on the PSN Api screen, however it allowed me to continue, telling me that "Somethign went wrong initialising the API", but it did not stop me from continuing. That's a thank-you to Sony and Nixxes for finally allowing this access.

The game crashes for me unfortunately. I can start the game and run through the initial wizard (where it asks whether you want to enable HDR, Screen Brightness etc), but a few seconds after the SONY logo appears the game crashes. I've tried Proton 9.0-4, Proton Experimental and GE-Proton-9-27

steam-2561580.log

EDIT: Might have solved it by setting: sysctl -w vm.max_map_count=262144, but still testing.

+1 on the audio issues I tried running

pw-metadata -n settings 0 clock.force-quantum 50

With no luck

here are my logs zipped steam-2561580.zip

(sorry for the 2 post for some reason github wasn't showing my the post I made yesterday)

Edit: this seems to happen on nobara as well as steamos
Also in all 3 hzd crashes after a while of losing all game audio

Hello, there seems to be an issue with Steam Input when using the Deck's controller on Horizon Zero Dawn Remastered. It may be a Proton issue, but it's not currently clear. When pressing Y to auto loot a container, and sometimes when pressing start to pause or select to open the map, the game will sporadically not accept any input, or ignore the input. This problem has been reported by numerous users on Steam and Reddit, and on Windows machines the fix is generally to disable Steam Input for the game. However, on the Deck this is not an option as Steam Input is the only way the Deck's built in controller is recognized.

A workaround is binding the left trackpad to the mouse function, and wiggling it every time you open a menu or go to auto loot. That seems to kick it into gear and allow the input to go through.

Some references to the issue:

https://www.reddit.com/r/SteamDeck/comments/1o42smu/horizon_zero_dawn_remaster_controls_stop_working/

https://steamcommunity.com/app/2561580/discussions/0/685238092472456107/

I have a problem with Horizon Zero Dawn™ Remastered when Proton 10 is used. Game always starts in borderless windowed mode even if it previously set to use exclusive fullscreen. Also when switching between windows with alt-tab it just hangs.
When Proton 9 is used the game starts with exclusive mode and can be alt-tabbed just fine.
Proton-experimental and Proton-GE are also affected.
There are also reports about that problems on protondb.

@Shished by borderless windowed do you mean the "fullscreen" option? nothing is explicitly called borderless so I want to make sure we are on the same page. I see that when exclusive fullscreen is selected, the game will switch to fullscreen while tabbed out before returning to exclusive fullscreen when tabbing in, but this does not result on the game crashing or hanging.

Can youg ive more information about your setup? gpu model, driver version, desktop environment...

@simifor I meant Fullscreen vs Exclusive fullscreen.
I did further testing and found that my previous comment is wrong, sorry for that.
If the game is set to Exclusive Fulscreen, it will hang on alt-tab in both Proton 9 and 10, and screen mode will reset to Fullscreen in both versions on game start.
What different between Proton 9 and 10 is that with Proton 10 the game will not open in full screen, the Gnome top bar will be visible while with Proton 9 the desktop UI will not be visible.
My PC specs:

OS: Arch Linux (Steam Flatpak runtime)
DE: Gnome 49
KERNEL: 6.18.9-zen1-2-zen
CPU: Intel Core i5-14600K
GPU: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 21.1.8, DRM 3.64, 6.18.9-zen1-2-zen)
GPU DRIVER: 4.6 Mesa 25.3.3 (git-a9c6420d8c)
RAM: 32 GB