Posts with tag lag

The Canadian Radio-television Telecommunications Commission recently ruled that Rogers Communications, one of the largest internet service providers in Canada, has violated federal net neutrality rules. Last year, I wrote a few Lawbringers about the subject, which discussed what Rogers had to actually do to escape violation of certain internet traffic throttling complaints. Basically, Rogers was making WoW players' internet access slower because WoW looked like peer-to-peer traffic on their network.

Rogers is finally going to have to answer for the throttling issues, even after all of the requests and demands to change their packet inspection protocols. The communications company has until Feb. 3 at noon to respond to the complaints about internet throttling or face a hearing with the CRTC board.

Hopefully, the same type of rules can make their way to America, where internet service is abysmally slow and throttled like crazy. Prior to the Cataclysm launch, Blizzard released the new WoW client, which used a peer-to-peer system to upload and download information, patches, data, and all that jazz. This data accidentally triggered internet service providers' bandwidth alerts for torrent traffic and was subsequently throttled to lower speeds. After realizing that many users were experiencing lag issues with the new launcher and their ISPs, Blizzard began its outreach to ISPs in order to work together to fix the problem. A year later, people are still having problems, and Rogers in Canada has admitted to throttling WoW bandwidth.

---

Pop law abounds in The Lawbringer, your weekly dose of WoW, the law, video games and the MMO genre. Mathew McCurley takes you through the world running parallel to the games we love and enjoy, full of rules, regulations, pitfalls and traps. How about you hang out with us as we discuss some of the more esoteric aspects of the games we love to play?

We've got two stories to talk about on The Lawbringer today, both interestingly involving letters. That's right -- letters. To you from me, that sort of thing. These letters, however, are instruments of change in a world where we as consumers seem not to have much control or ability to change the big picture concepts that dot our path to consistent entertainment. The amount of energy that we have to put into just getting in a decent WoW session is staggering at times.

The first story revolves around Rogers, one of the largest Canadian internet service providers, famous for its lame bandwidth caps and my old Canadian guildmates shouting "Rogers sucks!" as much as they could on Mumble. Yes, it is another chapter in the Mathew McCurley Guide to Awful Bandwidth Throttling -- but hopefully, this new information and story chapter will get us on the path to better WoW experiences in the face of the immense throttling of WoW data as peer-to-peer traffic.

The second story is all about letters that you will want to send. Last week, I wrote The Lawbringer about Senate Bill S.978, colloquially being referred to as the anti-streaming bill. While not directly prohibiting video game streaming or even mentioning video games anywhere in the proposed legislation, video games are nonetheless obliterated in the crossfire of the entertainment industry and would-be illegal streamers making millions off of pirated entertainment, movies, music, and more. The Entertainment Consumers Association has begun a letter-writing campaign to inform and implore Congress to not pass a bill with such broad and language lacking description.

Most people who follow my exploits in World of Warcraft know me as a dyed-in-the-wool member of the Horde. In fact, I've played Horde my entire WoW career, from the early days of the official release up through the end of the Wrath. I killed Nefarian for a second time alongside my Horde brothers and sisters and ended Cho'gall's reign over the Twilight Hammer cult. If you've been following my main character's exodus from Horde to Alliance through the WoW Insider Show or Twitter, you've heard bits and pieces of why I transferred servers. Falling into the hands of the Alliance is the fault of two men -- Lodur and Matticus.

Most people who follow my exploits also know about the dreaded lag issues that I was having because of still unsolved issues with certain internet providers and odd packet inspection (presumably). Connecting to the Chicago data center was never a problem until the release of Cataclysm and, really, not until I started to raid heavily around late December 2010. Things got real ugly during late December. This is my story of changing what I could to keep playing the game that I love.

Pop law abounds in The Lawbringer, your weekly dose of WoW, the law, video games and the MMO genre. Running parallel to the games we love and enjoy is a world full of rules, regulations, pitfalls and traps. How about you hang out with us as we discuss some of the more esoteric aspects of the games we love to play?

