All im seeing from your posts is complaining. We are aware there might be an issue.
If we can fix it. We will. End of story.
Posting about how badly coded oQueue may be is not constructive.
I won't tolerate futher posts of that nature unless they hold real constructive criticism.

I gave constructivce criticism. I said, stop sucking at coding, learn to fix issues and quit pushing on the issues being something else that isn't oqueue.

the b.net disconnects have been happening over the last 10-14 days.

oQueue hasn't been modified since april 19th... 25 days ago. meanwhile, blizzard has pushed a few patches (and some hotfixes) in the same time frame.

yea... must be oQueue.

The issue I'm talking about has been happening over the last 5+ months.. oqueue has been modified a lot since then, and so has WoW... Yeah, must be WoW even though in my previous thread I mentioned that I completely cleared my UI and made sure it was oqueue causing the problem and it was.. Never happens to me without oqueue on.. Yeah, must be oqueue. But thanks for closing my other forum account because I won the argument.

@modpowerabuse
what problems are those? this thread has 3 or 4 different symptoms being tossed around. if you have time drift issues, that is due to your system clock being off. if you have bnet disconnects, that is most likely due to bnet gltching out the last 10-15 days. if your having fps fluttering standing alone in the middle of nowhere, with no other addons, then it would be due to oQueue processing the messages it receives... the number of which, per second, you can see on the setup tab. if your system can't process 10-20 messages in a second without fluttering, it's not oQueue... even if they are oQueue messages.

if you have all other addons off an experience the problem, yet I do not, that leaves your system or the number of people you're receiving messages from is much higher then mine.

of course, if you actually wanted this resolved, you'd hop on vent and we'd figure it out.

"sucking at coding" is not constructive criticism.

We are not here to argue with you. There is no argument. We are here to resolve issues if we think we can. If we can we will. If we cant then we won't. If you cant handle that and act appropriately then we will take whatever action we deem appropriate.

Ah yes, because closing someones account without any previous record on the forums is appropriate action. Idgit. Over react to me calling something out about the add-on. As stated previously, I ruled everything else out and the only thing that causes FPS stuttering is Oqueue. Without it, the game will run fine in arena and battlegrounds! But egads, you say it must be my computer causing the problem! Nope, seems oqueue doesn't want to work properly with my machine and others have mentioned this FPS stuttering hence this thread in general! Especially considering I don't use, nor have I ever used the battle.net desktop client. Huh! How odd is that, ruling out all the things you say it is but oqueue!

i award you no points

Hi,

just thought I'd chip in. I've been testing by running WoW without launcher (NOT the desktop client). But using Wow-64.exe to run the game also doesn't help. Still getting random B.net disconnects.
I've also been testing by removing any btags with cyrillic letters in btag or character name (sorry Russians), but there is no difference, so character encoding doesn't seem to play a role for me.
Is there any way to use the older version of oqueue (prior to 1.8.x, for example 1.7.8) without having the warning about upgrading popping up? I would like to test it, because I don't remember getting the disconnects in that version.

There would be no way to get the warning to not popup. Im also not sure if you would be able to waitlist for groups, and you might always find yourself having a raid lockout conflict. It looks like the lockouts were added in 1.8.8. If you didnt do pve but tried to get into pvp groups it might work.

We don't normally handout old versions of the addon by a rule of thumb so ill have to check on this.