sunrun.4521

Thank you! =) Finally some communication and confirmation that the issue is going to be fixed! PRAISE JOKO!

The alternative with Guild Wars 2 on macOS Catalina is not being able to play at all, though.

World of Warcraft? :p Not only does it use Metal but the developers actually reply with Mac-related updates on their forum, too.

They didn't announce anything regarding the Mac client during the recent event. With the release of macOS Catalina just a few weeks away and no response from ArenaNet in this thread since last year (... by a staff member who's no longer with them), it's looking increasingly like they've abandoned their Mac players. I submitted a bug report but they said "we cannot comment as to if and when a fix will be implemented to any 32-bit components for the game client".

Anyone want to start taking bets about whether this gets fixed for the release of Catalina? B) I'm going to guess it doesn't and we're all going to be screwed.

I'm interested in this too, but it looks like we won't get a reply. We're now just one week away from WWDC and Apple releasing the first dev beta of the next version of macOS, which GW2 presumably won't run on unless ArenaNet fixes this. At the very least, they need to fix it in the next three months or there are going to be a lot of people who upgrade to macOS and then find GW2 no longer runs. Hopefully Apple doesn't also take the opportunity to change OpenGL from deprecated to removed in the next version, or the 64-bit issue will be the least of our worries (it does seem more likely that OpenGL will be available for a little while longer, but we'll find out soon enough...).

Yep, same problem, I've given up on the Firecracker Lighting adventures because of this - constant crashes, usually near the beginning, or as soon as you hit the last firecracker, which is particularly demoralising. Speaking of New Year content, good luck playing Dragon Ball. There's so much stuttering and hitching that it's unplayable (one of the main complaints in general about the Mac client which still hasn't been addressed after all this time). I guess Mac players just aren't a priority, so it's rubbish performance until OpenGL goes from deprecated to removed, then it'll be adiós anyway.

I'm getting the compatibility warning on Mojave with the 64-bit version as well, so presumably some components of it must still be 32-bit.

Just reporting back to say the performance is still garbage. SO. MUCH. STUTTERING. omg.

Just a quick note that GW2 runs fine on Mojave for me (late 2016 15" MBP w/TB, Radeon Pro 460). I seemed to be getting a few extra fps where my character was left compared to when I last logged in, but that might just be differences in players. Still as janky/hitchy as ever when rotating the camera/whenever it loads new assets though. (note re Apple marking OpenGL as "deprecated" - it just means they intend to remove it in some future version of macOS; "deprecated" is different to "removed") Edit: Forgot to mention that the Touch Bar controls are now back for me as of a recent GW2 update.

The Touch Bar controls are still completely missing for me...

I'd love to know if this is going to be fixed, because it seems like it would be negatively impacting performance: Your Umbra Occlusion Booster evaluation license has expired. Pleasecontact sales@umbrasoftware.com to obtain a valid license or toextend your evaluation period. In case of techical problems pleasecontact support@umbrasoftware.com.Applications using an expired evaluation version of Umbra OcclusionBooster will execute but view frustum and occlusion culling will bedisabled.If you have a valid evaluation key, supply it as a parameter toUmbra31::Library::setEvaluationKey().

The GW2 Mac team better get cracking. While OpenGL will work in Mojave, and may also work in next year's version as well (they haven't actually specified when OpenGL will be changed from "deprecated" to "removed"), the path is now clear: move to Metal or your game stops working.

The jerkiness/hitching is the main problem for me as well. If you don't move, it settles down and fps goes back up to normal/decent levels, but start moving/rotating the view and it seems that any time it has to load an object or texture it pauses while it does it (even with an SSD). If you're in a high player environment it's especially bad as, I assume, that means more objects for it to need to be loading. Specs:High Sierra 10.13.42.6GHz Intel Core i716GB 2133 MHz LPDDR3AMD Radeon Pro 460

