so after your "Fix" we have problem with additional instances again. We cant get into ulduar 25.

Reporting from Argent Dawn;

AD is a pretty busy realm, we get login queues often so it's no surprise that, before the fix, I came across the 'full instance' issue every single night at peak times and sometimes even at off-peak times. However, since the fix I haven't received the instance capacity message even once.

Thanks Blizzard :)

I tried on Friday and was kind of afraid to enter Gnomeregan for my achievments.
"Will I see that message again or will I be able to really enter?"

It actually worked, I was able to enter on my first attempt, which was a relief!

But again, this shouldn't have taken so long to fix. Although it's just a game, what about the frustration that was created or the wasted time that was actually paid for?
I know, nobody is forcing us to play WoW, but imagine the following;

There would be this new concept launched by famous movie theatres where you can buy a set of tickets that are valid for x number of movies in the next year. There would be one drawback however; they don't bother to check the maximum number of available seats, they just keep selling tickets.

Sounds familiar?!

The only difference is that it would be a more 'public' problem, a lot more people would understand that something unacceptable was going on and media and consumer organizations would get involved.

The problem however that is the root cause of all these forum threads tho is treated as if it's 'only' affecting a couple of million geeks.
Sometimes Blizzard really seems to forgot that there are real people behind accountnumbers. People that actually have rights and opinions and deserve some degree of respect.

So please, fix everything properly and think about new features afterwards.

