[Main Thread] Crashes on launch after maintenance Jan 24th

I’m already running Monterey and its not working for me.

4 Likes

tick tock its been 2 days… clearly there’s an issue with older hardware/OS that’s not working… as you suggest Monterey/Ventura but that only works for some new laptops, i tried both on my older 2O14 MacBook Pro Retina and it still wouldn’t work…

here’s from my GXlog

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)

Mac is upgraded as high as it will go, and it’s pretty cheeky to introduce a patch (not an expansion) - that, without warning has a caveat of getting a new Mac… for a game, that worked 30secs before the patch was introduced.

15 Likes

Blizz are such crooks, you think we will get anything outta this? Prob not… they already over charge us for an old ancient game that they can’t even update properly. Prob still running the entire servers off some gameboys in the basement.

1 Like

No need to SHOUT :slight_smile:
Shaman are so excitable. we’ll just have to file a Class Action Lawsuit. :money_with_wings:
Actually we probably agreed not to hold Blizz accountable for issues like this, as part of the fine print in the user agreement

2 Likes

It’ll be cute when they stealth modify the minimum OS requirements on their webpage from macOS 10.15 to something in the 12s.

9 Likes

Make/Model of the system: MacBook Pro (Retina, 15-inch, Late 2013)
Processor: 2.3 GHz Quad-Core Intel Core i7
GPU: Intel Iris Pro 1536 MB
OS Version: macOS Big Sur Version 11.7.2

I’m on 12.6.3, still crashing. Ventura is the 13.x.x but it only came out last year.

2 Likes

hey. i’m running monterey 12.3.6. whatever is wrong with world of warcraft has to do with an update mac os had early in the morning before the restart and patch update on tuesday. mac had an update for monterey, idk about the other os. i tried running ptr for retail, and i’m having the same issue. does it have to do with a cinematic that plays at the games intro perhaps? or did blizz really make a game that is not compatible with most of their subscribers computers? i hope it’s not the latter. just letting you know it either had to do with wow’s update, or apples update. did anyone play the ptr with it working? cause i was able to play retail after the mac os update that morning and it worked fine. i hope ya’ll figure it out.

I only ran the Monterey update today, and it was no different than before. It’s also crashing for non Monterey users.

i wonder if it was crashing for mac users in ptr. i think i saw someone in the thread saying it worked for them on macs before 2009, and someone said it worked for them on monterey, so i’m wondering if it was some security update apple did that isn’t working with the patch. idk if ptr was offline, but i did try to play on it a few months or weeks ago and it would just crash. i just figured it was offline.

1 Like

Let me ask you, is the PTR for the next patch already playable? Does it crash? Just want to confirm this, I think someone mentioned it.

i saw that there were two versions of ptr up. the older one has the same issue as current retail concerning mac os.

This worked:
Choose Apple menu > System Preferences, then click Software Update. Install macOS Monterey or Ventura. After downloading, the installer opens automatically.

The gx.log output pretty much points to an issue with Metal support being the culprit here, or at least related, thanks for posting that. Just for comparison’s sake, here’s mine from my iMac (Retina 5K, 27-inch, Late 2014) :

