Okay to Update?

Hello Friends-

With the new macOS release imminent, I was wondering what the general rule of thumb would be to updating right away. This will be my first go around playing with mac as my primary platform and just wondered from those on the RC if we are good to go with dragon flight pre patch right on its heels.

that’s why i’m testing the release candidate now. I didn’t want to install a new macOS 1 day before 10.0 to find out new macOS was broken.

So far so good though. I tested RC1 yesterday and RC2 came out today and testing that now.

1 Like

Awesome- looking forward to hearing your findings. You’re doing the good work my friend!

Yeah WoW works fine on Ventura but be aware if you use third party stuff for your mouse like I do (Logitech GHUB) there are issues with it still. For me when playing sometimes the docks appears for no reason and previous had issues with the extra buttons on my G502, not sure if that is Apple or Logitech but there can be issues like that.

doesn’t surprise me Epoeu, one thing that’s buggy me about Ventura is that the start application hidden feature isn’t even working. Means if you have apps that are supposed to start in background when you boot, they’ll actually pop right open instead.

So things appearing that aren’t supposed to is just a Ventura feature :smiley:

I’ve been using Macs since 1987.
You can pretty much guarantee that the new MacOS will have problems. I usually wait about a month before updating.

1 Like

You can use a feature Rommax put in for players like myself that will keep WoW in focus and prevent the Dock from ever popping up. This mode simulates the focus locking effect of exclusive fullscreen mode, but without actually being EFS mode as Metal does not have such a mode just like DirectX 12 does not.

To enable this feature you can add the following line into your config.wtf file:

SET ExclusiveWindowMode "1"

This will also disable CMD-TAB and CMD-H while WoW is focused, so be aware of that. CMD-M does still work, but will take a moment (about five seconds) to switch between fullscreen and windowed modes when this feature is enabled. To disable this feature, simply change the 1 to a 0 in the config.wtf file’s CVAR line or delete the line entirely and save the file.

Hopefully this remains working for those that are able to continue using the DF client come pre-patch. Sadly I’ll be schlepping over to the Windows side to set up WoW’s internal controller support due to the hardware combination I’m on preventing me from moving on from 10.13.6 just yet (thanks Apple and nVidia). But at least you’ll have a way to prevent the Dock from interfering anymore.

2 Likes

Cool, thank you going to try it out.
It might be also the LGHub and the macro’s I am making, I had that issue back on Windows when I made macro’s and combining them triggered all other things haha.

Hi Tia-
This edit to the config file didn’t seem to take for me. I’m getting the dock popping up randomly every few minutes, which causes my mouse settings to freak out for a bit. Any ideas?

Yay for this thread!

Oh crap, I wonder if MySQL will survive the upgrade.

The version released today is same as RC2, so i’ve been running it for days safely without any issues in wrath classic or retail or in beta (so assume pre patch should be fine too)

1 Like

With that setting in the config.wtf file, are you able to use CMD-TAB while in the game? You can test it at the login screen by manually launching the game client. If CMD-TAB only switches the cursor from the password field to the email field and vice versa, it’s working properly and something else broke in the client. If CMD-TAB is working and switches out of the app, you did not enter it correctly into the config.wtf file. It is case sensitive and must have no spaces before or after the ends of the CVAR line.

It may be something else in the client. I copy/pasted that edit directly into classic and retail at the very end.

The one thing I need to add to this is that I’m playing on an external monitor. Does that change the variables I need to add to the config file?

It’s possible. I can’t rule that out as I don’t have a way to test against that scenario. In your config.wtf file is there a line with the following CVAR?

SET gxMonitor

If there is none, you may try specifically setting it to the following:

SET gxMonitor "1"

This will force WoW onto the external monitor regardless of whether or not the display is mirrored or is used as an extended desktop. A setting of “0” (zero) forces the game to use the primary/internal display. Perhaps forcing the use of the external with this CVAR will prevent it from interacting with the internal display that would normally house the Dock.

Thanks for the idea. When I’m back from my work trip this week I’ll give it a shot and report back. Appreciate it!

Tried it and it’s working though LGHub was now crashing in the background so it’s the Logitech software. Anyways it seems now the specials keys are actually seen in WoW while this was not some releases ago so I’m using the onboard mem config for the Logitech thus not having to run the software. Now I am Intel-Rosetta software free!

Thanks this made me search further!
Oh yeah if you use the ExclusiveWindowMode be sure to also disable CMD-H as in my case I would just get a blank screen and only option then was to hard reboot my Mac.

I’m playing on an intel-based iMac 2019. I upgraded yesterday and regret it. I’m getting horrible framerates. I had no issues before, in dalaran I’m getting about 10fps. When I engage in combat, my frames will instantly go from 60 down to 10-20. If I can’t figure it out, I’m going to wipe my mac and re-install Monterey.

Yeah, I’m changing my recomendation from yes to no for safe to upgrade.

So far ventura seems to introduce 3 bugs (that we know of) to wow

  1. memory leak when using 2 or more spaces/screens, accelerated massively by uncapped fps (foreground fps cap turned off) (EDIT, this one is not ventura specific)
  2. UI flickering in wrath classic when clicking and using full screen mode.
  3. vsync using incorrect refresh rate on freesync screens (often lower) and hitching with tripple buffering.

i tested Ventura for a week prior to release specifically to avoid giving bad recommendation. I was supposed to catch these issues but didn’t :\

I didn’t play wrath classic in full screen mode (only happens in full screen). I didn’t trigger memory leak cause I had capped foreground fps. i didn’t notice vsync issues cause I turned freesync off

I managed to avoid all 3 issues by accidentally using the right work around for all 3 of them as my norm.

1 Like

Since I sadly updated before I headed out for work, I’m kinda stuck.

Any settings you’d recommend for me on a 14MBP M1Max 32 core w/64gb ram running on an external monitor to mitigate some of the issues outlined above? Def feeling them in WOTLK and PrePatch.

Omegal would you be able to test for me please if Starcraft 2 can run well? (Even if it’s lower settings as long as it’s usually 60FPS) I heard really terrible things about macOS 12.0 and beyond for SC2 and so I haven’t updated since 11.5 or so.

I want to be able to play SC2 so I haven’t updated.