The Lawbringer is taking a little detour today to discuss one of the more esoteric issues (like I try to do here) that many players are facing today dealing with World of Warcraft. It is interesting that one of the biggest hurdles to playing an MMO is present outside the game rather than within. Today, I want to talk about Time Warner/Brighthouse and the intense lag of 2010 and 2011. In fact, we'll visit the past and see how these companies interacted with Blizzard, and then take a stroll into the present and try to understand what's going on right now.

Confused? You might be, especially if you aren't a Time Warner or Brighthouse customer. There are some other ISPs affected by all this mess, but for now, I'm sticking to the most complained-about. Here's a quick little rundown of what's been happening over the last few weeks (and for some people, months) due to issues with Time Warner and Brighthouse internet service.

This Breakfast Topic has been brought to you by Seed, the Aol guest writer program that brings your words to WoW Insider's pages.

Lag is probably the single most common excuse for mistakes in all internet gaming. From the beginning of the big craze of first person shooters to now, mistakes are chalked up to lag. The expressions change from: "Oh sorry, you didn't get a heal? I lagged real bad!" to "Oh, I had a huge lag spike!" -- even expletive-laced shouts at the lag itself, as if you could personify bad latency. This happens in PUGs, guild runs, and even just friend and family groups.

The question is how often are people actually lagging versus how often is it merely an excuse, because no one else can prove you did not lag. The truth is, it is not always lag -- but sometimes it is. I have went on expletive-laced tirades when I disconnect during a boss fight or see that horrible thing when my entire action bar is lit up with queued spells but I am not moving. However, if you actually make a mistake that is your fault, I am a big proponent of taking credit for and owning it. If you blame lag or someone else every time you make an actual mistake instead of taking ownership of your shortcomings, you never learn from them. Admitting you used an ill-timed spell, moved into the fire, or just got caught up in your rotation and had a lapse of attention allows you to learn and grow from your mistakes (and hopefully never make them again).

Do you ever use lag as an excuse when it was a personal mistake? Is it a common go-to excuse you use often? Or do you believe in admitting your mistakes and trying to get better from them?

Some actual new information from tonight's developer Twitter chat with Lead Systems Designer Greg "Ghostcrawler" Street and J. Allen Brack? I'm as surprised as you are. When asked why the resplendent (and glowy) Crystalsong Forest is oddly barren of anything to do beyond sightsee (and, of course, the rare quest), we received some interesting info about game performance:

Part of the problem is that it sits beneath Dalaran, which ended up being more of a resource hog than we had anticipated. We didn't want to draw too many more players to that zone. Initially the Crusaders' Coliseum was going to be there, which is why some of the quests send you there. We just worried too much about the performance hit.

So what does this mean to the average WoW-player? That you can enjoy the peace and quiet of Crystalsong Forest for a long time to come, because additions to the zone just aren't on Blizzard's agenda. And it's probably for our own good -- we all know what a lagfest Dalaran can be, don't we? Now close your eyes and just imagine combining that with all of the players that come and go from the Crusader's Coliseum. If your thoughts on this imaginary scenario are anything other than "do not want," well, we'll just have to agree to disagree.

There is quite a thread going around with some ideas about how to fix raiding lag. Lag, like many cross-computer issues, is a pretty complicated thing -- there's all kinds of reasons it could be happening, from errors on your computer to errors on Blizzard's end, and all the little connections and switches in between. A certain amount of lag is unavoidable. But there are certainly some things you can do to make sure the link between your client and Blizzard's server is working at its best. This thread, which started on the EJ forums and then moved on to Livejournal, has some good tips in it, including turning off most combat logs like Recount and even Blizzard's official "Everything" log -- having to write down everything happening in game does cost some computer time as you play. Blocking addon "spam" is another way to keep things simple and clear -- while lots of useful addons help you share information between raid members, sending that info back and forth can cause problems when you're down to milliseconds of lag.

The final suggestion is to run a third-party program that's supposed to keep your latency high, but I would be leery of doing that -- a better solution if you continue to have high latency constantly, even after making the changes above, would be to go to Blizzard (and/or your Internet Service Provider, or ISP) with your issues. They have a good guide to smoothing out your connection, and many times the problem can be with your router or firewall, which is usually a quick fix.

Are you frustrated with your friends running in place?

