|
Range showing 10 when on Hunter...
Okay I'm sorry if this was said before.... BUT..
When on my hunter, I click ANY mob, it says range 10 .. once pet engages the target, range number change, OR if I make the pet 'stay' and I move to a different spot, and click a target the range shows up properly, but once I have pet move 'follow' range goes to 10 again.... Is this a nui error, or something else? (yes diables ALL addons but nui) - seems it get confused with the distance to pet, instead of target. Also... if I 'resize' from fullscreen to windows (recduced) size I get multiple: nUI Warning..anchoring nUI_HUDUnit_(etc) to nui)hudlayout --anchor point has <nil? value. ((sorry cant copy and paste the chat window for some reason)) using nui 5.0-6.29 (Plus) |
Have you edited any of nUI's layout files?
|
nope.... it just started happening (when I got my pet..) Just start playing a hunter....
on my warrior, lock or rogue it works right... the (nil) value happens on any toon... |
Hmmm... I have a level 80 lock and a level 80 hunter both, can't recall seeing that with either one. I'll look into it.
|
Adding to this one... (not the range 10 thing but...)
Why does this happen? nUI: Warning.. anchoring nUI_HUDUnit_NoBars_Player to nUI_HUDLayout_NOBarsFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_NoBars_Focus to nUI_HUDLayout_NOBarsFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_NoBars_Target to nUI_HUDLayout_NOBarsFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_NoBars_Casting to nUI_HUDLayout_NOBars -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_PlayerTarget_Focus to nUI_HUDLayout_PlayerTargerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_PlayerTarget_Player to nUI_HUDLayout_PlayerTargerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_PlayerTarget_Target to nUI_HUDLayout_PlayerTargerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_PlayerTarget_Castbar to nUI_HUDLayout_PlayerTarger -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_PlayerTarget_FocusTarget to nUI_HUDLayout_PlayerTargerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_PlayerTarget_Pet to nUI_HUDLayout_PlayerTargerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_PlayerTarget_Tot to nUI_HUDLayout_PlayerTargerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_HealthPower_FocusTarget to nUI_HUDLayout_HealthPowerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_HealthPower_Target to nUI_HUDLayout_HealthPowerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_HealthPower_Player to nUI_HUDLayout_HealthPowerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_HealthPower_Focus to nUI_HUDLayout_HealthPowerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_HealthPower_Pet to nUI_HUDLayout_HealthPowerFader -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_HealthPower_Castbar to nUI_HUDLayout_HealthPower -- anchor point has a <nil>value. nUI: Warning.. anchoring nUI_HUDUnit_HealthPower_ToT to nUI_HUDLayout_HealthPowerFader -- anchor point has a <nil>value. This happened when I came back to my computer, after a few mins (computer auto lock) and the screen size didnt change... I have been getting this on a regular basis... then my buttons (pet row) dont work, till I do a /rl .... |
I honestly have no idea why that would be happening. Is your HUD working correctly?
I would suggest maybe deleting the [ Interface > AddOns > nUI ] folder and then reinstall a fresh copy of the addon. It almost looks like parts of the addon are missing, or there's a version conflict. |
it all works properly.... but then again maybe my 'range' error is part of the same problem....
going to delete and reinatl nui now.... will let you know... **** EDIT *** Nope... still same above error..... also disabled ALL addons, went in with 'core' nui... and when running in windowed mode, and you got from maxized to mini screem I get the <nil> value error..... from mini to max or back again.... |
Any luck, looking into these issues?
|
I honestly have no clue what could possibly cause what you're talking about.
|
Have you tried renaming/deleting the character folder in the wtf directory ?
..\World of Warcraft\WTF\Account\<name of account>\<name of server>\ Might be a long shot but who knows. |
Quote:
the <nil> value happen ANY time I resize the game screen... OR return to the game after My computer 'locked' (I lock My computer when I leave it.. else the kids play on it...) Will try to rename the WTF folders and post when I try that.... |
3 Attachment(s)
Nope I am still getting that my 'range' to target is '10' when pet is beside me, if I make my pet stay, and move away from him, then the 'target' distance in the Player/Target HUB works correctly...
I did rename my WTF folder, and no difference.... And if you run the game with 'windowed' mode CHECKED, and resize the screen from blizz default to Maximzed, I get the anchor point errors.... Please let me know what you need to help dupilcate these 2 errors.... Attached Images of what I mean... 234929 - the nil value 235053 - 'Range 10' beside pet 235139 - 'Range (normal)?' Pet made to 'stay' .... |
Quote:
Try RangeDisplay, I hope it doesn't have this issue (if it does, please report it :) cheers, mitch |
I will try again to see if I can repeat either of these errors and let you know what I find.
Quote:
|
posted pics a couple msgs up.... ;)
|
I am also having the same error regarding the incorrect range being displayed.
It was working fine earlier today when I was playing, but at that point I was having issues being able to feed my pet. And before submitting a bug report about it, I deleted my nUI directory and downloaded/installed a fresh copy of it; which fixed the pet feeding issue, but created the range display error. :confused: |
I am also having this problem, tried all the above mentioned steps and didnt fix it. then i redid my talent points and noticed that it started working. so i did talent points one by one and the range problem starts as soon as i put a point in hawkeye for the increased weapon range.. hope this helps track it down.
|
I'm pretty sure having the point in Hawkeye is not a contributing factor to this issue, as I'm going the Beast Mastery route (currently sitting at 11/0/0) and am *still* having this problem.
|
| All times are GMT -6. The time now is 05:05 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI