Blizzard updater stuck at updating setup files
That means Task Manager shows 32 tiny little performance graphs. NET really fast (lots of C /CLI these days), and is killer for working on all that multithreaded rendering code.
Anyway, the fix is a bit clumsy but it seems to work (so far!
“Diablo III.exe” would pop up in Task Manager, and then silently disappear a few seconds later.
According to the Windows Event Viewer, it was crashing.
I did some experimenting and it seems to hit once the # of available logical processors hits 17.
If it’s 16 or less, no matter how you spread them around the two physical processor sockets, it’s fine.
A better solution would be to find a program that remembers cpu affinity for processes and can set it on launch.
Unexpectedly in mid-May 2017, Blizzard announced they would be hosting Bungie's Destiny 2 in the desktop app (Windows-only).Hacking the thread affinity to Because it’s not ready yet.I’m making some big bets on a new rendering and a completely new way to write code for the tools in order to enable fine-grained history.I added Diablo 3 to Steam, and now at startup I force Steam to use every other logical processor with the utility.This also fixes a few other games such as Deus Ex: Human Revolution.