Well I am playing on Twilight's Hammer and we had to cancel our raid yesterday due to instance servers being full. So 25 people waiting 45 mins to get a server and then having to cancel is pretty anti fun, and reading that Twilight's Hammer should be fixed makes it slightly worse :(

why skip frostmane?

After this capacity update, we have been experiencing raid wide server lagg inside Ulduar and Trail of the Crusader, while attempting bosses. This issue made stoped us in progressing further, because tanks where dying due to not recieving heals during the lagg spikes. Our whole raid experienced this, among other guilds we talked due at the current time. This was on Grim Batol.

I am greatful taht you did update the capacity, but it doesn't help much when we can't use the created instance too any good.

Sincerly, Tyraa

I have a dead serious question. Why do bgs lagg like hell since the "reconfiguration"? Ruin one to save the other? That was the big sollution?

---

Q u o t e:
In our continued efforts to improve the availability of instances, we have implemented the instance capacity updates on additional realms last week. The update took place during maintenance on Wednesday 02/09 (Phase 1) and concluded during a short downtime on Thursday 03/09 (Phase 2), and has now been successfully completed on the realms listed below. We plan on continuing the with this method of putting the updates in place over a two day window on further batches of realms over the coming weeks and will keep this thread updated with those developments.

---

Could you provide us with a timeline for the NON updated realms? Not to be rude, but there's still quite a few having this problem and we have no idea when will it be fixed.

And still you only list the ones upgraded.... keeping everyone else in the dark

---

Q u o t e:
why skip frostmane?

---

Different server cluster.

Yours will get done with the rest of Misery BG.

---

Q u o t e:


Different server cluster.

Yours will get done with the rest of Misery BG.

---

Last time I checked, Outland was in Misery, and we have had our upgrade already. Frostmane is also already in the list in the starting post.

Well done so far but is there any ETA on the few missing battlegroups?

Vaneras linked this thread as a way to stop our complaints about the fact that Frostmane has been suffering from queues and instance-lag, yet I see nothing here on those issues. What's the explanation that should be awaiting us here, or is it another case of Vaneras suffering from illiteracy?

I'm seeing the issue fairly simple. I pay for a service that isn't given at the moment. I've just extended my game time for 2 more months. If the issue isn't resolved by then i will cancel my subscription and with me many players in my guild. I've brought the issue to the attention of a GM, only to get a very standard response. Enough is enough. Í'm not happy with the service rendered by Blizzard, thus i have the right to cancel my subscription. And please don't tell me, that i pay just for access to the game. I pay for a gaming experience. I don't like the gaming experience, due to this issue, thus i'm close to moving on. There are plenty of very promising games due out in the near future, and hopefully they will have learned from the mistakes i feel Blizzard has made concerning keeping players happy and updated, and resolving issues as soon as possible. What Blizzard doesn't seem to understand is that it's the players that make a game a success or a failure. If you loose the players, you loose the game.

I would like to hear the reason, why this severe problem hasn't been fixed yet. The problem is well known as is the cause. How it can be that hard for a corporation like Blizzard to fix this simple problem?
Raise the server capacity, put a queue system, similar than battlegrounds (not very good fix imo, but better than current situation).

I honestly think somekind of refund would be appropriate if these problems continue like this. Last night tried to get in Blackfathom Deep. Couldn't get in. After 10 minutes constantly trying a horde group appeared there and of course encountered the same problem. Two groups at the dungeon like BFD? Come on...
We lost one dps after 15 minutes waiting, can't really blame him, but made things a little tougher (well slower actually). In the end it took 28 minutes! Can someone say that's reasonable?
And before someone says anything, I don't exaggerate at all. Time is easily seen in 30 mins buffs, which were used at the entrance and which had 2 mins left when we got in.

Before BFD I tried to do Stockade two days ago. That time it took "only" 16mins to get in. Before that, few days earlier, same problem. Might been SFK or something, didn't take time, but it was too long.

Three instance in a row, all separate days, all had the same problem. Bugs are nasty, but this ain't one. I'm paying my mounthly fees and except something to be done soon or some game days to be offered without a cost.


I'm posting with this char as most of the problems have been in low level dungeons. It seems that Blizzard tries to hide the problem and gives lvl 80 dungeons and other end-game instances priority here. The problem still lies there and it's not acceptable to move problems to low lvl chars.


Oh, and one more thing:
x minutes waiting, 16 mins waiting, 28 minutes waiting. That's the list of three last dungeons I've tried as already said in the post. Still I can't see Moonglade in the starting post where optimized realms are listed and fixed "during few coming months". Does that mean I have to wait like half a year for my realm to be fixed? I'd like to have a blue post about this, because if I have to wait that long my problems to vanish, I might to consider my next payments...

Trying to play last night on the Moonglade server and still having this really annoying problem.

My friends and I get together once a week on a Sunday night to do some instancing and catch up with each other. So last night we decided to do the Culling of Stratholme, got to the instance entrance and had to spend 10 minutes trying to get into the poxy instance dealing with constant 'Additional instances cannot be launched' messages.

This problem really should have been fixed a long time ago, Blizzard know it is an issue and that it is degrading the game experience for a lot of players and yet it still has not been fixed.

Hi.

I'm on a realm that is still affected by this issue, and I see from the login screen that there is no announcement of a fix this maintenance period either, meaning that for at least part of brewfest, and perhaps all of it, us achievement hunters will be encouraged to go to an instance that will very likely not be available for several hours, judging by my recent experience.

It is clear that there is some prioritisation going on somewhere - I havent heard of anyone on our battlegroup complaining about significant delays getting into level 80 raid instances or into ToC5; it is relatively rare for significant delays to hinder entry to other level 80 instances; but level 60 instances are extremely tedious to enter.

Is there any possibility of having the priorities temporarily changed to allow BRD to actually happen during the limited period that it is possible to get the achievements, drops etc for this festival? Or if not, then some other kind of fix?

Thanks.

I would like to know when Azuremyst will be fixed. We waited 2 hours the other night to get into Scarlet Monastry, then gave up. Another night a 25 man raid failed to get into a level 70 dungeon in Netherstorm for 2 successive nights, after and hour and a half people give up and drift away. I have low level alts that are too high for some of the dungeons where I have quests because I have never been able to get into the instance. All my guild are angry and frustrated and that's not a good gaming experience.

We would really appreciate an update on when the problem will be fixed for the remaining realms. I suppose a credit for all those hours of lost gaming time is too much to ask.

I would also like to know when Azuremyst is scheduled. I play for ~5 hours a day on avarage. I spend ~1 hour each day running into this issue. That means that i am losing more than 1 day of gametime each week.

Could we please get an update on this matter?
Even though you're busy with other stuff, you could delay it 2 weeks just to fully fix the isntances issue.