I was having this problem. i disabled all the extras in OQ setting including chat and auto accept mesh nodes and have not had a problem since. Not 100% this fixed it but odd coincidence if it wasn't the fix.
Forums are in read-only mode.
Battle.net Disconnects
I don't really have anything new to add to this, but I wanted to include my name in with the folks experiencing battle.net disconnects that are clearly related to oQueue. It's been going on for a couple of weeks now. I disabled oQueue and the problem went away. When I re-enabled, it happened once again. However, I did start using the wow-64.exe link to start WoW. Prior to this, I experienced a 1-2 second lag after battle.net reconnected. After using wow-64.exe to start the game, the lag spikes stopped or were too small to really notice, though I continued to see the random battle.net disconnects.
That said, I do apprecate this addon. Some people in this thread came off way too harsh against the people who put this addon together without any expectation of compensation. I use this addon pretty much every time I log into WoW. Sure there's an issue, sure it's an inconvenience, and the issue is clearly related to oQueue. But that's no reason to treat those who spent their own free time to create this addon like crap. For all that this addon does and how easy it makes fidning groups--and people to join your groups--this issue is relatively small. So from this user, I want to say thank you for creating and maintaining this addon. And hopefully this issue will be ironed out soon.
That said, I do apprecate this addon. Some people in this thread came off way too harsh against the people who put this addon together without any expectation of compensation. I use this addon pretty much every time I log into WoW. Sure there's an issue, sure it's an inconvenience, and the issue is clearly related to oQueue. But that's no reason to treat those who spent their own free time to create this addon like crap. For all that this addon does and how easy it makes fidning groups--and people to join your groups--this issue is relatively small. So from this user, I want to say thank you for creating and maintaining this addon. And hopefully this issue will be ironed out soon.
you do realize that oQueue is one of the few (if not only) addon that actually uses b.net, right? disabling oQueue doesn't indicate that oQueue was the problem... only that you stopped experiencing the problem as you stopped using b.net
Thanks Pephredo.
Also, just to reitterate what tiny has already said: there really are few addons that use Battle.net. When we have oQueue enabled we use Battle.net way more than any other addon, or in any other situation. If there is an issue with Battle.net, it is sure to come out with oQueue enabled as with oQueue disabled, or oQueue not installed, nothing was using Battle.net to, so the issue would go unoticed. While this doesn't mean oQueue is the problem, it might just indicate their is a problem with Battle.net, which only rears its ugly face with oQueue enabled, as the addon uses it. This leaves oQueue with nothing it can do.
Really is a hard thing to diagnose, as we don't control Battle.net so we cant test this HUGE variable in the equation.
Also, just to reitterate what tiny has already said: there really are few addons that use Battle.net. When we have oQueue enabled we use Battle.net way more than any other addon, or in any other situation. If there is an issue with Battle.net, it is sure to come out with oQueue enabled as with oQueue disabled, or oQueue not installed, nothing was using Battle.net to, so the issue would go unoticed. While this doesn't mean oQueue is the problem, it might just indicate their is a problem with Battle.net, which only rears its ugly face with oQueue enabled, as the addon uses it. This leaves oQueue with nothing it can do.
Really is a hard thing to diagnose, as we don't control Battle.net so we cant test this HUGE variable in the equation.
Well then logically it would still have to be oQueue that affects the b.net connection in some way that it causes random disconnects. You factor out oQueue, and b.net stays connected with no problems. You add oQueue back in, and b.net disconnects randomly. It may not be oQueue directly causing the disconnect. Maybe it's simply overload caused by oQueue. Either way, oQueue is involved. It's basic mathematics at that point, especially if it is, as you suggest, one of the only addons that use b.net.
But all that said, today as I was using oQueue to get a Flex 4 group, I haven't experienced any disconnects. So that could mean that it really is load related. I mean, in the end, it doesn't really matter to me. I'm still going to continue to use oQueue. It's a great addon.
But all that said, today as I was using oQueue to get a Flex 4 group, I haven't experienced any disconnects. So that could mean that it really is load related. I mean, in the end, it doesn't really matter to me. I'm still going to continue to use oQueue. It's a great addon.
Essentially what it comes down to is its extremely hard to test. As there arent really any other addons which put any strain on battle.net whatsoever, we can't just disable oQueue, and then enable those addons to see if they also cause battle.net to glitch out.
So we can't clearly see if oQueue is the cause of the problem, or if something in battle.net is the issue.
Its like this. If there is a pothole on the road, but no cars drive on that road. Then nobody cares. But if a housing development is built on that road and now cars are hitting this pothole, suddenly everyone cares. But this doesnt exactly mean that the cars caused the pothole, just now that cars are driving on the road, people are noticiing the pothole.
Obv the road is battle.net, and the cars are oQueue.
Please don't think im brushing it off as oQueue is never at fault. Im just trying to show the perdicerment we are in.
So we can't clearly see if oQueue is the cause of the problem, or if something in battle.net is the issue.
Its like this. If there is a pothole on the road, but no cars drive on that road. Then nobody cares. But if a housing development is built on that road and now cars are hitting this pothole, suddenly everyone cares. But this doesnt exactly mean that the cars caused the pothole, just now that cars are driving on the road, people are noticiing the pothole.
Obv the road is battle.net, and the cars are oQueue.
Please don't think im brushing it off as oQueue is never at fault. Im just trying to show the perdicerment we are in.
So just adding my 2cp, too. I have thes same issue mentioned. I notice it only during peak hours, though. I also have a high number of bnet friends, both people I know and those acquired thru oQ.
So I'm wondering if others have the same observations, which might account for why some of us get this issue and others (I'm the only one in my guild with this issue) do not.
So I'm wondering if others have the same observations, which might account for why some of us get this issue and others (I'm the only one in my guild with this issue) do not.
@warrior03
I definitely notice more disconnects during peak hours. I was on early in the afternoon the other day--mentioned above in my post--and I had virtually no disconnects. There were only a few people on my b.net list that were logged in. But as my b.net list became more populated with active people, the disconnects were more frequent. The most disconnects I experienced were on Tuesday evening, which also lends credence to the theory that it's a load issue. My perception is that there are a lot more people on on Tuesday evening than throughout most of the week following as that's when a lot of guilds raid, just after the server resets.
I definitely notice more disconnects during peak hours. I was on early in the afternoon the other day--mentioned above in my post--and I had virtually no disconnects. There were only a few people on my b.net list that were logged in. But as my b.net list became more populated with active people, the disconnects were more frequent. The most disconnects I experienced were on Tuesday evening, which also lends credence to the theory that it's a load issue. My perception is that there are a lot more people on on Tuesday evening than throughout most of the week following as that's when a lot of guilds raid, just after the server resets.
I have this issue as well. After reading other posts in this forum, I've concluded it is a bnet issue. Bnet can't handle the traffic load. What has worked for me is lowering my friends list. Once my friends get above 65 I start experiencing a problem. Using the bnet launcher seems to exasperate the problem, and the launcher uses bnet to communicate as well. What I've done, is NOT use the bnet launcher, and kept my friends below 60. This is a bnet traffic issue. Blizzard is aware of the issue, but will have to redesign on their end for traffic. Currently they have to many pans in the fire. Adding more servers to handle the traffic isn't the solution, it's actually the coding on their end. They're not worried about fixing it now, because when WoD launches they're implementing their own oQ type of program. So until then...
Keep your friend list below 60. Don't use bnet launcher and the problem goes away. What I find humorous is that while Blizzard realizes the importance of oQ, the Dev's use it, they underestimate how oQ keeps players connected to one another. oQ is literally the only reason many still play the game. The ablilty to find others to play with is vital to the sucess of WoW. Blizzard should be bending over backwards to fix bnet. To do anything possible to keep oQ functional. But egos are egos, and they don't want to admit their game is lacking in such a basic way. Friends, and connections are what keep people playing this silly game. Just my 2 cents.
Keep your friend list below 60. Don't use bnet launcher and the problem goes away. What I find humorous is that while Blizzard realizes the importance of oQ, the Dev's use it, they underestimate how oQ keeps players connected to one another. oQ is literally the only reason many still play the game. The ablilty to find others to play with is vital to the sucess of WoW. Blizzard should be bending over backwards to fix bnet. To do anything possible to keep oQ functional. But egos are egos, and they don't want to admit their game is lacking in such a basic way. Friends, and connections are what keep people playing this silly game. Just my 2 cents.
Ok first off, Tiny STOP blaming B.net for your problems. Second, when I dont use OQueue I STAY connected to B.net ALL DAY, but soon as i turn it on I can't even build a group because it constantly "Disconnects from B.net" and when i turn it off it stops. Last but not least I ALWAYS use B.net with or without OQueue because I have over 10 IRL friends but under 45 total that also play WoW with me and it STAYS on with OQueue disabled all the time I have NEVER seen it off when OQueue is off as well. With that being said QOueue is the obvious problem so instead of blaming B.net, the B.net Desktop, and Blizzard because they DID'NT creat the addon YOU did so take the blame for your faults you created and fix them please, because ATM with this problem I can't even use OQueue so its a worthless addon with this bug... /sigh