I ran AddonSpamFu last night and the addon Athene's Gear Check seemed to be the biggest offender. From one person alone I had recieved over 200k bytes over the course of just Onyxia's lair.
During some of the burstier sends from AGC and LibHealComm 3.0 we had a couple people D/C (people with either bad connections or lower-end computers).
I think its about time to start having prohibited addons in raids, the only person that should have Gear Score or addons like that are the raid leader, and only for FL to determine Ilvl. Also, high-share addons such as Carbonite or the like are unnecessary.
Has anyone determined what exactly LibHealComm does? Would having people disable it gimp our healers ability to heal? If I understand it correctly, its simply an addon that gives visual-heal effects to prevent overhealing; however, if everyone is doing their job properly then that is unnecessary.
Last edited by Feylna : 10/03/09 at 1:40 PM.
Reason: Clarity
Has anyone determined what exactly LibHealComm does? Would having people disable it gimp our healers ability to heal? If I understand it correctly, its simply an addon that gives visual-heal effects to prevent overhealing; however, if everyone is doing their job properly then that is unnecessary.
Well, you are right in that it transmits info about incoming heals. Other addons can use it to show visual incoming bars or numbers, or whatever they like. As a mainly raid healer I wouldn't like to be without it. Especially if you have more than one player raid healing, it really helps a lot to know who the other one is healing and where you need to concentrate on.
If I understand it correctly, its simply an addon that gives visual-heal effects to prevent overhealing; however, if everyone is doing their job properly then that is unnecessary.
It's not as much about overhealing as it is about knowing who is going to die if you don't heal them.
I ran AddonSpamFu last night and the addon Athene's Gear Check seemed to be the biggest offender. From one person alone I had recieved over 200k bytes over the course of just Onyxia's lair.
During some of the burstier sends from AGC and LibHealComm 3.0 we had a couple people D/C (people with either bad connections or lower-end computers).
I think its about time to start having prohibited addons in raids. Has anyone determined what exactly LibHealComm does? Would having people disable it gimp our healers ability to heal? If I understand it correctly, its simply an addon that gives visual-heal effects to prevent overhealing; however, if everyone is doing their job properly then that is unnecessary.
The issue here is that people have been using these addons for some time, and issues have only appeared after this patch. Obviously some changes have been made to the server and/or game and while perhaps disabling addons can assist the issue, it's seems more like fighting a symptom than a cause.
I'm highly doubtful that 12k or something like that over a fight from LibHealComm is an issue that should cause massive instability and constant server boots. It's such a small amount of data compared to what the server already sends each client on a regular basis in regard to the combat log, positions of NPCs and players, stat updates, etc.
If clients are being flooded by data somehow, it's most likely data being sent from the server, not from addons. For instance, a lot of people have huge disconnect issues after a major patch because their client is trying to refill their itemcache and the hanging causes a server timeout.
I posted this for my guild yesterday. Several people who had the DC on pull problem now no longer DC on those pulls. It might not be a fix for everyone, but its worth a shot.
I had this exact issue, normal ping times but random DCs in random locations (during raid encounters, during heroics between pulls, standing around dalaran doing nothing etc) and I could also log back in immediately.
Turns out it's caused by a corruption of the game's data files, namely patch.mpq and patch-2.mpq (in the data subdirectory). I moved them to a separate folder and had the repair tool redownload and repatch everything overnight. The new patch.mpq I got wasn't even the same size as the old one so I have no idea why blizzard's repair tool didn't pick this up in the first place. My old (bad) patch.mpq was 3.911.336 kb, the newer correct version is 3.910.853 kb (euro English version, probably the same as US version)
Since I did this fix I disconnected once, in about 12 hours of playing including 3 raids. Before I was getting disconnected at least once per hour, so for now I'm calling it fixed.
Can other players confirm that their patch.mpq file is 3.910.853 kb (preferably players that aren't having issues with disconnects)? I've been having disconnects on Gormok 25 man heroic, Onyxia (when the whelps spawn) and on Anub'Arak 25 man heroic. I'm interested to see if the patch.mpq file truly is the cause of (or at least contributing to) these disconnects, but I don't have the fastest internet connection on the planet, so I'm a little hesitant to download a 4 Gb file.
Most players in my guild are attributing my disconnects (especially on Anub'Arak) to my computer, which isn't top of the range. Still, my 7800 graphics card, 2 Gb of RAM and single core 2.41 Ghz processor don't seem to disconnect me on much more graphically intense fights, such as Firefighter 25 man, Algalon 25 man, or Twins 25 man. It goes without saying that I'm attempting Anub with minimal or no addons and all video settings on low (1024x768 resolution). I did however come across some video settings that need to be manually added to the WoW config file to take effect:
Outside of a raid, I can already notice a steep increase in my fps (anywhere from 70-100 in cities excluding Dalaran) with this change. If I still disconnect tonight, I think it's safe to say performance can be ruled out as one of the causes of these ToC disconnects (at least for me).
I'm also going to try the Fubar addon spam tracker and for those that are wondering, I've read on the US WoW forums that typing /ignore <name of player with addon spam> will prevent their addons from spamming you permanently. Apparently /ignore blocks even unseen channels of communication.
Very interesting. A number of people in the guild seem to have 3,910,853 (some of which have disconnection problems, some of which do not) and a number have 3,911,336 (including myself).
It seems to be one of those two numbers in almost every case.
Is there any particular reason behind this? It's hard to sort out which is the 'correct' version and which isn't, since not everyone with the smaller filesize seems to have disconnect issues. I find it strange it's possible for the patcher to regularly end up with two distinct and consistant outputs like this.
Very interesting. A number of people in the guild seem to have 3,910,853 (some of which have disconnection problems, some of which do not) and a number have 3,911,336 (including myself).
It seems to be one of those two numbers in almost every case.
I have 3.911.334 (4.005.205.969 bytes), and I get disconnects _sometimes_.
Rather than compare filesizes, why not check md5 (I doubt it, but it might show a difference between the same size files and people that disconnect/don't disconnect) ? I never have disconnected in a 10/25 man, enUS client values below.
Could the different sizes be due to localisation-specific data (e.g. the smaller size is for EU WoW)?
I also have the "correct" file size and suffer constant disconnects in 25-ToC and Onyxia, but I'll do a checksum compare later and see if that reveals anything.
Originally Posted by Heenk
"IRONBRANCH, THE FLOWER BED IS IN DANGER! ASSIST ME!"
I would imagine enGB, mxMX, esES, enUS or whatever would all be different.
e: Actually, most of the localization stuff is in other MPQs, so maybe they should be the same. Although MPQs might not match due to the patching process, as the repair tool verified my WoW install and someone else's while having different md5s.
Addon memory got linked to performance back when WoW was using the original Lua garbage collector. In a nutshell, every once in a while the garbage collector would go through every bit of addon memory looking for variables, etc that were no longer in use and would dump them from memory. If you had your full addon load this would be a significant lag spike.
The incremental garbage collector included in one of the WoW updates (TBC / 2.0?) spreads this out over time. So a giant set of addons will still slow you down but won't cause those massive lag spikes. Most of the addon performance issues lie elsewhere these days, though having tons of addons increases the chance that one or more of them will misbehave and cause issues.
We've made some changes to the Thorim encounter in Ulduar to reduce the amount of information sent when you initially start the fight. This should reduce the amount of lag and disconnects that some players experience when starting the encounter.
If you have completed the Thorim encounter after today (10/6) and are still experiencing issues when engaging the mobs in the arena, please post in this thread.
Please keep this thread on topic, and only post if you are still experiencing disconnects during the Thorim encounter.
If that fixes the disconnects on Thorim they could apply the same fix for Gormok, right?
Cartographer and the Carbonite Suite are especially spammy as well. I'd hesitate calling "HealComm" spammy, as that implies that it isn't provided a valid raid purpose. The communicative value of knowing who is healing what is worth a few 10s of kilobytes an hour.
Back in the SSC days I played Addon Nazi for our guild and had the guild disable several especially bad ones and had notable guild performance increases. However, even at its worst, the amount of data in that channel should not be disconnecting someone on their own. The usual suspects for a disconnect when reconnection midfight has to do with the game trying to redraw frames while significant amount of data is flying around. Pitbull or other UI mods are especially harsh about this, as they seem to react differently to drawing their frames during combat than out.
Altering your raids addons to regulate a few people's problems is probably barking up the wrong tree though. Try looking for the more likely culprits, as well as the ones least likely to generate discontent before going that route.
If that fixes the disconnects on Thorim they could apply the same fix for Gormok, right?
Quite possibly. Like I mentioned above, it's far more likely that it's the servers themselves generating the data choking the clients rather than mods. The majority of mod setups simply don't generate a huge amount of network traffic compared to what the game server itself is capable of pumping out.
Pitbull or other UI mods are especially harsh about this, as they seem to react differently to drawing their frames during combat than out.
Unit frame add-ons are very restricted in what they are allowed to do during combat. Essentially, only things the built-in WoW unit frames offer are allowed. Frame creation and deletion, sorting, etc. are not. Unit frame add-ons are absolutely not the reason for disconnections.
An update on my disconnect issues: Problem seems fixed! I've begun ignoring all players in the raids I attend, except the officers and my disconnect problem has disappeared. By disappeared, I mean no dc's on any fight in ToC 10MN, 10M HC, 25MN, and 25M HC including Gormok the Disconnecter! I tried all of the other suggested fixes, with little result (reg fixes, wtf/cache/interface folder deletion, upgrading the my ADSL linespeed, driver updates, firmware updates, the list goes on). I've managed to greatly increase my fps and slightly reduce my ms with these changes, but I still disconnected in ToC 25 and ToC 25 only as many other players have reported. I'm interested to hear if many others have had similar success by ignoring their raid members? If so, it's time to push Blizzard for an interface option to block addon spam from other players.
Side Note: I still "feel" as if a dc is incoming at some points in ToC 25. Usually, this is marked by a high influx of data, such as the beginning of the raid aoeing adds on Anub'arak. My spells highlight for as much as 1 second while chain casting, so I immediately react by stopping all casts and facing my camera to the ground for 3-4 seconds. I don't know if this is due to my refusing to ignore 3-4 raid members (namely officers who will shout at me ), but my performance in raids is rarely hurt and best of all, I stay online.
Seems like it has worked for the most part, our main DCers only suffer the stagger effect like most of us now. Of course until now we are still highly wary of their situation, especially since we need their performance in heroic.
Obviously it needs a little more time to tell if this is the fix or just an attempt.
10/01/09, 12:22 PM
), but my performance in raids is rarely hurt and best of all, I stay online.
Similar Threads