Finding it difficult to get a good spot for the Dalaran costume contest?

Are you tired of having to set your hearth in the dark and dank sewers of Dalaran?

Have you ever thought, "Man! I wish I could report how bad the lag is right now!"?

Well, if you're like millions of other players that have experienced lag, then maybe you'll be interested in what Blizzard has announced hitting the PTR! You can now use the "Report Lag" feature announced in the latest patch notes for Patch 3.3 as part of the latest PTR Build (Build 10676). No longer are you forced to submit endless GM Support Requests or post hundreds of lag reports on the forums. In three easy steps you can now have peace of mind, knowing your lag will be successfully reported. Looking at it, it seems pretty easy to use.

1. Click the Knowledge Base/Help button.
2. Then click Report Lag.
3. Then you just select the type of lag you are experiencing. Which will most likely to be either "Movement" or "Spells and Abilities." When you're all done you get a "Your lag report has been successfully reported" message.

Now, Blizzard will know exactly when you experienced your lag so they can track down the cause and resolve it. My only fear is they will have so many reports from Dalaran we'll get a "No Lag Reporting Servers Available" for the first few days it's used.

---

Patch 3.3 is the last major patch of Wrath of the Lich King . With the new Icecrown Citadel 5-man dungeons and 10/25-man raid arriving soon, patch 3.3 will deal the final blow to the Arthas. WoW.com's Guide to Patch 3.3 will keep you updated with all the latest patch news.

---

We've been getting a steady stream of tips and tweets in about the stability issues plaguing nearly every server tonight, and Blizzard has finally confirmed that something isn't working right.

Most people are experiencing extreme lag both in instances and out in regular zones. There doesn't seem to be any rhyme or reason to it all, just constant server-side lag that impairs things like looting, completing quests, using items, buy items, or trading things to other players.

Pretty much every wonderful thing that could have lag to it does; including the lovely 30 second mount cast.

Hopefully the rolling restarts that will be taking place tomorrow morning at 5:00 a.m. PDT / 8:00 a.m. EDT will fix this. Although I'm hopeful that there would be some quick resets tonight to apply a hotfix or whatever else Blizzard needs to do in-order to make the game more playable.

We'll update this post with any additional information if we get it

Welcome back to The Queue, WoW.com's daily Q&A column where the WoW.com team answers your questions about the World of Warcraft. Allison Robert will be your hostess today.

Adam and Alex are busy packing for BlizzCon, so I've sneaked into the Queue offices to answer some questions this evening. There's no consistent theme here, folks; we're all over the map today with BlizzCon, lore, and player textures. If you don't see your question here, I still have a few in mind from the last post to answer tomorrow.

Smapdor asks...

There are 3 historical scenarios that can be found in Yogg-Saron's "brain room"...What is the Shadow Vault event? I would guess that it is something as important lore-wise as the (other) two, but I have no idea.

It's widely believed that the Shadow Vault "memory" depicts a very recent and very unfortunate occurrence that took place (without player knowledge) after the Wrath Gate event. The NPCs in question are thought to be the souls/spirits/incorporeal whatsamajiggies of Saurfang the Younger and Bolvar Fordragon, who perished in the fight, victim to the Lich King and the Royal Apothecary Society respectively. The Wrath Gate cinematic implies that the Arthas has at least Saurfang's soul to toy with (which would explain the Orcish Turned Champion), but the identity of the Immolated Champion is less clear. Bolvar is by far the most likely possibility -- after all, the Immolated Champion is wearing the same armor Bolvar wore going to his death -- but nothing's been confirmed. Bottom line? Expect to see both Saurfang and Bolvar show up in the Icecrown Citadel raid in some capacity.

We're getting tons of reports in of Wintergrasp behaving a bit oddly today, and I can confirm them to be true on my home server of Cenarion Circle. Wintergrasp battles are lasting, at most, 5-10 minutes with no more than 10 minutes between battles. Good for farming Marks of Honor, not so good for trying to kill Archavon and/or Emalon.

