- More Information
| Created On: | Dec. 8, 2006 |
|---|
- Authors
- About Simple Range Indicator
This is an ace3 version of the very old simple range addon. Now the frame can be locked and moved by mouse and commandline arguments not requiring external addons like moveanything anymore.
Type /sri or /simplerangeindicator to get all options.
When installing this while having the older simplerange, delete the simplerange folder to avoid trouble. The new folder name is simplerangeindicator.
It now contains optional SharedMediaLibrary support as well as RangeCheck-2.0 support and libraries are embedded.
GUI configuration via blizzard's addon UI is also supported.
- Downloads (6)
- Tickets
- Comments
- RSS
You need to login or register to post comments.
Benefits of Registration
- Interact with hundreds of thousands of other gamers on an open social network.
- Post your stories, news, images, videos, and other content to share.
- Create a network with your fellow gamers or join an existing one.
- Gain reputation for everything you do.
- Similar Addons
- 2,836 Auctioneer Auction & Economy, Mail, ...
- 1,176 BigWigs Bossmods Raids & Encounters, Other, ...
- 755 GuildEventManager Group/Guild Management, Raids ...
- 585 Druid Bar Other and Druid
- 541 Minimap Button ... Other
- 8,871 QuestHelper Map and Quest & Leveling
- 4,630 Atlasloot Enhanced PvP, Map, Tradeskill, and ...
- 3,875 GroupCalendar Group/Guild Management, Quest ...
- 3,824 Omen Threat Meter Raids & Encounters
- 3,608 Preform AV Enabler PvP
Advertisement
- +0
- Thumbs Down
- Thumbs Up
Elsia saidThanks for the testing, all very good to know.
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidInstalled v2.4.2 and did tests again.
Sure enough, yes, removing AceTimer-3.0 usage and relying on your own methods has reduced CPU usage of SimpleRangeIndicator (SRI) to comparable levels as RangeDisplay. Nice work :).
Ace3 when SRI v2.4.2 is active uses no additional CPU time. When targeting nothing, SRI & LibRangeCheck-2.0 use no CPU either, as before. But when targeting something, SRI medians 0.073 CPU/sec (a tiny bit higher than before) while LibRangeCheck-2.0 medians at 0.19 CPU/sec. A large improvement; SRI is now better overall in all aspects than RangeDisplay. Not using CPU when you are idle/have nothing targeted combined with comparable in-target usage is ideal.
As well, the Interface options GUI panel (press ESC key, click "Interface" button) for SRI has changed in v2.4.2 to now be fully usable. Also nice work :).
- +0
- Thumbs Down
- Thumbs Up
phamtastik saidI can not get this addon to work, it loads with no errors but everytiem i use the /sri or /simplerangeindicator it does not give any commands. There is no GUI options in the interface as well.
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidI tested it here alone with only the mod & its embedded libraries loading; works fine with no problems.
Which means you most likely didn't install it correctly. You download the most recent version 2.4.2 above? And did you click the "Install Guide" tab (beside "Description" above) and read it/follow it if you don't know how to install mods?
- +0
- Thumbs Down
- Thumbs Up
Elsia saidThanks for this, basically it turns out that AceTimer-3.0 at this time is slow, using GetTime on every OnUpdate rather than using the elapsed argument of it. I removed AceTimer-3.0 for now and replaced it with custom OnUpdate handling. Let me know if that fixed the performance differences you are seeing.
Also the profile options width problem is related to ace3. I added a bandaid for it but really that should be fixed in ace3 and I'll revert that change once ace3 has better default behavior.
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidA few issues after testing v2.4.
--In the new Blizzard "Interface", "Addons" tab, Simple Range Indicator shows up as it should. But the font size slider (when you select "Font") is cut off by the right side of the Interface frame. You can move the slider up to size 30, but then moving it further right is beyond the right side of the frame.
Same thing with the Font face option, but its more serious. The arrow you click to get the font drop down list is cut off by the right side of the frame and is inaccessible. You thus can't change the font at all. Also the same thing when you select the Profiles option for the mod. The text and the dropdown boxes are all cut off on the right side of the frame, making some of it unusable.
None of the Blizzard options in Interface have this problem. They all fit within the frame properly and all dropdown menus can be accessed (such as options within "Mouse" and so on).
--In "## X-Embeds:" in the TOC, there is still "RangeCheck-1.0" listed, even though the mod no longer uses it.
--The following isn't a problem here, as I know where to get the extra library it needs. But the v2.4 ZIP download should include the LibRangeCheck-2.0 library it can use.
--This uses a fair bit more CPU time than the also-updated, Ace3 RangeDisplay.
Having OptionHouse & totally standalone Ace3 (from the Wowace SVN) as the only mods loading, Ace3 itself consumes an average of 0.100 CPU/sec (with CPU profiling enabled).
Load RangeDisplay, LibRangeCheck-2.0 & LibSharedMedia-3.0 in addition to Ace3 & OptionHouse. Median CPU/sec used when that mod is active and you have a target selected (& numbers appear in RangeDisplay's frame):
Ace3: same as above (0.100 CPU/sec)
RangeDisplay: 0.053 CPU/sec
LibRangeCheck-2.0: 0.069 CPU/sec
LibSharedMedia-3.0: none
total: 0.222 CPU/sec median
Next disable RangeDisplay and load Simple Range Indicator. Again all libraries loaded are standalone: Ace3, LibRangeCheck-2.0 & LibSharedMedia-3.0. Select a target to be sure numbers appear:
Ace3: 0.280 CPU/sec median with peaks of up to 0.790 (an increase of 0.180 CPU/sec median).
Simple Range Indicator: 0.046 CPU/sec
LibRangeCheck-2.0: 0.053 CPU/sec
LibSharedMedia-3.0: none
total: 0.379 CPU/sec median. A 71% increase over RangeDisplay.
The interesting thing with this is that when you deselect a target (so SimpleRangeDisplay's numbers no longer appear), the Ace3 CPU/sec usage reduces back down to 0.100 median and both the mod & LibRangeCheck-2.0 use no CPU at all. So there appears to be more performance optimizations that could be made for SimpleRangeDisplay when a target is selected.
The text display of Simple Range Indicator I find far more appealing than RangeDisplay's, so hope these issues can be resolved.
- +0
- Thumbs Down
- Thumbs Up
Elsia saidA new version is now available, which uses Ace3, LibSharedMedia-3.0 and LibRangeCheck-2.0. Options are now inserted into blizzards GUI.
- +0
- Thumbs Down
- Thumbs Up
Elsia saidSome people may already have Rock regardless because they run fubar or carthographer or whatnot. In fact a lot of people do.
Also if you read what I write closely I'm not recommending any framework. I mention that its optionally supported. I.e. I tell nobody to install Rock just to get the GUI. Once I'm sure ace3config works as well it goes into the list.
Above all this addon is kinda happy to not be part of the silly framework pecking that one can find elsewhere though it is happy to be a source of amusement ;)
- +0
- Thumbs Down
- Thumbs Up
Phanx saidI find it amusing that your addon uses Ace2 (a framework) and you're recommending Rock (another framework) as a GUI config option.
- +0
- Thumbs Down
- Thumbs Up
Elsia saidMade 2.3.0.5 default download.
- +0
- Thumbs Down
- Thumbs Up
Elsia saidThanks for reporting this. I'm currently on vacation and won't be back to test anything until the 28th, but I dry-coded and uploaded a new version (2.3.0.5) which hopefully fixes the problem. Can't test it myself unfortunately. Let me know if it worked. I'll make it the default download afterwards.
- +0
- Thumbs Down
- Thumbs Up
reli515 saidHi, I was trying to get this addon to work with 2.3 and I kept getting an error, that said:
"...AddOns\SimpleRangeIndicator\SimpleRangeIndicator.lua:97:attempt to index field 'profile' (a nile value)"
Any suggestions as to how to fix this?
- +0
- Thumbs Down
- Thumbs Up
Elsia saidYeah that should be the error. Try 2.3.0.4. You should get "Range: Unknown" for cases where no intrinsic spell-cast or other interact ranges are available for some reason (like a player in ghost form).
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidDon't know if the bug you fixed is related to the error I received tonight, but...
Testing focus targeting on a new warrior alt with r2.3.0.2. Had a friendly in my party set to the focus. Either clicked the focus frame (running PitBull for unit frames) or something else and the following error came up:
SimpleRangeIndicator-2.3.0.2\\SimpleRangeIndicator.lua:274: bad argument #3 to 'format' (number expected, got nil)
- +0
- Thumbs Down
- Thumbs Up
Elsia saidFound a bug while targeting players in ghost form, when friendly range is enabled. Hopefully it's fixed now with 2.3.0.4.
- +0
- Thumbs Down
- Thumbs Up
Elsia saidHaven't heard of any troubles so 2.3.0.2 is now default download.
- +0
- Thumbs Down
- Thumbs Up
Elsia saidThanks for the feedback Zidomo. I added friendly target support. Use "/sri friendly" or RockConfig/Niagara (if you have rock or niagara installed) to toggle the option. Default is on. Also the new 2.3.0.2 zip contains embedded Ace2 and RangeCheck-1.0 libraries. I opted not to include SharedMediaLibrary to avoid unnecessary bulk. If you want custom fonts, install SML separately and it will be automatically supported.
TOC got cleaned up, as well as option order in RockConfig or Niagara.
Please test this. Once I get positive feedback (or error reports, that I fix) I'll make it the default download. For now it's beta so select it from the downloads list.
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidSRI v2.3.0.1 seems to work OK so far; the ranges it is giving are finally identical so far to what RangeDisplay is showing, tested side by side (which also uses the RangeCheck-1.0 library). But SRI uses far fewer CPU & memory resources, along with looking better than that mod. So, nice work :).
Some things involving the new use of RangeCheck in v2.3.0.1. The TOC should be modified so that "RangeCheck-1.0" appears on both the ## OptionalDeps: line and the ## X-Embeds: line, along with the other libraries used. If you want users to manually deal with RangeCheck (not user-friendly; including the RangeCheck & Ace libraries in the ZIP is recommended), having it listed in OptionalDeps won't hurt.
As to features, something that would be really nice to see in this is the ability to be used on non-combat targets, as RangeDisplay allows. So that you can more easily position raid/party members on fights where distance is an issue, before the fight starts.
- +0
- Thumbs Down
- Thumbs Up
Elsia saidDidn't find any problems with the RangeCheck-1.0 library support so making the beta release download now. I noticed that RangeCheck-1.0 doesn't seem to have very good ranged for Shaman but it's very nice for hunters and mages at least. If you want better Shaman ranges you'll have to bug whoever maintains RangeCheck over at wowace.
- +0
- Thumbs Down
- Thumbs Up
Elsia saidOK I added a beta version (you will not get this from default download yet, just dl from the download list) called 2.3.0.1beta.
It contains RangeCheck-1.0 support if it is present.
I won't bundle RangeCheck-1.0 so go download it from wowace if you want that feature. It works fine without and will use the old interaction ranges that blizzard API provides.
There are 1-2 small things I may wanna add, which is why this isn't release yet. It should work fine though. Don't think there is any chance for a bug here at all.