Item bar lag?

[Jafula]

I have my background fps set to 10, maybe I should set it to 21?

Yes, that would help at lot, assuming your computers can handle the extra graphics load.

Wow odd behavior indeed, the only time I've had an issue with the item bar is in Oculus with the drakes. Everyone uses it but only two get mounted, the other three have their drake on a "use cooldown" and I have to wait about 10 seconds and then manually click them.

Could this be a chat throttle lib thing too?

No, I don't think so given the item starts its cooldown.

I just recently updated to the newest Jamba, and noticed severe lag sometimes now with slaves accepting quests, completing quests, and this is the annoying one: constant "Follow broke" messages, even when I can see they're all following.

If it helps, I do have the quest watcher enabled.

The quest watcher is probably sending a bit too much traffic. Try turning it off and see if that helps.

Too much traffic in the addon channel causes a lot of issues like this.
I hope Jafula can minimize the amount of messages that are sent through the channel since it adds up to be a lot, and i think sam was saying something somewhere about some rather unnecessary looking messages being spammed there.

Yup, too much traffic is the cause. I made a lot of improvements in 0.5 (from 0.4) to minimize traffic. Unfortunately it seems that the new Jamba Quest Watcher can be a bit heavy on the traffic. I'll have a closer look at that when I get a chance.

Nah, Sam, was looking at the team online channel which is totally different to the addon channel. Also Sam had turned on the debug switch which had caused him to see a heap of debug messages.

[Dooz]

I've been getting "I am Attacked," "Follow broken," and sometimes I have to reset the group loot because the wrong toon is looting (slaves are opting out). My bgfps is set to 15 I'll bump it up to 21 and see what happens.

[moosejaw]

There is a communication logjam on your setup for sure. Disabling Jamba Quest Watcher cured it for me. Keeping a seperate keybind for "/console reloadui" (on all instances) for when it gets bad is also a good idea. That will reset all the comms for you and help with troubleshooting your changes.

Double check that you unchecked Quest watcher in the Jamba settings and pushed it to all the slaves.

I don't recall if I set my background fps to 25 or 20. I'll have to check that tonight and correct all of my team settings if they are too low.

Good luck Lyon and keep the updates coming.

[Maxion]

I tried setting my background fps to 21 and quested for a while on some lowbies with the watcher on, and after a while I ended up having to manually click for quests in all the windows pretty often since the communications channel was too clogged.
Definitely going to keep the watcher disabled until this is fixed, really nice when it works though, but I still hate being unable to click anything behind it, especially since it prevents clicks for its full size regardless of how many quests are actually being tracked.

[moosejaw]

I went back to Quest helper for quest tracking for now. Reasons:

Quest watcher- comm issues, I don't want to scroll the list, the double watch list with default blizz tracker.

Blizz tracker- doesn't do party, quirky positioning depending on addons used, will always be stable, list extends too far sometimes and overlaps my UI.

Questhelper- good filters, party tracking on one line, easy to move, my nine year old can see all his missing quests easier than with the Blizz tracker. Kids these days

[Lyonheart]

does questhelper remove the bliz default one?

[alcattle]

does questhelper remove the bliz default one?

I do not think it gets rid of everything but I have not used QH since the Blizzard Quest tracker changed

[moosejaw]

Quest helper does remove the blizz tracker.

[Jafula]

For those that are interested:

I have added a new option to Jamba - Core: Communications called "Boost Jamba to Jamba Communications**". Basically it changes the settings in ChatThrottleLib to be faster at the risk of disconnections... The option will be on be default but you can turn it off.

function AJM:BoostCommunication()
    if AJM.db.boostCommunication == true then
        -- 2000 seems to be safe if NOTHING ELSE is happening. let's call it 800.
        ChatThrottleLib.MAX_CPS = 1200 -- was 800
        -- Guesstimate overhead for sending a message; source+dest+chattype+protocolstuff
        ChatThrottleLib.MSG_OVERHEAD = 40
        -- WoW's server buffer seems to be about 32KB. 8KB should be safe, but seen disconnects on _some_ servers. Using 4KB now.
        ChatThrottleLib.BURST = 6000 -- was 4000
        -- Reduce output CPS to half (and don't burst) if FPS drops below this value
        ChatThrottleLib.MIN_FPS = 10 --was 20
    end
end 

Edit: And if all your toons are in a party - pushing settings and other comms functions are a lot faster, including the quest watcher.

[Jafula]

More Quest Watcher updates. I found a significant bug where everytime you completed a quest, every toon was sending out its complete watch list all over again, which causes a significant amount of addon traffic. I've knocked this one on the head, so the next release of Jamba should have a nice fast quest watcher.

I've also optimised the way Jamba sends messages and commands. Previously in a 5 person team, Jamba would send the same command 5 times to each toon. Now if all your toons are in a party/raid, Jamba will only send the command once. This makes for very quick "Push Settings".