As for the other methods that didn’t work on M1 machines, they also won’t let you run Diablo 4 on Mac M2. Also, just like with the M1 machines, the Game Porting Toolkit method also works on M2 Macs. So this particular issue is affecting 0.1% to 1% of the userbase…Ĭompare that to the server issues they ran into during the night, that possibly affect the 99 to 99.9% other users… Blizzard is out making profit, so that means they have to please the bigger base… So first things that got fixed were the servers… Then they could move on the the other, more minor bugs… Yes this is most disgruntling to hear/read, but that’s a cold hard fact… Actually I’m somewhat relieved they actually tried to compile a build through the night, even if eventually it was unsuccessful… They actually care about that 1% or 0.You’ll have no problem playing Diablo 4 on Mac M2 if you go for our Boosteroid cloud gaming instructions, as this method is very versatile and works on pretty much any Mac model, regardless of the type of CPU that it has. I don’t know how many sales were made during the pre-release period, but I’m assuming that it ranges between 10 to 100 millions. I understand people can get angry over this, hell, I am too, but I also can ake a step back an take into account that this issue – with a 1.5k post on the US forums, from which at least a third is ranting and not helping the devs, so let’s say 1k user actually reporting the bug, and let’s be generous, affects actually ten times more people – affects something like 10k users. Unfortunately the build didn’t meet QA terms, which cannot be foreseeable. Steps have actually been taken, the fact that they started a build that went through QA somewhat around 2AM at their time means that they’ve actually done something. This tread is ongoing since yesterday, with promises that it is going to be fixed soon, and not a single freeking step has been taken since.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |