RangeDisplay
Estimated range display. Type /rangedisplay for configuration or /rangedisplay locked to lock/unlock the frames.
RangeDisplay is a simple range display addon. It is using spell range, item range and interact-distance based checks to determine the approximate range to your current target. Due to the whackyness of interact-distance based checks, recent versions only use those when spell/item based checks are not possible . The display can be configured in many ways (displaying only the max range, adding border and background, etc).
Currently you can set up RangeDisplay to show your current range to your target, focus, pet and mouseover units. The mouseover unit range can be anchored to the mouse or placed at a fixed position.
New in v3.8.0: It is possible to add sound notifications to "range sections" (similar to color setting). The sound will be played when entering the section. If two sections have the same sound file attached to them, then the sound is not played again if switching between the two sections.
This sound notification is enabled by default for the target unit's close range section.
Displaying max range only: if you want to display only the maxRange, you need to set Text to "%d" and tick the Reverse option for the section(s).
Open /RangeDisplay/libs/LibRangeCheck-2.0/LibRangeCheck-2.0.lua
Go to line 440 and change it:
from: local spell, rank = GetSpellName(i, BOOKTYPE_SPELL)
to: local spell
That will fix the LUA error and RangeDisplay will work properly
Wont be just this addon. Another hud type addon gave me the same problem, Icehud. Might be something with ace on the ptr?
To test,
- I removed all addons except this
- cleared the wow cache, interface, wtf.
- Tried to quit and come back with the windows already locked.
- I reboot the computer
- disabled any programs running in windows.
- I tried logging in without targeting anything, and with targeting something quickly.
- I tried starting the game right after clearing the wow cache, and starting without clearing the cache.
- Tried to start the game with launcher.exe, or wow.exe.
To duplicate, moving forward was a good way for me to test if the game lags every half second. The freeze was gradual, and noticible 5 seconds after logging in. After 15 seconds, the game froze more noticibly but stayed the same from then on. Quit game completely, and come back, and same thing happens.
I noticed there was no problem after I run /reload. I noticed there was no problem if I logged out and back in. I noticed it works great in patch 3.3.5.
I checked your rangedisplay.lua, and onUpdate() and update() are not running when it freezes so must be somewhere deep in the ace db. Any ideas where in code might be running something every 0.5 seconds ? Thanks
This issues is most probably caused by LibRangeCheck's item info caching function. Probably it "lags" for nonexistent items. I'll have to check which item(s) cause lag, or do the caching in some other way. It might be that the problem will not happen on live servers where these items will probably be available on the server (not sure about that though).
Thanks for the report, I'll look into it.
cheers,
mitch
Update: I just got informed that blizz changed the way GetItemInfo works, it'll now poll the server instead of returning nil if the item is not in the local cache. I'll have to update the item caching logic for 4.0 as currently I try GetItemInfo every half sec for 10 secs per item, which is no longer needed. Unfortunately it also means that I can't get rid of the lag for items that are not in the local cache... What's worse: apparently the item cache is cleared on each login :(
Update2: erm, I'll have to check out what exactly happens with this. The info I got about the new GetItemInfo behaviour doesn't explain the lag...
will get back when I find something useful.
cheers,
mitch
Couldn't reproduce it in live after the patch...
cheers,
mitch
To the best of my knowledge, it already works on the ptr. I might have to clean up some spellIds in LibRangeCheck (as most range modifier talents are removed), but since the spell ranges are determined at runtime anyway, they don't really "hurt".
I'll definitely check it out on 4.0 when it hits live :)
cheers,
mitch
I'll test all my addons once patching is done, hopefully everything will be back to normal in a couple of days.
cheers,
mitch
I couldn't see your talent tree with that link. Could it be that it's a pre-4.0 talent tree?
I'll look into the shammy spells (in fact, I'm going over all classes now), so I might find something fishy yet. (unfortunately I don't have a hight level shaman to test with).
cheers,
mitch
Now that I've "laid it on thickly"... ;-)
I've been trying to get to the config screen so I can turn off the sounds. They'd be great if it only worked during combat, but... So my problem is every time I type "/rangedisplay" I get the error message "Failed to load RangeDisplay_Options: DISABLED".
Is there a command I can use to re-enable the options so I can tweak the tool?
Thanks again...
If all else fails, type:
/run RangeDisplay.db.profile.mute=true
in the chat window.
cheers,
mitch
ps: have you checked the 3.8.1 version? sounds are only enabled for enemy units by default in that version.
v3.8.0 auto-locks when first entering combat. Also, a simple ctrl-click on the any of the range frames locks them ;). I'll change the default profile from character specific one to "Default" though (that is, a common shared one).
cheers,
mitch
cheers,
mitch