Oh, oops. I didn't see this forum. Thank you for reposting, Cybear!
OGear displaying the wrong gear item level in Heroic raids
With the new raid setups, oGear seems to view items dropped in Heroic SoO (old normal level) as Flex-level gear. I've gotten several pieces out of Heroic SoO on a character over the past couple of days, and all of them display as item level 540 instead of 553 for regular Heroic or 559 for Heroic Waforged. The items from Normal (old Flex) display correctly as item level 540. My oGear is up to date. Is anyone else experiencing this problem?
I have nothing really new to report other than to add myself to the list of folks experiencing stuttering lag. When I disable oqueue, it disappears, and I, like others, have taken to turning of oqueue until I need it. I don't have much technical experience, so I can't offer much more than that.
The lag is not major. Most of the time, I can live with it. It's not even long periods of lag. The screen stutters--I'll have several seconds of 60-80 fps with a fraction of a second dropping to ~15-25, and it continues to happen until I disable oqueue. I have noticed that it even happens when I'm not in a busy area, such as away from the shrine and out in a low population part of the world. When I'm running the group, waiting for my wait list to fill, the stuttering happens more often. If I'm merely looking up groups to join, it doesn't seem to be as bad. It's also not as bad when I'm actually in the raid, though I do still notice some stuttering.
The lag is not major. Most of the time, I can live with it. It's not even long periods of lag. The screen stutters--I'll have several seconds of 60-80 fps with a fraction of a second dropping to ~15-25, and it continues to happen until I disable oqueue. I have noticed that it even happens when I'm not in a busy area, such as away from the shrine and out in a low population part of the world. When I'm running the group, waiting for my wait list to fill, the stuttering happens more often. If I'm merely looking up groups to join, it doesn't seem to be as bad. It's also not as bad when I'm actually in the raid, though I do still notice some stuttering.
@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.
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.
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.