Home
Gaming  

Diablo 4 will now turn on resolution scaling by default on PC, so don’t be alarmed if things suddenly look blurry


Blizzard has revealed the patch notes for Diablo 4’s next update, which will arrive tomorrow, March 18 on all platforms. This is a smaller patch, so don’t expect anything massive. Ironically, though, the biggest change has little to do with gameplay.

This patch adds new graphics technology, and it also makes a change that aligns the game with so many other modern releases.


To see this content please enable targeting cookies.

Patch 2.1.4’s biggest addition is support for Intel XeLL and XeSS Frame Generation. Diablo 4 already supports the image upscaling side of both of those technologies, but it will soon get Frame Generation, too.

Although this is nice to have, most people who care about the tech will likely own an Nvidia card and make use of DLSS there instead. Regardless, you’ll be able to turn that on in the game’s graphics options menu.

Now, onto the more controversial part of the patch. After installing it, the game will now default to enabling resolution scaling. In other words, it won’t run at native resolution by default. The chosen upscaling method will depend on your hardware, according to Blizzard.


A couple of fixes for Headhunt events, too. | Image credit: Blizzard Entertainment.

It’s not yet clear what sort of settings Blizzard has chosen for the different hardware configurations, but the practice of enabling DLSS and FSR – or image upscaling in general, is quickly becoming more and more common across modern games. Some games even default to – and expect – Frame Generation to be enabled, such as the recently released Monster Hunter Wilds.

Apart from all the technical upgrades, the patch also comes with a few bug fixes, including a fix to a bug that prevented Scour events from being completed, and another that cause herb node icons to disappear from the minimap during the same event.

The patch also fixes an – admittedly amusing – bug that prevented players from being able to rename a loadout when they disabled the mature language filter. You can read the full change log on Blizzard’s blog.





Source link

Exit mobile version