Has the hitching/jerkiness improved for anyone? It's still just as bad as ever for me. Starting to move anywhere or rotating the camera results in hitches that sometimes last two seconds, so an FPS of less than 1.

Yep, that's my experience on a high end MacBook Pro as well. It seems to do some main-thread-blocking texture/model loading or shader compilation that results in the entire game freezing for as short as a split second, but sometimes as long as up to several seconds. It makes for a very bad experience (sometimes unplayable for things like jumping puzzles, especially when other players are around) and is my number one complaint with the current state of the game. It's nice to see they're making progress on other issues but this one should be a high priority.

The hitching is making me want to not play this game any more. Just try doing a jumping puzzle when the game pauses for sometimes an entire second or more during the middle of jumps because other players come into view... Today's daily included King Jalis's Refuge jumping puzzle and Sanctum Sprint. Is this some kind of punishment for Mac players? If this was on Windows, people would be howling in protest at how atrociously stuttery and hitchy the game is. I guess I was stupid to believe that this many months after release this problem might have been given the attention it needs. I guess I should consider myself lucky that I don't have the incredibly long load times that other people are experiencing. It's funny that the GW2 site says "The Mac version of Guild Wars 2 runs well on" ... "MacBook Pro 13", 15", 17" (Mid-2012)", yet I'm experiencing these performance issues on a top of the line MacBook Pro 15" (TB, Late-2016) with the best available GPU.

Thanks for the update Jon. The shader hitching recently seems to have become much worse than it's ever been for me (on latest High Sierra on a MBP with Radeon Pro 460), so it's nice to know this stuff is still being looked at. It used to be some hitching at first and then things would mostly settle down, but now it's much more frequent and the hitches are longer pauses.

I really wish there'd be some improvements to the "hitching"... it's making the game so jerky when new models/shaders/whatever are loaded/compiled. It seems much worse now than it was previously.

Hi all, I wanted to provide an update on this High Sierra bug, where letting a 2016/2017 MacBook Pro go to sleep was destroying graphics performance. After being on the beta releases for a while now, it appears this bug has finally been fixed as of macOS 10.13.3. beta 3! So if you have a 2016/2017 MacBook Pro with Radeon GPU and have been experiencing terrible GW2 performance that's temporarily fixed by a restart, it looks like relief from the issue will be on the way in the public release of macOS 10.13.3. As an aside, I've noticed increased "hitching" in the game as of a recent update, which appears to be something lots of other people are experiencing as well and which doesn't look like it's related to this High Sierra issue.

Yep, same, but only after my MacBook Pro has been asleep long enough to enter standby. I'd love it if the GW2 devs could weigh in on this - is this behaviour they're seeing on 2016/2017 MacBook Pros with Radeon GPUs? If so, if they have any clues about the specific cause I'd love to add them to my open radar with Apple about it. A restart fixes the performance until it's allowed to do a longer sleep again, and the issue persists in macOS 10.13.2 beta 2.

I don't think GW2 can override those shortcuts, because Control + Arrow Keys are system keyboard shortcuts for moving between Spaces (left and right), Mission Control (up) and Application Windows (down). If you never use them you can turn them off via System Preferences -> Keyboards -> Shortcuts.

Updated today, Mac client crashed immediately after trying to go into a map. Restarted the client, it said it had to repair the data archive, so I let it do that and when it looked like it was finished GW2 crashed and brought up the bug report window, which I couldn't do anything with because it was beach balling as well. GW2 was sitting there consuming 68% of CPU until I killed it. Thankfully it seemed to be OK the next time I ran it... yikes.

If you're on High Sierra, there's a bug where after a sleep long enough to enter standby mode, Metal and OpenGL performance are terrible. Restarting fixes it and doubles the frame rate (this is something impacting all games, not just GW2).

I usually only ever sleep mine as well (until now!). I've only ever closed the lid without GW2 running, and it happens in that situation (maybe I should try letting it sleep while GW2 is running and see if it doesn't happen).