This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What steps will reproduce the problem?1. Reload UI in raid2. error below3.
What is the expected output? What do you see instead?All unit became visually "out of range"
What version of the product are you using?r303
Do you have an error log of what happened?"Grid2-3.3.0.303\\modules\\StatusRange.lua:72: attempt to call upvalue 'check' (a nil value)\nGrid2-3.3.0.303\\modules\\StatusRange.lua:16: in function <Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:14>\nGrid2-3.3.0.303\\modules\\StatusRange.lua:53: in function <Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:49>\n\nLocals:|r\n(for generator) = <function> defined =[C]:-1\n(for state) = <table> {\n -2147483648 = \"raid10\"\n -2147483648 = \"raid4\"\n -2147483648 = \"raid16\"\n -2147483648 = \"raidpet14\"\n -2147483648 = \"raidpet13\"\n -2147483648 = \"raidpet9\"\n -2147483648 = \"raid13\"\n -2147483648 = \"raidpet11\"\n -2147483648 = \"raid20\"\n -2147483648 = \"raid9\"\n -2147483648 = \"raid15\"\n -2147483648 = \"raidpet16\"\n -2147483648 = \"raidpet14\"\n -2147483648 = \"raidpet16\"\n -2147483648 = \"raid1\"\n -2147483648 = \"raid5\"\n -2147483648 = \"raid2\"\n -2147483648 = \"raid12\"\n -2147483648 = \"raid3\"\n -2147483648 = \"raid11\"\n -2147483648 = \"raid18\"\n -2147483648 = \"raid21\"\n -2147483648 = \"raid17\"\n -2147483648 = \"raidpet16\"\n ", -- [1] "-2147483648 = \"raid6\"\n -2147483648 = \"raid14\"\n -2147483648 = \"raid8\"\n -2147483648 = \"raid19\"\n -2147483648 = \"raid7\"\n}\n(for control) = \"0x0380000001D3DB38\"\nguid = \"0x0380000001D3DB38\"\nunitid = \"raid10\"\nCheckUnitRange = <function> defined @Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:71\ncache = <table> {\n}\nRange = <table> {\n GetPercent = <function> defined @Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:94\n defaultDB = <table> {\n }\n indicators = <table> {\n }\n RegisterMessage = <function> defined @Interface\\AddOns\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:118\n UnregisterAllEvents = <function> defined @Interface\\AddOns\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:202\n Grid_UnitChanged = <function> defined @Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:41\n db = <table> {\n }\n SendMessage = <function> defined @Interface\\AddOns\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:87\n OnDisable = <function> defined @Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:80", -- [2] "\n UnregisterMessage = <function> defined @Interface\\AddOns\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:181\n RegisterEvent = <function> defined @Interface\\AddOns\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:118\n UnregisterAllMessages = <function> defined @Interface\\AddOns\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:202\n IsActive = <function> defined @Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:90\n enabled = true\n Grid_RangesUpdated = <function> defined @Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:62\n OnEnable = <function> defined @Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:24\n name = \"range\"\n Grid_UnitLeft = <function> defined @Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:37\n GetFrame = <function> defined @Interface\\AddOns\\Grid2\\modules\\StatusRange.lua:58\n frame = <unnamed> {\n }\n UnregisterEvent = <function> defined @Interface\\AddOns\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:181\n Grid_UnitJoined = <function> defined @Interface\\AddOns\\", -- [3]
Please provide any additional information below.Turned off an addon on reloaded ui and got this upon re-entering. Error continued periodically until I completely relogged. Sorry for the huge stack, but for some reason the copy from BugSack disappeared and I had logged off.
What is the range value that you set in StatusRange options ? What is your character's class ?
40 yd, Druid. It was only on the reload in the raid.
Ok, I didn't understand that at first. So GridRange doesn't initialize correctly on a ReloadUI().
I'll check that. Thanks for the clarification.
Does this still occur ? On rev316+ ? I have some reports that indicates that it might work.
Okay, as per Ticket 81, this seems to be occuring still.
I can't test inside ICC as I don't raid. The fact that Range checks may be changing depending on the zone you're in is quite disturbing.
You can manually force a Spellbook scan (which should, if successful, clear this error) by typiing the following in chat:
/run GridRange:ScanSpellbook()
Once it's down, please type also the following two lines and post the result here :
/run print(GridRange:GetRangeCheck(40)) /run print(GridRange:GetRangeCheck(38))
I'm particularily interested to know if the returned value is "nil" or "function:<something>" and if the two are "functions", if they are exactly the same or not.
Both scripts return 20DFF6D8 38 (checked 3 times). If it helps, I'm reporting with a rogue and the range issue just popped up in TOC 25H, however but it's happen on my priest in ICC. Just checked the range and although I remember setting range initially to 40 it was showing as nil in the options.
Hmm... That's something quite different than I thought. Can anyone confirm that the setting of range becomes somehow nil ?
Just to confirm, by nil I mean, blank. (Sorry it was late). Next time I'm due to raid is sunday so I'll post again if the error returns.
Range isn't clearing itself during the 3 occurrences of the range error today. However I maintain that it originally was set :p
The error is now appearing in the entrance to ICC as well as TOC. GL and ty for an otherwise great mod.
Okay. Rewrote parts of the implementation. Grid2 should now print some information about the range method used (if any) when updating it's range check.
I'm interested by :
Had a "Grid2 Range updated. No range check function returned, this is an error." today, rev 334, after a UI reload. Got no kind of lua error to post. Got my frames to alpha fade when not in range, after the UI reload, everyone appeared as in range, even if they weren't.
I'm a warrior, my range was set at 38 yards, if i open the grid2 options and check if the value is there, everything is ok.
Edit: Reselecting the range again, or switching it around, fixes the problem, at least until another UI reload. 25 man raid, in ICC
I have a similar error but without an errorlog... the whole evening yesterday 1 person was out of range, he stands directly besides me and grid2 shows him as "out of range" This error was present only on him... me being a Tankadin, having checked Ranged 40m and usually it uses "Gift of the Naaru" as spell for the range check.
http://img713.imageshack.us/img713/492/wowscrnshot021210201302.jpg
Screenshot where clearly 2 people stand beside me, but are out of range!
Pretty sure this is now fixed.
To post a comment, please login or register a new account.