Diablo 2: Resurrected Fix ‘Could Potentially Affect All Users’

Diablo 2: Resurrected Devs Want to Make Sure They Don’t Make the Problem Worse

Diablo 2: Resurrected fans were glad to know that the redo of one of the greatest action RPGs of all time was finally launched. However, its release has not been entirely smooth. Many players complained that their characters suddenly disappeared and that they were locked out of their games.

Blizzard has since rolled out what Diablo 2: Resurrected players assumed was a permanent fix to last week’s issues. Unfortunately, one particular problem that is connected to an AVX—Advanced Vector Extensions—issue seems to be taking longer to patch. AVX are extensions of the x86 instruction set architecture that was first introduced in early 2011 on intel Sandy Bridge chips. To make it simple, AVX has been around the gaming industry for a while, and has apparently resulted in some confusion over what type of hardware can and cannot run Diablo 2: Resurrected.

diablo 2 resurrected bug fixes

The minimum supported CPU required to run Diablo 2: Resurrected is listed as either an Intel Core i3-3250 or an AMD FX-4350—both of which support the AVX instruction set. Considering that the game was advertised to feature the same “underlying game engine” from 20 years ago, players who had lower end hardware still took a swipe at running the game. It worked, for a bit.

While CPUs without AVX are below our minimum spec, we want to try to ensure as many people as possible can play,” stated Community Manager PezRadar. “In optimizing the game, we inadvertently included the need for AVX for launch.” At the moment, Diablo 2: Resurrected devs have decided to allot more time for testing. “QA is going to spend another few days of testing across all of these scenarios and setups in an effort to ensure we are not impacting existing players,” he added.

With that said, it has become clear that a fix is coming, but Blizzard is intent on not ending up making things worse for all Diablo 2: Resurrected players. “The fix could potentially affect all users, even those outside of not having AVX support,” PezRadar continued. “So, we are wanting to make sure we do proper testing.”