In reply to Ebren:
Separate FPS issue since the Oct 1 update: on my M4 Air, gx.log shows the GPU as family:Unknown and the client falls back to mtl_1_1 shaders (~24 ms GPU/frame on lowest settings). If you’re seeing an FPS drop too, check your gx.log and add it here: [Mac] FPS regression since Oct 1: M4 GPU family:Unknown, client falls back to mtl_1_1 shaders Your gx.log is in World of Warcraft/classic_beta/Logs/. Look for the line starting with “Using shader family.” EDIT: Note for @Rommax: the 70205 improvement
The logs mentioning mtl_1_1 is fortunately (unfortunately?) a misnomer and non-issue. mtl_1_1 is the name for the only set of mac/metal shaders the game has and is way newer than the name implies. I think every shader is at least targeting mtl_2_3 if I remember correctly. It’s a relic of me picking a bad name when metal came out. I would have picked a more generic name if I realized Apple would bump up the version every year.
Unknown being mentioned in logs for the Apple GPU family is also a non-issue. There’s no code to emit Apple family names in any case. It’s all just info for making sense of crash logs and doesn’t affect any meaningful decisions. It’s not as important for Apple GPUs since their naming convention is consistent (M1, M2, M3 etc). It’s more helpful for stuff like when you have an “AMD Radeon 7800 XT” and you’re trying to remember if that’s an RDNA 1, 2 or 3 family card?
That all being said, I can try to do a pass to make the log output less confusing.
Both of those issues seen in the logs should be unrelated to the performance issues you’re reporting (which I can look into).