Hello fellow gamers.
I am one of those locked out from playing the game because of the infamous ‘AVX’ issue and come to you now with some recent discoveries that will put this whole debacle to rest and reveal the truth.
First some background. On September 23rd when Diablo 2 Resurrected released, I was there at zero-hour looking at the “Play” button just waiting for it to glow blue in anticipation for the long awaited remaster. When I heard my friend on Discord yell: “ITS UP! ITS UP!” instantly I restarted my Battle.net client and there it was… glowing blue like a clear summer sky! I press “Play”… crash.
After trying again, and again without success I started troubleshooting, reinstalling, looking at every blue post, support thread and everything I could find on Google to find a solution but still it did not solve the problem.
Since then we have come to learn that this is related to something called ‘AVX’ and been told that our poor computers just simply aren’t strong enough to use it. But there was one thing that rubbed me the wrong way about this answer… my CPU (i7-3770k) has support for AVX! So I started doing more research looking into it, as a computer savvy guy and developer myself I just simply couldn’t believe it. My computer is above the minimum requirements so I should be able to run it right?
Some time passes and I get an answer from Blizzard Support. They tell me that my motherboard does not support AVX… shocked with that answer I do more research. Thinking to myself “can a motherboard really not support all the features of the CPU?”, of course this couldn’t be the case and today I finally found out why!
As a developer, I started up a project and wrote some code. I compiled it using the infamous AVX… Runs perfectly.
I compile it using AVX2… crash.
Interesting, so I do what any developer would do in my situation, I look deeper into the D2R executable and find that the binary uses instructions exclusively targeting AVX2, which is different from AVX.
So the proof, in the binary I found that it uses an instruction called ‘vpbroadcastd’ you can find more information about that on <cant put link but you can search vpbroadcastd on google and find Intel Intrinsics Guide> where it stated that it is a feature in AVX2. Looking into the binary more I bet I can find even more AVX2 exclusive instructions.
Now you may think, what’s the big deal, AVX here AVX2 there it doesn’t matter. But it does! If my research is correct then it is proof Blizzard has officially lied not only in the many blue posts, the support answer I got pointing fingers at my motherboard but also on their minimum requirements article because i3-3250 does not support AVX2.
Why they did not come forward and just tell us they accidentally enabled AVX2 instead of AVX if this is what happened is up for debate.
TL;DR: D2R uses AVX2 not AVX and we’ve been lied to.
Sorry for the long read but hopefully I got the point across without to much tech gibberish, let me know what you all think about this. Does it change anything?
Edit: One thing that I forgot to mention is that if it is true that AVX2 is required them lying about it could be considered illegal under U.S customer protection laws. I’m not a lawyer so that’s all I’m going to say about that.