Thanks.For more Diablo 4, be sure to check out our dedicated section or some of our Guides & Tutorials just below:ĭiablo 4 Class Builds - Best Barbarian Build | | Best Necromancer Build | Best Sorcerer Build | Best Druid Build | Best Rogue Build | All Classes Tier List | Best Class For Beginners | Build Calculator |Ĭlass Mechanics: Sorcerer Enchantment System | Barbarian Arsenal | Rogue Specialization | Necromancer Book of the Dead | Druid Spirit Animals | Unlock Golems | Can a blue please confirm the D2R team has tried to run it on Win11? I’m seeing mixed messages on whether it’s even supported. This is a pro custom-built (Falcon NW) machine that I unboxed 2 hours ago. I don’t believe we all have the exact same driver issue. I’m seeing quite a few reports on the internet of this exact same behavior. I did an uninstall/reinstall (not yet a clean install of everything, including bnet), same behavior. Music stops, little flame widget in the bottom right freezes, and client crashes, no error report. Since that first crash, the client crashes every time between the Blizzard/D2 title splash and the main “Press any key” title screen. Relaunch from bnet thinking it’s just a fluke. Within 5 seconds, I get the error report in the background, which I close. Open the Task Manager and end the D2R process.
Totally fine until randomly in the middle of the sanctuary the graphics freeze, mouse cursor still works. D2R client launched, I configured my game settings and did a Chaos Sanctuary run since that’s one of the more graphics-intensive maps. Brand new rig, first app I installed was bnet and D2R.
0 kommentar(er)
