Additional instances cannot be launched, please try again later.

[Maticus]

People could argue that this belongs in the Raids and Instances thread, but it's not about the instances themselves, it's about Blizzard's work priority schedule.

Clearly, the "Additional instances cannot be launched, please try again later." problem is pretty big. I understand why they made a limit on the number of instances, to ensure that the raiding experience remained of a certain quality, and that's great - if the majority of people can even get into a raid!

I'm leveling an alt at the moment, and everyone knows what a pain it is to find a decent group for an instance, especially the low level ones as there are fewer players of the correct level to choose from. It's always the same, you finally get a group, then all make your way to the instance (Razorfen Downs in my case, which isn't a quick trip for Alliance). Then you spend ages all running backwards and forwards until you're lucky and get a free instance slot. Last night my group only had to do this for around 5 mins, but on Wednesday night a group I was in actually gave up after 45 mins of trying to get into Uldaman.

I think this is a major issue and Blizzard should be looking to resolve it asap. When most people can't access instances and raids at peak times, it's bad news. I know it can't be a simple problem, and Blizzard claims its looking into the matter - but it's been an issue for a few months now and it's only getting worse as more people buy the game - yes, subscriptions are still growing, albeit slowly right now.

[waflob]

This is a pet peeve of mine.

My theory is that Blizz know what the problem is, know how much the solution will cost, but the bean-counters that run the company now won't allow the expense, as it is cheaper to lose a few subscriptions than to do the right thing.

Also, bear in mind that this has been going on since October last year. Quite disgraceful and embarrassing for Blizz, but the only option we have is to stop playing. This would, perversely, also solve the problem.

[Wintrow]

I too think that it would be a matter of adding a server to the realm and re-dividing the instances between the instance servers. And with hundreds of realms... that adds up pretty quickly yes.

[Janfader]

Well, if the bean counters run their company, then Blizzard will soon find themselves in a hole fast much like the other companies having bean counters run their companies...

It is a problem as I'm a jr.master for a guild I help run/maintain and run lower level guildies through them all (yes all). I also teach them to the lower lvl officers so I can maintain end game play with the SGA.

Blizzard better wake up soon. I'm close to taking another summer off as well a few of my friends too that play the game. The SGA also has stated the same thing. SGA - Small Guild alliance on Eonar.

Maybe their 500 million dallor budget for the movie is causing a issue??? lol

[Maticus]

Speaking of the movie - there better be some news on that at BlizzCon...

Anyway, it's not like Blizzard to ignore problems with their games. They're obviously still trying to increase the player base, the Ozzy Osbourne ads are still running here in the UK, but the servers can't take it.

I feel that Blizz should've seen this coming. They've been adding regular servers when the game's population goes up, it makes sense that sooner or later the instance servers were going to fall over.

[Janfader]

Would it be a burdon at all for Blizzard to state this issue when you log on? The yellow font stuff... They could be honest about it all and just tell you when you log in "Sorry for the instance inconvienances, we're working a solution". >enter time frame<

[prion]

not a huge issue on my server, most of the time i have no more than a 5 minute wait, but it was a major problem during the lunar festival.

I think we can expect more of the same during holidays and special game events unless they increase capacity.

[Marlous]

If they don't fiond a solution soon, then it's going to be all jammed up by the time Brewfest hits with all the Coren Direbrew farming.

[Maticus]

not a huge issue on my server, most of the time i have no more than a 5 minute wait

Is it affected by server population or are the instance servers totally separate?

[prion]

i don't know.

but i tend to start around 10pm eastern which i would think is still a fairly high use time.

... /shrug

[Breewyn]

Is it affected by server population or are the instance servers totally separate?My belief is that they are totally separate, despite all those who swear the problems are worse on certain servers than they are on others. If it was worse on certain servers, we would see Blizzard encourage people to transfer. Plus the BG servers are separate, aren't they?

I think the biggest problem is all the people out there (including me) who are solo'ing instances. I went to UD Strat for a mount run and there were 3 of us trying to get in the darn thing, all for solo runs. I also like to solo UBRS when I need to farm gold.

[mmorpg man]

i personally blame it on the increase of people getting boosted through all the old content. Still, this has been a recuring problem since before wrath, surely blizzard would have found a viable solution by now. Then again, maybe not, i'm not a programmer so have no idea about these things.

[Janfader]

i personally blame it on the increase of people getting boosted through all the old content. Still, this has been a recuring problem since before wrath, surely blizzard would have found a viable solution by now. Then again, maybe not, i'm not a programmer so have no idea about these things.

Only thing you can blame it on is someone not doing their job at Blizzard. They have been at this long enough and have seen their game increase to 11 million people. You can't tell me they didn't see this problem coming. They just need to be ahead of the game > implementing top of the line servers, or hosts for the demand of the customers. It's quite sad really.

[Janfader]

Only thing you can blame it on is someone not doing their job at Blizzard. They have been at this long enough and have seen their game increase to 11 million people. You can't tell me they didn't see this problem coming. They just need to be ahead of the game > implementing top of the line servers, or hosts for the demand of the customers. It's quite sad really.

*can't edit my post... sry for a post after post...*

Last night we could not get into anything. 30 minutes + and we just gave up. Yes, some days are worse than ever... However school is out and the hounds are back.

Is there any news on Blizzard fixing this?

[prion]

is there any news on Blizzard even acknowledging the problem?

[waflob]

Yes, they acknowledged the problem in October last year - since then though - squat

[Maticus]

Actually a blue poster said this earlier:

The limit is to ensure that the instances remain playable for those who are in them. If we allow to much traffic into the instance, then the latency in those instances becomes untenable. This is our current solution, but we're currently working on a solution that will not inhibit the number of instances created.
Not much but it's a start I guess. Meh, actually they've been saying this for a while. Would be nice to know roughly when this fix would be applied. I still consider it a very important issue. They might as well take away the option for instances at peak times, because that's the effect it has on many of us.

[Wintrow]

One workaround would be to try and spread instancing.

Like, raid before noon instead of at night. Y'know, ... at off hours.

[Maticus]

One workaround would be to try and spread instancing.

Like, raid before noon instead of at night. Y'know, ... at off hours.

Wonderful if you have no job or school/college :smiley:

Sorry if I missed any sarcasm/irony/humour intended there!

[rgirty]

I really hope we see a fix prior to 3.2 or at least at the launch.

I was very frustrated when our guild could not even get in to ulduar to raid it when 3.1 hit.

It took us 3 days to get in.

There won't be any instances available for long stretches of time if they don't do something prior to the patch.

[Wintrow]

Wonderful if you have no job or school/college :smiley:

Sorry if I missed any sarcasm/irony/humour intended there!

There was no irony or sarcasm in my previous post. Only ignorance.

[waflob]

They might as well take away the option for instances at peak times, because that's the effect it has on many of us.
Not a bad idea actually. At least that way, I could go do something else, KNOWING that I can't get into an instance. As it is, I keep running up against the entrance, because maybe THIS time, I'll get in.

At least they do acknowledge the problem - unlike tppk in D2

[Tater]

If they do actually start giving conquest badges for Heroics. You can forget about getting in any instance for several months.

[rgirty]

If they do actually start giving conquest badges for Heroics. You can forget about getting in any instance for several months.

Which is why it needs to be fixed.

Surely someone at blizzard has stated in some sort of meeting "the instance servers are saturated now. The upcoming content patch and badge changes are only going to lead to more saturation."

Blizzard needs to treat the root cause, and not the symptoms. What they are doing with WG by queing and only allowing so many people in IS NOT A GOOD SIGN.

Given the history of server log in que, and the upcoming WG que it would stand to reason that blizzard would treat this situation by simply giving you a "loading" screen for an instance and giving you a que number.

Can you imagine? "Heroic Violet Hold, you are number 19,363 in que estimated 43 minutes remain"

Before you say "that won't happen"

Think back to the 30-45 minute ques people were getting JUST TO LOG ONTO THEIR SERVER several months ago.


Basically, this is what is happening now you just don't see any kind of que status and end up jumping in and out of the door until it loads.

Only time will tell, my money is on a que... i don't see blizz actually fixing this.

[aquafine]

Blizzard seems to be saying "Oooooh recession is scary!" When the fact of the matter is they haven't changed their prices and honest to god it doesn't seem to have effected them. In fact with the recession they seem to be excelling. Anyway the profiteers are just too afraid to use money then find out that people can't afford the game anymore. They might also look at it like "Why should we spend more money on the game before the next expansion when we already have 11mil players?"

[waflob]

If they do actually start giving conquest badges for Heroics. You can forget about getting in any instance for several months.
I must have missed that part - seriously? Will heroics have a "hard mode" for these, or are they just making it silly?

[Janfader]

I must have missed that part - seriously? Will heroics have a "hard mode" for these, or are they just making it silly?

Silly...

Last night same thing... 30 minutes at least and just had it with this BS.

I'll focus on getting my toons up to 80 as well max'n out my professions. This is getting ridiculos. I would love to be reimbursed for the amount of time I've spent waiting to get into a instance.

Even last night, in global chat, people where saying "I have a toon already in the instance, pst me for invite" etc...

It's getting that bad??? please.

[Maticus]

Blizzard just posted this, a glimmer of hope at last!

We are aware of the concerns regarding situations where players are unable to zone into an instance due to an instance limit being hit, which results in a message stating that additional instances cannot be launched. This limit was implemented as a short-term solution to preserve the gameplay for players who are already in an instance and to prevent numerous issues that can happen when too many instances are active at the same time, but we are currently working on better solutions to ensure that players can get into instances when they want to.

As one of the solutions to this situation, we are in the process of modifying our hardware setup to allow for more instances to be active without negatively impacting the performance of these instances. Once this hardware reconfiguration is complete, we expect to see a noticeable reduction in the number of players hitting the instance limit. However, this improvement to the hardware is a complicated and delicate process that will also require extensive testing before it can be fully implemented, so it may be some time before the updates can be completed. We would like to assure you that this issue currently a top priority for us, and we are working on resolving it as quickly as possible.

Further information and updates regarding this will be provided as we make progress in this process. Thank you for your patience during this time.

[Shellar]

Edit: Ninja'd :(

< Aww sorry Shellar :( .. Mati >

[rgirty]

Blizzard just posted this, a glimmer of hope at last!

We are aware of the concerns regarding situations where players are unable to zone into an instance due to an instance limit being hit, which results in a message stating that additional instances cannot be launched. This limit was implemented as a short-term solution to preserve the gameplay for players who are already in an instance and to prevent numerous issues that can happen when too many instances are active at the same time, but we are currently working on better solutions to ensure that players can get into instances when they want to.

As one of the solutions to this situation, we are in the process of modifying our hardware setup to allow for more instances to be active without negatively impacting the performance of these instances. Once this hardware reconfiguration is complete, we expect to see a noticeable reduction in the number of players hitting the instance limit. However, this improvement to the hardware is a complicated and delicate process that will also require extensive testing before it can be fully implemented, so it may be some time before the updates can be completed. We would like to assure you that this issue currently a top priority for us, and we are working on resolving it as quickly as possible.

Further information and updates regarding this will be provided as we make progress in this process. Thank you for your patience during this time.

blizzard speak for:

We know its a problem, we aren't losing subs we'll fix it when we get ready.

We know there is going to be a massive problem when people start running instances and raids like naxx 5x more than they do now due to conquest emblems.

We still won't fix it in a timely manner because we aren't losing money.

Thanks, blizz.

[waflob]

On the one hand, I appreciate the fact that they *appear* to be doing something. On the other hand, since when is 9 months "short term" ?!?

This Blizzard response should have been made before Christmas last year.

[Janfader]

On the one hand, I appreciate the fact that they *appear* to be doing something. On the other hand, since when is 9 months "short term" ?!?

This Blizzard response should have been made before Christmas last year.

Agreed ^^

Here's a question. Are all the instances i.e. Azeroth, OL's, NR tied to one large instance server or 3 different instance servers?

Last night we could not get into any OL instances, however I pop on my Priest and run UK without any issue to get in.:ponder: While the group I left prior to that where still unable to get into SH in OLs. Odd.

[rgirty]

If a real fix is on the horizon we would have more concrete information about it.

If anything blizz is great at trumpeting what they call improvements, but what most of us think of us "it should have been that way to begin with" kind of fixes.

[Janfader]

If a real fix is on the horizon we would have more concrete information about it.

If anything blizz is great at trumpeting what they call improvements, but what most of us think of us "it should have been that way to begin with" kind of fixes.

Does anyone know any tricks? I've been told to log off/on and it helps... helps with what I would love to /know...

I was also told Blizzard is creating a "query" for the instance like BG's for a temp fix i.e. 3.2 I guess. This won't help IMO.

[rgirty]

Does anyone know any tricks? I've been told to log off/on and it helps... helps with what I would love to /know...

I was also told Blizzard is creating a "query" for the instance like BG's for a temp fix i.e. 3.2 I guess. This won't help IMO.

Create an alt and place them in dalaran/ironforge/stormwind or the corresponding filthy horde city and spam trade/general chat with messages that the opposite faction are attacking one of the above cities.

Sometimes enough people will rush to see that it will open up an instance faster....or so i heard.

Not that I would actually try this to get into heroic VH quicker...nawe i wouldn't do that.

[zXz]

Create an alt and place them in dalaran/ironforge/stormwind or the corresponding filthy horde city and spam trade/general chat with messages that the opposite faction are attacking one of the above cities.

Sometimes enough people will rush to see that it will open up an instance faster....or so i heard.

Not that I would actually try this to get into heroic VH quicker...nawe i wouldn't do that.But most people who would go help defend org, tb or the alliance equivalent probably have /join worlddefense. And so they can tell when a place is being attacked regardless of where they are playing at the moment.

[Mazhulsage]

Blizzard shoudl have taken care of this MONTHS ago. It's truely bullcrap that we have to continue paying a subscription for something that is happening literally every single day, especially since it's the summer.

[Janfader]

Blizzard shoudl have taken care of this MONTHS ago. It's truely bullcrap that we have to continue paying a subscription for something that is happening literally every single day, especially since it's the summer.

Hey Maz, I fully agree with what your stating. We had two guildies last night say something similiar to what you wrote - and their new to the game (3 months).

Seeing my role in the guild is to now start running the 80's through roics and still aiding with running guildies through instances on Tuesday and Thursdays... I'm finding myself in instances all the time... well... when the instances are actually working. 7:00pm to 10:00pm everyday seems to be impossible to get into an instance. Weekends is nearly impossible.

Due to this, we're forming arena teams which I haven't actually researched at at - stats/talent specs etc... I just hope the cue time is quick.

[Wintrow]

Perhaps the issue can be somewhat alleviated if people would all reset their instances after they're done with them?

[Janfader]

Perhaps the issue can be more easily solved if people would all reset their instances after they're done with them?

Hey Wintrow, that's just maybe the answer! But, I think once everyone is out of the instance, the query is reset? I don't know - but maybe your right - makes sense IMO.

This question needs to be answered by a Blizz blue.

[Wintrow]

Non-heroic/raid instances are automatically reset 30 minutes after everyone leaves.

The only thing THEY could do is, when everyone leaves, to ask the group leader "Seems everyone left the instance xxx, you want to reset it?".

Shortening the timer will lead to ppl hopping out and in for a quick repair or something getting shafted.

[Mazhulsage]

It's just that this has been going on for SOOOO long... I understand it's summer. I understand it's the weekend. I understand that means over 9000 people will be doing instances... Come on though. At least give us a queue, instead of having to run around in a circle and sometimes see someone else's group run up and they get through but you don't...

[rgirty]

It's just that this has been going on for SOOOO long... I understand it's summer. I understand it's the weekend. I understand that means over 9000 people will be doing instances... Come on though. At least give us a queue, instead of having to run around in a circle and sometimes see someone else's group run up and they get through but you don't...

Blizzard is enhancing the argent tournament even MORE in the next patch...maybe that is blizzard's answer to less people in instances.

Yes? No?

[Janfader]

I just want to thank Blizzard persoanlly for screwing up their once great game. After the release of 3.2 yesterday with all its horrific lag issues and UI issues and they still didn;t even touch the issue of instance not being able to launch. In fact, its got even worse. Hours upon hours last night without getting into any of them. I had a few guildies run the new Argent one and upon their death (getting back inside of it), they got caught in the corner of the instance and were stuck without question or answer > they're still stuck to this date with that toon.

I hate to sound negative, however this patch is pathetic on many accounts where Blizzard should of focused their fixes were problems are occuring - not to introduce more.

[rgirty]

As I stated earlier in this thread, it won't be addressed. It hasn't been.

Wintergrasp itself also now only allows so many people in the battle, which more or less turned it into a timed BG.

We did finally get to raid the new 25 man, but we had so many players with UI issues (i'll give it to blizzard, most of these were due to addons) and connectivity issues we ended up with only 20-24 people for most attempts.

I honestly think the only think blizzard will do for a while about the instance servers is offer more bs solo content like expanding the tournament.

[clevins]

There's a blue post on the instance thing.. long term fix, blah blah. I think they screwed up by not having this addressed in the same patch where they made it wy more attractive to run heroics again, though I had no issues in the ToC runs this evening.

And lag? You're really surprised that on patch day when tons of people all log in at once that there's lag? really?? I've seen no UI issues at all - yes, addons need updating, but if you're surprised by that or the lag, you've not been paying attention.

3.2 is a nice patch and in far better shape than 3.1 was. Please don't whine about lag (no one likes it, we all expect it when everyone comes back) or addon issues (get updates). The instance thing is the only real issue and that's not new to the patch.

[rgirty]

And lag? You're really surprised that on patch day when tons of people all log in at once that there's lag? really?? I've seen no UI issues at all - yes, addons need updating, but if you're surprised by that or the lag, you've not been paying attention.

I should have been more clear. I wasn't talking about lag. I was talking about random disconnects and other issues.

We had multiple raiders that would DC at certain points of the battle, not unlike what happens at the beginning of the thorim battle.

We had people who would dc and then not be able to log back in if their corpse was in the instance.

We really didn't have any lag issues, just the wonky random dc's that we'd partially seen in ulduar.

I've been paying attention, i've been through a few patches now. What we experienced last night was very much unlike what we had experienced before.

3.1 we simply couldn't get in the instance, we were in just fine last night but had the random issues with connectivity (not lag). Sorry if you consider this whine, just commenting on the experience we had during our raid night in regards to full instances (we didn't have an issue with that)

[Janfader]

The 3.2 lag was everywhere and the worst I've ever seen - and I'm running a high end machine now. I have every right to complain ty Clevins, as I'm pretty sure this is a freedom of speech world we live in, plus being the internet. I'll have no care in your argument to this subject.

Blizzard, keep throwing clean sheets over the dirty ones... its really making things worse.

[SwervinCL]

The 3.2 lag was everywhere and the worst I've ever seen - and I'm running a high end machine now. I have every right to complain ty Clevins, as I'm pretty sure this is a freedom of speech world we live in, plus being the internet. I'll have no care in your argument to this subject.

Blizzard, keep throwing clean sheets over the dirty ones... its really making things worse.

The only real lag that I ran into last night was in Dalaran. Went to Org, everything was normal.

The other problem that we had last night was getting into instances. I think the patch went pretty smoothly. I didn't even expect to play at all last night and was surprised that the servers came up.

The instance thing 'should' have been fixed with this patch. It was an issue before the patch. They gave people reasons to run heroics and adding more instances/raids to the game. Now, you spend more time trying to get into the damn place than actually running it.

[Janfader]

The only real lag that I ran into last night was in Dalaran. Went to Org, everything was normal.

The other problem that we had last night was getting into instances. I think the patch went pretty smoothly. I didn't even expect to play at all last night and was surprised that the servers came up.

The instance thing 'should' have been fixed with this patch. It was an issue before the patch. They gave people reasons to run heroics and adding more instances/raids to the game. Now, you spend more time trying to get into the damn place than actually running it.

The lag I expeirenced was worse in the major spots, however still lag in areas like Ice Crown, Grizzly Hills (places where dailies are) etc... but whatever right.

The main issue here is the instances for sure.

Perhaps just PvP in BG's and form some arena groups??

[clevins]

freedom of speech gets tiresome when it's predictable. "Hey, there's a major patch the servers get crushed with people all logging in to check it out and... what? LAG? OMG"

Of course there's lag when there's tons of people all on at once to check out a patch. Yeah you can ***** about it, but it you sound like a long period amnesiac because this happens every patch and mostly goes away. It's load related. The instance thing doesn't seem to be and stops one from doing something totally.

Oh and you have no freedom of speech. Misunderstanding of the concept which relates to government being able to limit what you say. Here, the site can delete anything we say and no rights are being infringed because you have none. This is a private place. Just like I can tell you to shutup or leave my house (or you can do the same to me) because it's our place.

[rgirty]

Yeah, but hopefully the mods here won't let this place turn into the officials. It isn't like the boards here are swamped with traffic making it impossible to manage.

[Janfader]

freedom of speech gets tiresome when it's predictable. "Hey, there's a major patch the servers get crushed with people all logging in to check it out and... what? LAG? OMG"

Of course there's lag when there's tons of people all on at once to check out a patch. Yeah you can ***** about it, but it you sound like a long period amnesiac because this happens every patch and mostly goes away. It's load related. The instance thing doesn't seem to be and stops one from doing something totally.

Oh and you have no freedom of speech. Misunderstanding of the concept which relates to government being able to limit what you say. Here, the site can delete anything we say and no rights are being infringed because you have none. This is a private place. Just like I can tell you to shutup or leave my house (or you can do the same to me) because it's our place.

Clevins, I've always respected you and still do. Sometimes people need to vent here because others will chime in or agree or to disagree.

I was expecting lag on the day of 3.2 just not to the degree it was at.

And to stay on topic, not one member in OPG (guild I'm in) could get into any instances. If that wasn't frustrating enough, we decided to try PvP BG's.... that was a big mistake. But ater a long 3 hours of getting pwned by the horde we won one!!!:laughing:

Laughing Skulls guild for the horde side on Eonar are one wicked PvP guild.

[JFrombaugh]

Yeah, I've noticed this too. It happens not just on high population servers but everywhere (my server's population is ranked as "Medium" on the realms list and I still have rarely, if ever, gotten in an instance on my first try since Patch 3.1 launched.)

I can't tell you how many times my guild has had to call off a Heroic/Raid run because we just couldn't get in, and if Blizzard doesn't create solutions to this problem (which there are solutions) instancing in WotLK is just going to get this massive rep of "get a group together to run at an instance portal repeatedly". Raiding guilds are about 4 months ahead of the more casual crowd. They've already pissed us off, the so-called "noob" players won't be far behind. In a day where raids are accessible to more people than ever before, Blizzard REALLY needs to do something.

[ptarn]

Indeed, it's getting beyond ridiculous now, especially with the Emblem-craze that's got everyone running instances like there's no tomorrow. I know people have said it before, but come on... Blizzard will have to do better than this! People don't pay a monthly fee just to try and get into an instance every night (and fail!).

[Janfader]

Indeed, it's getting beyond ridiculous now, especially with the Emblem-craze that's got everyone running instances like there's no tomorrow. I know people have said it before, but come on... Blizzard will have to do better than this! People don't pay a monthly fee just to try and get into an instance every night (and fail!).

Last night again for ToC, and trying to help my RL friends progress through OL's. Ramps, BF, SP, UB all full.

[Shellar]

I'm inclined to believe the blue post that claims that AICBL is a server specific issue. Since WotLK's release, I've run into this problem only once.

[rgirty]

Indeed, it's getting beyond ridiculous now, especially with the Emblem-craze that's got everyone running instances like there's no tomorrow. I know people have said it before, but come on... Blizzard will have to do better than this!.

Let examine the problem, with a bit of history thrown in.

When new content and or expansions come along most of us experience a log in que at the server level.

Blizzard did nothing to fix this, except explain that the problem would be reduced when everyone wasn't logging in at the same time. Basically they said this was a spike, and they weren't making changes to address a spike in log on population.

The situation with instances is nearly the same EXCEPT you do not get put in a que... you might get lucky and jump right at the exact time or spend a good deal of time jumping into the portal.

Did blizzard know this would happen when they made the badge change?

YES

But much like the server log in que, they view it as a spike.

My theory:

Internally they believe the badge craze is just a spike, and will let players deal with it. They think players will be so burned out on instances after the badge craze that any fix they put in place now to accommodate large numbers of people doing instances will be totally useless 4-5 months from now.

I believe the ony encounter will be on its own set of instance servers, separate from the rest in some sort of 1/2 attempt to load balance.

In reality, they could fix it if they really wanted to the ROI simply isn't there for them.

Money made by fixing the problem is LESS than letting it remain as is.

More solo content will be added to the game, like the tournament which serves multiple purposes. Blizzard can point at it and say "new content" at the same time it lightens the instance server load.


This problem will not be fixed any time soon, it has been going on for way too long... ever since people started trying to get the worthless achievements from old instances.

If blizz wanted to fix it by now they would have. People can complain until the end of time, but until the money gained > money lost for them by doing it they will not do it.

I really expect hell to be raised at blizzcon over it, and no definitive statement will be made "we're working on it" is all we will ever get.

[Janfader]

I really expect hell to be raised at blizzcon over it, and no definitive statement will be made "we're working on it" is all we will ever get.

As it should be IMO. It's pretty lame and making our guild's progression a joke right now. There's only so many outside instance quests (dailies) with decent gear (lvl 200 gear). .. .

Rr....

Quote from a guildie last night:

"Opened a ticket with a GM last night in regards to the instances...Blizzard is upgrading hardware as fast as they can and then they are testing their upgrades, they do not have a timeline in place as to when this issue will be resolved, but they do say that this should "dramaticly" improve instacnce availability."

Its really bad on the server I'm on. People are selling instance spots.

[ptarn]

Selling instance spots? That's... that's beyond crazy right there!

[rgirty]

Blizzard is upgrading hardware as fast as they can

Do they really think blizzard has been updgrading hardware as fast as they can for even the past 6 months that they have had this issue?

Why did they wait until the badge craze THAT THEY INITIATED to start upgrading...

I don't buy it, and if after some tuesday we see the problem vanish i'll be shocked.

I doubt few if any players are cancelling over this issue, if they are the net loss isn't greater than what the fix would cost.

[Janfader]

Do they really think blizzard has been updgrading hardware as fast as they can for even the past 6 months that they have had this issue?

Why did they wait until the badge craze THAT THEY INITIATED to start upgrading...

I don't buy it, and if after some tuesday we see the problem vanish i'll be shocked.

I doubt few if any players are cancelling over this issue, if they are the net loss isn't greater than what the fix would cost.

lol, I just stop playing my mains and suffering levelling my priest (now 74). Well,, I guess I do the daileis.

It's a dog lost in a field of cats, hell the kitchen sink seems full next to the dishwasher.

[rgirty]

New blue post info today, but there is other info here as well.

I took this from another forum



Quote from: Zarhym
We've been undergoing infrastructure maintenance on our various databases to address the instance capacity issues for several weeks now. It's a very involved and complicated process, but a great number of realms have already seen relief. We are continuing to work on the Battlegroups that have yet to see the infrastructure changes necessary to improve the instance capacity available to players on each realm.

With that being said, I have to add that there is little to no art, development, or design involvement in fixing such an issue. They are concerned with developing and designing future content for the game and that will continue as our technical and database administrators focus on their tasks. Developers do not perform the restructuring and maintenance of our realms and databases, particularly given that we're based in California and our databases are in various locations around the world. It's a misnomer to suggest that content design focuses resources away from hardware restructuring.

Our database administrators will continue to work on the hardware structure of each database, also working closely with third parties who are helping in resolving the issue. We're working on gathering a report of the progress we've made thus far, as well as our plans in the coming weeks, and will be providing this information to our players when it is available.

[...] You are correct in that patch 3.2 drove more players to instances further impacting the issue, however, I never claimed otherwise. I simply stated that development time doesn't need to be cut or re-focused in order to more quickly alleviate this issue.

[...] The fact that some realms are experiencing realm capacity issues more frequently due to the patch doesn't mean it's going to hinder or delay our ability to resolve the issue. If I'm understanding you correctly, I think your statement is incorrect.

Just to be clear, most realms are not experiencing this. Some realms that may have been experiencing this in the last few months are no longer being affected. Those realms that are still suffering from instance capacity issues have, in most cases, noticed an amplification of the situation since patch 3.2 was launched. Those are the players we're seeing posting here; and for them, we're working on a progress report so everyone is aware of the steps being taken.

[...] Restructuring our hardware across all realms and battlegroups without excessive amounts of down time is a very long and tedious process. It's definitely something that is a high priority for us to fix, but it's complicated -- even beyond my own understanding of our hardware. While we are aware that this is greatly affecting players, there is a limitation on the expedience at which such massive restructuring of our hardware systems can be accomplished.

[clevins]

Yeah so fix it. And it's not merely first come first served. For example, I was killing time last night and decided I'd to get Don Carlos' hat from Durnholde on my 80 DK.. So I ported to CoT, flew down... and could not zone in due to this error. I could ride to Culling of Strat and zone in right away. It's pretty apparent that they're prioritizing people zoning into Northrend instances which is fine... but I've tried Durnholde multiple times since then, including in the middle of the afternoon... and nothing.

I'd have a ton more sympathy for them if this was a problem that was a month old... but seeing this for several months is BS - they should have been tracking what percentage of instance server capacity they were at and when the trend was consistently at 50-70% and rising they should have started work. What they did was let it become an issue, then address it. Kudos for addressing it, boo for waiting until it was an issue.

[Janfader]

Yeah so fix it. And it's not merely first come first served. For example, I was killing time last night and decided I'd to get Don Carlos' hat from Durnholde on my 80 DK.. So I ported to CoT, flew down... and could not zone in due to this error. I could ride to Culling of Strat and zone in right away. It's pretty apparent that they're prioritizing people zoning into Northrend instances which is fine... but I've tried Durnholde multiple times since then, including in the middle of the afternoon... and nothing.

I'd have a ton more sympathy for them if this was a problem that was a month old... but seeing this for several months is BS - they should have been tracking what percentage of instance server capacity they were at and when the trend was consistently at 50-70% and rising they should have started work. What they did was let it become an issue, then address it. Kudos for addressing it, boo for waiting until it was an issue.

WB Clevins! That's more like it.:flowers:

100% agree. QFT.

[Wintrow]

For what it's worth, since the restructuring, I have not experienced this issue ONCE. Where before it was rampant...

I'd say:
GG Blizz and keep going at it. You'll get it sooner or later.

[Janfader]

Yesterday around 7pm server time, we tried to get a bunch of 70+ into a Kara raid (have guildies expeirence raiding situations). And could not get into Kara... 1 hour or more and nothing. Such a huge disappointment for not only myself but for many players new to a raid and we're so excited about running Kara.

Sad.

[Wintrow]

Yesterday around 7pm server time, we tried to get a bunch of 70+ into a Kara raid (have guildies expeirence raiding situations). And could not get into Kara... 1 hour or more and nothing. Such a huge disappointment for not only myself but for many players new to a raid and we're so excited about running Kara.

Sad.

Well, I can imagine I'd be pissed as well if I'd still be experiencing it myself.
Perhaps they can, as a quick in-between thing, implement an instance counter in the UI. So we can tell what our odds are of running into the issue...

[rgirty]

Ran two instances last night, spent 10+minutes trying to get into each of them.

Jumping back and forth at the door with 50 other people hoping to get lucky.

Not fixed.