Still not working for me either. I hoped that maintenance this morning would have fixed it. Sad!
Not overly tech savvy here, but what should I be concerned with when upgrading to Ventura? Currently running OS 11.6.8 (Big Sur) on a 2019 MacBook Pro, graphics are AMD Radeon Pro 5300M 4 GB. I seen some comments about a memory leak and metal 3, I’m not sure if those would apply to my setup or not…any input is appreciated!
This has happened before after apparently more major patches on the Mac side. My experience has been that it will take several days for Blizzard to fix, and there’s nothing we users can do but wait. If we’re lucky, we’ll be able to play again on Monday, but I’m not holding my breath. It will take as long as it will take.
2 Likes
Aranolla - I asked the same thing earlier. Someone here said you should be fine if you have AMD Radeon Pro 5000/6000 series. So it sounds like you should be good to go with a 5300.
1 Like
Same for me Irishred! Such craziness! Grrrrrrrrrr
Hey all,
Thanks for all of the information that has been shared in this thread so far. The WoW team continues to work on this crash which only affects specific Macs and specific macOS versions. We do not have any new information to share regarding the technical cause of the crash, but it is still under investigation and being worked on.
As many have discovered upgrading your macOS (if possible) can be a solution for this crash. We generally recommend using the latest version of macOS if you can, since newer macOS versions come with bug fixes and new graphics drivers. Ventura is the latest macOS available, but if your Mac is not able to upgrade to Ventura you may try Monterey.
We will make sure to share any updates we receive from the WoW team.
13 Likes
can’t upgrade mac beyond big sur. game worked perfectly before the patch
13 Likes
Telling us we need newer OS’s and systems when you release a patch that doesn’t meet your own minimum specs is atrocious and quite frankly disrespectful to your users and customers.
23 Likes
I would upgrade if it were possible…I’m not in the financial spot to afford a laptop that can run anything above Big Sur atm, as this one was a gift from my grandparents in 2013 and the last few years have not necessarily been a financial breeze…
3 Likes
Thank you!
What I think Jambrix means is that upgrading is the only currently known solution.
It sounds like they still don’t know what the problem is for the rest of us though and are still trying to figure it out.
At least we have been acknowledged.
5 Likes
Yeah, the last time I upgraded my Mac OS, it literally killed my laptop and I had to take it into Apple to pull important files and photos and they had to factory reset it. Not doing that nonsense again. Please fix this because I’m losing days on my almost ending subscription time.
6 Likes
Any other software company would have rolled back the release and apologized for not putting out appropriate software. This is right up there with Batman: Arkham Knight which was pulled from market.
5 Likes
HOW LONG IS THIS GONNA TAKE, THIS IS UNVELIBABLE. I AM LOSING GAME TIME THAT I AM PAYING LAST TIMW IT WAS MORE THAN A WEEK THAT I COULD NOT PLAY BECAUSE OF THE SAME ISSUE AND I DID NOT RECEIVE ANY COMPENSATION FOR THE GAME TIME LOST FRO YOU.
Plus I am losing the opportunity to complete the achievement that lunar festival holiday has.
7 Likes
Another temporary solution is to try Bootcamp if you can.
I put Windows 11 on an external SSD a couple years ago for Windows only games and I was able to install WoW and play last night. Sucks to have to restart the computer and switch OS, when everything else I do is on Mac, but at least it works for now.
1/26 10:42:26.818 Error Loading Shader: 3186452
1/26 10:42:26.821 NotifyOnDeviceCreate
1/26 10:42:27.052 Invalid: newRenderPipelineState Failed: Error Domain=CompilerError Code=2 “Compiler encountered an internal error” UserInfo={NSLocalizedDescription=Compiler encountered an internal error} (Prism:0x00000000)
1/26 10:42:27.052 Invalid: CreateRenderPipeline failed: VS: 2978021(0) PS: 2977525(0) (Prism:0x00000000)
1/26 10:42:27.052 Metal Legacy Device Create Successful
1/26 10:42:27.052 Using shader family mtl_1_1
1/26 10:42:27.052 No
1/26 10:42:27.052 Detected Graphics Defaults: 2 (CPU = 5, GPU = 2, MEM = 5) WindowSize: 1152x720
1/26 10:42:27.196 Render Settings Changed. New Render Size: 384x240 (1152x720 @ 33.3%)
1/26 10:42:29.128 Render Settings Changed
1/26 10:42:29.130 Device context was lost. Attempting recovery. Occurrence: 1
1/26 10:42:29.149 GxRestart
1/26 10:42:29.149 Metal Device Destroy
1/26 10:42:29.149 NotifyOnDeviceDestroy
1/26 10:42:29.154 Choosing low power gpu: “Intel Iris Graphics”
1/26 10:42:29.161 NotifyOnDeviceCreate
1/26 10:43:07.590 Invalid: newRenderPipelineState Failed: Error Domain=CompilerError Code=2 “Compiler encountered an internal error” UserInfo={NSLocalizedDescription=Compiler encountered an internal error} (Prism:0x00000000)
1/26 10:43:07.590 Invalid: CreateRenderPipeline failed: VS: 2978021(0) PS: 2977525(0) (Prism:0x00000000)
1/26 10:43:07.590 GxLowLatencyMode: None
1/26 10:43:08.272 Crash Summary: ERROR #134 (0x85100086)
from gx log
MacBook Pro (13-inch, Mid 2012)
2.9 GHz Intel Core i7 de dos núcleos
16 GB 1600 MHz DDR3
Intel HD Graphics 4000 1536 MB
macOS Catalina 10.15.7 (19H2026)
Not a solution for me, but I do appreciate the update.
iMac (Retina 5k, 27-inch, late 2014
Processor 3.5 GHz Quad-Core Intel Core i5
Memory 16 GB 1600 MHz DDR3
Graphics AMD Radeon R9 M295X 4 GB
2 Likes
My refurb M1 Mac Mini just arrived. I’ll be in soon. GG Blizzard
3 Likes
Blizzard not sure if this is feasible but how about rolling back the latest patch for us Mac users?
10 Likes