Blizzard has finally ironed down exact cause of apples bug. It’s a bug specific in apples api NSWindow::contentAspectRatio
Again, I have to emphasize that blizzard isn’t using api incorrectly, it’s behaving incorrectly under right conditions. None the less, because blizzard knows exactly what’s broken in apples code, they’ve come up with a work around in an upcoming 10.0.7 PTR build that works around bug by sort of resetting or “cleansing” the broken state with another api call before calling contentAspectRatio
I’m sure our favorite forum troll won’t be able to comprehend this as an apple bug and think it’s blizzard fixing their own bug cause “no other application does this” but I think any intelligent person and developer will understand sometimes software devs have to work around OS/driver bugs and it can take ages to even find the cause (cause it’s hard to debug code that’s not your own, all you’re doing is accessing an api and expecting it to work way it’s documented).
probably eventually but classic syncs usually take til a major content update so classic era possibly never or next season of mastery if they do another, and wrath classic, maybe for trial of crusade or ICC
A full year later and this issue still isn’t fixed. I read about them discovering the issue and that’s good to know. I wonder why Blizzard can’t use their leverage as a large company and lean into Apple (yes I know, a much huger company) and request/demand a fix on this asap, if it is proven Apple’s code is the source of the issue. I can understand Blizzard saying “F this” with Apple support and drop it moving forward with their games. I don’t like it, but I understand it. Apple sucks. And I’m an avid Apple Product user, but not for much more. If Blizz stops supporting mac for wow, Im literally done with Apple products. In fact, I just bought a new top of the line Windows PC for Gaming so I’m halfway out the door already. F Apple.
It actually is an apple bug, it was literally thorough explained to me, and forwarded to apple, But in 2 weeks you won’t have to worry about it anymore, cause it has a work around.
You lack any fundamental understanding of development though. A specific metal api can be broken, and only be used by one application. In fact WoW is near cutting edge when it comes to metal api usage. Most games on macOS don’t even use metal at all and ones that do use lower versions of it and older apis.
Pretty much only exception to this is resident evil village and no mans sky cause apple paid them to use modern apis, but even then they didn’t use the one that causes the window hang cause those games didn’t rely nearly as much on switching between fixed and unfixed resolutions, while scaling, which is where the issue is. If you call unlock fixed scaling and then call lock again after, it’d freeze. Basically the freeze was caused by unlocking the window while dragging then locking it after and when it’d re-lock it’d freeze cause the api was broken to do so. The work around is kinda hacky but works by flushing the errored variables before re-locking.
It’s really not a hard concept to understand how an apple bug LOOKS like it’s blizzards fault, because they are only ones using the broken API in question.
i just tested the PTR 10.1 and it is working ! WOW! It can resize now ! Amazing
On a side note , in PTR from previous M+ testing - all ground effect spells cannot be casted - you will be lucky to find a place in valdraken to be able to cast healing rain or rain of fire, and suprise; surprise this is now present in 10.0.7.49267 after today client update.
Any idea what is changed and why this is present - it impacts only MACOS - both my macs clients have the issue, and my windows game client have no problems.
I just noticed after i read previous post of you that live gave can be resized now as well - and i have no problems to resize my screen in 10.0.7.49267 - and i start thinking that fix of resizing is now causing ground effect spells to be bugged.
So if NSWindow::contentAspectRatio is what is broken, when did it break? That’s an ancient call – dates back to Panther (10.3) – so I doubt it’s been broken since 2003 and we’re just now hitting it.
So the bug is with NSWindow::contentAspectRatio, the default is 0, meaning not aspect ratio restricted
If you set contentAspectRatio to something else and then back to 0, the window gets into a broken state where resizing will cause it to crash
It’s like setting it to 0 doesn’t fix up the internal state correctly
The workaround to bug:
setting NSWindow::contentResizeIncrements to 0 as well, when setting contentAspectRatio to 0
The theory is that setting contentAspectRatio to non-zero internally uses contentResizeIncrements but then setting it back to 0 doesn’t undo what it did
regardless, 10.1 does the work around and avoids issue.
Why it broke specifically in the 9.x patch is probably related to changing how window code works, which again was NOT A BUG despite what some trolls say. Just that different window code behaves differently using same api it’s always used, which meant tracking down issue literally took a LONG time, especially since it was a bug in such an old function, as you said.
Wondering when/if this fix will apply to Wow Classic and WotLK Classic. I noticed last night the window resizing working on my M1 iMac, but not on my M1 Mac Mini. Both are using MacOS Ventura 13.4.1.
wrath didn’t get fix with the rebase in argent tournament update? if not then I wouldn’t expect it to ICC update sadly. they tend to rebase client only for major patches.
Classic era rebased client for hardcore PTR, so see if fixed there maybe. if it is, you can expect fix whenever that goes live (the client, even if you don’t play HC)
Classic only syncs with retail (and any fixes it gets) on new content phases, not at random intervals. There is no need for hyperbole. Content phases are only about 6 months apart for wrath and classic era is getting a new one soon.
If the code change is based on 10.x code, and the classic client is not based on 10.x but 9.x, then yes. Classic only rebases the client to latest retail client once in a while. It’s really quite simple. Classic client specifically remains code locked while it’s in a season outside of most critical issues. This isn’t one of them
I swear, Blizzard could literally eat babies and Omegal would be like “well you see Blizzard has to eat babies because blah blah blah so they really have no choice it’s the only logical option”
I just know the difference between an issue that’s actually a bug in apples OS that does have work around now but for a specific version of game client. and one that’s squarely blizzards fault (like the sheer incompetence around battle.net launcher the last few months). Heck I uninstalled mac version of Diablo 3 and installed windows version in wine cause mac version was completely unpatchable. i figured I’m playing diablo 2 and 4 in game porting tookit, why not 3 as well.
