WowAce

http://www.wowace.com/addons/shadowed-unit-frames/tickets/789-new-range-checker-is-intermittently-not-working/

Follow up from the above, still not working.

Using v4.0.7-1-gd3e80e0

I don't see any particular issue at this point. What is the mob you're having the problem on, and what class/spec are you?

Hi. I'm having the same issue.

This doesn't happen constantly, but where I have been able to reproduce it is dungeons - Iron Docks and Everbloom in particular.

I always notice this issue at the first boss (Witherbark, the big tree), then it continues throughout the dungeon. This doesn't seem to happen in the open world consistently, so far I have narrowed it down to when a loading screen happens (zone transition).

Opening the configuration dialogue and changing range-checking spells fixes this issue until I go into some of these dungeons again.

It also happens only on enemy targets and it breaks at 25 yard, see screenshots:

http://i.imgur.com/l0MbojA.png http://i.imgur.com/6i167pk.png http://i.imgur.com/8rJxYtD.png

I'm a Shadow Priest.

EDIT: In those screenshots, my offensive range-check spells were "Shadow Word: Pain" and alternate "Mind Flay"

Do you have the combat fader enabled?

@Shadowed: Go

I can't find that option and I don't recall ever seeing it.

same problem, i ve the range checker with a 40y skill, and it works sometimes like it would be 25y just sometimes, pretty weird, because other times it works perfectly

i'm shaman

Try with latest alpha. I was able to replicate it once but haven't been able to in the last few days.

Tried the latest alphas in a while. Problem is still present, unfortunately.

Range Finder "bugs" out at 20-25 yards in some particular cases.

Odd, I'm really not able to replicate it at all. Hm, let me think about it

Try latest alpha. I've mostly reverted the changes at this point so it should work fine.

This target bug is happening a lot to me as well

What version?

Still happening with v4.0.8-4-gb04843b

To confirm, you did NOT have a problem previously? The current range checker version is pretty close to the old one that people weren't reporting issues for.

Not sure which range checker I started having issues with, all I know is it started happening around 6.0

Is there any way I could check what is causing this with a /dump somehow?