Horizon Zero Dawn 1.11 update #941
Comments
|
Hi @phush0 could you try dxvk-nvapi from jp7677/dxvk-nvapi#60 (there are binaries attached to that PR)? |
|
More problems: |
Hi @jp7677 , I've attempted to do this (I believe I retrieved the correct binaries). The new nvapi doesn't cause DLSS to appear where it should in the menu, even with appropriate launch settings that function for other games. Looking at proton logs, it seems that the NvAPI workaround is still being enabled. I don't believe the flickering textures/foliage are related to nvapi, as there are reports in this steam thread of the same issue presenting itself to users with AMD cards. The issue definitely does seem to be with proton, however. Here are two proton logs. In the first, I booted the game, went to the settings menu, saw no DLSS, and closed. |
|
Can definitely confirm that the graphical issues as described by @Vaudrain appear to be exactly the same on two separate systems. With the difference being that the Nvidia system doesn't open up DLSS when "PROTON_ENABLE_NVAPI=1" is enabled. System 1. System 2. Seems to be separate problems going on. One that affects the graphics, blurring and smearing especially with camera movement, no matter the in-game settings. The other is that same issue, but when FSR is enabled there are coloured artefacts on screen. In one seen I could see the outline of the 'current objective' text that shouldn't be there (didn't get a screenshot of that)
It's got the look of some sort of temporal issue, especially in that second image. |
|
In order to enable DLSS game needs |
Could you please attach the dxvk-nvapi logs here with the nvapi binary from the PR? Please remove the old log file first because logs will be appended to the existing file. |
here working example Proton Experimental uses DXVK DXGI so you have to use Flickering is still there and better observing - it is not flickering just some foliage have wrong textures - transparent and rotation of the camera just draw edge of the foliage inside. May be a game bug who knows. |
|
@phush0 I'm confused by your latest posting. Does DLSS works now with the game update? The logs you posted are not from the branch like I had asked. |
|
It is working with stock NVAPI in Proton Experimental with |
|
Alright, then I just assume that not having DLSS was a configuration issue. |
|
Yes, I can confirm that not having DLSS was a configuration issue. First time I've encountered The foliage issues confirmed by @Blitzwing1 are still present, and the addition of any upscaling (FSR or DLSS) introduces a chromatic element to the artifacting. I don't know if it's any help, but here's a video demonstrating it, it's much easier to see in motion. The nature of the artifacts does mean that youtube compression completely crunches it though. |
|
I see similar chromatic artifacts with AMD RX580 RADV when using FidelityFX. |
|
I'm also affected by this bug introduced in 1.11. I'm on NVIDIA RTX 3060Ti (495), tried different Proton versions, no NVAPI enabled. Especially the grass, but also trees are very wrongly colored and there is a lot of smearing when moving camera. I took another footage: https://streamable.com/9mvl10 I never tried to debug/dump any logs of vkd3d-proton, but let me know if I can provide anything helpful. |
|
Hey I also have this issue (arch linux, AMD rx580) let me know if I can post anything to help. |
|
Hay, same issue here. Ubuntu 20.04 Tried with Proton 6.3 as well as Experimental. |
|
Definitely got graphical artifacting, at least on foliage. It almost looks like the foliage is some transparent, with a texture layer behind it, like you might have in GIMP or Photoshop. When I move the camera, it's like looking through a window into the underlying layer, which isn't moving at all. It reminds me of the anime Gankutsuou: The Count of Monte Cristo, where a similar thing is done as a stylistic choice. It looks normal when I hit escape. Video here: https://user-images.githubusercontent.com/3501477/145696479-6e358c49-30d2-4444-91fb-0b229339cf23.mp4 Another bug, when I try to use the new FSR upscaling option from within the game, all the 3D graphics turn black. I can see the HUD and the menus, but I can't see the world. Game version 1.11 |
|
On ProtonGE 6.21-GE2 AMD RX580 adding RADV_DEBUG=llvm to steam command fixed the graphical artifacts with foliage. This workaround hasn't affected performance and the game is running well. |
Do you, or anyone else, know if there's an Nvidia equivalent to this? |
|
@kscherer What issue is that? Could you give more information, hardware, mesa version, screenshot etc please? |
|
The screenshots from @Blitzwing1 above show the graphical artifacts related to foliage. With FSR there are extra colors. Without FSR there is also graphical corruption. It is this specific issue that is "fixed" by adding RADV_DEBUG=llvm to the Steam command with and without FSR enabled. With the addition of RADV_DEBUG=llvm the game runs great, looks great and I haven't noticed any other issues. My system is RX580 running Proton 6.21-GE2 on Ubuntu 21.10 with mesa 21.2.2. I don't know if the workaround is relevant to Nvidia hardware. I learned about this workaround here: https://www.protondb.com/app/1151640 |
|
I know it's not much help but on a 5700XT, Proton Experimental and current mesa main branch it works fine. With or without FSR and both version 1.11/1.11.1 I can try running on another mesa release. Might possibly be already fixed. |
|
No, it's very useful! If you could try to reproduce with the same version (Mesa 21.2.2) that would be awesome. It could be a Polaris specific issue or something we fixed since Mesa 21.2.2. |
|
Tried mesa 21.2.2 with both Proton 6.3-8 and Experimental. Can't reproduce on NAVI10. |
|
I'm on Mesa 21.2.5 with Proton Experimental and i experience the same foliage issue. GPU is a AMD VEGA 56 |
This is probably not an AMD-specific issue, it happens in exactly the same way on NVIDIA. I think the debug mode just changes some context of how vkd3d, the game, and the drivers interact so it may be some ordering or locking issue. I'm not sure, tho, if this is related to a recent game update (I think they FSR lately), or a vkd3d/Proton update (didn't run the game in a while) - the title indicates it's due to a game update. Since both NVIDIA and AMD show the issue, it's unlikely that a Mesa update would fix it - if it does, it's probably rather a "hide" than a "fix" (similar to how the RADV debug mode hides the bug). So it's probably more likely that a vkd3d improvement properly fixed this. If using FSR on NVIDIA, the foliage is covered in LSD-like rainbow colors drawn over a black background but it still has the same "smearing" effects we can see without FSR where it seems that the game just draws alpha textures over non-cleared buffers, leaving behind traces of the previous frame which then slowly fades away. While only foliage seems to be affected (which probably has a lot of alpha texels), it seems that lighting and illumination is sometimes also way off - but that may just be my personal experience over the black foliage with the funny colorful LSD effects... :-D |
I can say that it likely isn't something that was fixed in versions beyond 21.2.2 as I tested it on 21.3.0 and had the exact same issues, nor do I think is it related to Polaris as I'm on vega and it still happened, plus others seem to have the problem on Nvidia chips. Unfortunatley I had x11 bug to all heck on my desktop to the point where i had to reinstall the whole os, I'm currently transferring HZD from my laptop back over where I can test 21.3.1, with and without the "RADV_DEBUG=llvm" ENV variable pointed out by @kscherer and report back. |
Pretty sure it's a game update, since I was actively playing this game on a Glorious Eggroll version of Proton, didn't change anything other than update the game, and suddenly had this bug. No Proton and as far as I can tell no vkd3d updates either, unless those are downloaded separately in some way. And I have a 1080ti, so no AMD Mesa whatever for me. May have been something already broken in vkd3d and that simply got exposed by the update for all I know, though. Or vkd3d exposing a bug in the game. You tell me. |
|
Jup i downgraded the game back to 1.10 and it worked flawless again, its definitely the update. |
How did you downgrade? I've been trying DepotDownloader and I just couldn't get it to work. It kept downloading 1.11 files anyway. |
|
So, I've tried both 21.2.2 and 21.3.1 both still have the same issues as described in other comments, smearing and blurring without up-scaling, and when up-scaling is enabled coloured artefacts too. With "RADV_DEBUG=llvm" set then it cures those issues and seemingly allows up-scaling with FSR to work as well. Seems like whatever issue is happening it doesn't affect AMD's official shader compiler, but obviously impacts RADV and Nvidia's drivers in the same way. |
Depots/manifests to downgrade
Links to SteamDB: Updated files: No artefacts after downgrade |
I was already doing that. Seems to me now that while I did, I wasn't actually launching from my downgraded game folder, but from my updated game folder. I'm now on 1.10 again. Nice. Now there's still one problem, how do you prevent Steam from updating the game again? Because apparently that was what I was (and still am) actually struggling with. |
Awesome work! |
Well it's really just down to downloading DepotDownloader (https://github.com/SteamRE/DepotDownloader), and then running the aforementioned 2 commands in your DepotDownloader directory. 2 folders will be created with some files inside, among which those 4 files. One will contain the exe, the other folder the bin files. Copy them over to your game folder and you've now downgraded your game. I recommend backing stuff up, Steam can be a bit annoying, trying to force game updates down your throat. If you have a game folder somewhere that you know works, you can always go back. |
I suspect that Steam will override the files when I try to start the game and they will be updated (broken again) - am I correct? |
It did update it at first, yes. But I just replaced the files again, and Steam thought it was still the updated version when it wasn't anymore. No idea when Steam will notice that my version is out of date, though. It very much might try to update again later. |
I can confirm the fix and would like to add a few points. In order to avoid downloading dozens of gigabytes you can create two files: and after that run the commands: The ${USERNAME} variable should be set with your Steam username. You will be prompted for password as well as the 2FA code. |
How do you downgrade? I haven't found a good answer |
first you will need to install dotnet runtime on your machine (assuming you do not already have it). You will need dotnet runtime 5.0 or newer specifically. if you search dotnet runtime linux there should be a link from microsoft.com in the first page of your results walking you through installation for your specific linux distro (or its base distro, in my case ubuntu 20.04). The next thing you will need is the DepotDownloader referenced above in @Amanoo 's post. after that you should follow the download steps in @georgitsenov 's last post. I recommend making the file lists he refers to in nano, it was easy enough as I was already in a bash shell for most of the dotnet installation process. Finally you need to replace the existing HZD files in your steam folder with the ones you have just downloaded. launch the game and you are golden. Hope this helps. |
Thanks for the reply! |
|
I have uploaded a script that will automatically downgrade Horizon Zero Dawn for those who are having trouble in the future. It can be found here. |
|
The game is crashing after replacing with these files. The message just says Unfortunately the game has crashed, do you want to send a crash report. |
Try launching it a few more times. My game also crashes a lot at launch these days. Once you've been in the game story for a few minutes, it's stable. |
|
Hi @HansKristian-Work does this fix in #962 also fix the grass texture bug (grass smearing etc, the bug seen here: #941 (comment))? Thanks. |
Hi, I know you didn’t direct the question at me but if I can save busy maintainers their time I will try. I’ve only had time to boot up the game run around a bit, try it out on my AMD desktop and Nvidia laptop, with and without FSR on the AMD machine and with and without DLSS on the Nvidia and I’m fairly sure it is working just like before the 1.11 update to the game. tl;dr seems all good now. |
|
That sounds great to me, hopefully I can test it out when it comes to Proton Experimental and/or ProtonGE and confirm that the grass bug is fixed for me too. |
|
I can confirm that the latest vkd3d-proton fix in #962 has fixed not only the grass texture smearing but also the FSR black screen bug I was experiencing. I'm getting better graphics and better performance now thanks to the fix. |
|
Proton Experimental usually carries the latest dxvk and vkd3d branches when it is updated. I just tried and can confirm: Graphics rendering is working properly again, and the game also loads proper textures again instead of super-lowres textures with reduced or even missing geometry - all good again. |
|
I just updated HZD and downloaded Proton GE 7.0rc6 which has just been released. I can no longer look into another dimension by looking at grass, whether with FSR on or with FSR off. Issue resolved. It still looks a little bit trash with FSR on, but that's probably just FSR itself making it look a bit grainy through some sort of oversharpening. Simple upscaling makes it a bit blurry instead of grainy, since it actually does too little while FSR overcompensates. I think I prefer Proton's built in FSR implementation. |
here in center over stairs - in front of the palm tree
left bottom corner
After 1.11 update there introduced upscallers. With VKD3D from Proton Experimental - DLSS is not working - can not be selected in game menu at all. Nvidia Vulkan Beta 470.62.13. Startup params:
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 gamemoderun mangohud prime-run %command%There are flickering textures in benchmark, on foliage (attached to buildings).
note: all settings to HIGH, except AA is off
The text was updated successfully, but these errors were encountered: