Latest Crossover / MacOS / Battle.Net / Diablo II Resurrected not working together.

John Hammer1 wrote:

It's not just about the impact on some specific game the OP reported. It's about a bug in Rosetta2. Even though the next version of MacOS coming this fall is likely to have only a partial implementation of Rosetta2 and even though it is eventually going to be fully deprecated, many Mac users will rely on Rosetta2 for quite some years to come. Patching out a bug seems to be a reasonable ask of the developer of Rosetta2, which happens to be Apple itself. There is no reason this specific API call should continue to fail to resolve now that it has been identified and reported to Apple.

My post had nothing to do with bugs. The bugs just reinforces my point about the house of cards needed to play Diablo here. It was purely based on knowing how difficult it can be to get non-native apps to run on a system using WINE....games are even more difficult.

Games are the most difficult apps to get running smoothly & properly even on their native supported systems. Games tend to push the current limits of the hardware so developers are known to take questionable risks to make a game run reasonably well on supported systems. Those "hacks" may not always play well with the WINE hacks, or the GPU proxy layer & may be doing things Rosetta2 was never made to handle.

It is a bit like the Telephone Game/Whisper down the line game that a teacher performed in elementary school with my class. What was whispered to the first person was not the same as what the last person spoke....the message got mutated....it is kind of similar here with all of these different layers that must perform exactly as it would on an Intel-based Windows system. There is no way it will be perfect since the WINE developers are doing their best to reverse engineer the entire Windows APIs & translating them to another set of APIs on the Mac. Something similar occurs with Rosetta2, but with CPU instruction sets. There are so many ways things can break at each point.

People generally buy games to have fun. Is it fun searching forums & the Internet for clues on how to make the game work? Chances are it will break again with the next update to macOS, or the game, or WINE, or the GPU proxy layer. I'm sure some people enjoy the puzzle of getting things to work out, but most do not.

People who want to play games on their M-series Macs should select a game made for an M-series Mac.

If you want to play games, then a Mac is not the best choice of computer to do so. The majority of games are made for Windows and only hacks allow them to possibly run on other systems. If Blizzard cared, then they would make a fully supported Mac version.

It is bad enough you want to run a Windows game on a Mac, but an M-series Mac on top of that. An M-series Mac adds so much more difficulty to running such a game because it requires even more hacks than it does for an Intel Mac. You now have to worry about Rosetta2 and also need an extra hack to deal with the M-series GPU which may allow some games to work, but I understand graphical performance will not be that great for many games.

FYI, in a few years it is expected that Rosetta2 will no longer be available with later major versions of macOS, so the whole Windows gaming on an M-series Mac will no longer be an issue since it won't be possible to do so.

If you want to run Diablo, then play it on a Windows PC or on a game console where it is fully supported by Blizzard. Otherwise you will be trying to fix game issues whenever Blizzard, macOS, or even Codeweavers update their software.

It's not just about the impact on some specific game the OP reported. It's about a bug in Rosetta2. Even though the next version of MacOS coming this fall is likely to have only a partial implementation of Rosetta2 and even though it is eventually going to be fully deprecated, many Mac users will rely on Rosetta2 for quite some years to come. Patching out a bug seems to be a reasonable ask of the developer of Rosetta2, which happens to be Apple itself. There is no reason this specific API call should continue to fail to resolve now that it has been identified and reported to Apple.

It is up to those third-party vendors to fix the problem.

Contact a third-party vendor - Apple Support

My goodness, I better remove that Silicone right away before it damages my Mac!

Apple's own Game Porting Toolkit, on which some of the underlying technology which allows this specific game to run, also relies on Rosetta2.

Would it make you feel better if the report was that this specific Rosetta2 bug was impacting the way a pacemaker application were working? A bug in Rosetta2 is a bug in Rosetta2, it doesn't matter what specific applications are being impacted – it ought to be patched.

You are contributing nothing here and don't even seem to understand why GPTK exists, how it was built on the open-source WINE core, or how it is being used to run Windows applications in MacOS and Linux environments. Maybe not even what a BUG is. So scamper away now back to your hole, Ned.

den.thed wrote:

No, the problem is that you are relying on Rosetta 2 to play Intel based Windows games on a Silicone Mac.

Love it!!! I may use that next time since people don't seem to care about the details. Maybe I'll include a Jenga like graphic to go with it.

It’s a bug in Rosetta2.

No, the problem is that you are relying on Rosetta 2 to play Intel based Windows games on a Silicone Mac.

Yeah’ seems like a good time to move on.