Battle.net Disconnects

It has been brought to our attention that a number of users are experiencing frequent Battle.net disconnects and fps stuttering while using oQueue. This issue appears to effect those using oQueue, and those not using oQueue aswell.

If you use the battle.net desktop client to launch your WoW, we recommend running WoW without the battle.net client, and launch it directly from the WoW icon.

Some users have confirmed that this has stop'd their disconnects and stuttering issues. Please let us know if this helps.
Rwait made a intersting point earlier that the issue may be related to using the battle.net app:
http://solidice.com/threads/oq-not-working-again#post-2523
CONFIRMED: Did exactly what that poster did. Closed the battle.net desktop app, logged out, then logged in again through just the wow client. No battle.net issues at all!

--------------------------------------

oQueue version 1.9.0 has made changes to hopefully address this issue.

Just so you're aware, in my case, I have not been running the battle.net desktop client at all and I have been experiencing both issues. I have 93 battle.net friends (though this fluctuates above 90 frequently).

I am running the 64-bit build of WoW in Windows 7. I have a theory that possibly the people whose issues appeared to be fixed by running WoW without the battle.net client may be using the 32-bit build. Note that this is just a theory I have not tested.
well i like using battle net app so If is possible to fixe that for next patch will be great! thanks for the team who support us!
Theres really nothing for us to fix as far as this goes pmmsr, the issue is with the client most likely. These issues are effecting people whom use oQueue and whome don't use oQueue.
I dumped the BNET client a while ago and I'm still having this issue quite often. There's absolutely something funky going on. If you say you've seen it happen non-oQueue, that's interesting. I wonder what's going on.
I've seen people report it happen to them, and they do not run oQueue. I don't experience the issue, so I am just reporting on what others have reported to us.

There has been some reports on both battle.net and mmoc that non oQueue users are experiencing similar issues.
Hi there,

I've been having this problem with oQueue since the last few versions, I think ever since 1.8.x (if I recall, 1.7.8 was ok).
I am NOT using Battle.net desktop client.
If I disable oQueue, the disconnects are gone.
I have currently 30 btag friends added, all except 1 added via oQ.

One other thing I noticed is I often get quite a large "time drift" discrepancy. It can get as much as 15+ minutes. Sometimes logging off and back in help, other times not.
I also noticed this getting a bigger problem in later versions. Sometimes it takes up to a minute (usually a few dozen seconds) for the addon to register when I put myself in a queue (or cancel it).

At least in my case, the culprit for disconnects is 100% oQ - if perhaps in union with another addon, can't say, but as I said, I only get the disconnects when I have oQ enabled.

Still, one of the best addons around, kudos to everyone involved.

Just so you're aware, in my case, I have not been running the battle.net desktop client at all and I have been experiencing both issues. I have 93 battle.net friends (though this fluctuates above 90 frequently).

I am running the 64-bit build of WoW in Windows 7. I have a theory that possibly the people whose issues appeared to be fixed by running WoW without the battle.net client may be using the 32-bit build. Note that this is just a theory I have not tested.
Win 8.1 64bit client 64bit as well, exiting new launcher does not help to resolve the issue
Are you just closing the client, or starting WoW from the wow icon.

What seems to be (speculation) helpful; is running WoW from the icon labeled WoW64.exe in your World of Warcraft folder, if you are running the WoWLauncer, then there is a possibility the launcher is running the app.
launched with Wow-64.exe without loader running, seems to cure the issue
Log in to leave a reply.