Anyone else having issues with the TBC Classic 2.5.3 client crashing their Macbook Pro when launching the game?
Sometimes the game fails to launch and gives this code:
CommandLine Parse Error: psn_0_69649(0): Invalid argument: psn_0_69649
Sometimes launching the game just outright causes my Mac to crash and reboot.
MacBook Pro (16-inch, 2019)
MAC OS Catalina
version 10.15.7 (19H1615)
2.6 GHz 6-Core Intel Core i7
6 GB 2667 MHz DDR4
AMD Radeon Pro 5300M 4 GB
Intel UHD Graphics 630 1536 MB
Since this mornings update, launching the game from both the battle.net client and the wow app directly causes my entire system to freeze requiring a hard reset. I have not had any issues with TBC before this mornings update.
Deleting and reinstalling the game does not fix the problem.
Specs:
2019 Macbook Pro 16 - Catalina
2.4 GHz 8-Core Intel Core i9
32gb ram
AMD Radeon Pro 5500M
I had the same issue, and adding the line mentioned in PSA: SET gxAdapter issue allowed Burning Crusade Classic to finally start successfully. This of course means you are playing with the lesser graphics card, so just a temporary fix.
I have the very same, 16 inch 2019, AMD Radeon Pro 5600M / Intel UHD Graphics 630, Catalina. What does your Logs/gx.log say? It should indicate which card it is picking via a line something like
Choosing gpu by name: “Intel(R) UHD Graphics 630”
Edit: I just realized my card number is slightly different, so not exactly the same.
This is a WoW log file; if you are on the battle.net launcher, with Burning Crusade Classic selected in the lower left drop down, click the [Gear Icon next to Play] > [Reveal in Finder] to bring up Burning Crusade Classic’s installation directory. There should be a Logs folder in there, and then a gx.log file inside of that folder.
Update, working for me now with the intel graphics, I didn’t notice the note about retyping the quotes when copying and pasting from the forum. FPS kinda sucks with the integrated graphics though.
I found it odd that so many reports have come in for this since the update today. It seems the AMD Radeon Pro 5500M is a common factor here yet I’m not sure if that’s true for everyone posting here. Typically a full system crash or restart is outside what we’d have much to assist with, yet based on these reports I’ve poked the developers and will update back if I hear anything.
In the mean time, can anyone who’s affected by this reply with their OS version and their GPU in the system?
To add to this though, I have been playing Burning Crusade Classic on this same system for weeks now with no issue. It was only this morning when I went to start Burning Crusade Classic that this issue started happening. Retail still works fine, even using the AMD card.
Edit: So pretty much yea, what you said seems to be the case (except that I have 5600M).
I was having this same problem and so I updated to Monterey from Catalina and now I can at least launch the client. I have a different problem now which is that all water appears discolored though.
MacBook Pro (16-inch, 2019)
Graphics AMD Radeon Pro 5500M 8 GB
OSX Catalina → Monterey
