additional-instances-could-not-be-launched
Latest
Additional instances cannot be launched, please find something else to do.
After a long bit of extended maintenance last night for patch 3.3, and after fighting with add-ons and general instability, many players were greeted with a familiar and disappointing message from sever. Additional instances cannot be launched, please try again later. Heads exploded, babies cried, and anarchy ensued as people once again saw this dreaded error. We've been told for months that the cross-server instances and other solutions were supposed to fix this, that they would be the salvation to all our problems. Not so. At least, not yet. We are told by our sources that the central problem likely lies in there being too many players attempting to run instances. Before, if you had a server-wide instance capacity of say 1,000 instances open at any one time, you now have a battlegroup-wide instance capacity of over 10,000 instances open at any one time (just making these numbers up for the sake of argument here). Last night, in the rush to try out the new dungeon finder and cross-server mechanics, the battlegroup-wide instance capacity was reached and destroyed in a blink of an eye. You had literally tens of thousands of people running instances in each battlegroup, entirely overwhelming the system.
Breakfast Topic: The trouble with instance servers
My server rarely encounters the Door Boss, but many of you have to deal with the above error on a constant basis. The error originated as a fix for high population realms that had issues with instance lag and crashes. Rather than have you frustrated with problems while in the dungeon, Blizzard decided to put a virtual bouncer at the "door" to keep the load down on the instance servers. While I do think that this was a good idea on Blizzard's part, I think that they erred greatly by not putting a queue at the "entrance" so that you can do other things while you wait -- much like the way Battlegrounds are handled.My friend Joe has to deal with the problem with on his realm and therefore made sure to ask his designated Blizzard representative when he attended the Laguna Art Museum benefit dinner. Producer Carlos Guerrero replied that they needed to upgrade the hardware on the affected realms in order to allow more instances to be launched at the same time. Presumably, that is what the extremely extended downtime was for on Tuesday. So my question to you is, did it work? Are you meeting the Door Boss with the same regularity, or are you able to enter instances more frequently now that your realm has been upgraded?
BlizzCon 2009: Blizzard announces cross-server instances
In what will certainly be the be-all end-all solution to "additional instances cannot be launched", Blizzard announced cross-server instances and LFG at the Dungeons and Raids panel at BlizzCon 2009.By taking advantage of brand-new hardware separate from your realm's instance servers, not only will you be able to find groups from pools of players in your entire battlegroup, your realm's specific instance servers will be free of the stress of mass heroic-running.On top of the convenience factor, Blizzard says that rewards will be in place for players who lead groups through instances successfully. The nature of the rewards is currently unknown but Blizzard promises more information soon. Blizzard says that the feature will be used for 5-mans only at this time. It'll be launched with 3.3, not with Cataclysm. Fantastic news! No more "additional instances" errors, a larger pool of players to choose your groups from, and rewards for good party leaders. Great news for everyone. BlizzCon 2009 is here! WoW.com has continuing coverage, bringing you the latest in Cataclysm news, live blogs, galleries, and reports right from the convention floor. Check out WoW.com's Guide to BlizzCon for the latest!
Instance throttling explained
If you do a lot of instances, you're probably familiar with the error message "Additional instances could not be launched. Please, try again later," and the accompanying dance of spamming the instance portal until it lets you in. For me it seems to happen most at the Azjol-Nerub portal, but that's probably just coincidence. Anyway, although I've been seeing this error pretty much since WotLK launched, Wryxian just made a post today in the European forums explaining what it's all about. Basically, it's an attempt to fix instance performance; if too many instances are running at the same time on the instance server, lag and possible crashes result (and I'm sure we've all experienced that), so there's a limit imposed on how many instances can be up at any given time.
