Screen gets blurry

When i am playing my screen gets blurry when i move. This happens alot in dungeons. The screen resets after i go into the options screen and go back. It is unplayable for me at the moment on the pc.

I tried multiple settings turned off but nothing works.

Has anyone else encountered this problem?

Picture of the issue

2 Likes

It’s not your PC. It’s 99% the anti aliasing setting in game that probaly uses TAA variant. This causes motion blur when you start moving.

3 Likes

Exactly, the TAA causes motion blur when you start moving !
It’s so annoying and burns eyes !

1 Like

Anything from my side i can do to counter this?

Same issue here with rtx 3090. Dunno what to do… I ll try to replace dlss file…who knows… ^^;

Guys I can confirm that the best current fix, as guys have already mentioned here, is to get the latest nvngx_dlss.dll from techpowerup (NVIDIA DLSS DLL 3.1.13). Then just replace that file in your base Diablo 4 folder after each time you reload the Battle.net app / close the game (as it will revert it back to the 3.1.1 DLSS DLL version when you close the game or when you load up Battle.net - you will see the 33MB patch come through).

This doesn’t remove the blur completely, but it is now 90% gone. Much harder to notice while playing now … and especially in those slow camera pans during in game cutscenes.

I am running a 5950x, 3090 and the Alienware Ultrawide QD-OLED (so 0.1ms response times) … playing @ 3440x1440 with DLAA on.

Easiest way to test is to load into game as normal … then just zoom all the way in and look at your character standing still. You will see his/her helmet blur heavily when they are breathing looking at them from above.
Now log out … replace the DLSS DLL to 3.1.13 and watch your character breathing again. Blur will be almost gone now.

Just remember to replace the DLSS DLL everytime u load the game (after you open up Battle.net and just before you hit play) as it will revert back to the old 3.1.1 when you reload Battle.net / after you close the game.

Hopefully Blizz / Nvidia add the nvngx_dlss.dll at the driver level when the next driver comes out (like they have for other titles) … so it always uses the latest dll instead of the one that shipped with the game.

Wall of text … but it fixed it for me … try it for yourselves.

1 Like

Cannot reproduce on Radeon. This blurring is a Nvidia thing? D4 uses older Nvidia library? Hopefully they will upgrade to the one you found.

Not a Nvidia thing … I believe it is a native motion blurring to the D4 game engine … as the blurring is still present even with DLSS or DLAA off.

However for me at 3440x1440 and with DLAA on (which is basically DLSS @ native res as an AA method far superior to anything else and more performant) the latest DLL is much much better at cleaning up the image during the ‘reconstruction DLAA’ pass during motion.

So for Nvidia users it def is a huge improvement in masking this blur using 3.1.13 vs 3.1.1 DLSS DLL

So basically what you are saying is, it’s the TAA from the game but you are bruteforcing it with supersampling and the latest DLL improves the quality of that.

While this might help people with high-end GPUs who can afford to enable DLAA it does’t fix the problem and does nothing for 90% of the users :slight_smile:

1 Like

Improvement is also there with DLSS @ quality … but yes, better with DLAA .

So as D4 isn’t that hard to run most Nvidia users will benefit from swapping the DLSS DLL to the latest version.

Also I don’t think it is the TAA as turning on DLSS usually disables other AA methods as it overrides them. Think just motion blur, which is fine for consoles @60fps, but PC users who can push higher fps usually disable motion blur via game settings.

If it is not an Nvidia thing, have there been reports of Radeon users experiencing it? You can point to right topic please?
I have Radeon, everything maxed out, zero blurr. I don’t even know what antialiasing game is using, just maxed out and it works perfectly fine.

Seen other Radeon users say they also can see the blurring when moving.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.