launched with Wow-64.exe without loader running, seems to cure the issue

Happy to hear it worked :)

guess what

problem is back, but it is not that frequent now (not running loader at all, just wow 64 exe)


also sometimes during rbg's for example, bnet goes off, than comes back on, but untill the reload, oq does not get that it is back, and premade gets lost (waitlist disapears) reloading that results in fresh new empty premade

Uhhh this is wrong, I get FPS stuttering and I don't even have the battle.net desktop client. At all, it's not on my computer. I always open it from the wow.exe and only use the launcher for updates. THe oqueue add-on consistantly uses more and more MB the longer it's on in game, and is the only add-on I've found causing the FPS stuttering WHILE in Arena/BGS. If you look into the oq general chat you see tons of people spamming lines of codes which I assume is how this add-on works, between that and b-net tags in general. Regardless, whenever I do arena WITHOUT oqueue I never have this problem! So, seems there's more than one SEPERATE issue but the issue is indeed coming from Oqueue as well! Don't brush it off and say 'sorry, nothing to fix' just because YOU personally cannot replicate the problem.

At no point did I "Brush it off", or say there was nothing we could do. I merely suggested that for the time being; users whom may be having this issue, try a fix which has helped some other users.

But hey, read it as you wish.

You did brush it off, you said there's nothing for you to fix implying the problem is not in the issue with the poorly coded add-on you have here. Not only does it have an abundance of glitches, but it has bloating issues and obviously issues causing FPS stuttering as well.

**SIGH**
Guess i did say that (in a earlier post).

Im not gunna sit here and act like the addon is perfect. But im also not gunna sit here and defend it against people who get it for free.

Anyways, for the time being we are un sure where the issue is, if there is one. If we find it, we find it and well fix it. Until then hang tight.

Second thought:

Look at it this way: Battle.net normally has little to no load on it. Other than oQueue traffic, the load which is put on Battle.net is minimal (whispers and chats and such). As oQueue gets more popular, more and more strain will get put on Battle.net. If Battle.net cant stand the load, well then theres really not much we can do as we don't control Battle.net. oQueue has features and functions which try to limit the amount of traffic it pushes across Battle.net but for the most part, the communication it does: it needs to do.

and how does battle.net contribue to FPS stuttering, or oqueue adding people on your waitlist to your battle.net friends that you didn't even invite to a group yet? How about how laggy oqueue is, sometimes you invite someone and it does absolutely nothing or you hit wait list and does nothing and maybe 5 minutes later it does it.

oQueue adds people to your friends list when they hit the find mesh button.

Ex: I hit find mesh, the score keeper gives me the btags of 5 people who were online in the last hour. If those people are online then we are auto friended.
Ive never seen oQueue just add someone to my friends list when they were on my waitlist without me clicking invite.

When you press waitlist, or invite, that information is sent in a friends request, which uses, you guess it BATTLE.NET. If Battle.net is glitching out or is under heavy load, this information is delayed and it takes awhile to get from one person to another, if the request / message even gets there in the first place.

I have no idea about the FPS stuttering. I don't see it. My game runs fine. So does everyone else who we communicate with on a regular basis. There may be a additional variable which doesn't exist for us, so kind of hard to test for it when we don't have the issue.

You know, nobody is forcing you to use oQueue right? If its not working out for you, then i suggest exploring alternative solutions.

1. type /etrace
2. watch the messages being processed
3. go to a training dummy
4. feverishly attack the training dummy and watch the etrace window

even if 50 msgs/sec were constantly going thru oqueue, it's still nothing compared to the number of messages being processed by the wow client in a raid or rbg

Ah yes, the whole 'go away if you're having issues with the add-on working properly' seems you're really out of ideas and don't have a fix and probably won't ever. The animosity when I'm just trying to get an issue within the add-on resolved when you keep giving the run around about such things and about how glitchy and badly coded it is. If you're offended by this, then no one is forcing you to keep oqueue running.