WowAce

What steps will reproduce the problem?
1. Be in a Raid
2. Have "alpha" indicator to the only status "range"

What is the expected output? What do you see instead?
You're half hidden, because you're "out of range" of yourself! Oo ^^

What version of the product are you using?
r294

Do you have an error log of what happened?
None provided.

Please provide any additional information below.
I *think* this bug was introduced with r292.

I have the same issue with r296.

Tried to check the code but GridRange:GetUnitRange(unit) is returning the right answer (as is: in 10 yards).

One thing I noticed is also that the pets range is quite messed up. I'll try to debug some more later.

Arz

Update: Issue seems disappeared. This doesn't mean it's not there, just I'm unable to reproduce it 100%. One thing I've always noticed tho is: range is slightly wrong. It's set to 40y, but frame start fading at 38y.

Arz

[edit]: I found the issue with the 40y / 38y, opening a new ticket for that one since it's correction is straightforward and the one related to the player oor isn't.

hey,

yeah the bug magicly disappeared after a loading screen (zoning out of obsidian sanctum), couldn't examine further, because we aborted the raid due to heavy lags (day before patch day >.<)

Bye, Ravengus.

Ok, I did several tests, and tbh I can't say anything for sure, but I think I spotted the issue. I might be completely wrong tho, since my LUA coding skills are similar to the ones of a drunk monkey. Anyway, all the comments are referred to StatusRange.lua file.

Point 1: there is a "local cache = {}" definition. I'm not totally sure it's cleaned up correctly after a change in the raid composition, or between two raids. Shouldn't be a biggie tho.

Point 2: terrible doubt. In same file there is a "local function Update()". Now I changed some bits of it, reloaded an nothing happened. NOTHING. Are we totally, absolutely sure that in the following definition of Grid2LayoutFrame, where that friggin' function is embedded in the OnUpdate trigger the *right* one is used and not some other one ?

Anyone reading this is hereby authorized to call me moron if that is impossible, but from my experience in programming nothing is impossible for real.

Other than that, I'm totally clueless, expecially because the "bug" is there, then it's not there, then it's back, then... I hate that kind of bugs.

Cheers, Arz

I am having this same exact problem, in raids I see myself out of range this started ever sense r289, and has continued through each build sense then.

Closing this one, as it is very similar (and probably the same as) Ticket-70. Continue the discussion there.