If this is how you try to lower the lag Wintergrasp causes on servers, I think the quote "ur doin it wrong" applies. In all seriousness, I'm kidding about that and this is obviously not working as intended. Considering the Mark and Honor gains people are getting from this, I wouldn't be surprised if we see some emergency maintenance and rollbacks soon. I wouldn't get too attached to your gains this afternoon.

Zarhym has got some answers to the widespread problem of lag in Wintergrasp after patch 3.1 the other week. He says Blizzard figures the problem is simply population based -- there are many more people playing in the battleground than there were before the patch. For that reason, they're having trouble coming up with good solutions: the battleground is designed to be non-instanced, and that's why a lot of people like it, so putting a limit on the amount of people in there is not the way to go. Hardware isn't a solution either -- Blizzard's hardware is already top-of-the-line, and not only would upgrading it take a while anyway, but my guess is that most of the lag issues come not from Blizzard's side, but from the connections between players and them, which they may not have any control over anyway.

So yes, we're more or less out of luck -- as long as Wintergrasp is extremely popular (and even Zarhym remembers the naysayers before the release with a smirk), there will always be a certain amount of lag in there. There are a few good suggestions floating around the comments thread -- one is that Wintergrasp should always be conquerable, which seems like it would keep down on the flood of people, though of course there'd be other issues if that were implemented.

At this point, Wintergrasp lag may just be something we have to live with. Eventually, you have to think the population will drop back down, and then those of us still in there will enjoy lag-free battles again. But Blizzard has taken on quite a goal trying to do non-instanced PvP full of vehicles and towers without any lag at all.

There appears to be connection problems going around as multiple people are unable to log in tonight, including multiple tipsters and yours truly. It's definitely a widespread problem, as the Blizzard Tech Support team is currently asking for ISP and tracert information over on the official forums while they try to track it down.

While some people are positing that this is a merged battle.net account problem, it's worth noting that we also know of many people, including a couple of our bloggers, are still able to log in fine with a battle.net account. At the same time, some posters in the aforementioned thread are saying that they can log on fine when they use an unmerged pre-battle.net account from a family member or roommate.

Once we get a clearer idea of what the problem is or when it's been fixed, we'll let you know.

UPDATE, 10:30 PM EST: Okay, This is Daniel again, and I can log on with a battle.net account. This is the same one that wasn't working not 10 minutes ago, for the record.

UPDATE, 11 PM EST: It looks everything is working fine again. Play on!

Back before Wintergrasp was first introduced, Blizzard told us that they'd finally figured out world PvP. They said to us that they'd figured out how to have hundreds of players fighting in an open zone at a time, without any major slowdown or lag issues. At the time, we were skeptical (and this was even before the instance lag after the WotLK release), and we continue to be: anyone who ducks inside Wintergrasp while things are nuts can tell you that they're far from perfect.

But maybe not for the reason you think. Beatus on Kul Tiras posted a pretty well-written complaint about the layout of Wintergrasp on the EU forums, and new blue poster Ancilorn speaks up with a little insight into just how Blizzard was planning to keep down the lag in WG. They were planning to spread players around to the towers in the southern side of the zone, thus allowing hundreds of players to play, but in a few separate groups conquering different objectives.

The only problem, says Ancilorn, is that there's not enough incentive to split players up -- people who go south miss out on honor and daily quests, and there's not enough reward to make them go that far. He says a retuning of the map will eventually be done to try and spread out the battle a little more.

Crygil posted an important announcement last night concerning the lag and associated performance issues in Naxxramas. Blizzard has made some recent optimizations to Naxx, and they want to know what all of our experiences are like in the instance this week. As such, they're asking everyone to post feedback in terms of performance in the thread over on the official forums.

Now by performance I don't think they mean "My pocket Paladin can't tank."

What they're looking for are detailed reports such as "When I was attempting to do the Heigan dance, my entire group lagged behind a good 5 to 10 seconds. We decided to go and raid Hogger after we wiped for six hours in a row." Or "The Ice Block appeared after Frost Breath when my guild was taking down Sapphiron because of the 30 second lag."

Matt Rossi wrote a great piece yesterday on the need for designing the fights around latency. Hopefully this will become less of an issue as Blizzard works out their backend mechanics; and it appears this change is a major step forward.