Nothin to do with it. 10.0 added far more verbose logging so the freeze issues could be fixed on beta that affected all macs. That’s why you see a lot more lines. As for why 10.15 is crashing for users, I did pass that on to be looked at.
1 Like
lala: how do you set gfxCardStatus in config.wtf?
do you have any other ideas on how to play with the metal flags? you sound like you have some knowledge on the valid gfxCard variables for config.wtf
You don’t set that in the config.wtf. It’s a third party utility. You can find it here: https://gfx.io/
Disclaimer: This is not software endorsed or provided by Blizzard or Apple. Although it should be genuinely safe as it’s been around for years, use at your own risk.
We had severe issues in beta with freezing and crashing but it was mostly resolved a couple weeks ago.
Haven’t been able to log in to beta in at least a week (real life has limited my WoW time so I’ve been levelling alts and doing Hallow’s Eve stuff in the little time I’ve had).
Logged in today (live game) and, while I’m not crashing, the game is (as someone else mentioned below) just a slide show. Going from SL zones to Dalaran (Legion era) improved slightly but not to the point the game is playable.
2020 27" iMac here, seems to be working fine for me so far no crashes.
10/26 14:18:01.604 LogOpen
10/26 14:18:01.604 World of Warcraft Retail x86_64 10.0.0.46313
10/26 14:18:01.604 macOS 13.0.0 (22A380) x86_64
10/26 14:18:01.604
10/26 14:18:01.604 Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz | Sockets:1 Cores:8 Threads:16
10/26 14:18:01.604 32.0 GB System Memory
10/26 14:18:01.604 On AC Power - Battery Not Present
10/26 14:18:01.610 Adapter 0: "AMD Radeon Pro 5500 XT" family:RDNA type:Discrete vendor:0x1002 device:0x7340 driver(0x0) location:1
10/26 14:18:01.610 Monitor 0 "iMac" Size(2560x1440) Pos(0, 0)
10/26 14:18:01.664 Choosing gpu with monitor attached: "AMD Radeon Pro 5500 XT"
10/26 14:18:03.009 Error Loading Shader: 3186452
10/26 14:18:03.010 NotifyOnDeviceCreate
10/26 14:18:03.011 Metal Legacy Device Create Successful
10/26 14:18:03.011 Using shader family mtl_1_1
10/26 14:18:03.011 <IsGPUDriverOutOfDate> No
10/26 14:18:03.011 Detected Graphics Defaults: 6 (CPU = 7, GPU = 6, MEM = 7) WindowSize: 5120x2880 WorldRenderSize: 2560x1440 (0.5%)
10/26 14:18:03.011 GxLowLatencyMode: None
10/26 14:18:03.095 Render Settings Changed. New Render Size: 2560x1440 (5120x2880 @ 50.0%)
10/26 14:18:04.115 Render Settings Changed
10/26 14:18:13.323 Metal Device Destroy
10/26 14:18:13.323 NotifyOnDeviceDestroy
10/26 14:18:13.334 GxShutdownPosted work around here
6 Likes
Ok based on your response I SOLVED the issue. Fortunately for me I have another another mac that’s working so I copied all the folders and files in the WTF folder and added them to the same directory on my mac that was not working and then booted up the game. Worked like a charm!
If there was a way to attach the files here I would so others could pull from here.
2 Likes
What if your wtf is empty because you reinstalled?
2 Likes
I also have the same issue
2 Likes
omegal
this isn’t a proper fix man. even with the latest patch if i remove this line the game crashes.
the problem with the fix is that i can’t see the login screen at all. the game opens and my screen remains my desktop. i only know wow is running because the taskbar shows Wow. but i have to usually command-tab out, and command-tab back in to see the character screen.
yes it’s better than nothing but i thought the patch to 46340 would have fixed this.
can you please tell them to hurry up?
edit: i also noticed if you try to view the dragonflight cinematic at the character screen (bottom right button) you’ll crash the game.
I’ve got both a 2020 Mac Mini (Intel) and a 2018 Macbook Pro (Intel) and they both run WoW just fine, although the Mini had some REALLY bad stuttering after I upgraded to Ventura. I’ve gotten around that by switching to “Metal (Legacy)” in-game, but I’m not sure what I’m missing as a result.
indent preformatted text by 4 spaces
10/30 09:08:58.369 LogOpen
10/30 09:08:58.369 World of Warcraft Retail x86_64 10.0.0.46366
10/30 09:08:58.369 macOS 13.0.0 (22A380) x86_64
10/30 09:08:58.369
10/30 09:08:58.369 Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz | Sockets:1 Cores:6 Threads:12
10/30 09:08:58.369 32.0 GB System Memory
10/30 09:08:58.369 On AC Power - Battery Not Present
10/30 09:08:58.382 Adapter 0: "AMD Radeon RX Vega 64" family:Vega type:External vendor:0x1002 device:0x687f driver(0x0) location:1
10/30 09:08:58.382 Monitor 0 "Dell S2417DG" Size(2560x1440) Pos(0, 0)
10/30 09:08:58.382 Adapter 1: "Intel(R) UHD Graphics 630" family:Gen9_5 type:Integrated vendor:0x8086 device:0x3e9b driver(0x0) location:0
10/30 09:08:58.382 Monitor 0 "Dell S2417DG" Size(2560x1440) Pos(0, 0)
10/30 09:08:58.481 Choosing gpu by name: "AMD Radeon RX Vega 64"
10/30 09:09:00.125 Error Loading Shader: 3186452
10/30 09:09:00.128 NotifyOnDeviceCreate
10/30 09:09:00.129 Metal Device Create Successful
10/30 09:09:00.129 Using shader family mtl_1_1
10/30 09:09:00.129 <IsGPUDriverOutOfDate> No
10/30 09:09:00.129 Detected Graphics Defaults: 6 (CPU = 7, GPU = 6, MEM = 7) WindowSize: 2560x1440
10/30 09:09:00.129 GxLowLatencyMode: None
10/30 09:09:00.227 Render Settings Changed. New Render Size: 2304x1296 (2560x1440 @ 90.0%)
10/30 09:09:01.801 Render Settings Changed
10/30 09:17:03.015 GxRestart
10/30 09:17:03.015 Metal Device Destroy
10/30 09:17:03.023 NotifyOnDeviceDestroy
10/30 09:17:03.142 Choosing gpu by name: "AMD Radeon RX Vega 64"
10/30 09:17:03.144 NotifyOnDeviceCreate
10/30 09:17:03.144 GxLowLatencyMode: None
10/30 09:17:07.391 Metal Legacy Device Create Successful
10/30 09:17:07.391 Using shader family mtl_1_1
10/30 09:17:07.391 <IsGPUDriverOutOfDate> No
10/30 09:17:07.391 Render Settings Changed
10/30 09:17:41.180 GxRestart
10/30 09:17:41.180 Metal Device Destroy
10/30 09:17:41.188 NotifyOnDeviceDestroy
10/30 09:17:41.287 Choosing gpu by name: "AMD Radeon RX Vega 64"
10/30 09:17:41.289 NotifyOnDeviceCreate
10/30 09:17:41.290 GxLowLatencyMode: None
10/30 09:17:45.201 Metal Device Create Successful
10/30 09:17:45.201 Using shader family mtl_1_1
10/30 09:17:45.201 <IsGPUDriverOutOfDate> No
10/30 09:17:45.201 Render Settings Changed
10/30 09:17:53.684 GxRestart
10/30 09:17:53.684 Metal Device Destroy
10/30 09:17:53.684 NotifyOnDeviceDestroy
10/30 09:17:53.765 Choosing gpu by name: "AMD Radeon RX Vega 64"
10/30 09:17:53.767 NotifyOnDeviceCreate
10/30 09:17:53.767 GxLowLatencyMode: None
10/30 09:17:58.122 Metal Legacy Device Create Successful
10/30 09:17:58.122 Using shader family mtl_1_1
10/30 09:17:58.122 <IsGPUDriverOutOfDate> No
10/30 09:17:58.122 Render Settings Changed
10/30 09:39:58.060 Metal Device Destroy
10/30 09:39:58.060 NotifyOnDeviceDestroy
10/30 09:39:58.287 GxShutdown
[GryphonMD]
It’s working again on 2012 Intel Mac Mini, plated for a few hours last night for the first time in 15 years
What?
I am using a 2.9GHz MacBook Pro 15.4 inch from 2017 with 16GB of Ram
I run on macOS 11.5 (Big Sur) and it works just as well as it did in 9.2.5
I usually run the game around 30-50FPS depending on the content I’ll limit it to what it can handle and I run it at low quality settings.
For you to think people have to be lying just because they have a game running on their macs is wrong of you, maybe some people are just liars of course (trolls etc) but not everyone is trying to mess with you. Computers are finicky and you and I could have the exact same computers and mine might just work better and or not have issues.
Even if the specs are equal they’re not really equal. No two things are the same. Anyways… I’m sorry that you’re unable to play friend ):
a 2017 macbook pro would have avoided the AVX2 cinematic crash, and because you cap fps, you avoid the memory leak too. You dodged two bullets Bairon 
1 Like
What’s the AVX2 cinematic crash? I just skipped that cinematic since I’ll watch it when DF actually releases.
intel cpus that didn’t have AVX2 instruction set would crash when any cinematic started (it was finally fixed lasts night btw). any machine that had AVX2 worked fine for cinematics at least.
I’m on a 2019 iMac i7 with 32gigs of ram. I"m not crashing, but i’m having issues with horrible framerate drops while playing. I’m going to re-install the Old OS because the game play is so terrible.
this “fix” is really not one at all. it’s the same thing you told us to do. i still see my desktop for a while before i get to the character loading screen.
i’m better served tabbing out and going back to the game. why is this so hard to fix? i cannot believe this is over a video. it used to be you played it once and then it never showed up again. now it’s screwed up the boot sequence of a game
the question is still valid as to why avx2 became compulsory for this expansion pack.
the only thing that’s changed in the APPULL (say it with both cheeks full) landscape is the introduction of the small-brain processors, though i read support came just in time for shadowlands.
makes zero sense to use avx2 for cinematics when the previous approach was working fine.
plus, is the game distinguishing between M1s and intels for video? because we know the M1s don’t have AVX. why add avx for intel processors when they didn’t needi t?
thanks, pro.
you came to this thread nearly a week late and you’re showing your pro skills with your amazing insight.
people are liars, and the real problem is still a strange one.
why enable AVX on this expansion pack for intel macs when M1s don’t have AVX support at all?
i am thinking it’s just a big cover because the peabrains need to feel good about spending 2000 dollars on a mobile phone in a big piece of metal.
Why are you still arguing about this? It was already turned off and it was a compiler bug, NOT intentional. Its not like a designer went to work and was like “how do I F over intel users today? I know i’m gonna enable AVX2”
The reason why M1 wasn’t affected is because the arm compiler would never flip on AVX2 since arm cpus don’t support AVX2. even if flipped enabled it’d go “-arm? ok no AVX2”. Same compiler, same setting.
A lot of build process is automated and one of the flags in compiler was flipped to on (which tells it to compile AVX2 instruction automatically were possible) and that’s all there is to it. It was caught right away but due to nature of pushing out fixes, it had to go into a hotfix branch with many other fixes and go through like 3 days of QA before released. there is no conspiracy here, move on from it.
i think you’re misinterpreting my position. i am not saying blizzard is doing it on purpose to spite intel users. rather i think blizzard is trying to cater to the “new guys” aka M1s, and sometimes will make mistake at the expense of intel users.
the conspiracy is only on apple, whose CEO lacks a brain and decided selling devices with mobile processors with outrageous profit margins (i bet these boards cost no more than 2-300 dollars to produce–TOPS) was a priority.
i can’t wait to see PCI-E standards on ARM rofl. it’s going to be the funniest thing on the planet.
i wish the PPC and ARM eras were comparable, but they are so different that any reference to the former for the latter is inadmissible.