whose bright idea was it to put on an event when the game is in such a awful state? its taking five minutes or more to do a single load screen (if i dont crash, and then be unable to log in through multiple different errors) and this has been going on for DAYS.
OrdoHermetica wrote: »whose bright idea was it to put on an event when the game is in such a awful state? its taking five minutes or more to do a single load screen (if i dont crash, and then be unable to log in through multiple different errors) and this has been going on for DAYS.
...I mean, this has been the MO for literally years now. How many years in a row was the group finder broken during the Undaunted event, for example?
ZOS must have fixed something. Load times and other malfunctions seen yesterday were back to normal this AM.
blackpool9 wrote: »
This. Very much this. All this week I've been fine in the AM (Eastern US) and early afternoon. As it gets to late afternoon, load times start getting longer and I start to see more delays interacting with guild banks and guild stores. Then between 7pm and 11pm the game becomes virtually unplayable. After 11pm things start improving slightly, but I'm usually in bed before it gets back to normal. The one thing I haven't done is try using group finder in the AM, to see if that is any better at that time of the day.
It would be nice if we got *some* kind of acknowledgment from ZOS on these issues, but other than a perfunctory "we're aware of the reports of performance issues and are investigating" back on Tuesday it's been pretty much radio silence from the ZOS team.
ZOS_GinaBruno wrote: »Hey everyone, just wanted to let you know that we are aware there are issues right now including lag, long loading screens and issues logging in, to name a few. While we are fairly certain we've identified the problem, it's likely not something we can fix tonight. We'll let you know when we have an update but just wanted to set realistic expectations here.
Can we please have an update on what exactly would be "realistic expectations"? I wasn't able to find a word about the situation in today's DevTracker posts and it appears to be happening again tonight. Are we talking days or weeks to get it fixed? Can we have details on what went wrong and how likely it would be to recur?