Yeah, using taskset definitely makes a big difference in preventing 100% overload and certainly works as a somewhat annoying workaround (since it has to be done every launch). I just don’t think it’s the devs’ intention for the game to be limited that way to begin with, hence the bug report. Seems to me they’ve clarified many times over the years that the game, while CPU-heavy, is not truly single-core… but that’s precisely what the current default affinity issue forces the game to be.
Hell, even if it was truly single-core that kind of forced affinity setting is super weird. I play plenty of old games still (many of which are genuinely single-core) and that’s just not how any of them do it. Case in point: I just tested my classic Diablo 2 LoD install and it works as expected: with all cores available.