But before actually posting the ticket, please use the ticket trackers search function, see if there has been a ticket for the same thing.
The Twilight Blast /say has been declined, since it'd be way spammy.
Spammy how? This is the only reason my guild is stuck with DBM (believe it or not), and i don't get how it can be spammy. It's just a chat bubble after all. I know there's a personal warning, but isn't that just for when you get the Blast targeted on you? Not someone standing close to you.
Edit: And you only see the bubbles if you're actually too close to a person.
Ah, I do see now that that was showing my UI latency rather than world latency. I will have to do some more testing and fiddling.
Here is the difference that I'm feeling. Before, I could just do two-taps of my button to cast (I detest button mashing). The first would hit *just* before entering the red area, the second just after. My casts went off just fine, unless I was having latency issues where it was going up/down mid-cast of course. Last night, using the same method, a lot of my casts weren't getting queued up. I had to button mash (at least 4 taps) to get the spell to cast, and there seemed (though it may have just been me, being thrown off already) to be a *slight* delay in the cast bar changing over to the new cast.
Happened a few times for me aswell (Hunter spamming steady shots). Sometimes the castbar is lagging behind, but i see myself firing the shot but the castbar shows up a little late and it's not visible for more than a few milliseconds.
Some taint when using questitems in combat (similar to QuestItemBar):
1x <event>ADDON_ACTION_BLOCKED:AddOn 'QuestItemKeybound' tried to call the protected function 'SetOverrideBindingItem()'.
<in C code>: in function `SetOverrideBindingItem'
QuestItemKeybound-v0.1\Core.lua:22: in function `?'
CallbackHandler-1.0-6 (Ace3):147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[5]":4: in function <[string "safecall Dispatcher[5]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[5]":13: in function `?'
CallbackHandler-1.0-6 (Ace3):92: in function `Fire'
AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>
---
Possible to completely ignore any quest item scanning in combat perhaps? Also, this happens even if the item i'm using is allready keybinded.
Nice, keep it simple though, it doesn't have to scan for questitems other than when you actually use one. Also, ingame options isn't exactly needed, you could set the keybinding of your choosing in a simple LUA setting.
I'm looking for a nice and very simple addon that automatically keybinds the last questitem used to a key of your choosing. Lets say i use [Random Questitem] manually by clicking on it from my inventory. This addon/macro would automatically keybind this to a key, for example X to make it faster than having to manually click it from the bags all the time. There are a few addons that can do this, like QuestItemBar (http://www.wowace.com/addons/questitembar/), but this is a bit too heavy for my needs.
I know my test was far from practical, but it was impromptu and there weren't many other fights where I could fool around without a UI. I'm running an i7 920 @ 3.0 and an HD 4870 which both should be more than capable of handling WoW at 30 fps.
You'd probably get the same performance on an old dualcore/8800GTX, WoW is just simply poorly optimized to support high end hardware. I'm hoping we'll see some improvements in Cataclysm, i fear the water effects will be another FPS killer like the Shadow effect currently is though.
Uses ~2-3 seconds of CPU compared to 15-20 from Skada. Also, you might wanna convince your guild to switch over to DXE, it's the lightest bossmod out there from what i've tested.
Well, you could install Optionhouse (WowInterface) to monitor CPU usage and compare it against similar addons. This doesn't tell you WHY it uses too much CPU though, so i guess you should make an attachment with the lua file from your addon, so people can look over the code and give a few hints where needed.
When opening the bank or clicking the config button:
1x AdiBags-v1.0-beta-2-5-gb708a43\widgets\ContainerFrame.lua:502: attempt to compare two boolean values
<in C code>: in function `sort'
AdiBags-v1.0-beta-2-5-gb708a43\widgets\ContainerFrame.lua:548: in function `LayoutSections'
AdiBags-v1.0-beta-2-5-gb708a43\widgets\ContainerFrame.lua:219: in function `UpdateAllContent'
AdiBags-v1.0-beta-2-5-gb708a43\widgets\ContainerFrame.lua:153: in function `RegisterUpdateEvents'
AdiBags-v1.0-beta-2-5-gb708a43\widgets\ContainerFrame.lua:200: in function <AdiBags\widgets\ContainerFrame.lua:195>
<in C code>: in function `Show'
AdiBags-v1.0-beta-2-5-gb708a43\AdiBags.lua:330: in function `Open'
AdiBags-v1.0-beta-2-5-gb708a43\AdiBags.lua:529: in function `?'
CallbackHandler-1.0-5 (Ace3):147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0-5 (Ace3):92: in function `Fire'
AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>
Locals:
(*temporary) = <table> {
1 = AdiBagsSection1 {}
2 = AdiBagsSection6 {}
3 = AdiBagsSection7 {}
4 = AdiBagsSection8 {}
5 = AdiBagsSection10 {}
6 = AdiBagsSection3 {}
7 = AdiBagsSection4 {}
8 = AdiBagsSection9 {}
9 = AdiBagsSection5 {}
10 = AdiBagsSection2 {}
}
(*temporary) = <function> @ AdiBags\widgets\ContainerFrame.lua:498:
(*temporary) = AdiBagsSection5 {
dirtyLayout = false
total = 1
0 = <userdata>
slots = <table> {}
width = 1
buttons = <table> {}
count = 1
name = true
category = true
height = 1
Header = <unnamed> {}
freeSlots = <table> {}
container = AdiBagsContainer1 {}
}
(*temporary) = AdiBagsSection5 {
dirtyLayout = false
total = 1
0 = <userdata>
slots = <table> {}
width = 1
buttons = <table> {}
count = 1
name = true
category = true
height = 1
Header = <unnamed> {}
freeSlots = <table> {}
container = AdiBagsContainer1 {}
}
---
Using Beta 2.5
Also a question regarding bag updating while they're closed. As a hunter, whenever i fire an arrow, the bag updates causing a slight spike in cpu usage (i used other bag addons in the past that had way higher spikes than i get with this though). Would it be possible to ''stop'' listening to bag updates whenever the bag window is closed (or the user is in combat)? Not a huge issue currently, but it's a suggestion.
0
Spammy how? This is the only reason my guild is stuck with DBM (believe it or not), and i don't get how it can be spammy. It's just a chat bubble after all. I know there's a personal warning, but isn't that just for when you get the Blast targeted on you? Not someone standing close to you.
Edit: And you only see the bubbles if you're actually too close to a person.
0
0
Happened a few times for me aswell (Hunter spamming steady shots). Sometimes the castbar is lagging behind, but i see myself firing the shot but the castbar shows up a little late and it's not visible for more than a few milliseconds.
0
1x <event>ADDON_ACTION_BLOCKED:AddOn 'QuestItemKeybound' tried to call the protected function 'SetOverrideBindingItem()'.
<in C code>: in function `SetOverrideBindingItem'
QuestItemKeybound-v0.1\Core.lua:22: in function `?'
CallbackHandler-1.0-6 (Ace3):147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
<string>:"safecall Dispatcher[5]":4: in function <[string "safecall Dispatcher[5]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[5]":13: in function `?'
CallbackHandler-1.0-6 (Ace3):92: in function `Fire'
AceEvent-3.0-3 (Ace3):120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>
---
Possible to completely ignore any quest item scanning in combat perhaps? Also, this happens even if the item i'm using is allready keybinded.
0
0
0
0
You'd probably get the same performance on an old dualcore/8800GTX, WoW is just simply poorly optimized to support high end hardware. I'm hoping we'll see some improvements in Cataclysm, i fear the water effects will be another FPS killer like the Shadow effect currently is though.
0
Uses ~2-3 seconds of CPU compared to 15-20 from Skada. Also, you might wanna convince your guild to switch over to DXE, it's the lightest bossmod out there from what i've tested.
0
0
Started showing up out of nowhere, got quite a few of those.
Edit: Pops up whenever i open the bags now. Also noticed that there's an empty space between my Epic and normal white arrows in my bags.
0
0
Using Beta 2.5
Also a question regarding bag updating while they're closed. As a hunter, whenever i fire an arrow, the bag updates causing a slight spike in cpu usage (i used other bag addons in the past that had way higher spikes than i get with this though). Would it be possible to ''stop'' listening to bag updates whenever the bag window is closed (or the user is in combat)? Not a huge issue currently, but it's a suggestion.
0
After opening the configuration, then closing it, the ''esc'' button doesn't bring up the game menu anymore.
0
1x AdiBags: missing item class and subclass of 774:
AdiBags-r20100512085922\Localization.lua:51: in main chunk
---
Also, whenever closing the bag with ''esc'' the game menu pops up instead of just closing the bags.