The emphasis is that code was changed for ALL operating systems, and is only affecting the minority one with issues that have a clear way to avoid those issues…This makes it low priority (to any company not just blizzard), especially when the issue is genuinely not in their code but someone else’s.
Imagine you have a room where rearranging the furniture actually made room more optimal. Created more space, made it safer, loads of improvements. unfortunately, by doing so your blind friend who’s but 1 of dozens of people using this space, is now having issues with the new layout. Everyone else has benefited from the new layout, but it’s also really awful for the one person whom has a legitimate complaint and the optics around not addressing it can be really bad when you only focus on it from that view. However, in larger picture the changes make sense. It’s not the fault of person who moved furniture around, who’s goal was for the betterment of most, even if they are directly responsible for change that affected this one person.
Perhaps a terrible metaphor, but the point being the changes were made for a reason and are not reverted for a reason too and also can’t just be hacky fragmented for a reason either since blizzard literally moved away from that on purpose to unify the code base.
That’s pure speculation. It didn’t affect YOUR performance. WoW is used in many different configurations and hardware and changes are not make for sake of changes. It could have been changed to fix a crash with discord overlay, it could have changed because dx11 had issues with it that metal and dx12 did not (examples that have been relevant in past and not saying they are actual reason here). Just because the new code didn’t make things better for you, doesn’t mean it didn’t make things better.
As for reporting it to apple. Blizzard has thoroughly done so already. But apple is apple and they also prioritize the bigger picture, and for them that’s not obscure bugs in windowserver affecting games.
Dude I have a windows PC too. Literally nothing changed. No less power consumption, no better GPU performance. My GPU and CPU are the same temps, have the same % resources used, and use the same amount of power post-code “update”.
There are literally no noticeable benefits to this “unified code update”.
Yep, your PC totally covers all PC hardware. It has a nvidia, amd, intel gpu and runs on dx11 and dx12 at same time and runs on every version of windows at same time.
Blizzard doesn’t make change based soley on you, that’s what you’re not getting I guess.
IMO its a huge problem. If I touch the edge of my window the game crashes. Also apart from complete full screen mode, the biggest window option I have is 3200x1800 which is too small.
Blizzard changed some backend WoW code with 9.2, and now it’s highly unstable in MacOS (and it’s absolutely unusable in Windowed mode). Blizz says “not our fault, it’s a bug with macOS LOL”, even though literally NO other games or even applications bug out like WoW does, which means it’s a WoW-only issue (not a macOS issue). And now they’re refusing to fix this, or revert their code to the version that worked flawlessly.
No, it just means no other apps have made the switch to the “proper” Metal code yet, or at least none that you personally use. Blizzard is usually ahead of the curve when it comes to making changes to be as compatible with Metal as it can be. This time it bit them in the derriere, something that can and does sometimes happen when you’re literally “bleeding edge”. Unfortunately the discovery of the problem came after the codebase change, and reverting wasn’t an option at that point.
At least they pinned down *what* caused this bug, unlike the Diablo 3 FMOD bug that has plagued that game to varying degrees for a year and a half now (and that’s on the Windows side that gets far more frequent updates than do the macOS clients!).
The current issue in this thread has a workaround. Two of them in fact.
Apple will roll out a hopefully final fix, though this will probably require Ventura unless you get a lucky point release before then.
I’m sorry it’s taking as long as it is to get fixed, but maybe if Apple gave a damn about gaming on their platform they’d get that fix out sooner, especially since it affects their shiny new overpriced toys. Apple could have had this fixed with the 12.4 release. They chose not to. But hey, if it’s any consolation, Diablo 3 is unplayable on many Windows systems because Blizzard still hasn’t properly fixed the FMOD bug they introduced 1.5 years ago. That one is at least actually on Blizzard to fix. This one isn’t.
Oh, and that Intel driver bug that Blizzard tried to work around for what is it now, almost four years? Yeah, Apple never fixed that either. Your beef is with Apple, not Blizzard. Go yelp in their ears.
it literally is an option. people revert code all the time. there’s dozens of free and open sourced software reverting tools available, have you ever heard of git???
This wasn’t the only code change made. Reverting wasn’t an option for two reasons. First, other code also relied on this code. The second reason is that 9.2.5 was feature locked and the aforementioned other code was a part of the feature locked code. 9.2.5 wasn’t just a Metal code change, it was an accessibility code change too whic was significant. They cannot revert the code at this point since it was not just a singular change. That’s what you aren’t getting. Blizzard does have a versioning system, but just like everywhere else not all commits can easily or even feasibly be reverted, especially in a game where both the macOS and Windows client must maintain feature parity.
You aren’t going to win this argument. The code is set in stone and needs Apple to put out the fix. That’s one of the downsides of maintaining multiple platforms that require feature parity.
In your case the problem isn’t the game, it’s in the Battle.net app if I’m reading your other thread correctly (the one that good ol’ DonaldTroll from this thread hijacked). Unfortunately that issue isn’t related to this thread’s issue, it’s one caused by a combination of whatever OS version you’re using (presumably Monterey since you said you got a shiny new Mac in the other thread) and whatever the Battle.net app team broke, and believe me, they break that blasted app all the time. And it doesn’t help that the Battle.net app still isn’t M1 native; it runs on Rosetta.
I would try seeking help in the Battle.net Desktop App Mac Tech Support Forum. I won’t lie though - expecting much of a back and forth there from Blizzard probably won’t bear much fruit. There’s a reason they shunted the Diablo: Immortal tech support fora to that particular forum site vs. a game specific one like with WoW, D3, or D2R.
I wish I had better (and easier) news for you on this, but that “catch all” error you’re getting with the Battle.net app just seems to bite users in the rear more and more, and seemingly more on M1 macs than on Intel macs. I’ve been lucky so far, but I suspect my being limited to 10.13.6 may ironically have spared me from much of the bruehaha that later macOS versions have caused ever since Apple went and split the system and data volumes in Catalina.
This has literally nothing to do with Battle.net. It’s the WoW / WoWClassic game client. I open WoW through a shortcut to the application itself. Battle.net isn’t even running on my system when resizing WoW in windowed mode causes the application to freeze+crash.
And I didn’t “hijack” this thread or troll. I’m focusing on the exact issue the topic is named after, and reiterating the needs of hundreds of thousands of customers to Blizzard’s deaf ears.
Blizzard changed something, the game broke, and they’re refusing to fix it. Stop making excuses for them. Even if it is a problem with macOS / Metal API or whatever, Blizzard should NOT have switched to an unstable API / code base.
"