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).
Comments
-
mitchnull Owner
-
View User Profile
-
Send Message
Posted Oct 23, 2010-
View User Profile
-
Send Message
Posted Oct 20, 2010-
View User Profile
-
Send Message
Posted Oct 21, 2010Make sure you configure the section colors for the "mouseover" unit as well (each unit type has a separate configuration, but there's an option to copy one configuration to all other active units).
Also make sure that you test the mouseover ranges with "proper" targets (critters / mobs / other players outside of sanctuaries). Sanctuaries (shattrath/dalaran) are "no attack" zones and spells are "disabled" there, so I can't use them to check for ranges and fall back to interact-distance based checks (that's when the 0 - 7 - 8 - 28 ranges are shown).
hope this helps,
cheers,
mitch
-
View User Profile
-
Send Message
Posted Oct 21, 2010-
View User Profile
-
Send Message
Posted Oct 21, 2010cheers,
mitch
-
View User Profile
-
Send Message
Posted Oct 16, 20105,8,10,15,20,25,30,35,40,45 etc. and we cant change it.
Please could you do something with that ?
-
View User Profile
-
Send Message
Posted Oct 21, 2010Unfortunately those are the only ranges that I can check with the blizzard API that works for non-party/raid targets, so no, I can't make it any better in that regard, sorry.
cheers,
mitch
-
View User Profile
-
Send Message
Posted Oct 14, 2010-
View User Profile
-
Send Message
Posted Oct 15, 2010v3.8.3 is a quick fix for 4.0.1, I'll make further cleanups in LibRangeCheck-2.0 then I'll release 3.9.0. Till then, 3.8.3 should work.
cheers,
mitch
-
View User Profile
-
Send Message
Posted Oct 14, 2010Open /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
-
View User Profile
-
Send Message
Posted Oct 10, 2010Wont 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
-
View User Profile
-
Send Message
Posted Oct 11, 2010This 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
-
View User Profile
-
Send Message
Posted Oct 11, 2010Update: 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
-
View User Profile
-
Send Message
Posted Oct 14, 2010Couldn't reproduce it in live after the patch...
cheers,
mitch
-
View User Profile
-
Send Message
Posted Oct 15, 2010-
View User Profile
-
Send Message
Posted Oct 10, 2010-
View User Profile
-
Send Message
Posted Oct 10, 2010To 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
-
View User Profile
-
Send Message
Posted Oct 13, 2010-
View User Profile
-
Send Message
Posted Oct 13, 2010I'll test all my addons once patching is done, hopefully everything will be back to normal in a couple of days.
cheers,
mitch
-
View User Profile
-
Send Message
Posted Oct 13, 2010