The bug that was causing this issue has been found and will be addressed in an upcoming release. We know it's been very unpleasant, and we are sorry it took so long to address it.
The bug that was causing this issue has been found and will be addressed in an upcoming release. We know it's been very unpleasant, and we are sorry it took so long to address it.
The bug that was causing this issue has been found and will be addressed in an upcoming release. We know it's been very unpleasant, and we are sorry it took so long to address it.
It has to do with some new code we introduced using worker threads to take advantage of extra cores. It wasn't playing nice with the AMD FX's. We don't know why that is yet, but we just dialed it back a bit. You should still be getting really great CPU performance from those machines now. Rob
We run the game on GeForce hardware regularly, as well as hardware from other companies. Your issue does not sound the same as the other users in the thread. I've forwarded your information to our graphics lead.
If you guys are going to post "I am still crashing" in this thread, please post an ET number. It will go a long way to helping us figure out what you're running into. We did, in fact, fix a high volume crash, as I explained earlier, but there are lots of reasons people could be having difficulties. Rob
Hello, everyone. As of the patch today, the particular crash that most of you were experiencing in this thread has been resolved. Thank you for your patience. Of course, some of you may still experience other crashes, hopefully much less often. We will continue to hunt down and fix the highest volume crashes as we find…
I assure you we have not been changing things back and forth. We are working to diagnose the problem and we will have a patch with a fix as soon as we can.
This seems... different. I would suggest that if you have issues that do not match the problems that are being discussed in this thread (repeated crashes in PE, e.g.), you open a different thread or submit a bug report. Your screenshot looks like a driver issue to me.
Sorry, apparently it's not possible to attach the GamePrefs file. I'll update this when I decide what to do. Thank you to the those that did the Google Doc. :) Rob
It will fix any similar problems in Gauntlgrym. However, this is not a guarantee that you will not have to wait in a queue in general, for example, if there are no tanks or healers for a dungeon run. I'll let our community manager answer your event question.
You are totally correct. The flaw we found in our system is not completely addressed by the fix we made last night. We will release another fix as soon as we are able to "unjam" the premade groups.
Thanks for all your feedback. Our UI CPU performance is definitely not where we want it to be right now, and we will be doing our best to improve it. We will continue to focus on this after ship until it is no longer an issue.
We have determined that the client currently has an issue with Mumble - specifically the overlay, probably. You might get a better experience if you quit out of Mumble. This will also be fixed for the next beta.
Please consider following the steps in this thread: http://nw-forum.perfectworld.com/showthread.php?69201-Reporting-Client-Responsiveness-Issues We are interested in getting more information on this issue.