fps drop with patch

#1 - Feb. 4, 2014, 3:27 p.m.
Blizzard Post

am running on average 20 FPS lower across the board. WvW zergs now drop my fps to an unplayable level (4-6fps). Before patch everything was running fine.

Mac OS X 10.9.1
3.5 i7
8gb Ram
GTX 780m 4gb

So sad that every update seems to bring more problems than fixes. Especially for mac users.

#76 - Feb. 6, 2014, 7:34 p.m.
Blizzard Post

Hey folks. Just an update to let you know the devs definitely are aware of this issue and are working on a fix for it. As always, we don’t have an exact timeframe — ~official voice:~ “At 10:45 AM Pacific time on blah-de-blah date things will be better!” — but we thought it would be good for you to know the team is on the case!

I will now go post in the Bugs and TS Forums, so that folks there know this modest update. But this really is an OK place to post this issue in this forum. If we do not post a lot in this forum, the issues are reviewed and they are worked on, too.

Thanks again.

#88 - Feb. 7, 2014, 2:05 p.m.
Blizzard Post

Thanks for the update, Gaile. If you can’t fix this in the next couple of days, wouldn’t it be good to roll back the changes so you could fix them at your leisure? Right now, mac users cannot participate in any of the group stuff for living story. It would not be nice to have to miss all the events (current and future) because it takes a long time to fix things. Then, after you have fixed the issues and tested it (even on the mac client which obviously wasn’t in the QA process for this patch), you can roll it back out.

As to why people post in multiple places, you answered that yourself- silence. Perception is reality and people perceive that the company does not care about the mac beta client. Just look at the ‘is the mac client feasible’ post: a person comes here and says she is concerned about buying a mac because she knows that the mac beta client is no longer officially supported. That’s how people see it. However, this could be easily fixed by communicating more if there really is work on the client. If there is not, then communicating about that would be equally helpful.

I can assure you that the company truly does care about Mac players. Devs are working on Mac issues, not casually, but with genuine purpose. You’ll see this in the future, but please be assured that Mac is on the team’s radar and an important part of future updates and fixes.

#159 - Feb. 12, 2014, 6:01 p.m.
Blizzard Post

Just so you know, I don’t dip in here to do a meaningless “feel good” post and then disappear, considering that’s the end of the matter. As I have said — and I do wish we were in a position to speak in more detail, but that’s not possible quite yet — being relatively quiet does not mean the team is inactive on the Mac issues that concern you. Quite the contrary.

Edit: I had asked for player updates about this situation, but got one from the devs, instead. So no need to post about the FPS situation after all. Please see note two posts below for good news!

#161 - Feb. 12, 2014, 7:23 p.m.
Blizzard Post

Ok, here’s a new update to the update:

The devs have developed a fix that should address certain performance issues you have been posting about, and that fix will be rolled out after testing is completed.

That’s not months from now, by the way. Testing is underway!

#171 - Feb. 13, 2014, 12:01 a.m.
Blizzard Post

~snip~
Please ArenaNet please make this a usable game for us

Hear you loud and clear. It’s great there’s a fix on the way. And we know that you guys will update us on how it works for you. I’m impressed with the Mac GW 2 community and know that, even when a situation is heated, you guys come through with valuable information that helps us a ton.

Thank you for the update, Gaile!

Please relay our appreciation to the Devs for their work on this issue.

I will do that. They sit near me, and it’s nice to see them busy at work on stuff that you guys want and need.

+1 wins for Gaile.
- Gaile is awarded with cookie -

~Passes cookie to devs who are working on the fix. (Snatches a small nibble first because, after all, it IS a cookie.

#180 - Feb. 13, 2014, 2:27 p.m.
Blizzard Post

Hey guys — Just a few things:

  • We don’t have a “PC Team” and a “Mac Team.” So it’s not possible to give you names of people working on the Mac improvements. Basically, development is handled by the team as a whole, with several people picking up or providing input on various parts of a particular project. If we can flag names in the future, we’ll do it.
  • I’m not a technical support person, per se. Ashley and others on that team are more conversant with tech issues, and yes, you will see them around — they’re great!
  • Just to clarify, I don’t focus on Windows or PC; I do my bit for any player. (Well, there was the guy who wanted to use Unbutu and I had to let him down gently. )
  • Someone asked that we pass along a word of thanks to those working on the Mac updates and it was a pleasure to share that message. Thanks for your thoughtfulness.
  • All Mac improvements have and will have a thorough QA pass. If something creeps up after release, there can be a dozen different reasons why that happened. But testing is done and with every issue, we learn things that help us prevent future issues. (Nothing will ever be flawless, but each fix is both a fix and an education, if that makes sense.)
  • Progress continues on the FPS issue and more is coming in the future.
#187 - Feb. 13, 2014, 7:39 p.m.
Blizzard Post
  • We don’t have a “PC Team” and a “Mac Team.”

That certainly explains the absurdly low priority level we’re given. I mean we all knew it but seeing it stated in an official capacity stings a bit. It also explains why the mac client isn’t tested after each patch/build independently, if it was this current bug that dropped people from 40fps down to 8fps wouldn’t have gone live I’d hope.

Either way I’m still happy to know that the devs recognize we still exist at least in some capacity and things are being done to right this wrong.

Please don’t read that the wrong way. That means we don’t have a team for each discipline, but that anyone on our team may work on either. This is a good thing, as far as I can see.

Just wanted to post some findings here that I stumbled onto tonight.

I was having issues with safari mac os x 10.9.1 and completely not to do with guild wars but pages weren’t loading or were loading very slow. I did some digging and stumbled across some info about changing the DNS to Googles open DNS servers.

https://developers.google.com/speed/public-dns/

link explains more.

Long story short I set up my router and mac and phone and wives phone with that specific DNS of 8.8.8.8 and did a speed test at speedtest.net I usually get around 60ms ping and it returned a ping of 16ms. I then wondered how fast other things such as youtube and other locations loaded and they are blazing now. So I delve a bit deeper wondering how this would impact my Guild Wars 2 Game play and I am sitting at around 50 fps now and have amazingly noticeable speed increases in load times as well. So hope this helps anyone that wants to give it a go.

Wow, impressive! Thank you for sharing this information.

#260 - Feb. 20, 2014, 6:06 p.m.
Blizzard Post

We’re glad that most of you have noticed performance improvements following the Mac fixes that were part of the February 18th update. Rest assured, team members are continuing to work on Mac!

We forgot to include a note about this work in the update notes and we apologize for that lapse. The FPS changes were an official part of the build, not a happy accident or a stealth update. (Just in case you were wondering. ) We should have included a call-out about it in the notes and in the future, we’ll do our best to outline Mac improvements in the Update Notes to keep you better informed of the progress that the team is making.

#291 - March 11, 2014, 7:51 p.m.
Blizzard Post

I was just made aware of this thread, and I’m sorry we didn’t post sooner!

Can you please create a NEW thread, and post your issues? If you use this sort of title — FPS Issues after March 4 Build — it will be easier for us to sort out who is experiencing this issue, and more tidy to answer the newest set of issues.

I will ask if we can look into this, but a separate thread would help so much!

Thank you.