1/26 11:41:05.981  LogOpen
1/26 11:41:05.981  World of Warcraft Retail x86_64 10.0.5.47825
1/26 11:41:05.981  macOS 11.7.3 (1Z141Z3) x86_64
1/26 11:41:05.981  
1/26 11:41:05.981  Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz | Sockets:1 Cores:4 Threads:8
1/26 11:41:05.981  24.0 GB System Memory
1/26 11:41:05.981  On AC Power - Battery Not Present
1/26 11:41:05.985  Adapter 0: "AMD Radeon R9 M295X" family:GCN3 type:Discrete vendor:0x1002 device:0x6938 driver(0x0) location:1
1/26 11:41:05.985  	Monitor 0 "iMac" Size(2560x1440) Pos(0, 0)
1/26 11:41:05.985  	Monitor 1 "SMS27A350H" Size(1920x1080) Pos(2560, 0)
1/26 11:41:06.030  Choosing gpu with monitor attached: "AMD Radeon R9 M295X"
1/26 11:41:06.798  Error Loading Shader: 3186452
1/26 11:41:06.800  NotifyOnDeviceCreate
1/26 11:41:06.879  Invalid: newRenderPipelineState Failed: Error Domain=CompilerError Code=2 "
Linking two modules of different data layouts: '' is '' whereas '1' is 'e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v16:16:16-v24:32:32-v32:32:32-v48:64:64-v64:64:64-v96:128:128-v128:128:128-v192:256:256-v256:256:256-v512:512:512-v1024:1024:1024-n8:16:32'
SC compilation failure
There is a call to an undefined label" UserInfo={NSLocalizedDescription=
Linking two modules of different data layouts: '' is '' whereas '1' is 'e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v16:16:16-v24:32:32-v32:32:32-v48:64:64-v64:64:64-v96:128:128-v128:128:128-v192:256:256-v256:256:256-v512:512:512-v1024:1024:1024-n8:16:32'
SC compilation failure
There is a call to an undefined label} (Prism:0x00000000)
1/26 11:41:06.879  Invalid: CreateRenderPipeline failed:  VS: 2978021(0) PS: 2977525(0) (Prism:0x00000000)
1/26 11:41:06.879  Metal Legacy Device Create Successful
1/26 11:41:06.879  Using shader family mtl_1_1
1/26 11:41:06.879  <IsGPUDriverOutOfDate> No
1/26 11:41:06.879  Detected Graphics Defaults: 3 (CPU = 5, GPU = 3, MEM = 7) WindowSize: 5120x2880 WorldRenderSize: 1920x1080 (0.4%)
1/26 11:41:06.948  Render Settings Changed. New Render Size: 5120x2880
1/26 11:41:07.581  Render Settings Changed
1/26 11:41:07.582  Device context was lost. Attempting recovery. Occurrence: 1
1/26 11:41:07.609  GxRestart
1/26 11:41:07.609  Metal Device Destroy
1/26 11:41:07.609  NotifyOnDeviceDestroy
1/26 11:41:07.686  Crash Summary: ERROR #134 (0x85100086)
3 Likes

Thank you for the updates, Jambrix. I would love to have access to new drivers/graphics but if a fix can’t be done for the minimum 10.15 OS version specified in game specs, do we have recourse like a refund for the game or the 6mos. of game time I bought…?

7 Likes

Thanks for the update, but Just a reminder of Blizzard’s Mac system requirements stated on World of Warcraft purchase page:

Minimum Requirements
Operating System macOS® 10.15
Processor 4 Cores, 2.9 GHz processor (6th Generation Intel® Core™ Skylake or Apple® M1)
Video Metal® capable 3 GB GPU (AMD™ GCN 4th gen or Apple® M1)
Memory 8 GB RAM
Storage Solid State Drive (SSD) 128GB available space
Internet Broadband internet connection
Input Keyboard and mouse required
Resolution 1280x720 minimum display resolution

Recommended Specifications
Operating System macOS® 12 (latest version)
Processor 8 Cores, 3.6 GHz processor (9th Generation Intel® Core™ Coffee Lake or Apple® M1 Max)
Video Metal® capable 8 GB GPU (AMD™ RDNA™ or Apple® M1 Max)
Memory 16 GB RAM
Storage Solid State Drive (SSD) 128GB available space
Internet Broadband internet connection
Input Multi-button mouse with scroll wheel
Resolution 1280x720 minimum display resolution

2 Likes

Theres a lot of users who have MACS older than 2015, and Monterey and Ventura are not supported on the older hardware.

We right now we are pissed there’s no solution or communication on a fix for a game we paid $70+ for and also $15 a month and also the time invested, along with losing in game interaction with our friends.

This is very bad on Blizz’s part to have a Patch not be playable without more communication. IF the patch will not work on Older than 2014 Macs, would we get a refund the cost of buying the expansion along with the Subscription fees players have spent so far?

20 Likes

The germans have gotten some blue posts…

1 Like

Can you send link?

1 Like