Printable View
I LOVE the item bar, i use it A LOT while leveling up and questing on all my teams! The last few days i seem to be having some kind of lag, I place an item in the bar on my main, and sometimes it takes several minutes to appear in my slaves bar. It seems to be random, sometimes it works perfectly and others it can take a few seconds to many minutes to finally appear in the salves item bars. Any ideas?
the only times i get slow response (like jamba hp bars updating slow etc) is after i pushed some info, or whenever there is alot of traffic in the jamba chat channel.
Haven't seen it specifically for the item bar though.
Do you have Jamba-Quest Watcher enabled? If so, turn that off and see if that speeds things along... Please let me know if it does or if you do not have Jamba-Quest Watcher enabled.
I tried turning off quest helper and it still will not load the item in slaves for several minutes. It always works great for the first hour or so when i log in, but the longer I'm on with a team, the longer it takes to load an item in the salves bar. Turning off QH seems to help a little, but over time, even with QH off it will start to lag like I have explained.Quote:
Originally Posted by Jafula
I love item bar and use it constantly. Keep my drinks and quest items aslong as equipping new gear on all toons.
I have not come across the issue you have. I've tried turning on Jamba-quest and updating alot of features while doing it... but its almost instant still.
I heard a rumor one time [I have no source and I'm too lazy to Google it so it is currently a rumor] about how the background FPS affects the "pipeline" of addons that use channels, such as Jamba. Perhaps we can all gather 'round the fire while I lightly strum this guitar and we can all share what our background FPS is set at. Anyone care to go first? I cannot go first as I do not use Jamba [don't hate me Jafula].
Lol, Fenril, I don't hate you.
You are correct, a background FPS of 20 will halve the amount of data sent. Not good really... Jamba uses this library: http://www.wowwiki.com/ChatThrottleLib
Easy fix is to set your background FPS on everything to a minimum of 21.
Medium fix is for you to edit every occurance of ChatThrottleLib.lua in your wow addons folders and change this line to a lower value:
ChatThrottleLib.MIN_FPS = 20 -- Reduce output CPS to half (and don't burst) if FPS drops below this value
Harder fix is for me to work out how to override the library in Jamba.
I'll try this.. i have a super fast pc though, i can box 10 on this PC ( and have plenty of times) Also this item bar lag thing is new, it never used to do it. Also, the fact that it gets worse over time? it is instant for the first hour or so I'm logged in.Quote:
Originally Posted by Jafula
Hmmm, the lag over time is bizarre. I'll keep that in mind when I'm next doing addon channel stuff.Quote:
Originally Posted by Lyonheart
I have my background fps set to 10, maybe I should set it to 21?
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?
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.
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.
Yes, that would help at lot, assuming your computers can handle the extra graphics load.Quote:
Originally Posted by Maxion
No, I don't think so given the item starts its cooldown.Quote:
Originally Posted by DLoweinc
The quest watcher is probably sending a bit too much traffic. Try turning it off and see if that helps.Quote:
Originally Posted by Siaea
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.Quote:
Originally Posted by Maxion
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.
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.
Some drakes not mounting is because your toons are most likely all standing on top of each other, the vehicles don't like to all start in the same spot, so only some end up getting mounted.Quote:
Originally Posted by DLoweinc
The solution is to hit your spread out keys first.
Quote:
Originally Posted by Maxion
Thanks I'll try this, I seem to get Oculus as my first "random dungeon" each day, have for four days now
I had this issue as well, but i believe it's unrelated to jamba.Quote:
Originally Posted by DLoweinc
basically, if all the toons are stacked and all call their drake, it seems some get confused and try the wrong mount or something.
Basically 5 drakes come down, but only 2/3/4 get mounted.
try and spread your toons a bit and you'll never have the problem again, they'll all jump on their own mount correctly :-)
This is probably the iLevel in your gear. That and acheivements are what WoW used to set a "random" instance. Not sure how to fix unless you can do ICC.Quote:
Originally Posted by DLoweinc
Stuck this info in the Jamba - Getting Started thread. Good stuff to know about ChatThrottleLib.lua, I'll have to play around with that when I come back to WoW.Quote:
Originally Posted by Jafula
been awhile since I started this thread. I wanted to wait and try all the suggested fixes. I have lowered my background FPS, turned off quest watcher..etc. I have two issues that seem to be related. As time goes by I get longer and longer delays for both my item bar, as I have discussed, and when i click on quest dialog, just like with the item bar lag, I get delay. Both the item bar and quest interaction between alts works perfect for about 20 minuets than starts to delay.
system specs are
Windows7 64 ultimate
core i7 920
SSD drive
12gigs ddr3
Gf 280GTX video card
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.
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.
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 :)
does questhelper remove the bliz default one?
This did indeed fix my problem.Quote:
Originally Posted by Maxion
Thanks Maxion and Zub
I do not think it gets rid of everything but I have not used QH since the Blizzard Quest tracker changedQuote:
Originally Posted by Lyonheart
Quest helper does remove the blizz tracker.
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.
Edit: And if all your toons are in a party - pushing settings and other comms functions are a lot faster, including the quest watcher.PHP Code: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
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".
Nice. Thanks again for the fixes and this thread has been 'fixed' LoL.
SWEET! i miss QW! Ill be happy to have it back!